Mean focus this release has been improving the audio quality on the Usbridge. Remember, that legacy device we still support? Anyways, there were some reports about ‘clicks and pops’ hearable. At first I thought I couldn’t reproduce those, but after careful listening I could. Funny how our hobby works, isn’t it?
The rest are changes all over the place, including some nice performance improvements.
Here’s the changelog:
IMPROVEMENT: [display] make zone list adaptive
IMPROVEMENT: update Plexamp component
IMPROVEMENT: update UPnP player component
IMPROVEMENT: speed up configure step
IMPROVEMENT: update Linux kernel
FIX: cracks and pops on the Usbridge
FIX: LEDs behave different
As always I’d like to thank the beta testers for their test work and patience ;-).
@spockfish
I am seeing an odd one. I have my two Ropieee set to reboot each night at 1:04 to force Roon to stop playing so it can run a database backup. However, they have been up for days (since last update?).
Unit 1: Ropi-Zen up 5 days+13 hours - rebooted on schedule and then continuous on.
Unit 2: Ropi-SMSL up 1 day +13 hours rebooted on schedule the other night, but still streaming night music from Roon since yesterday. After setting it seems to daily reboot once and then forget.
I was just going to do a change/commit of the daily flop time and reboot them to see if everything comes back figured its worth the capture since something interesting might show up in the dump.
Raspberry Pi Zero 2 W Rev 1.0 with wifi and ethernet dongles
RoPieee 2025.05 (2450) [STABLE]
I click Pause play, clear the queue, then shut down the client. No need for all the rebooting. I have four servers with three subscriptions, but never more than one playing music at a time. I guess if you fall asleep with music playing, this is a way to stop it.
Yep, if anyone leaves it running, this method will stop play for the backups which run every few days. Then can just continue the auto-queue the next or some other day…
They were still playing today, so I manually rebooted them this morning… My guess at this point is that the time synch works first time (rebooted/initialized during day?) so, it ran the reboot at precise time (1:04am local), but for some reason the ntp synch target was not available when it came back up - my network/provider/etc… but it doesn’t circle back and try again for time-synch later if not successful synch?
I turned off the internal wifi on both.
I moved the backups to 3am so I could push one of the reboots back, so one at 1:04am, one at 2:04am.
Odd, was running for exactly one year – one since 6/6, and one since 6/8. Which ntp? I could set up a watcher and chart if ping is missing/slow which would indicate an isp maintenance issue.
I have last, stable version. Today is second day when my RP disappeared. Can’t enter to GUI. I see that RP is connected to router. IP is granted. Maybe this is problem with stable version?
