By binding a midi clock input to 'tap' in a Speed Dial you can get a really accurate BPM count, but in doing so you lose the ability to accurately set a duration factor above 1 due to the fact that "tapping advances the function to next step/position when speed dial is set to adjust duration."
It would be nice to have a little check box that allows us to disable advancing the chaser so we can use midi clock for timing and a higher duration factor.
As a side note: It would also be nice to be able to set the duration factor higher than x16 in the Speed Dial function properties (I know it can be done using the multiplier and divisor buttons on the dial its self). Perhaps 16 and 32 bars (x64 and x128).
Toggle to disable tap button advancing to next step in in a cue list/chaser
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
I'm still not convinced that hitting the tap button (thru midi - changing the duration) will have the chaser to advance.
During our last conversation - I pointed out that in your project you used the midi signal as a tap _and_ AS A GO (!)
Then we started the discussion about fractionals / dividers / ...
So? A new demo project so we can investigate?
During our last conversation - I pointed out that in your project you used the midi signal as a tap _and_ AS A GO (!)
Then we started the discussion about fractionals / dividers / ...
So? A new demo project so we can investigate?
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
DarkMain
- Posts: 10
- Joined: Sun Feb 03, 2019 12:06 pm
- Real Name:
No, you made the assumption that's what I had done. I never uploaded a project file for you to look at.
What you DID do was upload a project file for me lo look at that you had configured which you thought would work, however YOUR project file did the same thing as mine which means either a) You also configured it incorrectly or b) the software is doing what the documentation says it should do.
I even uploaded a video of me using your project demonstrating the problem.
Like I keep pointing out. The documentation states "For cuelists/chasers and RGB Matrices, the tap button advances the function to next step/position when speed dial is set to adjust duration."
Emphasis on "the tap button advances the function to next step"
We were talking about duration factor because it directly relates to what I was trying to achieve, something you seem to be missing.Then we started the discussion about fractionals / dividers / ...
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
Then send in your project please?
I cannot achieve a cue list to advance with a signal bound to the tap button ... sorry
I cannot achieve a cue list to advance with a signal bound to the tap button ... sorry
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
DarkMain
- Posts: 10
- Joined: Sun Feb 03, 2019 12:06 pm
- Real Name:
Any project I send you will be set up the same was as you setup yours except it will using a midi signal instead of a loop back to trigger the 'Tap'.
Is there any chance you can make a screen cap video (Like I did here - https://youtu.be/vmITbEDykmI) of it functioning properly on your setup (using the project file you supplied here - viewtopic.php?f=29&t=13072&p=55529#p55528) so I can see if its perhaps something I am doing wrong?
Is there any chance you can make a screen cap video (Like I did here - https://youtu.be/vmITbEDykmI) of it functioning properly on your setup (using the project file you supplied here - viewtopic.php?f=29&t=13072&p=55529#p55528) so I can see if its perhaps something I am doing wrong?
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
https://youtu.be/SqCwr_X-UMo
as long as the tap duration is longer than the running duration - the cue won't advance. (in the video you can see this happening 2-3 times ...)
(on the contrary: if shorter, it makes perfect sense to advance the cue since the new duration is shorter than the previous duration ...)
as long as the tap duration is longer than the running duration - the cue won't advance. (in the video you can see this happening 2-3 times ...)
(on the contrary: if shorter, it makes perfect sense to advance the cue since the new duration is shorter than the previous duration ...)
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
I tought we catched a bug ... I went on with changing the multiplier (in the Speed control)
result stays the same
https://youtu.be/W0zsyVjJq-w
as long as you don't tap earlier (changing duration time) than already passed time frame; the cue will stay in place.
result stays the same
https://youtu.be/W0zsyVjJq-w
as long as you don't tap earlier (changing duration time) than already passed time frame; the cue will stay in place.
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
DarkMain
- Posts: 10
- Joined: Sun Feb 03, 2019 12:06 pm
- Real Name:
Now take the setup from your second video (duration factor of 4), play a song and 'tap' on every beat.
The midi clock works by sending a signal every beat to keep other devices in sync, so to simulate that on your setup you need to click on every beat as well.
What happens?
Does the cue change every 4th click or does it change sooner? In my setup it changes sooner (roughly every second click).
This is why I would like to see a toggle or 'disabling advancing to the next step' when the tap button is pressed.
I work mostly with EDM music in a night club environment and try to set the lights to be as easy to use with as much automation as possible. Using the midi out from the back of the mixer is a nice easy way to keep the lights in sync.
I don't know how difficult the change would but even something like the following would keep a decent sync and perform better than the current implementation:
If chaser is playing and the 'global' duration becomes less than the 'running' duration, then continue playing the current step until completion and update to the new 'global' duration when moving to the next step.
(If that makes sense).
Edit: Actually, thinking about it, I don't know if that would work either as its likely to introduce 'drift' into the timing.
Maybe if there was a way to say "If duration factor = 4 then don't advance until 5th input is received"?
The midi clock works by sending a signal every beat to keep other devices in sync, so to simulate that on your setup you need to click on every beat as well.
What happens?
Does the cue change every 4th click or does it change sooner? In my setup it changes sooner (roughly every second click).
This is why I would like to see a toggle or 'disabling advancing to the next step' when the tap button is pressed.
I work mostly with EDM music in a night club environment and try to set the lights to be as easy to use with as much automation as possible. Using the midi out from the back of the mixer is a nice easy way to keep the lights in sync.
I don't know how difficult the change would but even something like the following would keep a decent sync and perform better than the current implementation:
If chaser is playing and the 'global' duration becomes less than the 'running' duration, then continue playing the current step until completion and update to the new 'global' duration when moving to the next step.
(If that makes sense).
Edit: Actually, thinking about it, I don't know if that would work either as its likely to introduce 'drift' into the timing.
Maybe if there was a way to say "If duration factor = 4 then don't advance until 5th input is received"?
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
Tapping to the beat with a multiplier of 4 _will_ advance the cue list by every tap - simply because the duration will always be longer than the current running time (tap-frequency multiplied by 4)
So basically you have a feature request - tap-button divider (by 4 16 32)
Well ... you could simulate this by: (work around)
* create a cue list driven by the tap button itself. (every tap _will_ advance the virtual cue list)
* the 3 first steps are dummys
* the fourth (16th 32th) step will send a 255 value to the loopback channel (make sure step 1 resets this condition)
now you divide the tap frequency by 4...
This should be the solution for you
So basically you have a feature request - tap-button divider (by 4 16 32)
Well ... you could simulate this by: (work around)
* create a cue list driven by the tap button itself. (every tap _will_ advance the virtual cue list)
* the 3 first steps are dummys
* the fourth (16th 32th) step will send a 255 value to the loopback channel (make sure step 1 resets this condition)
now you divide the tap frequency by 4...
This should be the solution for you
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
PearGroup
- Posts: 2
- Joined: Mon Aug 05, 2019 7:52 am
- Real Name: Pierre
Hi Everyone
Interesting thread, I have a similar problem but maybe with a simpler solution.
How about a "Manual Step" button
It does the following.
Pauses the duration (or override like when having two duration widgets)
But when pushing Trigger it manually advances to the next step in a Chase or Sequence.
The trigger button can then receive external input,
which will give absolute custom and dynamic freedom for the timing in steps.
This is all I need now and then I'm happy
Interesting thread, I have a similar problem but maybe with a simpler solution.
How about a "Manual Step" button
It does the following.
Pauses the duration (or override like when having two duration widgets)
But when pushing Trigger it manually advances to the next step in a Chase or Sequence.
The trigger button can then receive external input,
which will give absolute custom and dynamic freedom for the timing in steps.
This is all I need now and then I'm happy