Uhhmm... unless I'm totally misunderstanding how the RAW data is being held in the camera's memory.... it should be in the format of RGBG (bayer matrix) for all of these cameras.Aren't they all luminance values taken direct from the sensor? They just happen to have a color filter over each one. No such thing as a "colorPixel" in RAW.
Quote from: Barney Fife on 04 / April / 2008, 01:37:18Uhhmm... unless I'm totally misunderstanding how the RAW data is being held in the camera's memory.... it should be in the format of RGBG (bayer matrix) for all of these cameras.Aren't they all luminance values taken direct from the sensor? They just happen to have a color filter over each one. No such thing as a "colorPixel" in RAW.Still need to find out what color filter is for which pixel. I am planning to apply a different response curve against each of those 'color filtered' pixel (e.g. the one with green filter will have the 'Green' response curve applied to).
Can you confirm that the CHDK RAW file is readable by dcraw?
Anyway, it should work very quick to prevent camera from shutdown by watchdog timeout.
unsigned short curve; // The 3 different color level conversion can be done here... // (we'll do twice the Green one).// Assume to have the following matrix// (0)(1)// (2)(3)Cut out the outdated code to make room in the post...Thank you all for your input.Hope that I won't have to declare this as a dead feature.
> unsigned short curve; > ...> pixVal[k]=curve[2*(i&2)+(k&2)][pixVal[k]]; // Assumme BayerThe expression 2*(i&2)+(k&2) can has 0, 2, 4, 6 as the result, but declaration is "curve".Is it supposed to be 2*(i&1)+(k&1)?
Well I finished the coding and run a couple of test...
What does your code do?
How do we add it to CHDK?
Can you post some results for us to see?
This might be an excellent way to "fix" the color shift that happens when averaging RAW images for in-camera HDR. Averaging 3 or 5 bracketed RAW frames seemed to provide some excellent results in another thread where people were testing this. But highlights were getting strongly shifted into magentas/reds (most likely due to not having a proper color profile for RAW import that wasn't expecting that many frames added together needing compensation more accurately).
I hope you don't give up working on this. For the advanced photographer this would be an excellent addition. The more that can be done with some simple and well-tested defaults in our cameras, the less that needs to be done in editing. I for one would love to be able to tone-down the contrast a bit more in my camera (for a simple example). Canon loses too much dynamic range in its JPGs by trying to produce garish "advertising" images to the average consumer.
Started by kdeal
Started by vine
Creative Uses of CHDK
Started by msl
Started by cedricb
RAW Shooting and Processing
Started by an0n