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=W
	chnHGEMXPn9EXI4YBDtdIP99ABWWvD2bmlKc+F9KbvUl4awLrmj7A9ad6fGhhIJ4
	x0wJgExwM9bUPTJAhxm5S+AVLC2VwiAdDQA9B7zLvAQxGz8oh1NhxyoL7Kg5Gnqy
	Lh12dqa2jtAuhMHjMxAWVdj5hLR+RwTUTj4yJE69Rs=
MIME-Version: 1.0
In-Reply-To: <list-5149382@media-motion.tv>
References: <list-5149382@media-motion.tv>
From: Louai Abu-Osba <me@louai.org>
Date: Mon, 22 Jul 2013 15:30:34 -0400
Message-ID: <CABan1zO_+uF0G-R+pCVZXU1kMkmKewvVA8MZ5qa0q8YpNg6Sjw@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

It's certainly very practical in the short term to stick with a well
known container like Quicktime. But Quicktime sucks more every year. I
was a former QT fanatic and now I just hate the idea of a single,
highly secretive company controlling the container my work is poured
into. A container that at times just seems insane (e.g. the gamma
shift). Standards changes are always painful, but it would just delay
adoption to do things the "sorta right way" instead of the "the right
way". EXR skipped the former option and we're all better off.

On Sun, Jul 21, 2013 at 3:42 PM, Steve Oakley <steveo@practicali.com> wrote=
:
> so can I ask -
>
> what would it take to write Dirac into single file MXF or QT as container=
s ? seems to me that using established well known containers would mean onl=
y needing to add the codec into the right place in your system and then you=
 could easily r/w the files and exchange them. no doubt if Ogg container on=
ly had to live on my machine it would be fine, but exchange becomes more of=
 an issue.  I'd rather see a standard documented container with a common co=
dec than yet another new container format.  FWIW, before the win users say =
they don't want QT as a container, please know that you don't have to have =
QT installed on your machine for apps to be able to r/w it. Adobe wrote med=
iacore as an underlying lib that does direct I/O on several flavors of QT s=
o that you can access QT files w/o having QT the app & libs installed on yo=
ur machine. It also means a fast / mean / lean way to do QT file I/O withou=
t the limitations of PC QT32.
>
> S
>
> On Jul 20, 2013, at 4:00 PM, Brendan Bolles <brendan@fnordware.com> wrote=
:
>
>> BTW, I've posted a Theora plug-in for Windows and put download links in =
the README documents for my two repos.  See them here:
>>
>> https://github.com/fnordware/AdobeOgg
>> https://github.com/fnordware/AdobeWebM
>>
>>
>> There are 4 plug-ins total, all in beta.
>>
>> AdobeOgg has Ogg Vorbis and Ogg Theora plug-ins.  Vorbis is audio-only w=
hile Theora adds VP3 video.  The Ogg Vorbis plug-in on Mac also supports FL=
AC, a lossless audio codec/format.  Since Vorbis and Theora both use the Og=
g container, the goal is to merge these two plug-ins and then add other cod=
ecs so that Theora is one of many to choose from.  I'm currently planning t=
o add Dirac, VP8, VP9, PNG, and OpenEXR on the video side.  Audio formats w=
ill be Vorbis, PCM, and hopefully FLAC, plus maybe Opus and Speex.
>>
>> AdobeWebM has a WebM movie plug-in plus a WebP still-image plug-in for P=
hotoshop.  I plan to further refine these as well.
>>
>> Here's an HD WebM movie if you want to see what WebM can do:
>>
>> http://media.xiph.org/tearsofsteel/tears_of_steel_1080p.webm
>>
>>
>> Please try them and let me know how it goes!
>>
>
>
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>