Repeating a Cue List sequence from MIDI does not seem to work.
I've created a Cue List From a Single Shot cue list. It's 'next Cue' value is keyboard key '1' and Midi CC 64. It's 'stop' value is keyboard key '2' and Midi CC 20.
If I press '1', the Cue List sequences until the end and stops, as it should. I can press '1' again to perform the same sequence as long as I first press '2' (to 'stop' it). Not sure if that is what is supposed to happen, but, it works. Unfortunately, the same does not happen with MIDI events. Even though I send the 'stop' midi event (CC 20), I cannot start the cue list more than once, even if I hit keyboard 2 to 'stop' it first. The only way I can re-trigger the cue list is to exit run mode and load the project again.
This appears to be similar, but, maybe not the same as this: https://sourceforge.net/p/qlcplus/discu ... it=25#6c5d
Cue List Won't Restart from MIDI unless project is stopped and reloaded
-
john poremba
Upon further investigation, it appears the Cue List stop External Input is ignored.
A simple test: run a looping cue list and try to stop it with a MIDI signal. I can't get this to work. A button triggered off the same MIDI event sees it, but, cue list stop does not. Hope this helps...
A simple test: run a looping cue list and try to stop it with a MIDI signal. I can't get this to work. A button triggered off the same MIDI event sees it, but, cue list stop does not. Hope this helps...
-
john poremba
Further Light on the subject ('value' is the 3rd MIDI byte):
1) Midi In and Midi Out are not symmetrical (out can send single messages, in requires message pairs in some cases). Except for sliders, MIDI in requires two message words: A 'value' > 1 followed by a 'value' of 0. Otherwise, it is not reliable. Specifically,
A) a 'value' of 1 followed by a 'value' of 0 works for buttons, but, not cue lists (where only the first such event is acted upon). This is a bug.
B) if a 'value' of 0 is not received, further messages are ignored. This might be a bug, but, is at least questionable and a reliability issue.
2) Just because learned inputs in buttons/Cue lists work doesn't mean the function will work as it has to follow 1) above too.
3) If 1) is violated, it can make future MIDI input signals unreliable, possibly bytes out-of-sync. If this happens, it will requiring a QLC exit and restart.
Hope this helps...
1) Midi In and Midi Out are not symmetrical (out can send single messages, in requires message pairs in some cases). Except for sliders, MIDI in requires two message words: A 'value' > 1 followed by a 'value' of 0. Otherwise, it is not reliable. Specifically,
A) a 'value' of 1 followed by a 'value' of 0 works for buttons, but, not cue lists (where only the first such event is acted upon). This is a bug.
B) if a 'value' of 0 is not received, further messages are ignored. This might be a bug, but, is at least questionable and a reliability issue.
2) Just because learned inputs in buttons/Cue lists work doesn't mean the function will work as it has to follow 1) above too.
3) If 1) is violated, it can make future MIDI input signals unreliable, possibly bytes out-of-sync. If this happens, it will requiring a QLC exit and restart.
Hope this helps...
-
Massimo Callegari
Hey John, sorry for the delay.
Cue lists not accepting the stop key is a confirmed bug.
I've already solved it some days ago. Will be available in the next version.
Basically now with an external controller you can map a button that acts like the Cue list UI start/stop button.
Thanks for spotting this out.
Cue lists not accepting the stop key is a confirmed bug.
I've already solved it some days ago. Will be available in the next version.
Basically now with an external controller you can map a button that acts like the Cue list UI start/stop button.
Thanks for spotting this out.