- 20 Sep, 2018 1 commit
-
-
Frank Bossen authored
remove SVN detection See merge request jvet/VVCSoftware_BMS!113
-
- 19 Sep, 2018 1 commit
-
-
Benjamin Bross authored
With new Xcode and clang-10.0 SVN revision number detection in CMakeLists.txt causes a compilation error with cyclic redundancies. - Fix by removing this feature completely. (useless in git repo) - Not affecting results
-
- 14 Sep, 2018 1 commit
-
-
Frank Bossen authored
-
- 13 Sep, 2018 2 commits
-
-
Frank Bossen authored
Ternary split: fix for issue #87 See merge request jvet/VVCSoftware_BMS!111
-
Karsten Suehring authored
Uses option #1 re-defining the meaning of maxTtSize being the longest side of the partition.
-
- 11 Sep, 2018 2 commits
-
-
Frank Bossen authored
Cpr para seq fix See merge request jvet/VVCSoftware_BMS!108
-
Xiaozhong Xu authored
-
- 10 Sep, 2018 4 commits
-
-
Xiang Li authored
Revert "Merge branch 'High_Precision_Motion_Vector_Storage' into 'master'" See merge request jvet/VVCSoftware_BMS!110
-
Xiang Li authored
Revert "Merge branch 'cfgUpdate2' into 'master'" See merge request jvet/VVCSoftware_BMS!109
-
Xiang Li authored
This reverts merge request !106
-
Xiang Li authored
This reverts merge request !107
-
- 09 Sep, 2018 4 commits
-
-
Xiang Li authored
Update cfg files See merge request jvet/VVCSoftware_BMS!107
-
Xiang Li authored
-
Xiang Li authored
-
Xiang Li authored
High precision motion vector storage See merge request jvet/VVCSoftware_BMS!106
-
- 08 Sep, 2018 4 commits
-
-
Frank Bossen authored
Cpr para fix See merge request jvet/VVCSoftware_BMS!105
-
Xiaozhong Xu authored
-
Yan Zhang authored
-
Yan Zhang authored
Fix a bug that lead to different result when the macro is on and off
-
- 07 Sep, 2018 2 commits
-
-
Yan Zhang authored
Motion vecotrs are always stored with 1/16-pel precision; highprec flag, setLow() and setHigh() functions are removed from the MV class; SPS HighPrecision flag is also removed. The following strategies are followed: 1. Motion vector data in the buffer are always stored in high precision. 2. Motion vector used for motion compensation are always in high precision. 3. Motion vector difference data are always in low precision. 4. Encoder side motion estimation always use low precision. 5. Motion vector bits calculation are always performed in low precision. 6. Candidates of motion vector prediction list are always in low precision.
-
Yan Zhang authored
Motion vecotrs are always stored with 1/16-pel precision and the High precision motion vector SPS flags are removed. The following strategies are followed: 1. Motion vector data in the buffer are always stored in high precision. 2. Motion vector used for motion compensation are always in high precision. 3. Motion vector difference data are always in low precision. 4. Encoder side motion estimation always use low precision. 5. Motion vector bits calculation are always performed in low precision. 6. Candidates of motion vector prediction list are always in low precision.
-
- 05 Sep, 2018 7 commits
-
-
Karsten Suehring authored
fix performance differences when CPR macro off and CPR on but config flag off See merge request jvet/VVCSoftware_BMS!103
-
Karsten Suehring authored
patch from bug report #84: encoder bug for affine 6-parameter search See merge request jvet/VVCSoftware_BMS!102
-
Karsten Suehring authored
K0248 GBI: fix interaction with Affine mode See merge request jvet/VVCSoftware_BMS!101
-
Yu-Chi Su authored
-
Karsten Suehring authored
Inter AMT encoder fix See merge request jvet/VVCSoftware_BMS!100
-
Xiaozhong Xu authored
flag off
-
Karsten Suehring authored
Patch provided by: Yuwen He
-
- 04 Sep, 2018 7 commits
-
-
Vadim Seregin authored
-
Vadim Seregin authored
-
Vadim Seregin authored
-
Vadim Seregin authored
move tools stats after STATS__TOOL_TOTAL_FRAME, otherwise it is not compiling with JEM_TOOLS = 0 due to 0 array size
-
Vadim Seregin authored
-
https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_BMSVadim Seregin authored
# Conflicts: # source/Lib/EncoderLib/EncCu.cpp # source/Lib/EncoderLib/EncCu.h
-
Yan Zhang authored
Motion vecotrs are always stored with 1/16-pel precision and the following strategies are followed: 1. Motion vector data in the buffer are always stored in high precision. 2. Motion vector used for motion compensation are always in high precision. 3. Motion vector difference data are always in low precision. 4. Encoder side motion estimation always use low precision. 5. Motion vector bits calculation are always performed in low precision. 6. Candidates of motion vector prediction list are always in low precision.
-
- 03 Sep, 2018 5 commits
-
-
Frank Bossen authored
use correct vector resolution in CPR search range setting See merge request jvet/VVCSoftware_BMS!97
-
Xiaozhong Xu authored
-
Vadim Seregin authored
-
Karsten Suehring authored
Remove bug fix macro under JVET_K0346 See merge request jvet/VVCSoftware_BMS!96
-
Frank Bossen authored
create BMS_TOOLS macro to switch all BMS only tools (including JEM_TOOLS) See merge request jvet/VVCSoftware_BMS!95
-