Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1085)
Subject: Re: [AE] lossless codec in a container roundup
From: Brendan Bolles <brendan@fnordware.com>
In-Reply-To: <list-5152920@media-motion.tv>
Date: Tue, 23 Jul 2013 09:36:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C018A18-0E69-41EA-9270-AE226BD5B88F@fnordware.com>
References: <list-5152920@media-motion.tv>
To: "After Effects Mail List" <AE-List@media-motion.tv>

On Jul 23, 2013, at 6:20 AM, Byron Nash wrote:

> Great line of thought Brendan and Stephen. Open, Professional, and =
extensible should be the aims. I'll certainly do everything in my power =
to help push it into adoption. Will you have to work with the major =
vendors to get compatibility out of the gate or is what you are =
proposing already compatible?


These files will be totally legit MXF files, but not compatible with =
probably any existing MXF reader because they will use different codecs. =
 Since MXF itself doesn't set any codec standards, many programs that =
use MXF are already not compatible with each other even though they're =
using the same file format.  This new file format aims to not have that =
problem.

But as an MXF, any other thing that someone wants to do with it, like =
parse out metadata, should work just like with a regular MXF.  We will =
have an easy-to-use library available for people to add support for this =
format in their programs, but someone already reading MXF could probably =
just add the open codecs to their reader and it would work.

My first priority will be to make a Premiere/Media Encoder plug-in, then =
probably an After Effects plug-in.  That will let people who don't need =
to go outside those programs to start testing it in production.  These =
plug-ins will be open source, so they will serve as examples to other =
vendors for how to add support to their programs.  Hopefully they will =
do it themselves with your encouragement.  Or if there is demand and =
resources available, more open source plug-ins could be made.

Since Apple will no doubt drag their feet, we'll probably have to make a =
QuickTime component at some point (different from a QuickTime codec).


Brendan