Introducing RoPieee - A RoonBridge-to-go image for the Raspberry Pi

Audio Gear Talk RoPieee
422

All, I’ve pushed out an update on the Remote Extension to the beta channel. This fixes the pesky ‘unknown’ bug when updating the software. If everything goes according to plan you will not notice this update at all.

You can see if this update is active if you check the version of the extension in Roon: it’s bumped from 0.2.0 to 0.2.1.

I really hope that with this fix we can focus more on the functionality in stead of getting the basics working in general.

Thank you all for your patience and feedback!

4 Likes
423

IMG_8253.JPG4032×3024 1.76 MB

Ok looking good I now have an album cover and name and playback position. After 10 mins or so, not timed it, it blanks the display that is good.

Still no audio on the digiamp+ but getting there and I see it’s 0.2.1 in the extension too now after a resarrt or 2 :stuck_out_tongue:

1 Like
424

ok then you’re good for now. The digiamp+ is on my list.

425

No 0.2.1 here, after several reboot/restarts.

426

just wait. it can take up 30 minutes

427

Ok guys I’m having a bad night. Loaded up the original beta image. There was a problem with the attached DAC hat, which didn’t allow the install to proceed. With that removed it installed, well something did.

I’ve got no touch screen display , nor any setting within the ropieee setup screen. ssh root@ropieee doesn’t seen to work as a root login so I can’t install the touchscreen from the command and nothing appears in the ROON extension list.

Clearly it’s me rather than anything else, but can anyone point me in the right direction

428

Hey Harry @spockfish

I’m on externsion 0.2.0 (it hasn’t updated yet, but will soon) but here is something different to previous reports.

I was running Ropieee Touchscreen fine yesterday after I did the update (the first progress bar update) and did the committ changes - I first had Roon playing to a single zone AND THEN enabled group zones and it was working.

Today I had Roon playing to group zones BEFORE I switched on Ropieee Touchscreen.

And I got the the unknown screen. So this is a bit different because this isn’t unknown after an update and the first reboot.

Mind you 0.2.1 may fix this too (I’m about to find out) but the above was a little different to yesterday’s reports (I think).

I’ll update this after I have 0.2.1 and try these 2 different sequences:

  1. Play to a single zone > turn on Ropiee > then enable group zone

  2. Enable group zone > then turn on Ropieee

Update 1: I notice the progress bar has now gone to the bottom of the screen but Roon Ext is still 0.2.0 for me. I tried the above 2 sequences and both are fine on this “new” version 0.2.0

Update 2: Okay after 30 minutes or so of playing , the Roon Ext is now showing 0.2.1. I did a reboot and the Touchscreen is frozen - I had group zone enabled. There is no “unknown” shown - it’s a black screen with no cover art, no album title, no song title, only the playback buttons and progress bar showing. The time is showing and works. I disabled group zone and the screen is still frozen. The Roon extension has disappeared. With a single zone, I did a reboot and it’s working again and then I enabled group zone and it’s working fine. With group zone enabled, I did another reboot and it’s fine. So it looks like it was the first reboot after it installed 0.2.1 that was a little buggy - the same ‘unknown’ bug except with the ‘unknown’ text, perhaps?

Update 3: I shutdown Ropieee, disconnected the power for a minute. Then with group zone playing, I powered up Ropieee again get the frozen screen (playback controls showing and nothing else). Something still a bit buggy with group zone it seems. Rebooting had everything working again, but it’s been a little inconsistent.

Update 4: I repeated update 3 above, and I get the same problem - after shutting down, disconnecting Pi power, and powering up Ropieee with group zones enabled, I get the same blank screen. Again, rebooting it fixes it.

Update 5: I shutdown Ropieee, disconnected Pi power. I had ONE single zone playing in Roon and then powered up Ropieee and the same problem. So it’s not an issue with group zones it seems.

429

On another note, whenever Ropieee Touchscreen is ready to go live (no rush at all) can I make a friendly request to have the album cover as big as possible (keeping it’s aspect ratio of course).

I would love to know how others feel but for me, having the album cover fill as much of the screen as possible is a greater preference than the playback controls and progress bar. I think this may be why there were a few comments that people are happy for the playback controls too be smaller.

I personally would be happy with just big album cover, album title, song title. Everything else is a major bonus of course.

The Pi is such a bigger screen than the old Squeezebox Touches, I would love for the album cover to be the main feature of the main screen.

I would love to know what others feel too.

I’m going to steal @Easysqueezy 's photo from another thread because I don’t have PiCorePlayer running but this is the view, with the album cover at maxiumum size and easier to view from across the room, on the same Pi 7" Touchscreen. I don’t believe there were many complaints about the playback buttons being too small, not that I’ve seen on all Picoreplayer forums.

IMG_0384.JPG2592×1936 1.66 MB

430

Ok when I went to bed last night the screen was in darkness after I assume going it timed out from not playing anything as play was stopped and my digiamp+ doesn’t work yet…but when I woke up it is showing this…reboot time is 5:04am

Sadly it is now no longer discoverable as an endpoint in roon. Maybe the audio settings have been affected too after reboot.

IMG_8254.JPG4032×3024 1.41 MB

431

Pfffff… ok. The unknown bug hits again after changing some stuff. This takes a little bit more thought. I had exactly the same when I woke up this morning.

Anyhow, you can fix it by just going into your settings screen (on the web page I mean) and ‘commit’ stuff (without changing anything). After the reboot that follows everything will work again.

I won’t push another update until this issue is solved, because it’s giving me a headache :wink:

432

Just an update on the above.

Update 6: I had to restart my Windows PC due to new Windows 10 updates. So obviously Roon Server was restarted too when restarting my PC. Anyway after restarting my PC and Roon Server, I repeated the above steps. I had group zone playing in Roon and THEN powered up the Pi. Everything seems fine now.

I’ve now powered down the Pi (while Roon is still playing to grouped zones) and powered up the Pi again, and repeated this 3 times to replicate my earlier issues. Unlike before, Ropieee working fine each time now, on booting up. Perhaps restarting Roon Server did the trick. It’s also fine when Roon is playing to a single zone and the Pi is then booted. I never did the ‘commit changes’ thing after having these issues after going to extension 0.2.1

433

ok good to here. i’ve tested the zone thing rather extensively, so I was surprised to read your issues.

1 Like
434

Eeep, Harry @spockfish - it’s back.

I just booted the Pi after power had been disconnected.

Roon was playing to 3 endpoints (via group zone), and then I powered up the Pi and this is what I get again (while Roon is playing to 3 endpoints)

IMG_0305.JPG3024×4032 1.82 MB

And if I reboot Ropieee via the ropieee.local settings page, then it works again. It’s a bug with bootup it seems. Sometimes it boots fine, sometimes not.

435

There’s another thing: you’re playing with 3 zones. I’ve tested it with 2. Can’t imagine it makes a difference, but still.

But ok. to be clear on the booting stuff: when you boot via the ropieee.local settings page, you just hit ‘reboot’ right? Not via first ‘commit’?

436

Correct, after 0.2.1 I haven’t hit the ‘commit change’ button once. Only rebooting via the ‘reboot’ button.

I only saw this blank screen with 3 endpoints in the last instance. All previous instances (the same blank screen) were with 2 group zone endpoints.

Same thing - only after a proper boot (after power had been disconnected). And the problem disappears after hitting the reboot button.

It also happened, earlier as I mentioned, with a single zone.

And in all these cases, there is no HAT and no USB audio used - Ropieee is just a control point in these instances and it only happens for me when roon is already playing to the endpoint that is setup in Ropieee setting, and already playing before the Pi is powered up.

437

I seem to be stuck at the playback screen with no iso displayed host buttons and time bar and clock. Even though roon is playing away and indicating so. Basically what @dabassgoesboomboom posted as a pic and eerily with the same 1:12 ------- 4:23 time showing :confused:

Also the extension is no longer showing either.


438

eep :scream:

Good thing I posted the photo otherwise we wouldn’t identify the common time position.

Hopefully that helps Harry

439

ok… so you’re saying:

  • when rebooting via ‘reboot’ button everything works
  • just power down/power up does not work

?

440

Yep, it’s only an issue when powering up, for me.

I can shutdown from ropieee.local, no problem, but after I disconnect the power and power up again I get that blank screen.

Music is playing fine to the endpoints (same as wizardofoz) and I can still access ropieee.local.

When I reboot from ropieee.local, while Roon is still playing, it starts working again.

Regardless of one zone or group zone, I’ve seen the same problem with both cases, as I noted earlier above

441

Ok. I’m gonna test that. I never disconnect the power. Still can’t imagine what the difference is, but hey :wink:

Is this for you 100% reproducible? As in: every time I go through this cycle I end up with this frozen screen?