I’d like to give big shout to thank you for this fantastic distro and support you provide to us in Roon community!
Big, big thank you…!
Now, if I may ask for advise… when I was going through Roon KB, I saw this link about Linux Audio and inside it talks about how to get Native DSD mode which as I can read, my DAC, Gustard X20u is supported.
Henry, I believe you are describing an answer to my latest issue. I have successfully migrated all five of my RPi3s from the Raspbian Jessie Lite RoonBridge install to the DietPi. I must say that the install process through DIetPi is amazingly simple and fast.
I now have all five devices with the default standard “root” as host name and “dietpi” as password. However, I’d like to change the host name and password to a custom and more secure set and I see I can do that through the DietPi-config interface. When I do so, and reboot, I can’t login through the changed host name and password. Access denied.
After formatting and re-installing DietPi and RoonBridge on one of the RPi3s three times, I realize that it is not me. There is something one must do to enable a changed host name and password.
Henry references deleting some file within the Linux file system, presumably after doing the dietpi-config change to the host name and password, but before the reboot, to fix this. I need more specific Linux command assistance to follow what I need to do. Can one of you folks detail out for me and others? Thanks much. JCR
If you logged in before, your Mac adds an RSA key to the specific hostname/IP of that Pi. If/when the hostname/IP changes, your Mac flags this as a possible intrusion: the system you are trying to connect to, does not longer appear to be the same machine as previously.
The hostname/IP/key combinations are logged into a text file in your home folder. To access it, open Terminal.app and type
nano .ssh/known_hosts
Move your cursor to the offending line(s) and use CTRL-K to delete the line (you can delete all if you want to).
Save and close: CTRL-X, Y.
When reconnecting to your Pi(s), your Mac will now see them ‘as new’ and ask to to store the key to the new hostname.
@Dan_Knight@RBM I have a strange DPi question. I’ve got 3 DPis networked and working swell with Roon, 2 using Meridian Explorer2s, and 1 using an AudioQuest Dragonfly 1.2. All work perfectly with Roon.
I subscribe to the Berlin Phils Digital Concert Hall and Met Opera on Demand and stream audio from them via Shairport to the DPis. The DPis using the Meridian Explorer2s work perfectly. The DPi using the AQ Dragonfly plays mainly “hiss” with some audio present at a much lower level.
I’ve got all DPis setup the same using USB Audio DAC sound card and the filtering that disables HDMI and limits the processor. I’ve re flashed the SD card and reinstalled all software with the same results. I’m stumped.
Worked a treat!! Thanks Dan. FYI I was building it for a headless pi zero with an IQAudio DAC. Ended up building the image on a Pi 3 and then moving the SD card back to the Pi zero.
@fritzg
Depends on your tolerance for extreme tinkering I guess Control point choices for linux are scarce even on the big platforms. If you have a gui, UPPlay is the simplest. Not a renderer though.
The same developer did quite a bit of work to get some upnp functionality in mpd, now incorporated in (at least) the git version. So, if compiled with --enable-upnp, mpd has a upnp database plugin. Unfortunately this is the extent of the documentation. The gist of this approach, as I understand it, is translating upnp into something mpd understands, allowing it to serve as “client” and a sort of quasi-renderer of files served via upnp.
Using this I was able to get playback in mpd with a minimserver library. That was in Arch Linux though so whether this is possible in diet pi, not sure, but maybe helpful as a proof of concept. If mpd is available on diet pi and is compiled with --enable-upnp, I could see it being possible without too much work.
If I’ve misunderstood what you mean by client, disregard.
Since my Linux skills are minimal and DietPi is so intuitive for one lacking said skills, I’m going to wait until version 147 hits before I test the possible fix. I’ll let you know how it goes.
Neat! Sorry I didn’t mean to create work for anyone
Sorry if I was unclear @fritzg, the option first has to be enabled by the creator of the package. But with that, simply adding the following in ~/.config/mpd/mpd.conf should result in upnp servers showing in mpd clients.
database {
plugin "upnp"
}
The database plugin is set to “simple” by default so either change that, or add the above if no reference to database exists in mpd.conf. There are no options for upnp. The plug n play part of it should work straight away but…no warranty is implied!