From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/amv: use correct quantize tables Date: Mon, 10 Apr 2023 01:42:56 +0200 Message-ID: <20230409234256.GG1164690@pb2> (raw) In-Reply-To: <CAFUs7TSdiGO_SBsSDC6hXaea6ZkXt6zkBLfigVaAMX4KkqCd2Q@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1538 bytes --] On Sun, Apr 09, 2023 at 04:37:49PM +0800, AlexGuo1998 wrote: > So sorry that gmail trashed the patch. Re-sent as an attachment. > From 14910cef473a2858d5cf5e3bf855730762456de1 Mon Sep 17 00:00:00 2001 > From: AlexGuo1998 <AlexGuo1998@163.com> > Date: Sun, 9 Apr 2023 15:57:05 +0800 > Subject: [PATCH] avcodec/amv: use correct quantize tables > > The official encoder has a mode to generate mjpeg AVI files, which > embeds the correct quantize table. Change the table we use (both encoder > and decoder) to match that. > > Signed-off-by: AlexGuo1998 <AlexGuo1998@163.com> > --- > libavcodec/mpegvideo_enc.c | 16 +++++++--------- > libavcodec/sp5x.h | 21 +++++++++++++++++++++ > libavcodec/sp5xdec.c | 9 +++++++-- > 3 files changed, 35 insertions(+), 11 deletions(-) decoder and encoder changes should be in seperate patches and the version should be increased for encoder changes so any software reading a file can from a bitstream version metadata indentify it. For this to work of course the version first needs to be stored. So one should check LIBAVCODEC_IDENT is stored This would then also allow the decoder to match the encoder optimally thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB "You are 36 times more likely to die in a bathtub than at the hands of a terrorist. Also, you are 2.5 times more likely to become a president and 2 times more likely to become an astronaut, than to die in a terrorist attack." -- Thoughty2 [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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-04-09 23:43 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-09 8:20 AlexGuo1998 2023-04-09 8:37 ` AlexGuo1998 2023-04-09 23:42 ` Michael Niedermayer [this message] 2023-04-10 4:09 ` AlexGuo1998 2023-04-10 14:17 ` Michael Niedermayer
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=20230409234256.GG1164690@pb2 \ --to=michael@niedermayer.cc \ --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