Resolume Forum

Upgraded to latest Arena, setup that computer to control another Resolume instance on another computer with OSC messages - everything is working ok, but BPM does not go through. It does if I do tap tempo - that OSC command gets sent. Or if I do "half the bpm rate" - that OSC command also goes through. But the one I really need desperately to work - the only one I am really trying to sync here - the BPM counter change does not. Any idea what's happening? Is this a bug? I have done this before successfully, so it's a bit of a weird new development for me....

Halp!

zebbler wrote:Upgraded to latest Arena, setup that computer to control another Resolume instance on another computer with OSC messages - everything is working ok, but BPM does not go through. It does if I do tap tempo - that OSC command gets sent. Or if I do "half the bpm rate" - that OSC command also goes through. But the one I really need desperately to work - the only one I am really trying to sync here - the BPM counter change does not. Any idea what's happening? Is this a bug? I have done this before successfully, so it's a bit of a weird new development for me....

Halp!

you are lucky to have that working out of the box.
soon you will encounter more weird things happening with that setup, like clips playing jittery, shrinking to half size if video cards max texture size differs... going all the way to having the client resolume all turn black, until it is restarted.

Only way I could make two resolume instances work in sync like master-slave is a a bridge between the two machines with some message filters.
I have made my own, but you can try it, download link is in my signature.

edit: also you should check osc mapping for the bpm counter on master and slave to be the same

Thanks for the recommend.
Yeah - OSC mapping is a nightmare. We are currently using a Processing "white-filter" pass through - to not allow any OSC messages that we don't want. Was just confused about why BPM counter has stopped working in OSC control... Good call on checking that OSC label is same on both buttons, I'll check that now.

Alas, the message seems the same on both Resolumes:
/playbackcontroller/bpm

That's the thing that no longer gets forwarded from one Resolume to another via OSC.

Has anyone else experienced this somehow?
Is it the new Resolume? Should I downgrade? [I really don't want to - like some of the new features]

ok, have a look at the processing sketch to see wether or not it gets the bpm osc message.
if resolume is not sending it, it will be another bug in the long list of osc related .
edit: just checked, my 4.1.11 sends the bpm correctly

Well, at the moment, we are just testing two Resolumes linked directly into each other, to eliminate confusion.
And they don't work as far as changing the BPM data goes.
Other things work though, so it doesn't seem to be our connection. And before I go tinkering with my Processing code - I would like to at least past this hurdle.....
My Resolume is also same as yours 4.1.11
So weird

Maybe we should upgrade both Resolumes?
We are sending out of a brand new version into an older version...

is bundles off in sending resolume?
oscP5 has sometimes difficulties handing bundles.

Ravensc - amazing! That was the issue indeed. So weird - most of other OSC commands were getting sent through, but this one (playbackcontroller/bpm) was consistently getting dropped out. But unchecking "bundles" fixed this for me. Thank you!

ravensc wrote:is bundles off in sending resolume?
oscP5 has sometimes difficulties handing bundles.