+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Official moOde 7.2.1 support thread (/showthread.php?tid=3788)
RE: Official moOde 7.2.1 support thread - suit4 - 05-09-2021
(05-09-2021, 03:38 PM)Tim Curtis Wrote: Post output from the commands below and I'll have a look.
Code:cat /etc/alsa/conf.d/_audioout.conf
cat /etc/alsa/conf.d/_deviceout.conf
cat /etc/alsa/conf.d/_sndaloop.conf
lsmod | grep snd_aloop
cat /etc/mpd.conf
Code:
cat /etc/alsa/conf.d/_audioout.conf
pcm._audioout {
type copy
slave.pcm "_deviceout"
}
cat /etc/alsa/conf.d/_deviceout.conf
pcm._deviceout {
type copy
slave.pcm "hw:0,0"
}
cat /etc/alsa/conf.d/_sndaloop.conf
#
# This file provides a default Loopback device by overriding the _audioout device defined in /etc/alsa/conf.d/
#
# The trailing underscores are removed/added by job "alsa_loopback" to effectively turn the override On/Off.
# This job is submitted by snd-config.php and corresponds to the setting "ALSA loopback ON/OFF".
#
pcm.!_audioout {
type route
slave.pcm {
type multi
slaves {
a { channels 2 pcm "_deviceout" } # Original output
b { channels 2 pcm "hw:Loopback,0" } # Loopback output
}
bindings {
0 { slave a channel 0 }
1 { slave a channel 1 }
2 { slave b channel 0 }
3 { slave b channel 1 }
}
}
ttable [
[ 1 0 1 0 ] # left -> a.left, b.left
[ 0 1 0 1 ] # right -> a.right, b.right
]
}
lsmod | grep snd_aloop
snd_aloop 24576 0
snd_pcm 94208 5 snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_aloop,snd_bcm2835,snd_soc_core
snd 73728 10 snd_compress,snd_timer,snd_aloop,snd_bcm2835,snd_soc_core,snd_pcm
cat /etc/mpd.conf
#########################################
# This file is automatically generated
# by the MPD configuration page.
#########################################
music_directory "/var/lib/mpd/music"
playlist_directory "/var/lib/mpd/playlists"
db_file "/var/lib/mpd/database"
log_file "/var/log/mpd/log"
pid_file "/var/run/mpd/pid"
state_file "/var/lib/mpd/state"
sticker_file "/var/lib/mpd/sticker.sql"
user "mpd"
group "audio"
bind_to_address "any"
port "6600"
log_level "default"
restore_paused "yes"
auto_update "no"
follow_outside_symlinks "yes"
follow_inside_symlinks "yes"
zeroconf_enabled "no"
zeroconf_name "Moode MPD"
filesystem_charset "UTF-8"
metadata_to_use "+comment"
audio_output_format "192000:24:2"
replaygain "off"
replaygain_preamp "5"
volume_normalization "no"
audio_buffer_size "16384"
max_output_buffer_size "131072"
max_playlist_length "16384"
max_connections "128"
decoder {
plugin "ffmpeg"
enabled "yes"
}
input {
plugin "curl"
}
input_cache {
size "128 MB"
}
resampler {
plugin "soxr"
quality "very high"
threads "0"
}
audio_output {
type "alsa"
name "ALSA Default"
device "_audioout"
mixer_type "software"
dop "no"
}
audio_output {
type "alsa"
name "ALSA Bluetooth"
device "btstream"
mixer_type "software"
}
audio_output {
type "httpd"
name "HTTP Server"
port "8000"
encoder "flac"
compression "0"
tags "yes"
always_on "yes"
}RE: Official moOde 7.2.1 support thread - Tim Curtis - 05-09-2021
The file /etc/alsa/conf.d/_deviceout.conf should like below after setting Output device to "Pi Headphone jack" in MPD Config and then clicking SAVE.
Code:
pi@rp1:~ $ cat /etc/alsa/conf.d/_deviceout.conf
pcm._deviceout {
type copy
slave.pcm "plughw:1,0"
}RE: Official moOde 7.2.1 support thread - suit4 - 05-09-2021
(05-09-2021, 05:21 PM)Tim Curtis Wrote: The file /etc/alsa/conf.d/_deviceout.conf should like below after setting Output device to "Pi Headphone jack" in MPD Config and then clicking SAVE.
Code:pi@rp1:~ $ cat /etc/alsa/conf.d/_deviceout.conf
pcm._deviceout {
type copy
slave.pcm "plughw:1,0"
}
Ok, the setting already was "Pi Headphone jack".
I switched to "Pi HDMI 1" and saved the settings. The _deviceout.conf still has the same timestamp.
I switched back to "Pi Headphone jack" and saved again, still no change in the file.
For some reason, saving does not work.
I tried to save the MPD settings at 19:30, below are all the files in /etc/alsa/conf.d/. Some seem to get a change, some not.
Are the file permissions, owners and groups correct?
I guess, I just could change the file manually, but like to drill down to the reason saving does not work.
Code:
ls -l /etc/alsa/conf.d/
total 44
-rwxr-xr-x 1 root root 299 May 9 19:30 20-bluealsa-dmix.conf
-rw-r--r-- 1 root root 1087 Dec 15 12:57 20-bluealsa.conf
-rwxr-xr-x 1 root root 51 May 1 13:33 _audioout.conf
-rwxr-xr-x 1 root root 48 May 1 13:33 _deviceout.conf
-rwxr-xr-x 1 root root 856 May 9 14:48 _sndaloop.conf
-rwxr-xr-x 1 root root 284 May 9 19:30 alsaequal.conf
-rwxr-xr-x 1 root root 137 Dec 15 12:57 btstream.conf
-rw-r--r-- 1 root root 1098 Mar 27 11:10 camilladsp.conf
-rwxr-xr-x 1 root root 396 May 9 19:30 crossfeed.conf
-rwxr-xr-x 1 root root 1450 May 9 19:30 eqfa12p.conf
-rwxr-xr-x 1 root root 260 May 9 19:30 invpolarity.confRE: Official moOde 7.2.1 support thread - Tim Curtis - 05-09-2021
The symptoms suggest either an incomplete update or some sort of other breakage.
I'd start with a fresh r721 image.
RE: Official moOde 7.2.1 support thread - DRONE7 - 05-10-2021
Reports of USB DAC's no longer working after update.... I can confirm....mine worked for 2 minutes then stuttered as if having a resource issue then went mute and can no longer be made to play....many reboots, restarts of mpd, ..... hardware is good and tested....MoOde seems not to route audio to USB...odd ?
RE: Official moOde 7.2.1 support thread - Tim Curtis - 05-10-2021
No issues on my end with USB DAC after update.
Whats the Audio debug section look like in Moode log?
Example
Code:
20210509 223716 worker: -- Audio debug
20210509 223716 worker: ALSA cards: (0:b1 | 1:Headphones | 2:Revolution | 3:empty
20210509 223716 worker: MPD config: (2:Allo Revolution DAC | mixer:(Revolution ) | card:2)
20210509 223717 worker: ALSA mixer actual (Revolution )
20210509 223717 worker: ALSA Revolution volume set to (0%)RE: Official moOde 7.2.1 support thread - DRONE7 - 05-10-2021
(05-10-2021, 09:50 AM)Tim Curtis Wrote: No issues on my end with USB DAC after update.
Whats the Audio debug section look like in Moode log?
Example
Code:20210509 223716 worker: -- Audio debug
20210509 223716 worker: ALSA cards: (0:b1 | 1:Headphones | 2:Revolution | 3:empty
20210509 223716 worker: MPD config: (2:Allo Revolution DAC | mixer:(Revolution ) | card:2)
20210509 223717 worker: ALSA mixer actual (Revolution )
20210509 223717 worker: ALSA Revolution volume set to (0%)
Hmmm... maybe I have a corrupt upgrade... can no longer log in via ssh.
I will re-image and configure a new install tomorrow. :-)
RE: Official moOde 7.2.1 support thread - suit4 - 05-10-2021
(05-09-2021, 07:03 PM)Tim Curtis Wrote: The symptoms suggest either an incomplete update or some sort of other breakage.
I'd start with a fresh r721 image.
Hi Tim, thanks,
a fresh install worked.
RE: Official moOde 7.2.1 support thread - adrii - 05-10-2021
I don't seem to have an audio copy on the ALSA loopback device when using Moode as a bluetooth speaker. (It looks like bluetooth audio as input doesn't use the audioout/deviceout framework).
RE: Official moOde 7.2.1 support thread - Tim Curtis - 05-10-2021
Correct. See mpd.conf below. Bluetooth still has a separate output. It was left this way because the code that manages switching between Local and Bluetooth output needs a rewrite to be compatible with the new ALSA routing framework. Maybe it can be done for the upcoming 7.3.0 release.
Code:
audio_output {
type "alsa"
name "ALSA Default"
device "_audioout"
mixer_type "hardware"
mixer_control "Revolution "
mixer_device "hw:2"
mixer_index "0"
dop "no"
}
audio_output {
type "alsa"
name "ALSA Bluetooth"
device "btstream"
mixer_type "software"
}
audio_output {
type "httpd"
name "HTTP Server"
port "8000"
encoder "lame"
bitrate "320"
tags "yes"
always_on "yes"
}