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 :)

RED RAW from Komodo Not Interpreting Kelvin as shot in Premiere.

Ryan Hills

New member
Joined
May 2, 2013
Messages
1
Reaction score
0
Points
0
Hey everyone. I am having a RED RAW issue in Premiere. I am editing an interview shot on two different REDs. A Cam was a RED Gemini shot at the native 5k. B Cam was a Komodo shot at its native 6k. I am editing in Premiere on a new M1-Max Macbook using Monterey.

All clips were imported via Premiere. I've created proxies. When creating the proxies, Premiere/Media Encoder was able to interpret both cam's clips at the native 3200K that the cameras were set to. When looking at the master source clip effects/RED source settings, I see that the Gemini clips are able to read and adjust the native kelvin settings (3200k) and I am able to adjust the slider.
When I look at the Komodo clips' RED Source Settings, the Kelvin slider is set to 0 and is nonadjustable.

It seems that Premiere is interpreting these clips at 1800K and I am not able to change it. (I was able to recreate the look of these clips in REDCINE-X and adjusting the Kelvin to 1800 gives me the exact look that Premiere has).

I knew there would be issues like this with the new M1, but just wondering if anyone else is having this issue since I havent been able to find any documentation about it online. Am I missing a plugin/firmware? I have a potential work around by sending everything to Resolve, but this project is absolutely massive (20ish hrs of interviews) and I'd like to send my rough cuts out with just a basic REC709 to client.

  • System specs: CPU (model), GPU + RAM: Macbook Pro, M1 Max, 64GB RAM
  • Software specs: Premiere 22.1.2
  • Footage specs: R3D
 
Back
Top