Please read my comments marked by ">>" This is really great info But if you didn't want to run an application all the time to play the sound, could you not configure SystemB to serve as a sink for system A?
from what i can see, the server is always sending something to the multicast address(224.0.x.x) but only when there is actually audio being generated at the server would there be a valid stream. The problem is I don't know if you can always count on the same multicast port# being for the valid stream. From what I've seen on my system, the same multicast port# is used. Plus, I need to manually run a player application in order to read that stream.
I think Pulseaudio has this concept of sources and sinks, where sources stram any sounds, and Sinks can grab any streams and just play them without an application because the sound server will send send them to your speakers. Is this not correct?
I fully understand what you're asking. Essentially, you want the 2nd system to be the speaker for the 1st system. This is beyond my pulseaudio knowledge. I've never really understood how this aspect work nor configured. I tried some quick configuration with 'source' and 'sink' using the pulseaudio applet but without success
-- View this message in context: http://www.nabble.com/%22Network-Sound%22-tp23279806p23327024.html Sent from the openSUSE community mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org