Using OSC to change BPM - bug

Post your questions here and we'll all try to help.
Post Reply
User avatar
gpvillamil
Posts: 550
Joined: Mon Apr 04, 2005 03:33
Location: San Francisco, California

Using OSC to change BPM - bug

Post by gpvillamil »

So I'm trying out the possibility of using one instance of Resolume 4 to control one on another computer via OSC, and it seems to be working fine, except for this:

When I change the BPM on the "master" computer, the BPM on the "slave" immediately goes to 500.

The "master" is a Macbook Pro on OS X, the "slave" is running Windows 7. The same behavior also happens when going the other way, from Win 7 to OS X.

I haven't looked at it with an OSC debugger yet, but I think you are actually sending the BPM value, not a float between 0.0 and 1.0

User avatar
gpvillamil
Posts: 550
Joined: Mon Apr 04, 2005 03:33
Location: San Francisco, California

Re: Using OSC to change BPM - bug confirmed

Post by gpvillamil »

Yep, confirmed.

Resolume is sending this when you change the BPM:

print: /playbackcontroller/bpm 121.

but it is EXPECTING to receive a float scaled from 0.0 to 1.0

Pls fix this, kthxbye.

Joris
Posts: 5186
Joined: Fri May 22, 2009 11:38

Re: Using OSC to change BPM - bug

Post by Joris »

Thanks for the find! Ticket made!

Post Reply