Am 30.10.25 um 21:15 schrieb Paul B Mahol via ffmpeg-user:
On Thu, Oct 30, 2025 at 6:42 PM Richard Bartczak via ffmpeg-user <
[email protected]> wrote:
Am 30.10.25 um 19:33 schrieb Richard Bartczak:
Hello,
I assume to be on a good way if I use this as presuppostion :
ffprobe -loglevel error -select_streams v:0 -show_entries
packet=pts_time,flags,key -sexagesimal -of csv=print_section=0 "21
Bridges.ts" > txt
And here I got the info :
https://video.stackexchange.com/questions/19250/how-to-identify-i-frame-from-idr-frame-in-the-ffprobe-show-frames-output
"Frames with key_frame 1 (will have picture type I) are IDR frames.
I frames with key_frame 0 are not."
Now my question how to combine it ?
To get the timestamp and an indication of an IDR-frame ?
Regards
Richard
I am sorry,
it must be :
ffprobe -loglevel error -select_streams v:0 -show_entries
packet=pts_time,flags -sexagesimal -of csv=print_section=0 "21
Bridges.ts" > txt
packet : key removed
Regards
Richard
demuxed packet != decoded frame
_______________________________________________
ffmpeg-user mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
ffmpeg-user mailing list -- [email protected]
To unsubscribe send an email to [email protected]
I ssems, it is not possible with ffprobe and -skip_frame nokey:
ffprobe -loglevel error -select_streams v:0 -show_frames -sexagesimal
-skip_frame nokey -of csv=print_section=0 "Arizona Junior.ts" > txt
I got the output for every key_frame :
video,0,1,
The third entry does indicate key_frame 1, it does mean all I-frames are
IDR-Frames, that is wrong. I did check it with Avidemux, cut the h.264
video at an indicated IDR-Frame, got the correct hint by Avidemux it is
an NIDR-Frame, and the further video analysis leads to an error
indication :
[h264 @ 0x62ba725abf00] co located POCs unavailable
Any further idea ?
Regards
Richard
_______________________________________________
ffmpeg-user mailing list -- [email protected]
To unsubscribe send an email to [email protected]
