Solved / Cue List Pause from midi controller

Report an issue that you found while using QLC+ 5.x.
Please provide as many details as you can, a sample workspace if available and don't forget to read the forum posting guidelines first !
Post Reply
giacomo
Posts: 569
Joined: Tue May 26, 2015 6:17 pm
Real Name:

Hello,
I've noticed today that the pause is not working from a midi controller,
Play button from a midi controller is working normally but when I press it again anything happens.
Nano Kontrol 2 - last appimage 20230307
Ravel_CafeMuller_00.qxw
(86.24 KiB) Downloaded 211 times
ps. nice improvements in cue list navigation :)
http://qlcplus.org/forum/viewtopic.php? ... ist#p66667
Last edited by giacomo on Mon Mar 13, 2023 12:03 am, edited 1 time in total.
User avatar
mcallegari
Posts: 4932
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

I just tested this and it works as expected (with a nanokontrol 2 btw)
giacomo
Posts: 569
Joined: Tue May 26, 2015 6:17 pm
Real Name:

here a video of the same file and nanokontrol2:

https://my.opendesktop.org/s/jXMbWe7jSnDF9dx

1) I press PLAY and the cue list stops at cue 01;
2) I press NEXT > > cue 05 and around the middle xfade I press PLAY/PAUSE > > the PLAY button becomes green but the transition doesn't stop.
3) I press NEXT > > cue 08 and I try the same, the PLAY button is still green and anything happens.

Could it be because I don't have v4 installed?
Last edited by giacomo on Mon Mar 13, 2023 12:02 am, edited 3 times in total.
User avatar
mcallegari
Posts: 4932
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

I don't think so.
Does this issue happen in every project or a specific one?
I tried on a simple project and it worked
giacomo
Posts: 569
Joined: Tue May 26, 2015 6:17 pm
Real Name:

Massimo, I just added a video to my answer while you were writing.
I've tried a new simple project and PAUSE it's working normally, not in the project uploaded.
I've tried to delete the cue list and added it again but the issue is still present.
Maybe it's an heritage from an older v5 version?
The issue is not relevant for this performance, thanks to look at it.
Post Reply