[Noob] [Solved]can I send multiple commands from the same source?

[Sixgun77]

My midi controller(midi captain std) allows one switch to send multiple commands via sequential presses. For example, switch number one can send 4 different commands for 4 short presses, and 4 different commands via 4 long presses.

Here's what I'm trying to do: hit button one on the controller to start the chase for a given song, then hit the same button to switch to the chase for the chorus, then hit it again to go to the chase for the guitar solo, and so on.

I tried to test this out by making a green scene and a blue scene, but I can't get them to swap from one scene to the other by hitting button one on the controller multiple times.

Part of the problem is that the button widgets toggle on/off with sequential presses. Is there a way to stop that? I tried toggling the extra press in the button wider Properties in the profile editor, but that didn't do it. I don't see a way to set one button widget to fire off different functions. Is there a better way to go about achieving what I'm trying to do? Does it matter what midi command type I use(CC, midi note, etc)?

I'm sorry about all of the noob questions, I'm still learning what this program can and can't do.

[MichelSliepenbeek]

I don't see a way to set one button widget to fire off different functions.

Have a look at Collections https://docs.qlcplus.org/v4/function-ma ... ion-editor.

Another option could be the use of Scripts https://docs.qlcplus.org/v4/function-ma ... ipt-editor

[Sixgun77]

I'll take a look at that, i haven't used collections or scripting yet.

Is what I'm attempting even possible using the widgets? I'm assuming that there's a setting i don't know about.

Assume I'm pressing button "A" on my midi controller 4 times.

1st press (midi CC 10) triggers Button Widget 1 which triggers chase #23
2nd press (midi CC 11) triggers BW 2 which triggers chase #4
3rd press (midi CC 12) triggers BW 3 which triggers chase #86
4th press (midi CC 13) triggers BW 4 which triggers chase #25

Does the type of midi command matter? Is there a chart for midi note commands for qlc+ like my dmx board has? Maybe I can try doubling the midi command in press 2-4 to see if that will "double toggle" the widget? Removing the widgets from solo frame didn't seem to help any.

Thanks for all of the suggestions. I work 10hr shifts with a 1hr commute each way, so I have far more time to wonder about this stuff than I do to actually try programming it and testing it out, so the help is extremely appreciated.

[GGGss]

Assume I'm pressing button "A" on my midi controller 4 times.

1st press (midi CC 10) triggers Button Widget 1 which triggers chase #23
2nd press (midi CC 11) triggers BW 2 which triggers chase #4
3rd press (midi CC 12) triggers BW 3 which triggers chase #86
4th press (midi CC 13) triggers BW 4 which triggers chase #25

Since the midi signals are distinguished, your VC buttons are addressable.

Does the type of midi command matter?

It can be note-on-off or CC - doesn't matter ... if you had tried it already you'd have noticed.

Is there a chart for midi note commands for qlc+ like my dmx board has?

Not at all. Every midi command can be used. You can create an input profile to keep an overview when things get complicated.

Maybe I can try doubling the midi command in press 2-4 to see if that will "double toggle" the widget?
Removing the widgets from solo frame didn't seem to help any.

Are you asking us now why your sequences don't stay activated? I'm not sure what you want to achieve or what you experience.

If you put your button inside a solo frame, they will cancel the functions running and start the newly selected function. All four functions can run in parallel if you place your buttons outside of a solo frame.

Thanks for all of the suggestions. I work 10hr shifts with a 1hr commute each way, so I have far more time to wonder about this stuff than I do to actually try programming it and testing it out, so the help is extremely appreciated.

We can talk theoretically, like I am doing, but you need some practical knowledge before you can think about things theoretically.

Returning to the initial question, the solo frame is the way to go...
So, knowing all about the above, in one sentence, what do you experience as problematic?

[MichelSliepenbeek]

My midi controller(midi captain std) allows one switch to send multiple commands via sequential presses. For example, switch number one can send 4 different commands for 4 short presses, and 4 different commands via 4 long presses.

It is very nice that your controller has these options but i would not use it.
There is an easier way:

Your midi controller has also the options to use a number of banks (i guess it was 16) and you can switch banks Up and Down with the two buttons on the right.
Create a standard Frame on your Virtual Console.
Open Properties and on the Pages Tab box Multiple Pages On, box Circular Scrolling On and set the number of pages to 16 (if it was 16, otherwise use the same number as your controller has banks).
For External Input - Previous Page select Auto Detect and press the Down Button on your Midi Controller and for External Input - Next Page select Auto Detect and press the Up Button on your Midi Controller.
On the bottom off the screen you can change the name of each page from Page - 1 (Page -2, ...) to something more meaningfull (for instance the name of the song).

I assume you know that in QLC+ for a Multi Page Frame only the page that is on top is active (the manual does not mention that, but now you know ).
This also means that you need to set up your External Controls for every page again (even when they are the same).


Now create (up to) four Cue Lists on each page (to run the Chasers you want to use for that song, so could be different for each page).
Use the 4 Top Buttons of your Midi Controller to Start and Stop those Chasers and use the 4 Buttons on the Bottom to skip to the Next Step of the chaser (short Press, or move to the Previous Step of the chaser with a long press. This is when you want to correct a mistake).


To get the Page Numbers on Your VC in synq with your Controller at start up, make sure to set your Multi Page Frame to page 1 when you save your workfile.
If you have more than 16 songs: create another Multi Page Frame, and give the pages names like Set 1, Set2, ...... and put a Multi Bank Frame on each page.

[Sixgun77]

So, knowing all about the above, in one sentence, what do you experience as problematic?

The problem was that the 1st button press would work as intended, but the next press would shut the lights back off instead of triggering the next chase or scene that I want.

I think it's solved now, I got it running properly after work last night. Part of the problem was that with all of the troubleshooting I was doing, i had multiple widgets linked to the same functions and controller button.

I was originally using the solo frame, I only moved widgets out of it to see if that was part of the problem. Also, I had indeed tried both midi note and cc commands. Since nothing was making any difference i asked here in case there was something related that I didn't know about yet.

[Sixgun77]

My midi controller(midi captain std) allows one switch to send multiple commands via sequential presses. For example, switch number one can send 4 different commands for 4 short presses, and 4 different commands via 4 long presses.

It is very nice that your controller has these options but i would not use it.
There is an easier way:

Your midi controller has also the options to use a number of banks (i guess it was 16) and you can switch banks Up and Down with the two buttons on the right.
Create a standard Frame on your Virtual Console.
Open Properties and on the Pages Tab box Multiple Pages On, box Circular Scrolling On and set the number of pages to 16 (if it was 16, otherwise use the same number as your controller has banks).
For External Input - Previous Page select Auto Detect and press the Down Button on your Midi Controller and for External Input - Next Page select Auto Detect and press the Up Button on your Midi Controller.
On the bottom off the screen you can change the name of each page from Page - 1 (Page -2, ...) to something more meaningfull (for instance the name of the song).

I assume you know that in QLC+ for a Multi Page Frame only the page that is on top is active (the manual does not mention that, but now you know ).
This also means that you need to set up your External Controls for every page again (even when they are the same).


Now create (up to) four Cue Lists on each page (to run the Chasers you want to use for that song, so could be different for each page).
Use the 4 Top Buttons of your Midi Controller to Start and Stop those Chasers and use the 4 Buttons on the Bottom to skip to the Next Step of the chaser (short Press, or move to the Previous Step of the chaser with a long press. This is when you want to correct a mistake).


To get the Page Numbers on Your VC in synq with your Controller at start up, make sure to set your Multi Page Frame to page 1 when you save your workfile.
If you have more than 16 songs: create another Multi Page Frame, and give the pages names like Set 1, Set2, ...... and put a Multi Bank Frame on each page.

I haven't tried que lists at all yet, I'll give that a try. My midi controller will allow up to 99 banks/pages. The 2 right most switches are bank up and down(long press), i was planning on making one blackout and one just a static scene for between songs or if something goes wrong(short press). I can also have up to 4 long press commands, 4 long release, and 4 short release per switch.

If I get comfy with the que lists, I may try something slightly different. I might long press to start, and then short press to advance. Our current set list is 60 songs and we're writing more material, so I was planning on 8 songs per bank if I can make that work, just so it's fewer pages(less book keeping). I also have to go in and program the 3 segment LED rings for each switch

Thanks very much for the helpful information, I haven't tried to sync bank up/Down with the pages in a Frame yet. Why standard Frame instead of solo? Won't that leave the last que list running when I start a different one?

[MichelSliepenbeek]

I haven't tried to sync bank up/Down with the pages in a Frame yet

If you power on your DMX controller it will start with Bank 1. This means you have to ensure that QLC+ will also start at Page 1. That's all.

Why standard Frame instead of solo?

You can always use a Solo Frame within a Standard Frame, but once your Functions are within a solo frame you cannot stop the exclusion mechanism for specific functions.

Just an example to explain: for a number of moving heads i use a color selector with 7 colors, i have 7 buttons to select a gobo, i use 5 buttons for different positions and a few buttons to run RGB Matrices.
If you put everything in one solo frame, selecting a gobo would unselect the color, deactivate the position and stop the RGB matrix. That's not what you want.
Therefor use a specific solo frame for your color selector, use a specific solo frame for your Gobo's, use a specific solo frame for your positions and use a specific solo frame for your RGB matrices.

Now create (up to) four Cue Lists on each page

I used "up to" for a reason: It is possible to use more than one cue list, that way having two chasers running in parallel (at least if you don't put them in a solo frame).
You can use one chaser for Color changes (to create a specific mood) and another one for Level changes (like a strobe) to put accents on certain parts (like a drum break).
It is also possible to use the remaining buttons for other functions (like RGB Matrices, positions for your Moving Heads, ....).

[Sixgun77]

Just an example to explain: for a number of moving heads i use a color selector with 7 colors, i have 7 buttons to select a gobo, i use 5 buttons for different positions and a few buttons to run RGB Matrices.
If you put everything in one solo frame, selecting a gobo would unselect the color, deactivate the position and stop the RGB matrix. That's not what you want.
Therefor use a specific solo frame for your color selector, use a specific solo frame for your Gobo's, use a specific solo frame for your positions and use a specific solo frame for your RGB matrices.

Now create (up to) four Cue Lists on each page

I used "up to" for a reason: It is possible to use more than one cue list, that way having two chasers running in parallel (at least if you don't put them in a solo frame).
You can use one chaser for Color changes (to create a specific mood) and another one for Level changes (like a strobe) to put accents on certain parts (like a drum break).
It is also possible to use the remaining buttons for other functions (like RGB Matrices, positions for your Moving Heads, ....).

That's way more than I'm working with, but good to know. We have 6 pars, and that's it. Would using a single tap button or midi switch(completely separate from my current midi controller) as the advance button for the cue lists work? Then I could have my 8 different songs per bank, AND not run the risk of hitting the wrong button mid song(I'm running lights with my foot onstage while playing fretless bass and singing lead vocals). It would be nice to know BEFORE buying more hardware.