Public bug reported: This isn't necessarily a bug, but when receiving audio through module- native-protocol-tcp the server does not autostart when audio is being played on the client. The result is that the server must be started manually on the receiving machine before sound is output on the sending machine, unless the exit-idle-time on the server is set to -1. I am streaming over the localhost from withing a chroot, and this it is a serious resource drain to have exit-idle disabled.
Is there a way to configure autostart when using native-protocol-tcp? ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1829667 Title: Autostart doesn't work over native -protocol-tcp Status in pulseaudio package in Ubuntu: New Bug description: This isn't necessarily a bug, but when receiving audio through module- native-protocol-tcp the server does not autostart when audio is being played on the client. The result is that the server must be started manually on the receiving machine before sound is output on the sending machine, unless the exit-idle-time on the server is set to -1. I am streaming over the localhost from withing a chroot, and this it is a serious resource drain to have exit-idle disabled. Is there a way to configure autostart when using native-protocol-tcp? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp