SD450 BadPixel.bin? - Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes) - CHDK Forum supplierdeeply

SD450 BadPixel.bin?

  • 2 Replies
  • 2011 Views
SD450 BadPixel.bin?
« on: 05 / March / 2010, 02:02:59 »
Advertisements
So, I tried running the badpixel.lua script on my SD450 that I just got CHDK installed on, and got the script to run (after changing 'shoot()' to 'click "shoot_full"') and it exits with "File is saved", but using the file browser (or putting the card in my desktop computer), there's no badpixel.bin file created in the CHDK folder. Is this feature not available for the SD450, and therefore it doesn't have DNG options?

*

Offline fe50

  • ******
  • 3132
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: SD450 BadPixel.bin?
« Reply #1 on: 06 / March / 2010, 05:27:17 »
So, I tried running the badpixel.lua script on my SD450 that I just got CHDK installed on, and got the script to run (after changing 'shoot()' to 'click "shoot_full"') and it exits with "File is saved", but using the file browser (or putting the card in my desktop computer), there's no badpixel.bin file created in the CHDK folder. Is this feature not available for the SD450, and therefore it doesn't have DNG options?
After a short look to the CHDK source ... the SD450 should be able to produce DNG files, the DNG support is enabled.

 * is there a file "bad_tmp.bin" somewhere on the card ? rename it to badpixel.bin & place it in the \CHDK folder of your SD card
 * try creating the badpixel.bin file with your computer --> http://chdk.wikia.com/wiki/Badpixel_removal

Re: SD450 BadPixel.bin?
« Reply #2 on: 06 / March / 2010, 10:44:51 »
I'm on an Intel Mac running 10.4 at the moment, and the Bad Pixel Pro app for Intel Macs doesn't actually launch for me (I see it's icon in the dock for a moment and then it kills itself). Looking at its crash logs, I can see error lines indicating that I have version 5.0.0 of libiconv.2.dylib, and it requires 7.0.0, so I'll see if I can get MacPorts to help me out with that.

I did do a search of the whole SD card on my desktop for the term "bad", and only came up with the "badpixel.lua" script itself.

I did do some analysis of the badpixel.lua script itself (see this thread), and while ewavr pointed out where the bad_tmp.bin file should be created in the source, I'm wondering if the package I got doesn't have that line added to the proper source file. That would make sense of the evidence that no bad_tmp.bin file is created anywhere, and the script is returning "255", the 'special flag' number, rather than a more random number.

 

Related Topics