Help me understand Cubase AISO peaks

Post general topics related to Cubase Pro 8, Cubase Artist 8 and Cubase Elements 8 here.
Post Reply
JT3Jon
Member
Posts: 366
Joined: Thu Apr 07, 2011 9:16 am
Contact:

Help me understand Cubase AISO peaks

Post by JT3Jon » Tue Apr 26, 2016 10:54 pm

I need help understanding how to best utilize System resources while running Cubase. I've run a few tests with some interesting results.

Test 1: Load a single omnisphere multi (where its playing 8 patches at once + all its FX etc in stack Mode) and at a buffer size of 256, Multi processing on & AISO Guard on high. Result: AISO peaks. Whats weird is my CPU meter in activity monitor shows all CPU cores with tons of headroom & cubase using only 200% CPU (max is 100% x 24 for my cores + hyperthreading), but Cubase's Real-time peak meter is maxing out. I'm guess this has something to do with a single instrument being loaded on a single CPU, and once you max out that CPU you are done - but I dont get why I dont see a single core maxing out in activity monitor? Notice that 88% of my CPU is idle!!
01_1omni.png
1 omnisphere
(230.44 KiB) Not downloaded yet
Test 2: Spread out this same Omninsphere multi across 8 different omnispheres each playing one patch. Buffer still at 256, Multi processing on & AISO Guard on high. Result: AISO is no where near peaking, even though according to Activity monitor the same CPU is being use. (see picture 2)
02_8omni.png
8 omnispheres
(223.58 KiB) Not downloaded yet
Does this mean that Cubase only uses multiple processing if you are playing multiple instruments? Does this mean it is best in general to treat multi-channel instruments like Omnisphere, Kontakt, Halion, etc as individual instruments and load more instances with single patches vs less instances full of patches? That seems to be the conclusion I've hit with my tests, but would love to hear from other users.
Last edited by JT3Jon on Fri May 06, 2016 8:36 am, edited 1 time in total.
Cubase 9.5.41 OS10.12.6 MacPro 12-core 3.33Ghz, 64GB RAM, UA Apollo

roel
Member
Posts: 787
Joined: Wed Jun 27, 2012 2:20 pm
Contact:

Re: Help me understand Cubase AISO peaks

Post by roel » Wed Apr 27, 2016 11:55 am

The ASIO monitors shows if the audio signal reaches the soundcard in time, so if it's peaking it means that some audio chunks are not received in time, so the sound was interrupted. (audible or not)
If one of the cores is at it's max, then it is indeed plausible to have a ASIO peak in the very near future, because the core has trouble keeping up with the rest.

On the other hand, the things you are noticing are also correct i presume, but not as such directly related to ASIO peaks.
Yes, the more you spread your instruments over multiple dll's, the more options cubase has when doing the core handling. Most of the time this results in a far better general load overall (CPU).
When stacking is being done within a certain single vst, the entire package is handed over to cubase as one instrument. This can result in a heavier load on a single core or the cores that are reserved for processing that instrument.

As far as i understand, the internal settings of core handling within a vsti are not affecting the audio handling when running cubase. These settings are for standalone use (when the vsti has to do the core handling by itself).

But on the other hand, none of your cores are at max, so the peak is probably not related to the processer in this case.
When looking at the attachments you can clearly see that your video drivers are hanging. (on both pictures)
Imho the video driver (and the priority level it is giving) is interfering with your audio signal. If it has more priority at a certain moment then the audio signal, your chunks are waiting to be processed in a cue and what follows is that they are not processed in time, and the ASIO peak is nothing more then an indication of what has happened. Your audio chuncks arrived too late.

That this is not resulting in a peak when you have spread everything out over multiple ddl's is indeed a logical indication that this is indeed a more efficient way of processing, so every chunk still gets in time on it's arrival point. It's probably a very powerfull computer.
But that video driver is something you should be looking in to, since imho that is what is causing the underperformance.

Hope this helps a bit, but it is just an opinion on a forum.
kind regards,
R.
Cubase 10.5, vienna ensemble pro 5,
Master:laptop Clevo, P771zm, i7 4790S, 16 gig, 2xSSD samsung 840pro/evo, 2x Samsung SSD850 +touch screen
Slave: none, will probably never be replaced because latest processors are powerfull enough
Sound: Motu Ultralite MKIII (usb), Focusrite 18i20, behringer 16 ch mixer
control: Synergy, novation zero SL
vsti: Steinberg, East West, Vienna, Native Instruments, Spectrasonics and a lot of others
hardware: S760, CD3000xl, SY77, studiologic 990, alesis Q88,

User avatar
Grim
Grand Senior Member
Posts: 5064
Joined: Thu Jan 06, 2011 5:08 pm
Contact:

Re: Help me understand Cubase AISO peaks

Post by Grim » Wed Apr 27, 2016 1:17 pm

But on the other hand, none of your cores are at max, so the peak is probably not related to the processer in this case.
When looking at the attachments you can clearly see that your video drivers are hanging. (on both pictures)
Imho the video driver (and the priority level it is giving) is interfering with your audio signal.
Those are more specifically the Cubase video engine files.
Best bet if not running any video in Cubase is to rename or move these items out of the components folder.
I doubt that these hanging will have any effect on your audio tbh.
i7 5820k @3.7Ghz, 16Gb, W10Pro, Cubase 9.0x, Cubase 8.5.x, Audient iD22, Zoom UAC-2, Wavelab Elements 9.x, Nektar Impact GX61

Post Reply

Return to “General”

Who is online

Users browsing this forum: No registered users and 3 guests