Just a quick note -- there's been some ongoing work in preparation for
supporting WebM with the newer VP9 codec:
* fixing up our server configuration with updated ffmpeg & ffmpeg2theora
* fixing up the player to support VP9 as well as VP8
* adding support for producing WebM transcodes in VP9 in addition to VP8
Big thanks to a bunch of folks over on the ops side who have been helping
with the packaging! We had to backport some packages to get VP9 working,
and ffmpeg2theora needed some patches to work correctly in newer versions.
At some point in the coming weeks, the video transcoding servers will
with an updated operating system <https://phabricator.wikimedia.org/T104747>
(Ubuntu Trusty plus our custom packages). Once this is complete, uploaded
WebM VP9 files should start producing Ogg Theora and WebM VP8 transcodes
(currently you can upload them but they fail to work).
With TMH updates going out some time next week, playback of VP9 originals
<https://phabricator.wikimedia.org/T62272> should also start working in
Chrome and Firefox.
These updates also improve support of Opus audio files
<https://phabricator.wikimedia.org/T42193>, both standalone in Ogg audio
and in WebM videos.
Once we're satisfied everything works, we'll consider enabling production
of VP9 transcodes <https://phabricator.wikimedia.org/T63805>. These will be
about the same quality as VP8, but use only half the bandwidth. Later when
we figure out how to rig up adaptive streaming, this'll mean
bandwidth-constrained clients can bump up one resolution step in VP9 versus
One big warning -- VP9 encoding is 2-4x slower than VP8 encoding at the
same resolution... so we'll have to investigate comparative CPU load and
whether 1080p transcodes actually complete reliably before timeouts etc
hit. This may be something we have to roll out later after more testing.
But even if it takes us time to get VP9 output working, having VP9 input
functional will fix some existing files, make it easier to import from
YouTube and other sources that are more aggressively using VP9, and
generally makes us more future-proof.
This should be interesting to folks -- Popcorn.js, the highest profile open
source video editing/assembly project that is web browser-based, was Mike
Nolan's summer internship project at Mozilla. His video presentation is
Some of you may know he was at Wikimania in Mexico City and talked with a
number of us on the status of video in Wikimedia. He gives a shout out to
our efforts and the potential for Popcorn being part of the solution at the
end of this talk.
Mike and I also recently met with the Internet Archive folks in SF and
they're keen to keep working with us, and to look into funding for the
three entities -- the Wikimedia movement, Mozilla and Internet Archive.
Mike Nolan: "Going the Extra 10%: The Next Generation Video Editor on the
Since the dawn of YouTube and smart phones, video content on the web has
grown an immense amount. Once, where web pages were simple collections of
long form text markup are now rich multi-media applications. The user's
ability to store video content on the web has evolved along with many of
the web standards today but even now in 2015, users are required to often
times purchase expensive and bulky video editing applications with steep
learning curves to edit existing content.
This talk goes over Mike Nolan's intern project to modify the Popcorn Maker
library for transcoding the Popcorn Maker editor json into a flat ".webm"
I made Japanese subtitle for the movie on commons.
But I encountered 2 problems.
* This namespace ignores templates. So I can't put the license template to
it. This template is not appeared on the movie.
* It ignores also line breaks of subtitle. Especially, Japanese phrases
don't have spaces for reading, so it's hard for audience to understand
Anyone has a solution to this?