S95 Porting Thread

waldo

The DrvExp patch is not implemented on the S95 and this may explain that effect. I'll add that to the list.

Fernando

thanx a lot!

we are in version 3 so far, am I right?

waldo

Version 4 is the current one.
https://chdk.setepontos.com/d/5641/111

You can always get the current version here:
https://chdk.setepontos.com/d/5641/1

Fernando

I think it won't go lower than 80 ISO and faster than 1/1600... anyone? maybe I'm doing something wrong...

1/10000 looks exactly the same as 1/1600 and lowering the ISO to 10 does nothing...

using last version (4)

it works (it overrides) but it won't exceed normal camera limits (1/1600-15sec, ISO80, etc)...
I really hope this can be solved 🙁

emutier

Fernando
I think it won't go lower than 80 ISO and faster than 1/2000... anyone? maybe I'm doing something wrong...

1/10000 looks exactly the same as 1/2000 and lowering the ISO to 10 does nothing...

using last version (4)

ISO allways was a problem, I got some strange ISOs with my A710 back in the days, but it is wasn't really working at all. On no cam, as far as I know. Some cams support ISO 50 or even ISO 16 and other settings below 80, but it's "expectable" that ISO doesn't work for the S95.

shutterspeed-override isn't workin for me below 1/1600 either (over 15sec no problems).

further question:
in a manual focusing during video script the following lines have no effect - ideas anyone?

if is_key "up" then set_focus 120
if is_key "set" then set_focus 600
if is_key "down" then set_focus 2000

jbvideo

I just found out about CHDK, and have not tried it yet. I am just curious if anyone has tried the USB remote function to trigger a shot on the S95, as described here: http://chdk.wikia.com/wiki/USB_Remote_Cable

If so, what is the delay time between the signal and the camera shutter? Also, how consistent is the timing?

Microfunguy

jbvideo
what is the delay time between the signal and the camera shutter?

It is very variable.

Also, how consistent is the timing?

Very inconsistent if you trigger on USB going high, very consistent if you trigger on USB going low.

It varies, but photo taken about 20 msec after USB goes low with a repeatability of typically 1/5000 sec.

David

jbvideo

> photo taken about 20 msec after USB goes low with a repeatability of typically 1/5000 sec.
Wow! better than I expected. Thanks for the info.

mr.burns

Microfunguy

mr.burns
I am still alive

and your name lives on in the SDM source code !

Hi Microfunguy, my name lives in the SDM source code? Thanks, but what I did to get this honor?

Microfunguy

mr.burns
what I did to get this honor?

"Mr_Burns fix for G9 and other cameras that failed to autostart script"

mr.burns

Microfunguy

mr.burns
what I did to get this honor?

"Mr_Burns fix for G9 and other cameras that failed to autostart script"

Hi Microfunguy, aaahhh yes I remember now. Thanks for eternalize me, it's a great honor to me!

waldo

A new version is posted here:
https://chdk.setepontos.com/d/5641/1

Changes in this version:
Fixed crashing bug when displaying CCD temp
Disabled Fast Video Control in menu
Added support for fast shutter override
Added support for 1.00H firmware

hqasem

Waldo- Thanks for your hardwork. I use a script to remote trigger the S95, and it works great.

Compared to the S90, I noticed couple of things:
1) It takes a little longer to load CHDK on the S95. On the S90, the splash screen appeared almost instantly. On the S95, it takes about 5 seconds.
2) The splash screen colors are a little off - they appear as gray, white and thin orange rim. No red.

Both minor, and many many thanks once again.

Hussam

reyalp

hqasem
Waldo- Thanks for your hardwork. I use a script to remote trigger the S95, and it works great.

Compared to the S90, I noticed couple of things:
1) It takes a little longer to load CHDK on the S95. On the S90, the splash screen appeared almost instantly. On the S95, it takes about 5 seconds.

This probably means that the core_spytask_can_start isn't properly implemented yet.

2) The splash screen colors are a little off - they appear as gray, white and thin orange rim. No red.

This means CAM_BITMAP_PALETTE needs to be adjusted. This is easiest to do if the person doing the adjusting already has a camera with correct colors, but trying the existing values might come up with something close.

waldo

reyalp
This means CAM_BITMAP_PALETTE needs to be adjusted. This is easiest to do if the person doing the adjusting already has a camera with correct colors, but trying the existing values might come up with something close.

The S95 has a very limited palette (only 1 shade of red, for example), but I can make it look better than it does now.

This probably means that the core_spytask_can_start isn't properly implemented yet.

I can see from the code how that would explain the slow startup, but I still don't see how this is supposed to work.

The call chain for setting spytask_can_start=1, which would kick things off, is like this:

deleteHook()
core_hook_task_delete()
core_spytask_can_start()

But deleteHook is not called from anywhere. I checked the source for other cameras and they don't call it either. Am I missing something?

reyalp

waldo

But deleteHook is not called from anywhere. I checked the source for other cameras and they don't call it either. Am I missing something?

In dryos cameras, core_spytask_can_start() is called from boot.c, in init_file_modules_task. Even if you don't have FAT32 support, you should implement the initial part of this.

In general, grepping the tree for things like this can help you find your way around.

On the palette, the main concern is that all the important OSD elements are readable. Everything else is cosmetic 😀

waldo

A new version is available here:
https://chdk.setepontos.com/d/5641/1

Changes in version 6:

improved screen drawing updates
improved on previous fix for script-based zooming
improved color palette
shortened time to boot CHDK
optical zoom in movie mode is now working (but must turn off video digital zoom first (not a big loss !)
removed video bitrate menu option

This update is only for the 1.00E firmware. I will wait for reports from users of the 1.00H version before making any changes to the 1.00H version.

emutier

thank you so much waldo, zooming in videos is working great now! zooming+refocus = enhanced movie options 😉

(now someone has to find a way to get manual focus and manual shutter/ISO working on the S95.. )

scstudios

Great work on V6. The speed that it starts is WAY faster!! This is a huge deal to me as I have missed so many shots waiting for the bootup. Thanks a bunch!!

hqasem

Waldo- Thanks again for your efforts.

1) I don't see any improvement in boot time - about 5 seconds still. I have the 1.00E firmware.
2) The splash screen is much better - thank you. I noticed, however, that I cannot read the word "ALT" when I'm in play-mode (white-on-white?)

Cheers. -Hussam

« Previous Page Next Page »