BETA Release 2026.02

Audio Gear Talk RoPieee
42

Installation of last Beta, went smoothly on my RPI5 with Display2.

Thank you very much.

1 Like
43

Hi Harry,

I ran a few tests using Airplay 1 and 2 without any problems.

Regards

1 Like
44

Good morning Harry

Both screens ara up and running. No issues at all
Display 1 on Raspberry Pi 4 Model B Rev 1.4
Display 2 on Raspberry Pi 4 Model B Rev 1.5

Airplay no issues It’s working.

Tnx again

1 Like
45

All three units here are up and running with no issues noted. one Rpi3b with display and two RPi4s without display.

1 Like
46

all working well on a pi4 (beta build 3296)

model b rev1.4, 8gb memory, 16gb disk, wifi, no remote, no display

tried airplay 2, plexamp, roon

one question - why is pipewire listed as an available audio output ? (aplay -L and shows as an option in plexamp) … from what i can see pipewire is not installed

47

I’m experimenting with Pipewire, and this is just the Alsa compatible rerouting which is in place. It’s purely a configuration thingie, hence I didn’t saw the need to remove that.

1 Like
48

Hi,

i use HQP Embedded 5 and do not find NAA in version 2026.1, and not in beta 2026.2. I believe the problem is NAA 6.1. My HQP Embedded 5 works only with Ropieee 2025.10.2, i tried to update version 2026.1, and beta 2026.2, and new reflash SD-card with 2026.1, no one works.
HQP do not find NAA in all this versions, probably because is the NAA 6.1.

I reflash again a fresh 2025.10.2, is the only one works on my setup.

Someone know how to fix it? Thanks

49

Can you please keep messages like this message from the beta channel? This topic is only about the beta release.

Fyi NAA 6.1 requires HQP 5.16 as a minimum.

50

Hi,

I just pushed out another beta build…. I think we’re nearing releasing.

This one has some minor translation fixes, a fix for broken hotspot functionality during installation only with loooong network names (see here) , and still some work on the ‘force volume’ issue with the Topping DAC.

Let me know if something unexpected pops up.

Have a great weekend!

4 Likes
51

Heads up: for the Pi 4 (only) there’s another beta build incoming.

The issue with the ‘force volume’ is still not resolved, so I’ve pushed out another beta build with a fix so the user involved can test and verify.

4 Likes
52

Good morning Harry

Both screens ara up and running. No issues at all
Display 1 on Raspberry Pi 4 Model B Rev 1.4
Display 2 on Raspberry Pi 4 Model B Rev 1.5

Tnx again

1 Like
53

Updated 5 RoPieee’s (3 * RPI 3B+ and 2 * RPI 4B).
All working OK.
Thanks again for all the efforts spend on this magical piece of firmware.

54

Hi Harry,

I’ve just updated one of my units (Raspberry Pi 4 Model B Rev 1.5 with IQaudio Pi-DigiAMP+ hat). No problems so far, but FYI after the reboot it came back up at 100% volume which it’s never done before with previous updates. I didn’t notice and just blasted myself out of the chair :rofl:.

55

Can you send me feedback?

56

Hi @James_Fitzell

I think I know what’s going on. It has to do with some changes made with respect to the ‘force volume’ problem.

I’ll release a new beta asap to resolve this.

Thanks

1 Like
57

I’ve just pushed out a new beta release with the following issues addressed:

  • initial volume with HATs (ping @James_Fitzell )
  • native DSD support for McIntosh DA2 (ping @DDPS and @Chris.Ha )
  • another attempt at ‘force volume’ for USB DAC’s

Let me know how things are working out.

2 Likes
58

Thanks Harry, sorry I didn’t see this until this morning.

I see you have probably fixed it already, but before I install the update I rebooted (volume went back to 100%) and then generated feedback: 74ab5bfee9740bd6

59

I’m the Topping USB DAC user that Harry has mentioned, and wanted to give him a public thanks for sorting out the USB ‘force volume’ parameter. Hopefully others benefit as well.

1 Like
60

Native DSD playback works perfectly. The only issue I found is I started out by playing non-DSD content. Then I switched to DSD content. The screen display for the non-DSD content remained and never changed after that. Other than that, well done!

Here’s the feedback after doing that:

43bf896cc22fffcd

1 Like
61

Thank you very much for the quick turnaround and support on this.
This is incredibly helpful.

Great to see that Native DSD playback is now working. I’ll test it on my side and report back.

Really appreciate your help.