I was hoping since you use docker, it would be simple to swap out the version for testing, if not then don’t worry about it. I have been doing some thinking about this and feel that the increase in load will not be much, only would happen if the ffmpeg alarm or snapshot creation is running, and would be handy to have in case the thread crashes for other reasons besides the camera rebooting/reconnecting. I want to get this sorted, since I have read the code recently and its all fresh in my head, so getting it done now makes sense and not waiting to see if the problem goes away with a newer ffmpeg version.
EDIT:
@John_Siemon and @downloadme4free
If you’re willing to test an Alpha build of the binding, I made some changes you were both wanting made.
- FFmpeg snapshots will now auto restart and also take the camera offline if the stream locks up from a camera rebooting. I have tested and it seems to work here the 1 time I tried it.
- FFmpeg motion alarm should auto restart if the camera reboots, ffmpeg crashes, or goes offline. I have not tested this yet as its late and want to read the github issue on this topic before completing and doing the testing in the next few days.
Feel free to give it a go.