Chdk for SX130 IS ?

  • 1094 Replies
  • 178334 Views
*

Offline quid

  • **
  • 67
  • SX130IS
  • Publish
    Re: Chdk for SX130 IS ?
    « Reply #100 on: 15 / January / 2011, 15:45:04 »
    Advertisements
    Two more questions:
    - Do you start camera in playback mode and then switch to shooting mode, or switch between playback and shooting mode before trying to take a picture?
    - Do you have enabled Edge Overlay and/or Zebra?

    I've managed to crash camera with DNG enabled when I started camera in playback mode with Edge overlay enabled.

    *

    Offline quid

    • **
    • 67
    • SX130IS
  • Publish
    Re: Chdk for SX130 IS ?
    « Reply #101 on: 15 / January / 2011, 16:14:51 »
    Visible changes in new version:
    - Bracketing now works in custom timer mode
    - Better default colors
    - Jogdial is suspended in ALT mode (implemented JogDial_task_my)
    - Create badpixel.bin works correctly now



  • Publish
    Re: Chdk for SX130 IS ?
    « Reply #102 on: 16 / January / 2011, 05:01:01 »
    I can see, that now histogram is coloured, before it was only 'black or white'. Thx!
    if (2*b || !2*b) {
        cout<<question
    }

    Compile error: poor Yorick

  • Publish
    Re: Chdk for SX130 IS ?
    « Reply #103 on: 16 / January / 2011, 14:21:51 »
    Hello. I am new in forum but old CHDK fan with five cameras, A560 (stolen), A710 (for daughter), SX 100 (stolen), SX110 (stolen) and SX 130 (not yet stolen). I have learned much and created many nice pictures with help from CHDK. I am very happy with this progress. My SX130 works with CHDK from Reply #85 but crashes immediately with CHDK from Reply #101. Looking patiently forward to new changes. This is only my experience, maybe it could help. Regards to all from Danube banks.


  • Publish
    Re: Chdk for SX130 IS ?
    « Reply #104 on: 16 / January / 2011, 15:57:52 »
    Good work guys. I have tested the release in reply #85 (everything more or less worked), and have now moved to the latest one (and will test it... so far no problems).

    I was wondering...  in both releases DNG images cannot be created with a shutter speed of 1.3 seconds or longer. Is this a limitation in all CHDK releases, or just the SX-130IS?... I'm sort of curious  :)
    Another thing, can anyone get the ISO override to work? It seems ISO 80 is minimum and ISO 1600 is maximum. (nothing outside the already present values)

    The aperture override works...  F8.97, F10.07, F11.31 work, higher values do not produce results different than F11.31.
    I have also tested the shutter speed override up to 512 seconds (have not tried longer), and it works.
    « Last Edit: 16 / January / 2011, 16:51:09 by Mr_Speedy »

    *

    Offline reyalp

    • ******
    • 9951
  • Publish
    Re: Chdk for SX130 IS ?
    « Reply #105 on: 16 / January / 2011, 16:23:57 »
    I was wondering...  in both releases DNG images cannot be created with a shutter speed of 1.3 seconds or longer. Is this a limitation in all CHDK releases, or just the SX-130IS?... I'm sort of curious  :)
    It is not a limit on other cameras, and should not be. If DNG isn't saved in this case, raw hook is probably in the raw palace, or needs to be added somewhere else. I believe the capt_seq code has changed in these cameras (also g12 and other recent ones) so the raw hook may not be in the same place as before.

    1.3 suggests this maybe this happens when canon firmware decides it needs a dark frame or other extra noise reduction ? It would not be surprising if this was a different code path. Dark frame is usually 3 sec or more on other cameras.

    Quote
    Another thing, can anyone get the ISO override to work? It seems ISO 80 is minimum and ISO 1600 is maximum. (nothing outside the already present values)
    In general CHDK ISO override doesn't get you additional range, it just gives you control. Every time anyone has done a proper test, this has been confirmed. AFAIK the only reports of extreme ISO override working have not been accompanied by test data.

    As a general note, when checking overrides, you should *always* check that the actual image reflects the override (e.g. more or less exposed by the expected number of stops compared to not using the override). Do not rely on any exif info unless you have confirmed it is reliable for the particular override you are using. The canon makernote values tend to be more reliable than regular exif, but don't assume they are correct either.
    Don't forget what the H stands for.

  • Publish
    Re: Chdk for SX130 IS ?
    « Reply #106 on: 16 / January / 2011, 21:10:21 »
    In general CHDK ISO override doesn't get you additional range, it just gives you control. Every time anyone has done a proper test, this has been confirmed. AFAIK the only reports of extreme ISO override working have not been accompanied by test data.

    It may (or may not) be worth pointing out that the custom auto-ISO HI was able to go up to 1600 on the A700, where that camera's normal maximum ISO is 800. The result was the camera would underexpose images by up to a full stop in order to meet the shutter speed threshold in low light. Even though this meant that I would need to use an image editor to restore the correct exposure, and the photos had (predictably) severe noise problems, having this "virtual" ISO available allowed me to get photos that I don't think would have been able to capture otherwise. It was a useful feature.

    I don't see why ISO overrides shouldn't work the same way (if it's technically possible), lowering exposure to allow for a virtual ISO higher than the normal maximum.

    *

    Offline reyalp

    • ******
    • 9951
  • Publish
    Re: Chdk for SX130 IS ?
    « Reply #107 on: 16 / January / 2011, 22:26:25 »
    It may (or may not) be worth pointing out that the custom auto-ISO HI was able to go up to 1600 on the A700, where that camera's normal maximum ISO is 800. The result was the camera would underexpose images by up to a full stop in order to meet the shutter speed threshold in low light.
    Meaning actual sensor gain was not changed, correct ? Not sure what you are gaining. One stop under exposed means you are still getting the same gain as ISO800.

    Note that the highest ISOs in Canon settings (even the cameras that don't have a special "high ISO" mode) are often not actually sensor gain. It's done in jpeg processing, there is no difference in the raw (ISO 400 and ISO 800 are this way on my a540)

    edit: because of this, it's a good idea to compare raws if you trying to test ISO overrides.

    One thing you can do with ISO override is use a low ISO in "high ISO" mode, which gives you faster shooting low resolution images on some cameras (mostly digic 4 AFAIK). This "high ISO" is also not sensor gain, it's more like binning.
    Don't forget what the H stands for.


  • Publish
    Re: Chdk for SX130 IS ?
    « Reply #108 on: 17 / January / 2011, 02:06:54 »
    It may (or may not) be worth pointing out that the custom auto-ISO HI was able to go up to 1600 on the A700, where that camera's normal maximum ISO is 800. The result was the camera would underexpose images by up to a full stop in order to meet the shutter speed threshold in low light.
    Meaning actual sensor gain was not changed, correct ? Not sure what you are gaining. One stop under exposed means you are still getting the same gain as ISO800.

    Well, with the "virtual" custom auto-ISO, what you're gaining is the ability to take photos in low light conditions with a shutter speed fast enough to eliminate camera shake or motion blur using the same auto-ISO settings you would use for better-lit scenes. If something interesting happens (say) on the street, or while you're in a moving vehicle, you don't have time to fiddle with the exposure while whatever-it-is happens or recedes into the distance - all you can do is aim and shoot, and anything that lets you do that faster helps you get the shot.

    Admittedly, I'm not sure why else someone would want a virtual static ISO as an override. If you have time to set something like that up, then presumably you have time to get what you want by using the camera in some more normal fashion (e.g. using a higher shutter speed). My point, I guess, was that if the custom auto-ISO could reduce exposure, then presumably a static ISO override could do something similar.

    Quote
    One thing you can do with ISO override is use a low ISO in "high ISO" mode, which gives you faster shooting low resolution images on some cameras (mostly digic 4 AFAIK). This "high ISO" is also not sensor gain, it's more like binning.

    Yeah, the sx130 has a low-resolution low-light mode that appears to be binning. It'd be nice to be able to control that through CHDK, but I don't know what kind of control would be useful (or technically feasible). Maybe if there was some way to combine this with the custom auto-ISO so that it seamlessly starts binning as necessary in order to meet the shutter speed threshold? But this is leaving the realm of "shouldn't it work this way?" and turning into a pure feature request (and not a well-informed one), so I'll stop...

    *

    Offline alvm

    • ***
    • 116
  • Publish
    Re: Chdk for SX130 IS ?
    « Reply #109 on: 17 / January / 2011, 04:47:20 »
    Hello all,

    Where can I get CHDK source code for sx130 entirely? There are several files only in pastebin site...

    Alex.
    « Last Edit: 17 / January / 2011, 06:32:24 by alvm »

     

    Related Topics