Ad blocker interference detected!
Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers
Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.
Possible "README.TXT" file for the Vxworks cameras, but it didn't turn out very small:Edit
This is the small readme to CHDK. It provides just enough info to get you rolling, for more information use the links at the bottom of this text file. You have a VXWorks Camera (Digic II Processor), so follow this procedure to get your camera started with CHDK: - Exract the archive onto your SD card using an SD card-reader. You MUST use a card-reader. You cannot copy files to your SD card by just using "Windows File Explorer" and your camera connected by USB cable. The USB connection to the camera is just for downloading images, not uploading files. - Now that all the CHDK files are on your SD card, make sure that you have the right version of CHDK for your camera. - Insert the SD card into your camera. - Start camera IN PLAYBACK-MODE. - When you extracted the archive it placed a file on your card called "vers.req" (or "ver.req" depending on the camera model). This will allow you to see, with the right camera-button presses, the TRUE firmware version of your camera (and other interesting information). - Press your "Set" button, hold it down. While holding down your "Set" button press your "Display" button. You will see the version of the firmware in your camera. Confirm that it is the right firmware to match up with the CHDK that you downloaded. Your real firmware version is NOT 22.214.171.124 nor 126.96.36.199 Your REAL firmware version will look something like: "Firmware Ver GM1.00A". (Pressing "Display" again a few times while still holding down your "Set" button will let you see even more information about your camera, including total number of shots taken since it was made.) - If all went well, correct camera, correct firmware, correct CHDK, now you can actually load and run CHDK. - While still in PLAYBACK MODE press your camera's "Menu" button to open Canon's Menu - Scroll to the bottom of the menu to the "Firm Update" option which should now be available. If by chance that you fail to see the "Firm Update" menu option try pressing your Playback button twice. You might have to wait 2 seconds between presses. When this is done right the lens will retract and go into a power-saving viewer/slideshow playback mode. This seems to be an option on most Powershot Cameras. - Now that your menu cursor is on the "Firm Update" option, press your "Set" button or "Right" navigation button to enter the "Firmware Update" Screen. Either button press will work. - Press your "Right" navigational button to select OK. Press your "Set" button to confirm your choice. - Your camera will now load CHDK. You should see the blue "Print" button on the back of your camera flash a few times to let you know that CHDK is booting, and the CHDK Splash-Screen will appear in your viewfinder or LCD display. When fully loaded you will see a new battery-meter icon and several other things on your LCD or EVF display. Don't worry if they look like clutter, all of them can be turned on and off and repositioned on your screen in CHDK's configuration menu system. (CHDK <ALT> mode / Menu / OSD Parameters / OSD Layout Editor) - To enter CHDK's alternate menu system, press your "Shortcut" button. A small "<ALT>" will appear at the bottom of your screen. Whenever <ALT> is showing you may now press your camera's "Menu" button to enter CHDK's new menus. To exit <ALT> mode and return to your camera's normal operation just press your "Shortcut" button again. The settings that you apply in CHDK's menus will now be applied when using the camera normally (while not in <ALT> mode). The only time you will use <ALT> mode for actually taking pictures is if you run an automated CHDK script to take your photos for you. If you want to use your "Shortcut" button's normal function just press and hold it down a little longer. Some cameras allow you to reconfigure your CHDK "<ALT>" toggle button in the CHDK "Miscellaneous Stuff" menu in case you don't like it being the "Shortcut" button. - If you would like to have CHDK auto-load every time you power on your camera, then go into CHDK's menu system. (Press "Shortcut" to enter <ALT> mode, then your "Menu" button to enter CHDK's menus.) Scroll to the bottom of the main CHDK menu to the "Debug Parameters" option. - Enter the "Debug" menu and scroll to "Make Card Bootable...". Press your "Set" button. - Now remove your SD card and slide its little "write protect" tab to the locked position. Insert the card back in your camera. Now when you power-up your camera CHDK will automatically load. If you want to turn off CHDK's auto-loading feature just take out the SD card and put the write-protect tab back to the unlocked position. Don't worry about using the card either way. CHDK is designed to work with a locked card in this manner and all photos taken will be written to the card even when it is locked/write-protected. - Or for Windows users: use the "CardTricks" program (will be included here later). For more information visit the following links: CHDK Wiki: http://chdk.wikia.com/wiki/Main_Page Main CHDK Manual: http://chdk.wikia.com/wiki/CHDK_firmware_usage Allbest CHDK Manual: http://chdk.wikia.com/wiki/CHDK_firmware_usage/AllBest JuciPhoX CHDK Manual: http://chdk.wikia.com/wiki/CHDK/MoreBest CHDK Forum: http://chdk.setepontos.com/index.php In-Depth Guide explaining a lot of things: http://chdk.setepontos.com/index.php/topic,1167.0.html Timeline (changelog) of chdk: http://tools.assembla.com/chdk/timeline For more information about this build visit: http://chdk.setepontos.com/index.php/topic,688.0.html Download the sources of this build here: http://tools.assembla.com/chdk/changeset/head/branches/juciphox?old_path=%2F&format=zip You can get a nice app that will help you making your card bootable on windows: http://chdk.setepontos.com/index.php/topic,964.0.html <insert text with small description of chdk here> <insert text with installation tips for vxworks here> <insert more links and especially tricks for OS other than Windows> <convert to html?> but then in-camera reading would be difficult... <insert link to gpl, or quote gpl>
Suggested "readme.txt" file for the CHDK/GRIDS/ folder. Edit
What are Grids? Grids are an overlay for your EVF/LCD display that can help you with composition, cropping, subject/image alignment, and other novel things. Normally most cameras only offer you one simple option, a "Rule of Thirds" composition grid, but with CHDK the sky is now the limit on what you want displayed on your viewfinder for these handy photographer's tools. You may Load and run your Grid files from the CHDK <ALT> + Menu path of: "OSD Parameters" > "Grid" > "Load Grid from File..." When not in <ALT> mode you may quickly turn your Grid Overlay (and all other CHDK OSD elements) on or off with a simple Half-Shutter-Press + Right-Navigation button combination. Or put the "Grid" > "Show Grid Lines" menu toggle on your fast-access Custom User-Menu if not wishing to turn off all of CHDK displays. Grids are drawn as an EVF/LCD overlay by simple graphic commands. You may edit "Grid Files" using any basic text editor. (MAC users should check that they are saved as "plain text encoding", select "Unicode (UTF-8)" when saving your files, the same as when saving uBASIC script files.) For faster loading/searching access save them to your /CHDK/GRIDS/ folder on your SD-card, the default "Load Grid from File..." location. Grid patterns are drawn on your EVF/LCD display with the coordinates of: X = 0 to 359 (horizontally) and Y = 0 to 239 (vertically), with position 0,0 being in the upper-left corner and 359,239 being in the lower-right corner. When designing your own Grid patterns you must keep in mind that the 360x240 drawing coordinate area is in a 3:2 aspect ratio, but when displayed on your EVF/LCD display they will visually appear in a 4:3 aspect ratio. Use whatever method you have to convert your drawing-coordinates between the two. For complex grid designs one prolific grid-designer found it best to draw a new grid using any decent vector-graphic editor on their computer with a 360x270 (4:3) base canvas size and then resizing the final grid-design with "keep proportional" turned off to the required 360x240 (3:2) ratio. The new, and now-correct, drawing coordinates are then read off from the resulting 3:2 proportional image. All right-angles, complex shapes, curves, and circles appear fully proportional and correct in the EVF/LCD display. If needing to only do simple circles or squares with the 4:3 / 3:2 offset, take the X radius/dimension and multiply it by 8, then divide that result by 9, to get a proportionally equivalent Y radius/dimension. Format and commands for Grid Files for CHDK: @title <text to show in menu> @line x0, y0, x1, y1, lineColor @rect x0, y0, x1, y1, borderColor @rectf x0, y0, x1, y1, borderColor, fillColor @elps x0, y0, rx, ry, borderColor @elpsf x0, y0, rx, ry, fillColor # comment <a non-implemented note> Where: rect = hollow-rectangle rectf = filled-rectangle elps = ellipse, where x0, y0 = ellipse radius center, and rx, ry = the two radiuses/radii elpsf = ellipse-filled See the included sample Grid Files on their use. Spaces between commands and numbers on each line are optional. If designing a very complex grid you may need to omit all spaces to get your grid-pattern file to fit within the maximum memory of (approx.) 3886 bytes. All numbers can be either decimal or hex. Hex numbers are prefixed with "0x", as in "0x16". For color-numbers you may use your CHDK <ALT> Menu of "Miscellaneous Stuff" > "Draw Palette" to choose and preview them, or any of the "Visual Settings" color selections menus for font display colors -- which is sometimes easier because you can see all of the colors at once instead of previewing one at a time in the "Draw Palette" feature. For the most complete and latest collection of user-designed and submitted Grid Files, as well as a handy utility to create "text-grid designs", see: http://chdk.wikia.com/wiki/Grids Included are some sample Grid files, these are: 3to2grid.grd Match your EVF/LCD display to a 3:2 crop-ratio for prints matching that ratio, 6" x 4" prints. 3to8grid.grd <i>(Usage Unknown, I'm not sure why this one was included, perhaps someone else can clarify?)</i> golden1.grd Compose your subject placement in accordance with the "Golden Ratio". A composition ratio deemed most pleasing to the human-eye. This version is based on "golden-triangles". Place your subject where the two lines meet or aligned along their axes. (This grid may be used in reflections and flips, affording 3 more locations, do it mentally, or edit the grid file to reflect all 4 golden-triangle intersections.) golden2.grd Same as above, but showing you one more of the 4 total intersection/alignment possibilities. id.grd This grid is based on ISO/IEC 19794-5:2005 values required for administrative identity photo (passports, identity cards, driving licence...). A large red face shape represent the maximum size accepted, whereas the smaller green shape is the minimal size allowed. A grey area represent where eyes have to be. A vertical axis and two horizontal rulers should help for positioning the subject. The picture afterwards has to be resized to 35 x 45 mm before being printed. The best is to make a composition of 6 (2 lines, 3 rows) photo on a 10 x 13 cm format or 8 (2 lines, 4 rows) photo on a 10x15 format. The reprint should be done by a professional, not by your personnal printer...otherwise it might be refused by the administration staff. rulecross.grd Fashioned after some aerial-photography and photomicrography grids. Horizontal and vertical rulers bisecting your FOV. Divided horizontally in 4 units of measure and vertically in 3 units of measure. With half and 1/10th unit tic-marks. Small crosshairs in the open areas at 1/2 and 1-unit intervals. May be extremely handy for macro-photography when trying to keep the subject size the same in landscape or portrait orientations. Or when comparing subject size to one another when reframing or refocusing. rulers.grd As above, but without the crosshairs in the clear areas. sports.grd A "Sports Finder" grid. This grid was designed around the available image sizes of an "S3 IS" camera. When shooting in highest resolution of "L", 2816 x 2112 pixels, this grid displays the cropping areas as if you were using the "M1" - 2271 x 1704 pixels, the "M2" - 1600 x 1200 pixels, and the "S" - 640 x 480 pixel image sizes. This way you can view the full-frame in the viewfinder, but plan ahead for cropping to one of the other available resolutions. You can then watch for any activity outside of those image-resolution boundaries and be better able to follow any fast action in your viewfinder that might be entering or leaving the final-crop image area. One more pair of lines was included to show the "W" - 2816 x 1584 wide-angle FOV so when planning to crop for that resolution you can still watch for activity above and below your final image area, instead of just blacking out those areas as the camera normally does. It is worth noting, that even a 1600 x 1200 resolution image will still print quite nicely even at 7"x5" print size. For that little-league game this might be just the thing you need for following the action and still having photos to print out for relatives and friends. stolen.grd Load this grid before putting your camera down and you don't want anyone else to use it. When turning on your camera only the words "STOLEN CAMERA!" will show in the display. The view blacked-out, making subject viewing/framing useless. Unless they know how to turn off CHDK features. :) This is part of an experiment on using CHDK as a theft-deterent. Using this grid combined with an auto-running script file which flashes all your LED lights and triggers all the warning-beep sound-events in your camera, it might be a quite effective way to see/hear if someone is picking up your camera and turning it on without your permission, as well as rendering the camera useless to anyone without CHDK knowledge. third_h.grd Divides your FOV into 3rds horizontally. Based on the "Rule of Thirds" composition concept. (A simplified version of the "Golden Ratio" concept.) third_v.grd As above but dividing your FOV into 3rds vertically.
- Added in an some extra info that explains their use and how to design your own.
Dutch language Edit
Don't know where else to ask/say this, so hopefully one of the MoreBest/Juciphox developers will read this. The Dutch language file should be fully compatible with the latest build. I did the translation for changeset 479, but as far as I know no new text has been added since. Hopefully you will include this language file in future builds, so all Dutch users do not have to download this file seperately. If you do include it, please let me know (here or on my Talk page) what is the best practice to keep it up to date.
Regards, Spinal83 10:30, 2 September 2008 (UTC)
- Such things can be posted in the forum, e.g. here: the collaborative CHDK build. Fe50 10:56, 2 September 2008 (UTC)
- Thanks :) -- Spinal83 15:59, 3 September 2008 (UTC)
Sync Delay 0.1 seconds and 0.001 seconds broken Edit
I cannot get the sync delay to work on my camera. I have enabled all sync related options, but the camera will not delay any amount of time that I specify in the sync delay. I have tried several times, even telling it to delay 10/10 of a second (1 second), but when voltage is removed from the USB, the camera takes the photo as fast as it can without delaying at all. Both of my cameras exhibit this behaviour, so I think it is an overall bug and not specific to one model.
Since I have two slightly different model cameras (A650 and A630), they are out of sync by a small amount, which causes high speed stereo photography to be less than ideal. I know that the sync delay works in the specialized stereo build, but that build lacks a lot of features I enjoy in the regular build. And since the regular build supposedly has the option to delay, I would really like it to work.
Has anyone else found that chdk does not honor the specified delay? Sayno2quat 18:45, September 6, 2011 (UTC)