From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] PATCH - libmad MP3 decoding support
Date: Mon, 2 May 2022 20:36:38 +0200
Message-ID: <f332ac45-069a-2d21-41b5-0df414a17b0b@rothenpieler.org> (raw)
In-Reply-To: <9gALEgkn.1651513526.6738600.dif@localhost>
On 02.05.2022 19:45, David Fletcher wrote:
> On 2/5/2022, "Nicolas George" <george@nsup.org> wrote:
>> Is there a trac ticket? If not, please fill one: we would not want to
>> keep that bug.
>>
>> Regards,
>>
>> --
>> Nicolas George
>
> Hi Nicolas,
>
> I'll prepare a test case to demonstrate the issue and fill in a ticket.
> As far as I can tell this is an issue affecting older ARM hardware, it
> cannot be reproduced on x86 hardware. I now have some additional ARM
> hardware with a more capable CPU which should help pin down the problem.
>
> Best regards, David.
That sounds like a pretty serious issue to me, and I'd rather see that
fixed than an entire other decoder library pulled in, just to work
around it.
_______________________________________________
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:[~2022-05-02 18:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2022-05-02 19:24 ` Martin Storsjö
2022-05-04 23:47 David Fletcher
2022-05-06 18:29 ` Lynne
2022-05-07 11:43 David Fletcher
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=f332ac45-069a-2d21-41b5-0df414a17b0b@rothenpieler.org \
--to=timo@rothenpieler.org \
--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