azeteg
Active Member
Please send an email to [email protected] - someone will help you out asap.I just did it now but no change...
Please send an email to [email protected] - someone will help you out asap.I just did it now but no change...
Ya, I got that part. If I understand correctly though, wouldn't I be able to run VEP 5 if I loaded it up instead, and therefore run 32 bit Plug ins as long as I didn't save the metaframe in 7?
Please send an email to [email protected] - someone will help you out asap.
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?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.
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?
iostat -w 3 -I -c 60
VEP7 is giving me more fits about elicenser problems then I remember from VEP6, but otherwise is very smooth on Mojave so far.
- Test was performed with both application windows showing at 4k native resolution (see image below)
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.
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.
I stand corrected...figured it out. Tnx!This is incorrect. Our sample libraries can be installed to any location.
I even got my 32bit plugins to work finally
The firmware is mostly just so that we can boot from NVMe and APFS devices and stuff like that.
More Performance Test results with VEP7
This was mainly to compare Cubase vs LogicPro and DP, both with and without VEP7.
Test Configuration
Results
- MacPro 5,1 12 cores x 3.33ghz, 128gb ram, OSX 10.14.5 (Mojave)
- LogicPro 10.4.4
- Cubase 10.0.20
- DP10.01
- VEP 7.0.826
- 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.
Summary
Notes
- LogicPro is able to play the project without VEP with the greatest efficiency, using 25% average CPU usage.
- LogicPro+VEP, same tracks, instruments and FX with 34% average CPU
- Cubase+VEP can play same tracks at 49% average cpu usage.
- DP+VEP can do it at around 45% avg cpu, but I'm not sure if there is some config I can do to make it better.
- Cubase ASIOGuard did not improve performance, in fact better performance happened with ASIOGuard off.
- Cubase alone cannot play the project with or without ASIO Guard.
- I haven't done DP alone yet, will update here if I do.
- 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 very close to what DP+VEP can do.
- 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.
- VEP7 is giving me more fits about elicenser problems then I remember from VEP6, but otherwise is very smooth on Mojave so far.
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].