Do you know if there's a ixus 220 hs DNG profile, to correct RAW distortion and vignetting in camera? Thanks a lot.
Quote from: jstanley0 on 05 / December / 2011, 22:14:55In any case, I've attached some builds so others can try this out and provide feedback.The build on my camera just got into a state where it failed to refresh the screen after closing the CHDK menu.So, although vid_turn_off_updates() -> ScreenLock() is promising, there are still some kinks to work out.It'd be nice if we could hook in somewhere and get the opportunity to draw our stuff on the back buffer right before the firmware swaps buffers, but I have no idea whether that is feasible (or whether the original firmware actually operates that way, for that matter). Failing that, at least doing ScreenLock while the menu is up would prevent the worst of the visual issues, provided we can make it work reliably. (It strikes me as odd that pretty much no two models handle screen updates the same way. This isn't something I think Canon would do differently with every iteration???)
In any case, I've attached some builds so others can try this out and provide feedback.
I tried it on the G12 and although it does make the CHDK display a lot more stable it also causes major problems.For example if a script uses the 'shoot' command the camera tries to switch to review mode after the picture is taken. The screen goes black and the review is not shown (because of the lock presumably). The screen stays black and nothing is displayed again until the script exits.
.DNG metadata is still a bit messed up. in particular, the camera model name doesn't appear to be terminated properly.
Quote from: jstanley0 on 06 / December / 2011, 16:52:34.DNG metadata is still a bit messed up. in particular, the camera model name doesn't appear to be terminated properly.This isn't specific to our port; it's part of core/dng.c. I've compared the camera name tag in Canon's JPEGs and CHDK's DNGs. Both write the same 32-byte buffer, "Canon Powershot ELPH 300HS\x00\xff\xff\xff\xff\xff". But there's a difference--the JPEG gives the size of the item as 27 bytes (not including the FF padding), whereas CHDK's DNG gives the size as 32 bytes (including the padding).
If the DNG code is writing 32 bytes to the file then the size of 32 is correct.The 0 terminator on the string should make sure that any program processing the DNG ignores the padding bytes.
2 = ASCII 8-bit byte that contains a 7-bit ASCII code; the last byte must be NUL (binary 0)....The value of the Count part of an ASCII field entry includes the NUL. If padding is necessary, the Count does not include the pad byte. ...
What program is having trouble with the field?
Quote from: philmoz on 06 / December / 2011, 21:43:28If the DNG code is writing 32 bytes to the file then the size of 32 is correct.The 0 terminator on the string should make sure that any program processing the DNG ignores the padding bytes.Not according to the TIFF specification:Quote2 = ASCII 8-bit byte that contains a 7-bit ASCII code; the last byte must be NUL (binary 0)....The value of the Count part of an ASCII field entry includes the NUL. If padding is necessary, the Count does not include the pad byte. ...Each tag has its own offset field, so it's not necessary to know the true size of a tag on disk in order to find the next tag.Quote from: philmoz on 06 / December / 2011, 21:43:28What program is having trouble with the field?Picasa 3.5. I also remember reading about this problem somewhere else, but I've been unable to find where...
switch (IFD_LIST[j].entry[i].tag) { case 0x110 : // CameraName case 0xC614: IFD_LIST[j].entry[i].count = strlen((char*)IFD_LIST[j].entry[i].offset) + 1; break; // UniqueCameraModel case 0x132 : case 0x9003: IFD_LIST[j].entry[i].offset=(int)get_date_for_exif(exif_data->time); break; //DateTimeOriginal
Started by acseven General Discussion and Assistance
Started by ELPH300 « 1 2 » Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by VincentD « 1 2 3 » General Help and Assistance on using CHDK stable releases
Started by yoshiharra General Help and Assistance on using CHDK stable releases
Started by igb General Help and Assistance on using CHDK stable releases