Bug Reports against Recent Builds -- Report bugs here

[bugsplatter]

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

Okay, so mine's not dying then

[fe50]

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

Okay, so mine's not dying then

LOL - at least you won't see your cam dying on the amount of THESE bad pixels - they were already dead when Canon decided to pack your camera in a gummi bear colored box & sell it...to see your cam aging -or maybe also dying- have a look to the increasing amount of "new" bad pixels, the upcoming stars on your images...

[bugsplatter]

LOL - at least you won't see your cam dying on the amount of THESE bad pixels - they were already dead when Canon decided to pack your camera in a gummi bear colored box & sell it...to see your cam aging -or maybe also dying- have a look to the increasing amount of "new" bad pixels, the upcoming stars on your images...

I think the lens assembly will go before the sensor, it's now quite noisy and sloppy.

Another buglet I noticed on -778 (on a590 101b) is the top left corner value multiplier (for script param value entry) should go back to x1 after 'up or 'down' button press.  At the moment it displays the last used value, but the multiplier is reset to to x1 correctly, so it's just a call to refresh the display as well, I would think. Might go looking for it in the source, but don't hold your breath

[zeno]

There's a small bug in the ubasic interpreter which causes any script whose very first line is a loop-starting statement (eg while or do) to fail at the end of the first interation of the loop. It's caused by an error in the jump_line routine in ubasic.c:

Code: [Select]

static void
638 jump_line(int linenum)
639 {
640   tokenizer_init(program_ptr);
641   while(tokenizer_line_number() != linenum) {
642     tokenizer_next();
643   }
644   /* swallow the CR that would be read next */
645   accept(TOKENIZER_CR);
646
647 }
The problem is in line 645 - if the jump is to line 1 this causes a parse error. line 645 should read:

Code: [Select]

645    if (linenum >1) accept(TOKENIZER_CR);


[Briann]

Lockup problem with 102B
GM102B firmware is what my camera reports when testing in playback mode using disp & funcset.
With the full version of "sx10-102b-0.9.8-783-full_BETA" installed using cardtricks I succeeded causing in a total lockup with write protect on.

To get the camera usable again I had to open the battery compartment to enable use of the camera with the write protect lock off. This is very like I loaded a wrong version for firmware. Help!

[zodiac757]

[fudgey]

"AF/Macro/MF" selector button and "LEFT" are the same on SX110.

Can somebody DISABLE or bind it to an unused button?

I dislike zebra because it kills the grid lines.

The correct place for this is the SX110 porting thread but I see you double posted there already. http://chdk.setepontos.com/index.php/topic,2838.480.html


As for zebra overwriting grid lines, you can avoid that by editing CHDK source file core/gui_osd.c, change
#define ZEBRA_CANONOSD_BORDER_RESTORE   1
to
#define ZEBRA_CANONOSD_BORDER_RESTORE   0
and rebuild.

I use zebra like that on my a570. The downside is that zebra will then require more RAM (when zebra is active), which according to the table in http://chdk.wikia.com/wiki/CHDK/Camera_RAM_memory_usage could cause problems for you since sx110 appears to be one of the models with least available RAM. You can compensate by disabling things like games, curves, calendar, edge overlay and even lua if you can do without lua scripts by editing buildconf.inc, not using icons etc (refer to that memory usage page for more tips).

[zodiac757]

hi fudgey,

Thanks for your answer. I wrote to the SX110 forum too but I think here are more people. I'm just a user of CHDK so I'll wait for somebody in the other topic. (Maybe they are on holiday.)

Regards,
zodiac

[ADamb]

gensigs.sh crashes under WinXP_SP3.
Solution:
replace:

Code: [Select]

for v in $VERSIONS; do
    cat sig_ref_$2_${v}.txt | \
( read line; rom_start=($line) ; \
    while read line; do
    # workaround - multiword read does not work in Windows shell!
    line=($line)
        name=${line[0]}
        addr=${line[1]}
        length=${line[2]}
./gensig sig_ref_$2_${v}.bin ${rom_start} ${name}_${v} $addr ${length:-32}
    done
)
donewith:

Code: [Select]

for v in $VERSIONS; do
( read line; rom_start=($line) ; \
    while read line; do
    # workaround - multiword read does not work in Windows shell!
    line=($line)
        name=${line[0]}
        addr=${line[1]}
        length=${line[2]}
./gensig sig_ref_$2_${v}.bin ${rom_start} ${name}_${v} $addr ${length:-32}
    done
) < sig_ref_$2_${v}.txt
done

[CHEAT:]

I have SX100 with last autobuild 0.9.8-788. There is no redraw in games Connect 4 and Mastermind when orientation sensor accidentally triggers. Sorry for my poor english, I hope you understand me. Can someone post correct report in bugtracker? I think, it's easy to fix. Just like in other two games. Thanks in advance.

[Deformer]

Hello,
I have troubles with the bad pixel removing function on my G11. I installed "g11-100l-0.9.9-909-full_BETA" firmware on the 8Gb SDHC card formatted to contain two partitions.
"Badpixel" file (or "badpixel.txt" with the same result) containing only two coordinates (taken from the RAW file) separated by a comma is in the "A\CHDK" directory.

I tried Bad pixel removal option in both modes (Average, RAWconverter), but with no result. Tested on jpeg files, camera RAWs, CHDK RAWs.

Any solutions maybe?

[fe50]

Hello & welcome, Deformer !

I tried Bad pixel removal option in both modes (Average, RAWconverter), but with no result.

* use the show_bad tool to create the badpixel file --> http://chdk.wikia.com/wiki/CHDK_User_Manual#Bad_pixel_removal
* on a multi partitioned card store the badpixel file on the 2nd ("big" / data) partition
* store the file in the \CHDK subfolder on this partition

[Deformer]

2 fe50:
Thanks a lot! Finally working! I guess, there were wrong dead/hot pixel coordinates.
...When I tried previous 'show_bad' version, it didn't understand G11 RAWs, but everything is OK now.

And some additional info, maybe it can be useful for the development team:
-CHDK menu dissapears often, without any reason - tested with different combinations of CHDK features - Histogram, Zebra modes - on, or everything connected with the overlay off. Appears again if you press up/down buttons.
-"Flashlight" mode isn't working.
-When you turn the screen forward (autoportrait mode? ), the OSD text become mirrored.

[kaw]

Hi, everybody! The problem with the SX110IS, when shooting in raw. Source files crw obtained 0kb. I had to roll back to version 0.9.9 953, on which everything is normal.
P.S. Sorry for my english.

[reyalp]

Hi, everybody! The problem with the SX110IS, when shooting in raw. Source files crw obtained 0kb. I had to roll back to version 0.9.9 953, on which everything is normal.
P.S. Sorry for my english.

See here: http://chdk.setepontos.com/index.php?topic=5600.0