#50: Jack reset not working properly
-------------------------+--------------------------------------------------
Reporter: balbinus | Owner: admin
Type: Bugs | Status: reopened
Priority: 2 | Milestone:
Component: Liquidsoap | Version: 0.3.6+svn
Resolution: | Keywords:
-------------------------+--------------------------------------------------
Comment (by mrpingouin):
Concerning Jack, I think it's a feature that there's no buffer, and hence
a sensitivity to any latency in the main thread. On the other hand, Shout
could (optionally?) do stuff in another thread, or in Duppy: either only
the reconnection, or even also all the sendings. Slightly more latency for
Shout is OK. It will cost a bit of perf for liquidsoap but that should
remain reasonable (especially if the new behaviour is optional).
Now I'm daydreaming... the cool thing would be a generic way to send part
of the sources' graph to another thread, distributing the stream
generation with an asynchronous interface. (The asynchrony is the new bit
compared to previous daydreaming about distributed generation, which was
just about in/output.rtp()).
--
Ticket URL: <http://savonet.rastageeks.org/ticket/50#comment:8>
Savonet <http://savonet.rastageeks.org/>
Let's program our stream !
