SX40HS porting thread - page 10 - DryOS Development - CHDK Forum supplierdeeply

SX40HS porting thread

  • 258 Replies
  • 89830 Views
Re: SX40HS porting thread
« Reply #90 on: 14 / February / 2012, 13:15:13 »
Advertisements


I've managed to replicate this on my SX40; but only if I set the ISO override to a value above 930 (market ISO 1250).

I tried 1/4000 @ ISO 400 and don't have the problem - can you confirm that this crashes on your camera?

Working on a fix; but it may involve limiting the max override ISO in HQ burst mode.

Phil.
[/quote]


Hi Phil,

1/4000 @ ISO 400 didn't crash my camera, so I must have been mistaken.  Further testing showed that the crash happens somewhere between Real ISO 925 - 939.  Market ISO 1250, so, same as you.

Dave

Re: SX40HS porting thread
« Reply #91 on: 14 / February / 2012, 16:25:37 »
Phil, yes I can shoot JPEG with CHDK loaded.

I found a few things.
The attached version should fix the histogram.
Not sure about the badpixel.bin creation.

If the badpixel creation still fails try creating an empty badpixel.bin file manually in the CHDK directory on the SD card. Then see if you can shoot DNG files. It's also best to set the option to save the raw/dng files in the same directory as the jpeg files.

Phil.

Hi Phil
I'm newbie to Canon, CHDK, and this forum... so first I would like to thank you all for everything you've done\still doing  :)

I downloaded your built for my camera's firmware (1.00i)... May I ask how far are we from a beta version? also I would like to offer my help in anything you need for making a beta or final version.

My report: most of the features (I haven't tried all) of CHDK are working except:

1) the OSD :s
There’s a problem in the ODS display that causes it to disappear in the following scenario:
Take a picture, then erase it with the erase button. When you get back to record mode the OSD is gone.
The fastest way to get it back is to go to play mode, then again to record mode.

Also the OSD flickers sometimes and Canon's default histogram appear on top of the CHDK OSD.
But this might be the normal behavior of CHDK since after all... it's a hack :)

2) both games and curves are not available

3) both using the screen as flashlight, and using the zoom lever as a manual focus didn't work.

4) Raw in-camera developing is not working. Only the top section of the jpg is developed with the lower part actually captured live from the lens... resulting in wired looking jpgs :)

5) I used an USB charger to deliver 5v current to be used as a remote control trigger. The camera does detect the input... but this feature is crippled when 'synchable remote' is enabled because:
- When the camera is set on continues mode... it keeps taking picturessss no matter what you do.... I mean whither you cut the electric current or not.
- When the camera is set on normal mode. The remote function works but the screen goes black as soon as the camera locks focus... and it remains black till the shot is taken. Tried "LCD always on", didn't help.

6) Once by mistake I sat the ISO at a high number (around 7000 real iso) which made the camera goes mad... freeze for a couple of seconds... and then shutdown... haven't tried it again to verify it :)

Regarding the problem posted by davemt, I tried it and I confirm the highest possible ISO in burst mode is 930. In general, I noticed that the camera needs longer time in higher ISOs, so I bet this's the reason behind the error. I mean since *speed* is essential in burst mode, higher ISOs must be disabled or unavoidably cause problems.

I'm considering writing a script to switch the camera to record mode and add it to the autostart so I don't have to long-press the power button... what do you think?

Now it is true that I'm a newbie but I have a background in programming Java Script, ActionScript, PHP, and Visual Basic... I'm not professional in any of them though. But If there's anything I can help with just let me know.
Beauty is in the eye of the beholder

my eye: Canon PowerShot SX40 HS :)

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: SX40HS porting thread
« Reply #92 on: 14 / February / 2012, 17:25:27 »
I downloaded your built for my camera's firmware (1.00i)... May I ask how far are we from a beta version? also I would like to offer my help in anything you need for making a beta or final version.

The BETA version is available from the autobuild server - http://mighty-hoernsche.de/

Quote
1) the OSD :s
There’s a problem in the ODS display that causes it to disappear in the following scenario:
Take a picture, then erase it with the erase button. When you get back to record mode the OSD is gone.
The fastest way to get it back is to go to play mode, then again to record mode.

I'll look into this.

Quote
Also the OSD flickers sometimes and Canon's default histogram appear on top of the CHDK OSD.
But this might be the normal behavior of CHDK since after all... it's a hack :)

That's normal.

Quote
2) both games and curves are not available

3) both using the screen as flashlight, and using the zoom lever as a manual focus didn't work.

4) Raw in-camera developing is not working. Only the top section of the jpg is developed with the lower part actually captured live from the lens... resulting in wired looking jpgs :)

5) I used an USB charger to deliver 5v current to be used as a remote control trigger. The camera does detect the input... but this feature is crippled when 'synchable remote' is enabled because:
- When the camera is set on continues mode... it keeps taking picturessss no matter what you do.... I mean whither you cut the electric current or not.
- When the camera is set on normal mode. The remote function works but the screen goes black as soon as the camera locks focus... and it remains black till the shot is taken. Tried "LCD always on", didn't help.

Try the latest autobuild version.
Note that 'curves' is only available on old cameras with 10 bit sensors.

Quote
6) Once by mistake I sat the ISO at a high number (around 7000 real iso) which made the camera goes mad... freeze for a couple of seconds... and then shutdown... haven't tried it again to verify it :)

I'll test this, it may need to have an upper limit set on the ISO override.

Quote
I'm considering writing a script to switch the camera to record mode and add it to the autostart so I don't have to long-press the power button... what do you think?

The SX40 is slow to start; not much that can be done about it.
CHDK defaults to starting in playback mode as a safety precaution in case the camera is accidentally started when in a case, which might damage the lens.

An autostart script probably won't save you much time, you will need a delay to allow the camera to finish powering up before switching modes. If you try it let us know the results.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

Re: SX40HS porting thread
« Reply #93 on: 14 / February / 2012, 18:40:58 »
The BETA version is available from the autobuild server - http://mighty-hoernsche.de/
Sorry... I didn't notice it before because I used to check the camera's main page for updates (http://chdk.wikia.com/wiki/SX40) which state that only alpha versions are available.

I downloaded the latest version and tried it. My updated report:
1) the OSD disappearing problem is solved.
2) Games are working
3) both the screen flashlight, and using the zoom lever as a manual focus are working
4) raw developing still down
5) and still facing the same problems with remote control when 'synchable remote' is enabled


The SX40 is slow to start; not much that can be done about it.
CHDK defaults to starting in playback mode as a safety precaution in case the camera is accidentally started when in a case, which might damage the lens.

An autostart script probably won't save you much time, you will need a delay to allow the camera to finish powering up before switching modes. If you try it let us know the results.
Thanx for the tip... yea it makes sense and I think I won't bother with the script

Thanx
Beauty is in the eye of the beholder

my eye: Canon PowerShot SX40 HS :)


Re: SX40HS porting thread
« Reply #94 on: 14 / February / 2012, 18:49:32 »
5) I used an USB charger to deliver 5v current to be used as a remote control trigger. The camera does detect the input... but this feature is crippled when 'synchable remote' is enabled because:
- When the camera is set on continues mode... it keeps taking picturessss no matter what you do.... I mean whither you cut the electric current or not.
Strange.  Does it stop if you cut the current and then re-apply it ?

Quote
- When the camera is set on normal mode. The remote function works but the screen goes black as soon as the camera locks focus... and it remains black till the shot is taken. Tried "LCD always on", didn't help.
This is to be expected. You have selected "syncable" which means that CHDK takes the camera as close as it can to the point just before where the shutter actually fires and then holds it there.  Normal camera operations stop while the sync logic waits for you to release the trigger and fire the shot. The intent is to minimize the delay from trigger release to actual shutter release.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: SX40HS porting thread
« Reply #95 on: 14 / February / 2012, 18:59:16 »
Sorry... I didn't notice it before because I used to check the camera's main page for updates (http://chdk.wikia.com/wiki/SX40) which state that only alpha versions are available.

Wiki page updated.

Quote
4) raw developing still down

Can you provide more details of the steps that lead to the problem.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

Re: SX40HS porting thread
« Reply #96 on: 14 / February / 2012, 19:24:37 »
Quote from: waterwingz
Strange.  Does it stop if you cut the current and then re-apply it ?
No... everything works fine when 'synchable remote' is disabled. But I need it because the USB charger got *cheap* slide switch and the 0.5 second thing is just not practical for it.
When 'synchable remote' is enabled:
- In continues mode: as soon as a current is applied the camera start firing away as if it's a machine gun and there's nothing I can do to break the cycle but to turn the camera off.
- In normal mode: (aside from the black screen) it works... I apply the current and the camera lock focus and stand by. When I cut the current it shots.

Quote from: waterwingz
This is to be expected. You have selected "syncable" which means that CHDK takes the camera as close as it can to the point just before where the shutter actually fires and then holds it there.  Normal camera operations stop while the sync logic waits for you to release the trigger and fire the shot. The intent is to minimize the delay from trigger release to actual shutter release.
So any ideas on how I can get around this? customized script maybe?


Quote from: Phil
Can you provide more details of the steps that lead to the problem.
1) I click on "raw develop"
2) select raw file
3) exit the menu by pressing ALT
4) shot
in the old alpha version only the top section of the jpg is developed. In this version, nothing happens at I all when I press the shutter button. The camera just takes a new photo.
Beauty is in the eye of the beholder

my eye: Canon PowerShot SX40 HS :)

Re: SX40HS porting thread
« Reply #97 on: 14 / February / 2012, 19:54:10 »
So any ideas on how I can get around this? customized script maybe?
Going the scripting route might be the easiest way. 

Otherwise you could switch to the dev / unstable version.  The USB remote code has been completely re-written.   If you are not comfortable compiling your own code there is rumored to be an autobuild version about to be availabe. 
« Last Edit: 15 / February / 2012, 07:36:24 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: SX40HS porting thread
« Reply #98 on: 15 / February / 2012, 04:08:08 »
Revision 1671 (release-1.0) and 1672 (trunk) should fix the 'Raw develop' issue and also limits the max ISO override in HQ burst mode to prevent the crash.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

Re: SX40HS porting thread
« Reply #99 on: 15 / February / 2012, 08:59:20 »
Quote from: waterwingz
Otherwise you could switch to the dev / unstable version.  The USB remote code has been completely re-written.   If you are not comfortable compiling your own code there is rumored to be an autobuild version about to be availabe.
Honestly I'm still totally ignorant regarding writing scripts. I had my camera for only about a month now and currently I'm busy in my post-graduate exams. So I won't have free time for another 3 weeks. Hopefully by that time the new version would be ready.

Quote from: philmoz
Revision 1671 (release-1.0) and 1672 (trunk) should fix the 'Raw develop' issue and also limits the max ISO override in HQ burst mode to prevent the crash.
thanx
Beauty is in the eye of the beholder

my eye: Canon PowerShot SX40 HS :)

 

Related Topics