From: Vittorio Giovara <vittorio.giovara@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Add DXV encoder with support for DXT1 texture format
Date: Fri, 19 Jan 2024 17:58:26 +0100
Message-ID: <CABLWnS8dKrQned0RfWs_ZkWMEMtLYPr5SLZK8o3k09nwpb51sQ@mail.gmail.com> (raw)
In-Reply-To: <1b399697-c663-4ebf-8268-a23b7d06b6ec@gmail.com>
On Fri, Jan 19, 2024 at 5:56 PM Connor Worley <connorbworley@gmail.com>
wrote:
> Thanks for the feedback! For the next revision, is it preferred to reply
> to this thread or create a new one?
>
here is fine
> On 1/19/24 08:23, Vittorio Giovara wrote:
> >> diff --git a/libavcodec/allcodecs.c b/libavcodec/allcodecs.c
> >> index 93ce8e3224..ef8c3a6d7d 100644
> >> --- a/libavcodec/allcodecs.c
> >> +++ b/libavcodec/allcodecs.c
> >> @@ -106,6 +106,7 @@ extern const FFCodec ff_dvvideo_encoder;
> >> extern const FFCodec ff_dvvideo_decoder;
> >> extern const FFCodec ff_dxa_decoder;
> >> extern const FFCodec ff_dxtory_decoder;
> >> +extern const FFCodec ff_dxv_encoder;
> >> extern const FFCodec ff_dxv_decoder;
> >>
> > nit: keep list in order
>
>
> Not sure what you mean, the present order seems to be encoder followed by
> decoder for codecs that have both.
>
disregard, I assumed it was in alphabetical order
> > What does the HT stand for?
>
>
> Hash table -- this change implements a simple linear probing approach.
>
got it, would be nice to have a small comment on why it's needed, as
documentation
> >> +#define LOOKBACK_WORDS 0x20202
> >> +
> >> +enum DXVTextureFormat {
> >> + DXV_FMT_DXT1 = MKBETAG('D', 'X', 'T', '1'),
> >> +};
> >>
> > Why would you go for an enum here? Just for future expansion and the
> switch
> > case below?
>
>
> Exactly, that's the plan.
>
very cool
--
Vittorio
_______________________________________________
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:[~2024-01-19 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 8:27 Connor Worley
2024-01-17 13:12 ` Michael Niedermayer
2024-01-17 16:55 ` Connor Worley
2024-01-17 20:45 ` Connor Worley
2024-01-17 20:57 ` Connor Worley
2024-01-19 16:23 ` Vittorio Giovara
2024-01-19 16:55 ` Connor Worley
2024-01-19 16:58 ` Vittorio Giovara [this message]
2024-01-19 17:07 ` [FFmpeg-devel] [PATCH v2] lavc/dxvenc: add " Connor Worley
2024-01-19 19:16 ` Connor Worley
2024-01-23 20:32 ` Vittorio Giovara
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=CABLWnS8dKrQned0RfWs_ZkWMEMtLYPr5SLZK8o3k09nwpb51sQ@mail.gmail.com \
--to=vittorio.giovara@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