I was wondering whether it's a good idea to stop outputting OSC e.g. for FX that are bypassed or set to 0% opacity. I'm just working on a MAX patch and get all that OSC from a couple of comp effects which are set to 0% and I don't see why this data could be handy until the effects get dialed in. To me it's just "overload". Any enlightening ideas on this are welcome
Deactivate OSC out when bypassed/0
- Tschoepler
- Posts: 467
- Joined: Fri Mar 13, 2009 04:26
Deactivate OSC out when bypassed/0
Hey,
I was wondering whether it's a good idea to stop outputting OSC e.g. for FX that are bypassed or set to 0% opacity. I'm just working on a MAX patch and get all that OSC from a couple of comp effects which are set to 0% and I don't see why this data could be handy until the effects get dialed in. To me it's just "overload". Any enlightening ideas on this are welcome
I was wondering whether it's a good idea to stop outputting OSC e.g. for FX that are bypassed or set to 0% opacity. I'm just working on a MAX patch and get all that OSC from a couple of comp effects which are set to 0% and I don't see why this data could be handy until the effects get dialed in. To me it's just "overload". Any enlightening ideas on this are welcome
████▀ ▄█ tschoepler.net █████ zweifarbton.net █▄ ▀████
Re: Deactivate OSC out when bypassed/0
It's handy for people that use OSC to remotely monitor what Resolume is doing, or is going to do when they fade in the effect.
- Tschoepler
- Posts: 467
- Joined: Fri Mar 13, 2009 04:26
Re: Deactivate OSC out when bypassed/0
Makes sense, thanks. There was something wrong with MAX's opensoundcontrol object in the first place which led to serious CPU overload.
████▀ ▄█ tschoepler.net █████ zweifarbton.net █▄ ▀████