Frequent Music Stops Between Roon and Airplay Devices (ref#N1TW0M)

Support
1

What best describes your playback issue?

· Music stops playing mid-track

Is there a specific error message you see? If so, please select from the following options:

· Other

Please try to reboot your Roon Server and check to see if this helps.

· Rebooting my Server had no effect, the issue remains

Please try to reboot and unplug/replug in your affected audio device and check to see if this helps.

· Rebooting and unplugging/replugging my audio device, the issue remains

Please open your Roon Remote and select the "System Output" Zone and try to play to it. Do you encounter any playback errors with this Zone?

· I can play back music *without issue to System Output*, it is only the *other zone that has issues*

What method is the audio device connected with to the server (Roon Ready, HDMI, USB, AirPlay, Chromecast, etc.)?

· Airplay

Is the audio device on the latest firmware version, as per the manufacturer's app?

· Yes

Is there any change in behavior when using a different cable for the connection for the audio device?

· No, using a different cable didn't change anything

Have you reached out to the manufacturer of the audio device regarding this issue yet?

· Yes, but I have not heard back

Does the issue happen with local library music, streaming service music, or both?

· Only local content affected, and I don't have any streaming services to test with

Where is your local content stored?

· Somewhere else on the local network (NAS)

If you move the content from your NAS to a local storage location, do you still experience issues with playback?

· The issue happens for both the NAS storage location and on the secondary storage location

Please try playing content of a lower sample rate (44.1kHz or 48kHz), does this work as expected?

· No, lower sample rates are still affected

What is the model/manufacturer of the affected audio device(s) and the connection type?

· 4 AirPlay devices "MUZO Cobblestone" (brand and model Octavio Stream)

Describe the issue

Hello,

I am still experiencing issues between Roon and my Airplay devices "MUZO Cobblestone" (brand and model Octavio Stream). The music stops frequently and for no apparent reason. Under the same conditions (same server, same Windows 10 computer, same network, same Airplay devices), iTunes works correctly without interruptions. Admittedly, the sound quality is not as good and the interface is less pleasant, but at least it works.

This has been going on for months and successive updates have only made things worse. I don't even know if there is technical support capable of addressing and resolving these difficulties. It is clear that without a fix for these intolerable bugs, I do not see the point in continuing to pay such amounts for a subscription to software that does not work.

Best regards.

Describe your network setup

Roon server is running on PC windows 10. Music is store on a QNAP NAS. Playback on 4 AirPlay devices "MUZO Cobblestone" (brand and model Octavio Stream). These four devices are wired on three extenders ASUS ZenWiFi Pro ET12. Network is very fast and stable.

2

17 days ago you wrote that everything was working perfectly until Build 1407, is this not so?

I’m just asking because, as you know, there were known issues in that build, and the latest update to build 1413 seemed to have fixed it for most (all?) affected people. (Did you install it?). Of course, if you actually had issues for months, then this may be a different issue than the known bug from 1407.

3

Indeed, I installed version 1413, which improved the startup sound issue on Airplay devices. However, the problem of random cutouts persists as before. It took me a long time to understand what was happening. When playing music on my computer, it worked fine. But as soon as I switched to an Airplay group, the random cutouts reappeared. Sometimes it works for a day or two without issues, then multiple cutouts per hour occur. With iTunes, it works all day without any failures. I also tried Audirvana (which I’m not a fan of due to its interface and difficulty in creating multiroom groups), but it plays music continuously without fail.

It seems that the issue stems from Roon, possibly between Roon and Airplay. I checked the logs and found sequences like this:

05/20 09:36:16 Trace: [Octavio Bureau] [LowQuality 59,6x, 24/48 MP3 => 16/44] [100% buf] [PLAYING @ 0:22/4:20] Suite for solo cello No. 4 in E flat major, BWV 1010: Suite No. 4 in E flat major. 5. Bourrées 1 & 2 - Jean‐Guihen Queyras / Johann Sebastian Bach
05/20 09:36:16 Trace: [Octavio Chambre] [LowQuality 59,6x, 24/48 MP3 => 16/44] [100% buf] [PLAYING @ 0:22/4:20] Suite for solo cello No. 4 in E flat major, BWV 1010: Suite No. 4 in E flat major. 5. Bourrées 1 & 2 - Jean‐Guihen Queyras / Johann Sebastian Bach
05/20 09:36:16 Trace: [Octavio Parrot] [LowQuality 59,6x, 24/48 MP3 => 16/44] [100% buf] [PLAYING @ 0:22/4:20] Suite for solo cello No. 4 in E flat major, BWV 1010: Suite No. 4 in E flat major. 5. Bourrées 1 & 2 - Jean‐Guihen Queyras / Johann Sebastian Bach
05/20 09:36:16 Trace: [Octavio Salon] [LowQuality 59,6x, 24/48 MP3 => 16/44] [100% buf] [PLAYING @ 0:22/4:20] Suite for solo cello No. 4 in E flat major, BWV 1010: Suite No. 4 in E flat major. 5. Bourrées 1 & 2 - Jean‐Guihen Queyras / Johann Sebastian Bach
05/20 09:36:16 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 51788
05/20 09:36:16 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 51788
05/20 09:36:17 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 51805
05/20 09:36:17 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 51805
05/20 09:36:17 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 51813
05/20 09:36:17 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 51813
05/20 09:36:17 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 51819
05/20 09:36:17 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 51819
05/20 09:36:17 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 51882
05/20 09:36:17 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 51882
05/20 09:36:18 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 51942
05/20 09:36:18 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 51942
05/20 09:36:18 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 51961
05/20 09:36:18 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 51961
05/20 09:36:18 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 51985
05/20 09:36:18 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 51985
05/20 09:36:18 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 51997
05/20 09:36:18 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 51997
05/20 09:36:18 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52042
05/20 09:36:18 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52042
05/20 09:36:19 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52094
05/20 09:36:19 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52094
05/20 09:36:19 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52100
05/20 09:36:19 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52100
05/20 09:36:19 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52123
05/20 09:36:19 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52123
05/20 09:36:19 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52173
05/20 09:36:19 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52173
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52207
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52207
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52260
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52260
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52263
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52263
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52268
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52268
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52277
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52277
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52283
05/20 09:36:20 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52283
05/20 09:36:21 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52329
05/20 09:36:21 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52329
05/20 09:36:21 Trace: [airplay/client] [192.168.1.72] server lost 1 packets starting at seq 52406
05/20 09:36:21 Trace: [airplay/client] [192.168.1.72] resent packet to 192.168.1.72:37247 with seq 52406
4

Sounds like a network issue to me, TBH. How is everything (server, endpoints, NAS) connected, everything cabled or wifi? Does it happen only with local music from the NAS or also with streaming services in Roon?

It’s quite typical that other players work if the network is marginal, because Roon always needs more bandwidth (as the server sends uncompressed PCM to the endpoint rather than the endpoint fetching some compressed file type directly. So the data size is larger and there is traffic from storage (NAS or online) to server and from server to endpoint)

7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.