Release 2025.02

Audio Gear Talk RoPieee
1

Hi,

Let’s start the weekend with a new RoPieee!

As usual with ‘stuff all over the place’, but I think that the work done on Squeezelite (LMS) stands out: this has been done in close corporation with some folks on the LMS forum (thanks @CJS !).

Here’s the changelog:

  • NEW: auto-update firmware on the Pi 5
  • NEW: Squeezelite: enable downsampling
  • NEW: Squeezelite: support client side DSD decoding
  • IMPROVEMENT: update Linux kernel
  • IMPROVEMENT: slow down a bit on the Pi 5
  • ENHANCEMENT: update Squeezelite component
  • FIX: LEDs are inverted on Pi5

As always, the update will show up on your device(s) in the next couple of hours.

Enjoy and have a great weekend!

21 Likes
2

works without any issues (RPi 3) :clap:

1 Like
3

I installed and tested new stuff :slight_smile: I’ll write a few words afterward.

Donation in progress!

1 Like
4

One thing worries me:

Sometimes the OSMC remote controler works only in the vol.+ and -.
Play/Pausa and Stop features doesn’t work.

After restart remote works well for 30 min. Maybe this happend after suspend mode?

I set the same zone in RoPieee and in Roon Server, i.e. “Rone”.

The extension was correctly detected by the system.

Feedback: 197b7e671a341276

After reboot: a43a9aac79d32aaf

5

with 2025.02 (2160), Lyrion/LMS doesn’t seem to see my Ropieee endpoint.

It did with 2025.01 (2045).

6

Have you tried providing its ip address?

7

Yes, I’ve always hardcoded the “fixed IP address” of the LMS server on Ropieee’s Services tab.

LMS has never had any problem seeing Ropieee before, so it’s odd.

9

Previous feedback (72fa4398b92fe2de0) was sent with DAC switched off, which might confuse.

New feedback sent with DAC switched on: 248663355cee700b.

Lyrion still not seeing it. Roon RAAT, and Spotify Connect, do see it.

10

Only one of my 4 Ropieee devices needed the IP set for Squeezelite to work, the others were picked up automatically.
Not sure what the relevance of that is in truth

11

Thanks Michael, that seems odd.

But, in my case, it’s not seen even with the IP set (which it always has been).

12

I have never needed to set it until the first beta of 25.02 was released. @spockfish said something about a newer release of the Squeezelite library.

1 Like
13

In case it’s relevant, Lyrion can still see my other Squeeze clients: Boom, Receiver, Wiim.

14

Hi Calum,

I know what’'s going on…

Squeezelite, as opposed to many other services, tries to open the audio device even if there’s nothing to do (play). However, if your DAC is not powered on, or another service is playing, this fails. That results in a restart of the service, but there’s a limit on that.

That limit is new in the last release, which makes the difference in behaviour.

You can verify this by:

  • turning on your DAC
  • reboot RoPieee
  • play audio only via LMS

I’m pretty convinced this works - it’s also the reason why for other people this ‘just works’ (also for me) as the user flow is different.

Let me know. In the mean time I’ll try to come up with a decent solution for this.

Thanks

1 Like
15

Yes, that was the issue, thanks Harry.

It makes sense: my DAC, headphone amp, and Pi are all powered from the same mains power strip, but the DAC & amp have their own power switches, whilst the Pi doesn’t, so the Pi generally boots before I have switched on the DAC.

Following your suggested sequence, things now work as they used to with previous releases; thanks!

With that Squeezelite caveat…

:+1:

RoPieee 2025.02 (2160) [BETA]
Hardware: Raspberry Pi 4 Model B Rev 1.4; 4GB RAM, 16GB disk
Network: wired ethernet
Audio: USB DAC (TEAC) — Roon RAAT, Spotify Connect, Squeezelite
Display: no
Remote: Flirc — Roon RAAT only

1 Like
16

Harry did you see my feedback? This is Roon problem with remote controler or RoPieee?

Regards

17

I can see you’re using the remote control. Everything works expected, except one thing:

Besides volume control (up, down) I only see another command being sent, so I assume that’s play/pause. However, this is indentified in RoPieee as an unmapped key (it reports as F2) which is correct. But it also results in being ignored.

So you are saying that it works for 30 minutes after a reboot? That seems really strange.

18

Yes, about 30 minutes or less. Pausa/Play also worked. Same as Stop. Additionally, song switching (next and previous) worked. I have the impression that after some time the dilation goes into suspend mode and stop responding, except for vol. + and vol. - button.

19

Indeed I can see that after the reboot for the first 30 minutes or so the normal keys are being received and after 30 minutes it starts sending an unmapped key (F2).

What do you mean with “dilation goes into susppend mode”? Who goes into suspend?

20

I mean the extension in ROON/Settings/Extension → RoPieee Remote Control.

Maybe it’s something else?

If You want I manage new test and feedback.

21

No, this has nothing to do with the extension.
I had a quick look, but ‘KEY_F2’ is send when the battery is low. So I think that’s your problem :slight_smile:

1 Like