Version 1.7 Build 537 started second long pauses and intermittent stops

Support
1

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

ROCK OS 1.0 ( build 186), NUC7i5BNH, Server Version 1.7 (build 537)

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

Netgear GS105 - Ethernet

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

SOtM sMS-200 Ultra Neo; Bel Canto 3.7 - USB

Description Of Issue

After upgrading to build 537 I found that playback will pause intermittently for about a second long pause and will stop completely other times. It might pause once in an hour but I haven’t been able to find a pattern. It might play back for 20 minutes and stop completely as if I’d hit pause. Other times it might play for a couple of hours before it stops. It does not matter if it is playing Tidal or local FLAC files.

4

Hello @Muel, and thanks for the information! First thing to try would be connecting the Bel Canto directly to the core. Let’s see if bypassing the SOtM presents the same issue. Let me know if tracks continue to have playback issues when going directly to the Bel Canto.

5

Couple of hours with the Bel Canto connected directly to the core with no issue yet. Of course, it has gone for hours without completely stopping before but the pauses were often occuring once or twice per hour. I’ll have to listen for a number of days to hear if the pauses and stops occur.

Even if bypassing the SOtM sMS-200 Ultra solves the problem it seems suspect that the problem didn’t begin until immediately after updating to build 537. Eliminating the sMS-200 would not be a happy solution for me.

6

So after a couple of days with the Bel Canto connected directly to the core there has been no pauses or intermittent stops witnessed. What do you think a next step would be?

A little more information… before I started this thread I checked out the version of the SOtm SMS-200 Ultra and found that there was an update available for it. I updated it to the latest version but this had no affect on the pausing and stopping issue as it continued to have the problem.

Curious what you see as a next step? It seems suspicious that the problem started the same day after updating to build 537.

Thanks!

7

Hello @Muel,

Let’s go ahead and add the SOtm back into your setup and reproduce the issue one more time. When you do, please reply here with a timestamp (your local time) and I will enable diagnostics for your account. That should let us see what the SOtm is running into. Thanks!

8

Paused for a second at 3:16 central time. Paused again at 3:22; 3:23 and 3:26. Started again and a second later stopped completely.

9

Restarted again… lasted until 4:17 and stopped.
Thank you

10

Hey @Muel,

I have enabled diagnostics on your account so our technical staff can get some more insight into what’s going on here. The next time your Core is active a diagnostics report will automatically be generated and uploaded directly to our servers

Once that’s been received, I’ll be sure to update this thread and pass the diagnostics over to the team for further analysis.

11

Thanks! Should have some data by now… there has been plenty of pauses and one complete stop.

12

Do you have some diagnostics? There should be plenty of evidence of a problem as it has been pausing and stopping quite a bit.

13

Hey @Muel, I got em! Sending to our team now, I’ll be in touch once they’re reviewed. Thanks!

14

Hello @Muel,

Looking at the diagnostic logs, it appears that the SoTM sMS-200 ultra is suffering from dropouts during playback

05/11 20:47:13 Info: [stats] 24306mb Virtual, 3614mb Physical, 2114mb Managed, 295 Handles, 92 Threads
05/11 20:47:16 Trace: [SOtM 200 Ultra Neo] [Inactive] [100% buf] [PLAYING @ 1:51/3:14] Wish You Would - Billy Boy Arnold
05/11 20:47:17 Trace: [SOtM sMS-200 () @ 192.168.10.115:39453] [raatclient] GOT [17] {"status":"Dropout","samples":15242}
05/11 20:47:17 Trace: [SOtM sMS-200 () @ 192.168.10.115:39453] [raatclient] GOT [17] {"status":"Dropout","samples":22050}
05/11 20:47:18 Trace: [SOtM sMS-200 () @ 192.168.10.115:39453] [raatclient] GOT [17] {"status":"Dropout","samples":22050}
05/11 20:47:18 Trace: [SOtM sMS-200 () @ 192.168.10.115:39453] [raatclient] GOT [17] {"status":"Dropout","samples":11025}

These dropouts could be caused by intermittent network conditions or CPU resource exhaustion on the SOtM endpoint. The logs indicate that the Core is operating normally.

I would double check all of your network connections and give every device (ROCK + sMS-200 + Router) in your network path a full power cycle before continuing any further.

-John

15

So I shutdown, unplugged, plugged back in and restarted everything (again) with no improvment. I replaced the switch with a new one at 5:57 on 5/15. Still had problems. At 11:10AM on 5/16 swapped all ethernet cables and still had stops within an hour or 3. Next Steps?

Side note: It is not fun having the default volume going all the way up to 100 when restarting the Sotm endpoint!

16

Well I found the logs so I can see what you were reviewing… Today I created a new boot drive for the Sotm SMS-200 ultra with the latest version of their software. Looks like I’m still having the same problem:

05/19 02:59:46 Trace: [SOtM 200 Ultra Neo] [Inactive 2.8x] [100% buf] [PLAYING @ 5:31/6:48] Blue Rondo à la Turk - The Dave Brubeck Quartet / Dave Brubeck / Dan Brubeck
05/19 02:59:46 Info: [stats] 24118mb Virtual, 2382mb Physical, 1182mb Managed, 291 Handles, 94 Threads
05/19 02:59:48 Trace: [SOtM sMS-200 () @ 192.168.10.115:44513] [raatclient] GOT [122] {“samples”:14107,“status”:“Dropout”}
05/19 02:59:48 Trace: [SOtM sMS-200 () @ 192.168.10.115:44513] [raatclient] GOT [122] {“samples”:88200,“status”:“Dropout”}
05/19 02:59:49 Trace: [SOtM sMS-200 () @ 192.168.10.115:44513] [raatclient] GOT [122] {“samples”:88200,“status”:“Dropout”}
05/19 02:59:49 Trace: [SOtM sMS-200 () @ 192.168.10.115:44513] [raatclient] GOT [122] {“samples”:88200,“status”:“Dropout”}
05/19 02:59:50 Trace: [SOtM sMS-200 () @ 192.168.10.115:44513] [raatclient] GOT [122] {“samples”:44100,“status”:“Dropout”}
05/19 02:59:51 Trace: [SOtM 200 Ultra Neo] [Inactive 2.8x] [100% buf] [PLAYING @ 5:36/6:48] Blue Rondo à la Turk - The Dave Brubeck Quartet / Dave Brubeck / Dan Brubeck
05/19 02:59:53 Trace: [SOtM 200 Ultra Neo] [zoneplayer/raat] sync SOtM sMS-200 (): realtime=1125011318521 rtt=500us offset=-2658596681us delta=-77us drift=-112us in 183.8625s (-0.611ppm, -2.201ms/hr)
05/19 02:59:56 Trace: [SOtM 200 Ultra Neo] [Inactive 2.8x] [100% buf] [PLAYING @ 5:41/6:48] Blue Rondo à la Turk - The Dave Brubeck Quartet / Dave Brubeck / Dan Brubeck

Ideas from here? Buffer settings? These have never change since first installed. I already tried Sotm US support but have not heard back for a week. I’m actually not sure I contacted the right people if anyone knows.

17

Kind of strange… SOtM support had me copy some music directly to the SMS-200 Ultra microsd and play it in Roon from there. Seemed strange because it would still be playing through Roon so I’m not sure what that was accomplishing. We already determined there were no errors when playing directly from the ROCK to the DAC. Well with their test it has the same problem with the dropouts. I even tried playing with the buffer duration and Resync delay settings in the endpoint config. Nothing helped.
05/23 03:29:06 Trace: [SOtM sMS-200 () @ 192.168.10.115:41931] [raatclient] GOT [13] {“samples”:22050,“status”:“Dropout”}
05/23 03:29:06 Trace: [SOtM sMS-200 () @ 192.168.10.115:41931] [raatclient] GOT [13] {“samples”:22050,“status”:“Dropout”}

18

So I’m trying to find if I have a problem on the network, the Roon ROCK nuc, or the Sotm SMS 200 Ultra. Seems like there was no problem playing from the Core directly… didn’t hear any drop outs. I was using 2 endpoints at once (something I’ve done a lot for a long time without any issues), direct from the core and to a Chord Hugo. In a 20 hour period playing non stop I only had a few drop outs (see log). Is it normal to see a few dropouts like this? I wasn’t in the room to hear if there was a pause that time.
Then I powered everything off, restarted with Sotm in the mix playing and to the Chord. I had many drop outs and pauses in just a 40 minute time period (see 2nd log below). Help?

Drop outs for 20 hours of playing from both core directly and Chord
05/25 21:57:59 Trace: [Chord Async USB 44.1kHz-768kHz] [raatclient] GOT [9] {“status”:“Dropout”,“samples”:3543}
05/25 21:57:59 Trace: [Chord Async USB 44.1kHz-768kHz] [raatclient] GOT [9] {“status”:“Dropout”,“samples”:22050}
05/25 21:57:59 Trace: [prebuffer] short read: 0 / 8820 fill=436296
05/25 21:58:00 Trace: [Chord Async USB 44.1kHz-768kHz] [raatclient] GOT [9] {“status”:“Dropout”,“samples”:22050}
05/25 21:58:00 Trace: [Chord Async USB 44.1kHz-768kHz] [raatclient] GOT [9] {“status”:“Dropout”,“samples”:17640}
05/25 21:58:01 Trace: [ST12 Chord Hugo2] [Lossless, 16/44 FLAC => 16/44] [100% buf] [PLAYING @ 3:20/3:53] Kryptonite - 3 Doors Down

05/25 22:29:47 Trace: [Chord Async USB 44.1kHz-768kHz] [raatclient] GOT [9] {“status”:“Dropout”,“samples”:11343}
05/25 22:29:47 Trace: [Chord Async USB 44.1kHz-768kHz] [raatclient] GOT [9] {“status”:“Dropout”,“samples”:22050}
05/25 22:29:48 Trace: [Chord Async USB 44.1kHz-768kHz] [raatclient] GOT [9] {“status”:“Dropout”,“samples”:22050}
05/25 22:29:48 Trace: [ST12 Chord Hugo2] [Lossless, 16/44 FLAC => 16/44] [100% buf] [PLAYING @ 0:33/2:29] Smack - 3 Doors Down
05/25 22:29:48 Trace: [Chord Async USB 44.1kHz-768kHz] [raatclient] GOT [9] {“status”:“Dropout”,“samples”:4410}

Drop outs after 40 minutes of playing from both Sotm and Chord
05/26 01:34:38 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“status”:“Dropout”,“samples”:12419}
05/26 01:34:39 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“status”:“Dropout”,“samples”:22050}
05/26 01:34:39 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“status”:“Dropout”,“samples”:22050}
05/26 01:34:40 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“status”:“Dropout”,“samples”:11025}
05/26 01:34:42 Trace: [SOtM 200 Ultra Neo] [Inactive] [100% buf] [PLAYING @ 19:37/63:07] Peaceful Ocean Surf - Sounds of Nature

05/26 01:43:09 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“status”:“Dropout”,“samples”:22050}
05/26 01:43:09 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“status”:“Ended”}
05/26 01:43:09 Trace: [raat] [SOtM sMS-200 () @ 192.168.10.115:39225] => Disconnected
05/26 01:43:09 Trace: [raat] [SOtM sMS-200 () @ 192.168.10.115:39225] lost client connection. Retrying
05/26 01:43:09 Trace: [push] short read from connector (1)
05/26 01:43:09 Trace: [push] retrying connection in 6125ms
05/26 01:43:09 Trace: [raat] [SOtM sMS-200 () @ 192.168.10.115:39225] connecting (attempt 1)
05/26 01:43:09 Info: [transport] destroyed zone SOtM 200 Ultra Neo was playing? True
05/26 01:43:09 Trace: [zone SOtM 200 Ultra Neo] Suspend

05/26 02:05:09 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“samples”:7351,“status”:“Dropout”}
05/26 02:05:09 Trace: [SOtM 200 Ultra Neo] [Inactive] [100% buf] [PLAYING @ 0:21/3:26] Hey Jack Kerouac - 10,000 Maniacs
05/26 02:05:10 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“samples”:22050,“status”:“Dropout”}
05/26 02:05:10 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“samples”:22050,“status”:“Dropout”}
05/26 02:05:11 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“samples”:11025,“status”:“Dropout”}

05/26 02:10:06 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“samples”:21976,“status”:“Dropout”}
05/26 02:10:06 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“samples”:22050,“status”:“Dropout”}
05/26 02:10:06 Trace: [SOtM 200 Ultra Neo] [Inactive] [100% buf] [PLAYING @ 1:52/3:56] Like the Weather - 10,000 Maniacs
05/26 02:10:07 Trace: [SOtM sMS-200 () @ 192.168.10.115:39225] [raatclient] GOT [7] {“samples”:22050,“status”:“Dropout”}
05/26 02:10:08 Trace: [SOtM 200 Ultra Neo] [zoneplayer/raat] sync SOtM sMS-200 (): realtime=2297703386915 rtt=500us offset=679484386us delta=-171us drift=-6539us in 611.1945s (-10.699ppm, -38.516ms/hr)

19

So, I’m still waiting for some Roon support. Can you please review my testing comments and questions since your last reply?

20

Hello @Muel,

It is not abnormal to see a few “dropout” traces in the RAATServer logs even when playback is in a healthy state. Dropouts of a few thousand samples would affect the audio for fractions of a second and are often caused by the audio driver lagging behind playback temporarily.

Check your PM’s for further information on handling this support issue.

-John

21

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