Hello @1p2win,
Welcome to the Roon Community, and thanks for the detailed explanation — that really helps
A couple of important clarifications first:
Roon ARC cannot control or trigger playback inside your home.
ARC is a remote-only app designed for listening outside the home. It has no ability to start, stop, or adjust playback on your Roon Core or any local zones. Because of that, the music playing at home while you were using ARC was a coincidence rather than a direct interaction between ARC and your Core.
If Roon was already playing to a local zone on your MacBook (or another zone at home), that playback would simply continue until manually stopped. ARC connecting remotely would not affect it.
When your wife closed the laptop, macOS likely put the system into sleep/hibernation, which abruptly stopped the Roon Core. Since ARC depends on the Core being online, ARC then lost connection in your car — which matches what you observed.
Force-closing or sleeping the Mac while Roon Core is active can sometimes leave the Core in an unstable state.
This behavior is consistent with an interrupted Core process rather than data corruption.
To help us understand whether there’s anything deeper going on, please try the following:
- Reproduce the scenario:
- Start playback locally
- Leave the MacBook open with Roon running
- Connect via ARC from outside the home
- Then put the MacBook to sleep or close the lid
- Note exactly what happens:
- Does Roon freeze again afterward?
If you’re able to reproduce the issue consistently, let us know and we’ll be happy to pass this along to our QA team for further testing.
As a general best practice, if you plan to rely on ARC regularly, we strongly recommend running Roon Core on a device that stays always on (for example, a desktop, NAS, or Nucleus), rather than a laptop that may be closed or put to sleep.
Looking forward to your update — and welcome again to Roon! 