From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] ffprobe: fix XML rendering, review XML layout
Date: Sun, 15 Oct 2023 03:09:14 +0200
Message-ID: <2b2a432b-7b28-4386-b5fe-d60dac09a4a2@rothenpieler.org> (raw)
In-Reply-To: <20231014172428.382368-1-stefasab@gmail.com>
On 14.10.2023 19:24, Stefano Sabatini wrote:
> Fix rendering of int values within a side data element, which was
> broken since commit d2d3a83ad93, where the side data element was
> correctly marked as a variable fields element. Logic to render a
> string variable was implemented already, but it was not implemented
> for the int fields path, which was enabled by that commit.
>
> Also, code and schema is changed in order to account for multiple
> variable-fields elements - such as side data, contained within the
> same parent. Previously it was assumed that a single variable-fields
> element was contained within the parent, which was the case for tags,
> but is not the case for side-data.
>
> Previously data was rendered as:
> <side_data_list>
> <side_data side_data_type="CPB properties" max_bitrate="0" min_bitrate="0" avg_bitrate="0" buffer_size="327680" vbv_delay="-1"/>
> </side_data_list>
>
> Now as:
> <side_data_list>
> <side_data type="CPB properties">
> <side_datum key="side_data_type" value="CPB properties"/>
> <side_datum key="max_bitrate" value="0"/>
> <side_datum key="min_bitrate" value="0"/>
> <side_datum key="avg_bitrate" value="0"/>
> <side_datum key="buffer_size" value="49152"/>
> <side_datum key="vbv_delay" value="-1"/>
> </side_data>
> </side_data_list>
Isn't a change like that practically an ABI break, and thus would need
to happen on a major bump?
Alternatively, just leave the old fields as they were, they looks like
they can coexist with the new ones. At least XML wise.
_______________________________________________
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".
next prev parent reply other threads:[~2023-10-15 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 17:24 Stefano Sabatini
2023-10-14 19:50 ` Stefano Sabatini
2023-10-15 17:15 ` Michael Niedermayer
2023-10-17 9:56 ` Stefano Sabatini
2023-10-18 21:44 ` Stefano Sabatini
2023-10-20 17:02 ` Stefano Sabatini
2023-10-15 1:09 ` Timo Rothenpieler [this message]
2023-10-15 2:59 ` Stefano Sabatini
2023-10-16 8:47 ` Tobias Rapp
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=2b2a432b-7b28-4386-b5fe-d60dac09a4a2@rothenpieler.org \
--to=timo@rothenpieler.org \
--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