That was on a circled take, though. But still :)
Andrew I'm talking about your misinformation on ALE creation. All you have to do in Red Rushes is go to the tab "create ALE" and an ALE will be created before you can blink. How this process of milliseconds can hold you back from shooting Red in general is beyond me. At that point I was baffled at your ignorance and felt the obligation to point out the obvious.
What is on an ALE that I need anyway, that couldn't be covered by metadata coming from a file out of REDCine without an ALE? And how would those specific things benefit me moving from Media Composer to an Online (most likely in DVS Clipster)?
The QuickTime exported out of any of these applications only contain a single timecode and the name of the file is your only source reference. Very limited compared to the ALE file which tracks both timecodes, automatically tracks full and short file names, providing you flexibility and accuracy in the conform downstream. By tracking filenames as source in alternate columns, it also allows you to change the clip name to something more useful like 32A/3.
Again, worth the 10 seconds it adds to the process.
Now I guess the question is, would it ever be possible to produce an ALE straight from REDCine, without having to do all the steps inbetween (exporting as XML, and converting to ALE). AND somehow tie an ALE to the quicktime file, so it's a one step import (instead of ALE, then batch import).
And actually this was my primary problem from the beginning, not really the ALE itself, but the production of the ALE... a 2 step process, instead of 1.
(Preferably a "Import RED Footage" option in the menu, which opens up a find file window, you find the ALE, and then that Imports, dragging all the material with it, at the same time.)
If you use REDrushes you can do it all in one application as well as render directly to the DNxHD data rate of your choice. I cannot answer whether REDCINE will create ALE directly since Avid is not in control of that product development. We work with whatever REDCINE can export, and it is XML - Avid imports ALE, thus the extra step of converting XML to ALE.
i suggest you step back, take a breath and really think about everything you are getting into and plan and create a proper workflow whatever that is so you don't want to kill yourself later in the conform, especially since you wont have anyone else to blame because you did it all yourself.
|« Previous Thread | Next Thread »|