FFMPEG Tuning - Best Practice

[AdiAbuAli]

Hi,
I recently had issue with one V3 with bad Wi-Fi coverage and a lot of lost frames, caused FFMPEG to freeze and broke all other stream pipes and solved with FFMPEG_FLAGS=-fflags +flush_packets+genpts+discardcorrupt+nobuffer .

Anyways, I would like to please to see other user experience to tune FFMPEG flags (e.g. -flags low_delay, ...etc.).....as I see in FFMPEG website MANY parameters....even it can run as RTSP server!!

How to tune, how to re-order frames, how all cams be on sync when play the recorded files,....etc.

Thanks in advance for all ideas & experiences....

[mrlt8]

Thanks @AdiAbuAli! I added the flags back to the bridge in v1.0.1:

docker-wyze-bridge/app/wyze_bridge.py

Line 392 in d562b41

flags = "-fflags +flush_packets+genpts+discardcorrupt+nobuffer"

While the bridge will use the flags by default, you can still override them with FFMPEG_FLAGS as usual.

[AdiAbuAli]

Thanks Mrlt8...

[AdiAbuAli]

I tried libx264 -preset ultrafast parameters in FFMPEG command, and the result was fabulous.....anyways, I stopped it later, as CPU jumped 4x !

[AdiAbuAli]

To whom it may interest...
I noticed the stream is much smoother if you lower Log level to -loglevel error...specialy if you are running on low PC specs, and/or want to overcome Timestamp not set in stream 0 warning message by setting (-use_wallclock_as_timestamps 1)....
seems this will reduce overhead process on FFMPEG.....

Just sharing experience....

[mrlt8]

Log level is already the default behavior:

docker-wyze-bridge/app/wyze_bridge.py

Line 405 in a5e8894

["-loglevel", "verbose" if self.env_bool("DEBUG_FFMPEG") else "fatal"]