Server does not autostart when using module-native-protocol-tcp
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?