Tap Sync vs. Fade time / Scene time
Posted: November 13th, 2013, 1:28 pm
When programming a sequence, the option to change fade times and scene times gives you very much flexibility.
However, when running a sequence, if the tempo is set by pressing Tap Sync, all steps are re-set to the tap speed. (e.g. 0.6s)
Although this seems logic, I'd like it more if the step speed would be calculated based on the scene time.
Say the scene time is 2000ms (twice the default) and the tap sync speed is 0.6s, the effective step speed would become 1.2s (twice the tap speed).
Same goes for the fade time. 500ms would translate to 0.3s when running.
I don't believe this is a bug, I am convinced there is a good explanation for the current behaviour. I just don't know/understand it That's why I post it here rather than in the bug reporting area
What is the reason for the tap sync button to work this way?
Am I the only one that would like this behaviour above the default method?
However, when running a sequence, if the tempo is set by pressing Tap Sync, all steps are re-set to the tap speed. (e.g. 0.6s)
Although this seems logic, I'd like it more if the step speed would be calculated based on the scene time.
Say the scene time is 2000ms (twice the default) and the tap sync speed is 0.6s, the effective step speed would become 1.2s (twice the tap speed).
Same goes for the fade time. 500ms would translate to 0.3s when running.
I don't believe this is a bug, I am convinced there is a good explanation for the current behaviour. I just don't know/understand it That's why I post it here rather than in the bug reporting area
What is the reason for the tap sync button to work this way?
Am I the only one that would like this behaviour above the default method?