Skip to content
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

Wait sometime before closing muxers on EOF due connection error #4225

Open
kirek007 opened this issue Feb 5, 2025 · 2 comments
Open

Wait sometime before closing muxers on EOF due connection error #4225

kirek007 opened this issue Feb 5, 2025 · 2 comments

Comments

@kirek007
Copy link

kirek007 commented Feb 5, 2025

Describe the feature

My use case is that I'm streaming over RTMP and reading HLS. Sometimes there is connectivity issues so streaming to RTMP might be off let's say for 60sec or so. Currently, it means that HLS muxer is also terminated. Then on reconnection old HLS fragments are not available for the end client.
Is there any other way to improve that flow?

@hqkirkland
Copy link

I'd also like some kind of feature which would wait for a publisher to reconnect in the event of failure. This may also help for cutting between two source files: I use RTSP as ingest and FFMPEG tears down the connection after completing a file, which also terminates all client connections (RTSP, WebRTC).

It would be nice if there was a feature to send black frames and keep the connection alive for up to n seconds. Not sure how complicated an endeavor that would be. I suspect it's not entirely appropriate for a media server like mediaMTX to be this arbiter, and instead a source pipe should manage the cutover itself.

But as of yet, I haven't found a good "intermediary" kind of stream which continues to output while it waits for the source to reconnect. Would be nice if this was just built-in.

@kirek007
Copy link
Author

kirek007 commented Feb 5, 2025

I'm new to the project, but it looks amazing! tho, it lacks some features that are vital to me.
It would be great if the maintainer could point me in the right direction where to implement this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants