Release 2026.01

spockfish · January 23, 2026, 3:16pm

And as usual a big thanks to the beta testers and translators.

Enjoy!

JWC · January 25, 2026, 3:45am

Hi Harry,

Since this update, my RPi3 is having trouble playing 24/192 content. I have tried several tracks, and none of them make it past around 15 seconds. I have rebooted the RPi, Core, and Router, but there was no change. 24/96 content and below plays for hours without issue.

RPi 3b 1.2
Display 1
1GB RAM
Wired ethernet
USB output
2026.01 (3177) [STABLE]

Here is feedback following the reboot, then failing to play a 24/194 stream.
Feedback: 381cfdc76971dd6d

EDIT: As another data point, I have an RPi 4 with Display 1, ethernet, and USB output that plays 24/192 and 24/352.8 content without issue on the same network running 2026.01 (3180) [STABLE].

Many thanks for all of your work to support the Ropieee platform!
-Jim

spockfish · January 25, 2026, 8:50am

Hi Jim,

I can’t reproduce this. Tested on a Pi 3, equipped with display and content at 352.8kHz.

I can see an issue in your logs: dropouts, on the network side of things.

You already rebooted all the players involved, so I’m not sure what to make of this. What type of router do you have?

JWC · January 26, 2026, 1:36am

The router is a Linksys Velop mesh system (Wifi 6e version). The PI3 is wired to one of the daughter nodes, so formally, it’s an ethernet bridge (same as the other Pi4). Pretty fast Wifi 6e backhaul from node-node, though.

I’ve had stable 24/192 streams for 2-3 years, until the last update. Could there be an issue that the 1GB RAM on the RPi3 is a bit precarious after the change from 32 bit to 64 bit on the Pi 3? The RPi4 has 2 GB (and a faster CPU, and better-sorted USB, etc, etc).

Thanks again.

JWC · January 26, 2026, 1:59am

Well, I completed two more full reboot cycles of all components. The second one was a hardware reboot (pull the plugs) on all components, along with also reseating all network and usb plugs. That seems to have fixed it (streaming 24/192 for 10 minutes without interruption).

Sorry for the spam. I usually try not to be one of those guys that blames software before sorting all the local issues.

James_Fitzell · January 28, 2026, 6:24am

Hey Harry, I’ve found a bug (I think) although it’s relatively minor in impact and may have been around previously.

The issue relates to the display and only occurs when grouping players… when I group players there is always a “primary” endpoint (in my current situation this is “Lounge”) and then all the grouped endpoints (in my current testing this is “Study”). When I group these players my study display automatically switches to show the zone “Lounge+1” as expected… but an unexpected side effect is that the display is now showing (and controlling) the Lounge volume… not the Study volume. I can still interact with the Study volume via Roon (and/or HA) but while grouped as a secondary device it’s not possible to change the local volume via display anymore.

For reference, it’s technically impacting the beta rather than 2026.01 since most of my devices are in the beta channel and still on RoPieee 2025.12 (3173).

I haven’t generated feedback (I’m happy to but I doubt it’s that sort of bug). The relevant info is:

Raspberry Pi 4 Model B Rev 1.5
Memory Size 1GB
Disk Size 32GB
Official 7" Display 1
IQ Audio AMP+
LAN

wizardofoz · February 3, 2026, 9:31am

I’ve one unit that appears to be dead after updating no boot display nothing…I’ll try a reflash and do again. It has an IQAdIO digiamp hat output to speakers, rpi 3b and older original display 7”

Rene_Zwart · February 7, 2026, 2:58am

Hi, I have an issue (well two possibly) I’m using Ropieee as a Roon bridge for my USB DAC (ATM Fosi DS2 dongle) RPi is a 3B version.
1 - I can’t set it to a fixed IP number in a different Vlan. I can set it static to the DCHP issued number, but going from Vlan 1 to Vlan 2 and I lose visibility of the unit for direct IP access or ropieee.local, however my Unifi network system shows the unit on the old IP number and active.
2 - The volume is quite low. Is there a setting somewhere that allows a volume increase? Roon is at 100% and I need to crank the amp up beyond normal to get a listenable level - quite higher than for any other source.
Hope the info is sufficient, but please let me know if I need to submit more.
Thanks, René

David_Gibson · February 7, 2026, 3:37pm

Are you using the DS2 as a headphone amp or feeding to a separate amp? The Pi simply provides power to the DS2, so it doesn’t set the volume. The DS2 provides the volume control. If you’re using a separate amp there may not be enough voltage from the DS2 to drive the amp properly. Most DACs provide 1 to 3 volts to drive an external amp. There’s no data on Fosi’s website concerning the output voltage of the DS2. My guess it’s less than 1 volt.

spockfish · February 7, 2026, 3:59pm

Roon uses M-DNS heavily for discovery and other tasks. RoPieee uses M-DNS for the ‘.local’ address. Using vlan’s can be problematic in combination with multicast, so I would look at that.
What kind of volume are you using? DSP or Device?

Rene_Zwart · February 8, 2026, 3:05am

Hi David, appreciate your comments, thanks! I’m using the DS2 atm as a DAC feeding an Amp. I understand that it’s not intended for such possibly, but it’s replacing my Meridian Explorer2 in a secondary system (until I can replace it). All info about this dongle indicates it has a lot of power/volume so I thought it would work OK. Cheers, Rene

Rene_Zwart · February 8, 2026, 3:08am

Hi Harry, thanks for the response.

Your comment re use of M-DNS and multicast noted and I’ll need to read up on that.
I’m not using DSP or Device (Volume set at 100% in Roon).
Cheers, Rene

spockfish · February 8, 2026, 1:18pm

I assume this DAC has hardware volume control. Have you tried setting RoPieee’s ‘USB Force Volume’ option? It might be that it just is not set to it’s maximum.

thanks

Rene_Zwart · February 9, 2026, 10:15pm

That did the trick. Thanks!! Cheers, Rene