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 ;)
Ben@VSL | IT & Product Specialist -
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.
-
-
Are there any news concerning a release date? The pre-order is running for a good solid two months now, and it feels like it is starting to stretch patience a little. Would be nice if VSL could go back to their old ways, which was announcing a product when it was ready, not when they thought it would be ready in a week or so but then miss that date by several months.
-
To be fair there is no date for VSL to miss as a solid release date was never given. All Paul said was that VEPro 7 was in beta test and gave us some of the features. Agreed the pre-order has been going on for way too long but then again I'd rather VSL get it right on release and not what MOTU did with the release of Digital Performer 10.Are there any news concerning a release date? The pre-order is running for a good solid two months now, and it feels like it is starting to stretch patience a little. Would be nice if VSL could go back to their old ways, which was announcing a product when it was ready, not when they thought it would be ready in a week or so but then miss that date by several months.
An update from Paul would be nice.
-
To be fair there is no date for VSL to miss as a solid release date was never given. All Paul said was that VEPro 7 was in beta test and gave us some of the features. Agreed the pre-order has been going on for way too long but then again I'd rather VSL get it right on release and not what MOTU did with the release of Digital Performer 10.An update from Paul would be nice.
[/quote]
True. And you can't please everybody. Still, for Synchron Strings and VE Pro 7 there is a long time between announcement and release - rather too long for my taste. Reading the title of this thread, started on February 18: "SOON: VE Pro 7", yes I agree that an update from VSL regarding the progress would be nice.
-
