-
-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List of features proposed for deprecation or removal #2592
Comments
Can you please explain how removing an existing/working feature will positively affect the development? |
From our perspective, this reduces the maintenance burden and potential for bugs (for instance memory leaks in the decoder). Thank you for chiming in, though, this is exactly why those features are listed here! Our goal is to replace all possible use-case of gstreamer with a ffmpeg equivalent. If you want to share more about how you're using gstreamer with liquidsoap, we could see how your use-case could be migrated to ffmpeg. |
After more thinking, I am leaning toward implementing a single, minimal The effort is stalled at the moment because of some limitations in the clock implementation that we intent to fix in near future versions (most likely |
I use gstreamer in this way
|
|
I Have tested input.ffmpeg. It worked for the first 6 hours, When the m3u8 URL expires it feeds silence.
|
You should try to reload the url regularly. Since this takes time I'd suggest to reload it for instance once every hour:
|
I haven't looked into replacing GStreamer with ffmpeg, but I find its pipeline functionality very powerful and complementary to Liquidsoap. Here are a couple of examples I use: Receives an RTP stream from a Barix Instreamer:
Similarly, I can create an output RTP stream as well: I feel the input could probably be handled by ffmpeg, but what about the outputs? |
Hi, currently we have |
Both input and output can be handled by
On the sending side,
|
The latest The syntax is pretty much the previous example:
|
Thanks for all the feedback y'all. Obviously gstreamer should stay on a little more. It's just been difficult to debug historically for us and we're limited in developer time so we most likely will prioritize ffmpeg debugging and also support, as exemplified here. |
This issue tracks all features proposes for deprecation of removal to anticipate them and discuss:
Deprecation
Deprecated support should be kept for at least 1 or two major release cycle.
ffmpeg
. It's been effectively disabled in our CI for a while because it kept failing it randomly or was hard to build accross platforms so we don't even track if it works at this point.Removal
let json.stringify
. This was me trying to be overzealous and code a rendering counter-point tolet json.parse
but, in fact, the type annotation does not work with generalized functions. We should return tojson.stringify(...)
The text was updated successfully, but these errors were encountered: