From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] fftools/ffprobe: fix printing side data components and pieces Date: Tue, 5 Mar 2024 11:49:38 -0300 Message-ID: <48f25054-c5ce-4d3f-91c8-d89fbff70c35@gmail.com> (raw) In-Reply-To: <ZecvdM4y5246BxF3@mariano> On 3/5/2024 11:43 AM, Stefano Sabatini wrote: > On date Tuesday 2024-03-05 11:38:20 -0300, James Almer wrote: >> On 3/5/2024 11:34 AM, Stefano Sabatini wrote: >>> On date Monday 2024-03-04 15:56:46 -0300, James Almer wrote: >>>> Components and pieces are side data specific fields and there's a variable >>>> amount of them. >>>> They also need to be identified in some form, so print a type too. >>>> >>>> Signed-off-by: James Almer <jamrial@gmail.com> >>>> --- >>>> You can see the difference with >>>> >>>> ffprobe -show_frames -of compact $fate_samples/mov/dovi-p7.mp4 >>>> ffprobe -show_frames -of xml $fate_samples/mov/dovi-p7.mp4 >>>> >>>> fftools/ffprobe.c | 33 +++++++++++++++++++++++++++------ >>>> 1 file changed, 27 insertions(+), 6 deletions(-) >>>> > [...] >>> LGTM. Not clear if this is fixing a regression or if the format (at >>> least for XML/compact) was always wrong. >> > >> I'm on the fence on this. Try removing the SECTION_FLAG_HAS_TYPE from >> SECTION_ID_FRAME_SIDE_DATA_COMPONENT and SECTION_ID_FRAME_SIDE_DATA_PIECE >> and the output is broken again for the compact output. So at least >> compact_print_section_header() may be faulty. I did not investigate much >> because I'm not familiar with the code. > > That is, if you define the type (as in the current implementation) it > looks correct? Yes. Without the type, the unexpected line breaks return. So the path in compact_print_section_header() taken when SECTION_FLAG_HAS_TYPE is not set may be wrong. > >> In any case, this change is needed because of the >> SECTION_FLAG_HAS_VARIABLE_FIELDS addition for side data where the printed >> fields are not a fixed amount. > > Agree. > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@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-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2024-03-05 14:49 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-04 18:56 James Almer 2024-03-05 14:34 ` Stefano Sabatini 2024-03-05 14:38 ` James Almer 2024-03-05 14:43 ` Stefano Sabatini 2024-03-05 14:49 ` James Almer [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=48f25054-c5ce-4d3f-91c8-d89fbff70c35@gmail.com \ --to=jamrial@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git