Custom Query (1442 matches)
Results (22 - 24 of 1442)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#279 | fixed | Some text bugs related to tiles: derivation of columnWidth[] etc. in 7.4.2.1 | bbross | yk |
Description |
Besides editorial bugs, all the four equations are not complete by missing one value for each array not covered. Suggested changes are as follows.
"The vector columnWidth[ ], specifying the width for every of the num_tile_columns_minus1 columns in units of treeblocks, is derived as follows."
"The vector rowHeight[ ], specifying the height for every of the num_tile_rows_minus1 rows in units of treeblocks, is derived as follows."
colBd[0] = 0 for( i = 0; i <= num_tile_columns_minus1; i++ )
rowBd[0] = 0 for( i = 0; i <= num_tile_rows_minus1; i++ )
|
|||
#280 | fixed | Semantics of num_ref_idx_l0_active_minus1 is incorrect. | bbross | hellman |
Description |
Context: Page 60, section 7.4.3 'Slice Header semantics' The description of 'num_ref_idx_l0_active_minus1' still has wording that's taken from H.264, including (shudder) MBAFF. There are no field, frame or any other kind of macroblocks. I believe that all the text starting with 'The range of num_ref_idx_l0_active_minus1 is specified as ..' should be replaced with: The range of num_ref_idx_l0_active_minus1 shall be in the range of 0 to 15, inclusive. |
|||
#281 | fixed | num_ref_idx_l0/l1_default_active_minus1 range is too large | bbross | hellman |
Description |
Context: page 56, section 7.4.2.2 'Picture Parameter set semantics' Description for num_ref_idx_l0/l1_default_active_minus1 says that the range is 0 to 31, inclusive. As confirmed at the last meeting, the maximum number of reference pictures is 16, so this range should be 0 to 15, inclusive. Note that this is in two places (one for l0, one for l1). |