Signalling each EO class for luma and chroma are fixed 2-bit syntax elements.Signalling BO class luma and chroma are fixed 5-bit syntax elements. As you said signalling offsets depend upon input sequence, shich I have already done. Again signalling sao type(EO or BO) is fixed length syntax elements irrespective of input sequence. I have tested with different input sequence and the code also says same thing. I checked the standard and HEVC book.
On Wed, Apr 6, 2016 at 9:16 PM, chen <[email protected]> wrote: > >- m_entropyCoder.load(m_rdContexts.temp); > >- m_entropyCoder.resetBits(); > >- > >- for (int compIdx = 0; compIdx < 2; compIdx++) > >- m_entropyCoder.codeSaoOffsetEO(m_offset[compIdx + 1][typeIdx] + > >1, typeIdx, compIdx + 1); > >- > >- uint32_t estRate = m_entropyCoder.getNumberOfWrittenBits(); > >- int64_t cost = calcSaoRdoCost((estDist[0] + estDist[1]), estRate, > >lambda[1]); > >+ // sao_eo_class_luma and sao_eo_class_chroma are fixed-length 2-bit > >syntax elements. > >+ cost += eo_type_cost + calcSaoRdoCost(0, 2, lambda[1]); > > > it is not fixed-length, the codeSaoOffsetEO output depends on Offset and > plane_idx, it is different in difference input sequence > > > _______________________________________________ > 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
