192,018 users have contributed to 42,822 threads and 257,515 posts.
In the past 24 hours, we have 10 new thread(s), 66 new post(s) and 232 new user(s).
Hello everybody!
Finally some news on the features of VE Pro 7!
All the best from a busy busy busy Vienna,
Paul
Great news, really appreciated set of features and nice presentation (Hopefully stopping bad moods 😊 and... looking forward to final release!
Thanks for the clarification. Wasn't sure if the date froze on purchase or when Paypal posted it to my card - those have turned out NOT to be the same date in some cases.Hi musicman,
The exchange rate is the one used on the day of purchase. If you used PayPal, you might already see it in your PayPal account. You can also see a 'Show US-$ Info' on the bottom left of the VE Pro 7 product page.
Great to see happy first responses of details on the VE Pro 7 features!Best,
Stefan
On other notes it took about 48 minutes to download the whole library which isn't too bad as I had other things to keep me occupied. Surprised at how decent the Synchron freebie is. Now to just wrap my head around the Synchron player.
Also, we’re hoping for a little miracle on the AU3 side of things. We’re quite close to making this a GREAT feature for all Logic users out there, and even if a new version of Logic is probably not released when VE Pro 7 is ready, we’re hoping for some crucial fixes that will make this feature work!
This is very encouraging. in your talks with Apple, please make sure they do not overlook that the Scripter plugin will need to be updated to be aware about "port". Many orchestrators are relying on scripter for articulation management above and beyond the built in articulation set features of LogicPro. Scripter will need to become port-aware, just like tracks, the enviornment and everything else in order to fully support a multiport AU3 plugin. I really hope you guys will be able to make all that happen. But I also realize this depends a lot on what Apple decides to do to LogicPro in order to support multiple ports per instrument channel.
Good job getting the product info out to everyone...
This is very encouraging. in your talks with Apple, please make sure they do not overlook that the Scripter plugin will need to be updated to be aware about "port".
The best thing, when AU3 support is released, is to get rid of the Scripter plug-in and the Multi Port Macro ;
I have upgrade to V7 😉
This is very encouraging. in your talks with Apple, please make sure they do not overlook thatthe Scripter plugin will need to be updated to be aware about "port".The best thing, when AU3 support is released, is to get rid of the Scripter plug-in and the Multi Port Macro ; I have upgrade to V7 😉 Au3 will not eliminate the need for scripter! Scripter is used for articulation management by many people. That has nothing to do with the multiport macro or AU3. But the thing is scripter will need to become port-aware in order to function with a multi port AU3 plugin. Scripter can already work with the existing multiport macro because port is specified via CC99 and scripter can detect and send that. When AU3 comes, there will be internal data to track port inside the event object itself so unless that is exposed in scripter, then it will not be possible to have multi port articulation management scripter solutions any longer. Also, as vsl hinted already; they are working with Apple on this and “crossing their fingers” which is a nice way of saying that LPX has to be improved in order to support AU3 multiport configurarion. An AU3 plugin from vsl will be meaningless until LPX is updated in all necessary ways to support that. I agree we can all move past the multi port macro when that day comes but a lot depends on what Apple will do to LPX in order to support it, including changes to the environment, scripter, track headers, and probably other places as well and internally to support channelizing tracks on both ports and channels. Until such time the multiport macro still works. If vsl removes multiport cc99 support from vep7 I will not buy it
It is better to have the AU3 and Logic Expression Maps as it is hardcoded in Logic
It look like Scripter is interpreted, so will run more slowly
You can use Babylon Waves to handle your Logic Expression Maps
It is better to have the AU3 and Logic Expression Maps as it is hardcoded in Logic It look like Scripter is interpreted, so will run more slowly You can use Babylon Waves to handle your Logic Expression MapsFor many people, myself included, logicpro’s articualtion sets, (there are no expression maps in Logic Pro) are not adequate for certain situations, and scripting is necessary. In some cases the Apple articulation set output section is buggy as well. There are several third party solutions that work around those shortcomings with scripter. Those solutions will not be able to take advantage of AU3 multiport unless scripter is updated to be port aware. Babylonwaves does not provide solutions to these challenges they have just worked out a common set of input key switches to use with all libraries and setup the articulation sets for you but they are still limited by the limitations of logic pro’s articulation set feature set and bugs. And in some ways may be limited by trying to have one common input keyswitch paradigm which is a nice idea for simple scenarios but entirely inadequate for more complex situations. It’s a lowest common denominator in that sense. It doesn’t always facilitate all of the capabilities of any given library and nor does logicpro’s articulation set feature. I agree if your needs are simple then stick with simple solution such as that but if you have more advanced needs then scripter is often needed. It will be crucial for many people that vep plugin supports port awareness in scripter. For example, legato latency correction is a hot topic lately with some attempts to create better articulation management using scripter. There are other things too and plenty of room for future improvement to articulation management, but if scripter is not made port aware then those advanced scenarios will be blocked from being able to use AU3 multiport. For those of you with simple needs then I agree try to avoid scripter of course. By the way scripter does not in itself make anything run slowly it uses very little resources when scripted properly.
Simple question I'm not sure if it got asked yet: when will we know VEPro 7 is released? Email notification from Vienna? I ask because if it's the latter sometimes emails from VSL end up in my isp's Spam folder.
Simple question I'm not sure if it got asked yet: when will we know VEPro 7 is released? Email notification from Vienna? I ask because if it's the latter sometimes emails from VSL end up in my isp's Spam folder.
The product note says the cusotmers owning the license will receive personal notification via email, and the announcement will be into the newsletter (to the mailing list of customers enabling newsletter in the account preferences). When a newsletter is delivered, it is also available in the "News" section of the website.
It's hard it won't be noticed in my opinion. 😊
P.S. One time by the way, I found by chance a product available in my "MyVSL" page just before announcement, because of course they upload it first, and then they distribute the notice.
I am curious what this means for Vienna Suite. I mean, are we going to see a massive price drop on it to keep it in line with what Ensemble Pro costs? It appears that Vienna Suite and Vienna Suite Pro are going to be the same as what is coming with Ensemble Pro now...
Its reasonable to assume that that plugins included with VEP7 will be hardwired into VEP7 and will not be available for use directly in your DAW. While Vienna Suite would work in your DAW. And I think at least in the Pro version of vienna suite there are a few more plugins that are not really that interesting to most people. Practically speaking probably most people that would consider buying vienna suite are already owning VEP7 and probably won't need vienna suite anymore as a standalone product. The new plugins built into VEP7 look to have been updated a bit, at least in terms of colors and nice user experience, not sure if they actually do anything that vienna suite can't do.
The main value of vienna suite or what's included with VEP7 will be the EQ and compression presets, especially if you're using VSL instruments...
Okay - we all know that VEPro 6 and 7 can't communicate with each other - that much has been mentioned by Paul. But what about templates constructed in VEPro 6 - can those same templates be used in VEPro 7? I imagine they'd have to be copied over to another folder.
Okay - we all know that VEPro 6 and 7 can't communicate with each other - that much has been mentioned by Paul. But what about templates constructed in VEPro 6 - can those same templates be used in VEPro 7? I imagine they'd have to be copied over to another folder.
I imagine so, but once you go forward with a template, you cant go back. IE. loading a version 6 template in version 7 will automagically convert it to version 7 and the act of saving the project will make it no longer compatible with 6. Thats how most of this stuff works.
By the way, as a side note, its interesting how the tone has completely changed... As I said, wait and see if Vienna delivers. It sounds like they did from what I am hearing. For me, contrary to the opnions of everyone else here, I like the idea of Vienna Suite being integrated into Ensemble. The rest of the feature set is meh for me.
Okay - we all know that VEPro 6 and 7 can't communicate with each other - that much has been mentioned by Paul. But what about templates constructed in VEPro 6 - can those same templates be used in VEPro 7? I imagine they'd have to be copied over to another folder.
I imagine so, but once you go forward with a template, you cant go back. IE. loading a version 6 template in version 7 will automagically convert it to version 7 and the act of saving the project will make it no longer compatible with 6. Thats how most of this stuff works.
By the way, as a side note, its interesting how the tone has completely changed... As I said, wait and see if Vienna delivers. It sounds like they did from what I am hearing. For me, contrary to the opnions of everyone else here, I like the idea of Vienna Suite being integrated into Ensemble. The rest of the feature set is meh for me.
For your first statement that's a heck of an assertion because you're assuming VEPro 7 will open stuff done in VEPro 6. Just because others/w has done that in the past it may not happen here. Would be great if it does.As to your seond statement Vienna hasn't delivered anything except for a few more specifices of what's in the new version. I'll consider that they've delivered something when I actually have the new version on my computer and working.
Okay - we all know that VEPro 6 and 7 can't communicate with each other - that much has been mentioned by Paul. But what about templates constructed in VEPro 6 - can those same templates be used in VEPro 7? I imagine they'd have to be copied over to another folder.
I imagine so, but once you go forward with a template, you cant go back. IE. loading a version 6 template in version 7 will automagically convert it to version 7 and the act of saving the project will make it no longer compatible with 6. Thats how most of this stuff works.
By the way, as a side note, its interesting how the tone has completely changed... As I said, wait and see if Vienna delivers. It sounds like they did from what I am hearing. For me, contrary to the opnions of everyone else here, I like the idea of Vienna Suite being integrated into Ensemble. The rest of the feature set is meh for me.
For your first statement that's a heck of an assertion because you're assuming VEPro 7 will open stuff done in VEPro 6. Just because others/w has done that in the past it may not happen here. Would be great if it does.As to your seond statement Vienna hasn't delivered anything except for a few more specifices of what's in the new version. I'll consider that they've delivered something when I actually have the new version on my computer and working.
Umm, ok. The track record for most companies releasing a new software version of a product designed for creating something is on my side here. Rendering all previous work unable to be opened in the new version would be virtually unprecedented. Point me to a software product that has made all projects previously created in it unable to be opened in new versions without some ability to convert or upgrade the project. You might find one or two, but not much more than that.
As to your second comment, and I quote, "I did the pre-order thing and am downloading the Synchron library now...Paid through Paypal if that makes any difference." Apparently, they already sold you on it, as evidenced by this, "Let me be the first to say a big THANK YOU for this announcement. It's what a lot of us have been looking and asking for. And it's what's making me pull the trigger on getting the upgrade - especially the compatibility with OSX 10.10! While my major work is done in OSX 10.12.6 I still keep a boot partition with OSX 10.10.5 because I have some 32 bit plugins that for whatever reason don't play well in a 32 bit server running in OSX 10.12.6. It's not a big enough issue to raise a support ticket with (FYI the major one is NI's B4II Hammond organ vi). You have made me a very happy person this dreary day here." That is a much different tone than you and others had before, enough for you to purchase the pre-order.
Now Im off to work on designing a prototype mechanical lizard.
For your first statement that's a heck of an assertion because you're assuming VEPro 7 will open stuff done in VEPro 6. Just because others/w has done that in the past it may not happen here. Would be great if it does.
I would be staggered if it couldn't open VE Pro 6 projects. I'd put the chances of that at somewhere around 0.1%.
You say your loading time for that template is 35 to 40 minutes - please tell us you're not loading from a spinner drive but an ssd. Or multiple ssd's. If you're on a Mac Pro cheesegrater putting those ssd's in a pcie card adapter will double the loading speed from if they're in the drive bays.
Oh yes multiple ssds of course, and on a PC with double xeon.... Just lots of instruments i guess, and it loads up into about 240gb of ram . I know a couple of fellow composers who have the same "problem", so its normal for a template that size
Huge template then. How many instruments? If you have thousands, then it is what it is. This is another area where if VEP update made a substantial improvement for project load times, through parallelism or something...it would be instant buy for me.
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.
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
