Roon needing to be launched more than once after upgrade to Tahoe

Same problem Here.

1 Like

I am not going to be that pessimistic, I am a huge Roon fan and assume and expect a fix

I agree, Jon!

Respectfully to David, many of us (even speaking just for myself - a ‘lifer’ for over five years) have remarkably few actual problems; none (again in my own case) which has yet to be solved.

If it were true in absolute that:

[emphasis mine] then wouldn’t we all be experiencing the exact same things as David is? Please note that I’m not saying that David’s problems aren’t real and pressing. Just that there maybe something ‘awkward’ in that case which - Yes, Tahoe may be revealing more starkly.

But I’d need a lot more convincing of a fundamental incompatibility.

Good luck, @David_Moore2 :slight_smile: !

1 Like

Log from MAC when Roon hasn’t started show Exception:

10/18 09:50:40 Info:
Local Time: 10/18/2025 09:50:40 +03:00
Device Serial Number: xxxxxx
Roon Version: 2.55 (build 1559) production
OS Version: Mac OS X 26.0.1
Hardware Version: Mac14,15
Mono Version: unknown

Application Domain: Roon
Assembly Codebase: file:///Applications/Roon.app/Contents/MonoBundle/.xamarin/osx-arm64/Roon.dll
Assembly Full Name: Roon, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null

CPU0 Description: Apple M2 (64-bit)
CPU0 Num Cores: Physical: 8 Logical: 8

Exception Source: System.Private.CoreLib
Exception Type: System.NullReferenceException
Exception Target Site: SpanHelpers.IndexOf
Exception Message: Arg_NullReferenceException
Exception Data: none

–[ Stack Trace ]------------
System.SpanHelpers.IndexOf(Byte& searchSpace, Byte value, Int32 length)
System.Private.CoreLib.dll, IL 81, N 79
System.String.Ctor(SByte* value)
System.Private.CoreLib.dll, IL 13, N 43
System.Runtime.InteropServices.Marshal.PtrToStringAnsi(IntPtr ptr)
System.Private.CoreLib.dll, IL 0, N 31
Interop/Sys/<>c__DisplayClass13_0.b__0(Byte* name)
System.IO.FileSystem.DriveInfo.dll, IL 35, N 127

today I needed 5 tries to get roon to open…it varies it seems from day to day once in a while it opens on the first try sometimes the second or third and today the 5th…it is really annoying but so far at least it ultimately works…fix please!

2 Likes

You can add me to the list. Since upgrading to macOS 26.0.1 the issues have started. 3/4 times it now takes to open.
Macbook Pro M2 Max

1 Like

Me too. As described above.

2 Likes

doesnt seem this should take this long to issue a fix for

3 Likes

new upgrade today when I opened my Roon, I am hoping this includes the fix finally

Early testing indicates that Roon 2.56, released today, fixed this for me - but of course, time will tell for sure. Roon 2.56 and ARC 1.70 are Live!

Same here; so far so good. Thanks, Roon team!

Today’s update seems to have fixed it for me as well but it would have been nice to also have the icon fixed.

for me the update has not altered the behaviour and the ‘failed to initialize..’ & ‘roon lost control..’ notifications remain despite troubleshooting malarkey

1 Like

Till now remote app on Tahoe hasn’t reproduce startup issue.

‘Roon lost control of audio device.’ I still need to restart my macmini when I want to listen to another album. ???

https://community.roonlabs.com/t/exclusive-mode-on-my-mac-with-tahoe-is-not-working/309144/27?u=suedkiez

2 Likes

In my case, the problem occurs only in the wired (usb) situation. Via airplay there is no loss of control of audiodevice.

Yes, I think that’s expected in this error case because the problem is in the exclusive mode of the Mac’s local hardware audio device

1 Like