From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/wavdec: increase requested probe score for codec probe
Date: Fri, 9 May 2025 13:54:22 +0200 (CEST)
Message-ID: <1a1435b6-04d1-75de-47ae-f38fd23f0964@passwd.hu> (raw)
In-Reply-To: <20250509092108.GP29660@pb2>
On Fri, 9 May 2025, Michael Niedermayer wrote:
> On Fri, May 09, 2025 at 12:28:00AM +0200, Marton Balint wrote:
>> Codec probing was primarily added to the wav demuxer to support DTS-in-wav
>> files, but DTS probing functions return AVPROBE_SCORE_EXTENSION+1, so we can be
>> a bit more strict with the required score.
>>
>> This fixes MP3 misdetections for some wav files.
>>
>> Fixes ticket #11581.
>>
>> Signed-off-by: Marton Balint <cus@passwd.hu>
>> ---
>> libavformat/wavdec.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/libavformat/wavdec.c b/libavformat/wavdec.c
>> index dc7e49abc4..c65e0a2723 100644
>> --- a/libavformat/wavdec.c
>> +++ b/libavformat/wavdec.c
>> @@ -178,7 +178,7 @@ static void handle_stream_probing(AVStream *st)
>> {
>> if (st->codecpar->codec_id == AV_CODEC_ID_PCM_S16LE) {
>> FFStream *const sti = ffstream(st);
>> - sti->request_probe = AVPROBE_SCORE_EXTENSION;
>> + sti->request_probe = AVPROBE_SCORE_EXTENSION + 1;
>> sti->probe_packets = FFMIN(sti->probe_packets, 32);
>> }
>> }
>
> please add a testcase to fate, if possible. Such corner cases
> are important to be in fate
Sample is in the ticket, so it should be pretty trivial to do so. Can't we
fund someone to do this and the other fixed trac tickets without fate
tests?
Thanks,
Marton
_______________________________________________
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:[~2025-05-09 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 22:28 Marton Balint
2025-05-09 9:21 ` Michael Niedermayer
2025-05-09 11:54 ` Marton Balint [this message]
2025-05-10 15:19 ` Michael Niedermayer
2025-05-11 16:56 ` Marton Balint
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=1a1435b6-04d1-75de-47ae-f38fd23f0964@passwd.hu \
--to=cus@passwd.hu \
--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