[Bug 411688]
Sure mp3 would be way better. I just dont know how rtp works. I think its reasonable to use mp3 here. However I dont know how that works for streams and with pulse. Fixing the compression method would be the better fix, however a specific ip/hostname would not hurt neither. -- 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
[Bug 411688]
You are right that this feature needs to be enabled first to make the bug rise. However I do not think that documentating this bug/behavior solves the problem. I do want to use music streaming, but I cannot do this as my router routes the traffic into the WLAN. 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. 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. Another option would be to possibly create a port on the localhost and route that to the destination ip/name. And the kernel itself can do the name resolution. However I have no idea about that, but this could at least be a workaround to solve this issue. Other opinions? -- 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
[Bug 411688]
I've also noticed this in the most up to data pulse versions from archlinux. I also cannot use a ttl of 1, as the router does not decrease the value when routing into wlan, as it has the same subnet. Neither does destination ip 24.0.0.1 help. From my side I have no chance to change the router config, because the internet is provided by someone else. What works for me though is to stream the music directly to the destination via destination_ip=192.168.178.x I could also add a menu in paprefs that'd also adress the ip directly, however this is more of a struggle because of the old gtk2 (if anyone here is following the mailing list). It would be highly appreciated to fix this bug in the module itself and reduce the payload somehow. -- 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
