"Failed to Initialize" when Switching Sample Rates on MacOS Tahoe [Ticket in]

Support
21

Good day @GSpot !

Thanks for sharing your logs.

We have reviewed them and can confirm that you are facing the same ongoing issue as many other customers. We already have an internal ticket open and hope to resolve the problem as soon as possible.

Stay tuned!

Regards.

22

Thank you. Do you have any estimate of when this will be resolved? Since my Library is a mixture of sample rates, this issue is quite impactful.

23

Just saw this…

Also, just saw this: “macOS 26.1 (beta): The first developer and public betas were seeded on September 22 and September 24, 2025, respectively.” Does the Roon team have access to the developer beta and if so, does this resolve the Audio Device Initialization issue?

24

Hi @GSpot,

We’re not able to comment on a timeline, but we’re making good progress on getting a fix release ready.

Thanks for your ongoing patience! :raising_hands:

2 Likes
25

Thank you. Do you think the fix will come from Roon or is a Mac OS update required to resolve the issue?

26

Hello @GSpot ,

We’re working on a fix from our end that will be publised with a release, but it is possible that future MacOS versions will have some additional changes to mitigate this issue as well.

27

Thank you… coincidentally, I was excited to see Mac OS 26.0.1 released a few minutes ago and just installed it. Interestingly, the first sample rate change from 16/44.1 to 24/96 transitioned flawlessly. However, upon subsequent sample rate changes, I received the same “Failed to initialize the Audio Device” error, followed by the “Roon Lost control of the Audio device” message.

Would you like for me to upload the latest Logs?

28

Thanks for the update @GSpot - we have everything we need for now, thank you!

We’ll be in touch with updates as they come. Thank you! :folded_hands:

29

Hi everyone,

Since announcements about the pending fix will be in the main tracking thread, we’re going to close/merge reports into that thread for housekeeping. We want to ensure everyone has access to the same information in the same place.

We’ll share more information from development as soon as it is available. Thank you all again for your patience.

1 Like
32

Hi everyone,

A fix for this issue is undergoing public testing in #earlyaccess. If you would like to migrate your server and remotes to Early Access for testing, please follow these instructions:

Please let us know here or in the #earlyaccess category if you are still encountering the “failed to initialize” error after switching sample rates when using a MacOS-based RAATServer instance.

We’ll watch closely for your responses.

1 Like
33

I tried the early access version and it still freezes and shows “failed to initialize audio device”. I reloaded the original version and will wait until production version releases.

34

I upgraded the Roon Server to version 2.56, but I still encountered the same “failed to initialize” issue.

2 Likes
35

Frustrated with the issue of lose DAC control after updated to MacOS 26. Found this thread and also installed the early access build 1566 for Mac. Still get the issue. You can see these in log:
10/09 22:44:09 Info: Alert: Transport: playback_error_endpoint_device_init_failed
10/09 22:44:54 Info: Alert: Transport: playback_error_endpoint_lost

36

Just throwing my experience into the hat. M1 mac mini, 0.1 Tahoe update, latest Roon EA build. Experiencing the same issue with bitrate switching and losing control of the audio device.

3 Likes
37

Same. All the same conditions and symptoms. Incidentally Audirvana does not have any of these issues playing via my Chord TT2 from MacBook Pro M1. It all started with MacOS26.

2 Likes
38

Its not good enough with the amount of money we pay that’s there no fix

1 Like
39

First, I haven’t received notification of an available update to v2.56 (I’m still on v2.55 Build 1559). But perhaps more importantly, my question to the Roon Support team is: If you believed this v2.56 update would solve the device initialization issue with Mac OS 26.0.1 (Tahoe) – which it apparently does not based on @Thummarat_Prathomsur’s report – how is it that your development and release testing seemingly indicated that it resolved the issue, yet it hasn’t?

I’ve been in the software business my entire career and this trial-and-error approach with your releases leaves me very perplexed.

2 Likes
40

Has Roon tested MacOS 26.1 beta 2, which Apple reportedly released on October 6, 2025 under build 25B5057f? If so, does that resolve this device initialization bug?

1 Like
41

It’s being tested in Early Access as explained a few posts up