194,444 users have contributed to 42,922 threads and 257,971 posts.
In the past 24 hours, we have 6 new thread(s), 15 new post(s) and 74 new user(s).
I am having trouble with my Izotope Ozone 8 plugins. It seems like they crash the initial vst search and all other vst after them becomes "unknown".
Is this a known bug?
Not a known bug. Which operating system are you on, and which exact version of Ozone is this?
I know that the iZoptope VST plugins can be incredibly slow in scanning - since they appear to completely tear down and setup everything for each channel configuration.
Izotope Ozone 8.02a which should be newest one.
It says it is failing the verification and then it just stops and crash.
I will put the izotope .dll's in another folder and do a rescan and should be ok. I usually not use them outside the final master and in cubase anyway.
That sounds like quite a bit of activity.
Could you send me a screenshot of your VEPro in action, so I can assess what activity is going on?
Will do so today. Just the ET Tutorial from VSL website...no extra FX plugins (shrug). But I will make some screenshots today...
I loaded the biggest project I have ever made, originally done for VE6 and it loaded perfectly in 7, plays back just as well with that great new feature of being able to instantly see the articulations on the mixer (very useful! - previously they are somewhat "buried" within the VI instances). Also the range of new EQ/instrument settings available is great to have. There is no increase at all in CPU useage on my system.
I had to roll back to 6 due to instability and a bug with automation recall, so I used 7 and 6 side by side as it were. Pretty certain 7 in my use case is more efficient (I was using Nuendo with ASIO Guard at medium, 6 had to go to high. Day before I was still using the Cubase 10 trial.)
I'm also seeing the CPU issue when the GUI for an active instance is displayed. I had this issue on 6 as well and opened a ticket (Case 297541) about the problem.
My steps to reliabliy recreate the issue are below. It makes sense there would be additional CPU usage for drawing the meter but from my observation using the test outline below jumping from ~20% to ~100% showing a single meter seems like something else could be going on as well.
If it's helpful (or for someone to point out that I'm doing something wrong) here is a quick screen recording creating the issue I see. Apoligies in advance for the terrible chord progression
https://www.dropbox.com/s/tps64ryyeicjz80/Cubase-VEP7-CPU.mp4?dl=0
Here's a dumb question;
Will my Special Editions still work on VEP7 as it is fully functional in VEP6? What about my Slate Drums (SSD5) that are 64 bit? UVI (latest) ??
I'm a little wary of the Synchron Player. I've searched the site but everything seems to point the user towards upgrading and buy new Synchron Strings, etc. Would anyone care to weigh-in with their knowledge?
Please and thank you...
My SE Percussion works in VEP 7, I doubt there is anything VSL which won't. One user reported VEP 7 won't see UVI Workstation.
I like Synchron Stage mixing interface and the sound. The paradigm is a little different as to control.
The player itself is fine afaict.
One user reported VEP 7 won't see UVI Workstation.
Just to say that's resolved in the next build (my understanding is it was not an issue specific to the UVI Workstation, but a general problem scanning certain libraries on certain setups).
Nothng is affected re any VSL libraries, those will load as normal in VI Player or VI Pro, so no worries on that score.
If it's helpful (or for someone to point out that I'm doing something wrong) here is a quick screen recording creating the issue I see. Apoligies in advance for the terrible chord progression
https://www.dropbox.com/s/tps64ryyeicjz80/Cubase-VEP7-CPU.mp4?dl=0
Today I am noticeing that even if nothing is playing.. If I hide the VEP window, showing the DP window...CPU is pretty idle at 3%. Show the VEP window and hide the DP window...CPU usage jumps to 15% and stays that way..nothing is playing.
VEP is clearly doing something with the GUI that is using up 15% when nothing is happening. I hope you can get to the bottom of it.
Today I installed the update from this morning and performance is horrible, worse then yesterday, can't even play from Cubase at all without dropouts, DP only slightly better, Logic still plays it because Logic is somehow more efficient. But all three exhibit this problem of the extra 10-20% cpu when VEP window is showing.
Civilization 3 and Noiseboyuk,
I've found that in my VEP6 setups that I converted to VEP7, I had to go in and carefully reselect/replace plugins/instruments like UVI and Slate Drums to the AU versions to make everything work right. _then you have to save the VEP instances before you save the Server Project, which will be new.
As with VSL/VEP6, on a new install I first review and refresh the sample libraries via Directory Manager.
I then move onto opening the non-server versions of the VEP (now 7) bundle so that the plugins all get rescanned and any buffers, sample rates, numbre of midi channels, and nuber of audio i/o are set according to my preferences.
Another thing with a lot of 3rd party VI's is that you need to open the library settings within those plugins as well, making sure everything is just so. There have been times when I build a new setup and I forget to do all of that gruntwork, especially dreading Waves and UAD plugin rescans. I just try to get it in there while everything is fresh. Something scripted would be a much better way.
Dewdman42,
Thanks for posting that. Although the CPU % looks high, the total load in the graph window is still low. On my Steinway, I maxxed-out th polyphony, but I'm only using a stereo set and no reverb plugin. See attachment.
Something I did notice and I'd suggest is to turn off your Wi-Fi and use ethernet if possible. Same with Bluetooth. Disable any attached webcam. The Synchron stuff is great, but it's a CPU hog. You're not doing anything wrong. Try a simpler patch like the stereo "recording" Decca Tree and disable a couple of the room mic channels.
Limit all DSP inside of the Synchron Player like reverb: Use a "master reverb" that works with the whole mix and it should gel fine. If you have an external reverb unit, use that just for monitoring and only use the fancy convolution ones for when your printing final FX tracks and aren't concerned with latency, etc. YMMV.
I hope this helps or gives you a better idea. Cheers!
In that example I was using logicpro and 100 no nonnsynth tracks I would expect it to be. The same project in cubase is running the cpu cores all into the red 95%, and it’s not a heavy processing project. The main point is that the vep gui is adding 10-20% of cpu usage when it’s showing, even when not playing anything. I don’t think that is normal or acceptable.
Yep, I agree and I think that the latest DAW and Plugin updates are way too GPU intensive. Needlessly intensive, as in without benefit but for more complex color gradients in the UI. Especially any complex metering within plugins such as Waves' Emo D5 Compressor that causes observable usage spikes on my RX-580 card. I've often wondered about limiting the color gamut when using a DAW. Certainly the (thousands) web safe color scheme would be enough for everything. DAWs and VIs don't need to tax the GPU as if it were DaVinci Resolve.
Can you tried running the Synchron Pianos on a slave machine?
FWIW, I've never gotten audio sends/returns to work for a remote FX box. I think the only reason my Pro Tools is stable and still has just over 3ms of roundtrip latency is that the omly plugins I'm using are 3 instances of VEP7.
For this I blame Avid: The Adobe of the recording world. My machine is a Z370/i7 8700K (6-cores) at 4.8GHz, 64GB RAM, 6 internal SATA SSDs, a 500GB PCIe M2 SSD just for samples, an dGPU AMD RX-580 with 8GB GDRAM, Thunderbolt UAD Apollo 8 Quad: Geek Bench score of 6335 and 28325. Cinebench CPU score of 1457, MP ratio: 7.11x
What I've figured is this, and it drove an extra upgrade decision: If you have one or more machines that capable and available to use as slaves, an extra VEP7 license is way cheaper than building, let alone buying a new monster PC or Mac.
On my PC (Windows 10), VEP 7 keeps crashing and crashing and crashing when trying to open older server projects from VEP 6. No crash dumps are being created either. Even when simply creating and importing saved instances, it's crashing. Seems very buggy for an initial release. VEP 6 was a lot more stable on initial release. I've tried uninstalling and re-installing VEP 7 and the same things keep happening frustratingly.
Opening projects and saving projects appears to be a lot slower than VEP 6 too.
Any help would be greatly appreciated,
