Volumio 3 Buster Beta for RPi

Thanks guys for your reports.
Very very useful!

A post was merged into an existing topic: [NOT RECOMENDED!] Plugin and Tweaks Adventures on Buster Betas

since PI4 support boot from USB, so I flash the volumio3-beta.img to the USB, but it cannot boot from it

same USB with raspios img can boot with without issue

USB boot is not supported yet by Volumio and there are no immediate plans to add it.

Volumiobuster-3.067-2021-04-16-pi
RaspberryPi 4 + CM4 IO board
SanDisk Extreme SSD 1TB connected via USB port on CM4 IO board
DAC: Sotm SDP-1000 (Bus 001 Device 004: ID 20b1:2102 XMOS Ltd)
wired connection to a wifi router givien a static local IP with the MAC address registered


Everything else works except the following issues

  1. Default setting of CM4 IO board is USB disabled. Nothing came up on USB with fresh install. I had to put ā€œdtoverlay=dwc2,dr_mode=hostā€ in /boot/config.txt. After that no problem
  2. DSD files are being played as DOP even though volumio configuration is set to play DSD direct. My DAC Sotm SDP-1000 has XMOS chipset with Bus ID and Device ID as above mentioned. This is expected. However I can play DSD direct with this DAC on minimal Debian buster + MPD

Other than this everything works fine. I had SSD usb connection get disconnected once in a while with Volumiobuster 3.051 but it seems like the problem is gone with 3.067? It has been only 1 day, so it may or may not happen later.

Any ETA for volumio 3.0, my hifiberry dac + is cracking and cracking and this well documented responsiveness is teasing me

Please donā€™t ask for the obvious answer.
It will be ready when itā€™s ready.

3 Likes

Volumiobuster-3.067-2021-04-16-pi
RPi4B
DAC: Piano 2.1 with Kali reclocker

No audio out, and canā€™t set DSP duel mode to ā€˜noneā€™.

Still no audio with resampling on.

System log

Edit: the above log does not show the first part after boot (full of repeated error messages at some later stage).

Second system log

My volumio 3.067 on rasperberry PI3B stops playing content I see somthing like I Upnp error.

live log

I had to power off device to get things working again

Hi @gkkpch

Topping e 30,
Inverted settings : on DAC I see 5.64 DSD

found it :
volumio@volumio:/proc/asound/card1$ cat stream0
Topping E30 at usb-0000:01:00.0-1.4, high speed : USB Audio

Playback:
Status: Running
Interface = 1
Altset = 1
Packet Size = 536
Momentary freq = 352842 Hz (0x2c.1af0)
Feedback Format = 16.16
Interface 1
Altset 1
Format: S32_LE
Channels: 2
Endpoint: 1 OUT (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000, 705600, 768000
Data packet interval: 125 us
Bits: 32
Interface 1
Altset 2
Format: S32_LE
Channels: 2
Endpoint: 1 OUT (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000, 705600, 768000
Data packet interval: 125 us
Bits: 24
Interface 1
Altset 3
Format: SPECIAL DSD_U32_BE
Channels: 2
Endpoint: 1 OUT (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000, 705600, 768000
Data packet interval: 125 us
Bits: 32

Your last info :
Something odd in stream0, under Altset 3, I would have expected to see a line
DSD raw: DOP=0, bitrev=0

Needs to be checked whether relevantā€¦

Is v3.073 for general testing?

(Volumio 3 Buster Beta for RPi - #161 by chsims1) not addressed, but actually looking at that log for the first time, it seems to be a problem with vtcs.service (Volumio Tidal Connect Service??) rather than Piano 2.1 DAC/Kali reclocker.

Updated to v3.073 and usercinfig.txt is restored to default values.

Hi,
thank you for this new version.
I tried [Volumiobuster-3.073-2021-05-07-pi] on Raspberry 1 with HifiDigi.
I have a problem to add a network disk from my NAS.
ā€œā€ is replaced by ā€œ:ā€ so the path is NAS:directory instead of NAS\directory.

Hi

Just a question on the Piano 2.1 & Kali reclocker = do you know if the 3.xx version of Volumio could solve the issue with Dual Mono configuration issue (config missing) appearing around Oct 2020 ?
(meaning the Dual Mono configuration could not be choosen anymore)
If i am mistaken and the issue has been solved in 2.xx already, please correct me.

Have a nice day

@laluciol6990
I could select ā€œDual monoā€ & ā€œDual stereoā€, but no idea if either did anything, because there was no audio out. I couldnā€™t select ā€œNoneā€ ā€¦ rather I could select it, but it wouldnā€™t ā€˜saveā€™ as an option.

It works correctlyif I skip the first wizard. I can add the disk manually.

Hi laluciol6990,

As chims1 already stated Dual Mono is selectable but there is no sound and after playing around a little in v3.067 as well as in v3.073 i get the following message if trying to start music:
grafik

Happily i found that Kali/Piano is working again with v2.882 (First choose Piano2.1 DAC, reboot, then choose Subwoover mode 2.0, reboot, then choose Dual Mono, reboot againā€¦)
Still you have to resample to 32Bit if using Kali.

br
Josef

Thanks for the info about v2.882. I tried, but i go through a cycle of choosing Subwoofer 2.0 mode, reboot, Choosing Dual Mono which appear, reboot, then Dual Mono disappear, choosing Subwoofer 2.0 mode, rebootā€¦
So, not working that great for me, unless it is normalā€¦

As for trying this device with V3ā€¦it is my main device, used by everybody, so i prefer to wait a bit until it is stabilized (wifi dongle would have to be installed with command line, i noticed the USB harddrive is not writeable on the test machine with V3 -protection i assume-)
I have another device only used by me for testing, but no Kali & Piano on it

Have a nice day

Feature request:

In Music Library, make Volumio not show ._ files. MacOS for example pollutes with these files, and I imagine itā€™s quite common to use a Mac to copy files to a USB drive or similar, or use your Mac as the actual server.

It is very annoying since when you try to play an album, if first gets to the ._ files that cant be played. And it also looks messy. Of course we can manually delete them but itā€™s annoying. Thanks.:slight_smile:

Maybe adding it in .mpdignore with ._ * in the root of the disk should do the trick.
from mpd documentation:

To exclude a file from the update, create a file called .mpdignore in its parent directory. Each line of that file may contain a list of shell wildcards. Matching files in the current directory and all subdirectories are excluded.