Hi,
On Tue, Dec 20, 2016 at 7:59 PM, Michael Niedermayer wrote:
> On Tue, Dec 20, 2016 at 07:51:05PM -0500, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Tue, Dec 20, 2016 at 7:44 PM, Michael Niedermayer
> > > wrote:
> >
> > > On Tue, Dec 20, 2016 at 05:23:06PM -0500, Ronald S. Bultje wrote:
> > >
On Tue, Dec 20, 2016 at 07:51:05PM -0500, Ronald S. Bultje wrote:
> Hi,
>
> On Tue, Dec 20, 2016 at 7:44 PM, Michael Niedermayer > wrote:
>
> > On Tue, Dec 20, 2016 at 05:23:06PM -0500, Ronald S. Bultje wrote:
> > > The checked bitstream reader does that already. To allow parsing of
> > > superf
Hi,
On Tue, Dec 20, 2016 at 7:44 PM, Michael Niedermayer wrote:
> On Tue, Dec 20, 2016 at 05:23:06PM -0500, Ronald S. Bultje wrote:
> > The checked bitstream reader does that already. To allow parsing of
> > superframes split over a packet boundary, we always decode the last
> > superframe in ea
On Tue, Dec 20, 2016 at 05:23:06PM -0500, Ronald S. Bultje wrote:
> The checked bitstream reader does that already. To allow parsing of
> superframes split over a packet boundary, we always decode the last
> superframe in each packet at the start of the next packet, even if
> theoretically we could
The checked bitstream reader does that already. To allow parsing of
superframes split over a packet boundary, we always decode the last
superframe in each packet at the start of the next packet, even if
theoretically we could have decoded it. The last superframe in the
last packet is decoded using
