Q Light Controller+

kenact wrote: ↑Mon Sep 18, 2023 4:50 pm Are you trying to start a chase from the 1st step, whenever you trigger the midi drum pad?

MichelSliepenbeek wrote: ↑Mon Sep 25, 2023 9:25 am You could use a Script to Retrigger.

• Create a function
• Create a button on the VC
• Set button to "Launch Instance of function"
• (In the background, QLC+ duplicates your function in a hidden folder x number of times)
• Operate Mode
• Press button, button goes green while the function runs and clear when the function stops
• Press button multiple times, an instance (contained in the hidden folder) is launched for each button press. Button goes green while the functions run and clear when all the function stop.

MichelSliepenbeek wrote: ↑Mon Sep 25, 2023 9:25 am You could use a Script to Retrigger.
Basically you only need to Stop the function and then Start the function again.
So:
Stopfunction(functionXYZ)
Startfunction(functionXYZ)

Depending on the type of function you may have to put a Wait behind the Start (if functions don't have a Running Time, they get started but End immediately, so it will look to you as if the Script isn't working).

Create a Script, put a button on your VC that launches this Script and add the intended Midi Messages as External Input.
Now it is up to you to play with the parameters (including the Wait in your Script) to get the Timing Right: do you want a chaser to Loop or only to Run Once and how long should it remain on, should it Fade In, ..............


Warning: if you Change the name of a Function, all Buttons, Sliders, Collections etc related to this Function will automatically use the changed name.
This does not apply for Scripts: you need to change the changed name of your function manually.

If i set the "script button" in VC to Flash-mode, nothing happens with the function

Or did I get something wrong?

julianb240393 wrote: ↑Sun Feb 11, 2024 8:42 pm
I put "stop function", then "start function" and then "wait 10h" in the script

1. Build a chaser with whatever lighting content you want to be able to trigger. Set its Run Order to "Single Shot".
2. Build another chaser containing exactly 2 steps. The first step should be a "null" scene (with nothing defined), with timing set to 0ms fade in, 0ms fade out and 0ms hold. The second step should be the real chaser, with timing set to 0ms fade in, 0ms fade out and a hold time that matches the "real" chaser's run-time.
3. Add a Cue List widget to your Virtual Console, tie it to the 2-step "parent" chaser, and configure external MIDI input to trigger the "Previous" button. (be sure to keep the default option to "Run chaser from first/last step" if Next/Previous buttons are pressed when it's not active)
4. Depending on how your drum pad sends MIDI notes, you might have to reconfigure your Input Profile. I tested on Windows from external software called MultiPlay, routing MIDI into QLC+ via LoopBe1, and had to tweak the Generic-MIDI input profile before it would work. I re-configured the selected MIDI note as a "Button", and then enabled the optional Behaviour to "Generate an extra Press/Release when toggled". If you find you need to do this too: start on the Input/Output pane, then select the universe with your MIDI Input, switch to the Profile tab and edit your Input profile, click over to the Input Profile Editor "Channels" tab, locate the selected note, set it's Type to "Button" and then check the box to generate the extra press/release.

• It'd be nifty if the hold time on a chaser step that is a "sub-chaser" could be auto-calculated to match the overall duration of the sub-chaser... We don't want "infinite" in this case; we just want to "play the sub-chaser until it stops on its own".

• To use a VC Button instead of a Cue List to drive this, the only thing missing is to be able to re-trigger it while it's playing (it automatically becomes inactive once the chaser finishes, and can then be started again as desired). Would there be value in coding up a new external input option that could "re-start" the associated function if the external input is received while its function is already running?
  It would probably only make sense for functions that stop on their own; otherwise you'd have no way to turn it off using external input.... I've already done some work on a custom fork to add an option to change the toggle handling -- specifically to let external input tell the button to turn "on" if a non-zero velocity is received, and "off" if a zero velocity or note-off is received, instead of just toggling between off and on every time a non-zero input is received. If there's general value in letting a second "on" command "re-start" a function, I might consider adding that to my custom fork also. And I'd be happy to submit a PR for it someday too...