· Roon ARC: streamed track gets corrupted and cannot be played past a certain timestamp
Tell us about your home network
· irrelevant. the issue is only with the ARC application.
I'll provide more detail about the issue here, since I don't see a better place to do that in this form.
I'll be streaming a song through ARC (Android, Pixel 8), and then suddenly I'll notice playback will stop. I'll open up the app and notice the playback indicator is spinning. If I move the playhead backwards, I can play the track up to where the error occurred, where it will stop again. If I move the playhead forward in the track, it will give an error like "Corrupted media" or "Poor connection" (I've seen both). Skipping to another track works fine. (But this is not a good mitigation because I exclusively listen to albums start to finish.) Force-quitting the app does not fix it. Clearing the application cache does not fix it.
This does not happen consistently. But it has been happening to me for several years.
hat does sound frustrating, especially when you are listening album to album and the issue only shows up once you reach a specific point in a track.
Does this happen only with local media, only when streaming, or with both? If you can send us the exact local date and time, along with the track and artist, we can enable diagnostics and look for clues on your Roon Server at that timestamp.
When it happened to me yesterday, it was local media in my server streamed via the bandwith-optimized strategy. I’m not sure if it happens when streaming from e.g. Qobuz.
I’m not sure I can get you an exact local time and date, but it was between 4-5pm PDT yesterday (the 10th). The track was “Caravanserai” by Younger Brother. If it helps, I can keep replying each time it happens again.
Yes, please do let us know 2-3 more examples in the hope that we can pinpoint a pattern in the logging. If you can keep track of whether it was from Qobuz or elsewhere, it would be helpful as well. Thanks!
Wanted to follow up on this. Have you had a chance to gather 2 or 3 more examples for us, and note whether each one was coming from Qobuz or from another source? That extra context should help us spot a pattern in the logs, so please reply with anything you have when you can.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.
The team won’t abandon this report and we have an open ticket into the underlying behavior.
Just to clarify, are you using lockscreen controls when this occurs, or is the Roon app open and foregrounded on the Pixel?
The team has work in the pipeline to address this, but it’s unfortunately not prepared for release in any upcoming cycle. We can keep this thread open and marked ticket in to report any change in symptoms or progress in the meantime.
I was using neither the lockscreen controls nor the in-app controls. I was using the controls in the keep-alive notification while the device was awake and the app was backgrounded. But I assume these work the same way as the lockscreen controls.