Custom Query (1442 matches)
Results (4 - 6 of 1442)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#659 | fixed | "byte_alignment" presence condition in the slice_data syntax is not correct for tiles_enabled_flag=1 and entropy_coding_sync_enabled_flag=1 | bbross | chung |
Description |
In chapter 7.3.4.1 of JCTVC-J1003_d3, the condition for the presence of byte_alignment() is : if( !end_of_slice_flag &&
My understanding is that the byte_alignment is used for the entry_points of a slice. The condition is not correct, when tiles_enabled_flag=1 and entropy_coding_sync_enabled_flag=1. Indeed, in this case, there is an entry_point per tile Ctb row. Let's define the function TileWidthInCtbs[TileId], that returns the width of tile TileId in unit of Ctb. (If tiles_enabled_flag=0, this returns the picture width in unit of Ctb) The condition above becomes : if( !end_of_slice_flag &&
|
|||
#521 | fixed | "max_dec_pic_buffering" without index is not defined. | bbross | sasai |
Description |
max_dec_pic_buffering[ i ] sometimes appears with its index "[ i ]" and sometimes without it. Annex A. A4.1 Annex C C.3.1, C.4 and C.5.2 Replace max_dec_pic_buffering by max_dec_pic_buffering[ max_temporal_layers_minus1 ] |
|||
#614 | invalid | "mvd_l1_zero_flag" is used without definition | bbross | Feng Zou |
Description |
In I1003 D7 WD, "mvd_l1_zero_flag" is used in 7.3.7 Prediction unit syntax. It is a flag to determine whether the MVD from Pred_L1 is transmitted or not. However, this flag is not defined at all in the current version WD. |