Hey @maroen,
The journal you posted is the abort. It is not the device, the mixer, or the ALSA chain. Without those, this stays a Software-mixer guess.
Verbose stays on. Do the broken capture first (Software mixer), then switch to Hardware, restart Volumio, and repeat the entire list. Label every paste SOFTWARE or HARDWARE. One command omitted = start over.
A. Identity
cat /etc/os-release
cat /etc/volumio_current_os
uname -a
cat /proc/device-tree/model
cat /data/plugins/music_service/soloist_connect/package.json
B. Playback options as Volumio stored them
cat /data/configuration/audio_interface/alsa_controller/config.json
C. The whole ALSA config (the file, not a slice)
cat /etc/asound.conf
ls -la /etc/asound.conf /etc/asound.conf.d
cat /etc/asound.conf.d/*
D. Cards and PCM names
cat /proc/asound/cards
cat /proc/asound/devices
cat /proc/asound/pcm
ls -la /proc/asound
aplay -l
aplay -L
E. USB / I2S / HDMI (all of it, even if you think it is “every output”)
lsusb
lsusb -t
lsusb -v
dmesg | grep -i -e usb -e snd -e dac -e audio
cat /proc/asound/card0/stream0
cat /proc/asound/card1/stream0
cat /proc/asound/card2/stream0
cat /proc/asound/card0/usbid
cat /proc/asound/card1/usbid
cat /boot/userconfig.txt
cat /boot/config.txt
F. Mixer controls on the live card
amixer
amixer scontrols
amixer scontents
amixer -c 0 scontents
amixer -c 1 scontents
amixer -D plug:volumio scontents
G. What plug:volumio actually accepts (this is the open we die in)
aplay -D plug:volumio -v -d 2 /dev/zero
aplay -D volumio -v -d 2 /dev/zero
aplay -D softvolume -v -d 2 /dev/zero
aplay -D plug:softvolume -v -d 2 /dev/zero
aplay -D volumioLocalPlayback -v -d 2 /dev/zero
If a name does not exist, paste the error. Do not skip it.
H. Hardware params while something else holds the device
Play a local file from Volumio (not Spotify). Leave it running. Then:
cat /proc/asound/card0/pcm0p/sub0/hw_params
cat /proc/asound/card0/pcm0p/sub0/sw_params
cat /proc/asound/card0/pcm0p/sub0/status
cat /proc/asound/card1/pcm0p/sub0/hw_params
cat /proc/asound/card1/pcm0p/sub0/sw_params
cat /proc/asound/card1/pcm0p/sub0/status
lsof | grep -e pcm -e asound
fuser -v /dev/snd/*
Stop playback. Repeat the same hw_params / status cats (idle).
I. Plugin / daemon settings (no env file)
systemctl cat soloist.service
systemctl status soloist.service --no-pager -l
ls -la /data/plugins/music_service/soloist_connect
ls -la /data/plugins/music_service/soloist_connect/alsa-lib
In the plugin UI, write down: buffer ms, align volume, queue playback, Peppy metering, output trim. Do not export soloist.env.
J. Other AAMPP plugins
ls /data/plugins/audio_interface
ls /data/plugins/music_service
ls /data/plugins/miscellanea
cat /data/configuration/audio_interface/*/config.json
cat /data/configuration/miscellanea/*/config.json
FusionDSP, PeppyMeter, equalizer, Camilla: on or off for each capture.
K. MPD’s output (it uses the same graph)
cat /etc/mpd.conf
L. Crash journal for that mixer only
Verbose on. Play from the phone until it dies (Software) or until 30 s of music (Hardware). Then:
journalctl -b -u soloist.service --no-pager -n 400
The Hardware paste must include soloist-shim: pcm open plug:volumio period=. If that line is missing, the capture is unused.
M. “Every output”
You wrote that this happens on every output. Repeat A to L for each output you claim: USB DAC, HDMI, I2S, analogue. One zip per output, named.
N. Screenshots
Playback Options (output device, mixer type, mixer control, volume options) for each capture. Spotify quality setting.
Two complete kits. Full text. No slices, no “same as before,” no “I use a Douk.” Until both mixer graphs are in the thread, there is nothing to change.
Or simply forward log link url with replicated steps. Your choice.
Kind Regards,