SX110IS - howto start porting

[ewavr]

here is what i do (an example):

(auto-iso-shift must be enabled in the canon-options and alt-key must be the print-button)

I am sitting in a dark room. Boot the cam WITHOUT CHDK. P-Mode. Iso is manually set to 80.
I am holding the shutter half-pressed. it shows:
   ISO 80 ; exposure 1/5
The print button glows blue. I press it. Now the settings changed to recommended auto-settings
   ISO 320^ ; exposure 1/20

now i boot the cam WITH CHDK. (same room. same settings)
I am holding the shutter half-pressed. it shows:
   ISO 80 ; exposure 1/5
The print button glows blue. I press it. and nothing changes. neither with a short press nor a long press.

what are you doing (or rather why does it work as expected with your cam)?

This is well-known bug for cameras with autoISO shift function.
At present  there is only one medicine - change <alt> key to other key (if CHDK for SX110 can do this).

[axu89]

This is well-known bug for cameras with autoISO shift function.
At present  there is only one medicine - change <alt> key to other key (if CHDK for SX110 can do this).

Yeah.. I use the face button, its mostly useless for me. If I want the face focusing, its the first selection in SX110's menu after all.

[lucmovel]

I use the face button, too. It's in a much more convenient position and my print button is too hard to press.

[xiaoxiao0738]

After using the CHDK camera sx110, camera generated file suffix called CRW how to open it!
I would like to ask, to how to open?

[xiaoxiao0738]

After using the CHDK camera sx110, camera called CRW suffix generated document, with dng4ps2 and FastStone Image Viewer can not open the browser!
I would like to ask, to how to open?

[chdkj]

@Hyst, it is not in my intent to annoy you  . As said before, I'm not aware of all functions. Thought that we were talking about Custom ISO Shift all the the time --> Custom ISO Shift works with SX110 (and I like this feature...).
Auto ISO Shift is a built-in function of SX110 to change exposure related settings to new settings suggested by cam itself --> after you pressed the lightning blue print button (with Auto ISO Shift enabled in Canon menu). And up to now: with loaded CHDK nothing will happen after the print button press --> that did you mean.

EWAVR had a nice short explanation and a workaround http://chdk.setepontos.com/index.php/topic,2838.msg33121.html#msg33121. It works.

Greetings!

[chdkj]

perhaps ewavr or fudgey can take a look at the getbattery stuff in the dumps. if they cant find the function, nobody can

Oh Oh...
GetBatteryTemperature is implemented in SX110 as SX10 or SX100 does. Looks very similar (not to say identical). CHDK calls it simply via _GetBatteryTemperature and linked address in stubs_min.S.
Should working out of the box...

Not working MD scripts and corrupted Zebra is more annoying. Could it be that both are somehow related to each other? Wrong memcpy, wrong/unexpected buffer content?

@EWAVR or fudgey: may I ask you to have a look at this problem, please?


Greetings.

[chdkj]

This is well-known bug for cameras with autoISO shift function.
At present  there is only one medicine - change <alt> key to other key (if CHDK for SX110 can do this).

Thank you. Short and painless...
Change <ALT>-key works on SX110 and then Auto-ISO-Shift will work.

[reyalp]

Not working MD scripts and corrupted Zebra is more annoying. Could it be that both are somehow related to each other? Wrong memcpy, wrong/unexpected buffer content?

Wrong live view buffer, most likely. You can write the live view buffer to a file and examine it on PC. You can also watch the address and see if it looks reasonable.

If live view is wrong, histogram will also be wrong. If the camera has built in histogram, you can compare (there will be some difference, but it should be roughly the same shape)

[reyalp]

After using the CHDK camera sx110, camera called CRW suffix generated document, with dng4ps2 and FastStone Image Viewer can not open the browser!
I would like to ask, to how to open?

Currently few programs understand CHDK raw from 12 bit cameras like the sx110. If you look back in this thread, you may find something. You can also try dng instead.

[Hyst]

@Hyst, it is not in my intent to annoy you  .

don't worry... 

This is well-known bug for cameras with autoISO shift function.
At present  there is only one medicine - change <alt> key to other key (if CHDK for SX110 can do this).

good to know, thank you!


---
I don't know if it is a bug or, if i'm doing something wrong, but: what is it about the "flashlight" function (in misc. options). I enable it, but nothing happens.


greetings

[ewavr]

I don't know if it is a bug or, if i'm doing something wrong, but: what is it about the "flashlight" function (in misc. options). I enable it, but nothing happens.

This is a bug - "flashlight" function is only for cameras with rotating/swivel display.

[Obihoernchen]

http://chdk.wikia.com/wiki/SX110IS#Known_bugs updated...

Is there a way to check the Histogram without build in function. Maybe with PC?

[axu89]

Have you guys actually tried histogram in "Always" mode? It shows the exact same pattern most of the time (no matter where you point the camera) with random flicks of the "real" histogram. Its like the zebra-mode, random flicks of the real pattern. I believe these things are somehow connected. Ok, Im just guessing here, but maybe the MD keeps shooting because it sees this same "unstable" picture as the histogram when its in the always mode and shoot button isnt pressed. Forgive me if im totally wrong, I really dont know.

Thou.. when you press shoot button to half (having histogram always or shoot), the histogram starts working properly but zebra wont.

[chdkj]

Wrong live view buffer, most likely. You can write the live view buffer to a file and examine it on PC. You can also watch the address and see if it looks reasonable.

If live view is wrong, histogram will also be wrong. If the camera has built in histogram, you can compare (there will be some difference, but it should be roughly the same shape)

Thank you, Reyalp. Will check this in the next couple of days.

I've marked vid_get_viewport_live_fb() as "questionable" in a early stage of porting already but lost it of my focus. Will have a closer look on it...
Regards.