DaVinci 10 Lite + Edius

neben CineForm bleiben noch ProRES und DNxHD...
Edius kann ja beide lesen, wenn die Codecs installiert sind.

Für DNxHD gibt es zumindest freeware Konverter wie 5DtoRGB. Dies hat ein CMD-Modus, was möglicherweise "Batch"-fähig ist.

Mein 6.5 kann es zumindest.

AAF Export, XML Import (Medienverlinkung) sollte m. E. auch damit gehen.
Die 8bit VfW Einschränkung spielt bei denen wohl keine Rolle.

Hilfe für Batch Konvertierung:
(nicht getestet)

http://www.slashcam.de/info/Wi…DNxHD-wandeln-458760.html
http://www.squared5.com/svideo/mpeg-streamclip-win.html

Dieser Converter scheint zumindest in der MAC-Version auch mit professionelleren Formaten umgehen können.
Es lohnt sich einen Blick darauf werfen zu können:

http://www.wondershare.com/pro/video-converter-ultimate.html

Im Grunde gibt es drei Alternativen:

1. man arbeiten vom Anfang an in einem Codec was sowohl für Edius als auch für dV --> Medienverlinkung mit EDL / AFF ist möglich
-->hier können die verlinkten Tools / Converters eine Hilfe sein je nach dem welchen Intermediate-Codec man verwenden möchte.
2. man exportiert das Edius-TL entweder als AAF / EDL und benutzt die damit zur Verfügung gestellten Möglichkeiten ("nur benutzes Clips")
3. man exportiert in einem dV-fähigen Codec und zerschneidet in dV entweder mit der Szenenerkennung oder manuell.

Hier sind einige Workflow-relevante Zitate aus dem US-Thread.
------------------------------
------------------------------

"Try converting your footage to Cine Form, this will act like an intermediate that both Edius and Resolve will see. Then go to Resolve from Edius using AAF that's linked to the CF media."

"Put it another way, that is a real world pain. You have either a complex composite edit or a simple frame resize in Edius, or anything else in the Edius timeline that has changed the framing of the source clip. If you then want to grade these parts, there is really no way other than to group the composites in to a single render, or render any other frame altered source clip. You then import and colour these clips in something else and reimport them back. Then say you change your edit by a couple of frames, or do any resizing, or their is a last minute creative change. You will have to repeat this process all over again.

Now if the above scenario is carried out with CF clips in Edius. It is a simple matter of opening the source clips in FL, running parallel with Edius being open. Make your look/colour changes in FL, then switch back to Edius, and your new changes are all there to your clips in place within complex composites or any other frame size changes edits."

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

"Fwiw, I use Avid's DNxHD for an intermediate where necessary. You can download the Quicktime codec from Avid and it works just fine in both Edius and Resolve.
And don't forget that you don't necessarily have to use the AAF workflow prescribed in the Grass Valley doc you linked to.

You could simply export a flat file of your finished edit, targeting a Resolve compatible intermediate codec, and then cut that up in Resolve using it's Scene Detect function (or by using the "Pre-Conformed EDL" option together with a simple EDL of your timeline exported from Edius)

Or you could choose to use AAF but have the AAF exporter compress your used footage to a Resolve compatible intermediate codec as part of the export,rather than pointing at your original (but incompatible) media."

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

"You would be surprised at how often Andy's suggestion of scene detection actually happens. It works really well for hard cut drama type edits. It also works well to apply dynamic changes across things like dissolves or key framed FX clips. You may find that this option gets you out of other messes and not just with Resolve or colour grading.

For the purpose of grading or for doing FX work, I would strongly suggest that you are careful in using embedded transcoded footage to get from one place to another. Doing this will only add another step of degradation to your footage, unless you use uncompressed. Some codecs like HQ are brilliant and very similar visually to uncompressed, and lend themselves to being thrown about quite heavily in post, as long as the other post apps can read it. Other NLE specific codecs are not quite as robust as HQ when being pushed about.

It may well be worth your while in looking into an intermediate codec, that can be transported between all the post applications that you are likely to use, without the need for unnecessary re-encoding. This way you will hold the quality of your initial encode all the way through post, until you have to make destructive changes such as colour and FX.

If you are going to be dealing with raw or log type files, you will have to be careful to not destroy their attributes by transcoding to an intermediate that losses the ability to read the attributes. While using such intermediates is fine if you plan on only using them as proxies for speed, and then re-conform for the master. It is quite usual to want to stay online for the whole post process, this is were you have to be careful over using an intermediate to encapsulate raw and special log type source information.

BTW. If using any codecs that require QT to resolve them, maybe the Avid ones. You may want to run some test on gamma, to make sure it is the same when moving the files between apps and platforms. Maybe things have changed but I could never use Avid codecs properly when moving in and out of Edius, due to the gamma shifting. "

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