From: Nuo Mi <nuomi2021@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] rtp enc/dec update for vvc Date: Sat, 15 Jun 2024 21:14:37 +0800 Message-ID: <CAFXK13dEx3XHbBKu_ZqTR4ET3a6LEQj8iHz9X94hKFvUPQ28wg@mail.gmail.com> (raw) In-Reply-To: <79f412d6-74b1-49bc-a2c4-3e5a479e934b@frankplowman.com> On Sat, Jun 15, 2024 at 2:38 AM Frank Plowman <post@frankplowman.com> wrote: > Hi, > > Thanks for the patch. Unfortunately it looks to be corrupted and does > not apply. Also, it looks as though you submitted five near-identical > patches. I would suggest you try directing patches to your own mailbox > and re-applying them while debugging the formatting issues, rather than > sending lots of corrupted patches to the ML. > Hi ftaft, Thank you for the patch. you can refer to https://ffmpeg.org/developer.html#Introduction for the checklist. > > \ No newline at end of file > > diff --git a/configure b/configure > > index 83284427df..d331688eb4 100755 > > --- a/configure > > +++ b/configure > > @@ -296,6 +296,7 @@ External library support: > > --enable-libwebp enable WebP encoding via libwebp [no] > > --enable-libx264 enable H.264 encoding via x264 [no] > > --enable-libx265 enable HEVC encoding via x265 [no] > > + --enable-libvvenc enable H.266/VVC encoding via vvenc [no] > > This looks like you had the VVenC patchset applied when you created this > commit. If your patch depends on the VVenC patchset, it will have to > wait until that is applied (which could well be in the next day or two). > Hi ftaft, I have pushed the libvvenc patch. You can rebase and send your patch again. > > > --enable-libxeve enable EVC encoding via libxeve [no] > > --enable-libxevd enable EVC decoding via libxevd [no] > > --enable-libxavs enable AVS encoding via xavs [no] > > @@ -1867,6 +1868,7 @@ EXTERNAL_LIBRARY_GPL_LIST=" > > libvidstab > > libx264 > _______________________________________________ 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-06-15 13:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-14 2:35 ftaft2000 2024-06-14 18:38 ` Frank Plowman 2024-06-15 13:14 ` Nuo Mi [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-06-14 2:33 Robin shi 2024-06-14 2:20 ftaft2000 [not found] ` <MEYP282MB159238A1D829588D19DB4AACA6C22@MEYP282MB1592.AUSP282.PROD.OUTLOOK.COM> 2024-06-14 2:29 ` Robin shi 2024-06-14 2:17 ftaft2000
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=CAFXK13dEx3XHbBKu_ZqTR4ET3a6LEQj8iHz9X94hKFvUPQ28wg@mail.gmail.com \ --to=nuomi2021@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