(In reply to freedesktop from comment #17) > Lowering the rate is possibly not a good idea as it results in worse > quality. The format is by default "s16be" about which I have no idea what a > different format would help. I do not know if the data can somehow be > compress further, because this would definitely be an idea, but I dont know > the procols internal.
The data can certainly be compressed. I don't know if you've ever compared the sizes of mp3 and wav files. Typical compressed audio, when using a lossy codec, requires perhaps one tenth of the bandwidth that uncompressed audio requires, without too much effect on the audio quality. > So the only left option is to solve the routing. For my personal setup there > is no way to fix this on the router side, so the sender pulse module needs > to take care of it. Using an ip as destination works perfectly and would be > an option to use (which should be added to paprefs). However I tried that > the last days and due to dhcp my receiver always gets a new IP and using > hostnames would be a better idea. > > But the module does not seem to support hostnames. So I am wondering if this > could be fixed quite simple or needs a whole more work to do. Changing module-rtp-send to support hostnames doesn't sound terribly complicated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/411688 Title: pulseaudio floods network with multicast packets To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/411688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs