From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] lavc: deprecate avcodec_dct, av_fft, av_dct, av_rdft and av_mdct Date: Fri, 17 Feb 2023 14:08:53 -0300 Message-ID: <66307ef3-b214-47f6-6d4e-fbcc439f2004@gmail.com> (raw) In-Reply-To: <NOVI8Wy--3-9@lynne.ee> On 2/17/2023 1:54 PM, Lynne wrote: > This reverts commit 26cb36f35746fe6ef53688b119852bfa6d555f62. > > All filters and all codecs (except wmavoice) have been ported for the > lavu/tx API. > > The noise should be minimal. It isn't. I'm getting more than two thousand lines of warnings after applying this patch from libavfilter/vf_spp.c libavfilter/x86/vf_spp.c libavcodec/asvenc.c libavcodec/avdct.c libavcodec/avfft.c libavcodec/dct.c libavcodec/fdctdsp.c libavcodec/fft_float.c libavcodec/fft_init_table.c libavcodec/idctdsp.c libavcodec/jfdctfst.c libavcodec/jfdctint.c libavcodec/jrevdct.c libavcodec/mpegaudiodsp.c libavcodec/mpegvideo_enc.c libavcodec/rdft.c libavcodec/wmavoice.c libavcodec/x86/dct_init.c libavcodec/x86/fft_init.c libavcodec/x86/mpegvideoenc.c It's not just wmavoice, there's also mpeg and jpeg stuff, and one filter. For the actual fft/dct/rdft/mdct source files, you should use the deprecation warning pragmas to silence them, but the other modules need to be ported. This patch is also missing the schedule FF_API deprecation wrapper. > > Patch attached. > > > _______________________________________________ > 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:[~2023-02-17 17:08 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-17 16:54 Lynne 2023-02-17 17:08 ` James Almer [this message] 2023-02-17 18:45 ` Lynne 2023-02-17 23:59 ` Hendrik Leppkes 2023-02-18 11:52 ` Lynne 2023-02-18 13:15 ` James Almer [not found] ` <NOVgRri--3-9@lynne.ee-NOVgVXs----9> 2023-02-18 12:49 ` Lynne 2023-02-18 13:32 ` James Almer 2023-02-18 13:45 ` Lynne 2023-02-18 13:58 ` James Almer 2023-02-18 14:53 ` Lynne 2023-02-20 15:34 ` Anton Khirnov 2023-02-20 17:18 ` Lynne 2023-02-20 17:22 ` Anton Khirnov 2023-02-20 17:35 ` Lynne [not found] ` <NO_00XT--3-9@lynne.ee-NO_04wO----9> 2023-02-19 18:47 ` Lynne
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=66307ef3-b214-47f6-6d4e-fbcc439f2004@gmail.com \ --to=jamrial@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