Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Avid/Premiere not cooperating with RMD made by RCX

Sean_A

Member
Joined
Jul 14, 2017
Messages
13
Reaction score
0
Points
0
Greetings,

First and foremost, I'm a RED newcomer, which means that there is likely an obvious answer to my issue. But, I can't seem to put my finger on it.

In an attempt to follow the workflow presented in this guide: (http://www.red.com/learn/workflow/adobe-cc-premiere-pro-red-overview), I have been attempting to do a basic color grade in RCX, then import to Avid MC First/ Premiere CS6 (both on Windows) and edit from there.

Things get sticky when I try to load the grade from the RMD file that RCX created (Avid does this automatically, Premiere requires "Reload from RMD"). The colors are completely blown out. (see photo, far left is the problem child)

I've tried finding a solution online, but the best guess anyone has is that the color spaces are off. I'm aware that RCX shows the color space as REDWideGamutRGB and curve as Log3G10, with the new IPP2 pipeline. But these aren't options available in my versions of Avid Media Composer First and Premiere Pro CS6.

Someone suggested trying Rec709. This changes the color slightly, but it's still a nuclear wasteland.

I'm also well aware that the general consensus is to just edit raw, then grade in Resolve. I'm sure I'll try that eventually, but I'd really like to know why these programs aren't talking to each other the way they're supposed to.

TL;DR: What...the...hell...

I appreciate any input,

Sean.
 
Sean,

Check these settings in Redcine-X.


37445722150_f6b6af4fe1.jpg
[/url]Screenshot (12) by rand thompson, on Flickr[/IMG]


37942690906_923e7df9fb_b.jpg
[/url]Screenshot (3) by rand thompson, on Flickr[/IMG]



and not these settings. the settings in the "IPP2 Monitoring" section


38034645034_2a53cffdae_b.jpg
[/url]Screenshot (55) by rand thompson, on Flickr[/IMG]



If you have the settings in the first graphics. Make sure at export you have in the "Export Pipeline" dropdown menu , you have "Full graded IPP2 Mode" selected and not "Primary Raw Development" which exports your footage back into the log look of IPP2.


38079002564_39ae8006f7_b.jpg
[/url]Screenshot (68) by rand thompson, on Flickr[/IMG]
 
Last edited:
Also,

what are you importing? the raw .r3d file or a transcoded clip like for example prores. If raw.r3d the grade automatically wrote back to the .r3d file within redcine-x, so the grade is already there ,and importing the .rmd file again might double the effect of the grade. If prores .rmd files don't work with those.


Plus from looking at your screen grabs, It looks like you are importing your clips back into the "legacy" "color space" of "Redcolor" and "Legacy" "gamma curve" of "Redgamma" and not into the new "IPP2" workflow which you graded in inside of redcine-x.


38079263214_fe46bb731f_z.jpg
[/url]Screenshot (70) by rand thompson, on Flickr[/IMG]

could you do a screen grab of the pull down menus of "color version", "color space" and "gamma curve". these settings are your problem.
 
Last edited:
I have been attempting to do a basic color grade in RCX, then import to Avid MC First/ Premiere CS6 (both on Windows) and edit from there...
My opinion: both MC First and Premiere CS6 are kind of light duty or old systems, and I don't think you're going to gain anything by trying to edit Raw there.

I would just export DNxHD transcodes from Redcine-X Pro, use those for making all your edit decisions, and then when you're locked, export an XML or AAF into Resolve and relink back to the original R3D files. You'll have the choice of using the RMDs or not during color correction, assuning you use Resolve 14.1 which does have IPP2. You may find for certain purposes, RedLogFilm will give you more range in Resolve.
 

Thanks for going through all that. The settings match in Redcine-x.

I'm editing 4.5K .r3d files from a One-MX. Like I said in the OP, the IPP2 settings don't seem to exist in my Premiere CS6. Also, version 1 color is greyed out. Only version 2 is available.

Here are the screen grabs:
ERd8HB7.png
zKhkglK.png


My opinion: both MC First and Premiere CS6 are kind of light duty or old systems, and I don't think you're going to gain anything by trying to edit Raw there.

I would just export DNxHD transcodes from Redcine-X Pro, use those for making all your edit decisions, and then when you're locked, export an XML or AAF into Resolve and relink back to the original R3D files. You'll have the choice of using the RMDs or not during color correction, assuning you use Resolve 14.1 which does have IPP2. You may find for certain purposes, RedLogFilm will give you more range in Resolve.

I appreciate the workflow tip. But, correct me if I'm wrong, if I'm editing 4.5K raw with minimal performance issues, is there any benefit to transcoding to DNxHD first?
 
Sean,

you might just have to use the "legacy" controls instead of the IPP2(rwg/log3g10) workflow so that both your settings for color space and gamma match in both premiere and redcine-x. I don't know if you have the latest version of Premiere or not, I'm not currently using it, but maybe that would help. According to your screen grabs of redcine-x you graded in the ipp2 workflow and in the legacy workflow in premiere.


27042131289_ea6c21732d_z.jpg
[/url]MU3yYbh 2 by rand thompson, on Flickr[/IMG]



38079263214_fe46bb731f_z.jpg
[/url]Screenshot (70) by rand thompson, on Flickr[/IMG]


1) open up an empty Redcine-x pro 50 project, but don't import any footage in yet.


37445722800_643bccfaff_o.png
[/url]Screenshot (9) by rand thompson, on Flickr[/IMG]


2) Go to "Edit" then "Preferences"


37445722150_e3bbddf037_o.png
[/url]Screenshot (12) by rand thompson, on Flickr[/IMG]

3) Go to "image pipeline" and change the settings to these.


37445722870_07aebbf1f6_o.png
[/url]Screenshot (13 by rand thompson, on Flickr[/IMG]


4) and you should see these legacy controls come back after you import your footage.


37445722740_cfa4cff30b_o.png
[/url]Screenshot (9 by rand thompson, on Flickr[/IMG][/QUOTE]
 
Last edited:
Thank you, Rand. That appears to be the solution. Hopefully the issue doesn't reoccur.
 
You're welcome Sean. Hopefully no more issues.
 
Back
Top