On Sun, Jan 12, 2025 at 6:24 AM James Almer <jamr...@gmail.com> wrote:
> On 1/11/2025 3:40 AM, Nuo Mi wrote: > > Tested with: > > ``` > > wget > https://www.itu.int/wftp3/av-arch/jvet-site/bitstream_exchange/VVC/draft_conformance/draft6/CodingToolsSets_E_Tencent_1.zip > > unzip CodingToolsSets_E_Tencent_1.zip CodingToolsSets_E_Tencent_1.bit > > ffprobe -hide_banner CodingToolsSets_E_Tencent_1.bit -select_streams v > -show_frames -show_entries frame=pict_type,key_frame -of csv > > ``` > > > > From > > ``` > > frame,0,? > > frame,0,? > > frame,0,? > > frame,0,? > > frame,0,? > > frame,0,? > > frame,0,? > > frame,0,? > > frame,0,? > > ``` > > > > To: > > ``` > > frame,1,I > > frame,0,B > > frame,0,B > > frame,0,B > > frame,0,B > > frame,0,B > > frame,0,B > > frame,0,P > > frame,0,B > > ``` > > > > fixes https://trac.ffmpeg.org/ticket/11406 > > The subject should be something like "lavc/vvc/refs: export keyframe and > picture type in output frames". No reason to mention ffprobe, as this is > not about what library users will do with the introduced changes, but > what the changes are about in lavc. > Thank you for the suggestion, fixed by v2 > > Also, I'm surprised the decoder hasn't signaled keyframes all this time. > If we have a container, it will signal key frame information. I believe this is only relevant for raw bitstreams. Please correct me if I'm wrong, @Ruben Gonzalez. > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
