Hi Harry,
The feedback: 7f8b479c907e24f3
Kind regards, Frank.
1 Like
So if we stick with a stable we should be ok for now I assume. It’s a real PITA to reflash mine as taking the units apart is troublesome due to the cases I have in use.
Sorry had some other personal things taking up time too so not managed to get much done the last few days 
Just to be sure, the new versions do not support USBridge, right?
Kind regards,
Stephan
I’m not sure what you mean with ‘new versions’. This is the beta channel, which is meant for testing purposes.
But in general: the USBridge is supported.
Hi,
An update on the crashing 3A+ when using the beta: after extensive debugging and testing (a huge shout out to @Frank_M because he’s been very helpful in that!) it’s clear that the issue is caused by a specific kernel version. It is one of the latest patch versions, and when we go back a few patches everything is working ok. I’ve filed a bugreport with the Raspberry guys.
So, the good news is that we can explain ‘why’. The not-so-good news is that we had to go back a few kernel versions on the Pi 3 build of RoPieee: which means, for now at least, we can’t keep up with the kernel version as used with the Pi 4 and 5. I’m not sure what to do with this… dropping support for the 3A+? For now I’ll wait out and see what the Pi guys have to say about this..
I’ll release a beta build somewhere this weekend which corrects this (again, for now). Meanwhile I’ve managed to fix 2 reported issues with the display as well, so those will be in that build as well.
Oh, and I’m ordering a 3A+ myself today, because that way I don’t need to bother other people to do the testing for me 
Thanks
5 Likes
Like always You are our RoPieee/Roon Hero 
1 Like
OK Ive done bunch of LCD unit refreshes and seems still have some issues with a couple of displays that some show boot up text scrolling to a point then go ape s#it scrolling so fast its a blur then blank never top show anything again unless rebooted.
feedback is this one 12e3796bcf3824ca
another unit no display at all but its showing it in the tabs
feedback for that one here d901ce99be0244aa
these have been very stable units up until about April / May time frame.
Both are running stable, so this isn’t related to the current beta build…
Anyways, I did have a quick look. The logs seem fine, except that on the RPi3b-MancaveLCD I see quite a few undervoltage detected. The RPi3b-DiningLCD keeps on reporting that it can’t find the Roon server.
Thanks
Hi all,
I’ve pushed out another beta build. This is a result of the last few days spending time on figuring out what was going on with the unit of @Frank_M.
I also got myself a 3A+, because on that unit Frank could reproduce the issue rather quickly.
Long story short: I hope we’ve fixed it. I can’t reproduce it, but that doesn’t mean you can
So go out and test. I’m especially curious about Pi 3 systems…
Oh. And I managed to squash 2 display related bugs: one where the volume control showed up rotated, and the other one about cover art showing the previous one if there isn’t any.
Enjoy!
4 Likes
yes I reloaded and at the time of rebooting the beta had not materialised… any who…the mancave I stripped down and reconnected everything and its OK…YAY… and the Diningroon one seems to be ok for now again too.
Anyway Harry enjoy your holidays.
2 Likes
Hey Harry,
I’ve been running the beta on several devices (expanded it to my only Pi3 too).
During this I’ve noticed two other things that I wanted to mention but am not sure are bugs (one of them may not even be a Ropieee issue).
The first is simple, and possibly by design. When going to the devices page the “version” status shows the currently configured Beta/Stable state, rather than the actual version that is running. It’s not a big issue, and is rarely even going to show up, but it means that my Pi3 was showing as Beta while still running the old stable.
The second issue could be user error or a faulty device, but I thought I’d test out your new USB remote features. I bought this: Vaydeer Multimedia Controller Knob with One-Click Mute Function and 3 Volume Control Modes Audio Adjuster Volume Controller for Win7/8/10/MAC : Amazon.com.au: Computers with the intent of using it on one of my ropieees. It’s detected successfully, and the volume control works, but while (or shortly after) adjusting the volume the ropieee completely loses the RAAT stream. It then skips tracks and from that point on won’t play any music until I reboot the ropieee. Removing the remote sent everything back to normal 
. I know you’re going on holiday, but let me know if you want me to capture anything before I return it to amazon.
Thanks,
James
Hi James,
The first one is … sort of by design. What you see is the selected channel, not (necessarily) the active channel. That’s fixable, but it always end on the bottom of the list “as the user only sees this for a short period time after switching channels”. I need to make sure that at some point it comes at the top of the list
The second one I’m highly interested in! So yes, I’d love feedback! But there’s a caveat: coincedentaly my VPS provider is doing maintenance today. That means that my VPS is (still) offline, so the feedback wouldn’t make it 
I’m not sure how long you can keep the device, but my hope is that my server comes back online somewhere by the end of the day.
Thanks
Heee @James_Fitzell
Infra is back, so could you please send me feedback?
Use the device a little bit, and when it goes crazy send me feedback without rebooting.
Thanks!
1 Like
Done. @spockfish bbfcb89e0662ca17
I rebooted the device, then plugged in the remote, hit play, and then changed volume… it almost immediately had a brain fart and then I generated feedback.
The only thing that you might see is I tried to generate the feedback twice, the first time I used my phone, and after 10 minutes of “generating” I gave up and used the PC instead.
@spockfish two quick updates.
After generating the feedback I left the device sitting as is… and its CPU temp has gone up by several degrees and stayed there. I’m guessing the remote process is chewing up all CPU?
I also just did a different test (feedback 832377a24052b645)
This one is a little different:
- rebooted pi with remote connected
- hit play (using remote) which worked
- hit back/forward using remote… also worked
- music played fine up until I moved the volume slider one notch backwards, then within a second or two the music stopped
- let it skip through the next tracks and self-pause
- then unplugged the remote from the USB port, and hit play (which worked again)
- generated feedback
So, if you don’t use the volume slider… does it work then normally?
And I’ve looked at your logs… the device seem to behave correctly… but I see that Roon starts doing weird things: it stops, loads, plays, stops, loads, plays etc.
Have you also tried rebooting (just to be sure) your Roon server?
Correct. I will do some more testing (i.e. listen with it connected over a longer period without touching the volume) but from the testing so far:
- if I don’t touch the volume knob then everything works perfectly
- if I touch the volume knob then it breaks within seconds
And yes, I rebooted the roon server as part of my initial diagnosis (with no impact to the specific bedroom endpoint behaviour). I’ve also had music playing in another room at the same time as the bedroom endpoint breaks. I’ve got a screen on this device and I agree it looks like it’s sort of manually skipping (the Roon queue reflects this too).
But in reality I’m not skipping them, and it never plays again (even if I then use my phone to start a new album). From the point it breaks onwards not a single sound is heard… and the display shows 0 seconds of music and then skips through tracks like they’re unavailable (whether it’s cloud or local). Maybe it’s just a broken USB remote, but the CPU temperature change seems like a clue that some sort of process is pinned on the endpoint.
Hey Harry, I just did another test and had some fascinating behaviour (all hopefully captured in feedback 280f445ebf13facd)
The USB remote is plugged in, but I have not touched it.
I used the display to hit play, and then I used the display to change volume (from 26 to 15ish)… it almost immediately stopped music (although the screen shows a progressing audio bar) and then it skipped to the next track, at which point the volume reverted to what it was at previously (26) and music continued. I repeated this behaviour twice.
I then use the phone to control the endpoint, and hit play (again it started back at volume 26) and then I used the volume slider on the phone to drop to 15). It immediately broke the audio on the endpoint, and then I watched the phone skip through the next 3 songs before it displayed “too many failures, stopping playback” (unfortunately I wasn’t quick enough to screenshot it but I’ll do this later).
I think it’s fairly safe to say that this is related to volume control, and not specifically your fancy device …
Have you tried restarting your Roon server?
Yes, I’ve restarted the roon server. The problem is 100% tied to the USB device, even though I can trigger the failure without interacting with it.
If I unplug the USB, volume control is fine (via phone or display)… if I plug it in and use volume control in any way, it breaks.