Is the affected network Zone connected with Ethernet or WiFi?
· Ethernet
Does the issue affect all file formats?
· The issue affects *multiple/all* file formats.
Does the issue happen with local library music, streaming service music, or both?
· *Both streaming and local* *library* music are affected.
Do you encounter any playback errors with the "System Output" Zone?
· I don't have a System Output available, but I'd like to keep troubleshooting
How is the affected Zone connected to your RoonServer machine?
· Network - Ethernet
Which network audio protocol is the Zone using with Roon?
· Linn
Since this is a Linn Zone, have you ensured your devices are using the same Linn playback subnet?
· I've verified the subnet and the Zone still won't function.
Does the device show up at all in Roon Settings -> Audio?
· Yes, it shows up there, but it isn't Enabled
Does the "Enable" button unlock the Zone?
· I can Enable the Zone, but the Zone disappears
Does the device play audio from another source when using the same connection?
· The device has no problems with another audio source
Have you checked that Roon is whitelisted in any firewalls?
· I've checked the firewall and the issue remains
If the device has multiple output options, do the other options work as expected?
· Multiple output types are affected
Is the device using the latest firmware as per the manufacturer?
· Firmware is up-to-date but the issue remains
Do you have an approximate timestamp of when the issue last occurred?
· 30 minutes ago
What are the make and model of the affected audio device(s) and the connection type?
· Linn Akurate DSM3 (Roon tested), Roon Core installed on MacMini M1, connected to router and streamer via Ethernet
Describe the issue
Roon starts, but stops intermittently. MacMini M1, connected to Linn Akurate DSM3 (Roon tested) via Ethernet, local files and Qobuz. Qobuz functions fine alone with streamer. Local files playable with HDMI connection to streamer. When Roon stops, there is no protocol I have found that consistently works to revive it.
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help in ensuring we gather the right information.
First, can you please reproduce the issue once more and note the track name and the time at which the error occurs? Then respond here with that time and track name, and I’ll make sure we review the diagnostics related to that timestamp.
Here is a screenshot with the requested playback info. Selected music, two songs played, then silence. It still shows the first song of the album playing.
Thank you for providing that screenshot and the exact playback details! We really appreciate your help in capturing this.
I have some good news for you. The exact behavior you experienced—where a Qobuz stream abruptly stops but the app remains stuck showing the track as “playing”—was actually traced back to a widespread infrastructural issue on Qobuz’s end, specifically regarding their Akamai content delivery servers.
Qobuz’s engineering team has since identified and fully resolved this problem. Because the fix was made on their servers, your playback should now be completely back to normal without any troubleshooting or updates needed on your part.
Please go ahead and dive back into your music! If you happen to encounter any further drops or hanging tracks, just drop a reply right here, and we will be happy to investigate further.
Thanks for following back up, and I’m sorry to hear you’re still having issues playing Qobuz content.
I’d be curious to see if testing a different DNS server may help you here.
We have seen users have a better experience in the past if they change their Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS. Can you please give this a try and let me know if it helps?
Hi Benjamin, This dropout happens with local files too. I’m not sure how to go about the changes you are suggesting. Probably won’t have time til the weekend anyhow. I use Verizon Fios, with their router and an Apple WiFi setup. The setup in question is hard wired with Cat 5 ethernet, controlled with phone, iPad, MacBook via WiFi. I have no problem with other systems in my home using Qobuz, Apple Music and Spotify. That leaves Roon on the main system.
From a fresh diagnostic report, we can now see that every playback dropout is caused by the same critical error:
Critical: [songcastdirect] [Linn Akurate DSM] AudioThread:
System.NullReferenceException: Object reference not set to an instance of an object.
at Sooloos.Broker.Transport.SongcastDirectZonePlayer.ScdClientConnection.AudioThread()
This crash occurs all across your logs, and it happens at the exact moment playback starts, the Linn connects via SongcastDirect, the audio thread initializes, and then immediately crashes with a null reference.
A few additional things to test while we bring this crash trace to our development team:
Enable Sample Rate Conversion in Roon DSP. The crashes happen across mixed formats, 16/44.1, 24/96, 24/88.2, 24/192. The track-boundary error appears most often when Roon has to negotiate a format change between consecutive tracks. Forcing a single fixed output rate removes that negotiation entirely.
In Roon: Access your endpoint → MUSE → Sample Rate Conversion → set to a fixed rate (try "Power of 2" or lock to 24/192). This makes every track hand off at the same format and may eliminate the null object condition.
I would also separately test out creating a test playlist of 10 tracks that are all the same format — e.g., all 16/44.1 FLAC from Qobuz, or all 24/96 local files. If it plays without crashing for an extended session, that confirms format changes at track boundaries are the trigger.
Try limiting your queue to fewer tracks (playing from a small playlist rather than a large shuffled library) to reduce the pre-buffering activity, let me know if this changes any behavior.
the MUSE function is too well hidden. Do you know the expression “too clever by half”? There should be clearly marked control buttons under setup. UI is very important. I’m a sign maker, and like things to be very clear. Roon control surface seems like 1980s Windows.
While the MUSE icon might not jump out immediately if you haven’t used it before, it is actually designed to be quickly accessible right from your active playback screen without needing to dig through the main setup menus!
Here is our Help Center article, which includes step-by-step screenshots showing exactly where to find it: DSP Engine - Accessing DSP Engine
To access it right now:
Click the Speaker/Volume icon in the bottom right corner of the Roon app.
In the pop-up, look for the MUSE icon (the squiggly line) right next to your Linn zone name and click it.
Once you have the MUSE window open, just toggle on Sample Rate Conversion and set it to Power of 2 (or lock it to a fixed rate like 24/192).
Locking this in will stop Roon from constantly negotiating sample rate changes with the Linn DAC between tracks. Let us know if this stabilizes your playback!
I spent a good part of Friday with Roon playing my playlist of Jazz Guitar Guys, and it played for many hours without a glitch. The sample rate leveling seems to do the trick.
