In Table D.2.43 - Motion-constrained tile sets extraction information sets SEI message syntax, the loops around *ps_rbsp_data_byte[ i ][ j ][ k ] syntax elements suffer from an "off-by-one" loop condition.

"<" instead of "<=" should be used to transmit the number of bytes indicated in *ps_rbsp_data_length[ i ][ j ] syntax elements.

I'm trying to encode yuv video (1080p , Bit depth:8 bit ,Frame Rate: 120 fps (progressive) ) im using HM-16.18+SCM-8.7 , this is my code in f.cfg file :

InputFile : Jockey_1920x1080_120fps_420_8bit_YUV.yuv InputBitDepth: 8 FrameRate : 120 FrameSkip : 0 SourceWidth : 1920 SourceHeight : 1080 FramesToBeEncoded : 1 I'm using this command in CMD :

TAppEncoder.exe -c encoder_intra_main.cfg -c f.cfg

when I open the output file I get a green screen

​https://i.stack.imgur.com/Vkhif.png

Table rangeTabLps which was corresponding to Table 9-46 in standard specification, lists all lps range of every state. But, rangeTabLps still exists "interval inversion" problem, that is, the subinterval for the MPS may be smaller than the subinterval for the LPS. for example:

pStateIdx equals to 1 and qRangeIdx equals to 2, and lps symbol occurs, then m_uiRange equals to 167 which was smaller than 256, so m_uiRange = (m_uiRange << 1) = 334, because of lps symbol, the pStateIdx will translate to 0 and uiLPS = TComCABACTables::sm_aucLPSTable[0][ ( 334 >> 6 ) & 3 ] = 176, so, mps_range = m_uiRange - uiLPS = 334 - 176 = 158, which will cause mps_range < lps_range, that is a bug?