Re: [FFmpeg-devel] [RFC] Shaping the AVTextFormat API Surface

["softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Nicolas
> George
> Sent: Montag, 5. Mai 2025 16:32
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [RFC] Shaping the AVTextFormat API Surface
> 
> Stefano Sabatini (HE12025-05-04):
> > I don't understand this claim. There is a root, and each section can
> > have several subsections, so it is a tree in my view, although we set
> > a maximum depth. Where am I wrong?
> 
> Are we looking at the same thing? In ffprobe's output, we have sections
> “packets”, “streams”, “format”, etc., and in each section items, but
> that does not go deeper.

Please look at those graphs to see that your assumptions are inaccurate:

https://softworkz.github.io/ffmpeg_output_apis/ffprobe_schema.html 
https://softworkz.github.io/ffmpeg_output_apis/graph_schema.html

One example in plain text:

root
  frames (1)
    frame (n)
      frame_tags (n)
      frame_side_data_list (1)
        frame_side_data (n)
          time_codes (1)
            time_code (n)
          frame_side_data_components (1)
            frame_side_data_component (n)
              frame_side_data_pieces (1)
                frame_side_data_piece (n)    


> Making this API generic is not an easy task, but it is doable. We should
> not settle for an inferior API just because the person who proposed it
> wrote the code before designing it properly and now is in a hurry to get
> it applied.

Like I said in my previous response already: I'm not intending to rush 
things in any way. I don't even have a use case for which the API needs
to be located in libavutil. Even when it remains to live in fftools for a 
year or longer, I'm still good with it.
You'll have plenty of time for suggesting improvements or submitting an 
XML writer the way you want it to be, and - given it would be compatible
with the AVTextFormat API - the API could use yours instead of the current
one.

Doors are open for your suggestions, as long as those will fit in to the 
AVTextFormat API logic or are improving it in a way that the consumption
sites don't need to be rewritten (adjustments are surely acceptable).

Best regards,
sw


_______________________________________________
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".