In RawTherapee as they are already demosaiced the tools in the "Raw" tab will be disabled.
Code: [Select]exiftool -v4 FILENAME.RAW > list.txt
exiftool -v4 FILENAME.RAW > list.txt
Right... I'll do that tonight.
So far, it looks like VignettingCorrUnknown2 is not a straight copy from the ROM.
So again, it's certainly useful to have the option of going through linear DNG, but it's limiting in some ways.It would still be a good argument for including the lens correction parameters in CHDK DNG if we can, obviously getting correction in some applications is better than none
For example, RT allows you to do CA correction (there's another CA option outside the raw tab, but the results aren't quite as good), flat fielding and of course adjust demosaicing options in the raw tab. Some of the options in other tabs are also only available on raw images.
Quote from: koshy on 27 / June / 2018, 08:23:09Quote from: blackhole on 27 / June / 2018, 08:16:43Here you can see what has been added with the last update, and what ever was supported in Adobe products.https://helpx.adobe.com/camera-raw/kb/supported-lenses.htmlYes, like I said no "CANON POWERSHOT G9 X MARK II" or anything recent.The CANON POWERSHOT G9 X MARK II is supported, see here:https://helpx.adobe.com/camera-raw/kb/camera-raw-plug-supported-cameras.htmlThe PowerShot G1 X Mark III is also supported from CR 10.1 onwards.
Quote from: blackhole on 27 / June / 2018, 08:16:43Here you can see what has been added with the last update, and what ever was supported in Adobe products.https://helpx.adobe.com/camera-raw/kb/supported-lenses.htmlYes, like I said no "CANON POWERSHOT G9 X MARK II" or anything recent.
Here you can see what has been added with the last update, and what ever was supported in Adobe products.https://helpx.adobe.com/camera-raw/kb/supported-lenses.html
You're missing the distinction... The first item you posted was "supported lenses" the second is "supported cameras". The first item lists where Adobe produced individual *.lcp lens charaterizations, the second item lists what they support for debayering etc. Now, for any camera that has the correction of field curvature and or vignetting detailed on its RAW data (typically in the maker notes) Adobe does NOT supply *.lcp lens charaterizations as they would be redundant. That is why the CANON POWERSHOT G9 X MARK II is NOT on the first list you posted but of course is on the second. Hope that clears this up.
Quote from: srsa_4c on 27 / June / 2018, 14:06:33So far, it looks like VignettingCorrUnknown2 is not a straight copy from the ROM.If it's the right item that seems obvious. Field curvature correction depends on the current focal length and if there is an iris (which for the cams with native RAW there is) and such is used vignetting correction in addition depends on the aperture. With a couple of hundres zoom steps as reyalp pointed out and the number of aperture settings there would be far to many to just keep them in ROM to copy out. They need to be generated and the really intriguing question on that end would be what Canon FW aspects control that generation. Why would they be any different for RAW than what goes into the native JPEGs? just saying that if it were possible to reverse the generation process where the output is known it might be possible to use the same FW aspects on the cameras without native RAW for the CHDK DNGs. The reason to even ponder characterization based on image data was that I was willing to see that through for the whole lot of cameras that need it because the alternative (a in camera DNG solution) seemed lightyears away...
Why would they be any different for RAW than what goes into the native JPEGs
CANON POWERSHOT G15.CR2CANON POWERSHOT G16.CR2CANON POWERSHOT S90.CR2CANON POWERSHOT S110.CR2CANON POWERSHOT S120.CR2CANON POWERSHOT SX50.CR2CANON POWERSHOT SX60 HS.CR2CANON POWERSHOT G1 X MARK II.CR2CANON POWERSHOT G1 X MARK III.CR2CANON POWERSHOT G3 X.CR2CANON POWERSHOT G5 X.CR2CANON POWERSHOT G7 X MARK II.CR2CANON POWERSHOT G7 X.CR2CANON POWERSHOT G9 X MARK II.CR2CANON POWERSHOT G9 X.CR2
Line 1212: | | | 33) VignettingCorrUnknown2 (SubDirectory) --> Line 1278: | | | | VignettingCorrVersion = 3 Line 3068: | | | 44) VignettingCorrUnknown2 (SubDirectory) --> Line 3132: | | | | VignettingCorrVersion = 5 Line 3135: | | | 45) VignettingCorr2 (SubDirectory) --> Line 4610: | | | 31) VignettingCorrUnknown1 (SubDirectory) --> Line 4643: | | | | VignettingCorrVersion = 2 Line 5986: | | | 32) VignettingCorrUnknown2 (SubDirectory) --> Line 6052: | | | | VignettingCorrVersion = 3 Line 7555: | | | 34) VignettingCorrUnknown2 (SubDirectory) --> Line 7622: | | | | VignettingCorrVersion = 4 Line 9134: | | | 34) VignettingCorrUnknown2 (SubDirectory) --> Line 9201: | | | | VignettingCorrVersion = 4 Line 10980: | | | 43) VignettingCorrUnknown2 (SubDirectory) --> Line 11044: | | | | VignettingCorrVersion = 5 Line 11047: | | | 44) VignettingCorr2 (SubDirectory) --> Line 12554: | | | 33) VignettingCorrUnknown2 (SubDirectory) --> Line 12621: | | | | VignettingCorrVersion = 4 Line 14392: | | | 44) VignettingCorrUnknown2 (SubDirectory) --> Line 14456: | | | | VignettingCorrVersion = 5 Line 14459: | | | 45) VignettingCorr2 (SubDirectory) --> Line 16098: | | | 34) VignettingCorrUnknown2 (SubDirectory) --> Line 16165: | | | | VignettingCorrVersion = 4 Line 17513: | | | 31) VignettingCorrUnknown1 (SubDirectory) --> Line 17546: | | | | VignettingCorrVersion = 2 Line 18889: | | | 32) VignettingCorrUnknown2 (SubDirectory) --> Line 18955: | | | | VignettingCorrVersion = 3 Line 20067: | | | 27) VignettingCorrUnknown1 (SubDirectory) --> Line 20075: | | | | VignettingCorrVersion = 1 Line 21404: | | | 31) VignettingCorrUnknown1 (SubDirectory) --> Line 21437: | | | | VignettingCorrVersion = 2 Line 22782: | | | 33) VignettingCorrUnknown2 (SubDirectory) --> Line 22849: | | | | VignettingCorrVersion = 4
The DIGIC vignetting/distortion correction unit likely takes the correction data in a different format.
I looked up the related routines in g7x 100d - it was easy to find as 0x4015 is not an often used constant.The handler for tag 0x4015 is sub_FC49034C. The routine that creates the tag's content is sub_FC4F92D8. It's unfortunately rather complex - many small pieces of information is collected there.
Started by kdeal Feature Requests
Started by gvanhau General Help and Assistance on using CHDK stable releases
Started by davecool RAW Shooting and Processing
Started by vit40 DSLR Hack development
Started by studuatiga General Discussion and Assistance