S95 Porting Thread

waldo

Before I release new versions, there is something that I have to remember to take out of my personal builds so it doesn't confuse people. I prefer that the script title only shows in ALT mode when the shutter button is pressed halfway. I think this makes for less clutter on the screen but it is still very easy to check which script is loaded. When running a script, it looks the same as before.

Should I leave the "script title on half press" feature in on the next version? It's easy enough to take out again later.

Hollywood

Waldo, is there anything you can do to override the Miniature effect in picture mode from 4:3 to 16:9. In video mode miniature effect is 16:9 but in picture mode 4:3.

Thanks.

P.S. I always have to reload the firmware to start CHDK it doesn't autostart, any suggestions? I have CHDK from S90 your latest build (Diskboot & PS.F12) and the vers.req file on my SD card.

Thanks again with all your efforts.

Cheers.

waldo

Hollywood
Waldo, is there anything you can do to override the Miniature effect in picture mode from 4:3 to 16:9. In video mode miniature effect is 16:9 but in picture mode 4:3.

That seems to be hard-coded into the Miniature effect. I guess a workaround would be to crop to 16:9 on your PC after taking the picture.

Hollywood
P.S. I always have to reload the firmware to start CHDK it doesn't autostart, any suggestions? I have CHDK from S90 your latest build (Diskboot & PS.F12) and the vers.req file on my SD card.

If you are using a card of 4 GB or less with 1 partition, it should auto-boot.
If using multiple partitions, you will have to wait for that feature (but you will not have to wait very long) 😀

scstudios

waldo

scstudios
I tried the zoom script again with version 3. It still hangs the camera.

Must be more of a intermittant problem than I thought. It seems to work well for me.

I have two S95s due to 3d shooting. I cant get to 5 starts without it hanging. It is intermittent. I have long sleep commands all over thinking that may be it, but its not. I also read that you have to set zoom speed or it will hang. Even with all this, it hangs about 1 in 5 starts. This script is always going to be my startup because I am shooting at the 35mm focal. Even the prior versions hung about that often.

@title Zoomit
sleep 2000
set_zoom_speed 100
sleep 2000
set_zoom 2
sleep 2000
exit_alt
end

scstudios

Not really sure what is going on. If I sleep for 2000, the zoom script fails. If I sleep for 1000 it works. How could sleeping 1 second longer make it lock up. This is v3.

Hollywood

Thanks for the response Waldo...cheers.

asm1989

m4mmm, do iso override works with flash?

althio

With Av/Tv/ISO overrides, is CHDK correctly writing the values in EXIF-MakerNotes?

I can set the overrides.
I am fairly convinced the overrides are effective (very long time exposure & very short time exposure are OK, at the very least).
But I cannot found the overridden values in the Exif-Makernotes.

Fernando

AFAIK, chdk do not write the overriden values to the EXiF.

I was going to suggest that it would be great if it could optionally write a text file containing the real values used incl. overrides.
The text file should be named filenumber.txt
Now it is officially suggested 😀

althio

Fernando
AFAIK, chdk do not write the overriden values to the EXiF.

It is reported at several places in this forum and in the wiki at the FAQ page.

[url=http://chdk.wikia.com/wiki/FAQ#Q._I.27ve_shot_some_RAW_pictures._How_do_I_process_them.3F]FAQ page[/url] wrote:If you are using some of the new builds of CHDK with features like shutter-speed and aperture overrides then the original JPG EXIF header [...] may not reflect these new values that are outside of the normal bounds of your Powershot's EXIF information. A small utility was created that allows you to process your JPG files to update appropriate EXIF fields with these non-standard CHDK override shutter-speed, aperture, and ISO values. You can find the latest version of this utility at the new CHDK Forum [...]

As I understand it: overridden values can be written in the MakerNote section of EXIF data.
And you can copy them at the intended "standard" position in the EXIF header (default section). Manually with exiftool or by a small utility.

But right now, when I read this Exif-Makernote section, I find the values close to camera settings, not the CHDK-overridden and actual values.

waldo

Here is a new version.

Changes:
* Added work-around for script zooming issue (side-effect: sometimes takes longer to zoom)
* Added support for multiple partitions (I do not use multiple partitions so I will let others test)

~~Here's the link:~~

See: https://chdk.setepontos.com/d/5641/1

asm1989

Thanks waldo, can you post source too please

Bernd R

>Changes:
> * Added work-around for script zooming issue (side-effect: sometimes takes longer to zoom)
> * Added support for multiple partitions (I do not use multiple partitions so I will let others test)

I have a 8 GB card and i like boot chdk in future.if this work too on a IXUS 1000 HS, i like test multiple partitions if that can work on Ixus 1000 too.firmware addresses seem very simular.

I think i need create a small boot partition of size 30 megabyte or so and a second partition that contain the rest and store image

Hollywood

Thanks again Waldo for the update, always appreciated buddy.

Cheers.

Hollywood

I'm still having a slight problem with the autoboot on a 3.72Gb card. I can get CHDK to boot up manually by hitting the preview button but after when I shut down and restart, CHDK does not autostart.

I have the card in lock position and the latest build of Waldo's PS.12 and diskboot and the S90 CHDK files. When I power on/off I get a memory card locked message. Never had this issue with my S90 could it be a CHDK glitch?

Any info appreciated, thanks. Cheers.

waldo

Hollywood
I have the card in lock position and the latest build of Waldo's PS.12 and diskboot and the S90 CHDK files. When I power on/off I get a memory card locked message. Never had this issue with my S90 could it be a CHDK glitch?

Autoboot works consistently for me after hundreds of boots. Are you saying that CHDK does not attempt to autoboot at all? If so, maybe your card has not been properly prepared for booting. There is a Wiki page describing how to do that.

schwarms

waldo, I am also using your port every day - thank you for the great work 😀!
On my side the autoboot works, I am using it with 2 partitions on a 8GB SD card (there is no problem at all regarding to the auto start on my side).

But I have one little question, maybe I am doing something wrong: when I enable the "R G B" or the "BLENDED" histogram, it comes not colored like here: http://chdk.wikia.com/wiki/CHDK_firmware_usage, so the color-channels are not visible at all. Do I have to set up something on my side or is this maybe a S95-specific issue which can not be solved?

Thanks for your help!

Pixbo

Hello, one question...
Currently the S95, when using RAW+JPG, ignores the custom color setting. For example,
if you define sharpness -2 and shoot JPG only, you get sharpness -2.
If you shoot RAW+JPG, you get the default sharpness 0.
Can CHDK store the JPG that comes with the RAW in RAW+JPG mode with the user defined
sharpness setting?

Thanks!

Hollywood

Thanks Waldo, I will use cardtricks again to set up a bootfile. Maybe It got corrupted.

Cheers.

windjammer

Hello !

I have also a Canon S95 and iam very interested that chdk will run on my cam in future.

But my cam have also firmware 1.00H.
So I try to dump the firware with cardtricks and udumper but it don't woks. The tutorial with cbasic udumper say me nothing, but I will learn it. Perhaps someone can help me.

Thank you !

Greetings

« Previous Page Next Page »