SoftHub

Installation:

- To install CHDK on your Canon P&S camera, you need to know the model number and firmware version of your cameras in order to get the right version of CHDK for your camera
- Once you have the correct CHDK installation file for your camera, you need to prepare and load your camera's SD card with CHDK. The best method for doing this depends on how you intend to use your camera and the date your particular camera was released.

Fixes:

Compatibility with 1.3:
- Scripts are generally compatible.
You will see a warning if @chdk_version is not specified in the script header, but 1.3 compatible behavior will be used. If you use @chdk_version 1.4, the return values of some functions are changed.
- Some CHDK script mode numbers have changed, and some names have been removed. This does not affect common modes like, M, P and Auto, but might affect scripts that use more obscure modes, especially if the are referred to by number rather than capmode.lua names
- CFG files: CHDK 1.4 uses the same CFG files as 1.3.
It should generally be compatible and retain your settings, but if you don't want to risk re-doing your CFG, backing up the CHDK/*.CFG files before updating is recommended. Custom colors will be reset, and if you switch back to 1.3, colors may be incorrect. CHDK 1.2 CFGs should be migrated as was done for 1.3.
- Modules and language files are NOT compatible. You must update these when you update your build.

Significant changes:

- long file name support in script, file browser / selector.
- enhanced script @parameter header including compact format, Boolean values, table support, and full variable names in Lua.
- upper and lower case single characters can now be used as @param variables in uBASIC
- script header now supports @subtitle for better organization in script that use many parameters
Lua scripts now "compile" when loaded to reduce memory needed (original script text no longer stored in memory)
- Added @chdk_version parameter to specify version of CHDK script was written for, 1.3 assumed if none present.
- Made Lua script API use of boolean values more consistent, (@chdk_version 1.3 provides backward compatible behavior)
- enhanced UI functions for touchscreen-equipped cameras - touching menu areas and window buttons directly now works
- rework of CHDK color palette handling to allow separate palette definitions for each camera model - transparent grey color defined for OSD background use
- updates to GPS functionality for cameras with built-in GPS
- improvements in console handling when script running including console not timing out and console reset to "on" state when script errors are encountered.
- upgrades to Lua RAW shooting hooks to allow analysis and modification of RAW buffer during shooting
- scripts added to the User Menu can now be started directly from the User Menu via a full press on the shutter button. Using Func/Set now brings up a dialog box for ok/cancel. Selecting ok makes the script the current script and exits to the Script menu.
- usb_force_active now available on almost all cameras
- filewrite / remote capture support for many more cameras
- development support for digit 6 / thumb2 cameras
- Improved focus overrides
- Convert shot histogram code to a module.

About Digital Camera Firmware:

Updating to a newer firmware version than the one already installed on your camera can improve the device’s overall performance and stability, resolve various issues, and add support for newly developed features or enhance existing ones.

On the other hand, downgrading the camera’s firmware can recover its functionality in the unlikely event the currently installed version is faulty or the device’s performance dropped after an upgrade. However, bear in mind that applying an earlier build might not always be possible.

It is recommended that changing the camera’s firmware be performed when the new release resolves an issue that your device has been encountering, or adds a new feature (or enhances an existing one) that could prove useful for you.

This process isn’t intended to be destructive, but still, it’s best to save all your personal data and configurations before applying a different firmware. Moreover, make sure that the