Olivier, I couldn't reproduce the problem with b-frames enabled. I will be able to look into it better once I get the exact command line.
- Deepthi On Tue, Sep 24, 2013 at 1:25 AM, Steve Borho <[email protected]> wrote: > > > > On Mon, Sep 23, 2013 at 2:38 PM, Olivier Lapicque <[email protected]>wrote: > >> “(param->bframes+2)-1” seems correct for 1-backward and 1 forward >> reference (but seems like it would be too low for more than 2 refs). >> > > Yeah, we haven't re-enabled multiple refs yet after plugging in the new > lookahead. It should happen soon, though. > > >> **** >> >> The exact condition that was violated in the bitstream I saw is the >> following:**** >> >> NumNegativePics(4) + NumPositivePics(1) + num_long_term_sps(0) + >> num_long_term_pics(0) > max_dec_pic_buffering_minus1(3)+1**** >> >> ** ** >> >> I’ll get the exact cmdline parameters to reproduce this, but I was told >> that this problem occurs any time B-frames are enabled. >> > > Ah, ok. The problem is probably with NumNegativePics then. We'll take a > look at this. > > -- > Steve Borho > > > _______________________________________________ > x265-devel mailing list > [email protected] > https://mailman.videolan.org/listinfo/x265-devel > >
_______________________________________________ x265-devel mailing list [email protected] https://mailman.videolan.org/listinfo/x265-devel
