ok all you dreamers out there...
lets say you have a huge rig of stuff inside FL or XT or chainer or vsampler (all as a vst) and that rig is hosted inside another host.
What would be best, fastest, most intuitive, and elegent way to access all the parameters of the vsts hosted in your sub host?
I think major limitaitons are with the VST specs.
Ideally for me I'd like to see in the master host a menu of sub-hosted vsts with their own sub menue of vst parameters. All the parameters of the vsts sub-hosted would be vst parameters of the subhost itself; so... if you turned a knob of subhosted vst it would send that parameter change to the master host (who could ideally record it and play it back)
(confusing?)
What are your best ideas (realistic or not)?
Your best ideas to automate a vst hosted in a vst
-
- KVRAF
- 5350 posts since 8 Aug, 2003 from Berlin Germany
-
- KVRist
- 476 posts since 28 Jun, 2002 from Vancouver, Canada
It would have to be wrapped in the subhost, and everything would have to be taken care of there. It would be like the subhost didn't exist, and the main host only saw the subhosted VST.
But really the question should be ... why?
~MacQ
But really the question should be ... why?
~MacQ
-
- KVRAF
- 12235 posts since 18 Aug, 2003
You could send MIDI CC messages to the subhost, couldn't you? There are many limitations for VST, a lot of the stuff being done I don't think was the vision originally planned by Steinberg. Such is life.
-
- KVRAF
- Topic Starter
- 5350 posts since 8 Aug, 2003 from Berlin Germany
Why what? Why use a sub-host? Many reasons, mostly the sub host has functionality that your host does not, also the sub host set up can be reloaded in many projects.MacQ wrote:It would have to be wrapped in the subhost, and everything would have to be taken care of there. It would be like the subhost didn't exist, and the main host only saw the subhosted VST.
But really the question should be ... why?
~MacQ
-
- KVRAF
- Topic Starter
- 5350 posts since 8 Aug, 2003 from Berlin Germany
This is currently how it is done. Not very user fiendly or quick.shamann wrote:You could send MIDI CC messages to the subhost, couldn't you? There are many limitations for VST, a lot of the stuff being done I don't think was the vision originally planned by Steinberg. Such is life.
You create a level of abstraction when changing a vst parameter into a midi CC epecially when you can only record the parameter via midi and not via vst parametr automation. Not to mention you lose the name of what you are contolling. (How specific is the title CC 72 vs. OCS 2 pitch?)
Having a vst parameter also allows a host (only good host are doing this though) to display actaul VST parameter values in envelopes and displays (instead of a generic 0-128 or what ever). e.g. if you use a vst parameter to adjust the filter type you can see on an automation envelope in the host the values FilterType = LP, HP, BP, etc. instead of CC 4 = 1-128.
Why are vst parameters are so much better than a mapped CC: It is the most direct representation of a vst's state and allows the user recording via GUI movements.
-
- KVRist
- 288 posts since 3 Mar, 2004 from Denmark
Shoirtcircuit, the sampler, has a smart approach to automation which may be of some use.
It simply has 32 automation slots which can be automated from the host, and assigned to any parameter within shortcircuits mod matrix.
Thsi would work for a chainer type vst too. Just have a number of automation channels which can then be assigned, inside the chainer, to any parameter of any sub-hosted VST.
It's not the most elegant way, but i think it is the best the current vst spec will allow.
Pete.
It simply has 32 automation slots which can be automated from the host, and assigned to any parameter within shortcircuits mod matrix.
Thsi would work for a chainer type vst too. Just have a number of automation channels which can then be assigned, inside the chainer, to any parameter of any sub-hosted VST.
It's not the most elegant way, but i think it is the best the current vst spec will allow.
Pete.