190,120 users have contributed to 42,706 threads and 256,986 posts.
In the past 24 hours, we have 1 new thread(s), 19 new post(s) and 42 new user(s).
I have about 1750 instruments/articulations loaded in that template, and yes the ssds are all inside my server pc, I have the kontakt instrument preload buffer size set up to 60 kb. If I go lower than that my cpu starts overloading and i get voice dropouts... adn plus i got 256gb of ram on my server so might as well use it all 😊
Also thanks for the update on features. I am excited to see the load times are getting improved.
You will reduce your problems in doing articulation switching
Question;You mean VEPro right? There is no such product as VSL Pro. But anyways from something I read on this forum in another thread VEPro 6 overwrote VEPro 5 IIRC and if history holds and that bit is true VEPro 7 will overwrite VEPro 6. There may be a way around that at least in OSX if you rename the program to something other than what's installed. That's something that those of us do with Digital Performer if we want to have multiple versions on the same computer at the same time. For instance I have three different versions of DP - 9.02, 9.51 and 9.52
Does VSL Pro 7 replace Pro 6 as an update. If not, can we still use Pro 6 and Pro 7 together along with the old Epic Orchestra?
If Pro 7 replaces Pro 6, what happens to the other two license I have with Pro 6?
If you've been paying attention to this thread at all or the product page you only get one license with a base purchase of the VEPro 7 upgrade. Doesn't matter how many licenses you have with VEPro 6 or earlier versions. You have to pay extra to get the other two licenses to get to the three you had before.
The new Epic Orchestra does not replace the old one - it's an all new download.
Question;
Does VSL Pro 7 replace Pro 6 as an update. If not, can we still use Pro 6 and Pro 7 together along with the old Epic Orchestra?
If Pro 7 replaces Pro 6, what happens to the other two license I have with Pro 6?
1. The easiest one to answer, epic orchestra 2 is a completely seperate download that works in Vienna's Synchron player. If can be used side by side with Epic Orchestra 1, although, why youd want or need to do that is beyond me since epic orchestra 2 contains all the patches that 1 has and a hefty amount of additional content. True that the sound design will be different (ie. the coronet in the Epic Orchestra 2 will sound different than the one provided in Epic Orchestra 1), but once mixed, I dont think the difference is all that significant. I guess one thing this gives the ability to do is use EO1 vs EO2 on completely different machines (this is confirmed).
2. VEP7 software wise replaces the install of VEP6, that is, when installing VEP7, it will overwirte your install of VEP6, provided it works the same way the upgrade from VEP5 to VEP6 worked. It isnt a good idea to install VEP7 until you have all the VEP7 licenses you need (this is unconfirmed, but I think highly likely how this will work).
3. VEP6 will NOT communicate with VEP7. If you have VEP6 on one machine and upgrade another machine to VEP7, they will not communicate with each other (this has been confirmed).
4. Upgrade licenses do NOT replace your current licenses. Purchasing a VEP7 upgrade license will merely add a VEP7 license to your key fob, and you will keep your 3 VEP6 licenses (this is confirmed)
Basically, buy all the VEP7 upgrades you need first before you upgrade your physical installs of VEP7. As for Epic Orchestra 2, you can download and install that now and it will have no bearing on Epic Orchestra 1, so you can use that now or whenever you are ready to download and install it.
My understanding is that VEP server requires the VEP plugin to communicate with it, it does have direct access the midi ports on the machine where its running.
The non-server standalone version of VEP can listen to midi ports, but also does not communicate with your DAW via the VEP plugin.
If you want to figure out another way to get the audio from VEP back to your DAW instead of using the VEP plugin, then you could theoretically run the non-server verison of both VEP6 and VEP7 on two different machines, but that is missing a lot of the VEP-advantage IMHO.
Offhand I'd say no one consdering VEPro 7 hasn't been released yet (it's not in my account yet for d/l).Has anybodey tried to use IAC with VEP6 on one computer and VEP7 on another ?
Offhand I'd say no one consdering VEPro 7 hasn't been released yet (it's not in my account yet for d/l).Has anybodey tried to use IAC with VEP6 on one computer and VEP7 on another ?
May the Beta tester have test it 😊
Offhand I'd say no one consdering VEPro 7 hasn't been released yet (it's not in my account yet for d/l).Has anybodey tried to use IAC with VEP6 on one computer and VEP7 on another ?
May the Beta tester have test it 😊
If they did they won't tell us - that comes with the territory of being a beta tester - it's called an NDA.Keep in mind the old saw: those that know won't talk and those that talk don't know.
If I had to speculate I'd say it wouldn't work as that would circumvent the licensing we're getting in VEPro 7 and Vienna would never allow that. Better to just pony up the extra license fee which I know sucks but that's the only legitimate alternative and stay inside the VEPro ecosystem.
The big attraction for me with VS Pro is the Imager. But with the the other parts kinda sorta part of VEP 7, I'm even less likely to fork out 400 bucks for it.
I just upgraded with the assumption that licensing was similar to 6 - that is one set of three licenses....incorrect. Mea Culpa, but I have 3 (x3) VEP6 licenses and its spread out among 7 or 8 machines...that would make a full upgrade really expensive.
Seeing as how I won't be purchasing 6 or 7 more licenses for my remote machines, I'd like to know whether or not VEP7 will work with VEP6. That way I can put 7 on my main processing machine and use 6 in the remote machines for simpler tasks.
Thanks.
You should have paid closer attention to the product page. If you only had 3 licenses with your VEPro 6 setup you only need to buy 2 more licenses for VEPro 7 to get you where you were with VEPro 6.I just upgraded with the assumption that licensing was similar to 6 - that is one set of three licenses....incorrect. Mea Culpa, but I have 3 (x3) VEP6 licenses and its spread out among 7 or 8 machines...that would make a full upgrade really expensive.
Seeing as how I won't be purchasing 6 or 7 more licenses for my remote machines, I'd like to know whether or not VEP7 will work with VEP6. That way I can put 7 on my main processing machine and use 6 in the remote machines for simpler tasks.
Thanks.
It's been mentioned multiple times in this thread that VEPro 6 and 7 cannot communicate with each other.
That's fair, I SHOULD have. I admitted as much. I'm just trying to figure out how to use the new software without having to pay an arm and a leg more.
So, moving on.
If the two can't communicate, that would still work if I could run both 6 and 7 as plugins inside Cubase. I can have a 7 server on my local computer and have the other servers on remote boxes be 6. As long as I can run both 6 and 7 as plugins within cubase (or any other daw for that matter) simultaneously, I should be ok, otherwise, I'm out 90bucks for something that I can't use without spending a boat load more.
So I guess the next question would be whether I can run two instances of the VEP vsti plug in with two different versions from within the same DAW - I'd imagine as long as the Daw sees them as two distinct VSTi it shouldn't be a problem. That's how I can run Kontakt 5 and 6 simultaneously.
Can't be done. Period. Besides installing VEPro 7, if history holds, overwrites any existing installation of VEPro. So you'll only have VEPro 7.That's fair, I SHOULD have. I admitted as much. I'm just trying to figure out how to use the new software without having to pay an arm and a leg more.
So, moving on.
If the two can't communicate, that would still work if I could run both 6 and 7 as plugins inside Cubase. I can have a 7 server on my local computer and have the other servers on remote boxes be 6. As long as I can run both 6 and 7 as plugins within cubase (or any other daw for that matter) simultaneously, I should be ok, otherwise, I'm out 90bucks for something that I can't use without spending a boat load more.So I guess the next question would be whether I can run two instances of the VEP vsti plug in with two different versions from within the same DAW - I'd imagine as long as the Daw sees them as two distinct VSTi it shouldn't be a problem. That's how I can run Kontakt 5 and 6 simultaneously.
That's fair, I SHOULD have. I admitted as much. I'm just trying to figure out how to use the new software without having to pay an arm and a leg more.
So, moving on.
If the two can't communicate, that would still work if I could run both 6 and 7 as plugins inside Cubase. I can have a 7 server on my local computer and have the other servers on remote boxes be 6. As long as I can run both 6 and 7 as plugins within cubase (or any other daw for that matter) simultaneously, I should be ok, otherwise, I'm out 90bucks for something that I can't use without spending a boat load more.So I guess the next question would be whether I can run two instances of the VEP vsti plug in with two different versions from within the same DAW - I'd imagine as long as the Daw sees them as two distinct VSTi it shouldn't be a problem. That's how I can run Kontakt 5 and 6 simultaneously.
6 & 7 cannot be installed together on the same machine easily. There might be a clever workaround, but the install overwites any previous installations, provided it works the same way it has in the past.
My suggestion is to wait until you have upgraded all your licenses before installing 7, at least the future licenses are signifcantly less expensive than the first, so a little at a time. I agree, for the people running more than 3 licenses, this is not ideal, but I suspect that very few people are running more than 3 licenses.
It MIGHT be possible to run VEP inside a subhosting plugin like PlogueBidule where you can specify an alternative VST path or manually load a VST plugin that is not in the normal VST path. Then VEP7 plugin normally in the DAW, all on machine A. VEP6 server on machine B, VEP 7 server on machine C. But that is probably not the whole story, depends on what kind of internal interapplication and network communications and systems that VEP uses whether a VEP plugin isolated inside PlogueBidule would be completely seperated from a VEP plugin out in the DAW. Its worth a try, but I would not count on it until someone actually tries it.
Its definitely possible to run VEP Inside PlogueBidule, but what I'm not sure about is whether that one would be totally and completely isolated from VEP7plugin outside PlogueBidule.
As to having two versions of VEPro on the same machine I wonder if the following workaround would work (at least on a Mac):6 & 7 cannot be installed together on the same machine easily. There might be a clever workaround, but the install overwites any previous installations, provided it works the same way it has in the past.
My suggestion is to wait until you have upgraded all your licenses before installing 7, at least the future licenses are signifcantly less expensive than the first, so a little at a time. I agree, for the people running more than 3 licenses, this is not ideal, but I suspect that very few people are running more than 3 licenses.
Rename the existing installation of VEPro to something else
Install the new version with no alterations to the name
There's a bunch of people that have done that in order to have multiple versions of Digital Performer installed at the same time. For instance I have DP9.02, DP9.51 and DP9.52r2 all at once. The reason this works at least for DP and a Mac is that the installer looks at the name of the program which in this case the usually installed name is Digital Performer with no distinction as to revision. So once that name is changed the installer doesn't see it to overwrite it. It even works for whole number versions; in addition to the three DP9 versions I also have DP8.03. BVeing the licenses for each VEPro edition are different it might work.
No, it still wouldn't work because the used communication port numbers are the same. You must convince VEP 6 to use differend ports then the newer/ older version if this should work. And who knows which problems you'd also encounter. But if you find a solution that works, let me know ;)Very good point.
