[Aaron Leichter]

a year and a half later, and the problem persists. i’m having the exact same issue right now.

[Aaron Leichter]

I guess I just want to know why?

My issue is that I feel as though I’ve been led to believe that the DVCPROHD codec is native to the DVCPROHD tape, and that theoretically anything captured with this codec should contain the same amount of information as what exists on tape. I know the image on tape is compressed, but does the codec add additional compression in this case, or is it equal to what exists on the tape? Does capturing uncompressed 10-bit from a DVCPROHD tape actually provide more information than a DVCPROHD Quicktime captured from the same tape? If not, I would be inclined to simply export our sequences as is (also DVCPROHD codec, wouldn’t recompress) and import in to Smoke.

Any additional thoughts?

[Aaron Leichter]

A trick I’ve tried when posting for clients and dealing with washed out H.264 exports:

After you’ve exported the Quicktime, open in Quicktime player. Go to Window>Show Movie Properties (command J). In the properties window that opens, click on “Video Track” in the properties list, and then below that, click the “Visual Settings” tab. At the very bottom you’ll see a “Transparency” setting. Change that setting to “Composition”. Save the Quicktime. Note: This seems to disable the internet streaming Fast Start, so encourage clients to download instead of stream. Also note: I’ve noticed strange pixelation and jagged egdes that appear if I’ve downressed using any of Quicktimes preset dimensions options when exporting, so I always set the dimensions to “Custom” and manually type in what I want.

This method doesn’t necessarily solve the ever-mysterious gamma issue, but it seems to satisfy clients.

Best of luck.