Automation from plugins
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Can MuLab route and record automation from plugins? For example, OSCar can translate between DAW automation and network OSC messaging.
From what I can see, it's declaring the parameters I've set up correctly to MuLab -- for MuLab to drive the automation outbound.
But I can't see how to set up the inbound side, where the plugin exposes automation to the host. It's only declaring Audio In, Event In and Audio Out ports. It's a VST3.
The aim is something like having a tablet with controls to adjust mix levels, toggle tracks enabled state, etc.
From what I can see, it's declaring the parameters I've set up correctly to MuLab -- for MuLab to drive the automation outbound.
But I can't see how to set up the inbound side, where the plugin exposes automation to the host. It's only declaring Audio In, Event In and Audio Out ports. It's a VST3.
The aim is something like having a tablet with controls to adjust mix levels, toggle tracks enabled state, etc.
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Yes of course MuLab can record automation from plugins:
Simply press record and turn the knobs in the plugin.
Simply press record and turn the knobs in the plugin.
- KVRAF
- Topic Starter
- 7412 posts since 8 Feb, 2003 from London, UK
I tend to work completely modularly... so I'm really saying "what ins/outs do I connect from this VST3 Audio Effect so that I can use live automation and route it around inside MuLab". I'm not that interested in recording and playing back - far more in live use for control.
- KVRAF
- Topic Starter
- 7412 posts since 8 Feb, 2003 from London, UK
OK, so by adding automation sub-tracks, I expose the automation to composer. I can then use "Target" on the automation track to target something else. Is there no other way?
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
Ok i now get a better idea of what you wanna do:
Convert parameter A from module X to parameter B of module Y, right?
First thing i think of is the Parameter Event Generator, but not yet sure of it can do what you want.
Maybe the PEG needs an extension for that and/or an extra module like "Parameter To Controller" / "Parameter To Modulation" converters.
Convert parameter A from module X to parameter B of module Y, right?
First thing i think of is the Parameter Event Generator, but not yet sure of it can do what you want.
Maybe the PEG needs an extension for that and/or an extra module like "Parameter To Controller" / "Parameter To Modulation" converters.
- KVRAF
- Topic Starter
- 7412 posts since 8 Feb, 2003 from London, UK
OSCar expresses it as "automation": the same as "parameters", yes.
For example, mda Bright E. Piano has a "Vibrato" parameter. I'd like "/slider/1 0.3" to get converted to a parameter automation event stream that I can pass from OSCar to mda Bright E. Piano.
For recording, having this pass through the composer makes sense - or just some drop-in "record me the time-tracked sequence of live parameter movements between these two modules" into an automation clip module that can be plugged in for recording, saving and playback.
But for live use, I just want to wire the two directly together in the modular area ... Currently the VST doesn't have an event output node at all, so I don't know how it's even meant to expose these events for hosts. They do get declared to the host -- I could control OSCar from a parameter generator -- but I can't take those parameter it's generating anywhere else. So yes, it's essentially acting like a parameter event generator with multiple, named parameters.
For example, mda Bright E. Piano has a "Vibrato" parameter. I'd like "/slider/1 0.3" to get converted to a parameter automation event stream that I can pass from OSCar to mda Bright E. Piano.
For recording, having this pass through the composer makes sense - or just some drop-in "record me the time-tracked sequence of live parameter movements between these two modules" into an automation clip module that can be plugged in for recording, saving and playback.
But for live use, I just want to wire the two directly together in the modular area ... Currently the VST doesn't have an event output node at all, so I don't know how it's even meant to expose these events for hosts. They do get declared to the host -- I could control OSCar from a parameter generator -- but I can't take those parameter it's generating anywhere else. So yes, it's essentially acting like a parameter event generator with multiple, named parameters.
- KVRAF
- Topic Starter
- 7412 posts since 8 Feb, 2003 from London, UK
(And having direct automation of Bypass for any target would be good.)
