To be honest I have found no issues with either, but tend to opt or the most basic automated setup and ropieee seems to fit that requirement nicely, no terminal needed, no monitor and keyboard needed and no network configuration needed. If running a hat just set in the web GUI.
The lcd which is still in beta is getting there too, and while thee is still some tweaking to be done it’s pretty much there too.
I like the ropieee touchscreen support but don’t like lack of Spotify connect hence I use ropieee as a remote and dietpi with roonbridge and Spotify connect on another RPi. means I use 2 RPis but hey they are cheap enough and the dietpi one is hidden behind the screen.
The DietPi beta for x86_64 could potentially be interesting if it were possible to install RoonServer instead of RoonBridge. In that case, using linux to run Roon on a ROCK-incompatible system might be possible (or alternately if one wanted something almost as simple as ROCK, but with a bit more configurability).
@Dan_Knight, any word on what it would take to add RoonServer to the software options for x86_64 systems? I know little enough about linux to even estimate the level of difficulty, especially considering the wide range of x86 system configurations and drivers compared with something like an RPi.
I did not had that much time this week, so during the weekend I’ll write an introduction which also ‘explains’ the name
Anyways, I think the most important thing to mention (for this thread at least) is that RoPieee and DietPi are totally different beasts. DietPi is a very versatile distribution with a lot of functionality (and I love it). RoPieee is actually not a distribution. It has a single purpose, acting like RAAT-capable end-point, where the target audience are those people that do want to run a cheap endpoint based on RPi hardware, but don’t have (any) computer skills.
So this is for example the reason why functionality like Spotify support will not land in RoPieee, at least for now.