OK, I have received a request for the code, and I got a bit more testing time in. It's definitely not bug free or feature complete, but hopefully it will be of use to some of us before Res5 is released and solves all our problems
NYE Boston - the Video Bleep team helped ring in the New Year by setting up an immersive video dome with 3 edge-blended projectors. Visuals courtesy of a Hackintosh running Resolume, with a second computer running audio from Ableton and sending network MIDI sequences to the visual computer. Untitled...
I've had some success in the last week working with an OSC whitelist script that a friend wrote in Processing - it screens all OSC coming from the master computer and only passes commands to the slave computer which contain the whitelist terms. I've managed to slave-control a second copy of Res this...
Funny, I just came to the forum to post an OSC bug, and this thread was already at the top of the stack... First, +1 to the limitation of "always-on" OSC outputs. It would be nice to have more control over what gets sent out. There are times when I only want to send very specific commands ...
>> [NEW] MirrorQuad - Like Mirror, only better.
>> [NEW] Layer Opacity 0 = Bypass
It's like you read my mind, and magically added the things that I wanted. The layer opacity/bypass is HUGE for my setup. Thanks for continually improving this excellent program!
