Custom query (105 matches)
Results (25 - 27 of 105)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#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. |
|||
#20 | fixed | Mismatch of SHVC draft 5 and SHM-5.0 software in bit-depth scalability with 1x scalability | Vadim | auyeung |
Description |
When bit-depth scalability is enabled with 1x spatial scalability, SHM-5.0 software does not match the specification of the resampling process in section H.8.1.4 of SHVC working draft 5. SHVC draft 5 section H.8.1.4 specifies that when the base layer and enhancement layer have the same picture sizes, same internal bit-depths, and zero scaled reference layer offsets, the inter-layer reference picture ilRefPic is set equal to the decoded reference layer picture rlPic. However in SHM-5.0, when the base layer and enhancement layer have the same picture sizes and zero scaled reference layer offset, the inter-layer reference picture ilRefPic is set equal to the decoded reference layer picture rlPic without checking the bit-depth difference of BL and EL. Consequently, SHM-5.0 does not support bit-depth scalability with 1x scalability in the inter-layer prediction process. This bug was reported in JCTVC-Q0130, and two implementations of the bug fix are in the software attached in JCTVC-P0130-v2 with the following two macros:
|
|||
#102 | fixed | NO_CLRAS_OUTPUT_FLAG may not be disabled | Vadim | kolya |
Description |
Build is not possible when NO_CLRAS_OUTPUT_FLAG 0 |