Forum Jump
Originally Posted by: rockdude9k 
So I think you make a valid point, that VSL wants to prioritize their VST instruments over VEP. But I always thought that was kinda backward. I've been working in film scoring for 15 years and have worked for several A-List composers and I've never been in a studio that had VSL VST's as their primary libraries. Maybe a couple patches here and there, but never the whole template built around VSL instruments. So despite their marketing, I've always thought VEP was their most popular product.
So is their VST instrument market way more popular than VEP? Is that why VEP has been deprioritized?
Genuinely curious. For context I don't own a single VSL VST instrument.
The reason I thought that and was right about them wanting to port at least newer libraries over like Synchron before VEP has more to do with simple pride, if none of their plug ins but VEP run natively then it looks bad when you as a user are using other companies libraries in VEP but not VSL's. With Synchron ported first then they can port VEP and have a lot of plug ins to offer natively.
|
|
|
|
|
|
To be fair to VSL, they are not the only company with plug ins or DAWs not ported, Pro Tools native is still an open beta, and Reason Studios isn't even in beta. Then there's Air, PSP, NI, Audio Ease, Nomad Factory etc.
You'll notice all these companies are more than 10 years old, technical debt piles up, NI admitted that some of their plug ins have 15 year old GUI code. Reaktor their oldest product is last in line for native support. Who knows if Air or Nomad Factory will ever port? PSP have been going one plug in every couple months for a long time now.
|
|
|
|
|
|
Okay, ya I get the pride thing. I can see how they want to say VEP is native and here are all of our instruments that can run in VEP natively.
And at this point I wouldn't be surprised if it's VEP8 with new features and AS native. If that's the case, it would certainly help explain why it's taken so long.
I'm just still frustrated that they didn't focus on the bridge plugin. I've said it before and I'm saying it again, I just need the bridge plugin to run natively and then everything will be great. VEP is a tool, it's meant to be a workflow solution and it feels like marketing has taken over and said, no no, we have to have new features and a new version and it all has to be released with our other products. But from my point of view, I just want to use the tool that has become essential to my workflow. I would have happily paid $20 (or more) for the bridge plugin to be updated and then they can take all the time they need to release VEP8.
|
|
|
|
|
|
I have to agree with rockdude9k. I am now at the stage where I have reworked my Cubase template and I need to delete all my non M1 compliant plugins. Whether Universal Audio, NI, iZotope etc..
There are important software, like your Vienna Ensemble Pro 7 that provides so many other instruments for me on different servers.
I wouldn't know how to organize all my instruments without Vienna Ensemble Pro 7. It would be similar to NI saying, they don't care about the Kontakt 7 plugin anymore.
So my please to you, make our most important tool (At least for me and all who have bigger templates) a higher priority in your development.
|
|
|
|
|
|
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.