MIDI triggering a scene induces unwanted fade in/out

[booksix]

Using MIDI from Ableton to trigger my light show. It's going great but I have a weird issue:

I'm currently working on some strobe/pulse effects using some LED tubes and basic DMX dimmer packs. I have a scene that sends the dimmer to 100% and have it as a function for a button which is set to "flash function". Works perfect if I click the button in the VC - instant on/off (as intended and expected). However, If I trigger that SAME scene/button with MIDI it creates a fade in and hold/ramp out. I should also point out that I tested this with the button in "Toggle" mode and I get the same fades when triggering from MIDI but not clicking the button in the VC.

My current work around: If I put the SAME exact scene into a chaser, and trigger the chaser's button from MIDI the on/off is also instant (meaning the problem goes away) - but this means I have to create a new chaser for every different strobe effect I want, and constantly be modifying it's tempo dial to change speeds - vs just placing midi notes to create flashes... not ideal!

Why would the external triggering of a scene via MIDI cause it to fade/ramp? QLC+ 4.12.7

[GGGss]

And your scene has fade-times built in? -> remove those!
Re-use of the same scene (midi vs button-bound scene on your VC?) Do NOT reuse the same scene; create / make a copy / duplicate, or you will be in trouble (Calling that scene will undesirably call the shadow scene also!)

and ... we are @4.13.1 - use the latest version => we try to build on top of the previous version and do not want to regression debug issues (which IMHO lies in the reuse of the scene in question here...)

Send in your project-file to be sure about ^^^^

[booksix]

My bad - I actually stupidly thought scenes couldn't have fade times in their own programming - pretty stupid of me, especially since the dial button is right there And I only re-used the scene in the chaser to prove the point that it would not fade so the exact same scene HAD to be used (I won't do this in my production setup and already use duplicates for any scene that are used solo vs used in chasers).

As for updating QLC, yes I know I'm behind... but I've been building a complex rig that started from a scene on my current version of QLC. I don't have a real reason to update just before a super important show - I am having no real bugs or stability issues. I'm sure it'd be fine but that'd be an illogical risk and I can easily update at a later date when my touring season is wrapped for the year.

Anyway, thanks for clarifying in my dumb moment!!

[booksix]

... I take it back. Yes I was dumb but this did not actually solve the MIDI problem.

Fade times are 0h 0m 0s 0ms on all scenes for this purpose... When I manually click the button in the VC it is instant on/off, when I "MIDI click" the button via Ableton I get a fade in/out.

TBF, *maybe* this is behavior that isn't present in 4.13.1... I guess I'll have to try if all else fails!

[booksix]

Here is a test project file where the behavior is exhibited. I can upload a video if helpful, too, but essentially what I said above is happening: If I click the VC button with my mouse I get an instant on/off strobe behavior. If I click/play/program the MIDI note assigned to this button from Ableton I get a ramp in/out, and seemingly a short hold, too.

This also shows that it is not scene-fade related, nor scene re-use related (which, to be clear again, was not my original implementation). Anyway, thanks for any and all input!