Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
V
VVCSoftware_BMS
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Milestones
  • JVET Trac bug tracker
    • JVET Trac bug tracker
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • jvet
  • VVCSoftware_BMS
  • Merge Requests
  • !99

Closed
Opened Sep 04, 2018 by Yan Zhang@YanZhang
  • Report abuse
Report abuse

1/16-pel motion vector storage

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.

Check out, review, and merge locally

Step 1. Fetch and check out the branch for this merge request

-# All repo/branch refs have been quoted to allow support for special characters (such as #my-branch)
git fetch "https://vcgit.hhi.fraunhofer.de/YanZhang/VVCSoftware_BMS.git" "High_Precision_MV_Storage"
git checkout -b "YanZhang/VVCSoftware_BMS-High_Precision_MV_Storage" FETCH_HEAD

Step 2. Review the changes locally

Step 3. Merge the branch and fix any conflicts that come up

git fetch origin
git checkout "origin/master"
git merge --no-ff "YanZhang/VVCSoftware_BMS-High_Precision_MV_Storage"

Step 4. Push the result of the merge to GitLab

git push origin "master"

Note that pushing to GitLab requires write access to this repository.

Tip: You can also checkout merge requests locally by following these guidelines.

  • Discussion 3
  • Commits 2
  • Pipelines 2
  • Changes 22
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
0
Labels
None
Assign labels
  • View project labels
Reference: jvet/VVCSoftware_BMS!99