Variable in Step Based Cue Help

Thank you for reaching out.

I'm not seeing the effect restart, but I think I know what makes you say that. The change of the variable values happens in 0 and neither follows the cue time nor the effect's entry/exit time.

Can you confirm that you're also seeing the immediate change rather the effect restarting?

For me, if I wait in Q1 for a while to get through a few of the steps, the moment Q2 is sent, the effect restarts from step 1 and in the timing of the variable change recorded in Q2. What Nick described to me at LDI was that the variable would fade from value to value in the cue's timing, and that the rest of the effect would continue as if it had simply tracked through.

I just had a look at your showfile, sorry that I didn't before i responded the first time.

The reason why the effect restarts is that you change Variable 3 which is a timing variable. Those can't be changed without the effect restarting.

Regarding Variables 1 and 2 which are for the Level: It's currently written up (but not available in the software) that changes to effect variables should happen in cue time.

[EOS-51077]
Effect variables, allow crossfade for changing non-timing variable in cue transition

I will add a note that you ran into this as well.

I just had a look at your showfile, sorry that I didn't before i responded the first time.

The reason why the effect restarts is that you change Variable 3 which is a timing variable. Those can't be changed without the effect restarting.

Regarding Variables 1 and 2 which are for the Level: It's currently written up (but not available in the software) that changes to effect variables should happen in cue time.

[EOS-51077]
Effect variables, allow crossfade for changing non-timing variable in cue transition

I will add a note that you ran into this as well.

Ah man - this is the exact scenario that I was describing to Nick at LDI - and the second project where I'd like to do it. It's a real shame that it's not possible to have a smooth-fading, rolling chase progressively transform into a rhythmically strobe effect. Personally I feel like any parameter should be able to fade between values within an effect, since it's not possible for multiple effects to share parameters using HTP or LTP. Under many circumstances (at least in things that I want to do), it means that I cannot program what I can envision...

Sounds like a feature request!