DomainKey-Signature: a=rsa-sha1; c=nofws; d=louai.org; h=mime-version
	:in-reply-to:references:from:date:message-id:subject:to
	:content-type:content-transfer-encoding; q=dns; s=louai.org; b=a
	4lHngCIefwUcGJoU+OLy1na8L3l+Fqno+lZL0O02ogi27Ar0sHmOU3lsOdWleu+D
	qxVc0xKAnrylDmekjiwTj4l/qA7zFedIWt1GMPiRgirR7HRnNf0HPPULl7mSnSrx
	+ejRKQLStHNVVey0cd7vm78hk6jozx+6Znw4TcF78w=
MIME-Version: 1.0
In-Reply-To: <list-5153178@media-motion.tv>
References: <list-5153178@media-motion.tv>
From: Louai Abu-Osba <me@louai.org>
Date: Tue, 23 Jul 2013 12:44:20 -0400
Message-ID: <CABan1zPN4HMDxr3Jk6DhhFHxJEXQ3Hpt5eedkpYHUTOYQo-UaA@mail.gmail.com>
Subject: Re: [AE] lossless codec in a container roundup
To: After Effects Mail List <AE-List@media-motion.tv>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I can see why you'd want to rebrand MXF into a different
extension/name. That makes a lot of sense if you're including codecs
in the source and want to prevent codecs from being added via plugins,
but you still get the benefits of a standards association like SMPTE
furthering the container. I think adoption could happen pretty fast if
you start with a large niche like AE/Premeire users. Projects that
seed like this have a tendency to grow into an alliance of sorts when
they're successful.

On Tue, Jul 23, 2013 at 12:36 PM, Brendan Bolles <brendan@fnordware.com> wr=
ote:
> On Jul 23, 2013, at 6:20 AM, Byron Nash wrote:
>
>> Great line of thought Brendan and Stephen. Open, Professional, and exten=
sible 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 compatib=
le?
>
>
> These files will be totally legit MXF files, but not compatible with prob=
ably 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 par=
se 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 th=
e 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-in=
s 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, m=
ore 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
>
>
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>