Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • dav1d dav1d
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VideoLAN
  • dav1ddav1d
  • Issues
  • #48
Closed
Open
Created Oct 01, 2018 by James Almer@jamrialDeveloper

Artifacts in a sample with delayed random access points

delayed.ivf

They can be seen in the frames right after said points.

I'm not entirely sure if the sample is spec compliant, for that matter. I made it today with aomenc git head, and noticed that while section 7.6.2 states that the Sequence Header should be in the same TU as the coded key frame, in here it's in the same TU as the recovery point (frame with show_existing_frame pointing to the delayed key frame). It shouldn't affect decoding, i think, but it caught my attention.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking

VideoLAN code repository instance