PeppyMeter

[rpi]

You can specify two audio output sections in the mpd.conf: one for DAC and one for the peppyalsa. In this case you don't need to specify hardware output for the peppyalsa. Hopefully it works.

Best regards

[fdealexa]

Thanks Phofman ans thanks "rpi"

You can specify two audio output sections in the mpd.conf: one for DAC and one for the peppyalsa.

That's what I have done:

pi@moOde-Sala-Hobby:~/peppyalsa/src $ 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 "verbose"
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"
replaygain "off"
replaygain_preamp "0"
volume_normalization "no"
audio_buffer_size "4096"
max_output_buffer_size "131072"
max_playlist_length "16384"
max_connections "128"

decoder {
plugin "ffmpeg"
enabled "yes"
}

input {
plugin "curl"
}

resampler {
plugin "soxr"
quality "high"
threads "1"
}

audio_output {
type "alsa"
name "ALSA default"
device "hw:0,0"
mixer_type "none"
dop "no"
}

audio_output {
type "alsa"
name "peppyalsa"
device "peppyalsa"
mixer_type "none"
dop "no"
}

audio_output {
type "alsa"
name "ALSA crossfeed"
device "crossfeed"
mixer_type "none"
dop "no"
}

audio_output {
type "alsa"
name "ALSA parametric eq"
device "eqfa12p"
mixer_type "none"
dop "no"
}

audio_output {
type "alsa"
name "ALSA graphic eq"
device "alsaequal"
mixer_type "none"
dop "no"
}

audio_output {
type "alsa"
name "ALSA polarity inversion"
device "invpolarity"
mixer_type "none"
dop "no"
}

audio_output {
type "alsa"
name "ALSA bluetooth"
device "btstream"
mixer_type "software"
}

audio_output {
type "httpd"
name "HTTP stream"
port "8000"
encoder "lame"
bitrate "320"
tags "yes"
always_on "yes"
}

pi@moOde-Sala-Hobby:~/peppyalsa/src $

But I still have problems with "/etc/asound.conf":
If I configure the only available HW, the system returns the BUSY error
If I don't configure anything, it returns me "slave not configured"
If I configure NULL as a slave it seems ok but nothing goes to the FIFO.

Any advice for the slave argument or, better, for the entire asound.conf?

Sincerely and thank you both very much,
Francesco

[phofman]

Have you tried keeping just the peppymeter output with the properly configured slave soundcard, removing the direct hw:0 alsa output from your mpd.conf? IMO the peppymeter is clocked by period_elapsed calls of the slave device, these calls are propagated along the alsalib chain from the slave through all the parental plugins all the way up to the player. That way the soundcard at the end times transmission of samples throughout the whole upstream chain. IMO the slave device should be configured and be the real output soundcard device. But I have not tried...

[fdealexa]

Hi Phofman,
Thanks but, unfortunately I dont follow you, but I can try.
I say "try" because the mpd.conf, in moOde, is automatically generated at each reboot. I have to try to modify the related code.
If you have any additional idea, Please do not hesitate to let me know.
Thanks again and best regards,
Francesco

[fdealexa]

Phofman,
Still resource busy.
Thanks and regards,
Francesco ��

[phofman]

You have many alsa_outputs in your mpd config, apparently all of them enabled at the same time. Does each of them really output to a different HW device? If not, logically a latecomer will hit the "resource busy" error unless dmix plugin is somewhere in the alsalib chain to allow mixing multiple streams.

[fdealexa]

Hello Phofman,
It is true: that is the infrastructure of moode, my goal is to make Peppymeter running in that environment.
Last week I did it without any additional DAC board, using the headphone directly connected to the rpi.
Adding the board I am, now, experiencing the problem you are kindly helping to risolve.
Thanks a lot,
Francesco

[phofman]

It really does not matter which particular soundcard you are using, any HW device will be busy when a second open call is attempted.

I would be surprised if moode ruined MPD config to produce multiple opening the same device.

I would start by cleaning all the MPD outputs from the config and adding them back one by one. For peppymeter and playback IMO just the peppy meter with HW as slave should do. The other configs either should point at a different soundcard or should be incorporated into the peppymeter config chain. Experimenting will certainly take you to the desired result.

[fdealexa]

Phofman, I don't know what words to use to thank you.
I'll get back to the DAC-less setup as soon as possible and send you the details.
Thanks again and best regards,
Francesco

[fdealexa]

I apologize for the delay in the reply: I confirm that without any DAC card it works.
I'm trying now with the type file and slave null options.
Thanks for your attention and best regards,
Francesco