On Wed, Sep 25, 2013 at 5:27 PM, Olivier Lapicque <[email protected]>wrote:
> Shouldn’t it be X265_MAX(m_numReorderPics[i]* + 2*, > _param->maxNumReferences*+1*) ?**** > > Unlike H.264, the picture is added to the DPB before being decoded (so the > current picture always takes up one slot in the DPB) > I was just staring at that line myself. It would probably be more clear to add the +1 after the X265_MAX. What I wasn't sure about was whether m_maxDecPicBuffering is supposed to also include the max B frame count as well. -- Steve
_______________________________________________ x265-devel mailing list [email protected] https://mailman.videolan.org/listinfo/x265-devel
