Opened 7 years ago

Closed 7 years ago

#6176 closed defect (fixed)

Use of non-standard value (4) for displayUnit in webm containers

Reported by: Théo Owned by:
Priority: normal Component: avformat
Version: git-master Keywords: mkv
Cc: Blocked By:
Blocking: Reproduced by developer: yes
Analyzed by developer: yes



Starting ffmpeg 3.2.x we have noticed that for Webm containers, ffmpeg sometimes (quite often for us actually) sets the displayUnit field to a value of '4' (likely from here: ). I believe that according to the Webm documentation '4' is not a valid value for Webm containers.

You can find link to a file to repro on this Shaka-packager thread: as well as previous discussion related to this.

How to reproduce:
ffmpeg version 3.2+

ffmpeg -i original.mp4 -c:v libvpx-vp9 -pass 1 -b:v 0 -crf 33 -r 30 -threads 8 -speed 4 -tile-columns 6 -frame-parallel 1 -g 60 -an -f webm -y /dev/null
ffmpeg -i original.mp4 -c:v libvpx-vp9 -pass 2 -b:v 0 -crf 33 -r 30 -threads 8 -speed 4 -tile-columns 6 -frame-parallel 1 -g 60 -auto-alt-ref 1 -lag-in-frames 25 -c:a libvorbis -b:a 64k -f webm -y input.webm

Original file


Change History (1)

comment:1 by James, 7 years ago

Analyzed by developer: set
Component: undeterminedavformat
Keywords: mkv added; webm matroska aspect ratio removed
Reproduced by developer: set
Resolution: fixed
Status: newclosed
Version: 3.2.1git-master

Displayunit with value 4 is valid for Matroska, but you're right that it's not for WebM.

Fixed in 1ad60e4e70ecc71b1301bdc041fa133129338393 (git master) and 36fff6c75459a7e23ad04be60264643e9c3d2ce8 (release/3.2)

Note: See TracTickets for help on using tickets.