Q Light Controller+

Hi Everyone
I am new to QLC having used freestyler for a number of years. This seems much easier, but I have hit one issue. I tend to create multiple cue lists for the bands I am working with, and change on the fly to different cue lists for different songs, or within one song. I like to have each cue list automatically looping through the cues from a sound input (from the base drum mic). I have managed get an audio trigger working to run through a cue list. Do I have to create an audio trigger for every cue list? Is there a way to have an audio trigger that will trigger whichever cue list I have active?
I know that creating a sound trigger for a cuelist is fairly easy, but my concern is that if I discover during a show that the audio setting on the audio trigger needs changing then I would need to change all the audio triggers. I think I am missing something obvious.

I am running 4.12.4
thanks

Ken

I have one way to do this
1) add a generic dimmer to channel 1 on unused universe 2
2) Set universe 2 to have a loop back
3) Create an input profile for universe 2, dmx type, with channel 1 set to fader
4) Create a scene "sound_on" with channel 1 universe 2 dimmer set to full on
5) In VC create a flash function button to flash "sound_on" scene
6) Create Audio trigger and assign one item to VC widget button just created
7) Create solo frame
8) Add cue list to solo frame, and set "next cue" to input universe 2 and input channel 1, set behavious on "cue list" to "do nothing"
9) Add any other cues to solo frame with same settings
Run and whichever cue you select will move on when triggered by sound (or click flash button for testing purposes).

Thanks to people on this thread for point in the right direction viewtopic.php?f=29&t=15371

This shows how powerful the software is, but also seems a bit of a complex method to achieve this. Is there a simpler way?

Ken

For your specific purpose, there is no other way. Once you get used to the loopback magic, you'll easily see and follow the built structure.

Any clues on porting this from the Mac to the Pi? These steps work great on my Mac. But on the Pi, I can't seem to get the sound-on flash function button to be activated by the audio input.

I've created very simple audio input -> cue list shows, and it will work briefly. Then it stops working. Does the audio trigger work reliably on the Pi?

Follow up on the post above. I have things working on the Pi now, but I don't know specifically what was wrong. In order to get it working, I built a new virtual console, step by step. First the audio input and the sound_on button. Then one cue list. Then two cue lists. Then I added MIDI inputs for a foot controller to select the cue lists. Something about the order of building the VC is important I think.