I’m trying to understand why Resolume is not receiving OSC messages from GrabberSender, but it is for the Resolume Dispatcher. (Please see image below)
I see Grabber has a text input for the “source”, and if you put something in there, it will be part of the send message. So I leave it blank, making the osc message the same as what’s in Resolume Dispatcher. So I have no idea why Resolume will not receive OSC messages from Grabber.
Also, I did take a look at the Max patch, for both, and noticed that the p.sender is a bit different. I’m not sure if that has something to do with it. (See images below)
For the GrabberSender I needed to set the TargetIP to the local/internal IP 127.0.0.1, and whatever my Resolume port is, 7000 in this case, and keep the Name field blank.
I never thought to try the internal IP.. I guess I expected the Target IP to be what Resolume’s default port is for incoming OSC messages, because that’s what it was for the Resolume Dispatcher device. My Bad!
Thank you you all for creating these patches. They are a complete gamechanger. I’m looking forward to buying Beam 2 for Live to control some lights.
Is Resolume Dispatcher working for you? I am using it for the first time and already on Ableton 12.2. I’ve setup Wireshark on the Ableton host and Resolume client machines to monitor UDP OSC messages and somehow I am not transmitting them. I’m able to transmit and receive when Resolume is on the same machine as Ableton. Also, I am able to reforward the messages if I have Resolume OSC output enabled on the host machine (i.e. [Host: Ableton → Resolume] → [Client: Resolume]). Prefer to run only one instance if possible. I have the IAC driver enabled.
Drilled down in to System Settings > Privacy & Security > Local Network and found Ableton had access disabled. I guess I was asked out of context and rejected access to my LAN. Works now!
