From: "Raphaël Zumer" <raphael.zumer@vimeo.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/avutil: move dynamic HDR metadata parsing to libavutil
Date: Mon, 13 Mar 2023 12:56:34 -0400
Message-ID: <9e7b3d32-2b88-11e8-b5de-fbc0dcf95031@vimeo.com> (raw)
In-Reply-To: <AS8P250MB074499049F35CE71199098FF8FB99@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>
On 3/13/23 12:09, Andreas Rheinhardt wrote:
>>
>> +/**
>> + * Parse the user data registered ITU-T T.35 to AVbuffer (AVDynamicHDRVivid).
>> + * @param s A pointer containing the decoded AVDynamicHDRVivid structure.
>> + * @param data The byte array containing the raw ITU-T T.35 data.
>> + * @param size Size of the data array in bytes.
>> + *
>> + * @return 0 if succeed. Otherwise, returns the appropriate AVERROR.
>> + */
>> +int av_dynamic_hdr_vivid_from_t35(AVDynamicHDRVivid *s, const uint8_t *data,
>> + int size);
> Who has an interest in this function being public?
>
> - Andreas
I have no need for it so can change it to avpriv_ considering there's no serialization function available for it, if there's no objection to that.
Raphaël Zumer
_______________________________________________
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-03-13 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 17:33 Raphaël Zumer
2023-03-12 19:08 ` James Almer
2023-03-13 16:09 ` Andreas Rheinhardt
2023-03-13 16:56 ` Raphaël Zumer [this message]
2023-03-13 16:58 ` James Almer
2023-03-13 17:05 ` Raphaël Zumer
2023-03-13 17:10 ` James Almer
2023-03-13 17:34 ` Raphaël Zumer
2023-03-13 17:42 ` James Almer
[not found] <ec92f40f-0d6b-109b-d48e-1f24a0106f4b@tebako.net>
2023-02-27 16:53 ` Raphaël Zumer
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=9e7b3d32-2b88-11e8-b5de-fbc0dcf95031@vimeo.com \
--to=raphael.zumer@vimeo.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