Music playing stuck after seconds

Support
1

Core Machine (Operating system/System info/Roon build number)
Sonic Orbiter i5 with 8TB HDD with music. Running Roon Server 1.7 (build 521)

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Ethernet network. Netgear switch between core Roon machine and end point (Devialet). Main router is Netgear R7000 and is connected to Telco modem (fiber optic 200mb connection).

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Devialet Expert 400. Roon connects using Air protocol

Description Of Issue
Hi, very often, playback stop after 30-40 seconds. Music pointer is stuck but in front of the song title on the contents, the playing animation moves. There is no sound at all.

This is a screen shot:

image
image2911×2114 1.04 MB

Remote is on my PC.

Here is an excerpt of the Roon Server diagnostic log:

02/27 07:24:49 Debug: [identification] <2100271> identifier request id: bb3d785b
02/27 07:24:49 Trace: [library] finished with 18 dirty tracks 1 dirty albums 2 dirty performers 3 dirty works 3 dirty performances 1 dirty genres 0 clumping tracks, 0 clumping auxfiles 0 compute tracks, 0 deleted tracks, 18 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 28 changed objects
02/27 07:24:49 Trace: [dbperf] flush 100895 bytes, 38 ops in 7 ms (cumulative 46644318 bytes, 18112 ops in 31223 ms)
02/27 07:24:49 Debug: [identification] <2100271> status: CouldNotIdentify
02/27 07:24:49 Trace: [identification] <1982511> Identifying album [London Philharmonic Orchestra, Christoph Eschenbach, Tzimon Barto, Andrew Barclay, Erika Öhman and John Ryan - Messiaen: Des Canyons aux étoiles] with 12 tracks
02/27 07:24:49 Debug: [metadata http post req]: https://identifier.roonlabs.net/identifier/2/album?uid=ca460c72-59a7-4f5b-af52-b622e09ec66e&lid=&token=02938ec6-9373-46af-9903-6012a23d4909
02/27 07:24:49 Debug: [identification] <1982511> identifier request id: 9734fd21
02/27 07:24:49 Trace: [library] finished with 22 dirty tracks 1 dirty albums 4 dirty performers 6 dirty works 6 dirty performances 2 dirty genres 0 clumping tracks, 0 clumping auxfiles 0 compute tracks, 0 deleted tracks, 22 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 41 changed objects
02/27 07:24:49 Trace: [dbperf] flush 123318 bytes, 46 ops in 6 ms (cumulative 46767636 bytes, 18158 ops in 31229 ms)
02/27 07:24:49 Trace: [library] endmutation in 12ms
02/27 07:24:49 Debug: [identification] <866351> status: CouldNotIdentify
02/27 07:24:49 Trace: [identification] <333359> Identifying album [Paul Crossley, Tristan Murail, Philharmonia Orchestra, Esa-Pekka Salonen - Turangalîla-Symphonie / Symphony No. 3] with 2 tracks
02/27 07:24:49 Debug: [metadata http post req]: https://identifier.roonlabs.net/identifier/2/album?uid=ca460c72-59a7-4f5b-af52-b622e09ec66e&lid=&token=02938ec6-9373-46af-9903-6012a23d4909
02/27 07:24:49 Debug: [identification] <333359> identifier request id: 1f90921d
02/27 07:24:49 Trace: [library] finished with 13 dirty tracks 1 dirty albums 2 dirty performers 1 dirty works 1 dirty performances 0 clumping tracks, 0 clumping auxfiles 0 compute tracks, 0 deleted tracks, 13 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 18 changed objects
02/27 07:24:49 Trace: [dbperf] flush 72129 bytes, 28 ops in 4 ms (cumulative 46839765 bytes, 18186 ops in 31233 ms)
02/27 07:24:49 Info: [stats] 3998mb Virtual, 1645mb Physical, 739mb Managed, 0 Handles, 72 Threads
02/27 07:24:49 Trace: [Devialet] [Enhanced, 24/96 FLAC => 24/96] [100% buf] [PLAYING @ 0:43/3:02] Something (2019 Mix) - The Beatles
02/27 07:24:50 Debug: [identification] <1982511> status: CouldNotIdentify
02/27 07:24:50 Trace: [identification] <2134063> Identifying album [Metropolitan Hilarion Alfeyev, Russian National Orchestra & Moscow Synodal Choir - Metropolitan Hilarion Alfeyev: St. Matthew Passion (English Version)] with 18 tracks
02/27 07:24:50 Debug: [metadata http post req]: https://identifier.roonlabs.net/identifier/2/album?uid=ca460c72-59a7-4f5b-af52-b622e09ec66e&lid=&token=02938ec6-9373-46af-9903-6012a23d4909
02/27 07:24:50 Debug: [identification] <2134063> identifier request id: 3f16ae30
02/27 07:24:50 Trace: [library] finished with 12 dirty tracks 1 dirty albums 2 dirty performers 1 dirty works 1 dirty performances 0 clumping tracks, 0 clumping auxfiles 0 compute tracks, 0 deleted tracks, 12 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 17 changed objects
02/27 07:24:50 Trace: [dbperf] flush 72076 bytes, 26 ops in 7 ms (cumulative 46911841 bytes, 18212 ops in 31240 ms)
02/27 07:24:50 Debug: [identification] <333359> status: CouldNotIdentify
02/27 07:24:50 Trace: [identification] <122159> Identifying album [David Byrne and Brian Eno
David Byrne and Brian Eno - Everything That Happens Will Happen On this Tour - David Byrne On Tour - Songs of David Byrne and Brian Eno] with 1 tracks
02/27 07:24:50 Debug: [metadata http post req]: https://identifier.roonlabs.net/identifier/2/album?uid=ca460c72-59a7-4f5b-af52-b622e09ec66e&lid=&token=02938ec6-9373-46af-9903-6012a23d4909
02/27 07:24:50 Debug: [identification] <122159> identifier request id: 69b27464
02/27 07:24:50 Trace: [library] finished with 2 dirty tracks 1 dirty albums 1 dirty performers 0 clumping tracks, 0 clumping auxfiles 0 compute tracks, 0 deleted tracks, 2 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 4 changed objects
02/27 07:24:50 Trace: [dbperf] flush 12433 bytes, 6 ops in 0 ms (cumulative 46924274 bytes, 18218 ops in 31240 ms)
02/27 07:24:50 Debug: [identification] <122159> status: CouldNotIdentify
02/27 07:24:50 Trace: [library] finished with 1 dirty tracks 1 dirty albums 1 dirty performers 0 clumping tracks, 0 clumping auxfiles 0 compute tracks, 0 deleted tracks, 1 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 3 changed objects
02/27 07:24:50 Trace: [dbperf] flush 6461 bytes, 4 ops in 0 ms (cumulative 46930735 bytes, 18222 ops in 31240 ms)
02/27 07:24:50 Debug: [identification] <2134063> status: CouldNotIdentify
02/27 07:24:50 Trace: [library] finished with 18 dirty tracks 1 dirty albums 2 dirty performers 1 dirty works 1 dirty performances 0 clumping tracks, 0 clumping auxfiles 0 compute tracks, 0 deleted tracks, 18 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 23 changed objects
02/27 07:24:50 Trace: [dbperf] flush 104397 bytes, 38 ops in 3 ms (cumulative 47035132 bytes, 18260 ops in 31243 ms)
02/27 07:24:55 Trace: [Devialet] [Enhanced, 24/96 FLAC => 24/96] [100% buf] [PLAYING @ 0:43/3:02] Something (2019 Mix) - The Beatles
02/27 07:24:59 Trace: [devialet/audiosource] Sent 30000 packets, qdepth=5000
02/27 07:25:00 Trace: [Devialet] [Enhanced, 24/96 FLAC => 24/96] [78% buf] [PLAYING @ 0:43/3:02] Something (2019 Mix) - The Beatles
02/27 07:25:04 Info: [stats] 3999mb Virtual, 1645mb Physical, 746mb Managed, 0 Handles, 70 Threads
02/27 07:25:05 Trace: [Devialet] [Enhanced, 24/96 FLAC => 24/96] [30% buf] [PLAYING @ 0:43/3:02] Something (2019 Mix) - The Beatles
02/27 07:25:08 Debug: [prebuffer] sleeping in read -- this isn't good

This happens normally after I power up everything or use try to play music in the morning.

Let me know if you need anything else.

Thanks.

3

Hi @Gustavo_Gabaldon,

Thank you for reaching out and I appreciate you providing the log snippet as well, this really helps!

This part of your snippet indicates that the media did not buffer properly and hasn’t reached the endpoint in time. This could be due to an endpoint-specific issue, a networking issue or a Core issue, but there are tests that we can perform to narrow this down further. My questions are as follows:

If you try to enable “System Output” on your PC and try using the PC’s internal speakers, do you see this behavior there as well?

As per our Networking Best Practices Guide, can you confirm you have this option disabled?

Netgear R7000

We recommend disabling the “Enable Smart Connect” setting.

From the snippet above, it looks like you were playing local content. Have you seen this issue occur when playing back TIDAL/Qobuz content as well?

4

Hello Noris,

Thanks for your response. My comments below:

It does not happen with Tidal as well.

Let me know if you need anything else. Thanks.

5

Hi @Gustavo_Gabaldon,

Thanks for confirming the behavior doesn’t occur on “System Output”, this suggests that the issue is specific to the Devialet or how it is connected.

What kind of Netgear switch are you using? Is it a managed switch or unamanged one?

If your Devialet supports connecting via WiFi, can you check to see if the behavior is the same there?

Just to clarify here - did you mean to say it does happen with TIDAL as well, or it doesn’t happen with TIDAL?

6

hello @noris, my comments below:

Sorry, it does not occur with Tidal, so not sure if it is due to the Devialet.

Thanks.

7

Hi @noris,

From the fact that Tidal playback works fine, can it be inferred that the problem is not with the Devialet, that the network communication between the Sonicorbiter and Devialet is fine, and that perhaps there is an issue with HDD (local) playback from the Sonicorbiter?

Is there a way to diagnose that from within Roon?

Thanks.

8

Hi @Gustavo_Gabaldon,

Yes, this is a possibility here. Does your SonicOrbiter Core support USB media? If you wish - you could try connecting a USB drive filled with a small number of albums and verify if the same issue occurs with that.

Also, you may want to reach out to the SonicOrbiter support staff for further troubleshooting, perhaps they have some additional tools they can use to verify hard drive integrity.

9

Hello @agillis,

Is there something that can be done to troubleshoot this? It’s a sonicTransporter AP 8TB (Roon Server) .

10

If you have problem with Small Green Computer products please go to smallgreencomputer.com and click on contact us and submit a support ticket.

1 Like
11

Thank you Andrew. Will do. Cheers!

12

Finally, the internal HDD of the SonicTransporter was failing, which caused the problem.

Thank you to all for the support.

13

Hi @Gustavo_Gabaldon,

Happy to hear that you were able to locate the issue with the help of the SonicTransporter support team!

If you have any further issues feel free to reach out to us again and we can certainly assist. Until next time, take care!

14

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