USB auto suspend

Audio Gear Talk RoPieee
1

My Topping DAC is connected to the USB port of my Ropieee and has an auto on/off feature which I use along with the auto suspend feature of Ropieee. It works great 90% of the time, but occasionally when the usb port is suspended and the dac is consequently turned off, the ropieee end point disappears from the list of available zones in Roon. I need to manually turn the DAC on to make it re-appear, which is kind of inconvenient. I wonder if others have experienced similar issues?

2

That is normal. If the DAC is switched off or auto suspended at the USB end Roon won’t see it as an endpoint.

1 Like
3

so why does it work the way I want it 9 out of 10 times? The DAC is off, yet the zone appears in Roon and when I play something to the zone the DAC automatically turns back on.

4

Is Ropieee configured as i2S endpoint? In some configurations Ropieee makes itself the endpoint, in others it’s HAT or USB DAC will be.

5

I have a similar setup with a Pi and a Topping DAC, and I have not seen this. I’d suggest looking at the Roon server logs next time this happens, see if you can find anything there. What version of RoPieee do you use? (I use the regular, not the XL.) Pi3 or Pi4? Ethernet-connected or WiFi? My first guess would be that the Core is losing the network connection to the Pi.

1 Like
6

Thanks. I will look at the logs next time I see this. I also have regular RoPieee on Pi4 connected with Ethernet. My core is a bit old, so it’s possible it’s underpowered.

7

Interesting. How should I check what config it uses?

8

If you’re not using the I2S input of the Topping DAC, I doubt you’re configured for I2S.

@Henry_McLeod, doesn’t using I2S with USB require an additional piece of hardware to do the protocol transform? If @phi4 had that, I’d imagine he’d know it.

9

Ah, no I am using USB.

10

What are you running the Core on? Roon Server does seem pretty finicky about keeping its connection to each endpoint up and running.

11

Running it on an old Mac mini with wired connection.

12

Do you know what the processor in the Mac is? Which version of macOS?

13

It’s a late 2010 Mac mini with 2.3ghz core 2 duo CPU and 8g ram running El Captain.

14

El Capitan is pretty ancient, but if everything’s hard-wired, can’t see why it would matter. Have to wait for some more info from the log files, I think, next time it happens.

1 Like
15

Go to the admin web page and see if a DAC HAT is configured. If it isn’t you might need to get Harry involved.

16

It should say, “No HAT configured”, on the “Roon” tab, the line that says “Audio HAT”.

17

When I google “El Capitan network problems”, I see a number of WiFi issues, but no general networking issue. The Mac is hardwired, so that’s probably not germane.

18

It does say No Hat Configured there.

19

This issue happened again and it was right after I restarted my Roon Core. I captured the whole logs. The zone in question is ‘Study hifi’ which is a Ropieee connected via usb to ‘D90SE’. I see these in the logs:

01/24 15:01:35 Trace: [zone Study hifi] PlayPause
01/24 15:01:35 Trace: [zone Study hifi] Unpause
01/24 15:01:35 Trace: [zone Study hifi] Selecting Source state=Paused
01/24 15:01:35 Trace: [zone Study hifi] Unsuspend
01/24 15:01:35 Debug: [easyhttp] [65] GET to https://www.qobuz.com/api.json/0.2/track/getFileUrl?format_id=27&intent=stream&request_sig=9d67ccce6ea35dcb500ca92e15408e2f&request_ts=1643036495&track_id=127669697 returned after 82 ms, status code: 200
01/24 15:01:35 Info: [Study hifi] [zoneplayer] Playing: https://streaming-std.qobuz.com/file
01/24 15:01:35 Trace: [streamingmediafile] [1] [https://streaming-std.qobuz.com/file] [cachedbytes=0/-1] starting caching...
01/24 15:01:36 Trace: [streamingmediafile] [1] [https://streaming-std.qobuz.com/file] [cachedbytes=0/-1] got length 21838291
01/24 15:01:36 Info: [Study hifi] [zoneplayer]     Open Result (Playing):Result[Status=Success]
01/24 15:01:36 Trace: [prebuffer] ready 149940/441000 (34%) @ 0/180 sec
01/24 15:01:36 Info: [Study hifi] [zoneplayer] Performing initial seek to 6000
01/24 15:01:36 Info: [Study hifi] [zoneplayer] Starting playback
01/24 15:01:36 Trace: [prebuffer] ready 149940/441000 (34%) @ 6/180 sec
01/24 15:01:36 Trace: [streamingmediafile] [1] [https://streaming-std.qobuz.com/file] [cachedbytes=0/21838291] killing previous immediate read because 1835008 != 0
01/24 15:01:36 Trace: [streamingmediafile] [1] [https://streaming-std.qobuz.com/file] [cachedbytes=0/21838291] starting immediate read at off=1835008 length=21838291
01/24 15:01:36 Trace: [Study hifi] [zoneplayer/raat] StartStream Sooloos.Broker.Transport.RaatZonePlayer+Endpoint: StreamFormat(channels=2, bitspersample=16, samplerate=44100, isdts=False) => StreamFormat(channels=2, bitspersample=32, samplerate=44100, isdts=False) streamid=926230922
01/24 15:01:36 Trace: [D90SE] [raatclient] SENT [6]{"request":"setup","format":{"sample_type":"pcm","sample_rate":44100,"bits_per_sample":32,"channels":2,"sample_subtype":"none"}}
01/24 15:01:36 Info: [zone Study hifi] OnPlayFeedback Playing
01/24 15:01:36 Trace: [Study hifi] [Inactive] [PLAYING @ 0:06/3:00] Wear My Medals - Silverbacks
01/24 15:01:36 Trace: [musicpowerstate] music is playing, preventing idle sleep
01/24 15:01:36 Debug: [easyhttp] [66] POST to https://www.qobuz.com/api.json/0.2/track/reportStreamingStart? returned after 72 ms, status code: 201
01/24 15:01:36 Debug: [easyhttp] [67] GET to https://www.qobuz.com/api.json/0.2/track/getFileUrl?format_id=27&intent=stream&request_sig=a07b4da3b4425e72d6d5ae790ffcd284&request_ts=1643036496&track_id=130313711 returned after 93 ms, status code: 200
01/24 15:01:36 Info: [Study hifi] [zoneplayer] Queueing: https://streaming-std.qobuz.com/file
01/24 15:01:36 Trace: [streamingmediafile] [2] [https://streaming-std.qobuz.com/file] [cachedbytes=0/-1] starting caching...
01/24 15:01:37 Trace: [streamingmediafile] [2] [https://streaming-std.qobuz.com/file] [cachedbytes=0/-1] got length 49619570
01/24 15:01:37 Info: [Study hifi] [zoneplayer] Open result (Queueing): Result[Status=Success]
01/24 15:01:40 Info: [stats] 4225mb Virtual, 1477mb Physical, 758mb Managed, 76 Threads,  FDs 
01/24 15:01:40 Trace: [D90SE] [raatclient] GOT [6] {"status":"DeviceOpenFailed","message":"RAAT__OUTPUT_PLUGIN_STATUS_DEVICE_OPEN_FAILED"}
01/24 15:01:40 Trace: [Study hifi] [zoneplayer/raat] device open failed. stopping stream
01/24 15:01:40 Warn: [zone Study hifi] Track Stopped Due to DeviceOpenFailed
01/24 15:01:40 Info: [audio/env] [zoneplayer -> stream -> endpoint] All streams were disposed
01/24 15:01:40 Info: [audio/env] [zoneplayer -> stream] All streams were disposed
01/24 15:01:40 Info: sleep 0ms after flush
01/24 15:01:40 Info: [zone Study hifi] OnPlayFeedback StoppedLostEndpoint
01/24 15:01:40 Trace: [zone Study hifi] Suspend
01/24 15:01:40 Info: [zone Study hifi] OnPlayFeedback Stopped
01/24 15:01:40 Info: [zone Study hifi] Canceling Pending Sleep
01/24 15:01:40 Info: [audio/env] [zoneplayer] All streams were disposed
01/24 15:01:40 Trace: [Study hifi] [Inactive] [PAUSED @ 0:06/3:00] Wear My Medals - Silverbacks
01/24 15:01:41 Debug: [easyhttp] [68] POST to https://www.qobuz.com/api.json/0.2/track/reportStreamingEnd? returned after 195 ms, status code: 200
01/24 15:01:42 Trace: [raatserver] [D90SE] lost client connection. Retrying
01/24 15:01:42 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
01/24 15:01:42 Info: [raatserver] [D90SE] connecting (attempt 1)
01/24 15:01:42 Info: [transport] destroyed zone Study hifi was playing? False
01/24 15:01:42 Trace: [zone Study hifi] Suspend
01/24 15:01:42 Info: [zone Study hifi] Canceling Pending Sleep
01/24 15:01:42 Info: [zone Study hifi] Canceling Pending Sleep
01/24 15:01:42 Trace: [push] retrying connection in 65799ms
01/24 15:01:42 Warn: [raat_ll/client] [D90SE] failed to connect Connection refused
01/24 15:01:42 Trace: [raatserver] [D90SE] client connection failed. Retrying in 500ms
20

I am seeing something like this on my RoPieee device, too. But not quite. I am streaming an Internet radio station to a Chromecast Audio; the logs show that the connection to my RoPieee device, a completely different zone that’s not active, drops, and the resulting flurry of Roon’s reconnecting to all my devices somehow kills the Internet radio streaming. Beginning to suspect this is a Roon bug. Though I don’t know why the connection to my inactive RoPieee device drops; is this a standard thing to have happen on and off throughout the day?