Workaround for Redcine 108 DNxHD problem

[Seth Larney]

For those of you having the same problem as me with Redcine 108 not being able to export DNxHD quicktimes, this workaround seems to be getting me through temporarily until the issue gets resolved.

I have been exporting as MJPEG A QT's instead (you should be able to do this with any codec) and using MichaelP's ALE transform plus the Redcine XML to get the metadata into the ALE as per usual. When you batch import in Media Composer, just use the non-DNxHD QT that you have created, it will take longer to transcode and you will lose some quality etc, but it should import and link to the metadata fine none-the-less.

I have been using MJpegA for now which seems to import *fairly* quickly. I'm sure there's a better codec (different codec's transcode at different speeds).

Unless I've missed something obvious, this should work ok for now.

Oh, also, you can edit the transform that MichaelP generously supplied to change the ALE to 720p from 1080 if you are offlining at that res..

Cheers,
S.

 

[Seth Larney]

Btw, if someone finds through testing which is the best codec to do this with that would be great .. as I mentioned I am using MJpegA for now but I don't really have much time to go through them and test.

Cheers,
S.

 

[Jason Diamond]

if thats the workaround cant you use the proxies to generate an ALE with metacheater and batch import anyway? you can always make new proxies with new "looks" quickly and move from there?
im assuming that since you are going into the AVID you aren't necessarily "finishing" with these files directly so you can make your selects later.

just a thought unless im misreading your overall workflow/end result

 

[Seth Larney]

Hey Jason,

Sorry, I forgot to mention my workflow is for PC Media Composer. Proxies work well for OSX..

 

[Jason Diamond]

you are correct and thats a big bummer :'(
wow maybe a tiff seq or some other better quality workaround til build 16 gets that codec out there for PC

 

[MichaelP]

We have found the issue on the PC and will be updating the QT installer on avid.com as soon as we can. I will post a message here when available.

Michael

 

[Jason Diamond]

hot damn you guys are trying to keep up with RED! haha.

good work, thanks.

btw have you checked out REDRushes in the new beta build? we need some avid codec sweetness there stat!

 

[MichaelP]

REDrushes is very cool - if used on the same system as your Mac based Media Composer it is faster to just directly import the QT references.

Michael

 

[David_D]

But if we process using a full res debayering, isn't it better then importing using the reference movies into Avid? Of course, at the moment, you'd have to process as uncompressed to really get no loss, but nevertheless. Also, I'm having a bug importing QT reference movies directly into Avid since v. 3.0 and up of the QT component. I get a weird white 'negative' effect on all my imports, whatever the import res. I have confirmed this on both v. 3.0 of MC and v2.8.3, both on OS Tiger and Leopard. Downgrading to version 1.5 of the QT component seems to solve the problem, but no support for 4k 16:9 and some other stuff with 1.5, if I understand correctly. They read fine in Quicktime Player with the component, but they screw up on import. Any word from Avid on that?

 

[MichaelP]

There are a couple of issues at hand here. The export from RedCine has been fixed in the Avid DNxHD component of the Avid QT codec library. That will be an update to the QT installer on avid.com. When that does get posted I will post an email here to let everyone know.

Using QT reference on a Mac to import directly into Avid gets the weird 8 but luma/chroma inverse looking image. That is something that RED is looking into as it was introduced with their latest QT component when build 16 came out.

Michael