On 2/22/26 16:23, Elliot Smith via ffmpeg-user wrote:
The output of freezedetect is giving me numerous outputs like this...
Each time, the hex number after h264 @ is changing:
[h264 @ 000001e8f6e15d80] Late SEI is not implemented. Update your
FFmpeg version to the newest one from Git. If the problem still occurs,
it means that your file has a feature which has not been implemented.
I don't understand what is the significance of "000001e8f6e15d80". Is
"000001e8f6e15d80" a frame count number? This number is too big to be a
frame count number. 000001e8f6e15d80 = 2100086005120 frames? =
70002866837 seconds?
It is a memory address for debugging, nothing useful to you.
The "Late SEI" issue has nothing to do with your freezing detection
goal, just forget about it.
We already have an open ticket for it, I assume it matches your case,
but you can check it:
https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/21348
https://ffmpeg.org/ffmpeg-filters.html#freezedetect
duration, d
Set freeze duration until notification (default is 2 seconds).
It sounds like if I set d to 1, then duration until notification will be
1 second (30 frames.) However, this is not explained very clearly in
the documentation. I am asking, if I set d to 1, then will the duration
until notification be 1 second OR LESS, i.e., 2 frames?
I have never used the freedetect filter, but the documentation seems
quite clear. Your file is 30fps, so I guess if you set d=0.067, this
would detect a 2-frame freeze ? Just try and see if you get something
meaningful to you or not.
Nicolas
_______________________________________________
ffmpeg-user mailing list -- [email protected]
To unsubscribe send an email to [email protected]
