Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • MKVToolNix MKVToolNix
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 17
    • Issues 17
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Moritz Bunkus
  • MKVToolNixMKVToolNix
  • Issues
  • #3466
Closed
Open
Issue created Jan 01, 2023 by Dian Li@xslidianContributor

Non-standard usage of HEVC in FLV as input files

I'm seeing ByteDance (Tiktok etc) rolling out HEVC-in-FLV for domestic low-latency live streams in the past month.

Their implementation followed Kingsoft's style (2017), using codecID = 12 (0x000C).

hevc.flv

I see no downside allowing mkvmerge reading the video stream. You may want to warn the user about this unofficial codec ID.

  • MediaInfo identifies the video stream with no problem.
  • FFmpeg refused as it's not standard-compliant.
  • VLC (stable) doesn't support it (yet).

Note: I made a casual binary cut. The last packets in the file may be corrupted.

Assignee
Assign to
Time tracking