Skip to content
Snippets Groups Projects
  1. Oct 25, 2019
  2. Oct 19, 2019
  3. Oct 15, 2019
  4. Aug 25, 2019
  5. Aug 14, 2019
  6. Aug 09, 2019
  7. Aug 02, 2019
  8. Jul 29, 2019
  9. Jul 25, 2019
    • Yin Zhao's avatar
      JVET-O0193: remove transform depth in cbf ctx · f7e87bce
      Yin Zhao authored
      Note: in VVC draft 6 "–	If intra_bdpcm_flag[ ][ ] is equal to 1, ctxInc is set equal to 1.", which was set equal to 4 in VTM5. This integration also implements this change, to align cbf ctx with VVC draft 6.
      f7e87bce
  10. Jul 22, 2019
  11. Jul 20, 2019
    • Brian Heng's avatar
      Fix for Ticket #311 Scaling List Bugs · 29305d37
      Brian Heng authored
        - Previous fix broke dependent  quantization for the non-scaling list case.
        - Negative shift values are no longer set to zero, so the shift is applied repeatedly to the fixed invQScale value (g_invQuantScales) during each loop.
      29305d37
  12. Jul 19, 2019
  13. Jul 17, 2019
  14. Jul 15, 2019
  15. Jun 04, 2019
  16. May 28, 2019
  17. May 27, 2019
  18. May 23, 2019
  19. May 09, 2019
  20. Apr 27, 2019
  21. Apr 26, 2019
  22. Apr 10, 2019
  23. Apr 08, 2019
  24. Apr 03, 2019
  25. Apr 01, 2019
  26. Mar 11, 2019
  27. Mar 04, 2019
  28. Feb 08, 2019
  29. 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
  30. 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
  31. Feb 03, 2019
Loading