On Tue, Dec 15, 2015 at 4:41 PM, Andreas Cadhalpun <andreas.cadhal...@googlemail.com> wrote: > On 15.12.2015 08:17, Anton Khirnov wrote: >> Can you share the sample that shows the problem? > > I could, but it's of no use for comparing with libopus, because their > decoder errors out in an unrelated check. > >> From what I can see, libopus does not do any clipping at that point, so >> something else must ensure that there is no overflow. > > Indeed, the real problem is just a silly typo... > It might have been caused by the fact that the specification uses > i and k in exactly the opposite way than the code. > > New patch attached.
This patch might have been forgotten, ping reviewers. -- Vittorio _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
