On Fri, Jan 31, 2025 at 3:33 PM Marton Balint wrote:
>
>
>
> On Fri, 31 Jan 2025, Viraaj Raulgaonkar wrote:
>
> > On Fri, Jan 31, 2025 at 4:49 AM Marton Balint wrote:
> >>
> >>
> >>
> >> On Thu, 30 Jan 2025, Viraaj Raulgaonkar wrote:
> >>
> >> > If std_strict_compliance < FF_COMPLIANCE_STRICT, th
On Fri, 31 Jan 2025, Viraaj Raulgaonkar wrote:
On Fri, Jan 31, 2025 at 4:49 AM Marton Balint wrote:
On Thu, 30 Jan 2025, Viraaj Raulgaonkar wrote:
> If std_strict_compliance < FF_COMPLIANCE_STRICT, then warn the user of
> the invalid sample rate instead of returning an error. This allows
On Fri, Jan 31, 2025 at 4:49 AM Marton Balint wrote:
>
>
>
> On Thu, 30 Jan 2025, Viraaj Raulgaonkar wrote:
>
> > If std_strict_compliance < FF_COMPLIANCE_STRICT, then warn the user of
> > the invalid sample rate instead of returning an error. This allows the
> > sample rate to be decoded in certa
On Thu, 30 Jan 2025, Viraaj Raulgaonkar wrote:
If std_strict_compliance < FF_COMPLIANCE_STRICT, then warn the user of
the invalid sample rate instead of returning an error. This allows the
sample rate to be decoded in certain cases.
Fixes Trac Ticket #11361.
---
libavformat/riffdec.c | 7 +++
If std_strict_compliance < FF_COMPLIANCE_STRICT, then warn the user of
the invalid sample rate instead of returning an error. This allows the
sample rate to be decoded in certain cases.
Fixes Trac Ticket #11361.
---
libavformat/riffdec.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-
