long clips imported into media pool are partially black

[Bruce Carter]

Not sure what you’re asking David. The title they gave to the trouble ticket is: “Resolve C100 Spanned Clip Issue”.

[David Roth weiss]

It sounded as though your diagnosis changed between the post in which you first mentioned going to BM tech support and your latest post. That’s all.

David Roth Weiss
Director/Editor/Colorist & Workflow Consultant
David Weiss Productions
Los Angeles

David is a Creative COW contributing editor and a forum host of the Apple Final Cut Pro forum.

[Bruce Carter]

Well, they are actively working on it. I exchanged some email this morning. Hopefully it will be
accepted by the engineering group and a fix will be forthcoming. But in the meantime I have a
delivery to make so I’m going back to Symphony for this one.

[Bruce Carter]

While I wait for Blackmagic to respond to the bug submitted, I decided to try another approach. I tested what DaVinci calls a “Preconformed Flat Media File to EDL” workflow. With this approach I was successful. There are a couple of caveats though compared to a roundtrip workflow but in my case they aren’t a roadblock.

Here it is in outline form.

Inputs: C100 AVCHD and 2nd system sound wav files.

Outputs: ProRes 422 QT movie files

Workflow process

On Avid:

AMA-link to C100 AVCHD original camera files

Transcode to DNxHD36

Edit and achieve Locked Picture/Sound

Export DNxHD36 flattened master QT file (Same-as-Source)

Output EDL (Note: use output format CMX_3600)

On DaVinci:

Import DNxHD36 flattened master QT file

Import EDL (Note: turn off Conform Setting “Assist using reel names”)

Grade the project

Render out ProRes 422 QT master file

On Avid:

AMA-link to ProRes 422 QT master file

Edit trailer in same project as before

Export ProRes 422 QT trailer file (Same-as-Source)

Notes on the flattened master workflow

1. Tape names (Reel names in DaVinci) are not required and in fact must be ignored

2. Since this is not a roundtrip workflow it is essential to lock the picture and sound.

However, certain small changes could be made without too much effort.

3. This workflow is pretty fast to setup and accomplish compared to the many pitfalls

waiting to snag a roundtrip workflow.

4. In the “Color Correction Handbook – Second Edition” by Alexis Van Hurkman, on page 385, he

notes that HSL-Qualification corrections might shift at the baked-in dissolves.

5. In the DaVinci Resolve 12 User Manual, on page 540, mention of a Preconform button on the edit

page is made. This button does not exist.

[Bruce Carter]

Just wanted to post an update I received from Blackmagic Design Support.

“So we do support c100 but we do not support spanned clips at this time (meaning that only the first part of the spanned clip will show up.

A great workaround (very fast too) is to use application called Clip Wrap or Edit Ready from Divergent Media. This will rewrap (meaning original video is put into a new container without transcoding) and extract all of the metadata from MTS and insert it into the QT .mov wrapper. It also combines spanned clips into one.”

On my next C100 project I will buy the EditReady app ($50) and use it to prepare source files for
starting in either Avid or DaVinci.

-bruce

[Bruce Carter]

Did some workflow testing with DaVinci 12.5b1 and the C100 spanned clips bug is still there.

Got EditReady and tried it out. Found out that ER cannot create .mxf files itself. It can only
create .mov files. So to prepare C100 AVCHD files for a roundtrip workflow where you want
to edit offline in Avid and finish in DaVinci you have two options:

ER + Avid Option

1. use ER to convert the AVCHD files to mxf format wrapped in mov.
2. import the mov files into Avid using fast import

ER + DaVinci Option

1. use ER to rewrap the AVCHD files to mov.
2. import the mov files into DaVinci
3. export mxf files into a Avid MediaFiles MXF folder
4. drag the mdb file into an Avid bin or use Media Tool to populate the bin

Bottom-line is that a 32 minute spanned clip was correctly handled using either option.

However, after all the testing and figuring out that I can now setup for a roundtrip workflow, I’ve decided to
continue to use the flattened master workflow. In my case, and these workflows always
have to be tailored to the situation at hand, a project is very rarely kicked back for a revision.
And the one time that it was, I found there are a few ways to splice in changes after all.

So since the flattened master workflow is so much faster and easier to implement I going
to stay with it even if BMD fixes the bug.