You've to use the version for the RPi4/3. After installing, activate NAA:

No, Jussi's NAA OS has only NAA included, but no Roon Bridge. But you can also Ropieee and activate here NAA.

The good thing with the Red: You can use it for multiple services at once. For you (and also I do it): (i) as NAA client: Roon --> HQPlayer --> RED with output 1 (for example USB to May) (ii) as Roon endpoint: Roon --> RED with output 2 (for example I2S to May). In the second case, the Red will...

Mmh, release notes says: NAA 5.0.0-59, but HQPlayer shows 4.5.0...

Great, multi service is back, but NAA doesn't get the update to the current version.

On the bottom the DAC itself, above the May power supply and on the top the Envy.

You shouldn't place something on the top of the May, but take a look into the manual: May DAC --> May Power supply --> headphone amp like your Envy.

Sure, I'm owning since a longer time the Red, the May and HQPlayer. Also used different distributions (RedOS, Ropieee, Jussi's NAA,...) for the Red. And surely my HQPlayer is installed on a dedicated PC with an Intel i9. Mostly I'm using upsampling (and filters for some cans) to DSD256 or...

Do you've also the version 2023.04.15 found?

For me, it doesn't makes any sense to install HQPlayer on a RPi4 board. Only low level filters for pcm are working there without dropouts. The only argument for the HQPlayer OS on the Red, can be that you'll get with it newer drivers btw. more updates than with the NAA image.

And here you can use NAA and RAAT together in using different outputs?

For me the problem is: - The current Ropieee is crackling in using NAA or RAAT with the Red - The new RedOS don't allows two services at once - Jussi's NAA image has only NAA included

What to write? Bliss looks like a new one and the communication was fine. So I can him highly recommend as seller.

For the T+A I would (if SQ stays on the first place) prefer as streamer a NAA client like the Holo Audio Red, which is able to send native DSD1024 to the DAC. The RS 130 will output DoP and can't use together with HQPlayer as NAA client.

This is, how the DMP-A6 is designed. There isn't any deep sleep (with ethernet enabled) and so you need IR for starting it and no firmware update can change this behavior. But what I'm using: A triggered power outlet, which I can trigger over the network and set the DMP-A6 to go online after...

I prefer RopieeeXL, because there you've the newer NAA compared to the Red OS and you're able to use the Red in parallel as Roon endpoint or use it as two endpoints. But it depends on, how to use the Red in your system.

I would prefer here Ropieee XL or the HQP OS in using the Red as NAA client, because the Holo OS included an outdated NAA client version. Also you've to install and buy HQPlayer for upsampling to 1.5 MHz.

Using the Red as NAA client you've to take the way through Ethernet.

If you're only using the Roon bridge, than you'll the same versions on Ropiee and Holo OS. Some people are meaning, that there's a better SQ in using Gentoo player, but I don't agree with them.

With the Holo Spring 3 KTE, I don't see an advantage in using I2S instead of USB and so you can eleminate also the Gustard. The Red used as Roon endpoint (and connected to the Spring through USB or I2S) can perhaps be an upgrade (I've the Red connected to my Holo Audio May), but for you I see...

Sure, you can use the NAA OS, but I'm using the Red as two Roon endpoints. One with hqplayer and the other directly from Roon without hqplayer. Also sometimes my Red is used as UPNP client.

The problem with the firmware/OS from Holo Audio is for example the old NAA client. I prefer here RopieeeXL, which works without any problems with the Red.

If you're using the device as Roon endpoint, than all is fine. But if you want to use it as standalone streamer or video player, than the internal software is far away from perfect...

You can't install on it your preferred apps, because the OS is android based, but not open and there isn't any play store. Also actually it can't used as DDC. The base of the OS is a very old android 7.1 and there are not any planes to update it.

Again: I2S LVDS needs connected to the internally I2S bus, which the HDMI video out isn't. Changing pins per software is a complete different thing. In the case of the eversolo, you'll need an extension board and a new firmware. Anyway: The integrated hmdi out in the eversolo is the unique...