MIDI Triggers ignoring fade times
-
Hi guys, I have a very simple problem, but I can't figure it out!
I have a Program Change watcher that is triggering a Jump++ actor. The program value sets the scene number in the jump actor, and the trigger triggers the jump.It jumps fine, and takes scene data from the Program Change watcher just fine, but it ignores the fade times programmed into the Jump Actor.Can anyone explain why? I don't have anything affecting the fade times on the Jump Actor, and it fades just fine when I trigger it manually from within the patch, but when I trigger it via MIDI Program Change, it ignores the fade time.Almost as if it is getting a double-trigger from the Program Change watcher. Is that possible? -
to check what you are sending get MIDI Monitor
[s n o i z e : MIDI Monitor](http://www.google.ee/url?sa=t&rct=j&q=midi%20monitor&source=web&cd=1&cad=rja&uact=8&ved=0CCgQFjAA&url=http%3A%2F%2Fwww.snoize.com%2FMIDIMonitor%2F&ei=FiCEU_qpLMXiPN_fgeAP&usg=AFQjCNE05hOEJI9RUJmbnd3XIK9vzsSzYg&sig2=sLvq3oLNozFFRrElTefmEg&bvm=bv.67720277,d.ZWU) -
Try to change the input value of the control watcher from "0-127" to "127". It will avoid watcher to send multiple triggers.
Or try to insert multi blocker actor between control watcher and jump scene with the time value set to the duration of your fade or higher.Best Philippe
-
A screenshot might be handy if possible?
-
As fifou suggested, you are probably receiving multiple triggers from the MIDI input. Typically "button press" type MIDI events will send a 127 when pressed and a 0 when released. When a jump actor receives a second trigger while the fade is still active, it will jump to the new scene, ignoring the fade time.
-
@CraigAlfredson is right. His solution will work.Another way is to use use a Comparator actor. Send the MIDI value to the 'value 1' input, and set the 'value 2' input to 127. Ensure the mode is set to 'eq' -> "equal to." Then you'll get a trigger every time a 127 arrives.
Best Wishes,Mark
