From: "David Fletcher" <David@megapico.co.uk> To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] PATCH - libmad MP3 decoding support Date: Sat, 07 May 2022 11:43:02 +0000 Message-ID: <T8QuCMdz.1651923782.6918480.dif@localhost> (raw) On Fri May 6 21:29:51 EEST 2022 Lynne dev at lynne.ee wrote: > I disagree with this patch. The native decoder should be fixed instead, > or if it's not able to be fixed, users should use specialized libraries. > We're not adding a yet another decoding library to fix an issue on > very old ARM chips. > I suspect the problem is with the MDCT. We already have a better and > more precise fixed-point MDCT in libavutil/tx. The plan was to replace > the MDCT in mp3 once lavu/tx has more assembly, but if it helps, > should be fine to replace it now. Hi Lynne, I don't have a strong feeling either way. The patch (an earlier version) is already doing what I needed in the application with the Reciva radios. I posted it here to contribute back to FFmpeg, but if there's a better way to fix the problem that's great. If there's a better version of MDCT integrated into the native mp3 fixed point decoder I can test that on the ARMv4 hardware to see if the decoding bug is fixed. Certainly these are old chips but still lots of them around - a big part of them being useful is the assembly optimisations otherwise everything just slows down too much. Best regards, David. _______________________________________________ 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 reply other threads:[~2022-05-07 11:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-07 11:43 David Fletcher [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-05-04 23:47 David Fletcher 2022-05-06 18:29 ` Lynne 2022-05-01 23:16 David Fletcher 2022-05-02 7:19 ` Paul B Mahol 2022-05-02 17:41 ` David Fletcher 2022-05-02 18:46 ` Neal Gompa 2022-05-02 22:50 ` David Fletcher 2022-05-03 18:34 ` David Fletcher 2022-05-04 2:16 ` Andreas Rheinhardt 2022-05-02 9:47 ` Nicolas George 2022-05-02 17:45 ` David Fletcher 2022-05-02 18:36 ` Timo Rothenpieler 2022-05-02 19:24 ` Martin Storsjö
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=T8QuCMdz.1651923782.6918480.dif@localhost \ --to=david@megapico.co.uk \ --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