- Feb 08, 2019
- Feb 07, 2019
-
-
Taoran Lu authored
-
Karsten Suehring authored
-
Karsten Suehring authored
- fix block statistics code for IBC mode after JVET_M0483_IBC - enable build of block statistics code, when ENABLE_TRACING is specified on the command line
-
Karsten Suehring authored
- removes old getIBCMode functions from SPSNext - fixes references to this function in * reshaper * hash based ME Note: SPSNext is going to be removed. Fixes can also be applied with the removal patch.
-
Frederic Barbier authored
-
- Feb 06, 2019
-
-
Frank Bossen authored
-
Frank Bossen authored
Remove JEM_USE_INTRA_BOUNDARY and HEVC_USE_4x4_DSTVII
-
Frank Bossen authored
Use a single array with elements that comprise scan x position, y position, and index into block instead of separate arrays. Simplify array initialization code
-
Frederic Barbier authored
-
- Feb 05, 2019
-
-
Frank Bossen authored
-
Frank Bossen authored
Remove unused contexts and split intra mode contexts into luma and chroma sets to align with text description
-
Frederic Barbier authored
-
Santiago de Luxán Hernández authored
-
Karsten Suehring authored
calculate and check shifts only when they are actually used
-
Heiko Schwarz authored
-
Adam Wieckowski authored
-
Heiko Schwarz authored
The integration of JVET_M0297_32PT_MTS_ZERO_OUT adds unnecessary code as well as unnecessary processing in the encoder quantization process. - The suggested change simplifies the code and avoids unnecessary processing for the zero-out region.
-
Heiko Schwarz authored
The suggested changes fix the following two issues: [1] For blocks with width>32 or height>32, the scan created in initRom() (file Rom.cpp) are only valid for the non-zero-out region. However, in Rom::xInitScanArrays() (file DepQuant.cpp), the zero-out region is also used. This has the effect that the array raster2id[] contains wrong values. As a consequence, wrong neighboring positions cpos[] are derived. Even though a previous fix (fix #161) ensures that the positions are clipped to a value inside the subblock, these positions could still be wrong. It is suggested to fix the issue by correctly considering the zero-out regions for larger blocks (which is the actual source of the problem). [2] In State::updateStateEOS(..), the array m_absLevelAndCtxInit should be set equal to zero if a skipped subblock is selected. Otherwise, it could be possible lead to a usage of wrongs contexts for following transform coefficients. In Rom::xInitScanArrays()
-
Adam Wieckowski authored
-
- Feb 04, 2019
-
-
Xiang Li authored
-
Xiang Li authored
-
Karl Sharman authored
Decoder analyser did not work. This corrects the problem, removes unused entries and corrects the orders of strings vs enum list.
-
Frank Bossen authored
-
Adam Wieckowski authored
-
Frederic Barbier authored
-
Frederic Barbier authored
-
Adam Wieckowski authored
-
Adam Wieckowski authored
-
Adam Wieckowski authored
-
Tobias Hinz authored
-
Tobias Hinz authored
-
Tobias Hinz authored
- Feb 03, 2019
-
-
Frank Bossen authored
-
Frank Bossen authored
Make sure that the position of the sample in the template falls in the same subblock as the current sample before subtracting the offset of the begining of the subblock. Refactor code to make lines fit within a reasonable of characters.
-
Frank Bossen authored
-
Frank Bossen authored
Large blocks, i.e. with either width or height equal to 64, have fewer coefficients. The number of coefficients should thus be set accordingly
-
Frank Bossen authored
-