so, is everyone now settled on "715"? (a.k.a. "ver. 5.4.13715")
-
major bummer tonight....:(
I was trying out my first project with the new & improved VEP5 ver. 5.4.13741. I'm on a single MacPro, running DP8.07 on OS 10.8.5. I set up a piece with a single instance of VEP5 that contained 5 Kontakt 5 instances. All went really smoothly as I was writing the piece, but once I had a version I liked, I attempted to "bounce" all of my 40+ midi tracks to a 2-track .wav. This was the biggest thing that I was looking for with the new VEP5. It didn't work at all. The resultant .wav contained only bits & pieces of the 40+ midi tracks and after the bounce finished, a number of notes "hung". (first time I've had that in 3-4 years).
So has anyone else tried bouncing midi tracks to audio, using the new VEP5?
-
-
I'm still having the issue of faders dropping to 0 on my VSL WInds Project when I enable the VEP5 plugin in DP 8.
I am hoping that the latest update will fix that but I see the update is an AU update (don't see an MAS update.) Do I download the AU update of VEP5 and it will update the MAS version? I have the correct settings in DP with AU disabled etc. Is this the way to go?
Thanks!
DC
-
Dear Sir,
I am using it by DP 8.07 and 9, efficiency improved, however, in bouncing process, all instances reloaded several times in the bouncing process, it used more time, it was OK! but the vital problem is Eastwest Hollywood instance, it consumed more time in loading even I already used PCIe SSD with 32G ram, it turn out the bounced wave was without the sound of Hollywood plugin. My solution was just used AU instead of MAS in Hollywood instance. Can it be solved in the future?
-
VE 5.4.13888 64 bit
Host Mac pro 6,1 64G ram OS 10.10.5 runing DP 8.07 and 9, with Kontakt 5.5.1 , Play ver.4.3.1 and Space ver.1.1.23
Slave Mac pro4,1 32G ram OS 10.10.5 Eastwest Play ver.4.3.1 loading Hollywood Orch. wth PCI e SSD
Slave iMac 13,2 32G ram OS 10.9.5 Kontakt 5.4.1
Slave PC i7 16G ram Windows 7 Kontakt 5.4.3
bounced wave was without the sound of Hollywood instance because the reload process not completed yet while bouncing completed.
Besides, jumbo frames failed in AU(MAS not tried yet) mode , with Netgear Prosafe GS108T
-
a quick MAS success story: i just transitioned from DP 7.24 to 8.07 just so i could use the new MAS version of VEP. before, i was using 88 instances of the event input plugin (feeding 2 PC slaves) to make my very large template work, but my 6-core 3.33gHz 2010 mac pro could barely take it. according to activity monitor, it was idling at 80% CPU and going well over 100% during recording and playback, and i had to disable DP's automatic latency compensation to avoid crashes and stuck notes. but with the latest MAS version (888), DP 8.07, and OS 10.8 (latest), i only need one plugin per slave and my CPU idles at 17%. everything's working great so far. i just wanted to thank VSL for spending the time and resources to develop the MAS version - it's made a HUGE improvement for me!
-
Hello. I've been using VEP and Digital Performer for quite a while now, but just encountered a weird problem. Not sure where it started, or if it's a VEP or DP thing, but here goes.....
When bouncing offline in DP, if I use any output in VEP other than 1 & 2, there is a noticeable lateness in the audio when I import it in to DP. I tested with a midi drum track playing through Kontakt in VEP going out 1 & 2. When I bounce offline and re-import to DP, the timing is right on the grid. If I just change the output assignement in VEP to something else and redo this, the timing is behind the grid consistently. I've gone through every setting and option in DP and VEP trying to get around this but it's still there. Here's a screenshot of what the audio offset looks like:
The top track is using output 3 & 4 (I called it Offline Normal) and the bottom track is using 1 & 2 (from Audio)
Any ideas?
DP 9.02, VEP 5.4.1.3888, Mac Pro, MAS plugin version
-
-
I am getting constant Digital Performer crashes using DP 9.02 and VEPro 5.4.14074 on a Mac Pro. I have been using this combination for a few months without this problem but today DP crashes almost every time I hit Play. The crash report points to VEP MAS as the plugin causing the crash. I have numerous instances of VEP MAS in my sequence connecting to 3 PCs. VEP is not crashing on the Mac or the PCs.
You write that MOTU has reported a bug—is that specfically related to DP 9 and VEP 5?
I tried opening the DP file in 8 and the crashes continue. This is the same DP file that was working fine yesterday in 9. The crashes occur seemingly randomly. The sequence can play for 60 bars and then crash or play for 1 bar and crash.
-
Motu has confirmed some bugs in the DP engine, an update is on the way.
Martin,
MOTU just released DP 9.1. This may have been the update you were referring to...but in general I have found using the latest VEPro 5.4.14074 (MAS version) with the new DP 9.1 to be NOT as stable and not as efficient than when I was using DP9.02. This may be a DP problem of course because they completely changed how their audio engine works in this update with their new "nextgen / pregen" feature. The setting for that is turned off by the way for all VEPro5 plugins and they are set to run in "real time" in DP becaue they know it will not work well with it. But regardless ther is still something else going on and you all may have to get together with MOTU about this DP 9.1 verison and figure out why on large "film scoring" orchestral templates...using VEPro5 is spiking my CPU more and not very usable like it was in 9.02. And this is on a MacPro 5,1 12-core with 64GB RAM running Mavericks OS10.9.5. I use to be able to set the VEPro instances buffer to "2 buffers" each (running 6 instances in DP V-Racks)....but with that same setting in DP 9.1 and nothing else changed, I was getting severe audio waveform dropouts in all audio coming into DP from VEPro when the transport was actively playing or recording MIDI or audio. Audio coming into DP while the transport was stopped was fine. I have now had to set all VEPro instance buffers to a setting of "4 buffers" to get rid of waveform dropouts...but of course this affects latency greatly.
Please check in with the MOTU folks about getting VEPro5+ working solid with DP again. Till then, I will have to go back to DP 9.02 to get my solid template and machine runnnig smooth again.
Brian Ralston
Los Angeels, CA
-
I can report the following-
1) No cpu improvement on a session that uses VE Pro for most of it's VIs. It is actually possible cpu performance has gone down. Unfortutely, the update over wrote my 9.02 version, so toady I will re download 9.02 and will advise if I have additional data.
2) Audio glitching while undoing or creating looped sections in DP for editing.
3) Changing VE Pro buffers from 0 to 4 results in VE Pro playing behind the beat. (it was mentioned at one of the forums that VE seemed to work better at buffer of 4 so I tried it).
4) I am pretty sure I am going back to vers 9.02
Question- Does Vienna anticipate cpu improvment in VE Pro projects using the new DP audio engine once all bugs are removed? I am wondering if the main beneft will mostly likely be obtained by placing VIs inside DP itself. I run my VE Pro on one machine
-
Same here - lots of issues.
My playback meter goes up to 50% when playing a project with only a few instances of Kontakt loaded, which didn't happen in 9.02.
Still can't freeze in DP using VE Pro if the incoming channels are not 1/2. 3/4 or above and the freeze doesn't work.
UPDATE: I updated to El Capitan and this seems to now work. Much weirdness! Loving the new VE Pro though.
