Petri Teittinen
Well-known member
Hello gents,
I upgraded my Epic MX to 5.2.29 a moment ago, and had to do the dumb REDmote updating dance with my laptop again, even though RED has been aware of that issue for ages... but I digress.
Even though it wasn't specifically ordered on the instructions, I decided to do a black shade calibration. It had been a while since I last updated my Epic, so the partly re-designed GUI came as a bit of a surprise. I hope this issue is actually caused by my inexperience with the new GUI.
I first checked the default 24fps 1/48th factory black shading at shooting temps by letting the camera warm up and then setting FLUT to 8.00 - and it turned out to be quite badly off. Right side of the image had all kinds of extra artefacts on it, from vertical stripes to a magenta shade which got worse towards the right edge.
So I decided to black shade the 1/48th shutter speed first and save that as default calibration. I could have sworn Epic used to let me save a calibration to the "factory" slot, but on the 5.2.29 that appears to be impossible. In other words, I could save a 1/48th black shading only in the "User" slot. You know what that meant when I decided to do another black shading at 1/192 second shutter speed. Yup, that earlier calibration gets written over.
Of course I saved the 1/48th calibration to the SSD first, followed by the 1/192 once that was done, then copied both to my server for safekeeping. By the way, the noise on screen with FLUT 8.00 is now flawless at both shutter speeds.
But here's the silly part: as I can't use the Factory slot for anything, I'm down to a single calibration slot, the User one. This means that if I go from regular shutter speeds to faster ones for high frame rates, I need to load a calibration from the SSD.
Which takes 10-15 minutes!
If I had two calibration slots, one for 1/48 and other for 1/200, I could swap from normal to high fps shutter speeds in a few seconds. But now it takes 10-15 minutes. That's quite simply unacceptable.
I certainly hope there's something I've missed and have misunderstood the situation completely due to my boneheadedness.
I upgraded my Epic MX to 5.2.29 a moment ago, and had to do the dumb REDmote updating dance with my laptop again, even though RED has been aware of that issue for ages... but I digress.
Even though it wasn't specifically ordered on the instructions, I decided to do a black shade calibration. It had been a while since I last updated my Epic, so the partly re-designed GUI came as a bit of a surprise. I hope this issue is actually caused by my inexperience with the new GUI.
I first checked the default 24fps 1/48th factory black shading at shooting temps by letting the camera warm up and then setting FLUT to 8.00 - and it turned out to be quite badly off. Right side of the image had all kinds of extra artefacts on it, from vertical stripes to a magenta shade which got worse towards the right edge.
So I decided to black shade the 1/48th shutter speed first and save that as default calibration. I could have sworn Epic used to let me save a calibration to the "factory" slot, but on the 5.2.29 that appears to be impossible. In other words, I could save a 1/48th black shading only in the "User" slot. You know what that meant when I decided to do another black shading at 1/192 second shutter speed. Yup, that earlier calibration gets written over.
Of course I saved the 1/48th calibration to the SSD first, followed by the 1/192 once that was done, then copied both to my server for safekeeping. By the way, the noise on screen with FLUT 8.00 is now flawless at both shutter speeds.
But here's the silly part: as I can't use the Factory slot for anything, I'm down to a single calibration slot, the User one. This means that if I go from regular shutter speeds to faster ones for high frame rates, I need to load a calibration from the SSD.
Which takes 10-15 minutes!
If I had two calibration slots, one for 1/48 and other for 1/200, I could swap from normal to high fps shutter speeds in a few seconds. But now it takes 10-15 minutes. That's quite simply unacceptable.
I certainly hope there's something I've missed and have misunderstood the situation completely due to my boneheadedness.