Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

In need of an Expert!

Scott Crawley said:
Ah, so there was an IT professional lurking in here. ;-)
Click to expand...

Nah, just had one of those weeks where a job I lost out on because the other shooter dropped his price so far that he essentially paid the client so he could do it - turned into such a shitshow of incompetence that the sound guy, and eventually client called me; to help walk the 'Cinematographer' through camera setup. The guy ended up formatting the card instead of ejecting... I know, there are several safeguards against that; but still he managed.

So PEBKAC is top-o-mind here this week.
 
Scott Crawley said:
There is a special name for that kind of bug. They call it a Pebkac error. :-)
Click to expand...

No Pebkac here Scott.

I tried the newest Cine-X on a completely separate Mac and had the same problem.

Strange though - I'm sure everyone else here is using the newest version without any problems...

For reference it was reading 5600 as well.
 
I have reproduced your problem on my machine using 22.3.31869. Scopes are well-balanced, image is blue. Looks correct in CC. Metadata is all normal, no RMD exists. Please report this at https://support.red.com.
Did this happen to all of your clips, or was there anything unique about this one? By the way, this clip is REDcode 3:1, not 8:1 as you wrote.
 
Alexander,

Were you shooting the Motion Mount?

See this:

Casey Green said:
A client of ours recently returned from a shoot with our PL Motion Mount. * Note: Job went fine and all footage is intact and beautiful, however...

According to him, clips shot on the Motion Mount appeared to have a white balance that was way off. He discovered that it looked like it was only a REDCINE-X problem - not a footage problem at all. He told us that when he opened up one of the clips with only in camera settings applied in Adobe Media Encoder, it looked perfect, even though the version in RCX looked insanely blue. (Color Temp and Tint settings in RC-X showed they were in normal range)

It seems the Motion Mount actually was working properly and rendering colors beautifully, but that it was just RC-X that was reading the clips incorrectly. He went on to say that if he opened the clips in Adobe software (and probably other software like Resolve) they'd appear just as they did in camera. He also mentioned that he found he was able to adjust any other settings (like shadow, ISO, WB, etc) in RC-X and other programs would read those values normally.

RED has been notified of our experience so I imagine this will be resolved shortly.
Click to expand...
 
I guess I owe you an apology then. No thanks necessary. I'm curious as well.

It does appear to be an RCX error related to the motion mount. For the record, what graphics processing do you have installed?

Alexander Manning said:
Yes sir! I was...

Super curious as to what exactly is causing this! Thanks for the update.
Click to expand...
 
You're fine - apology accepted! Both Macs I tried it on had ATI Raedon HD 5770's.
 
Hello all,

By the looks of it this problem was fixed in RCX in the last couple of updates!

However, the problem still exists inside Premiere Pro CC when viewing the .R3D's natively (as I often edit Natively from them).

Any chance this is or can be fixed?

Best,
Alex
 
There is a big update to Premiere CC due soon, could be any day now, that should address a lot of these little fixes/ changes in in R3D support. R3D support in Premiere hasn't been updated for 6 months or so, AFAIK...
 
Anyone have a definitive answer on this? Has there been an update for this yet?

I'm sure someone here uses the Motion Mount and edits in natively in Premiere! Haha!

Is this something to send to RED or Adobe...?
 
I ran into this on a shoot in March using the PL Motion Mount, and an older version of RCX-PRO. Update to the newest version of RCX and you should see colors rendered correctly.

It's some bug in the interaction between the motion mount metadata and the older versions of RCX. Premiere is rendering your colors properly though, so no worries there.

EDIT: Alexander, I just saw your post on the previous page. It's odd that you're not seeing proper color in Premiere CC when you view the raw source. When I encountered this error, it did show up properly in that same dialog box in CC. Did you by chance change your actual WB to something else through RCX? Try re-importing your clips into CC to see if that helps.
 
Last edited:
Burke Doeren said:
I ran into this on a shoot in March using the PL Motion Mount, and an older version of RCX-PRO. Update to the newest version of RCX and you should see colors rendered correctly.

It's some bug in the interaction between the motion mount metadata and the older versions of RCX. Premiere is rendering your colors properly though, so no worries there.

EDIT: Alexander, I just saw your post on the previous page. It's odd that you're not seeing proper color in Premiere CC when you view the raw source. When I encountered this error, it did show up properly in that same dialog box in CC. Did you by chance change your actual WB to something else through RCX? Try re-importing your clips into CC to see if that helps.
Click to expand...

Looks right in RedCine-x but still wrong in Adobe...all my motion mount clips are reading very very blue.

Anyone have any ideas? Perhaps Adobe needs to be contacted?
 
You must log in or register to reply here.
Back
Top