[request] Resolume slave sync via OSC

[gpvillamil]

I was just messing around setting up an installation, and pondering the possibilities of having Resolume send out OSC, and came up with this idea:

If Resolume can *send* mapped OSC commands every time a control is triggered, and this is exactly the same command that it uses when *receiving*, then it would be possible to have multiple instances of Resolume running on different machines, all of them in sync, and controlled by one system.

You could for example have a Resolume "slave" running on a machine with a big screen in full screen mode, controlled by another instance of Resolume running elsewhere, with an identical composition.

Or you could have several instances of Resolume, each going to a separate projector, each with a composition structured the same way, but with different clips. All controlled by one instance of Resolume. In fact, depending on how you set it up, any instance could act as a controller...

This could be potentially amazing, if combined with a "collect and gather" feature. You could create a composition, do a "collect and gather", deploy copies of it to a bunch of Mac Minis, and open them all in Resolume "slaves" controlled by OSC.

I stumbled across this as I was making my sequencer patch more elaborate, and was using it to control multiple instances of Resolume. Instead of trying to duplicate the entire Resolume UI in Max for remote control, why not use Resolume itself?

[GeeEs]

For what i understand from your idea, you want to achieve some kind of MIDI thru? but then with OSC?

OSC out would be a great feature indeed, but then (imho) it has to be completely mappable/flexible.
Not only the same as the input, because then it's a lot easier to just run a "simple" laptop/computer with some kind of dedicated OSC server and connect that to the Resolume slaves? Effect would be the same, but the OSC server a lot more flexible. (I guess).

Anyway, curious about it.. Also very nice to see your little helping programs (sequencer/co-pilot/midi-osc thing...!!) taking over my Resolume !!

[edwin]

Can't you do this with a UDP broadcast, just send out the OSC to for instance 192.168.1.255.

[gpvillamil]

Can't you do this with a UDP broadcast, just send out the OSC to for instance 192.168.1.255.

Well, yes, but using an instance of Resolume as the controller. This would be easily possible if Resolume would *output* the corresponding OSC command when an interface element is moved.

So set up a copy of Resolume that outputs (master) to the multicast address on port 8000, and then set up other copies that listen (slave) on port 8000. If I trigger a clip in the master, it sends out the /layer/clip/connect message, and all the slaves get it and respond.

Like I said, I found that I was gradually duplicating the entire Res interface in Max, and it would be much easier to actually use Resolume itself as a master!

[mfo]

Why didn't I find this post earlier..?
I agree 100% with gpvillamil !!!

In fact I was working on a project that should use 12 beamers in a panoramic surround projection - via 4 pcs, each with a TH2go connected. Therefor I came to exactly the same conclusion - have one Resolume instance as master and 4 instances on the 4 computers as slaves - that's why I so frequently ask for OSC out!

Why not use controllers and spread the midi/osc messages to the 4 pcs?
Because of the clip triggering! I would love to see which clip I start. That cannot be done using a Keyboard or Pad-base controller or TouchOSC or whatever ...