Yeah, never noticed it before, but it says the Server is running. I’m beginning to think I may simply have a connection issue, and will go through the cables and connections tomorrow. Thanks for your help, too.
It’s been over a month already — are you ever going to fix it?
Maybe you want to open a proper support ticket by clicking here → Support and then Get Help. Let official support staff take a look.
My Rosetta test results (macOS 26, FiiO K11)
I have tested the Rosetta workaround as suggested to see whether it resolves the initialization issue.
System setup: MacBook Air M4 – macOS 26.1 (Sequoia), FiiO K11 (firmware v1.25), playback via CoreAudio USB directly from the same machine (not remote).
Procedure:
- Completely quit Roon
- Finder → Applications / Roon.app → right-click → Get Info
- Checked “Open using Rosetta”
- Launched Roon again and played music directly from this instance (not via Remote or ARC)
- Tested multiple tracks with changing sample rates
Result:
No improvement — the issue remains.
When switching sample rates, Roon still shows “Failed to initialize audio device.”
In macOS Audio MIDI Setup the K11 briefly appears as “0 in / 0 out,” after which reconnecting the DAC restores playback.
Thus, running Roon under Rosetta does not change the behaviour.
Qobuz plays flawlessly, so the root cause seems to lie deeper in macOS 26’s CoreAudio exclusive-mode handling, likely affecting all USB Audio Class 2.0 DACs, not just specific brands.
Hey all, thanks for patience. We are working on a solution to this problem.
1 Like
This problem has now existed for a long time, will it ever be fixed? Roon is completely useless as it is now.
1 Like
What’s happening?
· Other
How can we help?
· None of the above
Other options
· Other
Describe the issue
macOS 26 issue improved, but not resolved yet - device initialization error.
Describe your network setup
Local external SSD storage connected to MacMini M1, cat 8 direct cable to Roon Bridge on 2nd MacMini M1, with DAC connected via DDC over USB, followed by I2S (Denafrips both).
Been tracking this issue in the EA thread…Glad it’s being acknowledged and discussed in the main forum.
Workarounds are appreciated, but, I have to question why Swansian does not seem to exhibit this same issue? Exclusive mode works as it should, sample rate switching is intact, and the music flows freely. I’m using the same Schiit Yggdrasil USB 2.0-compliant DAC that I use with Roon.
Is anyone at Roon currently testing with the Tahoe “point 1” beta? Perhaps Apple has made alterations there which will be more favorable to Roon?
I don’t know what the answer is; I’m not a software engineer. All I know for sure is that Tahoe has been out for over a month and that I currently have other, paid music playback software which does not have the same problems as Roon does right now.
We await further testing.
Hi @Wouter_Kolkman,
Thank you for the update.
Could you please clarify what kind of issue you’re currently experiencing — is it related to sample rate switching or a device initialization error when starting the application?
This will help us better understand the behavior and investigate further.
Device initialization - happens when changing albums.
What’s happening?
· Other – My issue isn’t listed above
Describe the issue
I have a Denon PMA-a110 connected to a Mac mini Roon server. Recently Roon would give an error "Lost control of the audio device" when it tries to change the sampling rate of the signal. It will generally be able to the first and/or second time but then. it will give an error and the amp display will give an "unlocked" message. It worked fine before.
Describe your network setup
Denon PMA-a110 linked via usb to a Mac mini server
I just upgraded my Roon Server (MacBook Air M4) to Mac OS 26.1. I can confirm with certainty that this sample rate change/device initialization issue remains unresolved!
Vadim - same issue on device initialization (TT2 Chord DAC via USBC). Just upgraded my Roon server laptop (MacBook Pro M1) to MacOs26.1 - still same problem.
When switching bit rates and then sometime randomly, error pops up. Need to unplug/replug in the TT2 and then can play that one song.
I thought Roon said that the new MacOS 26.1 should fix this, but alas, not the case.
1 Like
The “point 1” update is out and the issue persists. Drats
1 Like
After updating my 2024 M3 Mac to Tahoe, I encountered the same issues everyone else faced, but I couldn’t stand it anymore and reverted back to Sequoia 15.7.1. Now Roon works smoothly again as it always has.
1 Like
It works perfectly fine with the Qobuz app on macOS Tahoe, i.e., auto sample rate switching no problem, so I am curious what particular issue that causes problems for the Roon team?
Just updated my Macmini M1 to macOS 26.1. Same problems. Either “failed to initialise” or “lost control”. Workaround is to upsample/downsample to a single rate - I chose 96khz as more recent releases seem to be 96/24. JRiver works fine. Audirvāna works fine. Roon doesn’t. It’s been weeks now. Not really acceptable.
1 Like
I’m considering the same strategy, as the length of time for this fix has become ridiculous. How long did that take you to revert and did anything break in the process?
2 Likes
Initially, I was hoping the issues would resolve themselves, but I felt it was a deep-rooted problem with the OS, so I decided to downgrade. For me, being able to use Roon comfortably is more important than running the latest OS.
Since I hadn’t taken a Time Machine backup, the downgrade process took about 3-4 hours, including backing up necessary files and performing a clean install of Sequoia. I explained my situation to ChatGPT, and it guided me through the appropriate steps, so I didn’t get too lost.
4 Likes