Opened 9 years ago

Closed 9 years ago

#69 closed defect (fixed)

potential issue with PPS reference layer location offsets

Reported by: johnnyVidyo Owned by: Vadim
Priority: minor Milestone: SHM-8.0
Component: SHM software Version: SHM-7.0
Keywords: Cc: Vadim, jct-vc@…

Description

There is a potential mismatch between SHM decoder behavior and semantics of the spec in the odd case that the PPS multilayer extension contains multiple reference layer location offsets with the same value of ref_loc_offset_layer_id[i]. The spec does not specify that different entries of ref_loc_offset_layer_id[i] must be unique. If multiple offsets for the same id are in the PPS, the spec's logic (F.7.3.2.3.3) dictates that the last offsets would overwrite any previous offsets applied to ref_loc_offset_layer_id[i].

The SHM decoder stores all offsets signaled in the PPS. When the decoder retrieves scaled reference layer offsets and reference region offsets, it calls functions TComPPS::getScaledRefLayerWindowForLayer() and TComPPS::getRefLayerWindowForLayer(), respectively. These functions search for the ref_loc_offset_layer_id[i], but begin with i=0 and increment. To follow spec, the loop should begin with i as the highest index (m_numScaledRefLayerOffsets-1) and decrement.

Alternatively, when parsing the offsets in the PPS extension, the decoder could simply store the reference layer location offsets and related flags in arrays indexed by ref_loc_offset_layer_id[i]. Then the decoder will match the spec, and the parameters can be more easily accessed by the reference layer id with no need for other levels of indices.

Change history (2)

comment:1 Changed 9 years ago by DefaultCC Plugin

  • Cc Vadim jct-vc@… added

comment:2 Changed 9 years ago by Vadim

  • Resolution set to fixed
  • Status changed from new to closed

fixed with rev 1035

Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber, Participant

  • Gerhard Tech(Always)
  • jct-vc@…(Subscriber)
  • johnnyVidyo(Reporter)
  • Karsten Suehring(Always)
  • Vadim Seregin(Owner, Subscriber, Participant)