Mailinglist Archive: opensuse (1318 mails)

[Randall R Schulz <rschulz@xxxxxxxxx>]

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