Backend stability work for rtsp streams #79
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After analyzing failure scenarios on my own low end cameras using neolink, wyze bridge and go2rtc on frigate I came to these changes.
One issue may be it just hangs on connecting or disconnecting the socket, I could not find the socket timeout option in the python-ffmpeg library so I wrapped it in some process timeout to keep moving, this may end up with 20 dead processes each holding the inodes on the deleted wav file, so the tmp needed to be bigger to accommodate.
I hit a scenario where it outputted FAIL and looped with a 0 byte file so added a delete there.
Hope this helps anyone.