I have built and loaded a DigiAMP+ RPi with latest Ropieee installed. I configured Ropiee, rebooted Roon Core and Control, confirmed that the unit is on the same subnet, etc.
Here’s the thing: Roon “sees” it in its About Window:
I think the AMP+ is not being detected as a device that is capable of audio output so try defining the AMP as a DAC+ instead. (I had the same issue when trying to get my AMP working with dietpi a couple of weeks ago)
Indeed the device is not properly being identified during initialization (it produces errors).
Have you tried removing and attaching the HAT again? Sometimes that helps…
Yes (sorry) I am using a hifiberry AMP2 (they all have confusingly similar names) but your symptoms appear to be the same as when I have mine defined (in dietpi) as AMP2 when it needed to be set to hifiberry dacplus (as it is the DAC onboard the amp that roon needs to communicate with)
Update from the OP: first, I continue to be impressed with the breadth and depth of knowledge in this community as well as your willingness to share it. Many thanks.
The ending, or at least stopping point, is a mixed bag. I had bought two DigiAMPs, and wrote about the first one I assembled (see above). Then I assembled the second one, installed Ropieee, configured, and, with one hiccup, it worked and continues to work.
@John_Mason’s suggestion to try a different config was a good one. When I first configured AMP #2, Roon AGAIN failed to recognize it. I then temporarily switched the configuration to IQAudio DAC, and Roon then “saw” the endpoint. BUT… Roon thinks it is now a “IQAudioDAC” and not an “IQAudio DigiAmp+” as I proscribed. So, @spockfish, methinks the DigiAmp+ config needs tweaking.
I have written IQAudio about the problem, inviting comment, and haven’t heard anything. Their banner says they are in “Stock Take” (a.k.a. taking inventory) until November 5th (!) I hope that they will respond to email. But maybe not. I’ve written five emails over the past few months; no response.
I am not looking forward to the refund experience. Their website says that, if a returned HAT “tests okay” when they get it, you get No refund AND a bill for the return postage. I might spend $50 returning a 42 pound (sterling) card, with no assurance of receiving anything. Hmmm…
@John_V Good to hear you have at least one of the amps working.
It’s odd that 2 different AMP manufacturers and 2 different pi distributions both have issues when you select their “amp” config instead of of the DAC. I mean it makes sense, as the data does go the DAC and the amp part is essentially invisible to the driver (I would have thought) but the config files need to reflect this.
It’s a tough call about sending it back. If I were in your shoes, I’d be tempted to take roon out of the mix, copy a track to the SD card to playback locally and collect console output from amixer and aplay to demonstrate how it works with the one device and not the other (if not for your own piece of mind).
btw, my amp has been mounted inside my granma’s old Bush valve radio to make a hipster endpoint for the kitchen.
Have been in touch these past few days asking for the configuration to be simplified and trying our quicktest images.
We have so few failures on outmr hardware we find majority of issue are software config.
We are always happy to exchange any board that fails but first it’s simple to ensure it’s not a software issue - especially when we test each board before it’s shipped.
We suggest you try quicktest image.
We suggest you use our official Roon Labs RAAT image over any roon bridge configuration.
If we can get feedback on the standard quicktest image then we can start to identify the next steps.
