I am using Ropiee as a roon bridge since a while and never had an issue via the RPI4 USB port, worked like a charm. I recently bought a streamer from Ian Canada (#93A) to upgrade my source, and it sounds amazing, when detected. When I power up the system sometimes it shows up, sometimes it does not. This morning I had to trigger a reconfigure in Ropiee to make the magic happen (disabled USB audio), and now it works again. Sometimes a single reboot helps. Anyone had any similar behaviour? I have seen similar with my ProtoDAC also, so have feeling the clue must be in Ropiee somewhere, but that is just a feeling, all feedback is welcome. All upgraded to actual latest versions indeed.
Thanks a lot for the answer. I missed capturing the logs, will do next time it happens. This morning it started without an issue. I will post the log identifier when the HAT is not detected next time.
This morning it happened again: roon says Device not found snd_rpi_spi_dac. Logs been sent under identifier âa24c6530aaa6865câ. Initiated a reboot from the Ropiee web interface, and it came up with no problem. Logs after the successful start: â0a9fbd7d2c4ecc55â. Hope these help identifying the issue.
Enabled USB again, rebooted, HAT not detected again, log identifier: âa9ef1cbd387d00b9â. Rebooted from web interface, everything works, log id: âd7ad52347cf34fb3â.
OK, I disabled USB audio and disconnected the cables, set the audio output of spotify connect to âoffâ, hope that is what you meant. I switch the system off every evening, and on in the morning when I am home. I will keep you updated on the developments.
I had another test: enabled Spotify to listen to some music I did not have on Tidal, and when roon did not see the HAT I could not play music with Spotify either. When roon sees the HAT Spotify also plays fine. I am afraid it is pointing towards ropieee as a possible place of the problem.
Please let me know if you need any more tests, logs or I can assist any way to resolve this.
First of all, I very much appreciate what you do, Ropieee is a very useful project and I know it should take a lot of time to maintain and develop it, so please do not take anything I say as a sign of disrespect, that was never and will be never intended.
Here is the story: my streamer RPI with the Ian Canada HAT running Ropieee, my DAC and my Amplifier are connected to the same Power Distribution Unit, which has a switch on it. In the evening I switch it off, removing power from all these devices. In the morning, I switch it on, powering them up. The roon core is always running on a PC powered separately. Several mornings, when I switch on the PDU, all seems right, Ropieee boots up, but roon does not see the HAT as an audio device. Several mornings it does. I could not find any pattern so far. Both spotify output and USB is disabled now, waiting for your highly appreciated help.
Your logs say otherwise: it is detected as an audio device, but Roon is not able to open it. Hence my question to disable all other services (I see at least UPnP active as well) and see if the pattern changes.
This sounds like a recipe for Ropiee booting at the same time as the DAC and potentially issues if it tries to access it befire itâs ready? (I realise thay depends on the DAC USB approach but could be related).
@spockfish just adding my own two cents. I have a ropieee with a generic USB DAC (spdif) and when I reboot that endpoint it never detects the device⌠I have to unplug it and plug the usb in again and it comes up. Itâs a bus powered device, so not the same as this issue but the cause could be similar. Iâve never reported it because I have this issue only on this device/dac⌠but I use the same dac on a different ropieee endpoint running stable and do not have this issue.
My buddy is the founder and owner of a smaller audio equipment company running since 30 years. He advised me to do so, as the lifetime of electronic components are not as long as it was a few decades ago, so according to him it makes sense not to have everything powered up when not in use. I follow his advice.
Hey Harry, relating to the earlier comment, just rebooted the relevant endpoint (upgrading to latest beta) and after the reboot as always the USB DAC doesnât come up. Generated feedback this time in case itâs useful. e80c4db1d68d5e11
When I unplug and re-plug the USB it always comes up. 9dd7cb7d9bf90fff is after a re-plug.