long hook_raw_size()
{
return 0xEC04F0;
}
Hi, I'm a newbie of CHDK with some knowledge of assembly (but not ARM assembly :'( ).Nope. Assuming you've already found For Developers - CHDK Wiki (http://chdk.wikia.com/wiki/For_Developers) no better link exists. Nor is one likely to appear, because step by step tutorials aren't a substitute for understanding.
I did the dump of the firmware of my SX110IS and I disassembled it with IDA, helped by some sigs and idc.
The problem is that I can't find in all the wiki a full and well structured tutorial on how to proceed with the porting of CHDK.
Can someone help me with a good link?
14 bit RAW? :o
Nor is one likely to appear, because step by step tutorials aren't a substitute for understanding.I hope to be able to explain my point without misunderstanding due to my bad english.
It's a 8Mpixels, so .... 10 bit RAW??? :blink:
Anyway, why I can find only few IDA database (idb) of disassembled firmware?
For example it will be useful for me to find the SX100IS firmware fully disassembled.Maybe not only SX100, but also A650, A720 (it seems that these CHDK ports are complete and bug-free).
Yes, 10 bit RAW for all CHDK ported cameras.
10 bits for every channel (R, G and B) for a total of 30 bits or a total of 10 bits?
In the second case is the sensor able to record 1024 colours only?? :'(
In my perspective, a tutorial could be useful only to organize some little information as:If you look through an existing ports platform/<camera>/sub/<firmware version>/*.S these things are pretty obvious. See also include/lowlevel.h and platform/generic/*, and be sure you understand Signature finder - CHDK Wiki (http://chdk.wikia.com/wiki/Signature_finder)
1) The list of functions that anyone must find into a disassembled firmware;
2) The list of hardware pointers (leds, keyboard,free RAM ecc..)
Anyway, why I can find only few IDA database (idb) of disassembled firmware? For example it will be useful for me to find the SX100IS firmware fully disassembled.For any camera with a dump available, load the bin, apply the vxworks or dryos FLIRT, run the idc scripts. I suggest doing this with all the reference firmwares, and whatever camera is most similar to your own. You can also work backwards from the sig_ref*.txt or stubs_entry.S/stubs_entry_2.s from any camera.
but it can't reach the startup() into the platform\generic\main.c
However I still need to understand how to find the correct value for RESTARTSTARTSee here http://chdk.setepontos.com/index.php/topic,2361.msg21829.html#msg21829 (http://chdk.setepontos.com/index.php/topic,2361.msg21829.html#msg21829) , if it helps
is there any news about this porting?Sorry for my long absence. In the last weeks I was away due to my job. And probably I will be away for the next weeks too! :(
should be LDR R3,=task_CaptSeqTask_myShame on me!! :D I was very tired.
// not in sig_ref
NHSTUB(UnsetZoomForMovie, 0xFF9689EC) // string "ZoomCon_UnsetZoomForMovie"
NHSTUB(PT_PlaySound,0xFF863970) // search on PT_PlaySound
NHSTUB(PutInNdFilter,0xFFA46ED0) // string TurnOnNdFilter ? TODO!
NHSTUB(PutOutNdFilter,0xFFA46EF4) // string TurnOffNdFilter ? TODO!
NHSTUB(DoAFLock,0xFF863A80) // PT_DoAFLock
NHSTUB(UnlockAF,0xFF863A90) // PT_UnlockAF
// These don't exist/aren't found in dryos
NHSTUB(Mount_FileSystem,0xFF81093C) // NULLSUB
NHSTUB(Unmount_FileSystem,0xFF81093C) // NULLSUB
NHSTUB(rewinddir,0xFF81093C) // NULLSUB
NHSTUB(SetZoomActuatorSpeedPercent,0xFF81093C) // NULLSUB
As noted above, your mileage may vary depending on what features you have enabled.Actually I was wondering about JogDial_CW and JogDial_CCW in sub/lib.c.
modemap[] = {
{ MODE_VIDEO_STD, 2597 }, // video standby, sx10
{ MODE_VIDEO_STD, 3622 }, // video in progress, sx10
{ MODE_VIDEO_COMPACT, 2599 },
{ MODE_SCN_AQUARIUM, 16407 }, //16408 in sx10
{ MODE_SCN_SNOW, 16403 }, //16404 in sx10
{ MODE_SCN_FOLIAGE, 16403 }, //sx10
{ MODE_SCN_SUNSET, 16402 }, //sx10
{ MODE_SCN_NIGHT, 16398 },
{ MODE_SCN_ISO_3200, 16413 }, //sx10
{ MODE_SCN_FIREWORK, 16405 }, //16406 in sx10
{ MODE_SCN_BEACH, 16404 }, //16405 in sx10
{ MODE_INDOOR, 32785 },
{ MODE_KIDS_PETS, 32784 },
{ MODE_NIGHT_SNAPSHOT, 32779 },
{ MODE_LANDSCAPE, 32780 },
{ MODE_PORTRAIT, 32781 },
{ MODE_AUTO, 32768 },
{ MODE_P, 32772 },
{ MODE_TV, 32771 },
{ MODE_AV, 32770 },
{ MODE_M, 32769 }
}
Where can we get a working modemap from?
keys_mask* --> ???
{ 1, KEY_PRINT , 0x10000000 },
{ 1, KEY_ZOOM_IN , 0x00000100 },
{ 1, KEY_ZOOM_OUT , 0x00000200 },
{ 1, KEY_RIGHT , 0x00100000 },
{ 1, KEY_UP , 0x00020000 },
{ 1, KEY_DOWN , 0x00080000 },
{ 1, KEY_MENU , 0x02000000 },
{ 1, KEY_DISPLAY , 0x04000000 },
{ 1, KEY_SET , 0x00010000 },
{ 1, KEY_ERASE , 0x01000000 },
{ 1, KEY_LEFT , 0x00040000 },
{ 1, KEY_FACE , 0x08000000 },
{ 0, KEY_SHOOT_FULL, 0x0000000C },
{ 0, KEY_SHOOT_HALF, 0x00000004 },
- press "menu" button short --> thats the <ALT> key, CHDK will "activated" (@developers: I beg your pardon)
- press "disp" button --> you will get the CHDK menu
1. CRW file can't be seen by DNG4PS-2.
hello, i'm french and i bought sx110 since november and i would like to know if chdk sx110 is ported? i'm reading the forum and i found a method chdkj but i don't understand, thanks to help me and sorry for my poor english
Based on the assumption of a 10bit-sensor so 0xEC04F0 is to big. If 12bit and a 4:3 aspect ratio:
0xEC04F0 =15467760
15467760/12*8=10311840
10311840/0,75=13749120
sqrt(13749120)=3708
3708*0,75=2781
so real sensor size should be 3708x2781 ????
return 0xEC04F0;The same size as for SX10. But SX10 is 10 MP camera, SX110 - 9 MP ???
- Video Zoom: Unfortunately real video zoom doesn't work. Only digital zoom is available but thats not that glorious. I think (but I don't know) CHDK is not able to bypass that restriction.
Maybe I'm wrong, but I think CHDK was able to pass this restriction on SX 100. At least I've read it somewhere..
- We should implement the firmware update method for using CHDK on sx110 --> look at here: http://chdk.setepontos.com/index.php/topic,2995.0.html (http://chdk.setepontos.com/index.php/topic,2995.0.html)
Code-related issues:
--------------------
- include/camera.h: cam_CFAPattern, CAM_COLORMATRIX1, cam_CalibrationIlluminant1, CAM_ACTIVE_AREA_* and a few other things
- platform/<camera>/main.c: modemap --> as ewavr said: Using propertycase browser in debug menu (propcase #49).
static struct {
int hackmode;
int canonmode;
} modemap[] = {
{ MODE_VIDEO_STD, 2600 }, //Verified
{ MODE_VIDEO_COMPACT, 2602 }, //Verified
{ MODE_SCN_AQUARIUM, 16408 }, //Verified
{ MODE_SCN_SNOW, 16404 }, //Verified
{ MODE_SCN_FOLIAGE, 16403 }, //verified
{ MODE_SCN_SUNSET, 16402 }, //verified
{ MODE_SCN_NIGHT, 16398 }, //verified
{ MODE_SCN_ISO_3200, 16413 }, //verified
{ MODE_SCN_FIREWORK, 16406 }, //verified
{ MODE_SCN_BEACH, 16405 }, //verified
{ MODE_INDOOR, 32785 }, //verified
{ MODE_KIDS_PETS, 32784 }, //verified
{ MODE_NIGHT_SNAPSHOT, 32779 }, //verified
{ MODE_LANDSCAPE, 32780 }, //verified
{ MODE_PORTRAIT, 32781 }, //verified
{ MODE_AUTO, 32768 }, //verified
{ MODE_P, 32772 }, //verified
{ MODE_TV, 32771 }, //verified
{ MODE_AV, 32770 }, //verified
{ MODE_M, 32769 }, //verified
{ MODE_EASY, 33311 } //verified
};
- include/camera.h: properties need to be adjusted/corrected
#undef CAM_SENSOR_BITS_PER_PIXEL
#define CAM_SENSOR_BITS_PER_PIXEL 12
#undef CAM_WHITE_LEVEL
#define CAM_WHITE_LEVEL ((1<<CAM_SENSOR_BITS_PER_PIXEL)-1)
#define DNG_SUPPORT 1
gives error
"cannot load chdk/badpixel.bin
please run
chdk/scripts/test/badpixel.lua"
when trying to enable new DNG format
chdk/scripts/test/badpixel.lua"--> you'll find a small "enable DNG support" guidance here: http://chdk.setepontos.com/index.php/topic,2468.msg30870.html#msg30870 (http://chdk.setepontos.com/index.php/topic,2468.msg30870.html#msg30870)
- LCD screen sometimes flickering (red snow)
I have just little experience with this, but yes, I would say corrupted zebra..- LCD screen sometimes flickering (red snow)
Corrupted zebra?
hi guys!
is this chdk the final version or an alpha (or beta)?
is it possible to play divx videos with the camera or it needs a really hard firmware hack?
it work for me but i would like to shoot in raw and what raw file prefix, raw file extension, raw subtract prefix and raw subtract extension???? many thanks
Since chdkj had a reasonable status report I'll just update it with what i did today.
I attached a patch against svn revision 729 and the latest binaries.
Current status:
Solved:
-------
- keyboard: mixed keys, wrong assignment, JogDial up/down is swapped
i tried the "CHDK-sx110is-100b-0.9.7" but keys (ub/down) are still mixed.Keys definitly work fine on my cam, I might have accidentally attached an old copy can you try the one attached to this post?
Actually thought it was kinda of a neat feature no idea how it works though its all chdkj's magic that made it boot.i see. still... if you figure it out, or someone knows how to change it, let me know :)
Personally I don't like running CHDK all the time so use the firmware update method to start it. (copy the fi2 file to sdcard, hit play, hit menu , bottom option)
Can someone PLEASE tell me how I can get the long exposures, up to the 64 seconds?
I have been playing with the override shutter speed and I change it but using it in Manual or TV mode, it does not get changed, even with the "Disable Overrides" set to off.
So can someone please tell me the steps to do a long exposure? Then, the instructions should be the same for doing a sort shutter, right?
Someone with better knowledge could update the wiki-page? http://chdk.wikia.com/wiki/SX110IS (http://chdk.wikia.com/wiki/SX110IS)
Can someone PLEASE tell me how I can get the long exposures, up to the 64 seconds?
I have been playing with the override shutter speed and I change it but using it in Manual or TV mode, it does not get changed, even with the "Disable Overrides" set to off.
So can someone please tell me the steps to do a long exposure? Then, the instructions should be the same for doing a sort shutter, right?
Manual & TV Mode are good (P & Av show extreme exposure calculations)
Then you have to change
Shutterspeed enum type: from Ev Step to Factor
Set "Override shutter speed" to let's say 9
Set Value Factor to let's say 10
--> 9*10 = 90 sec Exposure!
:-)
--> Found in initial A580 Port Thread and subsequent "Long Exposure" Thread
it does not work for me...
i could not manage to override the exposure. the OSD shows me my overrided exposure time. but just when i press the shot-button it switches to the original one. (it does not matter if i am in P, Tv, Av or M mode)
Actually I can't make DNG4PS-2 that Yarvieh compiled to work. It says
F:\DCIM\100CANON\IMG_4114.CRW
Error: wrong_camera_type
When I go to options to specify the camera and go back to convert it doesn't say anything
Just writes
-----------
finish.
When I press "refresh" RAW file list dissipates. When I start program again everything starts again.
I used the latest CHDK from Yarvieh and put the newest Verion of CHDK full in it.
So now you have all languages, sample scripts, alternative symbols and so on.
If you already have CHDK you only have to copy the CHDK folder over the existing one.
To the battery values... The camera turns itself off at 2000mV and when recharged batteries are inserted, it shows 2700mV (NiMH GP ReCyko+). I'd set the upper value a little lower than 2700, maybe 2650 or 2600, so it would show 100% longer. Better than starting at 90% or so.
it does not work for me...
i could not manage to override the exposure. the OSD shows me my overrided exposure time. but just when i press the shot-button it switches to the original one. (it does not matter if i am in P, Tv, Av or M mode)
None of the overrides work, TV, AV, ISO.. all show up in the OSD but when you press the button the TV-value shows original and the rest show the overrided value but none is affected by the overrides. Could it be similar problem?: http://chdk.setepontos.com/index.php/topic,2654.msg24845.html#msg24845 (http://chdk.setepontos.com/index.php/topic,2654.msg24845.html#msg24845)
b) or eventually you have a wrong "general" button: --> First entry on "Extra Photo Operations" needs to be set to DISABLED (= do not "disable Overrides"!) :-) If it is set to "ON" it WILL disable the overrides..
I tryed it out and its set to disabled, but no override work :(
I got camera to crush. When temperature of optics is displayed everything fine. When ccd temperature displayed everything is fine but when battery temperature displayed or "all displayed" camera crushes.
At present stage if you like to convert RAW from sx110 you need to make sure that JPG and RAW are in the same folder. Get this http://chdk.setepontos.com/index.php?action=dlattach;topic=2838.0;attach=3205 (http://chdk.setepontos.com/index.php?action=dlattach;topic=2838.0;attach=3205). Make sure you don't go to options and change anything. This will break the program. Gently select a folder with RAW+JPG then select destination and press convert. If you do this it converts RAW to DNG very well.
At present stage if you like to convert RAW from sx110 you need to make sure that JPG and RAW are in the same folder. Get this http://chdk.setepontos.com/index.php?action=dlattach;topic=2838.0;attach=3205 (http://chdk.setepontos.com/index.php?action=dlattach;topic=2838.0;attach=3205). Make sure you don't go to options and change anything. This will break the program. Gently select a folder with RAW+JPG then select destination and press convert. If you do this it converts RAW to DNG very well.
I still can't get DNG4PS2 to work. It is just unable to locate any of my CRW files. I tried putting them together with the JPGs (using CHDK menu settings) but nothing changed. Is there any filename requirement? What is the download for? I tried overwrite the official DNG4PS2 build with the downloaded EXE file but it fails to start, saying something like "configuration is wrong". Am I missing something here? Thanks!
Confirmed.. same here. Sad
I didnt know these cameras have multiple temp sensors before trying CHDK Shocked Whats the use of them :/
CHDK loaded very well on my SX110 IS. I ran the bad pixel script and turned the DNG option on. However, RAW files, when opened in Lightroom, have a strange, saturated pink cast. Have tried all options (camera settings + WB correction) but to no avail. Is DNG for SX110 IS still been developed?
Thanks for all your hard work on this build, I buy Canon mainly because of CHDK :-)
hi!
a can't make the sd card bootable...
nothing happens when I choose this on the menu
Because this option isnt for DryOS Cams. Its an option for VxWorks Cams.Every day learn something new :o
At present stage if you like to convert RAW from sx110 you need to make sure that JPG and RAW are in the same folder. Get this http://chdk.setepontos.com/index.php?action=dlattach;topic=2838.0;attach=3205 (http://chdk.setepontos.com/index.php?action=dlattach;topic=2838.0;attach=3205). Make sure you don't go to options and change anything. This will break the program. Gently select a folder with RAW+JPG then select destination and press convert. If you do this it converts RAW to DNG very well.
I still can't get DNG4PS2 to work. It is just unable to locate any of my CRW files. I tried putting them together with the JPGs (using CHDK menu settings) but nothing changed. Is there any filename requirement? What is the download for? I tried overwrite the official DNG4PS2 build with the downloaded EXE file but it fails to start, saying something like "configuration is wrong". Am I missing something here? Thanks!
Make sure that you install http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en (http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en)
Hi
i installed the chdk into my sx110.
but i cant find the time lapse feature. Can someone point me out where i cab use the time lapse feature?
I want to take time lapse of clouds moving...
Regarding the Battery Power...
Would it be useful the distinguish between accumulators and batteries?
Regards.
Regarding the Battery Power...Hmmm, I thought that this could be in a more general interest. Ok, anybody could change upper/lower battery values in OSD. But this is a nice feature of a (let us say so) very technical nature. It might be more user friendly to preload some values or to change the calculation depending on the type of battery used. Just an idea...
Would it be useful the distinguish between accumulators (edit: rechargeable batteries) and batteries (edit: disposable batteries)?
Regards.
- RAW is under development by Yarvieh ? Do you need assistance?RAW Support is fine codewise you had no bugs in it. The problem is CAM_COLORMATRIX1 is off so the DNG files the cam exports are not quite in match with reality. I have been working with dave of dcraw to get sx110 support in there and actually with his instructions shot a macbeth colorchart. I have been unable though to get a decent color profile out of dng4ps-2. If anyone else wants to take a shot at it pictures available here (http://updates.lcdstudio.com/dave/).
- RAW is under development by Yarvieh ? Do you need assistance?RAW Support is fine codewise you had no bugs in it. The problem is CAM_COLORMATRIX1 is off so the DNG files the cam exports are not quite in match with reality. I have been working with dave of dcraw to get sx110 support in there and actually with his instructions shot a macbeth colorchart. I have been unable though to get a decent color profile out of dng4ps-2. If anyone else wants to take a shot at it pictures available here (http://updates.lcdstudio.com/dave/).
I Attached the diff against the latest svn rev 744. besides a little bit of messing with the color matrix no other changes.
done. attached is the final diff, in case anyone wanna take a look.Thank you!
basically you just have to put a diff in the forum and wait for a dev to check it in.
reyalp had a better and longer explanation of the process some days ago, but the board search is borked right now.
done. attached is the final diff, in case anyone wanna take a look.thanks :)
Fixed capt_seq.c. Really forgot to call shooting_expo_param_override() :o. Shame on me!:)
Shooting overrides should work now but didn't test this exhaustive.
capt_seq.c (for devs) and diskboot.bin (for others -- it's in the zip) are attached.
Suggest that we release a comprehensive update to the autobuild server after major changes only.
Cheers.
PS: Up to now there are over 500 download of CHDK for SX110IS ! Impressive !
Fixed capt_seq.c. Really forgot to call shooting_expo_param_override() :o. Shame on me!
Shooting overrides should work now but didn't test this exhaustive.
capt_seq.c (for devs) and diskboot.bin (for others -- it's in the zip) are attached.
Suggest that we release a comprehensive update to the autobuild server after major changes only.
Cheers.
I have been monitoring the development of CHDK for SX110 and am happy that beta code is now available for testing. When I pressed FUNC SET + DISP, I see on my SX110, Firmware Ver. 1.0.0.0 which is not listed as 1.00b for beta in the CHDK Wiki page. Why? How do I get version b so that it is compatible with the beta code?
Quick note - setting OSD all sensors display to 'on' crashes the camera.I'm going to check this in the next couple of days.
I have been monitoring the development of CHDK for SX110 and am happy that beta code is now available for testing. When I pressed FUNC SET + DISP, I see on my SX110, Firmware Ver. 1.0.0.0 which is not listed as 1.00b for beta in the CHDK Wiki page. Why? How do I get version b so that it is compatible with the beta code?
So I don't have to worry about this 1.00b stuff. I read about CardTricks already. But the Wiki page said you need to make sure your camera has the right firmware before selecting the right CHDK. I am confused.
....someone can compile a tutorial for all the functions (so many to access) and will be bulkier than the one with camera..LOL..
getting software to read these CRW files
I have been monitoring the development of CHDK for SX110 and am happy that beta code is now available for testing. When I pressed FUNC SET + DISP, I see on my SX110, Firmware Ver. 1.0.0.0 which is not listed as 1.00b for beta in the CHDK Wiki page. Why? How do I get version b so that it is compatible with the beta code?
Fixed capt_seq.c. Really forgot to call shooting_expo_param_override() :o. Shame on me!
Shooting overrides should work now but didn't test this exhaustive.
capt_seq.c (for devs) and diskboot.bin (for others -- it's in the zip) are attached.
Suggest that we release a comprehensive update to the autobuild server after major changes only.
Cheers.
Rear Curtain flash sync = works!
Shutter Override = works!
Aperture Override = works!
ISO override = works!
Great work chdkj!
Quick note - setting OSD all sensors display to 'on' crashes the camera.
Rear Curtain flash sync = works!
Shutter Override = works!
Aperture Override = works!
ISO override = works!
Great work chdkj!
Rear Curtain flash sync = works!
Shutter Override = works!
Aperture Override = works!
ISO override = works!
Great work chdkj!
for real??
somehow it does not work for me... i downloaded the "sx110is-100b-0.9.8-749-full.zip" from the autobildserver... and replaced the files on my SD-Card with these.
and it still does not work..
greetings
Quotegetting software to read these CRW files
try activating 'DNG Extension', that should help software identify it as DNG ...
Yes, it is.Quotegetting software to read these CRW files
try activating 'DNG Extension', that should help software identify it as DNG ...
Yeah - I gave that a shot first thing. No dice w/ every program I could find.
Thanks anyway though! I only hope that the "DNG format" option is on someone's shortlist.
for some reason it only works with an auto-bootMaybe, I did something wrong, but overrides do work even with fw update method. It's the same binary...
if i use the firmware update method, the overrides do not work
anyhow: nice work
Maybe, I did something wrong, but overrides do work even with fw update method. It's the same binary...
Yes, it is.Quotegetting software to read these CRW files
try activating 'DNG Extension', that should help software identify it as DNG ...
Yeah - I gave that a shot first thing. No dice w/ every program I could find.
Thanks anyway though! I only hope that the "DNG format" option is on someone's shortlist.
Yarvieh works really hard to get a proper color matrix for RAW develop process.
@obihoernchen, regarding to the list of problems and the last version of CHDK for sx110:
- I think problems no. 8+9 are solved. I didn't encounter problems with zoom wheel or shutter button anymore.
- No. 5 (rear curtain flash sync) seems to be solvedhttp://chdk.setepontos.com/index.php/topic,2838.msg32655.html#msg32655 (http://chdk.setepontos.com/index.php/topic,2838.msg32655.html#msg32655)
- No. 6 (print-key=<ALT> and auto-iso-shift) seems to be solved. Auto-ISO-shift works for me. Hyst has originally post this error (http://chdk.setepontos.com/index.php/topic,2838.msg32067.html#msg32067 (http://chdk.setepontos.com/index.php/topic,2838.msg32067.html#msg32067).
NHSTUB(GetBatteryTemperature, 0xffc387ec) //found at 0xffc3885c but camera crashs if used, so point to GetCCDTemperature
Just out of curiosity, would some explain to me why anyone would prefer the more involved "firmware upgrade" method instead of booting straight into CHDK? I really can't see the point.
I would like to say a big thanks and /kudos to everyone involved to this project. Special thanks to nomi_68k for starting all the process.
My question regards the latest build. Will i find it at CHDK-SVN Autobuild Download http://mighty-hoernsche.de/? (http://mighty-hoernsche.de/?)
Or should i look in this threat? As i have understand there are 2 builds from 2 diffrent persons?
Thanks in advance and keep up. I only wish i knew how to help
I enter ALT mode and the camera starts taking snaps..I have loaded the badpixel script to create the .bin file...but it wont even let me enter the menu...its starts taking continuous snaps... and it reads..'DONT PANIC. THIS MAY TAKE A FEW SECONDS' :o
should I reload the CHDK or...where am I going wrong... :-[
I am not sure if this is a bug or not.......Does the cam shut down with your empty batteries or does the camera only show a "dry" battery icon?
I am not using rechargeable battery's but one use. However they seem to finish very very quickly. I managed to take around 60 pictures without flash before battery's run out.
Or i should change something in chdk menu?
as long as nothing breaks existing code in the other cameras, we can check in your patches. no problem.Thank you indeed!
I am not sure if this is a bug or not.......Does the cam shut down with your empty batteries or does the camera only show a "dry" battery icon?
I am not using rechargeable battery's but one use. However they seem to finish very very quickly. I managed to take around 60 pictures without flash before battery's run out.
Or i should change something in chdk menu?
...
decided for me to release new versions of CHDK for SX110 as file
attachments of my posts in this forum. Of course, that means a lot of
"active reading" to those who want to test a new version. If someone has a
better idea...
For now there is only one active development build as far as I can see.
Yarvieh released a modified version some days ago. I took his modifications
and have them put in my code. So my releases containing his modifications.
Other changes are not known to me. And I will publish my code from time to
time....
Everyone is invited to participate. But someone has to collect all changes
and then release a new official build to the autobuild server.
all i can do is beta test and my only knowledge is on electricity unfortunately. I can modify my camera to real time measure battery's if that count and report back with info about the state of measures with and without CHDK.
If i can be in any other help please ask me to. I will be more than happy to do it.
The camera shut down completely with the change battery's info on screen after that.What are you thinking: do we have a problem with the battery indicator?
I could make a website for pre betas. I have enough free webspace^^:-)
all i can do is beta test and my only knowledge is on electricity unfortunately. I can modify my camera to real time measure battery's if that count and report back with info about the state of measures with and without CHDK.
If i can be in any other help please ask me to. I will be more than happy to do it.The camera shut down completely with the change battery's info on screen after that.What are you thinking: do we have a problem with the battery indicator?
From step to step...
A new version of CHDK for SX110!
Optical zoom in video record mode works now.
Please test video bitrate settings.
movie_record_task() in movie_rec.c must call unlock_optical_zoom()
explicitly because SX110 doesn't support this feature officially (as SX10
does). Therefore no call to unlock_optical_zoom() was necessary in
SX10-code (which I've used as template).
BTW, all camera dependent code related to movie record looks very different
to SX10 so movie_rec.c needs some other modifications. I've changed also the code that deals with video bitrate and quality settings (http://chdk.wikia.com/wiki/SX110IS#Known_bugs (http://chdk.wikia.com/wiki/SX110IS#Known_bugs)). But not tested yet...
That's one of the main problems in this port. SX110 is somehow in beetwen
SX100 and SX10. Some functions have to port like this and other like
that...
Attached is an archive with a new Binary and an other archive with my code (for developers, based on r749).
If video bitrate settings works than I will ask phyrephox to commit a new release to the autobuild server.
Any ideas for "GetBatteryTemperature"?
all i can do is beta test and my only knowledge is on electricity unfortunately. I can modify my camera to real time measure battery's if that count and report back with info about the state of measures with and without CHDK.
If i can be in any other help please ask me to. I will be more than happy to do it.The camera shut down completely with the change battery's info on screen after that.What are you thinking: do we have a problem with the battery indicator?
I cannot speak without testing and have to sleep right now. I will do it tomorrow.
It does not seem as a problem with battery indicator (battery read data) since unloading CHDK keeps showing empty battery.
Somehow loading CHDK doubled the power this camera needs? Is this an option? Maybe more things works and thats why this happens?
I will modify my camera tomorrow and test with 4 sets of battery's. 2 sets of rechargeable and 2 sets on one use battery's.
I will test every set with and without CHDK and i will report any findings.
all i can do is beta test and my only knowledge is on electricity unfortunately. I can modify my camera to real time measure battery's if that count and report back with info about the state of measures with and without CHDK.
If i can be in any other help please ask me to. I will be more than happy to do it.The camera shut down completely with the change battery's info on screen after that.What are you thinking: do we have a problem with the battery indicator?
I cannot speak without testing and have to sleep right now. I will do it tomorrow.
It does not seem as a problem with battery indicator (battery read data) since unloading CHDK keeps showing empty battery.
Somehow loading CHDK doubled the power this camera needs? Is this an option? Maybe more things works and thats why this happens?
I will modify my camera tomorrow and test with 4 sets of battery's. 2 sets of rechargeable and 2 sets on one use battery's.
I will test every set with and without CHDK and i will report any findings.
read this ;) http://chdk.wikia.com/wiki/FAQ#Q._Does_the_CHDK_program_consume_additional_battery_power.3F (http://chdk.wikia.com/wiki/FAQ#Q._Does_the_CHDK_program_consume_additional_battery_power.3F)
Hi
I installed the updated version.
Now i am able to use the Zoom in video.But i am experiencing focusing problem at 8x+ is it normal?
Like when i zoom above ~8x the screen is blurred and struggles to focus with no result. Although below 8x it is able to focus(not perfect, but acceptable). But At 10x its not Focusing! atleast for me.. any idea why is happening?
The object is my 29 inch television, about 15 meters away.
I just tested the new release. Optical zoom now works in video mode, but I do lose focus after 70% or so.lol for me it works fine
Also, I changed the recording mode from Bitrate to Quality and the camera kind of crashed when I tried to record video. The screen turned off immediately and the controls would not respond, except the power button, it does turn the camera off. I could turn back on again, no need to remove batteries. Nothing was recorded. I tried three times, same result every time.
I just tested the new release. Optical zoom now works in video mode, but I do lose focus after 70% or so.
Also, I changed the recording mode from Bitrate to Quality and the camera kind of crashed when I tried to record video. The screen turned off immediately and the controls would not respond, except the power button, it does turn the camera off. I could turn back on again, no need to remove batteries. Nothing was recorded. I tried three times, same result every time.
In Quality mode I think camera can't record to SD fast enough. Thats why I think it crushes. If you lower the quality to 98% camera will not crush! Also if video gets busy @ 98% it will crush as well.720is chdk had some kind protection against that. If your SD isn't fast enough for recording it just stops the recording. If you're right on the edge then warning sing flashes on the screen. Also with 720is I found out the difference between different SD card speeds. Generic cards will stop at around 50%. Better cards will go up to 84%. Excellent cards can go to 98% I have one SanDisk 1GB that can do 99%.
When you fully zoom without recording, camera can zoom no problem. But when you recording and zooming then there is a problem. I think it's a bug.
@Hyst
Could you explain what is not working, please? Auto-ISO-Shift works as
expected for me: ISO value changes automatically depending on available
light and so on... Am I wrong?
I still couldn't record at 98%, but it *seems* to have recorded at 97%. Large files are recorded (20 secs. = 105 Mb), but I can't playback them entirely on my Linux box. Mplayer just playbacks two or three seconds and closes. Sometimes it will play a few more seconds, but never all the way through. They playback correctly on the camera.
Just checked the last copy chdkj posted here (http://chdk.setepontos.com/index.php/topic,2838.msg32804.html#msg32804) and can't reproduce the issue.
ok possible bug
I have 2 partitions
/dev/sda1 'fat16, 1536megabytes
/dev/sda2 'fat32, around 6000megabytes
chdk boots and automatically switches to the second partition when I go into menu to switch it to first, it doesn't is this default behavior???
also optical zoom doesn't work (after recording starts) with latest build right? and doesn't work regardless without chdk (zooming works before recording atleast right?
thank again for hard work :D
I still couldn't record at 98%, but it *seems* to have recorded at 97%. Large files are recorded (20 secs. = 105 Mb), but I can't playback them entirely on my Linux box. Mplayer just playbacks two or three seconds and closes. Sometimes it will play a few more seconds, but never all the way through. They playback correctly on the camera.
No, you got that backwards. I can play it fine on the camera, I can't play it on the PC. EDIT: I mean, I copy the file to the HD before playing it on the PC.I can watch entirely such recorded files (>300 MB) with mplayer and
I'm using a SanDisk SDHC 4GB Ultra II --> recorded movies with Quality @99%.I just tested the new release. Optical zoom now works in video mode, but I do lose focus after 70% or so.
Also, I changed the recording mode from Bitrate to Quality and the camera kind of crashed when I tried to record video. The screen turned off immediately and the controls would not respond, except the power button, it does turn the camera off. I could turn back on again, no need to remove batteries. Nothing was recorded. I tried three times, same result every time.
In Quality mode I think camera can't record to SD fast enough. Thats why I think it crushes. If you lower the quality to 98% camera will not crush! Also if video gets busy @ 98% it will crush as well.720is chdk had some kind protection against that. If your SD isn't fast enough for recording it just stops the recording. If you're right on the edge then warning sing flashes on the screen. Also with 720is I found out the difference between different SD card speeds. Generic cards will stop at around 50%. Better cards will go up to 84%. Excellent cards can go to 98% I have one SanDisk 1GB that can do 99%.
When you zoom 100% without recording, camera can focus no problem. But when you recording and zooming >70% then there is a problem. I think it's a bug.
sure.. i'll explain.
Auto-ISO-Shift ist not the normal Auto-ISO. Auto-Iso-Shift works like this:
Rec-Mode -> menu -> activate auto-iso-shift.
go to P- TV- AV- or M-Mode -> change iso (for example) to 80 (should be a low number).
Go somewhere, where the light is not so bright (some kind of "darkish" area).
half-press the shot-button. Now the Print-Button should be blue. press the print-Button.
Now you should see how the ISO and the exposure-time changed to recommended (AUTO) settings.
greetings
Lol I have a ******* card only about 6mb/write and I can Record @99% without Problems ;);-)))
next step...
Auto Focus Scan during movie records works now. You have to (use the new
binary attached ...) configure an option "AF key" in OSD\video parameters.
This AF key triggers a AF scan while recording. It works for me. Because an
automatic AF scan is not available for SX110 you have to trigger it
manually. --> start your recording --> if cams has lost the focus then press
your AF key (I prefer <SET>) --> AF will readjust while movie is still
recording.
Solution: enable CAM_AF_SCAN_DURING_VIDEO_RECORD in camera.h and find
the address for some_flag_for_af_scan (stubs_min.S) in fw dump at
ROM:FFD19814.
and: dedicated to obihoernchen :-): Startup Sound works. Don't expect to much.
Solution: corrected wrong entry point of PT_PlaySound in stubs_entry_2.S "NHSTUB(PT_PlaySound, 0xFFC4D9AC)"
next step...
Auto Focus Scan during movie records works now. You have to (use the new
binary attached ...) configure an option "AF key" in OSD\video parameters.
This AF key triggers a AF scan while recording. It works for me. Because an
automatic AF scan is not available for SX110 you have to trigger it
manually. --> start your recording --> if cams has lost the focus then press
your AF key (I prefer <SET>) --> AF will readjust while movie is still
recording.
Solution: enable CAM_AF_SCAN_DURING_VIDEO_RECORD in camera.h and find
the address for some_flag_for_af_scan (stubs_min.S) in fw dump at
ROM:FFD19814.
New version of CHDK for SX110 attached!
and: dedicated to obihoernchen :-): Startup Sound works. Don't expect to much.
Solution: corrected wrong entry point of PT_PlaySound in stubs_entry_2.S "NHSTUB(PT_PlaySound, 0xFFC4D9AC)"
Cheers!
next step...
Auto Focus Scan during movie records works now. You have to (use the new
binary attached ...) configure an option "AF key" in OSD\video parameters.
This AF key triggers a AF scan while recording. It works for me. Because an
automatic AF scan is not available for SX110 you have to trigger it
manually. --> start your recording --> if cams has lost the focus then press
your AF key (I prefer <SET>) --> AF will readjust while movie is still
recording.
Solution: enable CAM_AF_SCAN_DURING_VIDEO_RECORD in camera.h and find
the address for some_flag_for_af_scan (stubs_min.S) in fw dump at
ROM:FFD19814.
New version of CHDK for SX110 attached!
and: dedicated to obihoernchen :-): Startup Sound works. Don't expect to much.
Solution: corrected wrong entry point of PT_PlaySound in stubs_entry_2.S "NHSTUB(PT_PlaySound, 0xFFC4D9AC)"
Cheers!
next step...
Auto Focus Scan during movie records works now. You have to (use the new
binary attached ...) configure an option "AF key" in OSD\video parameters.
This AF key triggers a AF scan while recording. It works for me. Because an
automatic AF scan is not available for SX110 you have to trigger it
manually. --> start your recording --> if cams has lost the focus then press
your AF key (I prefer <SET>) --> AF will readjust while movie is still
recording.
Solution: enable CAM_AF_SCAN_DURING_VIDEO_RECORD in camera.h and find
the address for some_flag_for_af_scan (stubs_min.S) in fw dump at
ROM:FFD19814.
New version of CHDK for SX110 attached!
and: dedicated to obihoernchen :-): Startup Sound works. Don't expect to much.
Solution: corrected wrong entry point of PT_PlaySound in stubs_entry_2.S "NHSTUB(PT_PlaySound, 0xFFC4D9AC)"
Cheers!
I want to do this update and I see : "UPDATE FILE ERROR!!!"Are you using the file attached to the post (latest) or the one from the autobuild server? - The autobuild one doesn't work, the attached one(s) does.
Are you using the file attached to the post (latest) or the one from the autobuild server? - The autobuild one doesn't work, the attached one(s) does.
Best guess is that the autobuild server is using the wrong keys for encrypting the image.I also think so, because the Autobuild Server Version was stable. But after some updates the Autobuild Server Version isn`t stable anymore
maybe a new bug:
If I turn on the camera (holding on/off about 2 secs), the lens goes out, but sometimes the cam turns itself off (black screen, and nothing more), and the lens stays out. If I try to turn on-off again, the lens don't goes correctly back, just half way. It is just with the latest version.
Thanks a lot chdkjHmmm, it looks to me that this should be possible. AF keys are hardcoded in gui.c. That means, this is not camera specific code, it is rather CHDK-core code. And therefore I'm not willing to change this code in some SX110-binaries (because we are leaving camera dependent code here).
autofocus is now working :)
by the way.. instead of SET button.. can i use the Zoom button straightway?
like when i press zoom, it will zoom and auto focus both at the same time?
can zoom button be added in AF key[ ]?
Thanks a lot!
Works fine for me. Nice Work! Maybe you're able to add the following feature:That's the same as http://chdk.setepontos.com/index.php/topic,2838.msg32903.html#msg32903 (http://chdk.setepontos.com/index.php/topic,2838.msg32903.html#msg32903).
While shooting a video, you press a button wich toggles the AF-assist-beam (or AF-Light -- the red LED in front) on and off. So that you can shoot videos in dark areas (with at least a little bit light)
greetings
maybe a new bug:sounds foolish: are you really using the latest version? Battery state? I'm not sure that we are talking about a new bug.
If I turn on the camera (holding on/off about 2 secs), the lens goes out, but sometimes the cam turns itself off (black screen, and nothing more), and the lens stays out. If I try to turn on-off again, the lens don't goes correctly back, just half way. It is just with the latest version.
Are you using the file attached to the post (latest) or the one from the autobuild server? - The autobuild one doesn't work, the attached one(s) does.
If version from autobuild server has a lot of errors, could it be removed (until it becomes stable)?
Best guess is that the autobuild server is using the wrong keys for encrypting the image.I also think so, because the Autobuild Server Version was stable. But after some updates the Autobuild Server Version isn`t stable anymore
the sx110 is not using d3enc, but a whole different key. thats why autobuild fi2 doesnt work.
Works fine for me. Nice Work! Maybe you're able to add the following feature:That's the same as http://chdk.setepontos.com/index.php/topic,2838.msg32903.html#msg32903 (http://chdk.setepontos.com/index.php/topic,2838.msg32903.html#msg32903).
While shooting a video, you press a button wich toggles the AF-assist-beam (or AF-Light -- the red LED in front) on and off. So that you can shoot videos in dark areas (with at least a little bit light)
greetings
Ok, I've to have express myself more precisely. Sorry for that.
No it isn't, look again at the two posts, one is asking for auto-focusing automatically when zooming, one is asking for an option to turn the AF-assist light on (semi-)permanently for shooting in the dark/low light.
Thanks a lot chdkjHmmm, it looks to me that this should be possible. AF keys are hardcoded in gui.c. That means, this is not camera specific code, it is rather CHDK-core code. And therefore I'm not willing to change this code in some SX110-binaries (because we are leaving camera dependent code here).
autofocus is now working :)
by the way.. instead of SET button.. can i use the Zoom button straightway?
like when i press zoom, it will zoom and auto focus both at the same time?
can zoom button be added in AF key[ ]?
Thanks a lot!
@Main Developers
What are you thinking about?
Cheers!
I'm thinking about beer. Would be nice. What are you thinking about ? ;)@Main Developers
What are you thinking about?
would be nice :)
@PhyrePhoX: do we need a new category like d3enc_v2 or am I wrong?It uses the D4 values.
semi-automatic AF after zoom sounds OK, if you can find a reasonable way to do it. Add it to the bug tracker and submit a patch.
maybe a new bug:
If I turn on the camera (holding on/off about 2 secs), the lens goes out, but sometimes the cam turns itself off (black screen, and nothing more), and the lens stays out. If I try to turn on-off again, the lens don't goes correctly back, just half way. It is just with the latest version.
which Version Autobuild or latest?
For me this bug was only happen with the "old" (Autobuild) Version when you enable startup sound. But the newest Version fixed this.
Several comments:
...
4) Has anyone managed to make any of the motion detection scripts work on the SX110IS?
4) Has anyone managed to make any of the motion detection scripts work on the SX110IS?
Nope ??? I tried everything I found from wiki but couldn't get them to work properly.. The "Multipurpose Motion Detection" runs but seems to detect motion everywhere, no matter how I try to calibrate it. :(
@axu89
Try fudgey's Fast MD (http://chdk.setepontos.com/index.php/topic,471.msg21328.html#msg21328) script...
GnF that looks like the difference between canons "Market ISO" and "real ISO"
Because Canon havnt high end firmware like CHDK^^ Also because it isnt a Camera for Professional use, so canon think its enough to show the "wrong" valueGnF that looks like the difference between canons "Market ISO" and "real ISO"
Damn that is so true. Why does canon reports completly different iso?
hello, why optical zoom does not work on video with last chdk? thanksomfg... ::)
semi-automatic AF after zoom sounds OK, if you can find a reasonable way to do it. Add it to the bug tracker and submit a patch.
BTW, I have such patch for old (Allbest?) CHDK version. If anyone interested, I will upload it tomorrow.
I'm thinking about beer. Would be nice. What are you thinking about ? ;);-) Yep. Where?
semi-automatic AF after zoom sounds OK, if you can find a reasonable way to do it. Add it to the bug tracker and submit a patch.Hmmm, have to think about...
Turning on the AF lamp might be nice, but I'd be slightly concerned that LED is being over driven and is only designed to be on for short periods. It's also not really bright enough to help very much, at least not on any powershot I've used.I'm afraid you are right.
@PhyrePhoX: do we need a new category like d3enc_v2 or am I wrong?It uses the D4 values.
I would welcome that!semi-automatic AF after zoom sounds OK, if you can find a reasonable way to do it. Add it to the bug tracker and submit a patch.
BTW, I have such patch for old (Allbest?) CHDK version. If anyone interested, I will upload it tomorrow.
well, who wouldnt want such a patch? probably in a new thread though, so it doesnt get lost :)
I've the on/off problem again with sx110is-100b-0.9.8-755-full.zip too.Strange. I dont have any clue... Please try to narrow it down. Did you check your camera firmware version? Is your SD card free of errors (filesystem check or physical write test)?
I hold the on/off button, the lens comes out, but the camera turn itself off with lens out...
Sometimes it seems all right. I try to find where it comes from.
The first beta versions didn't do that.
Live histogram in "always" mode shows only "noise", but with half pressed shutter and in "shoot" mode it's ok.
I know zebra is not supported yet, but it turns itself on sometimes.
I'm using the first beta's cfg file. Shall I delete it and setup everything again??
really strange i dont have problems like that after the soundfix.I've the on/off problem again with sx110is-100b-0.9.8-755-full.zip too.Strange. I dont have any clue... Please try to narrow it down. Did you check your camera firmware version? Is your SD card free of errors (filesystem check or physical write test)?
I hold the on/off button, the lens comes out, but the camera turn itself off with lens out...
Sometimes it seems all right. I try to find where it comes from.
The first beta versions didn't do that.
Live histogram in "always" mode shows only "noise", but with half pressed shutter and in "shoot" mode it's ok.
I know zebra is not supported yet, but it turns itself on sometimes.
I'm using the first beta's cfg file. Shall I delete it and setup everything again??
Are your sure that core/gui.c in SVN 755 is clean? First line looks strange.I'm not sure what you mean ? gui.c didn't change in 755
The first line of the file looks normal to me gvim, windowsCode is correct , sorry. Mixed something up on my own installation with diffs.
4) Has anyone managed to make any of the motion detection scripts work on the SX110IS?
Nope ??? I tried everything I found from wiki but couldn't get them to work properly.. The "Multipurpose Motion Detection" runs but seems to detect motion everywhere, no matter how I try to calibrate it. :(
same here...@axu89
Try fudgey's Fast MD (http://chdk.setepontos.com/index.php/topic,471.msg21328.html#msg21328) script...
just tried.. same problem
Greetings
I tried it too, works like the Multipurpose MD. If I turn threshold up to >100 it wont trigger by itself nor with motion. I also tried tuning the other parameters like with the other scripts but no, it wont work like it should. :(Didn't play with scripts so far but did you try do mask some cells? There are hints about at the sx1-thread (http://chdk.setepontos.com/index.php/topic,3410.msg33072.html#msg33072 (http://chdk.setepontos.com/index.php/topic,3410.msg33072.html#msg33072)).
I tried it too, works like the Multipurpose MD. If I turn threshold up to >100 it wont trigger by itself nor with motion. I also tried tuning the other parameters like with the other scripts but no, it wont work like it should. :(Didn't play with scripts so far but did you try do mask some cells? There are hints about at the sx1-thread (http://chdk.setepontos.com/index.php/topic,3410.msg33072.html#msg33072 (http://chdk.setepontos.com/index.php/topic,3410.msg33072.html#msg33072)).
I tried. But if you try running the script, you will notice that masking the border cells is useless since motion is detected everywhere "randomly". Its strange..? ??? Maybe Im doing something terribly wrong? :oOk, thanks for testing. Don't think that you are doing something wrong regarding MD-scripts ;-). Can't exclude that some other things are broken in SX110-port and you are trapping in a subsequent error.
- Auto-ISO-Shift doesn't work (http://chdk.setepontos.com/index.php/topic,2838.msg32856.html#msg32856 (http://chdk.setepontos.com/index.php/topic,2838.msg32856.html#msg32856)) -->I'm really unsure about this. It seems to me that Auto-ISO-Shift works as expected: ISO selecting by camera will controlled by user settings.
here is what i do (an example):
(auto-iso-shift must be enabled in the canon-options and alt-key must be the print-button)
I am sitting in a dark room. Boot the cam WITHOUT CHDK. P-Mode. Iso is manually set to 80.
I am holding the shutter half-pressed. it shows:
ISO 80 ; exposure 1/5
The print button glows blue. I press it. Now the settings changed to recommended auto-settings
ISO 320^ ; exposure 1/20
now i boot the cam WITH CHDK. (same room. same settings)
I am holding the shutter half-pressed. it shows:
ISO 80 ; exposure 1/5
The print button glows blue. I press it. and nothing changes. neither with a short press nor a long press.
what are you doing (or rather why does it work as expected with your cam)?
This is well-known bug for cameras with autoISO shift function.
At present there is only one medicine - change <alt> key to other key (if CHDK for SX110 can do this).
perhaps ewavr or fudgey can take a look at the getbattery stuff in the dumps. if they cant find the function, nobody can ;)Oh Oh...
This is well-known bug for cameras with autoISO shift function.Thank you. Short and painless...
At present there is only one medicine - change <alt> key to other key (if CHDK for SX110 can do this).
Not working MD scripts and corrupted Zebra is more annoying. Could it be that both are somehow related to each other? Wrong memcpy, wrong/unexpected buffer content?Wrong live view buffer, most likely. You can write the live view buffer to a file and examine it on PC. You can also watch the address and see if it looks reasonable.
After using the CHDK camera sx110, camera called CRW suffix generated document, with dng4ps2 and FastStone Image Viewer can not open the browser!Currently few programs understand CHDK raw from 12 bit cameras like the sx110. If you look back in this thread, you may find something. You can also try dng instead.
I would like to ask, to how to open?
@Hyst, it is not in my intent to annoy you ;).
This is well-known bug for cameras with autoISO shift function.
At present there is only one medicine - change <alt> key to other key (if CHDK for SX110 can do this).
I don't know if it is a bug or, if i'm doing something wrong, but: what is it about the "flashlight" function (in misc. options). I enable it, but nothing happens.
Wrong live view buffer, most likely. You can write the live view buffer to a file and examine it on PC. You can also watch the address and see if it looks reasonable.Thank you, Reyalp. Will check this in the next couple of days.
If live view is wrong, histogram will also be wrong. If the camera has built in histogram, you can compare (there will be some difference, but it should be roughly the same shape)
Wrong settings in camera.h for SX110. (#define CAM_SWIVEL_SCREEN 1). Must be removed because SX110 doesn't have a swivel screen.I don't know if it is a bug or, if i'm doing something wrong, but: what is it about the "flashlight" function (in misc. options). I enable it, but nothing happens.
This is a bug - "flashlight" function is only for cameras with rotating/swivel display.
http://chdk.wikia.com/wiki/SX110IS#Known_bugs (http://chdk.wikia.com/wiki/SX110IS#Known_bugs) updated...Hi Obihoerchen,
http://chdk.wikia.com/wiki/SX110IS#Known_bugs (http://chdk.wikia.com/wiki/SX110IS#Known_bugs) updated...Hi Obihoerchen,
I think that Auto-ISO-Shift is solved (general Bug if <ALT> = Print, workaround: change <ALT>-key to <Face>). If Hyst agrees than would you change "bug" to "hint/tricky/obscure..", please?
I think that Auto-ISO-Shift is solved (general Bug if <ALT> = Print, workaround: change <ALT>-key to <Face>). If Hyst agrees than would you change "bug" to "hint/tricky/obscure..", please?
P.S. DNG is useable at least but colors are not how they should be...
P.P.S. Use DNG instead of RAW (--> you can find a lot of discussion about it in forum)
@PhyrePhoX: May I ask you to update autobuild with attached diff?Applied, svn 757
Fixed with it:
- Swivel screen disabled in camera.h for sx110
- fixed vid_get_viewport_live_fb in lib.c (Zebra, Histogramm, Motion
Detection works now.)
Regards!
fast :)@PhyrePhoX: May I ask you to update autobuild with attached diff?Applied, svn 757
Fixed with it:
- Swivel screen disabled in camera.h for sx110
- fixed vid_get_viewport_live_fb in lib.c (Zebra, Histogramm, Motion
Detection works now.)
Regards!
nice construction ^^
edited the article dont know wheather this is right? min. 3,6V / Wake-up: No ?
I'll try to figure out the other values like TV and so on
Anyone know a way for me to hide chdk osd while i preview the already taken photos? I seem not able to find a way to hide 3 things till now.
Battery and battery data (% or voltage)
Time
Temperature (either one of the 3 or all of them).
I think i was able to hide them till 754
nice construction ^^
edited the article dont know wheather this is right? min. 3,6V / Wake-up: No ?
I'll try to figure out the other values like TV and so on
Hmm.. I believe the min. is 3,4V like many other cameras but I dont have proper means to test it accurately. 3,6-3,7 work but its not the minimum.
Put it this way: 3,6V OK / Wake-up: No
nice construction ^^
edited the article dont know wheather this is right? min. 3,6V / Wake-up: No ?
I'll try to figure out the other values like TV and so on
Hmm.. I believe the min. is 3,4V like many other cameras but I dont have proper means to test it accurately. 3,6-3,7 work but its not the minimum.
Put it this way: 3,6V OK / Wake-up: No
Thanks! :)Anyone know a way for me to hide chdk osd while i preview the already taken photos? I seem not able to find a way to hide 3 things till now.
Battery and battery data (% or voltage)
Time
Temperature (either one of the 3 or all of them).
I think i was able to hide them till 754
Main Menu -> OSD parameters -> Hide OSD: In Play
Wow what a nice cam!
I tested Motion Detection a little bit here is the result :)
Between 80 and 90ms! Without any optimization!
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fwww.abload.de%2Fthumb%2F80mssrz1.jpg&hash=4091a2165db703d67bfab8fe3034e665) (http://www.abload.de/image.php?img=80mssrz1.jpg)
My experience with MD isn't going so well. Which script are you folks using, and what parameters?
My experience with MD isn't going so well. Which script are you folks using, and what parameters?
I use http://chdk.setepontos.com/index.php/topic,471.msg21328.html#msg21328 (http://chdk.setepontos.com/index.php/topic,471.msg21328.html#msg21328)
Default script parameters work, and you can turn trigger delay to 0. The script has nice read me -file, read it :)
Here are some practical test with MD on SX110IS:
@axu89
Wow! Cool. Camera Control via a heli rc... :-)
@Obihoernchen
Don't kill the rabbitt! Did you throw a potato?
do we have the advanced version with all 3 buffers? http://chdk.setepontos.com/index.php/topic,471.msg33535.html#msg33535 (http://chdk.setepontos.com/index.php/topic,471.msg33535.html#msg33535)CHDK source code says yes... have a look to /platform/sx110is/sub/100b/lib.c (e.g. online (http://tools.assembla.com/chdk/browser/trunk/platform/sx110is/sub/100b/lib.c)):
void *vid_get_viewport_live_fb()
{ void **fb=(void **)0x21a0; //ROM:FFC285D0 dword_FFC285D0 DCD 0x21A0, look also at ROM:FFC27FF0
unsigned char buff = *((unsigned char*)0x2014); //ROM:FFC285C8 dword_FFC285C8 DCD 0x2014 , look also at ROM:FFC27FA0
if (buff == 0) buff = 2; else buff--;
return fb[buff]; }
do we have the advanced version with all 3 buffers? http://chdk.setepontos.com/index.php/topic,471.msg33535.html#msg33535 (http://chdk.setepontos.com/index.php/topic,471.msg33535.html#msg33535)CHDK source code says yes... have a look to /platform/sx110is/sub/100b/lib.c (e.g. online (http://tools.assembla.com/chdk/browser/trunk/platform/sx110is/sub/100b/lib.c)):Code: [Select]void *vid_get_viewport_live_fb()
{ void **fb=(void **)0x21a0; //ROM:FFC285D0 dword_FFC285D0 DCD 0x21A0, look also at ROM:FFC27FF0
unsigned char buff = *((unsigned char*)0x2014); //ROM:FFC285C8 dword_FFC285C8 DCD 0x2014 , look also at ROM:FFC27FA0
if (buff == 0) buff = 2; else buff--;
return fb[buff]; }
In the link below there is a multi target picture taken with SX110. Maybe it can help to improve the color matrix.
http://www.imaging-resource.com/PRODS/SX110IS/FULLRES/SX110IShMULTIW.HTM (http://www.imaging-resource.com/PRODS/SX110IS/FULLRES/SX110IShMULTIW.HTM)
In the link below there is a multi target picture taken with SX110. Maybe it can help to improve the color matrix.
http://www.imaging-resource.com/PRODS/SX110IS/FULLRES/SX110IShMULTIW.HTM (http://www.imaging-resource.com/PRODS/SX110IS/FULLRES/SX110IShMULTIW.HTM)
Maybe we should do that:
http://chdk.setepontos.com/index.php/topic,390.0.html (http://chdk.setepontos.com/index.php/topic,390.0.html)
http://chdk.wikia.com/wiki/DNG4PS-2/Calibration (http://chdk.wikia.com/wiki/DNG4PS-2/Calibration)
chermucsnis it is possible for you to take a photo with these settings?
In the link below there is a multi target picture taken with SX110. Maybe it can help to improve the color matrix.
http://www.imaging-resource.com/PRODS/SX110IS/FULLRES/SX110IShMULTIW.HTM (http://www.imaging-resource.com/PRODS/SX110IS/FULLRES/SX110IShMULTIW.HTM)
Maybe we should do that:
http://chdk.setepontos.com/index.php/topic,390.0.html (http://chdk.setepontos.com/index.php/topic,390.0.html)
http://chdk.wikia.com/wiki/DNG4PS-2/Calibration (http://chdk.wikia.com/wiki/DNG4PS-2/Calibration)
chermucsnis it is possible for you to take a photo with these settings?
@obihoernchen: sx110-wiki-page looks good!!!
Just an idea: What's about the other 12-bit cameras? Do they possess a proper color profile? How do they got it?
Regards!
If you didn't have the correct address, you'd get garbage or a partial image, not an image with the wrong colors.
Incorrect CAM_BLACK_LEVEL in the sd990 had an effect somewhat like what was described here. See http://chdk.setepontos.com/index.php/topic,2972.30.html (http://chdk.setepontos.com/index.php/topic,2972.30.html)
If you didn't have the correct address, you'd get garbage or a partial image, not an image with the wrong colors.
Incorrect CAM_BLACK_LEVEL in the sd990 had an effect somewhat like what was described here. See http://chdk.setepontos.com/index.php/topic,2972.30.html (http://chdk.setepontos.com/index.php/topic,2972.30.html)
Not that I would understand a thing about this.. but I tried setting CAM_BLACK_LEVEL to 128 and calibration results are way better than before (with quick test picture of my laptop LCD (full of reflections). Error used to be something like 80% and now its just 17%.. Now if someone would just fine tune it and take a proper calibration picture :)
If you didn't have the correct address, you'd get garbage or a partial image, not an image with the wrong colors.
Incorrect CAM_BLACK_LEVEL in the sd990 had an effect somewhat like what was described here. See http://chdk.setepontos.com/index.php/topic,2972.30.html (http://chdk.setepontos.com/index.php/topic,2972.30.html)
Not that I would understand a thing about this.. but I tried setting CAM_BLACK_LEVEL to 128 and calibration results are way better than before (with quick test picture of my laptop LCD (full of reflections). Error used to be something like 80% and now its just 17%.. Now if someone would just fine tune it and take a proper calibration picture :)
I would do it if you could tell me:
1. how to change CAM_BLACK_LEVEL
and 2. how to compare the 2 pictures and measure the difference?
Yeah i think i can do it ;) I dont need the FI2 Feature i never use it :P
only one question in camera.h there is nearly 10 times #define CAM_BLACK_LEVEL and one value is 31 all other are 127. Which I have to change?
PS: Which values would be good? Should I also try 129, 130, ... ? Or is there only 127 and 128?
If you didn't have the correct address, you'd get garbage or a partial image, not an image with the wrong colors.
Incorrect CAM_BLACK_LEVEL in the sd990 had an effect somewhat like what was described here. See http://chdk.setepontos.com/index.php/topic,2972.30.html (http://chdk.setepontos.com/index.php/topic,2972.30.html)
Yeah i think i can do it ;) I dont need the FI2 Feature i never use it :P
only one question in camera.h there is nearly 10 times #define CAM_BLACK_LEVEL and one value is 31 all other are 127. Which I have to change?
PS: Which values would be good? Should I also try 129, 130, ... ? Or is there only 127 and 128?
Its a list of all camera models, SX110 is at the bottom of the file and not all cameras have it defined. I dont know what would be the effect if it would be undefined for SX110..
I will experiment more today if I have the time (propably not :( )
reyalp pointed out a good thread. Theres some discussion about the black level value:If you didn't have the correct address, you'd get garbage or a partial image, not an image with the wrong colors.
Incorrect CAM_BLACK_LEVEL in the sd990 had an effect somewhat like what was described here. See http://chdk.setepontos.com/index.php/topic,2972.30.html (http://chdk.setepontos.com/index.php/topic,2972.30.html)
You`re wrong in several points here, jpg's use 8 bit per channel not 10, the dng file format supports 12 bit data just fine and we are keeping all 12 bits no data is being converted. The problem is not that there is 'some' difference the dng looks like someone put a heavy blue filter on. Thanks for thinking along with us but though.
I have a idea but I donot know it works or not. we can disassemblers or decompilers the firmwares and find out how it deal with raw files, or find out the functions or code segments which deal with raw files.
jpg 1600x1200 | dng->jpg 1600x1206 |
| (https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg211.imageshack.us%2Fimg211%2F7738%2Fimg16741600x1200.th.jpg&hash=b6410feb2f524fc622da650fc063d628) (http://img211.imageshack.us/my.php?image=img16741600x1200.jpg) | (https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg141.imageshack.us%2Fimg141%2F9735%2Fcrw16741600x1202.th.jpg&hash=f2865d248dc44977d72f9e62fbec470f) (http://img141.imageshack.us/my.php?image=crw16741600x1202.jpg) |
Does this apply to all models using the chdk?No, it doesn't. Black level is set to 31 per default. But each camera might use an other value for it. S5is uses 31. Have a look at camera.h....
Is it for using the conversion to DNG in camera or does the DNG4PS2 program work with this change?As far as I've understood Black Level is used as a threshold in RAW pictures and also will be written as descriptive value in DNG-file. It's definitly not a clear answer to your question but I don't know how DNG4PS works.
I've the power on problem again. Sometimes in play mode too - using on/off or play button too.Remember it but I'm to lazy to search for...Could you describe it in more details, please?
The exasperating topic again:
Did some shoots in DNG and all are yellowish (yellow and blue). I've used the latest Autobuild version (with black level 128). Adobe Lightroom shows also two main peaks in histogram for yellow and blue.
BTW, bought a small tripod before. It's a so called Gorilla Pad and meant to be used as a travel tripod. And it works! That's a really cool toy!
But look at my pictures the are perfect with DNGps2 http://chdk.setepontos.com/index.php/topic,2838.msg34217.html#msg34217 (http://chdk.setepontos.com/index.php/topic,2838.msg34217.html#msg34217)Noticed that. If I'm open your dng in Adobe Lightroom and your jpg in IrfanView then the jpg will be shown as expected and the dng is blueish oversaturated (and violet). Compare the white wall right beside the window (underneath the red street lamp) or the black BMW. The DNG shows a slightly blue/lila wall and a lila BMW (the owner of the car will not be amused, I'm afraid). Do I have some problems with my software???
But look at my pictures the are perfect with DNGps2 http://chdk.setepontos.com/index.php/topic,2838.msg34217.html#msg34217 (http://chdk.setepontos.com/index.php/topic,2838.msg34217.html#msg34217)
But look at my pictures the are perfect with DNGps2 http://chdk.setepontos.com/index.php/topic,2838.msg34217.html#msg34217 (http://chdk.setepontos.com/index.php/topic,2838.msg34217.html#msg34217)
Because (perhaps ??) those all comes out from jpgs.
IrfanView, in this case, seems to work on the jpg attached to the dng, not on the raw.
The true raw image is also bigger than the jpg (3662x2760 vs 3456x2592) and displays a larger scene (see here http://chdk.setepontos.com/index.php/topic,2838.msg34223.html#msg34223 (http://chdk.setepontos.com/index.php/topic,2838.msg34223.html#msg34223) )
As you say, your images are identical, and this is impossible...
... I think :blink:
I think I will do a shortcut. Implementing GetBatteryTemperature (...) with hard coded return code 99 decimal (...)
Everyone agrees?
Better idea: just yank it out of the port. It doesn't work anyway. Why keep it?Yes i would say thats better, because 00 says sth. like doesnt work^^
"00" is better than "99". No one is going to think that the battery is frozen.
Better idea: just yank it out of the port. It doesn't work anyway. Why keep it?Scripts and ui code expect the function to exist. Putting hacks in the main code for this one camera to do something different would be stupid.
"00" is better than "99". No one is going to think that the battery is frozen.0 could be a real value. 99, if it were real, would mean your camera was destroyed. Note that the value is in C, it will be converted to 210 (also obviously bogus) appropriately if the user chooses to display in F.
is it possible to show ccd + optical temp only?No, it isn't. Otherwise it would require changes in camera independent code parts of CHDK.
(by "all" we can see the false sensor value too)
Sorry for my inferior knowledge about CHDK - but will it ever be possible to achieve a good-looking DNG format on the SX110IS (i.e. with no flaws as present)? I would love that, as the canon format is quite annoying to work with.It might be more helpful if you could explain in what way the current output is not acceptable, and also what tools/workflow are giving these unacceptable results. From what I understand, the color calibration in the latest autobuilds should be pretty good.
is it possible to show ccd + optical temp only?No, it isn't. Otherwise it would require changes in camera independent code parts of CHDK.
(by "all" we can see the false sensor value too)
Improving CHDK with "ccd + optical", "optical + battery", "ccd + battery" functions can be useful for the other cameras too. I think SX110 is not the only one camera that doesn't support all the 3 sensors....nevertheless we have to avoid camera crashs due to erroneous functions called by CHDK. GetBatteryTemperature is broken.
What does the other cams write with 2 sensors in "all" mode? (Maybe in an another topic we can find.)Other cameras (could) have the same problem. But SX110 is the only one that crashs (as far as I know). The whole discussion is based on that...
In jpeg with 9mp it's 36-360mm EFL. But in raw and nearly 10 mp? 34-340? Any tips? Or can we measure it? I will calibrate it with a Sony DSLR.You are right. Image dimensions influences focal length. I think it should be calculable.
dcraw -v -r 1.6254 1 2.1871 1 CRW_1356.DNG Maybe the "on/off error" solved (again:)Hmmm.. I don't know. DCIM is a standard folder by Canon and has nothing to do with CHDK. But apparently it helps..
I've deleted the empty folders in "\dcim", and their .ctg files, in "\dcim\canonmsc".
No errors after it.
That could be the reason that there wasn't any problems for a few weeks after formatting the card.
I've made a mistake .... I'm gonna crazy.;)
I've made a mistake by calculating EFL, so the right values are about 33-330mm. I'm gonna crazy.Zodiac757, may I ask you to have a look in platform\sx110is\main.c ?
So Main Menu / OSD / Misc values / Adapter Lens scale is 100 for RAW, 108 for JPEG.
It was wondering why need to modify Lens scale to 108 and why 33mm is the default. Now we know it.
A note on the ALT button ISO shift bug:I did notice it also from time to time. Pressed ALT-button (FACE) twice and CHDK menu appears. Sometime I had to to press FACE a third time because Canon Face Mode instead CHDK menu appeared. Could be a timing problem ...
If I set the ALT button to FACE from PRINT, this seems to disable the ALT button in CHDK when I turn the camera off and back on. This makes it so I can't excess the CHDK menu anymore.
I don't know the answers. I'm only thinking about scripting but I hadn't started yet.JPG will be written by the camera itself. I don't believe that one can extend the original 9MP to 10MP even if the sensor might be a larger one than 9MP.
My first idea was to make 10mp jpeg's with 33mm EFL instead of 9mp with 36mm.
I used basic language last on C64. :]
A note on the ALT button ISO shift bug:I did notice it also from time to time. Pressed ALT-button (FACE) twice and CHDK menu appears. Sometime I had to to press FACE a third time because Canon Face Mode instead CHDK menu appeared. Could be a timing problem ...
If I set the ALT button to FACE from PRINT, this seems to disable the ALT button in CHDK when I turn the camera off and back on. This makes it so I can't excess the CHDK menu anymore.
I don't know the answers. I'm only thinking about scripting but I hadn't started yet.JPG will be written by the camera itself. I don't believe that one can extend the original 9MP to 10MP even if the sensor might be a larger one than 9MP.
My first idea was to make 10mp jpeg's with 33mm EFL instead of 9mp with 36mm.
I used basic language last on C64. :]
Greetings!
The sensor is 10mp but sx110 uses 9 only.What do you mean ? Are you talking about the difference between jpeg size and raw size ?
If we could change the sensor for a greater, EFL won't grow.Definitely not with script, or without a lot of asm hacking.
The only way is to use the whole sensor - without taking raw. Maybe a script can't do that.
I gave it another try and to no avail. Cant for the life of me get the CHDK menu to appear. Display of battery left, time, and card capacity is good enough for now.I'm sorry. Can't help you right now because my SX110 is in service.
Anyway its all the same. ALT button in playmode brings up the Add to Print Menu and ALT Button in regular mode does nothing. It is supposed to show the blue ALT CHKD confirmation in the lower left I believe.
Anyway its all the same. ALT button in playmode brings up the Add to Print Menu and ALT Button in regular mode does nothing. It is supposed to show the blue ALT CHKD confirmation in the lower left I believe.
Did you assign a camera function to the Print/Shortcut key in the Canon menu ("Set PRINT button") ?
I don't like using zebra because It clears the built in grid lines by pressing the shot button halfway. So I've turned it off. My problem is the zebra automatically turns itself on again and again after a few days. Is it a bug??
No "on/off bug" after my solution :]
But we always give the length as 32. get_parameter_data gives us a string terminated by null and padded with 0xffThan it seems to be an application problem.
Hope nothing is too bad with your camera, why does it need service?Batteries drained out too fast. Fresh battery, 2 pics later --> "change the battery"...
Anyway its all the same. ALT button in playmode brings up the Add to Print Menu and ALT Button in regular mode does nothing. It is supposed to show the blue ALT CHKD confirmation in the lower left I believe.No clue. FACE=ALT works (worked) definitely for me.
Same here. Works as expected.I don't like using zebra because It clears the built in grid lines by pressing the shot button halfway. So I've turned it off. My problem is the zebra automatically turns itself on again and again after a few days. Is it a bug??
No "on/off bug" after my solution :]
lol your camera or whatever is strange I doesn't have any problems. All time Zebra off
I don't like using zebra because It clears the built in grid lines by pressing the shot button halfway. So I've turned it off. My problem is the zebra automatically turns itself on again and again after a few days. Is it a bug??
No "on/off bug" after my solution :]
lol your camera or whatever is strange I doesn't have any problems. All time Zebra off
Anyone know why when I use raw the color is always off? Here is an example image, I shot it with the DNG option enabled.just read the Thread and this http://chdk.wikia.com/wiki/SX110IS (http://chdk.wikia.com/wiki/SX110IS) ...
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi39.tinypic.com%2F25fnccp.jpg&hash=043c8b3524c1b620a78cb95ca9e29047)
Thanks!
...Only issue I had was the DNG's came out off color, but is this the colormatrix you says is coming?Yes, it is.
I've one week (and 3 workday :[ ) for holiday, so I'll open my third beer for this day - now!Prost!
But with SX100 it's for "disable overrides". It's unwanted switchig too but with an another function - not zebra.This is exactly that I meant. I will check it.
...Only issue I had was the DNG's came out off color, but is this the colormatrix you says is coming?Yes, it is.
@obihoernchen: could you record the shortcuts in wikia, please?
...Unfortunately, yes, it is.
Hmm, color matrix for SX110 from dcraw is too bad?
got an issue with the bracketing functionality with RAW enabled. For whatever reasons, the first shot is taken, dark screen, saving, review, the second shot is taken, but then the cam just turns off. I am using the selftimer variant to take 3 shots with Tv bracketing.No, I can't.
anybody to reproduce that?
I've on/off bug again-again. Now it came after shooting raw to "\dcim\100canon" (not the same directory with jpegs). The card was cleared a few weeks ago, so the new pics (jpegs) are now only in the dir named "132canon". There wasn't problems until I shot just jpeg (just only one time when it was after massive continuous shooting). The problem comes from the desription files in "\dcim\canonmsc" because after erasing "\dcim\100canon" with the raw file everything is ok. Maybe a Chdk function that checks these directories and/or files by starting camera. This bug comes most in play mode.
I had an another type of on/off error most by trying to start the cam in rec mode. I had this with empty or missing directories witch had desription files in "\dcim\canonmsc" - because the pictures was moved to my PC manually via a card reader.
I've a 4Gb AData Class6 SDHC card.
I've tried to turn on the camera many times without CHDK and had no errors this way. So It isn't a hardware problem.
Had anybody met this bug??? Only me???
Maybe "Add raw-suffix" in the "Bracketing in continuous mode" is enabled ?I did only a few test but option "raw suffix" in "Bracketing in continuous mode" was enabled and everything works as expected.
DryOS based cams could have problems with long filenames...Mantis #279 (http://chdk.kernreaktor.org/mantis/view.php?id=279) and forum link (http://chdk.setepontos.com/index.php/topic,2468.msg36226.html#msg36226), also Mantis #86 (http://chdk.kernreaktor.org/mantis/view.php?id=86).
Are there any updates on future releases for SX110 ?? Is anybody working on it ?Short answers: No. No.
(The last release was on 17th May )
Are there any updates on future releases for SX110 ?? Is anybody working on it ?Short answers: No. No.
(The last release was on 17th May )
Long version: CHDK for SX110IS is nearly finished. I'm waiting for a better color matrix to release the final version. The final version will be roughly the same as the version from May 2009. Clearing up some code and modifying some functions and a better color matrix will be built in. There will be no other enhancements! The specific port of SX110 is done since May.
CHDK will be improved in the future and CHDK for SX110 will do so automatically more or less --> but you have to use CHDK from autobuild.
We don't have a working color matrix for RAW/DNG. I'm not capable to produce one.
Greetings.
Regarding http://chdk.setepontos.com/index.php/topic,2838.msg37061.html#msg37061 (http://chdk.setepontos.com/index.php/topic,2838.msg37061.html#msg37061)Thank you. I will submit a patch later.
I can change to SX100 style controls in the trunk, but not having the camera I cannot confirm this is correct. If someone with the camera wants to test and post a patch, that would be helpful.
Yeah good news from vit40!WTF! I was talking with VIT40 some time ago and now I've missed the hit. Even without any tests: Thank you, vit40!
Look here: http://chdk.setepontos.com/index.php/topic,3930.msg37299.html#msg37299 (http://chdk.setepontos.com/index.php/topic,3930.msg37299.html#msg37299)
Lost my motivation, somehow... Other things got more attention... Sorry for late answer.we are everybody here thinking on your success.
Lost my motivation, somehow... Other things got more attention... Sorry for late answer.
...but I'm absolutely unable to do Av bracketing...Did a quick check: Av bracketing works as good as Tv bracketing does. Please be aware that CHDK will not avoid physical restrictions of the camera. So if you start for instance with an Av of 2,8 (or 4,3 with full tele) and want to lower it by 1 Ev so nothing will happen. You have reached the lower limit already.
Thanks for that. I've committed it, svn 822.
@Admins: May I ask to check in the diff? It's based on 813 and checked against current 821.
Did a quick check: Av bracketing works as good as Tv bracketing does. Please be aware that CHDK will not avoid physical restrictions of the camera. So if you start for instance with an Av of 2,8 (or 4,3 with full tele) and want to lower it by 1 Ev so nothing will happen. You have reached the lower limit already.
Greetings!
Question: How to set custom camera profiles in Lightroom?
Interesting...CHDK sets the DNG active area to the the full active area, and the DefaultCrop area to the size (but possibly not precisely the same location) of the camera jpeg
Why does ACR cuts pixels off and DCRAW does not? Is there any need to change/fix some code in CHDK for SX110 regarding this issue?
Raw images often store extra pixels around the edges of the final image. These extra pixels help prevent interpolation artifacts near the edges of the final image.SX110
DefaultCropSize specifies the size of the final image area, in raw image coordinates (i.e., before the DefaultScale has been applied).
#define CAM_ACTIVE_AREA_X1 8
#define CAM_ACTIVE_AREA_Y1 14
#define CAM_ACTIVE_AREA_X2 3688
#define CAM_ACTIVE_AREA_Y2 2772
...
#define CAM_RAW_ROWPIX 3720
#define CAM_RAW_ROWS 2772
...
#define CAM_JPEG_WIDTH 3456
#define CAM_JPEG_HEIGHT 2592
...
#define CAM_DEFAULT_CROP_ORIGIN_W ((CAM_ACTIVE_AREA_X2-CAM_ACTIVE_AREA_X1-CAM_JPEG_WIDTH )/2)
#define CAM_DEFAULT_CROP_ORIGIN_H ((CAM_ACTIVE_AREA_Y2-CAM_ACTIVE_AREA_Y1-CAM_JPEG_HEIGHT)/2)
I have SX110 fw 1.00b camera with chdk 1.1.0-2423. I have a zebra problem. In record mode, zebra displayed, but wrong. The blinking region not on the over exposured region and distorsed. The over eposured region (original is circle) now ellipsoid.Can you post a picture?
With this camera with playback mode zebra not working or not accesible, if i half press the shutter button used, the camera exit from playback mode. Print or face key no succes (try swap alt key mode too), and other key not display the zebra too.Yes, this is a limitation on cameras where pressing shutter switches to record mode. This is something that should be fixed. I guess we could show zebra if you half press in alt mode, like we do for histogram?
Of course, i can send the test image. Where can i send test images?You can attach it to a post here. If you started your post in the "quick reply" box at the bottom, you can just press preview to get full options.
In playback mode i see the histogram when i use set and half press shutter button and not switch to record mode. Only zebra not working.I'm not sure what you mean by set and half press? I think the problem of not being able to show zebra in playback applies to all cameras that switch to record mode when you half press.
I'm not sure what you mean by set and half press?
I think the problem of not being able to show zebra in playback applies to all cameras that switch to record mode when you half press.
Great news, record mode zebra seems work, will need to try in daylight too.Thanks for confirming, I've checked this in for chdk 1.1 and 1.2, will appear in the next auto builds.
No change in playback mode.Yes, I haven't done anything about that problem yet, it's unrelated to the other issue.
Possibly add support extra long exposure mode for sx110is fw 1.0b camera? I tested the maximum 64sec exposure, working ok, with or without dark frame subraction. I need longer time exposure. There is more in the sensor.Someone would need to implement exp_drv_task for this port. In the meantime, you might try stacking multiple 64 sec (or less) exposures.
Someone would need to implement exp_drv_task for this port. In the meantime, you might try stacking multiple 64 sec (or less) exposures.Just reporting... I implemented the exp_drv_task, I sent the file to mngc for testing.
Good news! Nafraf test build working. The current max. succesfully exposure time is 10min 33 sec. I working on a better test and i will come back the result. I confused with some problems.While it would certainly be interesting to know when / how it fails, there isn't specific length of time that "should" work. We bypass the cameras built in limits, and you get whatever you get after that. IIRC a590 was also reported to return black images at some time before the 2048 second maximum.
I found lots of intersting thing with dark frame modes. Currently we have a great working set_raw_nr function. I always use this function for my extra long exposured images. I shot all normal images without dark frame substraction. For short daylight exposure, dark frame not requied, for long exposure one dark frame useful. For extra long exposure mode, lots of dark frame required. Currently no mode for record only dark frames. My method on a590is is simple hardware mod, i use tube ring and fake filter (opaque). On sx110 this method not working. No tube ring for this camera. For example, paper black box not good enough, the internal light too bright (camera LED, for example).
I found this topic on record dark frames, control with mechanical shutter from lua script. I don't know how to adopt for my camera.This should work in any build with "native calls" enabled. The function required to register the Mecha event procs may vary on some cameras. If the return value of call_event_proc is -1, then the function probably isn't registered. If this happens, someone here can probably find the correct function for you.
If i understand properly, this script switch a shooted double image to one normal and one dark frame pictures separate.You can just close the shutter and take one shot to make a dark frame.
The CCD sensor temperature is important, different normal and dark frame CCD temperature not good. This is one thing why it's not good to use very old dark frames.You could take a series of dark frames and log the CCD temperature. Then log the CCD temp when you shoot, and match them up.
very interesting topic, a540 camera record a normal and dark frame separateThat code saved the raw before and after the canon dark frame. That doesn't give you the actual dark frame (most likely Digic does the subtraction when it reads out the dark frame, and so it's never stored in ARM accessible memory), but the difference between the two would show you what has been subtracted out. However, this method requires new hooks in the ASM code for every camera. Using the mecha eventprocs to close the shutter is a much more efficient way to get dark frames.
http://chdk.setepontos.com/index.php?topic=1998.msg18450#msg18450 (http://chdk.setepontos.com/index.php?topic=1998.msg18450#msg18450)
This more recent script might interest you as well : http://chdk.setepontos.com/index.php?topic=8833.msg92195#msg92195 (http://chdk.setepontos.com/index.php?topic=8833.msg92195#msg92195)
This should work in any build with "native calls" enabled. The function required to register the Mecha event procs may vary on some cameras. If the return value of call_event_proc is -1, then the function probably isn't registered. If this happens, someone here can probably find the correct function for you.
Depending on camera and settings, you may need to open the shutter after taking the dark frame.
In CHDK 1.2, you don't need a special build to use native, you just have to turn the "Enable Lua native calls" option on in the misc menu.
You could take a series of dark frames and log the CCD temperature. Then log the CCD temp when you shoot, and match them up.
The script attached here may be useful http://chdk.setepontos.com/index.php?topic=9229.0 (http://chdk.setepontos.com/index.php?topic=9229.0)
If you are the owner of a SX110is we need your help improving the manual focus / subject distance override capability of CHDK.
Please read the instructions posted here < Link to Testing Instructions (http://chdk.setepontos.com/index.php?topic=11078.msg108859#msg108859) > and test your camera.
TIA.
Hi,
Script test log file for SX110is, no crash.
- If i powered on the camera with long press power button, everything is ok. Camera in record mode, and switch to picture review mode ok.This is not a bug. When CHDK starts, it doesn't know which button it was started with, and defaults to start in playback mode. If you hold down the power button for longer, CHDK gets a chance to notice that the power button is down and starts the camera in record mode.
- When powered on short press power buttton camera and chdk booted ok in picture review mode, but if i press the picture review/record mode switch, camera crash, and turned off.
- When powered on short press power buttton camera and chdk booted ok in picture review mode. If i press the shutter button camera switch to record mode, without error.
Simple demo. Start your camera with an SD card not containing CHDK by pressing the "Playback/Review" button. Then press that button again. Observe that it turns the camera switches off on the second press, just like in your example.When powered on short press power buttton camera and chdk booted ok in picture review mode, but if i press the picture review/record mode switch, camera crash, and turned off.This is not a bug.
Chdk default settings switchable to sort power button => record mode?No. This has been discussed many times.
The problem is that at start-up, CHDK does not know if it was started via the playback button or the power button. (Unless you hold the power button down as described above). If CHDK were to always power up in shooting mode, the lens will extend every time, which could result in mechanical damage if you were pressing the playback button and not expecting it.