*Strange Behaviour in 4.6 Thread*

[imdrecordings]

Anyone seeing anything weird happening after this new update?

Samplitude V9 is now seeing a bunch of Native CPU Munching... :?

I threw in 3- Helios69 EQs (wich sound great by the way). Along with a 33609 & 2-1073s and my cpu jumped from 7-10% to 34%....

Tried saving and reloading.. same thing happend upon load up. I then disabled all Native based plugs and the Native CPU was still at 34%... :?

Tried the old Disable/Enable on the UA meter... nothing

Disablled all UADs and rebuilt with out the Helios69 plugs.. No CPU munching..

Weird.. :|

Feel free to post any weird findings you come across.

I'm going to work on recreating the munching.... track this bug down !!!!

 

[billybk1]

I have not noticed much difference in native CPU usage when using the latest v4.6 update with REAPER v1.832. In fact, it seems I am using even less than before, which was already wickedly low.
I added (3) Helios 69 EQ's to an exisiting 30 track/6 bus project @ 24/44 for a total of (24 PPI's) @ 91% total DSP usage across (4) cards. Total added native CPU usage averaged about 3.9% (about .16% native CPU per plugin). Total project CPU usage was 10%-17%, but native CPU usage attributed to the 24 PPI's was below 4%.
I am not sure if this lower native CPU is due to the v4.6 UAD-1 update or the latest REAPER 1.832 update that I just installed. Previously, I would average about 5% total native CPU using (24 PPI's) in that same project.

Project latency is 1024 samples, BTW.

 

[imdrecordings]

ok... I found it!!!
If you use the 33609 in SAM V9 and not in Hybrid mode... you get massive munching... HUGE MUNCHING!!!