Mailinglist Archive: opensuse (1325 mails)

[buzlite <bzb999@xxxxxxxxx>]

The group includes the addresses from 224.0.0.0 to 239.255.255.255, or,
equivalently, 224.0.0.0/4. The range from 224.0.0.0 to 224.0.0.255 (or
224.0.0.0/24) is designated for multicasting on the local LAN only.  I
believe PulseAudio only deals with multicast in LAN environments. Hence, it
uses 224.0.0.x.

That's why I used '$ sudo tcpdump -n net 224.0.0.0/8 -c 10' to look for IP
traffic whose destination IP is  224.x.x.x and whose source IP is the system
running the pulseaudio server.

If I understand your need correctly.  I believe you mean routing all sound
from systemA to systemB. if that is so systemA is the client and systemB is
the server. when both system has pulse audio configured properly, they
should be able to see each other automatically once they start up. In such a
case, all you have to do is go to systemB's
PulseAudioAudioApplet('padevchooser') and set DefaultSink=systemA.  After
which, any audio that is generated by systemB will automatically be routed
to systemA's speakers.  NOTE: you do not need to deal with multicasting in
such a scenario, pulseaudio is using tcp in this case.

Pulseaudio multicasting is only used if you have multiple hosts listening in
on audio broadcast from the source pulseaudio server.




Randall Schulz wrote:
> On Thursday April 30 2009, buzlite wrote:
> > -You can setup PulseAudio to serve your needs. Let's say you have 2
> > systems. SystemA and SystemB and assuming that they can see each
> > other. Let SystemA be the PulseAudio server and SystemB be the
> > PulseAudio client.
> >
> > ...
> >
> > On SystemB(client):
> > -------------------
> > -run 'tcpdump' to look for any multicast from the SystemA. Take note
> > of the multicast ip and port# (eg. 224.0.x.x). You'll need to refer
> > to it later in the player on SystemB.  On my system, it's
> > 224.0.0.56.46946.
>
> I'm not sure I know how to recognize multicast traffic. What's the clue?
>
>
> > $ sudo tcpdump -n net 224.0.0.0/8 -c 10
> >
> > $ mplayer -demuxer rawaudio -rawaudio
> > channels=2:rate=44100:samplesize=2:format=0x10001
> > rtp://224.0.0.56.46946
> >
> > -Note: As you can see, i'm using 'mplayer' in this example. but you
> > can use another that support RTP streaming.  Take note of the
> > parameter values that is specified with 'mplayer', you'd have to
> > probably enter it in you player.
>
> What I want to do is get all system audio emitted on the client routed 
> to the server, not just particular program's output. Is that possible? 
> If so, how?
>
>
> > ...
>
>
> Randall Schulz
> -- 
> To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
> For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

-- 
View this message in context: 
http://www.nabble.com/%22Network-Sound%22-tp23279806p23347741.html
Sent from the openSUSE community mailing list archive at Nabble.com.

-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx