Titan v2.0 chase problem

[ChiekuRs]

Using the forwards or backwards keys to move to the next or previous step in paused chase is a bit strange - step is changed with delay (that is equal to chase speed).

And also - selecting and deselecting fixture (without changing any parameters) puts it in programmer. Is this supposed to be like this?

[niclights]

Fixture selection is supposed to enter programmer. This is used in 'record by fixture'. I was not aware of this before either!

I agree timing with stepping through a paused chase is strange. It might technically be correct but it is not how it worked in Classic which I believe was more useful.

[Olie]

Using the forwards or backwards keys to move to the next or previous step in paused chase is a bit strange - step is changed with delay (that is equal to chase speed).

I will add this to the list of things to be considered to change. It is one of those gray areas though where some people want it a different way. I know I used to get complaints about the way it worked in classic.

And also - selecting and deselecting fixture (without changing any parameters) puts it in programmer. Is this supposed to be like this?

Yes this is correct. As soon as you select a fixture it is put in the programmer. If you have it in rec by channel then it makes no difference though as you still have to tag a channel for it to be included in a memory. Funny how the only reason you realise what is happening is probably due to the LED state for programmer which is in v2. It has always worked in this way.

[niclights]

Maybe there's a way to have both options?

Many people mention to me that they always liked the old function to step through paused chases using the STOP key. How about implementing this again for stepping without timing and keep forward/back with timing?

[(iCe)]

Hi guys, I would like to add some detail after going nuts yesterday trying to figure out what was going on. I also use unlinked chases a lot which I step with the GO button. Now when I program such a chase and step through it, the delay is messing up the timing. I set the cue overlap to 0% in an attempt to fix this, but it seems the cue overlap value isn't stored when you change it; thus leaving on the delay. You can try this yourself; just set it to 0, leave the screen and enter it again; it's back @ 100 again.

The only way I could find to get the behaviour I wanted was to unfold the chase, edit the times of each step and set the timings to 0 instead of Global (which is the default). I guess the Global setting uses the cue overlap percentage which you cannot alter; so that's where the delay is coming from.

[niclights]

The delay has nothing to do with cue overlap. If you are using unlinked chases (as opposed to the problem of pausing & stepping through a linked chase) then unfold and set delay to zero for each step.

I admit it is awkward that there is actually nowhere to set a global delay which would make this much easier. I had previously considered this a bug, but having discussed later disregarded since this was a function handled by crossfade setting in most circumstances. However, I think this does highlight again why a user might need separate control.