Romain Beauxis
Romain Beauxis
This should be addressed as part of the rewrite of clocks. Currently, using any two operators using the `Child_support` facility results in clock assignment issues. See for instance: https://github.com/savonet/liquidsoap/issues/2336
From the chat: > Just a suggestion: the "Interaction with the server" page in the docs could really use a reference to server.register somewhere. It's not mentioned at all, and...
See https://github.com/savonet/liquidsoap/issues/1829 for details.
See: https://github.com/savonet/liquidsoap/discussions/2331#discussioncomment-2549015
From the chat: > Hello! Is it currently possible (even in beta) to stream with ffmpeg encoder with multiple audio tracks? Liquidsoap is much easier to handle fallbacks (ffmpeg alone...
`Request.is_ready` semantics is unclear and buggy. See: https://github.com/savonet/liquidsoap/runs/5801028774?check_suite_focus=true This is due to a couple of facts: * We are using the request's data to determine if it is ready. This...
This PR adds a new syntactic construct: ```ruby # x = { foo = 123, bla = "bar" };; x : {bla : string, foo : int} = {foo =...
To be addressed in a future rewrite: currently, clocks are started regardless of their dependencies. This can lead to situation where a clock is asking data from a dependent clock...