No probs, glad you got it going and enjoy the binding.
It should be possible, but it needs you to have a play and understand the trade offs. Having a camera that allows keyframes every second (or even more often as some cameras allow you to specify how often, some even allow every second frame) will help the most, you will also need to keep the stream running non stop.
The binding has to work on as many browsers as possible with default settings, as many cameras with their default settings and also support working on demand for those that donāt want it running all the time. Compromises are made to allow it to work in a wide range of situations so if you play you can tailor it to what you want as you have direct access to the ffmpeg command.
It can actually be useful, if your TV takes time to turn on and switch inputs you still get to see the person at your door instead of their backs as they walk away
I use the cameras as a baby monitor so I really donāt care about a delay, each person uses cameras for different things.
I personally do the following and it works great here on a Google/Nest hub.
- Cast the ipcamera.jpg the moment the doorbell is pushed and also trigger the GIF. The binding can send a jpg faster than your camera, as some cameras need to wait for a keyframe to be created first which may be 2 seconds away.
- When gif is ready, cast it and it can include preroll time that shows the person walking up to the door and pushing the button (pretty cool as the button is the trigger) and it can be in 2x 4x or any speed you wish to see it fast forward and loop.
- You could get fancy and show a history of the days visitors with the gif file. I have it sent to me with pushover which makes a different noise to email on my phone.
Plenty of ways to automate.