IQ Audio question

I noticed the other day that the Pi-DigiAMP+ was listed on the partner site as ‘Roon Ready’ but I’m not really sure what this means when it’s a HAT that goes on a Pi (and the software/OS is necessarily something else)

I’ve got one of these running Ropieee and it doesn’t show up as Roon Ready at all… should it?
image

To be clear, I have no issues with the device or Ropieee’s support of it… everything is working fine. It just made me wonder why Roon list it as something that should show up as Roon Ready.

TLDR: looks like they used to have images for the RPi with OS that would make it show up, but they have not updated it for a while and it may not be available to download anymore?? AFAICT.
For more info see here:

and here:
https://forums.raspberrypi.com/viewtopic.php?t=353431
And another few bits of light reading:

But, (you may have already done this?) you can select it from the device settings to make sure the artwork and audio settings are appropriate for it:

Erm - it’s showing up in the “Roon” section of the audio devices - so therefore it is “Roon Ready”. If you want to set your mind at rest, look at the Signal path - I think you’ll see that it is using RAAT, and therefore is a Roon Ready device.

As a comparison, here’s my Artera Link endpoint, which is a RPi4 running RoPieee (also Roon Ready, since it uses Roon Bridge):

And here’s the signal path:

Maybe it’s purely a presentation thing. However all of my Roon Ready devices show in a different spot to all my Ropieee endpoints (and some of my Ropieee endpoints do not have “Roon Ready” DACs). E.g. you can see below two of my Ropieee endpoints showing separately (including the relevant IQ Audio DigiAMP+) and below that are all my Roon Ready devices (3 different brands, 4 different devices) and below that are the Roon Tested devices.

In terms of the signal path, everything going through Ropieee uses RAAT, but that doesn’t mean the DAC is Roon Ready. (e.g. the two below examples)
image
image

It’s a presentation thing - so long as RAAT is being used, then you’re OK. Roon Labs Roon Ready program " combines our RAAT technology with a comprehensive certification program, support infrastructure, and co-branding between Roon and device vendors in order to create the best experience possible for our users."

Thanks Bear, it’s auto detecting correctly (or close… technically it’s a DigiAMP+ but it’s detecting as a Pi-DAC+). And as mentioned it’s all “working”, I was just confused by the partner listing of this DAC being Roon Ready yet showing up like all the other Ropieee endpoints that are not.

Right, in which case they shouldn’t list IQaudio at all (it’s irrelevant or at most Roon Tested) and they should instead list Harry’s amazing Ropieee as Roon Ready :grin:

Case closed I guess.

This has all been discussed before - see IQAudio still listed as a partner

Certified devices are still listed as a matter of record, even when they are legacy.

And, as you say, you are running RoPieee - which uses Roon Bridge…

Yeah… another case of Roon knows best even when it doesn’t :man_shrugging:

I’d be pretty annoyed if I went and bought a device as “Roon Ready” and then discovered it was no longer supported due to changes in Roon (or the vendor in this case) but they kept it up because it “once did”.

As I mentioned in another thread you resurrected, IQaudIO devices are Roon Ready, and continue to be supported because they went through the certification program.

The rebranded products are the exact same devices. I guess Raspberry Pi could take them through the same steps, which would provide and update to the partners list, branding etc., but they have chosen not to do so – maybe because it is blatently evident that both are one and the same devices, and continue to be Roon Ready, i.e., supported.

I don’t agree at all. The approach is inconsistent and confusing. The partner site effectively tells someone that if they go and buy an IQaudio (and nothing else) they’re Roon Ready. Good luck with that.

I think we’ll just have to agree to disagree.

Roon Ready is Roons RAAT api, combined into a networked audio device, a HAT is not a networked device on its own and doesn’t combine Roons software this is on a user built SBC. Calling HATs Roon Ready really is incorrect terminology and is why they don’t show up under that section. It’s a marketing misnomer they really should be Roon tested like DACs are. They don’t have Roon api code in them to my knowledge therefore are not Roon Ready.

3 Likes

Exactly, the “Study” and “Bedroom” devices listed in James’ Audio section are the Roon Bridges (the Raspberry Pi’s) which will be listed separately and are technically neither Roon Ready nor Roon Tested simply because they are not actual Audio devices.

That’s not the cause.
There are a lot of bridges, which are Roon Ready.
I’m using e.g. a Holo Audio Red (it’s more or less a RPi4) with different OS (Holo Audio OS, Ropieee or HQPlayer OS)
In combination with the OS from Holo Audio it’s Roon Ready, otherwise not.
Functionality with Ropieee is much better (also used software and kernel.much newer) and so I prefer this.
So it’s in every case a hardware (with network connection and DAC or only as bridge) and a firmware, which RoonLabs can certify, if the manufacturer want’s it.

1 Like

I believe hes refering to using Roon Bridge software which Roon Ready devices do not they have Roon RAAT API built in. Roon Bridge software is for PC’s and SBC based kit. To be Roon Ready you don’t use Roon Bridge.

Just for giggles, I’ve dug out my old RPi3 with the IQaudio PiDAC+ and installed the RC3 candidate of the Roon Ready build (from the Internet Wayback machine).

It works…

2 Likes

I’ve replied in the other thread. It’s really unhelpful opening the same discussion points in two threads.

I had not meant the roonbridge, but an audio bridge in answer to Teun.