CHDK Forum
Using CHDK => CHDK Releases => Topic started by: philmoz on 28 / December / 2010, 19:45:18
-
Note:
CHDK for the G12 can be downloaded from the autobuild server (http://mighty-hoernsche.de/ (http://mighty-hoernsche.de/) or http://hacki.someserver.de/ (http://hacki.someserver.de/)). These builds are created nightly from the latest version of the CHDK code. The autobuild server creates 'safe' versions of CHDK with some options disabled. For example the current EXMEM (extended memory) system is still considered expiremental and is not enabled on the autobuild server.
Changes in Beta 8:
- Fixed zoom out when recording video. Can now zoom back out into optical zoom range after zooming in to digital zoom range.
- Fixed shutter & aperture overrides not working if shutter fully pressed very quickly (not waiting for half press of shutter to do focus / exposure calculation). A quick shutter press will now use any shutter & aperture override values; however ISO override value is not correct (unless you half press shutter and wait before full press).
Changes in Beta 7:
- Fixed intermittent startup crash (fingers crossed). Happens most often on when starting with a lot of images/movies already on the card.
- Fixed 'Dark Frame Subtraction' option (under RAW Parameters).
Changes in Beta 6:
- Fixed intermittent startup crash.
- Changed G12 startup logic to align with the CHDK standard (short press of on/off button starts in playback mode, long press starts in record mode).
- Implemented live viewport logic to improve motion detect speed, optimised motion detect code.
- Enabled bracketing in continuous mode when using the self timer.
Changes in Beta 5:
- Fixed crash when using set_zoom function in scripts.
- Fixed problem causing CHDK RAW/DNG files to not be saved when shutter speed was set to longer than 1 second.
Changes in Beta 4:
- Fixed problem affecting some scripts.
- Added support for 16:9, 3:2, 1:1 and 4:5 image size modes (zebra, edge overlay, histogram and motion detect should now work correctly in these modes).
- Added firmware version 1.00E (thanks to drunkentech for dumping the firmware and everyone who has helped test it).
Changes in Beta 3:
- Fixed the 'Make card bootable...' option (under Misc settings).
Changes in Beta 2:
- CHDK RAW files can now be saved in the same directory as the JPEG images (note, if you set this option and you are saving Canon RAW files as well, make sure you do not use .CR2 as the CHDK RAW file extension otherwise it will conflict with the Canon file names).
- Updated the core code to changeset 1006.
- Fixed a number of minor bugs.
Known issues:
- Dark Frame Subtraction is not working.
- RAW / DNG files are always saved to the DCIM/100CANON directory on the SD card. The option to save the raw files with the JPEG files is not working as the logic used to name the image directories has changed in recent cameras.
- CHDK Alt mode menu disappears sometimes. Pressing up/down/left/right buttons will usually refresh.
- DNG color matrix needs work.
- Splash screen and menu palette colors are off due to very limited palette available (also the palette is different in play and records modes so I have to pick colors that are the same in both).
- DNG thumbnail colors are a bit strange.
- Aperture & ISO overrides don't appear to work.
- The camera doesn't respond to turning the jogdial in Alt mode; but when you leave Alt mode any dial movements are then picked up and processed by the camera (e.g if you are on AV shooting mode the dial changes aperture. In Alt mode the aperture won't change as the dial is turned; but when you leave Alt mode the camera will then update the aperture). Be careful with the dial as camera settings may change when leaving Alt mode.
- If you zoom past the maximum optical zoom (5x) and into digital zoom when recording a movie you cannot then zoom back to anything wider than 5x optical zoom.
- Optical zoom motor noise is recorded very loud when recording movies (probably because the microphone is right next to the lens). [There is probably nothing that can be done about this.]
Things I've tested:
- CHDK RAW & DNG saving.
- Movie bit rate / quality setting override.
- Shooting override of shutter speed (long exposure works, very short exposure not tested yet).
- Shooting override of quality setting (can select super-fine JPEG quality).
- Scripts (motion detection, and intervalometer scripts tested).
- Manual boot (using Firmware Update in the Play mode menu).
- Autoboot from partitioned SD card larger than 4GB.
- Optical zoom & manual re-focus when recording movies.
Phil.
-
- Movie bit rate / quality setting override.
As part of my mission to remove as many 'questionable' features as possible, it would be interesting to know what you think of this, Phil.
(if you have time as New Zealand races towards 2011 before the rest of the planet :) )
-
- Movie bit rate / quality setting override.
As part of my mission to remove as many 'questionable' features as possible, it would be interesting to know what you think of this, Phil.
I have a hard time seeing any substantial difference between the highest quality setting in CHDK and the default camera setting - despite the file size being three times larger. That's not to say that there isn't a use for this in some circumstances (fast motion might benefit the most). There's also probably some use for lowering the quality setting to increase recording time for some people.
The 'super-fine' JPEG quality setting is a bit the same, it's almost impossible to see any real difference in the resulting JPEG images; but the 'super-fine' files are almost twice the size.
Regards,
Phil.
-
Hmmm .... in the 'lightweight' SDM build that I am working on I will exclude super-fine JPEG.
Incidentally, I have not kept up with this, what video exposure parameters can we override ?
Can we force fixed exposure ?
David
-
Hmmm .... in the 'lightweight' SDM build that I am working on I will exclude super-fine JPEG.
Incidentally, I have not kept up with this, what video exposure parameters can we override ?
Can we force fixed exposure ?
David
As far as I know on the quality setting can be overridden in video mode.
Phil.
-
Can you set a fixed exposure (shutter) override ?
-
I want to take a moment and thank you for doing this for the G12!
-
I also want to thank you.
Now I can go and buy the G12 :D
-
Hi,
New to CHDK but just got a G12. Firmware version 1.0.0E...
Tried the latest beta. 2GB card formatted in FAT16 using Cardtricks. Sent the zip of beta CHDK onto the card using same. Popped unlocked card into G12 : camera does not power-on. Did same with locked card : does not power-on either...
Is this firmware incompatibility?
Many thanks,
Thierry
-
Hi,
New to CHDK but just got a G12. Firmware version 1.0.0E...
Tried the latest beta. 2GB card formatted in FAT16 using Cardtricks. Sent the zip of beta CHDK onto the card using same. Popped unlocked card into G12 : camera does not power-on. Did same with locked card : does not power-on either...
Is this firmware incompatibility?
Many thanks,
Thierry
Unfortunately yes. It's very unlikely that one firmware version of CHDK will work on a camera with another version.
The 'Basic Dumper' script seems to work for most cameras to dump out the firmware:
http://chdk.wikia.com/wiki/Porting_the_CHDK#Q._How_can_I_get_a_firmware_dump.3F (http://chdk.wikia.com/wiki/Porting_the_CHDK#Q._How_can_I_get_a_firmware_dump.3F)
If you can get the 1.00e firmware dumped from your camera and send it to me I can look at doing a port. I'll need some help testing it though as I don't have a camera with that version.
Regards,
Phil.
-
If you can get the 1.00e firmware dumped from your camera and send it to me I can look at doing a port. I'll need some help testing it though as I don't have a camera with that version.
Regards,
Phil.
Thank you SO MUCH for your hard work. 1.00e, dumped with the Canon Basic Universal Dumper, is at http://drunkentech.com/g12versionE.zip (http://drunkentech.com/g12versionE.zip)
Please let me know if you have issues reading it. Thanks again! (Fixed the link)
-
Thank you SO MUCH for your hard work. 1.00e, dumped with the Canon Basic Universal Dumper, is at http://drunkentech.com/g12versione.zip (http://drunkentech.com/g12versione.zip)
I get a page not found error from the link.
Phil.
-
I get a page not found error from the link.
Phil.
Sorry, didn't capitalize the link. It's corrected on my original post
-
I get a page not found error from the link.
Phil.
Sorry, didn't capitalize the link. It's corrected on my original post
Got it, thanks. It will take a little while to get the basic port going.
It you want to help with alpha testing send me a personal message with your email address and I'll email you test versions when they are ready.
Regards,
Phil.
-
Firmware 1.00E is pretty close to 1.00C (that I have on my camera).
I've have a preliminary 1.00E version ready to test that the boot loader and basic functionality works.
Anyone want to volunteer to test it?
Phil.
-
Hi Phil.
Does USB remote switch work ?
(just connect to PC to get +5V signal).
David
-
Hi Phil,
I see someone beat me to making the 1.0E version available... Seems like new G12 owners are eager to get going with CHDK! Would be happy to help with the testing. Let me know where I can get the file. Thanks for the time you are spending on this for us know nots
Cheers,
Thierry
-
Hi Phil,
I was happy to read that development for G12 has been started. Thank you for taking the effort. I saw that you are looking for testers to have a look at the G12 1.0.0E build. I do own a G12 with this firmware version and I am happy to assist. I do have some experience with CHDK on a S90 incl. some script coding. But I do not have either the know how nor the infrastructure (development environment ) in place for helping with actual coding.
If it helps I could run a few tests. It would be nice if you could let me know which areas of functionality are the most critical ones.
regards
Burkhard
-
Hi Phil.
Does USB remote switch work ?
(just connect to PC to get +5V signal).
David
Not yet.
-
For anyone brave enough here is the alpha test version for firmware 1.00E.
There is a good chance that this will either not boot or will crash/lock up the camera.
It appears that manual booting does not work with firmware 1.00E yet so you will need to create a bootable SD card in order to use this.
Good luck :)
Phil.
-
Hi Phil,
thank you for providing the alpha version. Good news it boots and works on my G12. Here are some more details:
What is working
- Booting via bootable SD card
-Grids
- Histogramm - but suffering from odd color schema
- OSD Menue but
-odd colors
- Does not flip with the display hence gets unusable in case display is not in default position
- When display is in default position some strings are placed out of screen (e.g raw indicator at the right bottom is to far on the right side)
- Flickering a lot when camera is in shooting mode - seems more stable in play mode
- Menu entries get transparent instead of highlight color if in shooting mode
- RAW produces files but I am not sure whether or not they are valid or not (I do use the native RAW files anyway)
- Setting OSD colors but with very limited color choice
Scripting
- HDR4G - Using set_tv96_direct, get_propset() and a lot of basic stuff successfully
- Focus Bracketing script - Setting the focall distance succesfully, having some problems with setting to macro mode but that may be a limit of the script rather than the chdk build (though it works fine on my s90)
- Motion Detection (based on Fudgey's script) works fine as well
What is not working
- Zebra mode
- Aperture overwritinging
Hopefully I can do some more tests tommorow. If you update the software in between or have any hints where it does not make sense to have a look at yet (beyond the info on this forum) please let me know.
Thanks again for providing the build.
regards
Burkhard
-
Thanks for testing it - that's better than I'd hoped for :)
- Histogramm - but suffering from odd color schema
- OSD Menue but
-odd colors
- Does not flip with the display hence gets unusable in case display is not in default position
Recent cameras have very limited palettes so it's difficult to find a good set of colours to use.
CHDK OSD should work if the display is open and facing to the rear, or flipped around and folder back onto the camera. It doesn't work if it's rotated and facing forward (text is reversed) - not sure if there's an easy fix for this or not.
- When display is in default position some strings are placed out of screen (e.g raw indicator at the right bottom is to far on the right side)
You can use the OSD Layout Editor under OST settings to move things around to your liking.
- Flickering a lot when camera is in shooting mode - seems more stable in play mode
Known issue, seems to be a problem with many recent cameras. Pressing the up, down, left or right buttons usually brings the menus back.
- Menu entries get transparent instead of highlight color if in shooting mode
This was by choice (I like the transparent menus). You can change the colours under Visual Settings.
What is not working
- Zebra mode
- Aperture overwritinging
Can you give me more details on what is wrong with zebra? It works fine on 1.00c firmware.
Aperture and ISO overrides is something I still need to work on (they may not be possible).
Phil.
-
You guys must be on an earlier time-zone...! I have also done some testing and can confirm Burkhard's feedback: working very well already. I tried the ultra-intervalometer script which seems to be working fine. I did not go into the other stuff yet because I still need to figure out what will bring added value relative to the default G12 specs.
Great job!
Thierry
-
Hi Phil,
thanks for the feedback. I was not fully aware of the limitations. As for the Zebra mode: I have retested the feature and found that it was my fault (...I was using a transparent "color" to mark the areas out of range, couldn't belief it ...).
reagards
Burkhard
-
Hello phil, since i'm so much behind trunk and too lazy to adapt (read: overwrite) my g12 code with yours, can i ask you to try a lua shoot() when in HDR mode (inside SCN)? Here it shoots but then lua hangs, what about your port?
greets
c10ud
-
@Philemoz does this work correctly:
http://tools.assembla.com/chdkde/changeset/538 (http://tools.assembla.com/chdkde/changeset/538)
maybe better: function or macro get_image_offset()
-
Hello phil, since i'm so much behind trunk and too lazy to adapt (read: overwrite) my g12 code with yours, can i ask you to try a lua shoot() when in HDR mode (inside SCN)? Here it shoots but then lua hangs, what about your port?
greets
c10ud
Yes, it works fine (at least on firmware 1.00c that I can test).
Regards,
Phil.
-
uhm, i copied over the captseq code (which was about the same), but no luck -- i guess something's wrong in old core code then.. (btw, i'm running shoot() from ptp)
-
@Philemoz does this work correctly:
http://tools.assembla.com/chdkde/changeset/538 (http://tools.assembla.com/chdkde/changeset/538)
maybe better: function or macro get_image_offset()
It works on SX30 & G12. It's how I handle the variable image aspect ratios that don't match the viewport aspect ratio. It's used to stop the histogram & motion detect code from scanning the black bars at the top & bottom or left & right.
An image offset function is a good idea, I'll clean this up and post a patch.
Regards,
Phil.
-
uhm, i copied over the captseq code (which was about the same), but no luck -- i guess something's wrong in old core code then.. (btw, i'm running shoot() from ptp)
I haven't tried shoot from within ptpcam. I'll try it tonight and let you know.
Edit: 'lua shoot()' works from within ptpcam for normal and HDR mode.
Phil.
-
thanks, i'll see what's wrong here then:)
-
thanks, i'll see what's wrong here then:)
If you want a challenge see if you can work out why shooting_set_focus doesn't work.
It should allow the focus distance to be set from scripts; but I can't get it to work and I can't figure out what's wrong :)
Regards,
Phil.
-
some random infos (maybe you have them already, but i'll write them down for a quick reference -- and remember i am currently diverting from trunk :():
i'm seeing that while in MF, the set_focus thing seems to work (with infinite ~9000)
PROPCASE_SUBJECT_DIST1 and PROPCASE_SUBJECT_DIST2 are ok.
PROPCASE_REAL_FOCUS_MODE doesn't change when in MF, while PROPCASE_FOCUS_MODE goes to 1.
MoveFocusLensToDistance is correctly at 0xffb71f98 (while in MF, it changes the focus as expected).
When with PROPCASE_FOCUS_MODE=1 and not in MF, set_focus works but then camera autofocus again. I have set CAM_HAS_MANUAL_FOCUS. Maybe shooting_get_focus_mode() returns a wrong value?
Investigating..
edit: in the end, SET_NOW seems to work. SET_LATER crashes the cam! :)
edit2: i now see i need the expdrive task enabled in order to make it work with SET_LATER (right?).. i had it disabled because of "keep it tiny"...let's try enabling it.
edit3: meanwhile, i built a svn export of g12 from trunk (i had to change some BL _label to BL sub_address in order to fix some relocation error when compiling...maybe my gcc is too old?) and i see lua shoot() is indeed working. luar is hanging the stack, but i guess that's not a priority.
-
Deleted by a craven coward
-
I am currently working on a lightweight build that supports motion-detection (with the added SDM features including universal movie capture), HDR bracketing, focus-stacking, time-lapse single-shot (including fixed-shots or fixed-time burst), time-lapse with Tv bracketing, focus bracketing or both, DNG single or continuous shots, stereo slit camera and streak camera that builds the image in the camera.
So far, it does not use ANY menus.
David
-
@microfunguy
That sounds mental, cannot wait for a go on it.
Colin
-
<OT>
Thank heaven for that.
Yes, indeed: thank heaven for people like ewavr, reyalP, philmoz, rudi and many (!) other CHDK developers & workers - without such people CHDK would only be a poor copy of what is is !
...have huge promise but don't really produce much (remember CBasic?)
You should follow the development threads carefully and you should try to understand things before you're posting such nonsense >:(
cBasic: without the great development work on this, none of the newer camera ports would be possible !
"a lot less clicking thru menus" - aren't you able to read the documentation and use the user menu ?
"so understandably I want PTP" - don't shed tears here in a HACKER forum; talk to CANON, ask them why they give you only a "lightweight build" (don't people like you normally call this "user friendly" ?) implementation of PTP ?
</OT>
-
Deleted by a craven coward
-
CHDK seems to be engrossed in a series of Kafka-esque crazes that have huge promise but don't really produce much (remember CBasic?)
Without the cbasic work, none of the recent cameras (including G12) would be dumped, never mind ported. So yeah, total waste of time time ::)
-
That sounds mental, a lot less clicking thru menus then? Thank heaven for that. CHDK seems to be engrossed in a series of Kafka-esque crazes that have huge promise but don't really produce much (remember CBasic?) like optional scripting and exmem, not to mention PTP. I mean what is the point of a cut down version? My G9 can use the Canon PC software, my Ixus 95 cannot, so understandably I want PTP to replicate the Canon SW on my '95, not a half-baked version.
The CHDKDE people seem to be making the running right now- time for a merger?
Colin
I can't speak for anyone else; but I do this for me, I work on the stuff that I find interesting and fun - if it benefits others then that's a bonus.
You're more than welcome to do some actual development on CHDK and contribute in that way - then you can choose what bits get improved.
Alternatively you could set up a commercial venture around this and pay us to do it - then you get to call the shots and decide what is in and out.
My consultancy rate is $1,600 per day :D
Phil.
-
some random infos (maybe you have them already, but i'll write them down for a quick reference -- and remember i am currently diverting from trunk :():
i'm seeing that while in MF, the set_focus thing seems to work (with infinite ~9000)
PROPCASE_SUBJECT_DIST1 and PROPCASE_SUBJECT_DIST2 are ok.
PROPCASE_REAL_FOCUS_MODE doesn't change when in MF, while PROPCASE_FOCUS_MODE goes to 1.
MoveFocusLensToDistance is correctly at 0xffb71f98 (while in MF, it changes the focus as expected).
When with PROPCASE_FOCUS_MODE=1 and not in MF, set_focus works but then camera autofocus again. I have set CAM_HAS_MANUAL_FOCUS. Maybe shooting_get_focus_mode() returns a wrong value?
Investigating..
Thanks for that, I think it was the camera in MF mode that was messing me up. I have a test script working that can set focus distance. I also thought it was also possible to use the zoom lever to manually focus; but this doesn't seem to be working either - must still be missing something somewhere.
edit: in the end, SET_NOW seems to work. SET_LATER crashes the cam! :)
edit2: i now see i need the expdrive task enabled in order to make it work with SET_LATER (right?).. i had it disabled because of "keep it tiny"...let's try enabling it.
edit3: meanwhile, i built a svn export of g12 from trunk (i had to change some BL _label to BL sub_address in order to fix some relocation error when compiling...maybe my gcc is too old?) and i see lua shoot() is indeed working. luar is hanging the stack, but i guess that's not a priority.
I'm using gcc 4.5.1. Which addresses gave you errors?
Phil.
-
with gcc 4.3.3: (there could be something else, i don't remember exactly...this is what i get from a stock trunk, just a make)
first occurrence: ../platform/g12/libplatform.a(shooting.o): arm call to thumb
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `sub_FF815EE0_my':
boot.c:(.text+0x2f8): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
boot.c:(.text+0x308): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
boot.c:(.text+0x31c): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
boot.c:(.text+0x330): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
boot.c:(.text+0x340): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
boot.c:(.text+0x350): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `loc_FF81FB98':
boot.c:(.text+0x3a4): relocation truncated to fit: R_ARM_PC24 against symbol `_eventproc_export_SleepTask' defined in *ABS* section in main.elf
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `init_file_modules_task':
boot.c:(.text+0x43c): relocation truncated to fit: R_ARM_PC24 against symbol `_eventproc_export_PostLogicalEventToUI' defined in *ABS* section in main.elf
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `sub_FF876518_my':
boot.c:(.text+0x484): relocation truncated to fit: R_ARM_PC24 against symbol `_DebugAssert' defined in *ABS* section in main.elf
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `loc_FF875FB8':
boot.c:(.text+0x694): relocation truncated to fit: R_ARM_PC24 against symbol `_DebugAssert' defined in *ABS* section in main.elf
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `loc_FF865848':
boot.c:(.text+0x724): additional relocation overflows omitted from the output
collect2: ld returned 1 exit status
make[1]: *** [main.elf] Error 1
-
with gcc 4.3.3: (there could be something else, i don't remember exactly...this is what i get from a stock trunk, just a make)
first occurrence: ../platform/g12/libplatform.a(shooting.o): arm call to thumb
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `sub_FF815EE0_my':
boot.c:(.text+0x2f8): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
boot.c:(.text+0x308): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
boot.c:(.text+0x31c): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
boot.c:(.text+0x330): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
boot.c:(.text+0x340): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
boot.c:(.text+0x350): relocation truncated to fit: R_ARM_PC24 against symbol `_err_init_task' defined in *ABS* section in main.elf
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `loc_FF81FB98':
boot.c:(.text+0x3a4): relocation truncated to fit: R_ARM_PC24 against symbol `_eventproc_export_SleepTask' defined in *ABS* section in main.elf
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `init_file_modules_task':
boot.c:(.text+0x43c): relocation truncated to fit: R_ARM_PC24 against symbol `_eventproc_export_PostLogicalEventToUI' defined in *ABS* section in main.elf
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `sub_FF876518_my':
boot.c:(.text+0x484): relocation truncated to fit: R_ARM_PC24 against symbol `_DebugAssert' defined in *ABS* section in main.elf
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `loc_FF875FB8':
boot.c:(.text+0x694): relocation truncated to fit: R_ARM_PC24 against symbol `_DebugAssert' defined in *ABS* section in main.elf
../platform/g12/sub/100c/libplatformsub.a(boot.o): In function `loc_FF865848':
boot.c:(.text+0x724): additional relocation overflows omitted from the output
collect2: ld returned 1 exit status
make[1]: *** [main.elf] Error 1
Those are firmware addresses defined using the NSTUB macro in stubs_entry_2.s - they work fine with gcc 4.5.1. Looks like a gcc problem; but I don't know it well enough to say for sure.
Phil.
-
yep i saw that (and fixed with a simple s//)..surely it's a gcc issue..sooner or later i have to get back in track with updated tools :)
-
Hi - I'm totally new to CHDK, but I wondered:
Can you modify the firmware to enable manual audio level control? For use for example at a noisy concert so that the resulting audio doesn't sound distorted?
thanks
PS. Loving the zoom during video capture...
-
Hello
First I want to thank you for your work. Maybe I have found a mistake. If I use the optical zoom in video-mode and go over 5x (then I use digital zoom) I can't zoom out completely. I only can use the digital zoom. After I turn off and on the camera everything work fine. I hope you can understand, because my English isn't so good. :)
Michael
-
Deleted by a craven coward
-
@philmoz
I try to get the 16:9 Mode working with your new added Code in chdk.But when a x offset is need, the position of zebra, or grid is not shift in X
You can test this on a G12 in 1:1 shooting mode(here your 4:3 display have in x on both side a black border and its simular as 4:3 mode on a 16:9 display i think)
Please let me know if that work.
I add in lib.c this funcs but it do not work ok, because the offset in X is not add.
int vid_get_viewport_buffer_width() { return 480; }
int vid_get_viewport_width()
{
if (shooting_get_prop(PROPCASE_ASPECT_RATIO) == 1) // 16:9 is set to 1
return 480;
else
return 360;
}
int vid_get_viewport_xoffset()
{
if (shooting_get_prop(PROPCASE_ASPECT_RATIO) == 1) //16:9 is set to 1
return 0;
else
return 60;
}
int vid_get_viewport_image_offset() {
return (vid_get_viewport_yoffset() * vid_get_viewport_buffer_width() + vid_get_viewport_xoffset()) * 3;
}
int vid_get_viewport_row_offset() {
return (vid_get_viewport_buffer_width() - vid_get_viewport_width()) * 3;
}
-
please, canon g12 enter manual checks video manual control , iso , iris..
disable acg, increse bitrate.
this new camera canon g12 the sensor ccd no cmos
absolutely nothing rolling shutter
good depth of field 10megapixel
720p 20mbit
Someone can help in the development of this change??
-
I installed it onto the card.
I made the card bootable, but it does not actually load..no splash screen..
Any idea what I am doing wrong?
-
Hey, I'm new to CHDK. I just got the g12 and I'm ready to trick it out. I was wondering if you can increase the range of the manual exposure or if it has been done before? This is a great camera, but thats one thing that seems to be a weak point for it.
-
@philmoz
I try to get the 16:9 Mode working with your new added Code in chdk.But when a x offset is need, the position of zebra, or grid is not shift in X
You can test this on a G12 in 1:1 shooting mode(here your 4:3 display have in x on both side a black border and its simular as 4:3 mode on a 16:9 display i think)
Please let me know if that work.
I add in lib.c this funcs but it do not work ok, because the offset in X is not add.
int vid_get_viewport_buffer_width() { return 480; }
int vid_get_viewport_width()
{
if (shooting_get_prop(PROPCASE_ASPECT_RATIO) == 1) // 16:9 is set to 1
return 480;
else
return 360;
}
int vid_get_viewport_xoffset()
{
if (shooting_get_prop(PROPCASE_ASPECT_RATIO) == 1) //16:9 is set to 1
return 0;
else
return 60;
}
int vid_get_viewport_image_offset() {
return (vid_get_viewport_yoffset() * vid_get_viewport_buffer_width() + vid_get_viewport_xoffset()) * 3;
}
int vid_get_viewport_row_offset() {
return (vid_get_viewport_buffer_width() - vid_get_viewport_width()) * 3;
}
Zebra works correctly for me in all of the shooting modes on the G12.
Have you included the zebra code updates in gui_osd.c that use the new functions in lib.c?
Regards,
Phil.
-
Hello
First I want to thank you for your work. Maybe I have found a mistake. If I use the optical zoom in video-mode and go over 5x (then I use digital zoom) I can't zoom out completely. I only can use the digital zoom. After I turn off and on the camera everything work fine. I hope you can understand, because my English isn't so good. :)
Michael
That's a known issue (listed on the first post in this thread).
I haven't found a solution for this yet.
Regards,
Phil.
-
I think i found a problem. I installed it and right after i when into the menu and adjusted a few settings i clicked alt to get back out and now my screen is white with a occasional bit of the screen visible, however when i press alt again te screen is normal but i cant take pictures.
-
I think i found a problem. I installed it and right after i when into the menu and adjusted a few settings i clicked alt to get back out and now my screen is white with a occasional bit of the screen visible, however when i press alt again te screen is normal but i cant take pictures.
Can you provide more details of the settings you changed?
Alternatively you can delete the CCHDK.CFG file in the CHDK directory on the SD card to reset all the settings back to default. This file will be recreated when you restart the camera.
Regards,
Phil.
-
Hey, i've seen that zooming can lead to crashes of the camera. (e.g. zoom to max, then to 1)
using eventprocs manually i'm seeing that "PT_MoveOpticalZoomAt" is working well (must call "SS.Create" first though..)
however, if i hardcode it (just like you did with sx30, just calling _ExecuteEventProc() instead... i already used that trick for some other camera) the camera crashes. ideas?
edit:
calling the _ExecuteEventProc("PT_MoveOpticalZoomAt", val) in shooting.c instead of the usual wrappers.c place did the trick (with the previous call to ss.create, ofcourse).. very strange :)
-
Hey, i've seen that zooming can lead to crashes of the camera. (e.g. zoom to max, then to 1)
using eventprocs manually i'm seeing that "PT_MoveOpticalZoomAt" is working well (must call "SS.Create" first though..)
however, if i hardcode it (just like you did with sx30, just calling _ExecuteEventProc() instead... i already used that trick for some other camera) the camera crashes. ideas?
edit:
calling the _ExecuteEventProc("PT_MoveOpticalZoomAt", val) in shooting.c instead of the usual wrappers.c place did the trick (with the previous call to ss.create, ofcourse).. very strange :)
At the moment lens_set_zoom_point is not waiting for zoom_busy to go back to 0 after calling _MoveZoomLensWithPoint. This is because it sometimes gets stuck (zoom_busy stays at 1).
If you call set_zoom from scripts and change the zoom position too quickly (before the camera has finished setting the previous zoom) it can crash the camera.
I notice in the current changeset this is also a problem with the s95 and a workaround has been added - I will try this on the G12.
I had to use PT_MoveOpticalZoomAt on the SX30 because MoveZoomLensWithPoint did not work (crashed all the time). MoveZoomLensWithPoint seems to work on the G12.
Edit 19th Feb
I believe I've fixed the problem with calling set_zoom from scripts. Beta 5 has been posted with the fix.
Regards,
Phil.
-
does time lapse work yet?
-
I think i found a problem. I installed it and right after i when into the menu and adjusted a few settings i clicked alt to get back out and now my screen is white with a occasional bit of the screen visible, however when i press alt again te screen is normal but i cant take pictures.
I cant recall what settings i had changed, but i did as u said and the problem is gone. it works much better! Thank you for the help and i'm sure you hear this often, but THANK YOU for doing this and opening it up to this community for download!
Can you provide more details of the settings you changed?
Alternatively you can delete the CCHDK.CFG file in the CHDK directory on the SD card to reset all the settings back to default. This file will be recreated when you restart the camera.
Regards,
Phil.
-
does time lapse work yet?
Time lapse is not built into CHDK; but there are a number of time lapse (intervalometer) scripts that you can download.
See - http://chdk.wikia.com/wiki/UBASIC/Scripts#Intervalometer (http://chdk.wikia.com/wiki/UBASIC/Scripts#Intervalometer)
Regards,
Phil.
-
Zebra works correctly for me in all of the shooting modes on the G12.
Have you included the zebra code updates in gui_osd.c that use the new functions in lib.c?
Regards,
Phil.
I dont understand what you mean, i use the 1050 build, is this not in ?
I test also your aspect settings in camera.h.but this settings always work wrong on my Camera with 16:9 TFT display
IX1000 use the values that are add from the SX210 port.below you see sx 30 values
#undef ASPECT_XCORRECTION
#define ASPECT_XCORRECTION(x) (((x)<<1)) //correction x*screen_buffer_width/screen_width = x*960/480 = x*2/1
#undef ASPECT_GRID_XCORRECTION
#define ASPECT_GRID_XCORRECTION(x) ( ((x)<<3)/8 ) //grids are designed on a 360x240 basis and screen is 320x240, we need x*320/360=x*8/9 , 8 is the right value for sx210
#undef ASPECT_GRID_YCORRECTION
#define ASPECT_GRID_YCORRECTION(y) ( (y) ) //y correction for grids made on a 360x240 As the buffer is 720x240 we have no correction here.
#undef ASPECT_VIEWPORT_XCORRECTION
#define ASPECT_VIEWPORT_XCORRECTION(x) ASPECT_GRID_XCORRECTION(x) //viewport is 360x240 and screen 320x240, we need x*320/360=x*8/9, equal than grids, used by edgeoverlay
#undef ASPECT_VIEWPORT_YCORRECTION
#define ASPECT_VIEWPORT_YCORRECTION(y) ( (y) )
/* from sx30 do not work on 16:9 Camera display, so its deactive.
#undef ASPECT_XCORRECTION
#define ASPECT_XCORRECTION(x) ( ( ((x)<<3) + (x) ) >>2 ) //correction x*screen_buffer_width/screen_width = x*720/320 = x*9/4 = (x<<3 + x)>>2
//grids
#undef ASPECT_GRID_XCORRECTION
#define ASPECT_GRID_XCORRECTION(x) ( ((x)<<3)/9 ) //grids are designed on a 360x240 basis and screen is 320x240, we need x*320/360=x*8/9
#undef ASPECT_GRID_YCORRECTION
#define ASPECT_GRID_YCORRECTION(y) ( (y) ) //y correction for grids made on a 360x240 As the buffer is 720x240 we have no correction here.
//viewport
#undef ASPECT_VIEWPORT_XCORRECTION
#define ASPECT_VIEWPORT_XCORRECTION(x) ASPECT_GRID_XCORRECTION(x) //viewport is 360x240 and screen 320x240, we need x*320/360=x*8/9, equal than grids, used by edgeoverlay
#undef ASPECT_VIEWPORT_YCORRECTION
#define ASPECT_VIEWPORT_YCORRECTION(y) ( (y) )
*/
-
I mean with sources this from here.
http://tools.assembla.com/chdk/timeline (http://tools.assembla.com/chdk/timeline)
are this sources in release 1050 should be ok to get zebra working on Camera with 16:9 TFT display ?
-
I mean with sources this from here.
http://tools.assembla.com/chdk/timeline (http://tools.assembla.com/chdk/timeline)
are this sources in release 1050 should be ok to get zebra working on Camera with 16:9 TFT display ?
Yes all of the necessary code changes should be in 1050 (and later).
Do you have CAM_ZEBRA_ASPECT_ADJUST defined?
There are two different versions of gui_osd_draw_zebra in gui_osd.c based on whether CAM_ZEBRA_ASPECT_ADJUST is defined or not. My changes are only in the version where CAM_ZEBRA_ASPECT_ADJUST is defined. I don't have a camera that doesn't have this so I could not test any changes to the other version.
If the Ixus1000 doesn't define CAM_ZEBRA_ASPECT_ADJUST then you will need to modify the second version of gui_osd_draw_zebra to use the offset functions.
Regards,
Phil.
-
I mean with sources this from here.
http://tools.assembla.com/chdk/timeline (http://tools.assembla.com/chdk/timeline)
are this sources in release 1050 should be ok to get zebra working on Camera with 16:9 TFT display ?
Yes all of the necessary code changes should be in 1050 (and later).
Do you have CAM_ZEBRA_ASPECT_ADJUST defined?
There are two different versions of gui_osd_draw_zebra in gui_osd.c based on whether CAM_ZEBRA_ASPECT_ADJUST is defined or not. My changes are only in the version where CAM_ZEBRA_ASPECT_ADJUST is defined. I don't have a camera that doesn't have this so I could not test any changes to the other version.
If the Ixus1000 doesn't define CAM_ZEBRA_ASPECT_ADJUST then you will need to modify the second version of gui_osd_draw_zebra to use the offset functions.
Regards,
Phil.
I have in camera.h this in
#define CAM_ZEBRA_ASPECT_ADJUST 1
But i use for test a 3to2 grid.this draw on top and button only 2 lines
on a 16:9 shooting mode, it draw the lines not large enough.on a 4:3 shooting mode, it draw the lines at X 0, but should begin to draw at X60.
4:3 shoot mode on 16:9 display is simular in code as a 1:1 shoot mode on 4:3 display.
maybe i should first look wy grid not work, because code is not so complex as zebra
-
I have in camera.h this in
#define CAM_ZEBRA_ASPECT_ADJUST 1
I'll take another look at the code for the zebra offsets. If you have another camera it would help to see a photo of exactly what the zebra looks like when you choose 4:3 shooting mode.
But i use for test a 3to2 grid.this draw on top and button only 2 lines
on a 16:9 shooting mode, it draw the lines not large enough.on a 4:3 shooting mode, it draw the lines at X 0, but should begin to draw at X60.
4:3 shoot mode on 16:9 display is simular in code as a 1:1 shoot mode on 4:3 display.
maybe i should first look wy grid not work, because code is not so complex as zebra
The offset functions I added only affect zebra, histogram, motion detect and edge overlay. They don't do anything for grids.
As I understand it grids assume a 4:3 display and are hard wired for this - so the 3to2 grid defines two horizontal lines (at the top and bottom). These mark the area on the 4:3 LCD that a 3:2 image occupies. The grid is not altered by the shooting mode. if I select the 3:2 shooting mode then the grid and the image align on the G12, if I select 1:1 the grid still extends the full width of the LCD. In other words the grid is relative to the physical LCD regardless of the size and aspect ratio of the image within it.
On a 16:9 display you would need a different grid definition for a 3to2 grid - it should show as 2 vertical lines to mark the area a 3:2 image would occupy on the 16:9 LCD.
Regards,
Phil.
-
I'll take another look at the code for the zebra offsets. If you have another camera it would help to see a photo of exactly what the zebra looks like when you choose 4:3 shooting mode.
I have add value output of zebra.see that code
int gui_osd_draw_zebra(int show)
....
viewport_height = vid_get_viewport_height();
viewport_width = vid_get_viewport_width();
viewport_buffer_width = vid_get_viewport_buffer_width();
viewport_xoffset = vid_get_viewport_xoffset();
viewport_yoffset = vid_get_viewport_yoffset();
// debug output begin
static char osd_buf[64];
sprintf(osd_buf, "viewport_width :%8d ", viewport_width);
draw_txt_string(28, 3, osd_buf, conf.osd_color);
sprintf(osd_buf, "viewport_buffer_width %8d ", viewport_buffer_width);
draw_txt_string(28, 4, osd_buf, conf.osd_color);
sprintf(osd_buf, "viewport_xoffset :%8d ", viewport_xoffset);
draw_txt_string(28, 5, osd_buf, conf.osd_color);
// debug output end
when zebra is ok then
viewport_width 480
viewport_buffer_width 480
viewport_xoffset 0
when a 4:3 shooting mode is select, i get that values
viewport_width 360
viewport_buffer_width 480
viewport_xoffset 60
problem is that the left pos of the zebra draw is not shift by 60 pixels to right.
as you can see, on debug output, the code in lib look correct and return the x position
Canon Firmware draw the preview from X 60.on left side there is a black gap.so zebra need shift 60 Pixels to right.
i think when G12 is in 1:1 shoot mode
you should get simular values
viewport_width 240
viewport_buffer_width 360
viewport_xoffset 60
zebra buffer G12 use, i cannot use, maybe your code work only with zebra buffer now ?
EDIT:
I add code and shift grid 60 pixel to right work ok.In 4:3 shoot mode all is ok then.
But in 16:9 shoot mode, grid size is still too small.
I try to scale the values, but it seem float seem not work or my code is wrong.
when i calc the float value size vid_get_viewport_width /360 = 480 / 360.mean 1.33 in float
so the line that is draw, should be longer.because X 360* 1.33 = 478.8
void gui_grid_draw_osd(int force) {
struct gline *ptr;
+ int xoffs = vid_get_viewport_xoffset();
+ float size = vid_get_viewport_width() /360 ;
if (force || --interval==0) {
for (ptr=head; ptr; ptr=ptr->next) {
+ float x0 = ptr->x0*size+xoffs;
+ float x1 = ptr->x1*size+xoffs;
switch (ptr->type) {
case GRID_ELEM_LINE:
- draw_line(ptr->x0, ptr->y0, ptr->x1, ptr->y1, (conf.grid_force_color)?conf.grid_color:ptr->clf);
+ draw_line(x0, ptr->y0,x1, ptr->y1, (conf.grid_force_color)?conf.grid_color:ptr->clf);
......
change in other too
-
I have add value output of zebra.see that code
when zebra is ok then
viewport_width 480
viewport_buffer_width 480
viewport_xoffset 0
when a 4:3 shooting mode is select, i get that values
viewport_width 360
viewport_buffer_width 480
viewport_xoffset 60
problem is that the left pos of the zebra draw is not shift by 60 pixels to right.
as you can see, on debug output, the code in lib look correct and return the x position
Canon Firmware draw the preview from X 60.on left side there is a black gap.so zebra need shift 60 Pixels to right.
i think when G12 is in 1:1 shoot mode
you should get simular values
viewport_width 240
viewport_buffer_width 360
viewport_xoffset 60
zebra buffer G12 use, i cannot use, maybe your code work only with zebra buffer now ?
I can't see anything wrong so I'm stumped - as I said earlier it would help me a lot to see a photograph of what the 4:3 zebra looks like on the LCD.
Also does the edge-overlay work correctly or does it have a problem?
EDIT:
I add code and shift grid 60 pixel to right work ok.In 4:3 shoot mode all is ok then.
But in 16:9 shoot mode, grid size is still too small.
I try to scale the values, but it seem float seem not work or my code is wrong.
when i calc the float value size vid_get_viewport_width /360 = 480 / 360.mean 1.33 in float
so the line that is draw, should be longer.because X 360* 1.33 = 478.8
I haven't looked at the grid system closely so I don't know what the correct approach here would be. Are there any other cameras with 16:9 LCD's that have solved this?
Regards,
Phil.
-
I can't see anything wrong so I'm stumped - as I said earlier it would help me a lot to see a photograph of what the 4:3 zebra looks like on the LCD.
Also does the edge-overlay work correctly or does it have a problem?
here i have upload 3 images.you can see the zebra of the window is draw too far left and you can see the
debug output of the values.
http://www.zshare.net/download/869753874752dec8/ (http://www.zshare.net/download/869753874752dec8/)
Edge overlay too not work in shooting mode(same problem, is draw too much left).
but edge overlay work in play mode on 4:3 display.
maybe you have a idea how can fix this and it work with other Cams too ?
or is it possible that the buffer addresses are wrong.but i dont think so, because i see only problem, in 4:3 shoot mode.
// Live picture buffer (shoot not pressed) //ASM1989 keept like sx210
void *vid_get_viewport_live_fb()
{
return 0x0;
/*
//sx210 code left
void **fb=(void **)0x2180; // 0x2150 or 0x2180 (old SX200) ???? What for SX210
unsigned char buff = *((unsigned char*)0x2058); // found at FF84FA18 (guess work)
if (buff == 0) buff = 2; else buff--;
return fb[buff];*/
}
// OSD buffer //ASM1989 ixsu1000
void *vid_get_bitmap_fb()
{
return (void*)0x40471000; // found at FFA97414
}
// Live picture buffer (shoot half-pressed) //ASM1989 ixus1000
void *vid_get_viewport_fb()
{
return (void*)0x40587700; // found by search for VRAM Address @FFB4CB2C
}
// Histo etc. when in play mode maybe ?
void *vid_get_viewport_fb_d()
{
return (void*)(*(int*)(0x3230+0x58)); // found at FF877D10 (0x58 atFF877D48)
}
-
Hi ! Thanks for your development! ::)
Will in future works bracketing in continuous mode?? I miss it really in my g12. :'(
Regards
Manuel!!
-
here i have upload 3 images.you can see the zebra of the window is draw too far left and you can see the
debug output of the values.
Ah, now I understand - a picture really is worth a 1000 words :)
In your samples there is a zebra stripe down the right side of the image area - it looks like this was generated from the masked section of the image immediately to the right. This tells me that the xoffset is working for the bitmap buffer; but is looking at the wrong part of the viewport buffer to calculate the zebra.
I suspect that the sensor data is being stored left aligned in the viewport regardless of shooting mode and then displayed with an offset on the LCD. This is not how it works on the G12.
To test this try the change below and see what happens for zebra and edge overlay.
(Note this is not a good solution, ideally we need seperate xoffsets for the bitmap and viewport buffers; but that will take more work.)
void *vid_get_viewport_fb()
{
if ((mode_get()&MODE_MASK) == MODE_REC)
return (void*)(0x40587700-vid_get_viewport_xoffset()*3);
return (void*)0x40587700; // found by search for VRAM Address @FFB4CB2C
}
-
great, many thanks, now Zebra and edge overlay work perfect with your Fix
I only see that histogram seem not work correct.seem it read some random data.
I can produce the problem by do this steps.
switch on Camera, so it go direct to 4:3 or in Case of G12 to 1:1 shooting mode, and then move camera to a dark place(without press of shutter).now on my camera always the overexpose signal is show, and you can see that there are bright pixels in the history line at end .the problem was before your fix too in.so seem only histogramm code problem
when you switch mode during run from 16:9 to 4:3 then no overexpose is show, i guess the buffer keep some 16:9 data which is always read from 4:3 histogram.
only when you was in 16:9 mode and have a overexpose part, then its possible that 4:3 always show overexpose
EDIT:
maybe to get bracketing work G12 SX30 and some other define need add here.Ixus1000 and SX210 is add here too
http://chdk.setepontos.com/index.php?topic=5574.msg60231#msg60231 (http://chdk.setepontos.com/index.php?topic=5574.msg60231#msg60231)
@@ -736,10 +736,12 @@ short shooting_get_drive_mode()
736 736
defined (CAMERA_a480) || \
737 737
defined (CAMERA_s90) || \
738 738
defined (CAMERA_sx20) || \
739
- defined (CAMERA_d10)
739
+ defined (CAMERA_d10) || \
740
+ defined (CAMERA_ixus300_sd4000)
740 741
short n;
741 742
// unlike other cameras, sx200 does set PROPCASE_DRIVE_MODE when in custom timer mode
742 743
// SX 200 IS 0,1,2,3,4=Off, 2 Second, Custom, Face Detection
744
+ // SD4000: 0,1,2,3 = Off, 2 Seconds, Custom timer
743 745
_GetPropertyCase(PROPCASE_TIMER_MODE, &n, sizeof(n));
744 746
// note we return this only in custom mode.
745 747
// Other cameras would return 3 if any timer mode is set (?) even if it doesn't do multiple exposures
-
.
-
Just got CHDK going on my G12 last night. Works great! Thanks for all the hard work guys! I have been prodding the forum for one feature though. Does anything have any ideas how to get ETTL working in manual mode? As an underwater photographer It is one of the most irritating things that Cannon did in the G series cameras.
Keep up the good work guys :)
-
hello everyone,
ive got a little problem with bracketing in continuous mode. i would like to use the custom timer for tv-bracketing, but i dont know how to use it. bracketing with continuous shooting works very well, but the custom timer with exactly the same settings doesnt work.
Is it a problem of the g12 or am I the problem?
Custom Timer is better for bracketing because i can shoot without my hands on the camera to avoid camera shaking.
Greetings from Germany and thank you for your great work!
-
hello everyone,
ive got a little problem with bracketing in continuous mode. i would like to use the custom timer for tv-bracketing, but i dont know how to use it. bracketing with continuous shooting works very well, but the custom timer with exactly the same settings doesnt work.
Is it a problem of the g12 or am I the problem?
Custom Timer is better for bracketing because i can shoot without my hands on the camera to avoid camera shaking.
Greetings from Germany and thank you for your great work!
A fix for this will be in the next beta release - hopefully in the next few days.
Edit: Beta 6 has been uploaded that should fix this problem.
Phil.
-
so fast... thanks custom timer works well now!
-
I'm enjoying the port on my G12. Thank you for your work.
The G12 is pretty feature rich, and the biggest reason I built out my SD card with CHDK is to script HDR bracketing (5 shots at the moment). Although I can set_tv_rel I cannot get_tv and can't find a prop 0-300 to check or set Tv. I am shooting Manual Mode, but really the get_tv should work in any mode.
Ideally, if the camera is in autofocus, I would like to shoot_half (to focus) and then turn on manual focus so the focal point stays the same through the other shots.
I would love to see a prop/get_tv working, and secondary the ability to click "mf" (manual focus).
Thank you for your work, Charles "Revantine"
-
I'm enjoying the port on my G12. Thank you for your work.
The G12 is pretty feature rich, and the biggest reason I built out my SD card with CHDK is to script HDR bracketing (5 shots at the moment). Although I can set_tv_rel I cannot get_tv and can't find a prop 0-300 to check or set Tv. I am shooting Manual Mode, but really the get_tv should work in any mode.
Ideally, if the camera is in autofocus, I would like to shoot_half (to focus) and then turn on manual focus so the focal point stays the same through the other shots.
I would love to see a prop/get_tv working, and secondary the ability to click "mf" (manual focus).
Thank you for your work, Charles "Revantine"
I'm not an expert on scripting so I'm not entirely sure what part isn't working.
Can you post a sample script that you are having problems with so I can better understand the issue.
Thanks,
Phil.
-
I would like to thank all those who contribute to the build outs of CHDK!
Is it safe to put CHDK's latest beta (I believe 6) on the G12?
NOTE: I am used to CHDK on the G11...will it be very similar? (in use and in loading to SD card?)
-
I would like to thank all those who contribute to the build outs of CHDK!
Is it safe to put CHDK's latest beta (I believe 6) on the G12?
G12 builds are available from the autobuild server http://mighty-hoernsche.de/ (http://mighty-hoernsche.de/) It should be approximately as a safe (or unsafe) as any other CHDK version.
NOTE: I am used to CHDK on the G11...will it be very similar? (in use and in loading to SD card?)
Pretty much identical.
-
I'm enjoying the port on my G12. Thank you for your work.
The G12 is pretty feature rich, and the biggest reason I built out my SD card with CHDK is to script HDR bracketing (5 shots at the moment). Although I can set_tv_rel I cannot get_tv and can't find a prop 0-300 to check or set Tv. I am shooting Manual Mode, but really the get_tv should work in any mode.
Ideally, if the camera is in autofocus, I would like to shoot_half (to focus) and then turn on manual focus so the focal point stays the same through the other shots.
I would love to see a prop/get_tv working, and secondary the ability to click "mf" (manual focus).
Thank you for your work, Charles "Revantine"
I'm not an expert on scripting so I'm not entirely sure what part isn't working.
Can you post a sample script that you are having problems with so I can better understand the issue.
Thanks,
Phil.
A simple script to see the Av, it gets it, then print a number the corresponds to the setting.
The a and t are variables and have arbitrary names.
get_av a
print "av ",a
You can also get it be property
get_prop 26 a
print "av ",a
This should print a number for the shutter speed
get_tv t
print "tv ",t
There is an lua script that dumps all the properties at http://chdk.wikia.com/wiki/Lua/Lua_Reference (http://chdk.wikia.com/wiki/Lua/Lua_Reference)
You run the script and it records the current values, change the Tv, run it again and it will list props that have changed.
-
A very big thank you - again - to all that made chdk available for the G12.
I seem to have one issue I did not have before with CHDK on the PowerShot A640: I cannot run timelapse scripts when the screen is turned off. I'm running some timelapse scripts that work fine when the screen is on, but it looks like I cannot activate CHDK once the screen is off.
==> Does anyone has the same issue? (with beta 6 and beta 8)
==> Is there a way to turn off the screen in the script itself?
Many thanks in anycase!
-
A simple script to see the Av, it gets it, then print a number the corresponds to the setting.
The a and t are variables and have arbitrary names.
get_av a
print "av ",a
You can also get it be property
get_prop 26 a
print "av ",a
This should print a number for the shutter speed
get_tv t
print "tv ",t
On the G12:
Property 26 is USER_AV, the equivalent function to get this value is get_user_av96.
Property 268 is USER_TV, the equivalent function to get this value is get_user_tv96.
The corresponding functions to set these values are set_user_av96 and set_user_tv96.
There is no 'get_tv' ubasic command (and there has not been one in CHDK for a long time) - using 'get_tv' will crash the camera.
Phil.
-
A very big thank you - again - to all that made chdk available for the G12.
I seem to have one issue I did not have before with CHDK on the PowerShot A640: I cannot run timelapse scripts when the screen is turned off. I'm running some timelapse scripts that work fine when the screen is on, but it looks like I cannot activate CHDK once the screen is off.
==> Does anyone has the same issue? (with beta 6 and beta 8)
==> Is there a way to turn off the screen in the script itself?
Many thanks in anycase!
Under the CHDK ALT Menu, select the 'Miscellaneous stuff' menu.
In here you can set the 'Disable LCD off' value - setting it to Script will stop the camera turning of the LCD while scripts are running.
Phil.
-
A simple script to see the Av, it gets it, then print a number the corresponds to the setting.
The a and t are variables and have arbitrary names.
get_av a
print "av ",a
You can also get it be property
get_prop 26 a
print "av ",a
This should print a number for the shutter speed
get_tv t
print "tv ",t
On the G12:
Property 26 is USER_AV, the equivalent function to get this value is get_user_av96.
Property 268 is USER_TV, the equivalent function to get this value is get_user_tv96.
The corresponding functions to set these values are set_user_av96 and set_user_tv96.
There is no 'get_tv' ubasic command (and there has not been one in CHDK for a long time) - using 'get_tv' will crash the camera.
Phil.
Thank you Phil. I'm not sure how I missed 268 (it of course works). I didn't know about the get_user_tv96.
Thank you again, Charles
-
Phil, is it possible to switch to manual focus mode on the G12 from script?
-
I would like to thank all those who contribute to the build outs of CHDK!
Is it safe to put CHDK's latest beta (I believe 6) on the G12?
G12 builds are available from the autobuild server http://mighty-hoernsche.de/ (http://mighty-hoernsche.de/) It should be approximately as a safe (or unsafe) as any other CHDK version.
NOTE: I am used to CHDK on the G11...will it be very similar? (in use and in loading to SD card?)
Pretty much identical.
Hmmmm, cant seem to get this to work. I had G11 CHDK on an SDHC 4BG card and it worked fine. SO I used CardTrick to overlay CHDK to SDHC using overright..but it doesnt seem to have worked.
WHen I put my card in, locked, nothing happens..the camera can not boot.
Should I reformat and do that way?
-
The link you gave me doesnt seem to work
There are DNS issues with the autobuild server at the moment, use http://hacki.someserver.de/ (http://hacki.someserver.de/) instead
-
^^^ Thanks. that worked.
I have scripts that I downloaded for the G11 (Ltng1-MDFB-080914.bas and mint.lua) will these continue to work for the G12, or I do I need to find new G12 scripts?
Also, I am trying to run scripts...however, when I got into ALT mode, press the Set button, I get the Script Menu, then I select Load script from File...(i use the set button again to select this menu option). When I do this, it starts the default script, takes a picture and then somewhat gets stuck. I cant get to the select script menu to select a script!
Lastly (for this post :) ) what is the white bar on the bottom of my screen (when in CHDK mode) that goes 1/2 way across from left to right?
-
I have scripts that I downloaded for the G11 (Ltng1-MDFB-080914.bas and mint.lua) will these continue to work for the G12, or I do I need to find new G12 scripts?
Depends on the script. Some scripts refer to propcases ( http://chdk.wikia.com/wiki/PropertyCase (http://chdk.wikia.com/wiki/PropertyCase) ) by number, and in some cases these numbers are different between camera models. G11 is propset 3, g12 is propset 4. Many propcases are the same in these two, so there may not be a problem.
There may be other features or issues unique to the ports, these are for you to discover either by running into them yourself or reading the experiences of other users with these cameras ;)
Also, I am trying to run scripts...however, when I got into ALT mode, press the Set button, I get the Script Menu, then I select Load script from File...(i use the set button again to select this menu option). When I do this, it starts the default script, takes a picture and then somewhat gets stuck.
I don't understand. The set button should not start a script, it just loads it. The currently loaded script will be shown when you are in alt mode, but it isn't running. To run the script, you must press the shutter button. You can press the shutter again to interrupt the script.
Lastly (for this post :) ) what is the white bar on the bottom of my screen (when in CHDK mode) that goes 1/2 way across from left to right?
It's the free space bar, one of CHDKs many redundant free space displays ;) Can be turned off in the OSD settings.
-
^^^^
I know the set button shouldnt run any scripts but it does..not even sure what it is running as I dont even have any, except the default, on the SDHC card.
I have the C build for the G12 if that helps...anyone know what might be going on?
Am I correct to press the Set button to load up the list of scripts and navigate to the script location?
-
Phil, is it possible to switch to manual focus mode on the G12 from script?
There is no script function to set manual focus; but you can use the 'click' function to simulate pressing the buttons on the camera.
If you are in auto focus mode then:
click "up"
click "set"
should set manual focus.
Regards,
Phil.
-
^^^^
I know the set button shouldnt run any scripts but it does..not even sure what it is running as I dont even have any, except the default, on the SDHC card.
I have the C build for the G12 if that helps...anyone know what might be going on?
Am I correct to press the Set button to load up the list of scripts and navigate to the script location?
The 'Set' button should not run any scripts.
Does the 'default.bas' script file in CHDK/Scripts exist and have a size of 0 bytes?
You can also try deleting you config file CHDK/CCHDK.CFG and see if that helps.
Phil.
-
^^^ My default.bas script was empty and I even tried deleting the CHDK/cchdk.cfg file. Still when I press the Shortcut to go into Alt mode (At bottom of the screen, I see Default Script <ALT>, then press Set to get my menu. The first option is "Load Script from file..." I am pressing Set to go into that menu..but as soon as I press Set...it launches (I think) the default script (which is empty) and it takes a picture, then kind of gets stuck from there. I can end the script by pressing Shutter.
Even if I ShortCut into <ALT> mode, then press menu for the Main Menu and go to the Scripting Parameter menu...from there if I take the "Load script from file..." menu, it just takes a picture when I press func/set button. NOTE: I do see the "file browser" for a split second, but then it takes a picture and then kind of stays in Picture Hold mode and I have to turn off/on the camera to get back to operational.
Odd!
-
^^^ My default.bas script was empty and I even tried deleting the CHDK/cchdk.cfg file. Still when I press the Shortcut to go into Alt mode (At bottom of the screen, I see Default Script <ALT>, then press Set to get my menu. The first option is "Load Script from file..." I am pressing Set to go into that menu..but as soon as I press Set...it launches (I think) the default script (which is empty) and it takes a picture, then kind of gets stuck from there. I can end the script by pressing Shutter.
Even if I ShortCut into <ALT> mode, then press menu for the Main Menu and go to the Scripting Parameter menu...from there if I take the "Load script from file..." menu, it just takes a picture when I press func/set button. NOTE: I do see the "file browser" for a split second, but then it takes a picture and then kind of stays in Picture Hold mode and I have to turn off/on the camera to get back to operational.
Odd!
Very odd indeed.
Are you using the autobuild version or my beta version from code.google.com?
If you are using the autobuild can you try the latest from http://code.google.com/p/chdk-g12/downloads/list (http://code.google.com/p/chdk-g12/downloads/list) and let me know what happens.
Phil.
-
Very odd indeed.
Are you using the autobuild version or my beta version from code.google.com?
If you are using the autobuild can you try the latest from http://code.google.com/p/chdk-g12/downloads/list (http://code.google.com/p/chdk-g12/downloads/list) and let me know what happens.
Phil.
I must have been using the former...I downloaded from your beta version and I can now go about selecting a script. I will play around with it more later but it seems to have resolved my issue.
Thanks!
-
Thanks Philmoz for getting me what appears to be the right build. I can operate my scripts now. Now I am off for some fun!
I dont have one bit of feed back. When I go into <Alt> Mode, then press Set to get to the script menu...when I select my script I return to the Script parameter menu. From there, I can not execute the <- Back menu option. It wont do anything, no matter what I press.
I have to just press the Shortcut button to clear out of that menu.
-
Thanks Philmoz for getting me what appears to be the right build. I can operate my scripts now. Now I am off for some fun!
I dont have one bit of feed back. When I go into <Alt> Mode, then press Set to get to the script menu...when I select my script I return to the Script parameter menu. From there, I can not execute the <- Back menu option. It wont do anything, no matter what I press.
I have to just press the Shortcut button to clear out of that menu.
The 'Back' option on the scripts menu is to get back to the previous menu - it's used when you navigate to the 'Scripting parameters' menu from the main menu.
When you press Set in ALT mode you jump straight to the scripts menu so there's nowhere to go 'back' to. It would probably be sensible for 'Back' to close the menu in this case; but that's not the way it was written (it's the same on all cameras).
If you press the Menu button it will close the scripts menu without leaving ALT mode.
Phil.
-
Another instance of the mysterious shoot in script menu issue http://chdk.setepontos.com/index.php?topic=6299.0 (http://chdk.setepontos.com/index.php?topic=6299.0)
Phil, can you have a look at what might be different in your build and autobuild ?
-
Another instance of the mysterious shoot in script menu issue http://chdk.setepontos.com/index.php?topic=6299.0 (http://chdk.setepontos.com/index.php?topic=6299.0)
Phil, can you have a look at what might be different in your build and autobuild ?
I can reproduce it (using the current autobuild version); but not sure what's causing it.
Will post a patch when I've figured it out.
Edit: Weird. If I download the autobuild 1143 version I get this problem. If I build 1143 from the SVN source (unmodified) I don't get the problem! The autobuild DISKBOOT.BIN is about 3K larger than mine.
What version of gcc is the autobuild server using? I'm using gcc 4.5.2 in Windows to build.
Here's what I've found (using version 1143 from SVN):
gcc 4.5.1 - no problem (DISKBOOT.BIN is 253K)
gcc 4.4.0 - camera goes crazy when entering the file browser from any menu (DISKBOOT.BIN is 256K)
gcc 3.4.6 - no problem (DISKBOOT.BIN is 271K)
Edit2:
It appears to be a bug in gcc 4.4.0 when compiling the 'readdir' function in generic/wrappers.c.
The code generated by gcc 4.4.0 is passing the wrong address to _ReadFastDir for the second parameter.
A small change fixes it, will post a patch shortly.
Phil.
-
Phil, is it possible to switch to manual focus mode on the G12 from script?
There is no script function to set manual focus; but you can use the 'click' function to simulate pressing the buttons on the camera.
If you are in auto focus mode then:
click "up"
click "set"
should set manual focus.
Regards,
Phil.
I must leave ALT mode to change the MF mode (by pressing up), and the click actions failed as well. Is the user (me) broken? Did I miss a menu item, or command. Or is this expected behavior?
Thank you again.
-
-
-
Hi Phil, can you spot what R the differences in 1.00F from E or C ?
-
Hi Phil, can you spot what R the differences in 1.00F from E or C ?
Only minor differences between 1.00e and 1.00f. 1.00f patch has been submitted, should be on the autobuild server soon. Or you can use CHDK Shell to build it manually.
Phil.
-
Tnx, No I have G12 1.0e so I was wondering what Canon twiked for the 1.0f.
As it is very debatable why the do not issue firmware upgrades anymore.
-
Tnx, No I have G12 1.0e so I was wondering what Canon twiked for the 1.0f.
As it is very debatable why the do not issue firmware upgrades anymore.
Pretty much impossible to say what was changed. The code changes are buried deep in the firmware and not easily understood.
Canon rarely release firmware updates unless critical problems are found.
Phil.
-
Using a G12 with firmware F downloaded from here http://mighty-hoernsche.de/. (http://mighty-hoernsche.de/.) I set the custom auto iso on, and max 20 but the camera still uses mainly iso 500 for flash shots on auto iso. Using auto mode or P mode doesn't make any difference. Am I missing another setting somewhere? Any thoughts? Thanks in advance!
Scott
-
Using a G12 with firmware F downloaded from here http://mighty-hoernsche.de/. (http://mighty-hoernsche.de/.) I set the custom auto iso on, and max 20 but the camera still uses mainly iso 500 for flash shots on auto iso. Using auto mode or P mode doesn't make any difference. Am I missing another setting somewhere? Any thoughts? Thanks in advance!
Scott
It does work; but...
The ISO values in the Custom Auto ISO overrides aren't equal to the Canon ISO values you see on screen (it's this whole complicated thing about market versus real ISO which I won't go into - partly because I don't understand it all).
A value of 10 in 'Max ISO Auto (x10)' will lock the Canon max ISO to 160, 20 = 320, etc.
Experiment with the values to find what you need.
Phil.
-
It does work; but...
The ISO values in the Custom Auto ISO overrides aren't equal to the Canon ISO values you see on screen (it's this whole complicated thing about market versus real ISO which I won't go into - partly because I don't understand it all).
A value of 10 in 'Max ISO Auto (x10)' will lock the Canon max ISO to 160, 20 = 320, etc.
Experiment with the values to find what you need.
Phil.
[/quote]
If max 20=320, then why does it use 500 when I set it to 20?
-
If max 20=320, then why does it use 500 when I set it to 20?
Auto ISO is disabled in M and TV modes, or if the flash is set to auto.
Phil.
-
If max 20=320, then why does it use 500 when I set it to 20?
Auto ISO is disabled in M and TV modes, or if the flash is set to auto.
Phil.
P mode , Flash ON, and ISO still goes up to 500 when I set custom auto iso to 20.
-
If max 20=320, then why does it use 500 when I set it to 20?
Auto ISO is disabled in M and TV modes, or if the flash is set to auto.
Phil.
P mode , Flash ON, and ISO still goes up to 500 when I set custom auto iso to 20.
Flash On or Flash Auto (is there an 'A' displayed on the flash icon)?
Flash On will work; but as I said Custom ISO is disabled in Flash Auto mode (no idea why, that's the way the code code is written).
Phil.
-
If max 20=320, then why does it use 500 when I set it to 20?
Auto ISO is disabled in M and TV modes, or if the flash is set to auto.
Phil.
P mode , Flash ON, and ISO still goes up to 500 when I set custom auto iso to 20.
Flash On or Flash Auto (is there an 'A' displayed on the flash icon)?
Flash On will work; but as I said Custom ISO is disabled in Flash Auto mode (no idea why, that's the way the code code is written).
Phil.
Yep flash forced ON, not auto. On another note, I thought I read somewhere about there being another version of chdk that has more video options than the standard autobuild. Is there such a version? Where can I find it? Is the video quality of the G12 able to be noticeably improved upon? Thank for all the replies Phil!
-
Yep flash forced ON, not auto. On another note, I thought I read somewhere about there being another version of chdk that has more video options than the standard autobuild. Is there such a version? Where can I find it? Is the video quality of the G12 able to be noticeably improved upon? Thank for all the replies Phil!
Well I'm stumped - it works fine on my camera with firmware 1.00c.
I'll take a look to see if I can see any other reasons and get back to you.
Not sure what you mean by more video options - CHDK allows you to override the video bit rate, and enable optical zoom on the G12 (these are under the Video parameters menu).
Phil.
-
Yep flash forced ON, not auto. On another note, I thought I read somewhere about there being another version of chdk that has more video options than the standard autobuild. Is there such a version? Where can I find it? Is the video quality of the G12 able to be noticeably improved upon? Thank for all the replies Phil!
Well I'm stumped - it works fine on my camera with firmware 1.00c.
I'll take a look to see if I can see any other reasons and get back to you.
Not sure what you mean by more video options - CHDK allows you to override the video bit rate, and enable optical zoom on the G12 (these are under the Video parameters menu).
Phil.
Well, I figured it out. You have to set "Disable Overides" to "Off". I had it set to "Disable". I don't understand why there are 3 options... disable,off,enable. When I had it on disable it would still show the message "auto iso on" while shooting so I don't understand what the disable option does.
Video wise, just wondering if there is anything better.
-
...I don't understand why there are 3 options... disable,off,enable.
--> http://chdk.wikia.com/wiki/CHDK_User_Manual#Disable_Overrides (http://chdk.wikia.com/wiki/CHDK_User_Manual#Disable_Overrides)
-
Hello to everyone, first at all I'm happy to see this type of improvment of the camera features with CHDK software.
I'm here with one problem, I buy my first Canon camera on december 2010, is an PowerShot G12. When I buy the camera
I was happy but after few pictures I discover "HOT PIXELS" on each picture I made. I was very disappointed about the situation and disparate because in that moment I was thinking is something very bad with my camera, I go to the service (Canon original) and the problem was sort out in 20minutes, by "remaping" the senzor. Wich was good.
Now after 7 month I have the same problem with other "HOT PIXELS". I bring the camera to the service and they are very busy and keep me 15 day the camera to the service.
Now the big question: IT IS POSSIBLE TO HAVE THE REMAPPING SOFTWARE AT HOME ON AN CHDK VERSION OR SOMETHING?
Thank you.
-
Hello to everyone, first at all I'm happy to see this type of improvment of the camera features with CHDK software.
I'm here with one problem, I buy my first Canon camera on december 2010, is an PowerShot G12. When I buy the camera
I was happy but after few pictures I discover "HOT PIXELS" on each picture I made. I was very disappointed about the situation and disparate because in that moment I was thinking is something very bad with my camera, I go to the service (Canon original) and the problem was sort out in 20minutes, by "remaping" the senzor. Wich was good.
Now after 7 month I have the same problem with other "HOT PIXELS". I bring the camera to the service and they are very busy and keep me 15 day the camera to the service.
Now the big question: IT IS POSSIBLE TO HAVE THE REMAPPING SOFTWARE AT HOME ON AN CHDK VERSION OR SOMETHING?
Thank you.
http://chdk.wikia.com/wiki/Badpixel_removal (http://chdk.wikia.com/wiki/Badpixel_removal) may be useful.
-
Phill I read your answer in DPR forum about
"2011 models support CHDK autoboot from any size SD card, partitioning is no longer required for large cards. "
Will this be implement in G12 CHDK also?
-
Phill I read your answer in DPR forum about
"2011 models support CHDK autoboot from any size SD card, partitioning is no longer required for large cards. "
Will this be implement in G12 CHDK also?
Probably not, the boot process is controlled by the Canon firmware.
So unless Canon release a firmware update that adds this capability it won't happen.
This could also be a clever marketing strategy by Canon to encourage CHDK users to buy new cameras :)
Phil.
-
Oh, that's a bummer.
Canon marketing strategy is complete mystery to me.
Handicap important features on one side (intervalometer) while adding totally useless ones on the other side (Color swap)
-
What these last updates practically means ?
-Update for G12 & SX30 to support very large, partitioned SD cards
- Updated comments for G12 & SX30 to include correct firmware addresses for each version
-
What these last updates practically means ?
-Update for G12 & SX30 to support very large, partitioned SD cards
If you have an SD card that is larger than 32GB, and you partition it for CHDK, and you use Windows, then you can't format the large partition as FAT32. Windows will only allow it to be formatted as exFat.
The newer cameras support exFat partitions so this change allows CHDK to work in this configuration - with a small FAT16 partition to boot off, and a large exFat partition to store data.
- Updated comments for G12 & SX30 to include correct firmware addresses for each version
No functional changes in this patch - just updated some of the comments to avoid confusion.
Phil.
-
There is a free utility you can use to format partitions as FAT32:
http://www.partitionwizard.com/ (http://www.partitionwizard.com/)
You can also use this to partition the SD card with the small FAT16 partition though I used the CHDK function.
-
i personally don't have the camera but managed to obtain this dump
(note: while at it, i tried philmoz's new finsig and it's really great!)
g12 100g: http://www.zshare.net/download/9429181860714ee7/ (http://www.zshare.net/download/9429181860714ee7/)
-
Added the
full 8MB dump (most probably dumped with cBasic udumper) provided by c10ud from this forum post (http://chdk.setepontos.com/index.php?topic=5967.msg72618#msg72618) to the box.net/chdk (http://www.box.net/chdk) repository.
-
i personally don't have the camera but managed to obtain this dump
(note: while at it, i tried philmoz's new finsig and it's really great!)
g12 100g: http://www.zshare.net/download/9429181860714ee7/ (http://www.zshare.net/download/9429181860714ee7/)
Thanks for that.
Attached is a test version for firmware 1.00g if/when someone with this version want to try it.
Phil.
-
Hi Phil,
got the G12 the other day, found out about CHDK, got excited at first, then disappointed when I found out 100g was not supported, then excited again when I found this thread! :)
Tried your test version, as far as I can tell it works! It loads, has the CHDK menu and everything, even though as a first time user I cant really tell if anything's missing.
One weird thing I noticed: I changed the video setting to "quality" in the CHDK menu, and recording stopped after exactly 2mins. Got an 8GB SD Card with about 6GB free space.
Hooray for Phil, the hero user!
-
Hi Phil,
got the G12 the other day, found out about CHDK, got excited at first, then disappointed when I found out 100g was not supported, then excited again when I found this thread! :)
Tried your test version, as far as I can tell it works! It loads, has the CHDK menu and everything, even though as a first time user I cant really tell if anything's missing.
One weird thing I noticed: I changed the video setting to "quality" in the CHDK menu, and recording stopped after exactly 2mins. Got an 8GB SD Card with about 6GB free space.
Hooray for Phil, the hero user!
Do you get a flashing warning symbol at the top of the screen - this indicates the SD card isn't fast enough to write the video data.
What happens if you lower the quality value value?
Phil.
-
Phil, I recently bought 2GB class 2 SanDisk card just for CHDK, I record short 10-30" HD 1280 clips, no problem. Qt report ~18Mbit (CHDK report ~2.2Mb)
Nothing is flashing.
Using my 8Gb class10 Transcend, Qt report 19.2Mbit
What is the new "live view" feature in plain words? How can I use it?
-
Phil, I recently bought 2GB class 2 SanDisk card just for CHDK, I record short 10-30" HD 1280 clips, no problem. Qt report ~18Mbit (CHDK report ~2.2Mb)
Nothing is flashing.
Using my 8Gb class10 Transcend, Qt report 19.2Mbit
What is the new "live view" feature in plain words? How can I use it?
"Live view' is changes to the PTP code in CHDK to allow a program on your PC to download the LCD image data from the camera.
Once suitable client programs are developed it will make it possible to have remote control of the camera and be able to see the LCD image over the USB cable at the same time.
Phil.
-
Nice,
but you say that at the moment there isn't any program that implement this?
-
I just purcased a G12 after upgrading from an A590 where I had succes with CHDK.
I had the camera format my Sandisk 16gb SDHC card, loaded the proper build version, for 1.0e but i am not seeing the Firmware Update option at all, anywhere.
Any ideas ?
-
FYI I've formatted the card about 3 times, low level and normal, on different occasions and have copied the CHDK files to the card including the one necessary for the Firmware Update option to appear, the psi.f2 or whatever it's called.
I've tried pressing various buttons, tried pressing the Play button twice or more in succession, flipping back and forth between play and record, nothing.
I don't get it. The Firmware Update option that's supposed to appear in the menu in Play mode is just not there.
Firmware version GM1.00e
-
I figured it out:
When the camera if off, do NOT push the ON/OFF button. Simply push the Play button only.
Voila! It works.
-
FYI I've formatted the card about 3 times, low level and normal, on different occasions and have copied the CHDK files to the card including the one necessary for the Firmware Update option to appear, the psi.f2 or whatever it's called.
I've tried pressing various buttons, tried pressing the Play button twice or more in succession, flipping back and forth between play and record, nothing.
I don't get it. The Firmware Update option that's supposed to appear in the menu in Play mode is just not there.
Firmware version GM1.00e
You have to start the camera in playback mode using the rear 'review' button. Don't start the camera in record mode with the top on/off button then switch to playback mode. Once started immediately open the Canon menus and select 'Firm Update' from the bottom of the first menu.
If you are using a Mac then you may need to do additional steps when copying the files to the card (http://chdk.wikia.com/wiki/FAQ/Mac#You_may_have_issues_with_permissions. (http://chdk.wikia.com/wiki/FAQ/Mac#You_may_have_issues_with_permissions.)).
Phil.