This thread will address a couple of issues in one. The first is that I have been unable to load a preset to an “alternate” scene (one other than the saved state) without what I consider to be an unacceptable delay, during which the saved scene is audible. Even with the CC #43 message following behind the PC by no more than 1/256 note, the saved scene will be loaded long enough to hear it for a second or so. This is brutally noticeable for songs where the “start” is a scene set up for acoustic guitar. We load the song to Scene A via CC #43, but first it opens up Scene E, where the acoustic guitar is run through a high-gain chain for long enough to scream at FOH before it changes.
I could open a brand new preset for the acoustic song, but the goal was to operate within one (or two) presets for the whole show. This just seems like an insane flaw to accept from the unit.
The second (related) issue is that sometimes, a PC message followed by a Scene Change (CC) will result in the unit switching back and forth between those two scenes up to 4 times before landing on (hopefully) the correct one. Again, each change is audible. I conferred with another player I know, who said this often happens to him as well. What is going on here, and is there any way to address these issues?
Try to find out if there is a chase event setup and disable it. In my case this was activated in Cubase and was causing such behaviour. After deactivating chase events als is working as expected.
Thanks for the reply. Really not sure what you mean here, but in any case, I’ve simply avoided loading alternate scenes. Now, every song just gets its own preset.
How do you send the MIDI messages to the QC? Do you use the DAW to send the messages? If you use the DAW you must disable the Chase Event settings. In Cubase, which I use to send MIDI messages, these are under preferences >MIDI.
I just checked our DAW (Ableton Live) and “Chase MIDI Notes” is enabled in the Options menu. Again, we are no longer in need of a “fix” because I’m now using a different preset for every song, but I’m not sure we’d want to disable that option. Based on my understanding of it (based on a Google search after reading your reply), it seems that Chase setting is responsible for us being able to start a song or section halfway through and still have the Quad Cortex load the correct songs/scenes. If disabled, it would not load the correct preset if we started from, say, the bridge section (which is common during soundcheck).