-
Notifications
You must be signed in to change notification settings - Fork 33
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
RTMP plugin delivers end_of_stream on TCP disconnection #792
Comments
Since dropping the connection means we won't send anything anymore from the source, the end of stream is quite expected. I assume that the logic is to remove the element on the connection drop and spawn a new one - in that case, some further element should take care of intercepting the end_of_stream and be linked to the newly spawned source. |
A connection drop is something related to a problem in the transport layer. It signals a network fault, which in my opinion is unrelated to the end of stream event, which means that everything is done (whereas is not in this case).
Thanks to crash groups & dynamic pads this is very easy to accomplish and it is actually how we're handling it.
This element the has to know wether that was a false positive or not. I really think this is very confusing. This is an RTMP plugin, RTMP has a message that signals the real end_of_stream, let's just stick with it @mat-hek! |
Hmm, let's assume we don't send the end_of_stream. You get the |
Not in case the removed elements and the leftovers are connected with a dynamic pad right? |
I’d have to check, but I think in this case as well |
This issue is also related to
The RTMP stream is delivering end of stream when the TCP connection is dropped, see here. For us this is plain wrong logic, as one thing is an error such as a connection drop, one thing is an actual end of stream, in amf terms a deleteStream message.
We're turning output HLS streams into VOD when the transmission is ended, and this is an event you cannot withdraw, once player see that tag they stop reloading the playlist.
Can we add an option tunes this behaviour? Or even better (this is how we deal it in our work)
Basically we just notify the parent of the event, then the pipeline can decide how the rest of the children should react.
The text was updated successfully, but these errors were encountered: