From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avformat/riffdec: remove invalid sample rate check
Date: Sat, 25 Jan 2025 02:26:27 +0100
Message-ID: <20250125012627.GH4991@pb2> (raw)
In-Reply-To: <20250125011952.GG4991@pb2>
[-- Attachment #1.1: Type: text/plain, Size: 1590 bytes --]
On Sat, Jan 25, 2025 at 02:19:52AM +0100, Michael Niedermayer wrote:
> Hi
>
> On Tue, Jan 21, 2025 at 05:30:05PM +0530, Viraaj Raulgaonkar wrote:
> > Sample rates up to 2^31 - 1 are considered valid, while greater values
> > are invalid. Removing the check potentially allows the sample rate
> > to be decoded in all cases instead of halting demux for values
> > greater than 2^31 - 1.
> >
> > Fixes Trac ticket #11361.
> > ---
> > libavformat/riffdec.c | 5 -----
> > 1 file changed, 5 deletions(-)
> >
> > diff --git a/libavformat/riffdec.c b/libavformat/riffdec.c
> > index b7a85a6ab2..94dccb324e 100644
> > --- a/libavformat/riffdec.c
> > +++ b/libavformat/riffdec.c
> > @@ -179,11 +179,6 @@ int ff_get_wav_header(void *logctx, AVIOContext *pb,
> >
> > par->bit_rate = bitrate;
> >
> > - if (par->sample_rate <= 0) {
> > - av_log(logctx, AV_LOG_ERROR,
> > - "Invalid sample rate: %d\n", par->sample_rate);
> > - return AVERROR_INVALIDDATA;
> > - }
>
> the API does not really allow negative sample rates
If you want to export the stored sample rate value correctly, this would
need a API change (which is a alot of work and seems not justified here)
Otherwise, simply print a warning and return sample_rate/2 instead
(assuming that works, does it work ?)
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Some people wanted to paint the bikeshed green, some blue and some pink.
People argued and fought, when they finally agreed, only rust was left.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-01-25 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 12:00 Viraaj Raulgaonkar
2025-01-25 1:19 ` Michael Niedermayer
2025-01-25 1:26 ` Michael Niedermayer [this message]
2025-01-26 10:42 ` Viraaj Raulgaonkar
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=20250125012627.GH4991@pb2 \
--to=michael@niedermayer.cc \
--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