Bug Reports against Recent Builds -- Report bugs here

[PhyrePhoX]

hm i thought we uncommented that again later. weird.

[careyer]

BadPixel.LUA Script does not work on IXUS40 1.00J build 9.8.766.

When starting the script the camera takes a picture, the LCD screen gets deactivated and the camera is obviously computing something for about 10-15sec since the DirectPrint Button is blinking. Then the camera just powers off without retracting the lens. Looks like it somehow crashes. Would be cool if this one would work on the IXUS40s too since my cam shows signifficantly more bad or dead pixels lately. Objously semi-conductors show some kind of aging anyway :-(

[fe50]

BadPixel.LUA Script does not work on IXUS40 1.00J build 9.8.766.
When starting the script the camera takes a picture, the LCD screen gets deactivated and the camera is obviously computing something for about 10-15sec since the DirectPrint Button is blinking. Then the camera just powers off without retracting the lens. Looks like it somehow crashes. Would be cool if this one would work on the IXUS40s too since my cam shows signifficantly more bad or dead pixels lately. Objously semi-conductors show some kind of aging anyway :-(

Hi careyer,
the badpixel.lua script creates just a "copy" of the badpixel list stored in the Canon firmware, only with the pixels that were already "bad" while manufacturing. This script an its result (the badpixel.bin file) is only used for the creation of DNG RAW images.
The badpixel.bin file can also be created with the "show_bad_b.exe" tool...

To remove "new" badpixels, you have to create a file "badpixel" with the coordinates of the pixels; with CHDK then (all) the badpixels will be "removed", in the JPEG files & also in the RAW / DNG files. The creation of this file is done by the "show_bad.exe" tool, a Windows command line app; if you're running another OS you should be able to compile the tool for your system (e.g. with gcc) - the source code is included in the download package.
For the possible CHDK settings have a look to this post.

In the wikia you'll find some more informations about those two methods of badpixel removal, also the links to the tools...

     --> http://chdk.wikia.com/wiki/Badpixel_removal

[Skinkie]

A590;

- Disp button basically doesn't work as expected, the screen goes blank but pressing the button again doesn't make it come up again.

- Poweroff retracts the lens, screen goes off, camera goes on again on screen 'E24' and then turns off again.

[fudgey]

A590;

- Disp button basically doesn't work as expected, the screen goes blank but pressing the button again doesn't make it come up again.

- Poweroff retracts the lens, screen goes off, camera goes on again on screen 'E24' and then turns off again.

This very much sounds like a hardware problem not related to CHDK in any way i.e. your camera is probably broken and in need of service. To verify, use it without CHDK until you get the same error.

[Skinkie]

A590;

- Disp button basically doesn't work as expected, the screen goes blank but pressing the button again doesn't make it come up again.

- Poweroff retracts the lens, screen goes off, camera goes on again on screen 'E24' and then turns off again.

This very much sounds like a hardware problem not related to CHDK in any way i.e. your camera is probably broken and in need of service. To verify, use it without CHDK until you get the same error.

Sorry you are right, verified without CHDK.

[hotpepper]

On A560 didn't work the LCD control. "Disable LCD" function.

[3belas]

A590;

build a590-101b-0.9.8-772 : I thing some bugs with OSD display- while half pressing the shutter, the OSD flashes on and off, as well the original firmware's 2:3 grid lines. The problem more obvious with build a590-101b-0.9.8-770 (after half-pressing the shutter multiple times). This also occurs with build 758 & 769

[bugsplatter]

-778 on a590, the clock and temperature are displayed on play screen when I set chdk to not display on play.

ubasic: set_led x y [z] does nothing, shut_down does nothing.

Otherwise I'm having a ball writing my first decent script

[reyalp]

-778 on a590, the clock and temperature are displayed on play screen when I set chdk to not display on play.

This is with "hide OSD? in play" ?

Probably a bug. I'd guess address of recreview_hold is wrong. Which firmware version of a590 ?

ubasic: set_led x y [z] does nothing, shut_down does nothing.

set_led is not yet implemented on a590. Not sure if shutdown ever worked.

[bugsplatter]

This is with "hide OSD? in play" ?

Yes.  Double checked, the other OSD values MB free, Batt V disappear on play screen

Probably a bug. I'd guess address of recreview_hold is wrong. Which firmware version of a590 ?

Think so   It's 1.01B

set_led is not yet implemented on a590. Not sure if shutdown ever worked.

Hmm, okay, 'spose I gotta look at the source then...  I would like to properly shutdown the cam on low battery or end of timelapse session.  Shutdown works on some cams?

If I come up with anything you take unified diffs?  I've done small linux-kernel patch submissions and like their coding style and conventions. 

[bugsplatter]

I ran the badpixel script today, is >11000 bad pixels 'normal' for an 8MB CCD?  a590 101b, -778

[reyalp]

Search for "shut_down" in the forum. It appears that it works on some cameras, but has some quirks.

Quick test on my a540, it appears to do nothing, but If I press the alt button after it has run, the camera shuts down.

Not sure what normal badpixel count is. The file for my 6mp cam is 10kb

[bugsplatter]

Search for "shut_down" in the forum. It appears that it works on some cameras, but has some quirks.

Quick test on my a540, it appears to do nothing, but If I press the alt button after it has run, the camera shuts down.

Code: [Select]

:shutdown
if not (o & 8) then end
print "Shutdown..."
sleep 1000
shut_down
sleep 3000
end

Now works on a590 101b -778, key is to sleep before and after so the cam is idle, perhaps?

Not sure what normal badpixel count is. The file for my 6mp cam is 10kb

Badpixel file on my a590 is 46KB  But then I've been driving it hard recently.

[fe50]

Badpixel.bin on my SX10 (10MP) is ~47kB...