Custom query (105 matches)
Results (4 - 6 of 105)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3 | fixed | Requirements on bitstream conformance for reference index for inter-layer sample based prediction | jlchen | Kenneth |
| Description |
It seems that there is missing some requirements on bitstream conformance when the SamplePredEnableFlag is equal to 1. It can be resolved by following addition in the end of H.8.5: It is also a requirement of bitstream conformance that the refIdxLX not corresponds to an inter-layer reference picture if SamplePredEnabledFlag [currLayerId][rLId] is equal to 0. |
|||
| #4 | fixed | Requirements on bitstream conformance for collocated reference index for inter-layer motion based prediction | jlchen | Kenneth |
| Description |
There seem to be missing some text to specify that when inter-layer motion prediction not is used for a certain layer the temporal collocated reference index cannot correspond to an inter-layer reference picture. It can be resolved by the following addition of text in H.8.5: When 8.5.3.2.7 (Derivation process for temporal luma motion vector prediction) is perfomed it is a requirement of bitstream conformance that the RefPicListX[collocated_ref_idx] not corresponds to an inter-layer reference picture when MotionSamplePredEnabledFlag [currLayerId][rLId] is equal to 0 |
|||
| #83 | fixed | LayerConfig Configuration Option Not Operational | Vadim | Prangnell |
| Description |
From software version SHM 5.1, the LayerConfig configuration option is not fully implemented; it is not active. For example, when using the command switch "-lc0" to specify a specific configuration file for the base layer, this command is ignored during the encoding process and no error is produced. The same is true for all layers. I have included a screenshot image (below) of the configuration option to which I am referring. In the TAppEncCfg.cpp source code file, the string variable "cfg_LayerCfgFile" in the public member function "parseCfg" of class "TAppEncCfg" (starting at line 338) is relevant to this issue.
|
|||
