Saving Black Shade Cal Maps

[Dylan Macleod CSC]

I have a personal project I am shooting this weekend where I want to use the Epic in Timelapse mode.

I will be flipping back and forth between regular speed and slow shutters (for time lapse). I want to make sure I have the optimal Black shade Calibration for each shutter speed. From what I can tell in the Ops manual and some google searching - it seems that the Epic can store two Cal Maps.

Sooooo - I am thinking my only option is to use the "factory default" for "normal speed" (23.976). Then do a black shade at 1 fps under the "current FPS/exposure".

My question is - can I then just simply select "current FPS/exposure" in the SETTINGS>MAINTENANCE>CALIBRATION and assume it has stored the black shade I did at those settings?

Thanks in advance.

 

[Rodrigo Prata]

I`m also interested in this subject!

 

[Dylan Macleod CSC]

My worry is that it only allows you to use one "user created" black shade - the "current FPS/exposure". The factory default will always be exactly that, no? I.E. factory default isn't replaced by user black shade.

 

[Mike Lary]

My worry is that it only allows you to use one "user created" black shade - the "current FPS/exposure". The factory default will always be exactly that, no? I.E. factory default isn't replaced by user black shade.

You can create a calibration that works with factory settings (shutter speed falling within the normal range) and a calibration that works with a shutter speed outside of the normal range. You should be able to toggle between the calmaps to recall the different calibrations.

 

[Johnny Friday]

You can create a calibration that works with factory settings (shutter speed falling within the normal range) and a calibration that works with a shutter speed outside of the normal range. You should be able to toggle between the calmaps to recall the different calibrations.

....my reply Huh? how does one do this?

 

[Mike Lary]

....my reply Huh? how does one do this?

I'm not sure what you mean. Calmaps reference different calibrations. Selecting the calmap should recall the calibration.

 

[TheBied]

My worry is that it only allows you to use one "user created" black shade - the "current FPS/exposure". The factory default will always be exactly that, no? I.E. factory default isn't replaced by user black shade.

Dylan --

EPIC / Scarlet currently store 2 internal cal maps. One is the factory map and the other is the user map.

To switch between the 2 maps, use the pull-down selector in the calibration menu. The 2 choices will be 'Factory' or 'User HS'. The current exposure / frame-rate is used for performing the actual calibration.

If you are planning on using 4.0.3 or 4.0.6 you have the added ability to export/import cal maps that you have stored in camera to/from the SSD.

 

[Danai Chutinaton]

I've been confused about this for a long time. Is this correct?

When I do a default calibration, it will calibrate at the default frame rate and exposure (which i believe is 24fps and 180 deg. shutter) and then save that as the "Factory" map in the pull down menu? Or does it save it to the "User HS" option in the pull down menu?

And when I calibrate using the current framerate and exposure the cal map is saved as the "User HS".

Regarding FW 4.0.6, can you explain the new temporary and permanent options for importing calmaps from SSD?

 

[TheBied]

I've been confused about this for a long time. Is this correct?

When I do a default calibration, it will calibrate at the default frame rate and exposure (which i believe is 24fps and 180 deg. shutter) and then save that as the "Factory" map in the pull down menu?

And when I calibrate using the current framerate and exposure the cal map is saved as the "User HS".

No, this not correct. When 'USER HS' is selected it implies you are using the 1 user map stored on the camera (default OR current exposure / framerate). The 'Factory' calibration is permanently stored and cannot be overwritten.

Regarding FW 4.0.6, can you explain the new temporary and permanent options for importing calmaps from SSD?

I gave a short explanation here: http://www.reduser.net/forum/showth...t-and-Epic-BUILD-4-BETA&p=1124809#post1124809 regarding the temporary vs permanent options.

If you are using the temporary option, you will need to cycle between maps in the calibration menu if you want to restore to a map stored on camera.

It is also important to remember that if you format an SSD containing calibration maps, they will be lost during the format.

 

[Dylan Macleod CSC]

Thanks for the clarification Matthew. Yes - running 4.0.6. I did notice that I could save one to SSD which is a great feature.

So in order to have two "custom calibrations" (i.e. not factory) I can have one "in camera" as the "user fps/shutter" but the other will need to be stored on the card?

Loving the timelapse feature - by the way.

 

[TheBied]

Thanks for the clarification Matthew. Yes - running 4.0.6. I did notice that I could save one to SSD which is a great feature.

So in order to have two "custom calibrations" (i.e. not factory) I can have one "in camera" as the "user fps/shutter" but the other will need to be stored on the card?

Loving the timelapse feature - by the way.

That is correct.

If you want to have 2 custom calibrations available you currently need to store 1 or both on an SSD. (And probably on a computer for backup)

And just to repeat. If you import a map temporarily you will need reboot or cycle through the maps stored on the camera to clear the temporary map.

Thanks! It's been great to see all of the work done with it so far too.

 

[Brent J. Craig]

...so it seem the obvious question is how to create and save a number of shadings, back them up on a computer, and restore them as needed while shooting. Do we need files for 1fps, 1 frame per minute, 1 frame per hour?!?

The 30 minute "calibration" process might work in prep and testing, but 30 minutes on a production set can cost thousands of dollars.

Is Epic the right tool for our timelapse shots?

 

[Dylan Macleod CSC]

...so it seem the obvious question is how to create and save a number of shadings, back them up on a computer, and restore them as needed while shooting. Do we need files for 1fps, 1 frame per minute, 1 frame per hour?!?

The 30 minute "calibration" process might work in prep and testing, but 30 minutes on a production set can cost thousands of dollars.

Is Epic the right tool for our timelapse shots?

Hey Brent - I believe the calibrations are only sensitive to shutter speed and temperature. So the interval in your example (per second, per minute, per hour) could use the same one. It depends on how long your exposure is. I think in it's Beta form it is very useful - and will only become more so. So nice to have Epic quality timelapse!

But I agree - black shade length could do with a major reduction!

 

[Maz Mawlawi]

Has RED considered doing a very cheap and very small SSD size that we could use ONLY for storing Black shading maps, Key mapping export, firmware upgrades etc.. this "SSD" would only need to be like 128 megs (heck it could be an SD card inside the SSD casing)...no need for speedy flash memory or anything. Just pure storage. This would help dramatically and then we wouldn't have to use our expensive SSDs just for that function (it would also allow us to always have it on hand as opposed to formatting the SSD...copying from a laptop etc...)

maybe I will post this as a feature request...

 

[Tim Bradley]

Has RED considered doing a very cheap and very small SSD size that we could use ONLY for storing Black shading maps, Key mapping export, firmware upgrades etc.. this "SSD" would only need to be like 128 megs (heck it could be an SD card inside the SSD casing)...no need for speedy flash memory or anything. Just pure storage. This would help dramatically and then we wouldn't have to use our expensive SSDs just for that function (it would also allow us to always have it on hand as opposed to formatting the SSD...copying from .

maybe I will post this as a feature request...

Great idea! I would buy one to have in my kit.

 

[Michael Blieden]

Question on this topic. I have Dragon cal maps for LL and Skin Tone OLPF's, but I'd like to name them because I'm a dummy and I'll forget which is which. There doesn't seem to be an in-camera mechanism for naming different user calibrations. I tried exporting them to SSD>changing the names with a laptop>re-importing them. But the imports failed. Did they fail because of the name changes or are their naming conventions that I'm violating?

 

[James Falco]

Question on this topic. I have Dragon cal maps for LL and Skin Tone OLPF's, but I'd like to name them because I'm a dummy and I'll forget which is which. There doesn't seem to be an in-camera mechanism for naming different user calibrations. I tried exporting them to SSD>changing the names with a laptop>re-importing them. But the imports failed. Did they fail because of the name changes or are their naming conventions that I'm violating?

Blackshading is OLPF and frame rate independend!

Only two things that matter is sensor temperature and shutter speed.
The frame rate affects the results only if shutter is set to shutter angle as that changes parallel to frame rate.
But if you calibrate at 1/48sec and switch from 24 frames to 1 frame keeping shutter speed at 1/48, calibration will still be ok.

Center bottom screen where it says: Cal T/E, stands for Temperature / Cal map. If both are green. You are good.

 

[Phil Holland]

Center bottom screen where it says: Cal T/E, stands for Temperature / Cal map. If both are green. You are good.

Just a small correction.

The T/E stands for Temperature and Exposure (as in exposure duration or shutter speed). The Cal Map is generated for this combination of chaotic events

 

[Christoffer Glans]

They could have optimized the free space on the +1 Module to have a SD-card slot where storage of black shades, settings and other stuff are saved.
I'm not sure why there isn't anything like that.

 

[James Falco]

Thanx Phil.