200,779 users have contributed to 43,212 threads and 259,132 posts.
In the past 24 hours, we have 3 new thread(s), 10 new post(s) and 46 new user(s).
Hi iscorefilm,
We will announce the upgrade path from VE PRO 4 to VE PRO 5 when VE PRO 5 is actually released. And of course it will be a reasonable upgrade price (it has not been decided yet).
We won´t upset thousands of VE PRO 4 users, no worries.
So if you need VE PRO now, you should get it!
Best,
Paul
Thanks. I wasn't fishing for a price, so much as knowing that I won't make some horrible mistake if I get 4 now.
Not that any VSL product could ever qualify as a 'mistake' anyway 😊
-Sean
Sean, I think the most important question for you to consider is how important are the current features of VE Pro? If it is only the much vaunted new features that really interest you, I can see that you might want to wait until upgrade pricing is known. However if the current version has features that would really help your workflow, I would suggest that you just go for it. You don't have to upgrade immediately VE Pro 5 is released, and you'll have lost nothing.
FWIW for me the Preserve feature has saved many hours of my time, so for that feature alone it is worth its weight in gold. Almost....!
DG
As for workflow, there are features in both versions I'll want, but I'm still iffy. The Preserve feature used to be important to me but now I'm less sure. I recently posed a question but it wasn't answered.
I use VE as a standalone with LoopBe30 to route the midi from Cubase to VE. With that in mind, would there be any advantages to using VE within cubase instead? Latency won't matter to me, cause I'd rather run everything through VE and use Cubase stricly as a midi editor/sequencer. So I don't see any advantage to having VE as a VST plugin. Am I missing something?
-Sean
As for workflow, there are features in both versions I'll want, but I'm still iffy. The Preserve feature used to be important to me but now I'm less sure. I recently posed a question but it wasn't answered.
I use VE as a standalone with LoopBe30 to route the midi from Cubase to VE. With that in mind, would there be any advantages to using VE within cubase instead? Latency won't matter to me, cause I'd rather run everything through VE and use Cubase stricly as a midi editor/sequencer. So I don't see any advantage to having VE as a VST plugin. Am I missing something?
-Sean
Three things that immediately spring to mind:
DG
WHOA WHOA WHOA!!!!
Am I right in thinking that I could have an audio interface with 32 audio channels (16 stereo), but route the audio from VE back to the DAW with as many channels as my CPU and each VE instance can handle, rather than what my interface has?
If that's true, that will blow my mind away. That will save me SO MUCH money from what I originally intended to do. Sorry to pester you with questions but after reading the feature list and watching the videos- some of the features seemed a bit hazy. Thanks for answering my questions so far. This is my last question though, promise! [:D]
-Sean
Hi Sean,
Am I right in thinking that I could have an audio interface with 32 audio channels (16 stereo), but route the audio from VE back to the DAW with as many channels as my CPU and each VE instance can handle, rather than what my interface has?
Yes, of course you can do that, if you´re working with our LAN solution. Just as mentioned in the feature list of VE PRO, and explained in the manual [;)]
Best,
Paul
Just to add that using the term "LAN" can be slightly confusing if you only have one computer. [;)]
However, the answer is that you can route as many channels back as you like, just as you would with a regular VSTi. As I said, I currently have 110, and all of them are routed to audio tracks, so that when I am ready to print the VSTi to audio, I only have to hit record, and the whole thing takes as long as it takes to play the track. Pretty nifty...!
DG
