Intermittent Playback on MacBook Pro during High CPU Usage (ref#0DJJF9)

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

The music will be playing through my DAC or direct to my powered monitors from my Mac. The suddenly the music playback becomes intermittent and eventually no sound is heard. However, playback in Roon is still running. Every now and again the sound returns where the playback is running. This appears to happen when my processor is running above 80% and RAM at 60%. I have a MacBook Pro 2018 i7 RAM 16 GB.

Describe your network setup

modem is ISP installed, I believe its a Fiberhome kit, my router is a Linksys 4500 Velop. I am fully wired, I don't use wi-fi. My ISP speed is 550mb. I connect my Mac to an iFi uno, which I know works well. The problem began a few weeks after I had purchased the iFi and all was ok.

Hi @Christian_Coleman-Jo,

Thank you for your post. We’ve pulled diagnostic logging to see if we can pinpoint the events you’re describing - while we don’t see audio stopping due to processing load, logs do show sample loss accumulating in the network when the iFi Zone is in use.

At times, this packet loss accumulates in sufficient volume to overwhelm and tear the audio stream down completely; the Zone can usually re-request missing samples in time to buffer them, but not when samples drop out sequentially.

In a fully wired environment, this is most likely due to a) managed network components like a router or a switch holding up packets or b) bandwidth allocation issues.

If you have no other network hardware outside the Lyksys router, please verify that multicast forwarding is turned on in the administration page. If you do have additional network hardware, particularly managed components, then list them here.

The dropouts we’ve observed dont’ fully match your description - in the logged examples we’ve seen from your RoonServer diagnostics, the audio stream stops completely, most likely presenting as an error int he Roon UI. Do you have an approximate timestamp of when System Output on the affected Mac continued to play, but you heard no actual audio?

Hi Connor,

Thanks for the analysis. My network setup consists of the ISP modem wired to the Linksys router, the wired to an unmanaged Tplink switch, to a an ethernet to USB-C adapter to a hub then to the Mac. The iFi is connected via a USB-C to USB-A adapter.

Since I don’t really need the Linksys, I’ve taken it out of the link and now how ethernet straight to the switch and the same connection thereafter.

Unfortunately, i don’t have a timestamp for when the sound become intermittent or stops altogether, but I will look out for it now. In the meantime, I’ll be testing the system without the Linksys.

Could the iFi be causing the problem?

Many thank,
Christian

Hey @Christian_Coleman-Jo,

Thanks for the follow-up! Since some time has passed, we wanted to check in and see how playback has been performing? Did you have any dropouts in the last few days?

We’ll be on standby for your reply, thank you! :pray:

Hi Benjamin,

Unfortunately, I have been getting dropouts every time I play tracks on Roon. But I have identified that the dropouts are prevalent when CPU usage exceeds 90%, after which point playback sound dropouts altogether. I think that the UI was mentioned in your previous post and I think that certainly the UI in my Mac is an issue. I think that the Roon server requires a dedicated unit; sharing the server with other resource-demanding apps may not be ideal.

I’d be grateful for any comments you may have, other than changing my Mac completely.

Many thanks,
Christian

Hi Benjamin,

I’d like to provide do my bit by adding to this thread what I believe is causing the dropouts. I have been testing endlessly with various variables such as pausing non-system processes unnecessary for Roon to run smoothly; changing the server location to a much newer MacBook Pro with an Apple Silicon M2 chip (my personal on has an Intel i7 chip) with the iFi uno DAC attached and finally, I tested Roon back in my Mac but this time with an app that tames CPU processes on-demand (CPU Tamer).

I insist that the issue is related to high CPU load. I’ve been stuck to my screen monitoring at what points in the playback of any tune the dropouts occur. First conclusion is that there is no specific reason for the CPU load to increase dramatically from say 4% to 97% when no other applications are running. However, without a shadow of a doubt, when the CPU load exceed anywhere between 75% and 80% dropouts occur. No dropouts occur below 75% at all.

The tests I performed on the newer MacBook Pro proved my hypothesis. First, the CPU load did not increase spontaneously from say 5% to 95% - it remained stable all along the tests and no dropouts at all occurred after several hours of playback. Initially, I was convinced that my DAC was faulty, but I disproved that when testing with the M2 chipset Mac.

I used several kinds of cables so as to discard a connectivity issue. Nothing there.

The final test, with the CPU Tamer app, proved my suspicion since Roon worked well with the M2 Mac. My Intel chip Mac is the cause. Lo and behold, displaying the Tamer app, the all-too-common issue of the kernel_task process, the cause of most CPU high load issues, popped up at the top of the high-CPU usage percentage and right below it Roon Server.

The app allows the user to manipulate how each process behaves individually. For example, if I detect that the contacts process is acting up, I can tell the app to stop running that process immediately, run it as a low priority process or limit its activity if it exceeds a user-defined percentage.

I played around with various non-essential processes that were interfering with the CPU load and managed to control the sudden drastic increase in CPU load significantly. The good new is that the dropouts can be controlled but outside Roon, DAC or any other kit attached.

The bad news is that, as I understand it, if after resetting the Mac’s SMC and NVRAM the famous kernel_task process still forces high CPU load and the fans run at 100% continuously, it may well be time to replace the Mac (of course that is what Apple says).

Conclusion: nothing is wrong with Roon’s operation, neither is my overall hardware causing or adding to the issue. Plain and simple, even with a top-notch i7 or i9 Intel Mac, there is a propensity (particularly if it 5 years or older, which I’d imagine most are) for the system processes to become neurotic and operate haphazardly.

My Mac needs to be replaced, without a shadow of a doubt. But in the meantime, the inoffensive CPU Tamer app does the trick, at least I am in control of the dropouts not the other way around.

As a layman in this tech things, I would suggest that Roon look into this and if I’m correct, an article in your knowledge base might help users who are scratching their heads in perplexity wondering why an i7 or i9 Intel chip Mac with 16GB RAM doesn’t perform as it should.

I hope this drop in the bucket helps.

Christian

Hey @Christian_Coleman-Jo,

You have my sincerest apologies for the delay in following up!

You’ve done some incredible troubleshooting and detective work here! I wanted to let you know that although we don’t have any additional tests or troubleshooting steps for you to take, we’ll be taking your findings directly to our development team for further analysis and discussion.

We believe you’re correct in that there might not be any specific issues within Roon’s operation - but there might be room for some improvements in Roon’s behavior when these system occurrences do pop up.

I’ll go ahead and mark your response as a solution for now - if and when there is any additional information or follow-up action from our team, I’ll most definitely let you know! :+1:

Thanks again for all your hard work here! :raised_hands:

Hi Benjamin,

This is my passion, so there is no need to thank me, quite the contrary, I’m glad that it can be used to help others. However, tongue in cheek, a one-time free month would be a great prize!!!

All the best,
Christian

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.