VST automation forwarding through VSTi host.
-
- KVRian
- 584 posts since 10 Apr, 2004 from Malmö / Sweden
Hi everyone,
I was wondering if anybody knows of any VSTi host (a host loadable as a VSTi in another host), like EnergyXT or Chainer (which I haven't tried yet) or something, that can do the following:
* Load VSTs
* Be loaded in another VST host as a VST itself (act as a wrapper for VST:s while being loaded in another VST host)
* Receive multiple midi and audio channels from the VST host it is loaded within, send this data to VST plugins it loads, receive midi and audio data from the loaded VST plugins and then output audio and midi data back to the VST host it is loaded within.
... and FINALLY ...
* Let the VST host, it is loaded within, automate the VST plugins it wraps. Thus, the VSTi host I'm looking for is completely transparent to the VST host it is loaded within. For example, I could load the host that I'm looking for as an insert in Cubase SX2, which in turn could load some VST plugins in SX2's place. The point of this is that this would solve the problem of SX2 not being able to move inserts around. However, I would also like to be able to draw automation in SX2 to the plugins that I've loaded within the host plugin I've loaded in Cubase.
Does this make any sense? If EnergyXT could forward VST automation data, I would use that host for the job, but unfortunately this feature has not been implemented yet.
Thanks!
//Tomas
I was wondering if anybody knows of any VSTi host (a host loadable as a VSTi in another host), like EnergyXT or Chainer (which I haven't tried yet) or something, that can do the following:
* Load VSTs
* Be loaded in another VST host as a VST itself (act as a wrapper for VST:s while being loaded in another VST host)
* Receive multiple midi and audio channels from the VST host it is loaded within, send this data to VST plugins it loads, receive midi and audio data from the loaded VST plugins and then output audio and midi data back to the VST host it is loaded within.
... and FINALLY ...
* Let the VST host, it is loaded within, automate the VST plugins it wraps. Thus, the VSTi host I'm looking for is completely transparent to the VST host it is loaded within. For example, I could load the host that I'm looking for as an insert in Cubase SX2, which in turn could load some VST plugins in SX2's place. The point of this is that this would solve the problem of SX2 not being able to move inserts around. However, I would also like to be able to draw automation in SX2 to the plugins that I've loaded within the host plugin I've loaded in Cubase.
Does this make any sense? If EnergyXT could forward VST automation data, I would use that host for the job, but unfortunately this feature has not been implemented yet.
Thanks!
//Tomas
-
- KVRian
- Topic Starter
- 584 posts since 10 Apr, 2004 from Malmö / Sweden
Sweet! I'll have a look at it
.
Thanks a lot!
//Tomas
Thanks a lot!
//Tomas
-
- KVRian
- Topic Starter
- 584 posts since 10 Apr, 2004 from Malmö / Sweden
Oh, wait! Maybe I was unclear about this: It must no involve mapping between VST automation and midi cc:s. VST automation has 32-bit resolution and midi has only 7-bits. It's not even nearly enough for what I have in mind. Does Console do automation forwarding through mapping between VST automation and midi cc:s or is it true VST automation?
//Tomas
//Tomas
-
- KVRist
- 190 posts since 9 Mar, 2004
hmm, not entirely sure. Each vst you load up has its own automation settings window which let you assign midi cc and/or vst automation. I could try and check for you if you know of a test.
-
- KVRian
- Topic Starter
- 584 posts since 10 Apr, 2004 from Malmö / Sweden
Well, just load any VST plugin, which has a controllable VST automation parameter, in Console and draw an automation envelope in Cubase SX2 and see if the the plugin in Console can be controlled by the automation envelope in Cubase. If the automation data were converted through midi cc:s you would have to do some explicit mapping between Console's VST automation parameters and some midi cc, right? You can't just accidentally happen to go through midi cc:s without you knowing it, right
?
<edit>
If Console can forward VST automation to some plugin it wraps, there needs to be some VST automation input in Console that let's you listen to automation data, incoming from Cubase, and forward it to the desired plugin (by drawing a wire to the plugin's VST automation input)?
Does Console has some native envelope tool for generating VST automation events or something? I mean, either it needs to be able to forward VST automation data from the outside to the right plugin. Or else it needs to generate this data itself through automation envelopes (or other kinds of tools) by itself. Why else would it show VST automation inputs on the plugins?
</edit>
//Tomas
<edit>
If Console can forward VST automation to some plugin it wraps, there needs to be some VST automation input in Console that let's you listen to automation data, incoming from Cubase, and forward it to the desired plugin (by drawing a wire to the plugin's VST automation input)?
Does Console has some native envelope tool for generating VST automation events or something? I mean, either it needs to be able to forward VST automation data from the outside to the right plugin. Or else it needs to generate this data itself through automation envelopes (or other kinds of tools) by itself. Why else would it show VST automation inputs on the plugins?
</edit>
//Tomas
-
- KVRian
- Topic Starter
- 584 posts since 10 Apr, 2004 from Malmö / Sweden
Right then
!
Thanks once again
!
//Tomas
Thanks once again
//Tomas
-
- KVRian
- Topic Starter
- 584 posts since 10 Apr, 2004 from Malmö / Sweden
I'm running the 1.2.0 beta in Cubase SX2 right now. I have loaded JXSynth 1.2 in Console and I want to do VST automation on JXSynth from the automation envelopes in Cubase.
1. Console's VST parameters only read "Unknown", so how am I supposed to see JXSynth's parameters from Cubase?
2. How do I route from the Midi input component to JXSynth in order to forward the VST automation data? Or how does it work? I've found the Learn function in JXSynth (or rather, the Console part of the JXSynth plugin window) and it seems to work for CC and "Param". Is "Param" the VST automation parameter? Can it learn from the VST automation input sent from Cubase and then map the incoming VST automation data input to the selected parameter in JXSynth?
Any help would be appreciated
.
If I could get Console to work, this would be an amazing program
.
<edit>
Heh, found the answer on the Art Teknika site. Never mind
. This is so great
!
</edit>
//Tomas
1. Console's VST parameters only read "Unknown", so how am I supposed to see JXSynth's parameters from Cubase?
2. How do I route from the Midi input component to JXSynth in order to forward the VST automation data? Or how does it work? I've found the Learn function in JXSynth (or rather, the Console part of the JXSynth plugin window) and it seems to work for CC and "Param". Is "Param" the VST automation parameter? Can it learn from the VST automation input sent from Cubase and then map the incoming VST automation data input to the selected parameter in JXSynth?
Any help would be appreciated
If I could get Console to work, this would be an amazing program
<edit>
Heh, found the answer on the Art Teknika site. Never mind
</edit>
//Tomas