Avid 5 to RCX and back to Avid roundtrip...

[James_Mills]

Hey, all. Need a little more help, thanks guys.

First off, my friend told me that it's actually better to just color correct with RedCine than DaVinci because it uses the original RED color data whereas DaVinci doesn't... is this true?

Is there a way that I could have a roundtrip system where I transcode to DNxHD, import in Avid, edit, then send the sequence to RedCine to color correct from the native Raw files there? And then back to Avid to export?

If so, can you guys list the export settings I'd want for each trip so that I got the best quality I can at 1080? So far I have this:

1. Transcode from RedCine at DNxHD 175 10 bit

2. Open MXF and AAF files in Avid.

3. Edit.

4. ???

and so on...

 

[MichaelP]

Not true. Resolve and other DI systems decode the R3D file natively and have same parameter support for the different colorspace settings and such. Depending on your definition of color correction system, Redcine X could be considered one, but pales in color correction control over image when compared to Resolve, Baselight, etc. Not having secondaries alone puts it at a disadvantage for color correction. Add to that composting, tracking, mattes, etc. the control over all the pixels is just not the same. Also, HDRx control is not just a mere belnd slider, but the ability to put that control in shapes in the image where it is most needed and track the shape the objects or camera or both are moving.

As in the other thread, knowing that you are going back to color correct the R3D files after the edit, then 175x is overkill and waste of space. DNxHD 36 as a proxy is fine. You can make an EDL of the sequence (straight cuts only for Redcine X I believe) and you will get a timeline which you can re-color correct and then export higher quality DNxHD 175x as a transcode. Or, AAF to Resolve, link to R3D, color correct, and either go back to MC for finish as 175x or export final from there.

Michael

 

[James_Mills]

Hey, Michael. I'd prefer to use Davinci, but as it is right now my computer just can't handle it so it seems; it errors up and givs the whole "GUP used up" message (I have a 10.6 macbook pro, 15"). Did you mention before that baselite has a free plugin for Avid, or is this only with the newer avids?

Well I tried creating an EDL following these steps: http://www.sparkmedia.com/sparkwizdom/How_To_Output_EDL_From_Avid.pdf but it didn't really seem to work properly. I kept getting errors that stated I should restart the system, but then the text came up and I was able to save it so maybe it did work. I'm not sure how to get it into redcine though because it isn't an importable option when I try to import it... I'm wondering what I have to do instead?

Truth be told, I've always just used Avid's native color correction for my work... would this be a sin with Red footage? Would my color corrections through Avid still use the raw Red data? And did you mention something earlier about Baselite having an easy plugin for Avid, or was this only for later avid versions (remember I have Avid version 5)?

I know you're probably sick and tired of all my confusing questions. My bad, Michael. Thanks so much for all your help on here, I'd be so lost to death right now if it wasn't for your guidance...

 

[Job ter Burg]

Would my color corrections through Avid still use the raw Red data?

No.

 

[James_Mills]

Posted this in my other Davinci thread but think it's relevant here and would love any help y'all could give me:

"The great news is I finally got Davinci to work. I'm ecstatic, as you can imagine. Here was the list of things I had to do in order for it to run smoothly:

1. Download and upgrade to CUDA 5.0.37 (I had 5.0.306 before)

2. Make sure all my energy saver guys were completely off

3. Open the "Terminal" app on my computer and copy and paste the following:

defaults write -g AppleDisplayScaleFactor 0.85

This shrinks your Davinci app when you open it now (make sure it's closed when you do this) to 85% making it use less GUP. It works even better at .75 but that's a little too small imo.

Once you're done editing and using Davinci, just copy and paste the following in terminal to return back to normal:

defaults write -g AppleDisplayScaleFactor 1

Just some final worries of mine. I figured out how to get my Avid sequence in and out of DaVinci flawlessly, but there's two questions I still have:

1. What is the best transcoding resolutions in general for each shipment between RedCine then to Avid and then to Davinci and back to Avid? I don't want to waste harddrive space obviously... what I just did was transcode to DNxHD 115 8 bit from RedCine into Avid, edit, send to Davinci, grade, and then send back to Avid at 115 8bit again and then export from Avid as same as source (gave me 1.77 gb file for 2 minute mostly 3kres video). Would I be better off just exporting from Davinci to save space if I can (though I know it doesn't read my ime ramps when I use speed bursts effect)? Is there a section where I could save space to make the file smaller?

and lastly... 2. How can I change the timeline resolution on Davinci when working off an AAF project? I notice when I grade on Davinci regularly I can control the output resolution under the "Camera Raw" tab, but when cutting a linked AAF file during my roundtrip process it only has the one option "Camera Metadata" or something and won't let me change it. If I was able to downsize the playback just a tad I think I could sue Davinci on my MBP at 100percent size rather than having to shrink it to 85...

Thanks so much for all your help guys, I'm super super stoked that I can start using Davinci finally..."