Volumio Streamer Configuration Tips

Thanks, will give it a try.

 

Volumio may overwrite config.txt, but userconfig.txt is preserved.

 

nice! actually where / what is the config file name for Moode if you don’t mind sharing?

 

I don't have experience, but try this:

The first time you ssh into Ropieee, instead of

Code:

ssh [email protected]

or similar, you'll want to

Code:

ssh [email protected]

using password ropieee

Since you'll be logged in as root, you don't need to use the sudo or su command at the start of lines.

HOWEVER: Here's what the ropieee author says about tweaking like this..

 

For those using Moode, it’s ssh pi@ipaddress and the default password is moodeaudio.

 

I just followed these instructions: https://www.superbestaudiofriends.o...treamer-configuration-tips.11017/#post-348809

The only difference is #1 and of course login to mode though SSH. I now use the web SSH moOde has built in. Once you open Nano it will create the file.

 

Tip: Not sure of your Raspberry Pi Model?

From your ssh Secure shell

Code:

cat /sys/firmware/devicetree/base/model; echo

Using that command, the systems I am using to test Pi tips are

Raspberry Pi 3 Model B Plus Rev 1.3
Raspberry Pi 4 Model B Rev 1.4
Raspberry Pi Zero W Rev 1.1


I've tried to find a similar command that identifies HATs consistently.

Code:

cat /proc/device-tree/hat/product; echo

works on my HiFiBerry giving "Digi2 Pro" but not Pi2AES, PiFi or on a 'HAT'less system.

 

ah ok so after looking at it Moode's config file is named "config.txt" and is inside the /boot/ directory. (as opposed to userconfig.txt in volumio). Or so i think. hopefully this helps someone else out?

(although, are we supposed to create a new file named userconfig.txt in /boot/ ? will this actually load for Moode?)

 

The pi2aes does not follow the “hat” specification. There is no ID eeprom on board.

 

Woland, that doesn't make sense. Well, it does, but the "echo" is superfluous. What you have written will...

1. cat (display in this usage) the named file

2. echo... something. A blank line here, as there is no input to echo.

Unless, of course, you wanted a blank line after your output

 

That's what it is for. Try it without the echo and you'll understand why.

 

Oh, ok... Intentional. Sorry.

$ I don't have that device/distro/file so I can't. I'm guessing that the file doesn't have a newline at the end so the output would look like this para$ <cursor>

 

I have Raspberry Pi 2 Model B Rev 1.1 if you need to test anything. I use moOde, not Volumio, but both use MPD and similar systems.

 

TIP: Disable Raspberry Pi HDMI video output

Continuing with the theme of disabling unnecessary parts of the pi to optimize it for audio...

From your ssh Secure shell, test out the disabling command

Code:

sudo /opt/vc/bin/tvservice -o

If all is well, have this run every system start by inserting it into a startup file.

Code:

sudo nano /etc/rc.local

like this



Next time - a bit more complex but the most promising step of all - disabling USB ports.

 

TIP: Cut power to USB on Pi or PC

There's a lot of potential power use and noise from USB ports. Depending on the system configuration, we may switch off some all all of the USB subsystem and get benefits.

To do that, the first step is to ssh into the system, like in previous tips.

Optionally, we'll see if the hub is smart.

If it is, we'll install the uhubctl tool. It gives control over smart usb hubs, like the ones in Pis.

Optional Step
Test what kind of ports are available.

Code:

sudo lsusb -v | grep 'power switching' -B 1

On a Pi4b that shows hubs with per port and ganged power switching, so we will have some control.


To install uhubctl

Update system

Code:

sudo apt-get update
sudo apt-get -y upgrade

Install

Code:

sudo apt-get install make gcc
sudo apt-get install libusb-1.0-0-dev
git clone https://github.com/mvp/uhubctl
cd uhubctl
make
sudo make install

To see your current USB configuration:

Code:

sudo uhubctl

Here's what that generates on a Pi4b:

Code:

Current status for hub 2 [1d6b:0003 Linux 4.19.118-v7l+ xhci-hcd xHCI Host Controller 0000:01:00.0, USB 3.00, 4 ports, ppps]
Port 1: 02a0 power 5gbps Rx.Detect
Port 2: 02a0 power 5gbps Rx.Detect
Port 3: 02a0 power 5gbps Rx.Detect
Port 4: 02a0 power 5gbps Rx.Detect
Current status for hub 1-1 [2109:3431 USB2.0 Hub, USB 2.10, 4 ports, ppps]
Port 1: 0100 power
Port 2: 0100 power
Port 3: 0100 power
Port 4: 0100 power
Current status for hub 1 [1d6b:0002 Linux 4.19.118-v7l+ xhci-hcd xHCI Host Controller 0000:01:00.0, USB 2.00, 1 ports, ppps]
Port 1: 0507 power highspeed suspend enable connect [2109:3431 USB2.0 Hub, USB 2.10, 4 ports, ppps]

Why are there two hubs shown on a Pi4? The uhubctl docs explain...

To switch off all USB ports on a Pi4 (suitable for Pi2AES and other HATs)

Note: My network connection is WiFi, and was unaffected by the USB power changes. Let me know what happens with cabled networking.

To cut power:

Code:

sudo uhubctl -a off -l 2

If all goes well, you should see something like this:

Code:

Current status for hub 2 [1d6b:0003 Linux 4.19.118-v7l+ xhci-hcd xHCI Host Controller 0000:01:00.0, USB 3.00, 4 ports, ppps]
  Port 1: 0080 off
  Port 2: 0080 off
  Port 3: 0080 off
  Port 4: 0080 off
Sent power off request
New status for hub 2 [1d6b:0003 Linux 4.19.118-v7l+ xhci-hcd xHCI Host Controller 0000:01:00.0, USB 3.00, 4 ports, ppps]
  Port 1: 0080 off
  Port 2: 0080 off
  Port 3: 0080 off
  Port 4: 0080 off
Current status for hub 1-1 [2109:3431 USB2.0 Hub, USB 2.10, 4 ports, ppps]
  Port 1: 0000 off
  Port 2: 0000 off
  Port 3: 0000 off
  Port 4: 0000 off
Sent power off request
New status for hub 1-1 [2109:3431 USB2.0 Hub, USB 2.10, 4 ports, ppps]
  Port 1: 0000 off
  Port 2: 0000 off
  Port 3: 0000 off
  Port 4: 0000 off

Try plugging into a USB stick or something similar that runs off host power.. it should remain unpowered.


Poweroff didn't work on your Pi4? Maybe you have old firmware. If so, switch sdcard from Volumio to Raspian, and follow the steps here


To make the power-off command run every time your Volumio boots up:

Code:

sudo nano /etc/rc.local

and add the relevant line before the exit 0 line

Code:

uhubctl -a off -l 2

I'll cover some other hardware configurations next time.

 

Thank you for your work - how stupid that I recently started using an Asus Tinker Board ...
Have to see how that is compatible.

 

Yes, thank you Woland for bringing this to our attention and documenting it here - quite apart from the fact that there may be real audio improvements it's a lot of fun for a non-technical person to just jump into SSH'ing and feel fleetingly like they've got a clue what's going on (actually got a bit of a buzz hitting the light switch on the Pi). And so far so good (even via Moode) - I wonder if any of the changes improved stability as for the first time ever I had a session where Airplay to Moode didn't drop once.

On that point, maybe further down the line, and if it's in your sphere of knowledge, would be great to understand if there are network systems or configurations (or local settings on the Pi) that can improve connectivity - anyway, keep it coming and thanks again!

 

Hi @Woland, during the uhubctl install step I got the following. Can you offer any suggestions? TIA.

"Package gcc is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package make is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'make' has no installation candidate
E: Package 'gcc' has no installation candidate"[/QUOTE]

 

Interesting.

Try running this before the other steps

Code:

sudo apt-get update

if that doesn't fix it:

Code:

sudo apt-get upgrade

I'm a bit hesitant about running these upgrade commands because they might conflict with Volumio's own upgrades. If something major goes wrong, it's not a big deal to re-flash the sd-card and start again.

 

Thanks. The update went through fine but now I have some GCC dependency issue. If I solve it, I'll post here.