Weird Audio Crackling in Logic Pro - 2 Threads Maxed Out

[rm5]

So of course this has to happen at the worst possible time—while working on a client project! So out of the blue, I play back the project (which is almost done—I'm at the post-processing/mixing phase), and I get the sense that the audio driver is about to crash... and then there's weird crackling, which is of course indicative of such an issue. I opened up the performance meter and I noticed that 2 threads were completely maxed out. I tried lowering the thread count from 12 to 8, which only made it worse—and I also tried raising the I/O buffer size from 128 to 256 samples, which only fixed it somewhat (i.e. still a bit of crackling, but not as bad as with 128). Because of latency issues, I do not want to go any higher than 256. This is on my 5,1 Mac Pro with a 6-core E5645, 32 GB of RAM, etc. etc. (see sig.) I'm tempted to just copy the project file over to my M1 and finish working on there, and have to deal with intense swapping, etc.. It's absolutely unacceptable for this to be happening on a tight deadline (of tonight). The project is a moderately big orchestral production with 34 tracks, primarily using the Berlin Orchestra and Ferrum sample libraries, among some others.

Any ideas? I need this fixed ASAP. I don't mean to be harsh, but if I don't find a fix in the next hour, I'm switching over to my laptop... I just can't be having issues right now.

EDIT: Attached screenshot of issue

EDIT #2 - after some further testing, I should add:

• the crackling happens especially when the big hit happens at measure 35.
• Muting tracks does absolutely nothing to fix the issue.
• I also tried rebooting, which also didn't fix it.

 

[nollimac]

Marked as "resolved" because it's too late to fix anything; I had to export the final delivery so it wouldn't be late. THIS IS STILL AN ISSUE THOUGH that I'd appreciate help with for future projects. I've got plenty more projects coming, so...

So of course this has to happen at the worst possible time—while working on a client project! So out of the blue, I play back the project (which is almost done—I'm at the post-processing/mixing phase), and I get the sense that the audio driver is about to crash... and then there's weird crackling, which is of course indicative of such an issue. I opened up the performance meter and I noticed that 2 threads were completely maxed out. I tried lowering the thread count from 12 to 8, which only made it worse—and I also tried raising the I/O buffer size from 128 to 256 samples, which only fixed it somewhat (i.e. still a bit of crackling, but not as bad as with 128). Because of latency issues, I do not want to go any higher than 256. This is on my 5,1 Mac Pro with a 6-core E5645, 32 GB of RAM, etc. etc. (see sig.) I'm tempted to just copy the project file over to my M1 and finish working on there, and have to deal with intense swapping, etc.. It's absolutely unacceptable for this to be happening on a tight deadline (of tonight). The project is a moderately big orchestral production with 34 tracks, primarily using the Berlin Orchestra and Ferrum sample libraries, among some others.

Any ideas? I need this fixed ASAP. I don't mean to be harsh, but if I don't find a fix in the next hour, I'm switching over to my laptop... I just can't be having issues right now.

EDIT: Attached screenshot of issue

EDIT #2 - after some further testing, I should add:

• the crackling happens especially when the big hit happens at measure 35.
• Muting tracks does absolutely nothing to fix the issue.
• I also tried rebooting, which also didn't fix it.

View attachment 2183445

You should not have marked it "resolved."

 

[rm5]

You should not have marked it "resolved."

Fair enough. I'll "unmark" it then and remove the heading.

I'm just on my M1 for the time being.

 

[MrScratchHook]

Fair enough. I'll "unmark" it then and remove the heading.

I'm just on my M1 for the time being.

5,1 Mac Pro with a 6-core. "E5645" a.k.a (2.4) is the problem, especially with large amounts virtual instruments on lower buffer sizes. if you want to keep this machine you should install x5690(3.46) and max the ram to 64. you should be better at that point. not problem free just better off.

 

[rm5]

5,1 Mac Pro with a 6-core. "E5645" a.k.a (2.4) is the problem, especially with large amounts virtual instruments on lower buffer sizes. if you want to keep this machine you should install x5690(3.46) and max the ram to 64. you should be better at that point. not problem free just better off.

That's precisely what I thought the problem was. However, at this point, to be brutally honest, it's not worth the money IMO to upgrade it. I have more important things to be spending money on right now. The thing's already out of support, and other stuff like AirDrop, Find My, WiFi in general, and VMWare just do NOT work, and they won't work even after an upgrade. Also, I notice you have a 12 core with 2 X5690s, but doing that upgrade would require me to purchase another CPU tray, which I'm also not going to do. Sorry to be so stubborn, but I just don't think it's worth it. I have always been under the FALSE ASSUMPTION that more cores = better playback, whereas in reality, more cores + faster clock = better playback.

Also, 32 GB of RAM hasn't been an issue running these productions, but yes, 64 GB would be nice. Using my M1 with 16 GB of RAM at the moment, which is a huge limitation and I hit swap pretty quick, but at least it works better playback-wise.

Thanks for the help!

 

[MrScratchHook]

That's precisely what I thought the problem was. However, at this point, to be brutally honest, it's not worth the money IMO to upgrade it. I have more important things to be spending money on right now. The thing's already out of support, and other stuff like AirDrop, Find My, WiFi in general, and VMWare just do NOT work, and they won't work even after an upgrade. Also, I notice you have a 12 core with 2 X5690s, but doing that upgrade would require me to purchase another CPU tray, which I'm also not going to do. Sorry to be so stubborn, but I just don't think it's worth it. I have always been under the FALSE ASSUMPTION that more cores = better playback, whereas in reality, more cores + faster clock = better playback.

Also, 32 GB of RAM hasn't been an issue running these productions, but yes, 64 GB would be nice. Using my M1 with 16 GB of RAM at the moment, which is a huge limitation and I hit swap pretty quick, but at least it works better playback-wise.

Thanks for the help!

even if you keep the same ram, a x5690 only cost about $50/60 and its definitely worth the upgrade. you dont need a dual tray. the single is good enough

 

[rm5]

even if you keep the same ram, a x5690 only cost about $50/60 and its definitely worth the upgrade. you dont need a dual tray. the single is good enough

Well then I might actually consider it—I didn't realize the X5690s were that cheap! Last time I looked they were almost triple the price, but that was several years ago.

 

[MrScratchHook]

Well then I might actually consider it—I didn't realize the X5690s were that cheap! Last time I looked they were almost triple the price, but that was several years ago.

yup, they dropped alot....

Intel Xeon X5690 12MB 3.46 GHz Processor | eBay

Find many great new & used options and get the best deals for Intel Xeon X5690 12MB 3.46 GHz Processor at the best online prices at eBay! Free shipping for many products!

www.ebay.com