How to use a pulseaudio server in a certain port?

Need help with MPD?
Post Reply
doronbehar
Posts: 6
Joined: December 14th, 2018, 5:47 pm

How to use a pulseaudio server in a certain port?

Post by doronbehar »

I'm trying to setup mpd for balena-sound - eventually mpd is supposed to run in a docker container. Never mind the details, I'm instructed here to launch my application (mpd) with this environment:

Code: Select all

PULSE_SERVER=tcp:localhost:4317
What is the equivalent of doing it with `audio_output`? I tried:

Code: Select all

audio_output {
  type "pulse"
  name "Local Music Player Daemon"
  server "127.0.0.1:4317"
}
But I get no sound. Is this supposed to be right? MPD's docs says the `name` directive should correspond to the name the pulse server uses internally. What does that mean?

Help will be greatly appreciated by the balena-sound community.

max
Forum team
Posts: 1127
Joined: January 15th, 2013, 3:43 pm

Re: How to use a pulseaudio server in a certain port?

Post by max »

doronbehar wrote:
September 11th, 2020, 8:49 am
says the `name` directive should correspond to the name the pulse server uses internally. What does that mean?
No, it doesn't say that. It says
"Some plugins also use it internally, e.g. as a name registered in the PULSE server."
This means that the PulseAudio output plugin transfers this name to the PulseAudio server, so MPD appears as that name in the PulseAudio source list. But that's all, it doesn't need to "correspond" with anything. It's an arbitrary name you choose.

But read further:
"More information can be found in the Output plugins reference."
The plugins reference has a section about pulse: https://www.musicpd.org/doc/html/plugins.html#pulse

doronbehar
Posts: 6
Joined: December 14th, 2018, 5:47 pm

Re: How to use a pulseaudio server in a certain port?

Post by doronbehar »

I got it working, when I also set the `sink` to a proper value. Thanks @max :).

Post Reply