Quote from: philmoz on 30 / November / 2010, 05:43:23unfortunately the spec goes on to stateYou beat me by a matter of seconds, I have just read that !I am writing an application right now to save separate header and narrow image strips.A simple MSDOS bat file joins the raw and headers, I just need a utility to reverse the bytes.David
unfortunately the spec goes on to state
Quote from: philmoz on 30 / November / 2010, 05:48:46Interestingly I just found another address that seems to always contain the raw image data. The address is just over 32MB above the address found in the firmwareIs that the CHDK raw-cached option ?If so, why use it, is it faster ?David
Interestingly I just found another address that seems to always contain the raw image data. The address is just over 32MB above the address found in the firmware
Should not be too difficult.
Man this camera has some serious vignetting at the wide end
could be replaced with:Code: [Select] and r3, r2, r4, lsr #8 // r3 = (in >> 8) & 0xFF00FFThis is done 8 times in each loop, so there's a small saving this way (it still seems to work on my system).
and r3, r2, r4, lsr #8 // r3 = (in >> 8) & 0xFF00FF
My thought was to continue to write one file; but with the bytes not swapped. Then write a command line app that would fix up the DNG file(s) by swapping the bytes. Should not be too difficult.
This has been discussed previously. http://chdk.setepontos.com/index.php?topic=4657.msg45265#msg45265my preferred solution http://chdk.setepontos.com/index.php?topic=1390.msg53067#msg53067I don't like the idea of saving non-valid DNGs, it would be better to prepend our own small, well documented header to it so DNG aware programs don't end up reading our broken DNGs. I still have mixed feelings about adding Yet Another Format, but if we are going to do it, we should do it right.If you use cached raw buffer, the DNG saving time isn't so bad even on 14mp cams. I don't recall exactly what it was on sd990, but I don't remember it being too horrid.
Out of curiosity why do you fix the bad pixels in CHDK rather than write the bad pixel list to the DNG file using the FixBadPixelsList Opcode (and let the raw processor fix them)?
Started by kandrews
« 1 2 3 4 »
Started by philmoz
« 1 2 ... 28 29 »
Started by markoneswift
Started by hulland
« 1 2 3 4 »
Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by speedlite
« 1 2 »