Excellent news. I have been seeing long connect times when I'm connecting to my brand new VisionDaw slave(windows7 pro) as compaired to an instance on my desktop. Is this expected behaivor?
My desktop being osx 10.10.2
196,189 users have contributed to 43,015 threads and 258,397 posts.
In the past 24 hours, we have 1 new thread(s), 9 new post(s) and 172 new user(s).
Excellent news. I have been seeing long connect times when I'm connecting to my brand new VisionDaw slave(windows7 pro) as compaired to an instance on my desktop. Is this expected behaivor?
My desktop being osx 10.10.2
Hi,
Please define "long connect times"... how much longer does it take than with the previous version?
Did you change any preference settings (e.g., Ports and Audio Channels in the VE PRO Preferences?
You can always contact me at support@vsl.co.at with more details, screenshots, DP songs in specific cases (this should be the "announcement thread").
Thanks,
Paul
Hello everybody,
We have decided to add an info-screen when you first open VE PRO with the new MAS version in Digital Performer, which points you to the updated Vienna Ensemble PRO 5 manual with detailed instructions on a successful migration from AU/VST to MAS.
This version is now online in MyDownloads, with a few further improvements (check the VE PRO Changelog).
All the best from a busy Vienna,
Paul
"To accelerate the creation of your new templates with the Multiport Template for Logic Pro X and with the new MAS version for Digital Performer 8, you can use the MERGE funtion in Vienna Ensemble PRO ́s FILE menu"
Is this indicating that it's preferable for Digital Performer users to have one instance in your metaframe containing all your VI's vs. seperate Instances?
Hi,
Wow, you read the manual!
We think it´s nice to have more than just 16 instruments in one VE PRO instance, for better overview, less screen clutter, and of course to use with MIR PRO (all instruments in one room).
In any case, that´s now possible. I always use the channel collapse function to get more channels on the screen.
Best,
Paul
Hi Paul,
I'm looking for clarification on this as the manual isn't that clear to me. With the MAS version, can we now use Pre-gen mode or do we still have to set DP to run plug-ins in real-time? The only place Pre-gen is mentioned is under "Working with Audio Input/Event Input plug-ins."
Thanks,
Chris
I made a "how to connect VEPro to DP" video. It shows DP utilizing 48 MIDI ports. I also briefly touch on a couple related DP tips like MIDI Device Groups (which I plan on discussing in detail in a later video).
I also suggest that for your main templates at least, save your instances as vi frames and the project's VEPro Server's metaframe in your DP project folder. If anything ever goes wrong with instances not loading all you have to do is select all of your vi frames in the Finder and then drag and drop them into the VEPro server window. Then in DP add VEPro server interfaces and connect. You'll see all of you instances in the server interface window ready to be connected to. Then save DP.
Enjoy!
hi ! All ! I have problem with a new mas plug-in for weight dp.
before you press the button (disable instrument) vienna court discharged from the project, and then when you press the button to enable it includes.
So I built templates necessary instruments and included only those instances that are needed.
Now when you press the button to turn off court is not unloaded
Please see the video as it was in the old version vienna without mas plugin
Please see the video as it was in the old version vienna without mas plugin
vienna ensemble version 5.3.13407
I made a "how to connect VEPro to DP" video. It shows DP utilizing 48 MIDI ports. I also briefly touch on a couple related DP tips like MIDI Device Groups (which I plan on discussing in detail in a later video).
Great tutorial!
Thanx 😉
Hello again,
Another update: We have decided to pull VE PRO from MyDownloads and roll back to the previous version until we have fixed the AU/MAS confusion (working on it with high pressure, and it is looking good).
If you´d like to roll back, please use the VE PRO Uninstaller, this way the MAS plug-in will be completely removed.
I will let you know as soon as the update is available!If you´d like to accelerate beta-testing, please let me know at support@vsl.co.at, I´ll provide you with the next release candidate as soon as it is ready.
Thanks for your understanding and patience,
Paul
Paul,
I've had a number of issues with the latest update. Can you clarify which version we should be rolling back to? The software version I just downloaded is v.5.4.13682. Is this the previous version? It still gives the option to install MAS. I installed this version with the MAS optioin unchecked, but then couldn't get VE Pro to successfully communicate with DP at all.
Can you clarify which version we should be rolling back to?
Is there any answer on this? I'm highly regretting updating VEP before all the bugs have been worked out. I can't go 10 minutes without a crash, whereas before I didn't have any.
Hello Ben,
The version before 5.4.13682 is 5.4.13407, available in the Software Archive.
If you´d like to share the problems you are having and maybe want to send us crash reports and short instructions on how to reproduce the crashes you are getting, please send them to: support@vsl.co.at
Best,
Paul
Does it help lower CPU in DP to lower the 48x16 available midi channels per instantiation? or doesnt it matter?I don't believe so but I'll address it in the part 2 to my last DP/VEP video which should be up later this week. Upping the buffer size in the VEP server interface and optimizing the VEP thread count definitely helps with playback and online bouncing to audio though. Steve
Same with me.
Constant crashes DP 8 with 5.4.13682
rig was stable under old VEP.
Seems to be as the VEP template gets larger, crashes started occuring.
Sent support an email.
Love you guys - but this one sucked boiled eggs. Lost a lot of time dealing with it.
Same with me. Constant crashes DP 8 with 5.4.13682 rig was stable under old VEP. Seems to be as the VEP template gets larger, crashes started occuring. Sent support an email. Love you guys - but this one sucked boiled eggs. Lost a lot of time dealing with it.Have you noticed anything in the crash logs? 5.4.13682 has been extremely stable for me.