Resolume Forum

Hi All,

Thanks for looking into it. Glad you've identified the problem it's not just me..!

No problem waiting for the patch.

Many thanks,


Ben

Any solution regarding this issue? I'm having the same problems, very annoying.

Are you running the latest release (5.1.3) ? I'm not exactly sure anymore when this was fixed, it should be working on the current release.

Joris wrote:Are you running the latest release (5.1.3) ? I'm not exactly sure anymore when this was fixed, it should be working on the current release.

Hello!

Yes I have the latest version. I managed to partly get this thing working with two separate cues. Cue 1 sendin dmx 0 to resolume's tap function and cue 2 sending dmx 1 to the same function. I recorded them to another playback fader, so now to get the tap i need to use "next, stop" from chamsys console. In addition, using tap this way somehow forces me to "doubble tap" to get the desired response from Resolume.

The most ideal situation would be that the resolume's tap function would work from the same playback's "s" button in which I have the clip select and intensity; this ofc being playback fader too.

Hope this make's sense

Jouka

you could place the DMX channel you mapped to TAP,
on a separate fader on your console, then either use the fader's flash button or manually move the fader up and down on each beat.

Cue 1 sendin dmx 0 to resolume's tap function and cue 2 sending dmx 1 to the same function

that is one tap. And I think actually it should be 100% first, then 0% second for one tap. - (Can't test this right now Joris might know better.)
As stated before, it requires at least two taps for tap tempo to work:
the first is to start measuring time, the second is the first interval,
the additional taps make the calculated tempo more precise.