From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec: add Radiance HDR image format support
Date: Wed, 6 Jul 2022 21:29:22 +0200
Message-ID: <CAPYw7P4Wf_tXGS_DkBhqr67yjBySOqexAJaXCzHvo=THr+h=TA@mail.gmail.com> (raw)
In-Reply-To: <0c761087-abca-3934-fcf7-5c2a2a38e88e@gmail.com>
On Wed, Jul 6, 2022 at 8:50 PM James Almer <jamrial@gmail.com> wrote:
> On 7/6/2022 3:47 PM, Paul B Mahol wrote:
> > Added parser.
> > The test will be added after this is merged.
>
> [...]
>
> > diff --git a/libavformat/img2.c b/libavformat/img2.c
> > index 870d2ebbc5..b03075f3b0 100644
> > --- a/libavformat/img2.c
> > +++ b/libavformat/img2.c
> > @@ -91,6 +91,7 @@ const IdStrMap ff_img_tags[] = {
> > { AV_CODEC_ID_VBN, "vbn" },
> > { AV_CODEC_ID_JPEGXL, "jxl" },
> > { AV_CODEC_ID_QOI, "qoi" },
> > + { AV_CODEC_ID_HDR, "hdr" },
>
> This could end up confusing people, so preferably use RHDR or some other
> combination for the codec id.
>
Take it or leave it.
IT is HDR, not going to change.
Confusing can not happen at all it is codec.
>
> > { AV_CODEC_ID_NONE, NULL }
> > };
>
> _______________________________________________
> 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".
next prev parent reply other threads:[~2022-07-06 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 15:45 Paul B Mahol
2022-07-05 17:12 ` Anton Khirnov
2022-07-06 18:47 ` Paul B Mahol
2022-07-06 18:50 ` James Almer
2022-07-06 19:29 ` Paul B Mahol [this message]
2022-07-06 19:03 ` James Almer
2022-07-06 19:09 ` Andreas Rheinhardt
2022-07-06 19:12 ` James Almer
2022-07-06 19:21 ` Andreas Rheinhardt
2022-07-09 8:16 ` Paul B Mahol
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='CAPYw7P4Wf_tXGS_DkBhqr67yjBySOqexAJaXCzHvo=THr+h=TA@mail.gmail.com' \
--to=onemda@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