Discussion in 'Your DAW (Digital Audio Workstation)' started by Ben, Feb 18, 2019.
I just did it now but no change...
Please send an email to email@example.com - someone will help you out asap.
I tried launching VEPro 5 (with 7 installed), and you definitely can't launch the server - and I think you can't load both AU plug-ins.
The standalone VEPro 5 program did launch, so you could probably use it with IAC MIDI.
Yeah, you download something like 40MB, and then it needs to install the full library as a separate process.
I just purchased VEP 7 and this sort of report is undermining my confidence with being able to use V5 when I want to (older projects). :( It looks like opening older V5 projects NOW in V7 will work but once 'saved' they are forever now in V7 (not able to open in V5) - which, if all works just fine no problem, but.... the paranoid part of my brain is screaming - will I have 'issues' working -- moving forward in V7?
Well, you can make copies of them and put them in a separate folder.
But I guess that could be an issue if the VE Pro instructions are stored with your sequences rather than as VE Pro Projects?
Defimitely save your vep5 frames as separate vep7 files and keep the vep5 ones around just in case. I have not had any problems opening old frame files in vep7 FWIW.
But yes if you want to use vep5 again you will have to uninstall vep7 and install it.
Great advice from both of you - thanks. Makes me feel better about moving forward on 7.
More Performance Test results with VEP7
This was mainly to compare Cubase vs LogicPro and DP, both with and without VEP7.
MacPro 5,1 12 cores x 3.33ghz, 128gb ram, OSX 10.14.5 (Mojave), RX580 video
Audio Buffer at 1024
Test was performed with both application windows showing at 4k native resolution (see image below)
Test Project is E.T. Score tutorial originating from VSL website, it has been modified and runs on Cubase, Logic or DP with exactly same playback midi tracks feeding exactly the same VEP frame. ~100 tracks of VIPro instruments, MirPro and Miracle.
Procedure was to measure total system average CPU usage % every 3 seconds over 3 minutes while playing the first 3 minutes of the score.
Various combinations of Cubase ASIOGuard and LogicPro process buffer size were used to compare. Logic was testing with medium and Large Process Buffer size. DP was tested with low, medium, high audio priority.
Full Google Spreadsheet here:
LogicPro alone: wins the CPU war using 25% average CPU usage.
LogicPro+VEP: 34% avg cpu
Cubase+VEP: 49% avg cpu
DP9+VEP: 38% avg cpu
DP9 alone: 35% avg cpu. Also tried DP10 which performed 5% worse.
Cubase10 alone: can't complete the task, it will not play more than 15 seconds without crapping out. I did try all possible combinations of buffer size, ASIO Guard, etc. Will not play the project.
I'm thrilled that VEP7 can be used to make up for the fact that Cubase10 on its own has horrible instrument performance on the Mac. And its not terribly worse then LogicPro+VEP and DP+VEP can do. I view VEP7 as essential to use with Cubase on Mac.
LogicPro has some kind of odd PDC situation, which I will call a bug for right now, where if you select an empty track header for playback as is often customary to avoid core spiking issues, then audio is sounding more than one full second later then VEP is processing things, so the VEP meters are out of sync with audio, by at least 1sec. This is most likely a LogicPro bug of some kind, Cubase works normally and even LogicPro works normally if you select one of the instrument tracks into Live mode prior to playback, but other problems can come along with that.
If you want to try to run your own test, you might be wondering how I gathered the CPU usage. I used the following unix terminal command:
iostat -w 3 -I -c 60
to gather avg cpu every 3 seconds for 3 minutes. Make sure you start it at exactly the same point of the cue as it plays back.
iostat -w 3 -I -c 60
This could just be the usual USB crap (I have to reinsert dongles every once in a while, although I don't think that's happened since I consolidated everything from about six dongles down to two).
But if not, definitely let support@VSL.com know. There was an issue early on that they fixed.
Just curious, do you notice a difference in performance with different screen resolutions? I have a very similar machine to yours with a Radeon RX560, and I haven't noticed anything.
It takes about 4/5 of a second for Logic to switch screensets, regardless of whether the window configurations span two monitors or not.
nearly every day I am getting a LOT of elicenser problems, especially when I switch back and forth between LogicPro, Cubase and VEP. I shouldn't have to reinsert the dongle and its in the back of my machine where its safer, but also less convenient. The problem in my opinion is related to syncronsoft caching. I am going to wait for the dust to settle on VEP7 before posing lots of questions about this, but in a few weeks I plan to do that.
I did extensive testing last week on different display modes. On Sierra and probably High Sierra, yes VEP7 is using substantially more CPU when HiDPI settings are used. Actually its using substantially more just to display the GUI and double that if HiDPI is on. VSL provided me several different test builds to try different things. Nothing has worked so far. However after I upgraded to Mojave all of those GUI related issues went away. In fact in the process of doing all that Martin found some ways to improve GUI performance even more, but only on Mojave. So running VEP7 under Mojave out-performs VEP6 on every count, including big screens sizes and HiDPI too. However, older versions of OSX are going to struggle a bit unless/until they figure out a workaround.
Older versions of OSX are running VEP7 less performantly then VEP6 by all the tests I did, when the VEP gui is active and especially so when HiDPI mode is active. Sierra and probably High Sierra will get best results either using VEP6, or else avoid using HiDPI and avoid having the VEP window open. For now.
Mojave also bench marked 20% faster on my mac with geekbench, compared to Sierra...could have something to do with the GPU and metal assistance, no idea.
Dewdman, I'd like to thank you for taking the time of making all these detailed analysis and sharing them with the community. It is fascinating
That makes sense, given that Mojave includes a firmware update for our machine.
well I went back to VEP6 and Sierra again on my machine after the firmware update to retest using an experimental build from VSL and it was not faster. The firmware is not making our machine faster. The firmware is mostly just so that we can boot from NVMe and APFS devices and stuff like that. The speed improvements are I believe due to Mojave's Metal integration combined with the way VEP7 is coded to take advantage of those Mojave features. The bummer is that these GUI related changes in VEP7 run slower on OSX prior to Mojave. But I have found Mojave very good and solid and snappy and like I said, I scored 20% better with GeekBench, so its all good, I even got my 32bit plugins to work finally. So as of now, no complaints, I'm liking it a lot. folks with older hardware that can't go to Mojave, that's another story, if it were me I'd stay on VEP5/6 until VSL announces they have a fix for older OSX, or be prepared for some extra CPU overhead.
I stand corrected...figured it out. Tnx!
They have a graphic bug on my machine - the UIs, if they show up, are several inches away from where they're supposed to be.
That's in VE Pro - they actually do work right in Pro Tools 10, which only runs 32-bit plug-ins. However, PT 10 has its own menu-drawing graphic issue in anything later than... I think Yosemite.
I think it's also necessary to support graphics cards with Metal, because you have to go as far as High Sierra with the stock graphics card before putting in the [RX560 in my case].
Thank you so much for doing this!
And do we predict that ultimately with a stable vep 7 version Logic + VEP will outperfom Logic without VEP?
no I don't think so, Logic performs very well on its own. That is lowest CPU scenario I have tried so far, but I'm still messing around with DP and I plan to run Reaper through the same tests at some point.
But keep in mind there are operational advantages to using VEP, despite that you need a little more CPU overall then if you just use LogicPro alone. And Cubase is crippled without VEP! DP looks like it might be also a bit crippled without VEP, but I'm still working through how to optimize it, I'm not that expert at using DP, but its doing some weird stuff, even while idle, spinning the CPU in "realTime" mode, way more then the other DAW's. There must be a setting to stop that from happening but I have not found it yet, but basically I can get the DP+VEP performance almost as low as Logic+VEP. But DP alone, is not doing very well either, but it might be something about MirPro and ViPro that is not happy with DP...more later.....
Separate names with a comma.