On Mon, Jun 18, 2012 at 4:44 PM, David Gerard
<dgerard(a)gmail.com> wrote:
On 19 June 2012 00:30, Brion Vibber
<brion(a)pobox.com> wrote:
<warning: patent politics question may lead to
offtopic bikeshedding>
Additionally there's the question of adding H.264 transcode *output*,
which
would let us serve video to mobile devices and to
Safari and IE 9 without
any custom codec or Java installations. As far as I know that's not a
huge
technical difficulty but still needs to be
decided politically, either
before or after an initial rollout of TMH.
</warning>
It's entirely unclear to me that this is intrinsically related.
They're intrinsically related because one depends on the other to be
possible. This is a one-way dependency: H.264 output depends on
TimedMediaHandler support. TimedMediaHandler in general doesn't depend on
H.264 output, and should not be confused with it.
-- brion
I think what we should do here is go ahead and add support for ingestion
and output and then we can just adjust the settings file based on what
we /decide politically/ do going forward.
Since both the deployment review pipeline as well as the political
decision pipeline can be ~quite long~ probably best to have it all
supported so we can just adjust a configuration file once we decide one
way or another.
--michael