The band I’m currently touring with runs with a skeleton crew. I’m using more and more automation during the show. LV1 is currently sending and receiving MIDI program changes to and from Q-Lab which recalls my console scenes and Q-Lab cues. Q-Lab handles lighting, video, and backing tracks. I also have Q-Lab starting and stopping my Reaper records, dropping markers at scene changes, and naming the markers for the song. So, I have a lot going on.
The problem I’m running into is that the Scene 1 always responds to program change 1. Scene 2 to program change 2 , etc. When I rearrange my scene list on the LV1 to put it in order for the set list that night, LV1 renumbers the scenes and breaks the cues in Q-Lab because now Song 1, which was scene 1, might now be song 5. Since LV1 renumbers the scenes, the midi program number changes and Q-Lab will recall whatever is now responding to program change 1.
The same is true in reverse. If I’m recalling scenes on the console, Q-Lab will fire the wrong cue if I’ve rearranged the LV1 scenes.
My workaround currently is to only recall scenes on the console via Q-Lab, which works, (I can put my Q-Lab cues in any order I want) but I would love to have my scenes in the proper order on the console. I would also prefer to have the console fire the cues in Q-Lab.
My request is that I can define a program change number per scene and have it stick with that scene regardless of where it is in the scene list. It would also be nice is there was a direct OSC implementation… even if it was just for basic functions such as mutes and faders.
