Skip to content
Snippets Groups Projects
  1. Jul 15, 2019
  2. Jun 04, 2019
  3. May 28, 2019
  4. May 27, 2019
  5. May 23, 2019
  6. May 09, 2019
  7. Apr 27, 2019
  8. Apr 26, 2019
  9. Apr 10, 2019
  10. Apr 08, 2019
  11. Apr 03, 2019
  12. Apr 01, 2019
  13. Mar 11, 2019
  14. Mar 04, 2019
  15. Feb 08, 2019
  16. Feb 06, 2019
    • Frank Bossen's avatar
      Clean up scan data arrays · 5fa715f1
      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
      5fa715f1
  17. Feb 05, 2019
    • Heiko Schwarz's avatar
      added guard "#if JVET_M0257" as requested · d84aaf95
      Heiko Schwarz authored
      d84aaf95
    • Heiko Schwarz's avatar
      Cleanup: Remove unnecessary code/proc for zero-out · 68ea4ba5
      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.
      68ea4ba5
    • Heiko Schwarz's avatar
      Fix: Prevents usage of wrong contexts in DepQuant · ddf9fb96
      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()
      ddf9fb96
  18. Feb 03, 2019
  19. Feb 02, 2019
  20. Feb 01, 2019
  21. Jan 31, 2019
  22. Jan 25, 2019
  23. Jan 23, 2019
  24. Jan 18, 2019
  25. Nov 26, 2018
  26. Nov 06, 2018
Loading