RE: Audio Problems with FireFace
April 01, 06 3:56 PM
(permalink)
Okay, here's the update: I found a way to resolve the issue. I've pasted my post from the RME newsgroup below.
Alright - here's what I found:
If I start SONAR 5, and multiprocessor support is enabled, I get crackling in the FireFace, and the CPU meter doesn't actually reflect multiprocessing. If I disable multiprocessor support, the crackling goes away, and the CPU meter stays where it was. If I re-enable multiprocessor support, now the CPU usage drops to half of what it was, and the audio stays clean.
Most ofthe time the audio will then stay clean until reboot even if I close and re-launch SONAR; but there are a couple of things I can do in Windows that will re-trigger the problem before a reboot. It seems like it might be a Windows issue, but I haven't totally pinned it down yet. In any event, at least I know how to stop the crackling when it occurs, and I can get the FireFace down to 128-sample ASIO buffers with a high track playback count and 16 tracks recording with input monitoring.
Mr. moon - have you tried re-enabling multiprocessor support in SONAR after disabling it? I wonder if there's anything similar about our systems that are causing Windows or other applications to somehow mis-handle multiprocessing under certain circumstances.
I don't know if this is specifically a SONAR problem. I'm only really seeing the issue in SONAR, but it seems like it might actually be Windows triggering it. I'm going to email Ron Kuper about it in case there's anything Cakewalk can do about it.