You are not logged in. Please login or register.
RME User Forum → DIGICheck → Digicheck 5.2 OS X still 95% CPU
I was wondering why the fans on my MBP C2D 2.4 gHz were so loud: it turns out Digicheck 5.2 is still using over 94% of the CPU according to Activity Monitor. This seems a tad excessive. I'm on OS X 10.5.7.
FYI...
I have the same problem when using Totaliser. A restart of Digicheck helps for a while :roll
MBP 2.6 GHz, OS X 10.5.7 Digicheck 0.53 (FFUC/FF800)
Regards
Martin
digicheck 0.53? where did you get it?
I uploaded a test version which might fix the high CPU load issue. Please check:
https://archiv.rme-audio.de/download/dc_mac_test.zip
Thank you! It's sitting around 25-30% CPU. Still a tad high but much better than before.
Would be nice if Merlin could confirm this fix too...
Hi everybody,
it's getting a bit better here on an Imac 2.4, 4 Gb ram, OsX 10.4.11.
Just Totalyser window open, Medium size, Spec. An.: 30 bands, 0 ms rise-time, 1,8 s release, 50 dB range, bar mode, default settings for L.M and Gonio. CPU: around 60%
Used to be around 83%, so, it seems you're walking the right path.
Increasing Spec. An. rise time: CPU drops to 50%
Totalyser, activated audio processing, but no actual incoming audio: CPU 30%, used to sit at 50% on v. 0.52.
This is just a quick test I made regarding DC's behaviour on Tiger, looks like other guys are getting better results on Leopard....
I'm sure you guys at RME will succeed in making Totalyser a lighter, smoother app!!!
Well, what we try to fix here is the stone-old denormalizer problem of the Intel CPU. The test is easy. Use the Spectral Analyzer with full blown music, so every band is active. Note the CPU load. Turn off the input signal to digital zero and wait until all bars are empty. Note the CPU load again. If it is higher then there is still a small denormalizer problem left. We can fix this if we get confirmation, we did the same on Windows before. This kind of error does not happen on all machines (and of course not on ours), but it clearly exists.
Would be nice if Merlin could confirm this fix too...
:-)
On my own Macbook Digicheck now also is using about 25 - 30% CPU with Totaliser every time, thank you!
There is a Macbook in Studio: 0.53 was running and the aktually testversion chrashes.
I'm not able to open any window. I installed the previous version and every thing seems to be okay again.
Macbook in studio: early 2008
my own: the last model without unibody, both with Os X 10.57
bmdaugherty: the only difference between 0.52 and 0.53 seems to be the compatibility to Fireface UC.
I?m a beta Tester of this stuff.
regards
Martin
Hi,
DigiCheck 0.52, VLC player, loopback in Fireface mixer with SPDIF
DC / Preferences... Nominal update time 15 ms
Totalyser : about 14 - 16 % CPU
Spectral Analyser : about 8 - 10 % CPU
MBP 2.5 GHz, 4 GB, (early 2008) OSX 10.5.7
good ?
regards S-EH
This is what we see in our tests, but did you check the test version?
Yes I did now :-)
Totalyser : about 14 - 15,5 % CPU
Spectral Analyser : about 8,0 - 8,7 % CPU
so not a big differens on my MBP !
regards S-EH
Thanks. Still a riddle to us why only some machines show this problem.
Hi,
test results: Totalmix loopback through SPL Vitalzer
Totalyser CPU, full blown music: 60% (see my previous post)
Everything turned to digital 0: CPU slooooowly reaches 30%
iMac-OSX 10.4.11, 2.4 gHz, 4 Gb ram
...but still a trustful fan...waiting...
Regards
More optimization for less CPU load:
https://archiv.rme-audio.de/download/di … 54_mac.zip
RME User Forum → DIGICheck → Digicheck 5.2 OS X still 95% CPU
Powered by PunBB, supported by Informer Technologies, Inc.