Tracks stopping mid-track

Core Machine (Operating system/System info/Roon build number)

Synology Roon Server Vol 1

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Cisco ASA router, Cisco Catalyst switches

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Meridian 818 ,218, MS200, ethernet

Description Of Issue

While listening to music, the track will stop midway through playback. It will not restart via control and the only way to listen again is to select a completely different song. This happens on every song whether streaming or locally stored music.

Here is a recent log file…

05/29 10:28:06 Info: Starting RAATServer v1.6 (build 416) stable on linuxx64
05/29 10:28:06 Trace: [RAATServer] detected ALSA support
05/29 10:28:06 Info: [RAATServer] creating RAAT__manager
05/29 10:28:06 Info: [RAATServer] appdata_dir = /volume1/RoonServer/RAATServer
05/29 10:28:06 Info: [RAATServer] unique_id = 7f4a2b90-9f56-4360-824e-ca3c2fdd0d40
05/29 10:28:06 Info: [RAATServer] machine_id = 912a006b-f712-7cbb-91a3-4fa0b7b5960d
05/29 10:28:06 Info: [RAATServer] machine_name = ludwig-ma-nas01
05/29 10:28:06 Info: [RAATServer] os_version = Linux 3.10.105
05/29 10:28:06 Info: [RAATServer] vendor =
05/29 10:28:06 Info: [RAATServer] model =
05/29 10:28:06 Info: [RAATServer] service_id = d7634b85-8190-470f-aa51-6cb5538dc1b9
05/29 10:28:06 Info: [RAATServer] is_dev = False
05/29 10:28:06 Trace: [raatmanager] starting
05/29 10:28:06 Trace: [raatmanager] initialized
05/29 10:28:06 Info: [RAATServer] running RAAT__manager
05/29 10:28:06 Trace: [raatmanager] starting discovery
05/29 10:28:06 Trace: [discovery] starting
05/29 10:28:06 Info: [discovery] [iface:127.0.0.1] multicast recv socket is bound to 0.0.0.0:9003
05/29 10:28:06 Info: [discovery] [iface:127.0.0.1] multicast send socket is bound to 0.0.0.0:52701
05/29 10:28:06 Info: [discovery] [iface:10.15.2.15] multicast recv socket is bound to 0.0.0.0:9003
05/29 10:28:06 Info: [discovery] [iface:10.15.2.15] multicast send socket is bound to 0.0.0.0:44017
05/29 10:28:06 Info: [discovery] unicast socket is bound to 0.0.0.0:9003
05/29 10:28:06 Trace: [raatmanager] starting server
05/29 10:28:06 Info: [jsonserver] listening on port 44821
05/29 10:28:06 Trace: [raatmanager] announcing
05/29 10:28:06 Debug: [discovery] broadcast op is complete
05/29 10:28:16 Trace: [RAATServer] refreshing @ 10s
05/29 10:28:16 Trace: [raatmanager] announcing
05/29 10:28:16 Debug: [discovery] broadcast op is complete
05/29 10:28:22 Trace: [RAATServer] network reachability changed, refreshing discovery
05/29 10:28:22 Trace: [raatmanager] updating network interfaces
05/29 10:28:22 Trace: [discovery] stopping
05/29 10:28:22 Trace: closing multicast
05/29 10:28:22 Trace: [discovery] closing unicast send socket
05/29 10:28:22 Trace: [discovery] closing unicast recv socket
05/29 10:28:22 Trace: [discovery] starting
05/29 10:28:22 Info: [discovery] [iface:127.0.0.1] multicast recv socket is bound to 0.0.0.0:9003
05/29 10:28:22 Info: [discovery] [iface:127.0.0.1] multicast send socket is bound to 0.0.0.0:55321
05/29 10:28:22 Info: [discovery] [iface:10.15.2.15] multicast recv socket is bound to 0.0.0.0:9003
05/29 10:28:22 Info: [discovery] [iface:10.15.2.15] multicast send socket is bound to 0.0.0.0:47788
05/29 10:28:22 Info: [discovery] unicast socket is bound to 0.0.0.0:9003
05/29 10:28:22 Trace: [raatmanager] announcing
05/29 10:28:22 Debug: [discovery] broadcast op is complete
05/29 10:28:57 Trace: [jsonserver] [127.0.0.1:49405] accepted connection
05/29 10:28:58 Trace: [jsonserver] [127.0.0.1:49405] GOT[LL] [1] {“request”:“enumerate_devices”,“subscription_id”:“0”}
05/29 10:28:58 Trace: [jsonserver] [127.0.0.1:49405] SENT [1] [nonfinal] {“status”: “Success”, “devices”: []}
05/30 09:22:50 Trace: [jsonserver] [127.0.0.1:49405] read: eof
05/30 09:22:50 Trace: [jsonserver] [127.0.0.1:49405] destroying client

Hi @Maverick_Integration,

Can give some additional details about the Synology Core machine? Is the database stored on an SSD?

Does this behavior occur with all endpoints, including System Output of a remote device?

Model RS2416RP
DSM Version 6.2.2-24922
Local music is on SSD drives
Streaming is via Tidal
Both sources behave the same and cut off mid song. This has been tested on multiple endpoints. We are looking at multicast settings in our switches.

Hi @Maverick_Integration,

In an effort to better understand where this behavior is stemming from, I’d like to propose a test. If you temporarily use another device as your Core machine on the same network do things work for you in that configuration?

Will do. We have a tech heading over to site on Friday, who will run the core from his laptop instead of the Synology.

1 Like

We were able to have the Core run successfully off a laptop. Seems like the Synology is the issue.

Thanks for confirming that, @Maverick_Integration!

Since we’ve narrowed it down to the Synology Core, can you provide some specifics about the Synology device? What kind of CPU does it use? How much RAM?

Was the laptop Core connect to the network in the same way as the Synology or were there any differences?

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