S95 Porting Thread

waldo

Gioca
2. I set an aperture value of 2.06, I see that the value regularly appear in the screen upper left angle. (AV:2.06). But the camera follow the standard camera setting. In fact I see that the real AV value is the value of the standard setting in the camera. I see it because I display the Real Aperture with "OSD_Parameters-Miscellaneous_Value-Show_Real_Aperture" Menu, and the Real displayed aperture value isn't the override value, but the standard camera value. I try in AV and in M modes. I use v11 firmware.

The Av overrides work for me, both via ubasic and via the menus. You should ignore the camera's information display after the picture is taken and look at the picture brightness.

launcher20

Hi, can I use now RAW with 16:9 or only 4:3 ? In original firmware only 4:3 🙁 !

Great work !

Thanks !

waldo

launcher20
Hi, can I use now RAW with 16:9 or only 4:3 ? In original firmware only 4:3 🙁 !

Great work !

Thanks !

Raw is always 3744 x 2784.

emutier

launcher20
Hi, can I use now RAW with 16:9 or only 4:3 ? In original firmware only 4:3 🙁 !

-> Aspect Ratio in RAW
you can choose an aspect ratio if you shoot RAW, but only if you choose RAW+JPEG rather than just RAW. It's weird. And the jpg gets cropped, but the RAW gets a "crop square" thing applied to it just like you used the crop tool in dpp (all the full size data is still there). I know it works with dpp, not sure about Lightroom.

from 3. http://forums.dpreview.com/forums/read.asp?forum=1010&message=37321753

launcher20

Thanx for answer ! It works also in LR !!

Regards

polle44

Thanks for this wonderfull chdk.
I realy like the manual zoom.
But there is one thing I don´t understand: When pressing the power button to start the S95, I always see the last pic I´ve taken. But I want to start in shooting mode, not in playback mode?!
Camera reset and CHDK reset didn´t help.
Or is there any option in CHDK to deaktivate this "feature"?
I couldn´t find one.
Thanks for helping in advance!

reyalp

polle44
Or is there any option in CHDK to deaktivate this "feature"?
I couldn´t find one.
Thanks for helping in advance!

You should be able to hold the power button until the camera starts in shooting mode.

This isn't an intentional feature, it's an unavoidable side effect of the way CHDK starts. By the time CHDK is started, it doesn't know whether you pressed the power or play button.

polle44

reyalp

polle44
Or is there any option in CHDK to deaktivate this "feature"?
I couldn´t find one.
Thanks for helping in advance!

You should be able to hold the power button until the camera starts in shooting mode.

This isn't an intentional feature, it's an unavoidable side effect of the way CHDK starts. By the time CHDK is started, it doesn't know whether you pressed the power or play button.

Thanks, longer pressing the power button is the solution. That´s why the effect didn´t happen when it was cold outside and I was pressing the button with much more power...

Microfunguy

@Waldo

Can you confirm the address for malloc() in both 100E and 100H.

I am having great difficulty porting this to SDM.

If I display the first characters of the loaded script, the tester tells me they are constantly changing !

Difficult to see why that would be.

waldo

Microfunguy
@Waldo

Can you confirm the address for malloc() in both 100E and 100H.

I am having great difficulty porting this to SDM.

If I display the first characters of the loaded script, the tester tells me they are constantly changing !

Difficult to see why that would be.

On 100E, features like the logo, Show Memory Info, grids and zebra all work and all of those use malloc.

Microfunguy

waldo
On 100E, features like the logo, Show Memory Info, grids and zebra all work and all of those use malloc.

Yes, but as I asked, what is the address of the 'malloc()' function.

I don't know if the source-code I have is correct as it has not been officially uploaded yet.

waldo

Microfunguy

Microfunguy
Can you confirm the address for malloc() in both 100E and 100H.

waldo
On 100E, features like the logo, Show Memory Info, grids and zebra all work and all of those use malloc.

Yes, but as I asked, what is the address of the 'malloc()' function.

I don't know if the source-code I have is correct as it has not been officially uploaded yet.

I'm sorry, I misunderstood your meaning of "confirm".

Here is a link to the source I am using:
https://chdk.setepontos.com/d/5641/1

theworstnameever

waldo: just want to let you know -- thanks!

Microfunguy

waldo

Here is a link to the source I am using:

Thanks.

That is the malloc() address that I am using.

The value of the pointer to script buffer changes from a correct initial value (for the script loaded from a file) to a value far lower in memory that points to constantly changing values.

Presumably, the only other location it should be pointing to is the default built-in script.

Dificult to see how that can be incorrect.

Also, the code is common to all cameras and works fine on my A620.

Gioca

reyalp

ranom

reyalp
Keep in mind that not everything is the same on every camera. Even if the wiki is correct for some particular camera (which you should not assume!), only experiment can verify whether it is correct on your camera.

Thanks, I'll remember that from now on. I guess its just best to take a note of the used values, and edit the exif when you get home.

Once you've characterized how things work on your particular camera, you can rely on the exif fields you've determined to be reliable 😉

How about this issue ? It's very useful to have exif data, in order to evaluate CHDK experiments

waldo

Gioca

reyalp

ranom

reyalp
Keep in mind that not everything is the same on every camera. Even if the wiki is correct for some particular camera (which you should not assume!), only experiment can verify whether it is correct on your camera.

Thanks, I'll remember that from now on. I guess its just best to take a note of the used values, and edit the exif when you get home.

Once you've characterized how things work on your particular camera, you can rely on the exif fields you've determined to be reliable 😉

How about this issue ? It's very useful to have exif data, in order to evaluate CHDK experiments

Some cameras store the exposure override values in EXIF and some do not. The S95 is one that does not.

Gioca

waldo

Gioca

reyalp

ranom

reyalp
Keep in mind that not everything is the same on every camera. Even if the wiki is correct for some particular camera (which you should not assume!), only experiment can verify whether it is correct on your camera.

Thanks, I'll remember that from now on. I guess its just best to take a note of the used values, and edit the exif when you get home.

Once you've characterized how things work on your particular camera, you can rely on the exif fields you've determined to be reliable 😉

How about this issue ? It's very useful to have exif data, in order to evaluate CHDK experiments

Some cameras store the exposure override values in EXIF and some do not. The S95 is one that does not.

So, no expectation to have this issue solved ? and what about to write the override value in a separate file ?

fe50

waldo
Some cameras store the exposure override values in EXIF and some do not. The S95 is one that does not.

Doesn't the S95 store the real values in the EXIF Makernotes, as other Powershots do 🙁 ?

@Gioca: you may have a look to the complete EXIF data (including the Canon makernotes) with the ExifTool...

Microfunguy

Microfunguy
@Waldo
I am having great difficulty porting this to SDM.

This took me to the verge of madness ... !

On power-up, the default and saved CFG values are loaded.
Some CFG values have an associated function to load a script or reader file.
In that code, Canon firmware function strrchr() is used.

Unfortunately, the address in CHDK is incorrect.
It should be :-

NHSTUB(strrchr,0xFF8140D😎

for both 100E and 100H.

I think you will find CHDK grids do not work.

David

waldo

OK, I'll look into that. The grids seem fine on my camera, tho.

« Previous Page Next Page »