It depends on your network

It depends on your network setup, but some multicast addresses are specifically designed to avoid going out of the LAN. This is what the default PA multicast address does, so if you're PA multicast sender is on a wired LAN, the wifi network should not be seeing multicast traffic unless the interfaces are bridged or some other weird thing.

Or are you saying that the mere presence of multicast on the wired interface of the router breaks it?

Comment by anarcat
does "path" (fifo) work any better than "pipe"?
I haven't tried this, but my mpd.conf manpage says it will output to a fifo with the "path" audio_output option. Maybe that will work better than a pipe and allow you to avoid PA.
Comment by ecc
I moved the Pulseaudio troll to a separate post
So as I mentionned in an edit in the post, there used to be a rant/troll about Pulseaudio in the body of the text, but since that seemed to be generating more responses than the actual subject of the post, I thought it was better to move the discussion to a separate post. Comments were moved along and were of course not edited in any shape or form.
Comment by anarcat
Can't make it work.

Mpd doesn't seems to use pulse output

If I run pacmd list-sinks I got "No PulseAudio daemon running, or not running as session daemon." as an answer

In ps i got pulseaudio on mdp user

mpd 3001 1 0 80 0 - 22553 poll_s 18:01 ? 00:00:00 /usr/bin/pulseaudio --start --log-target=syslog

Any idea?

Regards,

Regis

Comment by R.
Got some errors in

Got some errors in logs

first

Feb 13 18:21:51 raspberrypi pulseaudio[3204]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

Got an answer from http://ubuntuforums.org/showthread.php?t=1878868&page=2 Make the script and run the four commands.

The line had disappeared from the log. The other lines are :

Feb 13 18:32:53 raspberrypi pulseaudio[3298]: [alsa-sink] alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Feb 13 18:32:53 raspberrypi pulseaudio[3298]: [alsa-sink] alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_bcm2835'. Please report this issue to the ALSA developers. Feb 13 18:32:53 raspberrypi pulseaudio[3298]: [alsa-sink] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.

Regards,

Comment by R.
Got problem with "zero

Got problem with "zero config" i put back the line in commentary and got it working. Got a delay 1 sec between the sound played on mpd server and the vlc on an other computer.

Comment by R.
Have you tried changing the
Have you tried changing the --rtp-caching option?
Comment by anarcat
Hi, Thanks for your answer.

Hi,

Thanks for your answer. On the PC I played with the network caching (round 280ms), on the Mac i finaly found where the option where hidden. But the delay seems to vary...

Is a RPi could be master and slave for mpd ntp stream?

Regards,

Comment by R.
uh?

Is a RPi could be master and slave for mpd ntp stream?

I don't understand your question.

Comment by anarcat
The Mpd computer is set to

The Mpd computer is set to stream to other computer. What i was thinking is enabling mpd to an other mpd machine and localy play this stream. Each mpd can act as a server or a listener, don't know if it's possible?

Comment by R.
Created . Edited .