Tapsync
#1
Hey Guys,

just Created an Chase:

Step 1: Dimmer 1 (100%); Dimmer 2 (0%)
Step 2: Dimmer 1 (0%); Dimmer 2 (100%)

Now I Changed the Fader to be an "Speed" Fader and the lower Button to be an "Tapsync"

- If I Move the Fader Up Chase is waiting at Step 1
- Now I start the Chase with "GO"
- Tap the Speed to 50 BPM by hitting the "Tapsync" Button 2 Times
- Now I want to Speed Up the Chase to about 60 BPM by hitting the Tapsync 2 more Times
- Now my Problem:
   I hit the Tapsync the first Time to Speed Up the Chase and the Tapsync is still listen, so
   the Speed Changes now to 11BPM and waiting the whole Time (11BPM) before changing
   to 60 BPM....

I'm not sure If this is how it should work, cause there is an fu**** long Break before getting
the right Speed. How long is the Tapsync waiting for Speed Hits? 2 times, 3 times?

That's is pretty annoying....
Hope you unterstand what I'm talking about...
Reply

#2
The Tapsync at the moment has a timeout of 60 seconds - so thats 1 BPM. I understand this can be annoying, its just the question of how to make it right for most people Smile

Denis
Reply

#3
(21-02-2019, 12:41 PM)denishessberger Wrote: The Tapsync at the moment has a timeout of 60 seconds - so thats 1 BPM. I understand this can be annoying, its just the question of how to make it right for most people Smile

Denis
Probably it would be a solution if the tapsync would come into affect as soon as the speed has'nt been changed for 4 
beats. Following example:
The tap is running at 60 BPM.
The user taps a new speed into the console with approx. 75 BPM. While he is tapping, the console still uses the tap of 60 BPM. During the next 4 beats the console checks that the new speed of 75 BPM has not been changed any more and takes this new speed into affect.
This would avoid the break.
Another possibility would be to wait 4 Manual taps before taking the new speed into account at the next beat.

Definitely, the first tap should not do anything. ;-)
Reply



Forum Jump:


Users browsing this thread:
1 Guest(s)