TommyD,
any observation of your testings that you could share already?
Thanks
Stefan
I managed to get WiFi working on my Pi 4 last night. The Pi has software version 311, but I had to tinker over SSH some: The CPU revision didnāt match the one that maps to rpi4 in /opt/RoPieee/lib/get_hardware_model. Running cat /proc/cpuinfo | grep 'Revision' | awk '{print $3}' outputs b03111.
I edited get_hardware_model to add in this as an rpi4 and all the wifi configuration options appeared and worked.
4 Likes
OK, so Iām doing something wrong: new Pi4 B (4GB) with Ropiee Beta (showing v311-1) but not appearing as a device in Roon Core configuration. Web interface is working fine. What am I missing?
Did you connect your DAC to RPi4? Had the same issue, but connected DAC and Roon saw RPI4 immediately.
Yep - USB MQA DAC (Meridian Explorer 2), so should hopefully have shown up immediately.
Hi @Skaffen,
Thanks for this! When Iām back from holiday Iāll add your findings.
Iāve got already a new detection mechanism in place (which just looks at the FDT loaded), but I did not had the time yet (thereās plenty of other āmore importantā stuff on the list) to replace this.
Anyways, thanks!
1 Like
None whatsoever - machine is on the network fine (311) but doesnāt show up in Roon. DAC doesnāt show up in ALSA - works fine with Ropieee/Pi3
Can you send me feedback so I can have a look in the logs?
Sorry Harry - where do I do that?
Go to the advanced tab in the web interface and see the button below right.
Guys,
Iāve pushed out a new update (313) to the beta channel. Biggest change with this release is support for the touchscreen. Furthermore some āunder da hoodā stuff necessary for the Pi 4.
Nowā¦ this is a rather delicate update. It requires several cycles, so you need to be patient.
For those with a screen that canāt wait, hereās a new image: http://image.ropieee.org/20190728-ropieee-ose_rpi4-beta.bin
Enjoy!
3 Likes
Yes! Itās working! Thanks Harry. 
1 Like
Awesome @spockfish. The previous build didnāt boot with my newly arrived Pi4, but this image worked. Thank you.
A very minor āissueā: when playing an album of which the album cover is missing, Ropieee gets stuck showing the previous album cover. Just mentioning it because I noticed it (I check final mixes of music I mix for myself and others in the living room as āregular musicā, album cover is always missing in other words), not because itās very important.
I have a feature request: I would like to have the option to make the clock a bit smaller, or to turn off the screen immediately after Roon quits playing. This might be a highly personal request, but I have trouble accepting the passing of time. The big clock now shows me Iām wasting my time watching television instead of making music. 
Oh wonderful, just noticed the āblank screenā option. Skip my last request, hee hee. 
However, when I turn off my set with my Logitech Harmony, the DAC is turned off first. This causes Ropieee to show a āno DAC connectedā message. This message does not fade to black after a while. I donāt know if itās supposed to (Iāve never seen the screen with a Raspi 3), but Iād like it to go to black after a while.
I need to look into the album cover stuff. This did not happen on the Pi3, so this seems a regression.
Did some more testing:
When I swtich from album with cover to album without cover, the previous cover art gets stuck. Skipping or stopping playing doesnāt change it. When I wait until the timeout (clock or black screen), and start playing again, the right (missing) covert art is shown.
About the other thing: would be an idea to add the option ignore āno DAC connectedā errors in the web config, so that it goes to sleep without error when I turn all equipment off?
Another finding: if I close the Roon windows app, the touch screen briefly (for 1 second) shows a āconnection failureā, and then shows the album cover screen again. Playing is not interrupted.