Custom query (105 matches)

Filters
 
or
 
  
 
Columns

Show under each result:


Results (28 - 30 of 105)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Ticket Resolution Summary Owner Reporter
#37 fixed Undefined variables in H.8.1.4.2 jlchen cgisquet
Description

This was found in Draft 7 (JCTVC-R1008v7). This also seems to be present in the ITU-T prepublished recommendation T-REC-H.265-201410. Because of this, the milestone and version are probably incorrectly set.

The first issue is a typo, which causes xPb to be defined twice instead of yPb.

Furthermore, the variables xP and yP, although obvious in light of other sections, are undefined there.

A simplistic solution would be to change [xy]Pb to [xy]P to fix this.

The changed text would then read:

For each 16x16 prediction block of the resampled picture with the top-left luma sample location at ( xP, yP ), where xP = xB << 4 and yP = yB << 4, for xB = 0..( ( PicWidthInSamplesCurrY + 15 ) >> 4 ) − 1 and yB = 0..( ( PicHeightInSamplesCurrY + 15 ) >> 4 ) − 1, its motion and mode parameters rsPredMode[ xP][ yP ], rsMvLX[ xP][ yP ], rsRefIdxLX[ xP][ yP ], and rsPredFlagLX[ xP][ yP ], with X being equal to 0 and 1, PicHeightInSamplesCurrYare derived by applying the following ordered steps:

  1. The center location ( xPCtr, yPCtr ) of the luma prediction block is derived as follows:

xPCtr = xP + 8 (H-65) yPCtr = yP + 8 (H-66)

#111 fixed Underspecification for nuh_layer_id of ilRefPic in H.8.1.4 jlchen cgisquet
Description

In JCTVC-W0076, an issue was identified with a modification to the pred_weight_table( ) for the "Current Picture Reference" tool (aka IBC), therefore introduced during the development of the SCC extension.

We believe that, while the chosen text solution (layer ID check) is OK, it underlines a lack of clarity, if not an "under-specification", in SHVC. While this was informally discussed with Qualcomm experts, we also had a request for filing this very ticket, so that as many eyes as possible weigh on the issue.

Here's the excerpt we think shows the issue:

  • If equalPictureSizeAndOffsetFlag is equal to 1, BitDepthRefLayerY is equal to BitDepthCurrY, BitDepthRefLayerC is equal to BitDepthCurrC, SubWidthRefLayerC is equal to SubWidthCurrC, SubHeightRefLayerC is equal to SubHeightCurrC, and currColourMappingEnableFlag is equal to 0,
    • ilRefPic is set equal to rlPic.
  • Otherwise, the following steps apply:
    • The inter-layer reference picture ilRefPic is generated as follows:
    • The PicOrderCntVal value of ilRefPic is set equal to the PicOrderCntVal value of rlPic.
    • The nuh_layer_id value of ilRefPic is set equal to rLId
    • The variable currLayerId is set equal to the value of nuh_layer_id of the current picture.
    • When VpsInterLayerSamplePredictionEnabled[ LayerIdxInVps[ currLayerId ] ][ LayerIdxInVps[ rLId ] ] is equal to 1, the following steps apply:
    • [...]

Please note that:

  • The text in italic is our addition and not present in the current text; this is not a proposal, but an example of what we thing could be expected.
  • The text in bold hints at why we think it should be there: the reader, and the implementer, would expect explicit setting of values here. But the only reference to layer IDs are through local variables.

In discussing this with Qualcomm's SCC and SHVC text editors, the rationale to consider the current text as sufficient is that the layer setting would be part of a DPB operation.

We are happy to discuss the issue here, which looks to be more SHVC-related than SCC. We consider it an editorial issue, but are unsure of the corrective aspect, if any, and its consequence.

#21 fixed The code for deriving (xRL, yRL) for inter-layer motion parameter derivation seems to be wrong Vadim danny
Description

TComDataCU::getBaseColCU() derives iBX and iBY for the reference layer luma sample location. However, it seems to lack the following shifting operations as specified in Eq. (H-51) of Section H.8.1.4.2.1: iBX = (iBX >> 4) << 4; iBY = (iBY >> 4) << 4;

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Note: See TracQuery for help on using queries.