-
Just to add a little perspective to this... it might appear as if thereās been a massive uproar about the upgrade but remember that this thread consists of complaints from about 10 people, and some of them repeating over and over. So I donāt think Paul and Vienna is too concerned.
So says the person who came up with the stupid idea of a subscription model for VEPro.
-
So says the person who came up with the stupid idea of a subscription model for VEPro.
Wow, you're still talking? The guy who doesnt understand how digital software licensing works? Wait, wait, is this the same guy who says that not purchasing a license for a software upgrade is the same as a downgrade?
Oh please, tell me more about how much of a troll I am, make fun of my username, and oh God, tell the joke AGAIN about how I came from gearslutz, because, youre a comedy genious.
For the rest of us that actually care, Im trying to figure out what we might be seeing in VEP7. We know its going to have new FX based on Vienna Suite, and we know it is not notation software.
-
Im trying to figure out what we might be seeing in VEP7.
Funny, isn't it? Shouldn't be you or me or any customer trying to figure that out.
Very true, but no reason we cant discuss functionality we'd like to see...
-
Hello everybody,
First of all: Thanks for all your input and postings here. We are happy to see that so many of you feel so passionately about this software, and we are doing our very best to justify your support and meet your expectations.
You probably know that Vienna Ensemble Pro development is always a very involved process, as we not only have to deal with a myriad of plug-ins and their āspecialitiesā but also with specific solutions for the various DAWs out there. What looks the same from the outside can be VERY different from a technical perspective and calls for a dedicated solutions (which again needs to LOOK the same from the userās perspective).
To use my favorite euphemism I learned from our developers: It can be tricky :-)
STATUS QUO:
We are now in the beta stage for VE PRO 7, to make sure that we have not missed any perspective and also to incorporate input and ideas from our beta team, with real-world situations, stress-tests and compatibility tests, and I am confident that we are on a great path to have VE Pro 7 ready for you within the next weeks.I am not posting a release date but we are aiming at a release in the last week of march, and we will also post updates of confirmed features as we get further ahead in beta-testing.
On a personal note: What worries me most in this thread is that there are so many āin-fightsā about who is right on a topic you have little to no information about. That lack of information is our fault, as we want to publish this information only when itās 100% confirmed. Iām just saying that itās not a pleasure to watch and we are sorry about all the anger this has caused.
I know that you will get along perfectly fine in the real world, as you are clearly all passionate musicians.
In this spirit: We are all looking forward to the time when we can finally announce more features, and we hope that Epic Orchestra 2.0 helps to bridge the time until we get there.
All the best from Vienna,
Paul and the VSL Team
Paul Kopf Product Manager VSL -
Hello everybody,
snippage here
In this spirit: We are all looking forward to the time when we can finally announce more features, and we hope that Epic Orchestra 2.0 helps to bridge the time until we get there.
All the best from Vienna,
Paul and the VSL TeamYou don't have to wait until everything is nailed down and working perfectly to let us know what's in the new version. A lot of us can't afford to spend the money on something to get a discounted price for something that may not work for us. After all why should Vienna earn interest on that money?
-
Hello Paul
The best to stop this very long thread is to give us a time table of what you are going to introduce in VEP 7
Not to put too much preasure on your very good programmer you could put a large time scale
i.e.
AAAAA for end of May
BBBBB for end of June
CCCCC for end of July
DDDDD .....
You put that in a table that you can update
The problem is there is no tust in VSL any more because what VSL user are needing is not develloped
We have been waiting for so many years for AU3 and NKS
Best
Cyril
-
Hello Paul
The best to stop this very long thread is to give us a time table of what you are going to introduce in VEP 7
Not to put too much preasure on your very good programmer you could put a large time scale
i.e.
AAAAA for end of May
BBBBB for end of June
CCCCC for end of July
DDDDD .....
You put that in a table that you can update
The problem is there is no tust in VSL any more because what VSL user are needing is not develloped
We have been waiting for so many years for AU3 and NKS
Best
Cyril
As to when to expect VEPro 7 according to what Paul said they're looking at the end of this month but I doubt that will happen. But I still don't get why Paul can't tell us more about what's new in version 7. The teasing Vienna is doing is costing them trust just like you say. Given the dearth of info on VEPro 7 I'm not surprised this hasn't shown up on Gearslutz - what's happened would only be 10 times worse over there.
-
What is AU3? Never heard of it before.
Audio Units version 3, multi port š
-
What is AU3? Never heard of it before.
Audio Units version 3, multi port š
Interesting but like I say - never heard of it before and my secondary daw (Digital Performer) uses au format plugs as it's normal format. I tried Googling au3 and the only stuff that came up was for an automated scripting language.
-
On dp you should be using the mas version of the vep plugin which provides true multuport. Au3 is mainly relevant for logic users. In a few weeks we should know what vep7 is. Personally I doubt they could deliver multi port on Logic Pro, regardless of whether they build the plugin as AU3, due to limitations in Logic Pro. It it sounds like we shall find out soon enough. Myself I am not the least bit concerned about waiting to find out whatās going to be in it. I would never pay for it until then and aside from missing the taikos, I donāt really see any problem related to that. Vsl should take their time to get it right and announce factual information about features. I have no problem with any of that. The licensing changes, however, have me very very disappointed in vsl as a company and unlikely to upgrade unless vep7 turns out to be a literal masterpiece. So, we shall see in a few weeks.
-
On dp you should be using the mas version of the vep plugin which provides true multuport.
I know about using the MAS version of VEPro in DP. It's just that my reference for au format plugin use was/is DP. Main daw is PT and of course that uses AAX format.
Au3 is mainly relevant for logic users. In a few weeks we should know what vep7 is. Personally I doubt they could deliver multi port on Logic Pro, regardless of whether they build the plugin as AU3, due to limitations in Logic Pro. It it sounds like we shall find out soon enough.
Myself I am not the least bit concerned about waiting to find out whatās going to be in it. I would never pay for it until then and aside from missing the taikos, I donāt really see any problem related to that. Vsl should take their time to get it right and announce factual information about features. I have no problem with any of that. The licensing changes, however, have me very very disappointed in vsl as a company and unlikely to upgrade unless vep7 turns out to be a literal masterpiece. So, we shall see in a few weeks.The license changes are my major heartburn with VEPro 7 and like you VEPro 7 will have to be outstanding for me to make the jump. Why pay money to go backwards?
-
Interesting but like I say - never heard of it before and my secondary daw (Digital Performer) uses au format plugs as it's normal format. I tried Googling au3 and the only stuff that came up was for an automated scripting language.
https://developer.apple.com/videos/play/wwdc2015/508/
-
Thanks Paul, donāt let a couple of people stop your inspiration and hard work.
WHAT?? ... No one wants to stop anybody from anything. The main concern in this threads was an āextremeā missing of information. And just to add this: The communication problem is a Herb-problem, not a Paul-problem. Paul does not make the rules in this firm. The business leader must take responsibility, not an employer.
-
Thanks Paul, donāt let a couple of people stop your inspiration and hard work.
? Paul's a company rep - nothing more, nothing less. He does what he's told to do.
Forum Statistics
196,363 users have contributed to 43,015 threads and 258,405 posts.
In the past 24 hours, we have 0 new thread(s), 7 new post(s) and 140 new user(s).