Before you start speculating...why dont you eliminate operator error as the cause. Check your settings, then come back and discuss with some facts in hand.
The colour balance issues was quite disturbing. Couple things to try
1) If the white balance was auto, the tint is also changed, from my understanding once you go back to manual or day light the tint may still be carried over. hence check the tint
2) also reset the black shading to factory default and shoot to see how the color temp change.
But the noise level is fairly high prior to having the upgrade done.
I have been in touch with red tech guys and will be sending some r3d files for them to look at.
So have you attempted to open an .R3D file in Redcine, and just look at it in there?
Proxies, which I offline with all the time, if I am not mistaken, take on the look that was set in the monitoring output of the camera, so if your ISO on set is set to 1200, your proxies are going to look grainy for instance.
But... all the while, your really shooting raw data, and the look you punch up on the camera is non-destructive to the raw data. If you open the raw in Redcine, you can view that raw footage at any ISO, white balance, color space, gamma space, etc.... you can always get back to raw.
So I'm guessing the change you've seen is a result of some kind of monitoring decision you've made at some point with the camera's viewing settings.
In my very humble opinion, proxies are for rough cutting only. I have never finished a project with proxies, I only export timelines with them during rough cut phase. All footage I work with gets transcoded via Redcine (Camera RGB and Gamma:REDlog) and conformed before grading happens in Color. There are other workflows too, but finishing with proxies is like eating hamburger when you could have steak. I don't mean that to sound flippant, just a proper analogy. If you would like assistance with workflow, happy to help.
(Anyone else on here, feel free to correct me about the proxy files baking in the camera viewing space... that is my understanding.)
You are right Steve... this process of "Restoring" the Black Shading before you "Start" it, will restore your Black Shading to the factory default values rather than calibrating over user defined black levels.
it is broken down in the new ops guide starting on page 80.
Stephen, if you would like to email me directly, you are more than welcome to. Nate - at - RED
We'll get you all squared away. :)
My I ask what's the point of having one black shading lap over an older shade? If this could degrade the image in any way, why does the camera not automatically restore to the factory default before a new black shade is performed?
Quick question, what version of quicktime are you running? If you are only viewing the quicktime proxies that may prove useful to know aswell. Are you ONLY looking at quicktime proxies, or is the same noise exhibited in red alert/red cine?
Here's what I did.
1. I did a full factory reset.
2. I did a reset black shading to factory default.
3. I installed Build 21.1.3.
4. I did a new black shading.
And, while I haven't been able to do a noise test on my editing system (it is parked at my editor's house and he's out of town), the strange white balance problem we were having is now corrected. Set at 5600K looks normal again.
I suspect that the problem may, indeed, be resolved, but I shall report back as soon as I can.
Thanks for all of your comments.
when you restore it, it will ask you to power cycle the camera, so it is a slightly longer process... it isn't necessary to restore it, but given a situation like this, or if there was a problem during the calibration, I would just "Restore" it to take me back to ground zero.
I hope this helps. :)
|« Previous Thread | Next Thread »|