Resolume Forum

Hi,

I'm just wondering if I did not understand how beat snap is supposed to work, or if it is buggy.

What I would expect:
If I set beat snap to 4 bar, clips should ALWAYS be triggered every "real" 4 bars. Which means at 1.1, 5.1, 9.1, ... 113.1, ... 1001.1, ... 65537.1, etc. etc..

Now if I press resync (reset to 1.1) while a clip has been triggered and waits to be started at the next x.1, the yellow/blue overlay bar (which counts to the next real bar e.g. 13.1) on the thumbnail keeps counting as before, and therefore it does not trigger the clip at the correct time. e.g. 10.1 instead of 13.1 (depends when you hit resync).

Clip timelines are reset when I hit resync (which makes totally sense), but not the beat snap clock. I think the clips (which have been triggered already, and are waiting for the correct bar) should be triggered immediately at a resync, including (or by) a resync of the beat snap counter.

hope that makes sense...

I think this is more an issue of differing expectations than an actual bug.

The beat snap delays the trigger until the first beat, x bars later. So if your beat snap is set to 4 bars, and you press the trigger on 10.3, it will trigger on 14.1 (let me know if that doesn't make sense, I'm struggling a bit to put it in words here). This countdown will keep running when pressing resync. Only the time till the first beat is affected by the resync action.

Something can be said for the way you expect it to happen though. If you want, I can make a feature request?

goto10 wrote:..., I'm struggling a bit to put it in words here

for this reason, thanks for your reply and try to make things clear. (I know exactly what you mean )

Let me try to sort my thoughts...

goto10 wrote:So if your beat snap is set to 4 bars, and you press the trigger on 10.3, it will trigger on 14.1

I would expect it to trigger on 13.1. Why? Because 13.1 is a "real" one (given you set beat snap to 4 bars --> 1, 5, 9, 13,...).

I might should explain why this is important to me. In electronic music sometimes it's really hard to hear the first of eight (or four) bars - so the moment where things are meant to change, when a new part is added or taken away, an effect is turend on etc. etc. (especially when you are totally into searching for a specific clip, not actively listening to the music)
So for that reason it would make sense if Resolume could be so smart to count for me, and trigger clips, so they fit into this 8 bar schema.

goto10 wrote:Only the time till the first beat is affected by the resync action.

You mean, the beat snap feature just ensures, that the clip is triggered at a x.1 (e.g. 10.1, 11.1, 12.1 etc.) but therefore not 'synced' to the already triggered ones, right? - I think it should be different. Or at least ask for a checkbox in the preferences for some kind of "modulo beat snap".

Goto10 wrote:Something can be said for the way you expect it to happen though. If you want, I can make a feature request?

Yes please, a feature request would make me happy

Examples:
Assumption: all clips are set to "beat snap composition", and comp is set to 8 bars

According to your explanation Joris "So if your beat snap is set to 4 bars, and you press the trigger on 10.3, it will trigger on 14.1", I would think that if I trigger 3 clips sequentially (set to 8 bar beat snap), that they will start delayed, instead of at the same time (which is the current behavior and should not change!)

What I understood reading Joris' explanation:
counter is 2.3 and I tigger clipA - according to you Joris, it will start at 10.1
counter is 4.2 and I trigger clipB - it will start at 12.1
counter is 6.2 and I trigger clipC - it will start at 14.1

what Resolume actually does:
counter is 2.3 and I trigger clipA - Resolume starts it at 10.1
counter is 4.2 and I trigger clipB - starts also at 10.1
counter is 6.2 and I trigger clipC - starts also at 10.1

what I would like Resolume to do:
counter is 2.3 and I trigger clipA - Resolume should starts it at 9.1
counter is 4.2 and I trigger clipB - at 9.1
counter is 6.2 and I trigger clipC - at 9.1

Hope that makes sense.

And finally another feature?
If I hit resync at the very end of the countdown (a few beats before the cip is supposed to be triggered), Resolume starts the new clip NOT at x.1, but instead at e.g. x.3 or x.2. - This only happens if you resync within the last bar of the countdown. I'm struggling a bit to put it in words here too...

sorry for this looooong post!

We've made a ticket to change the behaviour to snap to modulo 4, instead of + 4. To maintain backwards compatibility, this is probably going to happen on Res 5.

Unless this post if flooded with a deluge of +1s of course

Joris, thanks for the feature request. Let's see if the AVJs are flooding this thread. (chances are not too high, I guess)