That happens if your device changes (for example a reinstall) you can get around it by doing:
ssh-keygen -R device-ip-address-or-hostname
since you are ssh:ing using the hostname, VitOs probably got a new IP-adress that ssh doesn’t know about and warns you about it.
Thanks for the suggestion, will try it out!
The IP address remained the same. I suspect the recent updates of my Mac to cause the problem.
Regards, Paul
It worked, Magnus, thanks! Though I had to play around with the hostname as this seemed to have been changed.
Great thread. I’ve setup vitos on two pi4 endpoints today, one wired, one on 5ghz strong wifi. Listening to both local and tidal files. Other endpoints have been dietpi, ropieee and volumio, mix of wired and wifi. Not yet sure if I hear differences, but am planning to do more listening with vitos (arch).
I don’t trust their app method of installing via app. Am installing from Roon manually.
I did that too, the first time I set up a VitOS endpoint. I’ve been using the app since. Both seem to work. I’ve detected no malicious behavior so far. And, I’ve reported the issue to the VitOS guys.
Thanks David, Since Roon provides a great script for installing RoonBridge on Arm, it just seems odd that VitOS has you download an app to basically do the same. Anyways, glad that you’ve found no issues with the app part. Good to hear.
Magnus, this is definitely the correct way to setup time/region on Arch/systemd systems, but just in case having the time daemon running might take some voodoo sound quality out of the equation, I am just running this:
date -s ‘2021-03-01 12:52:04’ [after using timedatectl set-timezone America/Los_Angeles]
Of course, I’ll have to adjust after power outages, and it won’t be super accurate, but trying to keep daemons to a minimum during bridge testing.
I’m fiddling around with vitos and archlinux.
The RT Kernel is installed and working fine, latest available.
Maybe in my spare time I can make my own VitOS-style build… time permitting
[root@Raspberry-Pi-4B ~]# cpu-temp
- CPU temp : 32.6’C : 90.7’F
@fatez nice to see some console here, you might try some of tweaks from scripts i’m using on rpi4 and let me know how it sounds? 
GitHub - maniac0r/rpi-usb-audio-tweaks
wow thank you so much!
I’ll get into your scripts tomorrow!
you could almost think of creating a small image for the community
Thank You @maniac, Your scripts are much more elaborate than my little tweaks in config.txt and cmdline.txt.
Looking forward to try them.
Maybe @David_Snyder will find time to evaluate Your work too.
@maniac sorry, technical noob here, please could you tell me how to install VitOS with your scripts on a SD card for running on RPi 4? Thanks.
Unfortunately Im a not using ViOS (except it’s Linux RealTime kernel) so i’m sorry but can’t help with step-by-step instructions here.
There are 3 shell scripts in root folder on github, those are taking care of optimisations.
First one stop unnecessasry services (i’m running raspbian and sometimes use it other way as streamer so i did not want to make it permanent in OS startup scripts) Basically if there is USB storage attached to RPi during boot the script will just exit. Then stops wifi interface if there is IP assigned on ethernet. Some tweaking of ramdisk size and other (kernel) parameters done here too. Some of the RPi settings will be applied only after reboot (CPU, RAM, GPU frequencies and Voltages), but all future boots will be already optimised.
As first one finishes it calls immediately second one:
Second one unloads all unused kernel modules and bind specific processes and interrupts to specific CPU cores. Sets RT and standard priorities to specific processes.
I’ll install VitOS onto a spare RPI4 and do a direct comparison, VitOS/RPI4-USB, vs Ropieee/RPI4/Pi2aes-SPDIF.
Before I allow this software to access my network, I was wondering if any users have considered why Silent Angel are providing free software, including a connection app for all platforms, surely their must be some benefit to Silent Angel? I.e. data collection etc?
A few Q’s?
Thanks
I disagree with this comment. Although I do run an endpoint setup, I only do this to achieve a silent source.
SQ outcomes depend on so many factors, including the quality of your Dac’s USB implementation, your network switch topology/quality, cables, the PC supplying the signal, etc, etc.
I don’t think you can generalise. Maybe that’s your experience in your system.
I think the DAC plays a bigger role than endpoint vs core connection.
This is worth a watch.
I went back to Ropieee, with my RPI4 and Pi2AES hat.
I’ve been playing with multiple variants of RPi (and other SBCs), and DAC hats over the past several years. Including many distros of Linux. For the past 3 years I’ve been and forever will be a fan of roon. I have some type of end-point in 6 different rooms in my house. Most of them are I2S based DAC hats on RPis. Up to this point, both Roon Bridge, and Ropieee have been my end-point client software of choice. They are both easy to configure, and once done, they just sit there and simply work, and work well. I use tablets mostly for remotes - both Surface Pros and iPads.
Last Fall I heard about VitOS and thought I would give it a try. I downloaded the image today and burned to a microSD card. Powered up the 4GB RPi and VitOS came right up. I installed the phone app and then installed Roon-Bridge. How easy was that! Connected one of my original TBs to the USB out of the RPi. Opened roon, enabled the TB and configured it to my standard settings.
Since I’ve only listened to a few DSD tracks in my shop, I can’t speak to any noticeable SQ improvements - or not. The TB is an exceptional little DAC for the money, and its sound is generally very easy to listen to. It doesn’t best my more customized Ian Canada DAC stack with 5 PSUs that’s in my main system and is pure joy to listen to. Before I can render some subjective sonic differences between the VitOS, and my other versions of Linux I need more listening time. That process will be more difficult since I can’t easily simply swap out the uSD card and change the OS on my Ian stack and do an A/B comparison. Of course I do it on the test RPi, but I prefer to use my best sounding system to listen for any nuances that VitOS may highlight. Does VitOS run on a RPI 3? Plus with anything new there’s always this nagging ‘expectation bias’ that simply can’t be overcome. Our minds like to play tricks on us.
BTW, my roon core is running on a ROCK-based NUC i3 and my Synology NAS serves up the FLAC files. Everything works beautifully!
