Mailing List AE-List@media-motion.tv — Message #54220
From: Allen Ellis <AE-List@media-motion.tv>
Subject: Re: [AE] Lossless movie format
Date: Mon, 9 Jun 2014 14:13:30 -0400
To: After Effects Mail List <AE-List@media-motion.tv>
I am super excited for what you are working on! Thank you for kicking this off!

Wish list:
  • No gamma inconsistencies between platforms (I can't believe this is still unresolved!)
  • If the encoder crashes while rendering, or I begin to copy a file while it is transfering/still encoding, the rest of the file should still playable up until that point, not a completley corrupt file
  • Easily parsable information at the front of the file specifcying information like codec, bitrate, duration, etc
  • Can support bizarre frame/rates resolutions, to a great number of significant digits, allowing for future applications (DNxHD fails this terribly).

Bonus features:
  • GPU-accelerated encoding
  • Support for low enough bitrates that devices like SD cards could record in real-time if they need to
  • Resiliant to corruption. Checksums could indicate possible problems but it would be nice if it could attempt to play anyway without crashing the player or totally failing
  • The ability to define a poster frame / thumbnail, or generally support thumbnails easily. (Windows Explorer still doesn't show thumnails for .PSDs for instance)
  • I love Steve Oakley's idea of embedding the codec in the file as an option. Genius. Could eliminate the need to distribute/install codecs for certain users - just load the codec into memory from the file and discard when done, if they choose to accept that performance tradeoff.

Brainstorm/crazy ideas:
  • Meta data that could specify the file's history, or other useful information about where it came from. Obviously this needs application support, but for example: the name/path of the project file that originally rendered this file. Possible major privacy implications to address, perhaps should be off-by-default.
  • Possible "3d" support, allowing multiple, distinct images to be embedded in one file. Perhaps this is done by arranging each image side-by-side, but meta information could define distinct areas of the image with names (think concert LED mapping applications that have dozens of screens that need to play in sync)
  • Easy to add a description to the file, or preview the thumbnail/other metadata remotely. For example, if you are browsing an FTP share, it would be nice to download the first few hundred KB of a file only, so you can learn as much as possible about it, before commiting to a long file transfer.
    • Along that same line, imagine if you were able to embed proxies into a file. For some of our deliverables, I wouldn't mind spending a little extra render time and make the file a tiny bit larger if it meant easy previews from remote locations.



--Allen


On Mon, Jun 9, 2014 at 2:03 PM, Steve Oakley <AE-List@media-motion.tv> wrote:
codecs not installed is the #1 problem of QT, especially ProRes on PC, or QT in general on PC. more of a problem with non-video types.

 #2 gamma problems.

no one I work with uses OMF so I don't have those problems.

MXF Folders..."smart" producers who pull the media files out of the folders and hand those off :( but since this is going to be a single file format, not a problem.


so really the big goals should be :

no codec install problems - apps should natively support the format. however, as BACKUP having a QT/AVfoundation component might also be a good idea to get MOX files open in apps that due use QT but don't have native support. this might be really important to small developer's that don't have the resources of larger ones.

auto code updates - part of the API should be that if the codec is updated, the app can go pull it down from the web if its 1.2 and the file content is 2.0.

************ >>>>>>>

in fact here is an idea - Put the codec IN the media file as an option. this would guarantee codec install problems would never be a problem. its a minor bit of file bloat but if the actual codec code is a couple kb, even 50kb thats really nothing. this would solve all sorts of problems around users not having the latest codec, or correct one assuming down the road MOX opens up and extends to new codecs.

-----------------------

enough metadata to also have good gamma / FPS / log curve / Camera viewing LUT / TC interpretation by apps supporting the format. options like camera info would also be good.

S

On Jun 9, 2014, at 12:15 PM, Brendan Bolles <AE-List@media-motion.tv> wrote:

> On Jun 8, 2014, at 12:05 PM, Louai Abu-Osba wrote:
>
>> I hadn't realized this picked up again. I'm so beyond excited. I think MOX is a great name and I love the proposal.
>
>
> Thanks for the encouragement, Louai.
>
> I have a question for everyone: what have been your past struggles with existing file formats that you hope to solve with MOX?
>
> In other words: let's hear your rant about QuickTime/AVI/OMF/etc.
>
>
> Your responses will help me with the Kickstarter video and other messaging blah blah blah.
>
>
> Brendan
>
>
> +---End of message---+
> To unsubscribe send any message to <ae-list-off@media-motion.tv>


+---End of message---+
To unsubscribe send any message to <ae-list-off@media-motion.tv>

 
Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to ListMaster