The Avolites Discussion Forum

Hello,

Isn't there a bug with temporary chase speeds (actually not being temporary) ?
Chase speed originally set in the playback is 80 BPM, speed source local.
User setting is set to "Connected view sets temporary chase speed".
I launch the chase and progressively accelerate it to 300 BPM.
I never pressed 'Save temporary speed' but, when killing the chase and relaunching it, it starts with whatever speed I left in the connected view (300 BPM).
What I need is the chase speed to go back to 80 BPM when the pb is killed/fader lowered.
What am I missing ?

(Titan V9.1)

As far as I am aware the design is whether it is preserved or not when saved/loaded.

As far as I am aware the design is whether it is preserved or not when saved/loaded.

Hi,

It may be the langage barrier but I really don't understand your reply, sorry
My problem is precisely that any modification in the chase speed is preserved no matter what I do. I don't have (or don't understand how to) access to the 'or not' option

Maybe I get it totally wrong : what is the 'Connected View sets Chase Speed/sets Temporary Chase Speed' user setting supposed to do ?
Only difference I see is the presence or absence of a 'Save Temp Speed' button in the Edit Times menu - and as I understand it, this button is totally useless since, when you modify the speed in the connected view, the new speed is saved anyway, regardless of you pressing said button. Modified speed in the Edit Times menu is also saved, as expected, but you can save it wheter or not you use the Save Temp Speed button so, again, I don't see the point to it...

It is working as designed:

- New show
- Record chase with some empty steps
- Fire and adjust speed to 120 BPM
- Toggle user setting to [Connected View Sets Temporary Speed]
- Adjust speed to 200BPM
- Save show
- Load show

= chase is back to 120 BPM. In other words, if connected view sets chase speed then all the chases will save at their current value but if connected view sets temporary speed then they will all save at the speeds they were at before the user setting was toggled.

- Adjust speed to 200BPM again
- [Edit Times]/[Save Temporary Speed]
- Adjust speed to 300BPM
- Save show
- Load show

= chase is now at 200BPM. So the [Save Temporary Speed] set a new value to save at for that particular playback with subsequent adjustments ignored.

I admit it's a bit confusing and I did initially question it in the beginning but has been like that since v1. However, one thing I have noticed is that in the HUD any temporary speeds are displayed in pink. This is quite a useful visual indicator to show you have changed speeds that aren't going to save and also when you have returned to the original speed (or have reset using [Save Temporary Speed]). The touch workspaces don't show this at the moment but I think it might be a good idea if they did somehow.

I see. So, the temp speed is 'showise-temporary' and you need to reload the whole show to reset it.
Thanks, that really clarifies things for me.

The feature does make sense, although as I said I expected a reset whenever the chase is killed/reloaded.
I guess my best option is to make a 'reset chase speed' macro to quickly manually achieve that.
(I get that making good use of a rate master is a better and more practical solution, but my case here is quite specific).

Thanks again.