Yep, I gave up on this after a few days, not worth the inconvenience. Also found it a little buggy and inreliable.
I’m not able to get it to run. Off to try PiCorePlayer. If that’s a bigger challenge than I’d like, back to RoPieee. RoPieee seems to work well and it sounds good.
I have assembled three RPi4’s with RoPieeeXL. I don’t know how any other OS could sound any different or better.
With no WiFi support, the iPhone and Android apps are only to install Roon Bridge. Not sure why we have to do this as a separate step… perhaps for legal reasons, but the VitOS app is useless otherwise. Well, I guess it does have a “Reboot” button.
However, there’s nothing easier for getting an endpoint running. That’s impressive.
Because the license for Roon bridge forbids it to be redistributed by anyone other than Roon so it has to be downloaded from Roon servers by the user and
The box with the “KODI” logo is a Raspberry Pi 4 Model B/2GB. The VitOS installation went without a hitch. The default login for SSH is root/root (thanks, Neil). I did get some errors about the “which” command being missing when used the Linux installer for Roon Bridge (armv7hf). I could probably have ignored this error, but to be safe, I created a “which” command like this:
printf '#!/bin/bash\ncommand -v $@\n' > /usr/local/bin/which chmod +x /usr/local/bin/which
After doing that, I had no problems re-running the Roon Bridge installer. The VitOS O/S comes pretty bare, so I did find it helpful to add alsa-utils and htop. Here are commands for doing that (in case you’re not familiar with Arch Linux):
pacman -Sy pacman -S htop alsa-utils
The only other customization I made was to install a CPU temperature monitoring script. Helpful to make sure that my Flirc case is doing its job to keep things cool:
curl -Lo /usr/local/bin/cpu-temp ws-e.com/cpu-temp.sh chmod +x /usr/local/bin/cpu-temp cpu-temp - CPU temp : 47.2'C : 117.0'F
The real-time kernel in this build does not seem to support the Linux hardware clock interface, so if curl throws errors about SSL Certs, you may have to manually set the clock. If you’re managing your VitOS from a Mac or Linux host, you can set the date/time using something like this:
MY_VITOS_IP=192.168.1.100 ssh root@$MY_VITOS_IP date $(date -u +'%m%d%H%M%Y.%S')
Of course, use the correct IP address for your Raspberry Pi. This is not terribly precise, but it will get the time/date set within a second or so without much fuss.
With that out of the way, on to a description of the rest of my little headphones rig.
I’m powering the RPi4 with the $8 official Raspberry Pi power supply to minimize compatibility issues. The USB signal goes into an iFi Audio micro iUSB3.0 power/signal regenerator. Crucially, the iFi relieves the RPi4 of the responsibility for powering the DAC. USB ports on the RPi can handle a load of up to 500 mA, but recommended loading is only 100 mA, which is not enough to deliver best sound from a USB DAC.
The iFi iUSB3.0 provides a clean 5V power output and a separate power + data output. I’m using the power-only output to run my headphone amplifier, while the power + data output goes to the Khadas Tone Board DAC. For a headphone amp, I’m using the iFi Audio micro iDSD. Yes, the iFi has its own internal DAC, but I prefer the sound of the Khadas, so I’m just using the analog input of the iFi. A little strange, but it works brilliantly.
Headphones on rotation include the Audio-Technica ATH-M50x pictured here but also Sennheiser HD600/HD650, Grado RS2e, Status CB-1, and a few IEMs. I’ve discovered that the Tone Board DAC sounds best when fed a DSD64 input signal, so Roon Core is busy handling the upsampling from another room. I have just enough CPU power to deliver this upsampling without falling behind.
I do wonder about the business model behind Silent Angel VitOS and if there will be any updates to the O/S. The mobile app looks good and seems to be well maintained (at least for now). This is all disposable tech, I suppose, but it’s the best sound from headphones that I’ve achieved to this point, so I’m happy I gave it a try.
Connecting Core directly to a USB DAC is convenient, but it generally results in the worst sound quality. If sound quality is of little concern in your setup, by all means, but folks who are interested in stuff like VitOS likely care a lot about how things sound.
Yes. VitOS is about sound quality, not convenience. If you the convenience of Wi-Fi is of higher priority than absolute sound quality, then it’s not a great choice.
I’m always surprised to find audiophiles who are happy to spend $1,000 to run dedicated mains lines to their audio system yet refuse to spend $200 for a dedicated Ethernet run. To each his/her own…
Yes, I am tried to set up p4 with VitOS. I am feel good with the SQ which VitOS provided. Let me have more interests to build my own custom realtime 64bit arch OS.
Good luck with your build. It would be nice to have a 64-bit RT kernel for the Raspberry Pi Compute Module in our Allo USBridge Sig.
I have tried VitOS but see that RPI 4B/8GB after start booting shows “Require new software version for this board”.
I prepared SD card according instructions on http://www.thunder-data.com/vitos-for-rpi4
several times but the same result.
Can you please advise what can be a problem?
Could you share some screenshots of the OS showing what other apps/protocols are supported?
Their website mentions Airplay 2 and proper Spotify Connect for their Z1 server running VitOS .
Because we don’t want all to rip up our houses to run a cable upstairs to bedrooms where raspberry Pis as endpoints become useful streamers. WiFi is far more convenient for installs like this where no other networking kit is needed. I tried vitos it was good but not good enough to do away with convenience.
Do you have a cable TV outlet in the same room? If so, I’ve found MoCA (Ethernet over CATV coax) to work very well.
Perhaps AirPlay and Spotify Connect are features that are supported only by their $1,600 Z1 server. I do not see evidence of these in the free edition of VitOS for the Raspberry Pi.
Did you have a chance to obtain objective measurements, comparing VitOS to DietPi and RoPieee?
Objective? No, but subjectively, RoPieee < DietPi < VitOS in terms of sound quality with a USB DAC and wired network connection.
Call me suspicious, and I am not making any allegations, but is this software company a legitimate business? Has anyone checked the code for spyware? Is this likely?
I had some issues on my 8GB RPI. On the 2GB version it works like a charm.