I have preprogrammed 300+ songs with midi commands to trigger what light goes on/off, color etc. All of my trigger modes are set to flash and Latch and solo mode are set to “None.” However, Almost every time that I play the file to trigger lighting, one or another of the switches will stay activated. This causes many of the programs that I have done to sometimes not activate properly. Does anyone else have this issue? Any suggestions?
Just some ideas, I’m sure you probably checked these already, but it never hurts to be sure.
Make sure you are in Live mode. If not, buttons that are pressed in the editor can still be active as you are testing causing overlap.
Are you sure you don’t have midi notes still playing that activate those buttons?
Are you using any sequences? I have had instances where if I have a sequence that hasn’t completed yet and I trigger another scene, it can cause that sequence to stay activated. I had to move my next scene a little later so that it wasn’t overlapping.
Thanks for your thoughtful response.
I definitely have been using the live mode. It doesn’t happen with the same song every time. (then I would know where the problem lies).
I delete any overlapping midi notes in Logic Pro before I finalize the backing track.
I do not use any sequences. I just program all the lights to each song in Logic (midi) then play them as backing tracks using Bandhelper.
The error is not repeatable for me on any given song. It appears I may have to find a way to program in some sort of All Lights Off at each song. Usually, I just go to a blue stage light at the end and between songs
I am concerned about the support of the program though. No updates and deadlines that don’t get met. I have many hours invested in it to move to something else.
I found that I needed 40ms at least between midi notes. Any less that this and the results were variable. 40ms makes it all work every time,
I don’t have time to test it today but, do you find that it becomes a flashing light using 40 ms? What I mean by that it let’s say a blue light is going to turn to red. Does the light fixture go from blue to off completely then on to red? Is that 40 ms of “completely off” noticeable? I know it is a very short time but I do avoid strobe type effects. Thanks for your help
Yes, I do have the same issues. Midi commands intermittently not triggering the programmed buttons. It does not always happen, so there is no programming error and it can happen in different songs or different places.
My only remedy up to now seems to be to artificially pull notes (also note off events) apart from each other. This seems to prevent timing issues in the processing of notes in Photon. It is a pain of course because you can’t have your notes snap to the beat in your DAW when programming the lightshow…
I send a midi note for blue on, then some time later send a midi note for red on. In the fixture the ligh just changes from blue to red. If they are different fixtures then send blue fixture midi note on, off. That turns that one on. Then to swap to another fixture that is red. send midi note on for the red one, then 40ms later midi note on for the blue to set it off, then 40 ms later midi note off for the red fixture. I use latching rather that flash.
Are you going from Blue to red in one fixture and do you use flash or latch ?
I use primarily one fixture for both blue and red. Normally, I program a midi note to send an on message to a light that is red (for example) then at a specific beat or chord change, I program that same light to change to blue. It works most of the time. But not all of the time. After a number of songs, it appears on the “live screen” that a number of lights are still on, and they should not be. Thanks for answering.