Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
V
VVCSoftware_BMS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Custom Issue Tracker
    • Custom Issue Tracker
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • jvet
  • VVCSoftware_BMS
  • Merge Requests
  • !106

Merged
Opened Sep 08, 2018 by Yan Zhang@YanZhangContributor

High precision motion vector storage

  • Overview 0
  • Commits 5
  • Pipelines 2
  • Changes 29

Motion vecotrs are always stored with 1/16-pel precision; highprec flag, setlowPrec() and sethighPrec() functions are removed from the MV class; SPS flag indicate whether high precision motion vector is used 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.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: jvet/VVCSoftware_BMS!106
Source branch: High_Precision_Motion_Vector_Storage

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.