KVR Audio is the Internet's number one news and information resource for open standard audio plug-ins. We report new releases, product announcements and product updates (major and minor) for all VST Plug-ins, DirectX Plug-ins and Audio Units Plug-ins (and RTAS too). We manage a fully searchable audio plug-in database (updated daily), and offer many free member services including user reviews, product update notifications and a very active discussion forum. We also host official support forums for many plug-in developers plus the official Receptor support forum.
Plug-in Database: Virtual
Instruments, Effects & Hosts
Plug-in
Ranks
Banks & Patches
Download & Upload
Plug-in Ratings
by KVR Members
Wiki: Tutorials,
Audio Lexicon, ...
Listen to Music
by KVR Members
Search
KVR

Google Powered Search:

in new window

KVR Powered Plug-in Search:

AuthorTopic: Automation
elfan
Posted: 10th April 2004 07:25
Hi,

First of all I wish to thank Jorgen (and others?) for EnergyXT. I have never found anything quite like it, and I absolutely LOVE it. It is thrilling to see a modular VST-host which is also a VST-plugin. That way I can combine the things I like from EnergyXT with the things I like from Cubase SX, which I also use.

Obviously, I'm new to eXT so please forgive me if I don't know everything that I should know of. Still I have a question regarding automation of VST-parameters. Recently I read a post, on this forum, that said that Jorgen had confirmed that real parameter automation (not CC-mapping, which won't do since it is limited to 128 [or is it 256? 8 bits anyway] points of resolution) would be implemented in an upcoming version of eXT. Has this been done in version 1.24, or is there a set version for this feature to be implemented?

The thing is, now I use Native Instruments Battery in Cubase SX2 and use Cubase's plugin automation to directly control the sample start (among other parameters) value for different samples in Battery. First I tried letting Battery map between CC and the sample-start. However, this only gives me 128, or so, indexable points in the sample since the CC only can assume values between 0-127 (or between -127 and 128?).
As you probably can understand, it is very important for me that I can use real parameter automation and not CC-mapping (not that CC-mapping is useless, I just use that for other things Smile. Preferably I would like to be able to do this from Cubase and automate eXT, from Cubase, which could forward the automation data to its respective plugin within eXT. This because I prefer to use Cubase's note editor to sequence Battery for example, and it would be nice to also be able to control the automation from there in connection to the notes. However, if this is too much too ask, automation from within eXT could also work. I just need to know if, and/or when, I can expect this to happen Smile.

Regards & respect,
Tomas
jorgen
Posted: 11th April 2004 01:05
elfan, eXT has 128 VST params (unused at the moment). I have planned to add support for mapping those to MIDI CC, I'll see if they can map be mapped to VST params as well.

cheers
jorgen
elfan
Posted: 11th April 2004 08:04
Thanks a lot, Jorgen!

Let's say that it would impossible, or at least not worth it, to let eXT forward automation data from Cubase to the target plugin, i.e to do automation from outside eXT. How could/can real vst parameter automation be done from _inside_ eXT? I have heard of automation tracks (not CC tracks) which could be created in the sequencer or in a midi part in eXT. Is this possible in version 1.24 or if not, will it be possible in an upcoming version and if so, for which version is this planned (if planned for any particular version Smile.

Thanks once again,
Tomas
Forum topics in the archive are read only. New posts should be made in the main KVR Forums.
Disclaimer:
All communications made available as part of this forum and any opinions, advice, statements, views or other information expressed in this forum are solely provided by, and the responsibility of, the person posting such communication and not of kvraudio.com (unless kvraudio.com is specifically identified as the author of the communication).