PowerShot SX220 HS - Porting Thread

  • 562 Replies
  • 89321 Views
*

Offline Tiz

  • *
  • 29
  • Publish
    Re: PowerShot SX220 HS - Porting Thread
    « Reply #280 on: 20 / July / 2011, 15:25:59 »
    Advertisements
    I have a question: is it possible to "save" the settings of a CHDK installation?

    For example, if I upgrade to beta 8, I would not like to configure the entire OSD again and, therefore, I would like to keep my settings. Are the settings in the CHDK folder and, if yes, do I merely have to replace the boot files if I upgrade to the latest version?

    How do I keep my settings if I want to create the same installation on each of my SD cards?

    TIA!

  • Publish
    Re: PowerShot SX220 HS - Porting Thread
    « Reply #281 on: 20 / July / 2011, 16:15:12 »
    I have a question: is it possible to "save" the settings of a CHDK installation?

    For example, if I upgrade to beta 8, I would not like to configure the entire OSD again and, therefore, I would like to keep my settings. Are the settings in the CHDK folder and, if yes, do I merely have to replace the boot files if I upgrade to the latest version?

    How do I keep my settings if I want to create the same installation on each of my SD cards?
    Just keep a copy of the CCHDK.CFG file from the SD card on your computer.  Copy it back to the same place on the SD card after each upgrade.

    Or just update the DISKBOOT.BIN file with each change - leave the rest of the card alone.

    « Last Edit: 20 / July / 2011, 16:37:54 by waterwingz »

    *

    Offline fe50

    • ******
    • 3034
    • IXUS50 & 860, SX10 Star WARs-Star RAWs
      • fe50
  • Publish
    Re: PowerShot SX220 HS - Porting Thread
    « Reply #282 on: 20 / July / 2011, 16:29:03 »
    I have a question: is it possible to "save" the settings of a CHDK installation?
    For example, if I upgrade to beta 8, I would not like to configure the entire OSD again and, therefore, I would like to keep my settings. Are the settings in the CHDK folder and, if yes, do I merely have to replace the boot files if I upgrade to the latest version?
    How do I keep my settings if I want to create the same installation on each of my SD cards?
    Just save / restore / copy the CHDK configuration file \CHDK\cchdk.cfg - this file includes the CHDK settings.

    When re-using a config file from another camera or from an older CHDK version, there may be issues when the CHDK code has changed - you should reset the configuration then (reset from the CHDK menu or just delete/rename the config file); this may occur while a new camera is in development state...

    To update CHDK just replace the CHDK binary files:

    DISKBOOT.BIN (the binary file for the autoboot loading method)   and
    PS.FIR (older cameras) or PS.FI2 (on newer cameras) (for loading CHDK with "Firm. Update...")

    with the new ones.
    On a multi-partition setup (two or more partitions on your SD card) don't forget to replace the files on both/all partitions !

    From time to time you should just copy/unzip all files from a full CHDK download package, this way you'll also get the latest language files, sample scripts, readme files etc.

    There are two additional, camera-dependend CHDK files:

    * badpixel.bin for DNG RAW support
    * badpixel (or badpixel.txt) for general badpixel removal (RAW and JPEG)

    Those two files can not be exchanged between different cameras.

    FWIW - in the german CHDKDE version it is also possible to change / edit / save  the CHDK config file from within a running CHDK script - http://chdk.bplaced.net/content/chdk-inside/10-lua/124-konfiguration-sichern.html
    « Last Edit: 20 / July / 2011, 16:52:16 by fe50 »

  • Publish
    Re: PowerShot SX220 HS - Porting Thread
    « Reply #283 on: 20 / July / 2011, 16:58:23 »
    I wasn't sure if the camera can go up to f11. Now I have proof.  8)

    But there is no difference between f/8 + ND filter out and f/11 right?


    *

    Offline funnel

    • ****
    • 349
  • Publish
    Re: PowerShot SX220 HS - Porting Thread
    « Reply #284 on: 20 / July / 2011, 18:55:37 »
    But there is no difference between f/8 + ND filter out and f/11 right?

    Right, they're exactly the same. The Av override is ok, it's just the ND filter that's acting strange.

  • Publish
    Re: PowerShot SX220 HS - Porting Thread
    « Reply #285 on: 21 / July / 2011, 09:18:02 »
    Offtopic question to all Canon SX220 HS users:

    I recently noticed that there is some dust behind the first and second lens of my SX220. My other (much older) compact camera's (an A710 and IXUS 82 IS) don't have this "problem". Anyone here that can confirm that this is normal for this particular camera.
    « Last Edit: 21 / July / 2011, 09:20:44 by Blablaat »

    *

    Offline funnel

    • ****
    • 349
  • Publish
    Re: PowerShot SX220 HS - Porting Thread
    « Reply #286 on: 21 / July / 2011, 09:47:00 »
    I can confirm this. I had noticed a lot of Canon cameras have the same problem. You can try to clean them with compressed air but it's not guaranteed it'll work. I heard Canon cleans them for free under warranty. I have some dust too in there right now but it's not noticable in images. I'll have to send the camera to the warranty service sometime before the warranty expires to clean them. This is something I really hate about this camera.

  • Publish
    Re: PowerShot SX220 HS - Porting Thread
    « Reply #287 on: 22 / July / 2011, 03:52:38 »
    Another scripting question.  I am trying to get and set various camera properties.  I can do some of them via get_prop and set_prop, but not many of the "official" script commands work.  In particular get_tv crashes the camera when you put it anywhere in the script (without a "rem"). Which of these should work, and what about setting these ?
    select N
    case 1; X=get_day_seconds
    case 2; X=get_temperature 1   
    case 3; X=get_tick_count 
    case 4; get_iso   X   
    case 5; get_av X
    rem case 6; get_tv X   
    case 7; get_ev  X
    case 8; get_zoom   X         
    case 9; get_display_mode X                   
    case 10; get_drive_mode  X                               
    case 11; get_exp_count X                       
    case 12; get_flash_mode X                       
    case 13; get_flash_ready X                 
    case 14; get_focus  X                         
    case 15; get_histo_range X               
    case 16; get_IS_mode  X                                             
    case 17; get_mode X                     
    case 18; get_movie_status X                     
    case 19; get_nd_present  X                   
    case 20; get_orientation_sensor  X                 
    case 21; get_platform_id X                                 
    case 22; get_propset  X                                   
    case 23; get_quality  X                                               
    case 24; get_resolution  X                                                 
    case 25; get_shooting X                                                                           
    case 26; X=get_time   2                                                                       
    case 27; get_zoom_steps  X
    end_select
    Thanks in advance


    *

    Offline funnel

    • ****
    • 349
  • Publish
    Re: PowerShot SX220 HS - Porting Thread
    « Reply #288 on: 22 / July / 2011, 04:21:49 »
    Look here for all commands http://tools.assembla.com/svn/chdk/trunk/lib/ubasic/tokenizer.c . There's no get_tv, just get_tv96.

    Regarding the Video button you mentioned a few day ago I'll make a patch to fix that. The video button should be the rec button.

    There's also a new version out that fixes the Av overide half_shoot problem. Thx to philmoz for fixing that.

  • Publish
    Re: PowerShot SX220 HS - Porting Thread
    « Reply #289 on: 23 / July / 2011, 16:21:48 »
    Why does the shutterspeed override only works well in easy, auto and (full) manual? I usually shoot in Program and when I override the shutterspeed to let's say 1/250s it sometimes refuses and sets the speed at 1/80s. This is just an example, the actual speed varies.

    Sometimes it does work like it should... but it would be great if it works all the time. Did I do something wrong? I have set the "override shutter speed" to 1/250, the "value factor" to 1 and the "shutterspeed enum type" to Ev Step.

     

    Related Topics