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

Sheer codec ? (and RA / RC codec options)

Altering with the Log curve is not really helping you preserve highlight details, you are just moving the grey point so it seems that way. Remember you are likely displaying this on a 2.2 monitor. http://3.bp.blogspot.com/_bkp96efBnsQ/SPLNB8KvPXI/AAAAAAAAA-Y/GhXeZp5TiJM/s400/curves.jpg The green curve is Log-90 (nearly the same as RedLog), the cyan curve is 2.2 gamma, so as Log curve is above the 2.2 gamma curve (for all but the darkness shadow detail) the image will appear brighter. But all the curve clips at the some point, so all contain the same dynamic range. The reason to use a log curve over 2.2 gamma (and particularly over linear -- see old post: http://cineform.blogspot.com/2007/09/10-bit-log-vs-12-bit-linear.html) is to do with maintainly visually lossless compression through post production. If you need to extract details for Log 90 highest, any greater than 8-bit curves filter will do the trick.

Hmmm ... I wish I could understand in totality ! I can see that all curves hit the same black and white points ... (ie : I take it this means their 'values' are the same and therefore do not change). Therefore, the shape (which is not a million miles from the Gamma node in Shake) is just, as you say, make it seem as though I am ? right ?

So, bottom line, how do I [ If you need to extract details for Log 90 highest, any greater than 8-bit curves filter will do the trick ] ... I'm not totally clear what you mean by this ? and practically how do I achieve this ?

BTW : thanks for responding :usd:

EDIT : re-reading this, I guess you mean 16bit or float pipeline and lowering the white point in curves (Photoshop terminology) ?
 
We find the camera default 320 ASA is effectively applying digital gain, so we develop the base image to 250 ASA and disable white balance gains and DRX processing which both potentially clip or distort highlights.


Interesting...

Anyone from RED to comment on this? :detective2:
 
Interesting...

Anyone from RED to comment on this? :detective2:

It pretty common knowledge if you shoot 320 you can gain some highlights back (without using DRX) by changing the exposure or ASA in RedCine or RedAlert (this is what h2opixels saying with "... drop the ASA and re-render to recover any highlights".) Have found the some thing using the SDK. What the camera ISO actually is not the issue, rather developing the image with a 250 setting yields the best results, and that is what we trying to deliver to the customer. Once the SDK in updated to provide RAW, many of these issues go way, just store what the camera saw, from clipping to noise floor.
 
Hmmm ... I wish I could understand in totality ! I can see that all curves hit the same black and white points ... (ie : I take it this means their 'values' are the same and therefore do not change). Therefore, the shape (which is not a million miles from the Gamma node in Shake) is just, as you say, make it seem as though I am ? right ?

So, bottom line, how do I [ If you need to extract details for Log 90 highest, any greater than 8-bit curves filter will do the trick ] ... I'm not totally clear what you mean by this ? and practically how do I achieve this ?

BTW : thanks for responding :usd:

EDIT : re-reading this, I guess you mean 16bit or float pipeline and lowering the white point in curves (Photoshop terminology) ?

Yes, using 16-bit or floating point operations to adjust the output for you visual preference, 8-bit can intro visible band (particularly with curve changes.) This is all basic color correction, different tools the adjust the curves, white and black points and saturation. Read "the Rebel's Guide.." which state something like color correction can all be done with Levels, Hue and Saturion.
 
Yes, using 16-bit or floating point operations to adjust the output for you visual preference, 8-bit can intro visible band (particularly with curve changes.) This is all basic color correction, different tools the adjust the curves, white and black points and saturation. Read "the Rebel's Guide.." which state something like color correction can all be done with Levels, Hue and Saturion.

Sure ... the 'Log 90 highest' threw me ;-)
 
What is your work flow starting from R3D files => .... => Sheer encoded file ? I take it you have not done this in one hit (directly via RedAlert or RedCine) ? Unless this is the case, I'll lose interest pretty quickly ...

I'm afraid you'll loose interest then…
We only use it for FX shots going from FCP to AE (and back), our main workflow is FCP based. I had to give up on Shake, which made me quite sad. Too many problems on Intel machines with anything above 8 bit other than DPX, while FCP doesn't play nice with image sequences.

I wish Apple would integrate Color seamlessly via DPX with Shake, but that's never gonna happen :sad:
 
I'm afraid you'll loose interest then…
We only use it for FX shots going from FCP to AE (and back), our main workflow is FCP based. I had to give up on Shake, which made me quite sad. Too many problems on Intel machines with anything above 8 bit other than DPX, while FCP doesn't play nice with image sequences.

I wish Apple would integrate Color seamlessly via DPX with Shake, but that's never gonna happen :sad:

I have also been looking at http://www.gluetools.com/products_dpx.html but the volume of data is not insignificant (not too keen on dongles either). Smaller proxies do help, but more rendering (ie : TIME).

Cheers ...
 
Back
Top