CHDK Forum
CHDK Development => General Discussion and Assistance => Topic started by: HarpoMa on 05 / August / 2009, 13:12:41
-
Wikia Link - http://chdk.wikia.com/wiki/SD780IS (http://chdk.wikia.com/wiki/SD780IS)
Firmware Dump (original) - Firmware 100C (http://chdk.mydev.ca/IXUS100_SD780/ixus100_sd780_100c.zip)
Firmware Dump (8M Full Dump) - Firmware 100C - 8M Version (http://chdk.mydev.ca/IXUS100_SD780/8M_SD780_100C_fw.zip)
Firmware - See Autobuild (http://mighty-hoernsche.de/)
Wave - 1.00C (https://wave.google.com/wave/waveref/googlewave.com/w+oReiB0RmE)
Current status
Beta release from autobuild. Searching for bugs
Task List: (Updated March 20, 2010)
* Get the cam started - Done
* GUI output.
o General output - Done
o Histogram - Done
o Zebra mode DOES NOT WORK
o Fix grid - see msg34053 (http://chdk.setepontos.com/index.php/topic,2972.msg34053.html#msg34053)
* Logging output.
o OpLog functions
Progress: Dumped one type of OpLog
* Input Handler
o Keyboard handler - Done
o USB
* Shoot Task.
o control darkframe subtraction - Need Verify
o Bad Pixel - Need Verify
o Implement raw - Done
o Implement DNG - Done
o DNG4PS2 Color Profile - Done
o EXIF reporting
* Movie Task.
o Optical zoom - Done
o AF scan in video - Done
o Quality control - Need Verify (CHDK Bug here I think....)
* Multipartition boot
o Implement - Need Verify
* BASIC scripting
o Need Verify
* Lua scripting.
o Need Verify
* Overrides.
o Av - No Av on camera.
o Tv - Done (200+ Secs)
o ISO
o Subject Distance
o Bracketing in cont' mode
o Focus (set_focus)
Error Summary:
@Duke - Exif data is not correct when using overrides
@Duke - Not possible to switch between original canon modes auto and program while CHDK is loaded
@quikee - If "fast Ev switch" is enabled the Ev switching is bound to the same values as self timer (down).
Self timer is not recognized as continuous mode which makes it unusable for bracketing.
Could not get badpixel removal to work. I have a bad pixel and used badpixel file to set the coordinates of the pixel using DNG to determine the coordinate in an (raw) image editor.
Remaining video time in video mode is not shown if enabled.
@mstawick - * Cannot open RAW (even in IrfanView),
@mstawick - * Cannot open DNG in LightRoom, Photoshop; IrfanView opens,
@mstawick - * Menu sometimes dissappears (even in 'P' mode, when camera doesn't autofocus); i'm not sure exactly at what conditions this happens,
@mstawick - * The camera (canon-generic OSD while taking the shot) shows fastest time as 1/1500 (even if override is set higher) and the highest ISO as 8000 (same gets written in EXIF). I have compared shots taken with ISO8000 and ISO1600 - no difference. I don't know what to think about it. Either the real highest ISO is like 1600 or something doesn't quite work with override. Sorry if I have written something totally retarded,
@mstawick - * In "shutterspeed enum type" = "Factor" the longest time is 15". In "Ev step" is 64". Is this correct? I was hoping for longer,
Fixed --> @mstawick - * Bracketing doesn't work with custom timer. It does work with manual continuous shooting same as quikee (2),
@mstawick - * SUGGESTION perhaps Ev quick switching would be better with zoom-in / zoom-out controls with alt active; also navigation through menu would be easier with zoom-keys, or is it only me?
Fixed --> @drakon&kiserian - When i make movie and use optical zoom, after 3.0x (when digital zoom comes) i can't bring it back to 1.0x -it just stops ant 3.0x
@drakon - its it possible record video with more fps than 30? (slow motion) Responce: CHDK can not change the FPS or the codec used for video (edit: hardware limitation)
@twista - sometimes the chdk menu closes down
@twista - in the left bottom there is a grey stripe/balk(where ALT stands)
Fixed --> @twista - when i zoom i.e. 4x in video mode the zoom wont get back (another said this before i think)
Fixed --> @mstawick - At present ps.fi2 is the only way (although I found my issue and a fix will be shortly here)
@jensemann - In video mode the (half-pressed) AF Key doesn't work.
Fixed --> @mstawick - And I think that you have introduced a new BUG - when shooting picture in RAW format, the camera shuts down after saving the picture on the card. Only RAW is saved, without JPG.
-
I'm keeping my fingers crossed for this one! I can't help with development, but I can help with testing. Many thanks for your effort! Cheers
-
My fingers are crossed too. I have no knowledge about how to do things but if I can I'll help with testing.
Well done!
-
Awesome news!
I'm willing and ready to test (but not much use for anything else i'm afraid)
-
Awesome. You can really dump the FW by blinking the AF LED? You guys are geniuses!
-kap
-
Thumbs up! :)
I'm also willing to test.
Jens
Can someone please point me to where I can find more about this blinking stuff?
-
The best area I find is http://chdk.wikia.com/wiki/For_Developers (http://chdk.wikia.com/wiki/For_Developers)
If you look under the porting area and such you will find out how to build a blinker circuit (either audio port or RS232). Personally I prefer the RS232 version but that is personal preference it seems. When I have a bit more time I plan to post my methods and tools used for my efforts. They are based on a lot of work by others but have been modified for my desires.
Harpo
-
-
I hate to ask questions like this but can someone tell me their theories on why this is happening to me....
I can boot my port of CHDK as a PS.FI2 without issue (it turns on the light) The light turn on is in the entry.S of the loader area and uses...
LDR R3, =0xC0220128
MOV R2, #0x46
STR R2, [R3]
However, if I build a DISKBOOT.BIN with the exact same code it won't turn on no matter what button I press. I've read about the startup sequence but alas no joy for anything I do.
HarpoMa
-
DISKBOOT appears to not work on these new cameras where udumper doesn't work. This was noted in the sx200 thread.
-
Have a look at http://chdk.wikia.com/wiki/SX10 (http://chdk.wikia.com/wiki/SX10)
The SX10 also have DIGIC 4 and there are some source code examples.
-
Have a look at http://chdk.wikia.com/wiki/SX10 (http://chdk.wikia.com/wiki/SX10)
The SX10 also have DIGIC 4 and there are some source code examples.
SX10 is one of the older digic IV cameras, that does not have problems with diskboot and udumper.
-
SX10 is one of the older digic IV cameras, that does not have problems with diskboot and udumper.
Is there an alternative method, or is this where development is stuck at?
-kap
-
The status of the SD780 port is always updated in the first posting. You might be best to review the wiki as you seem interested and the wiki gives a great overview of the various methods you can employ to port a given camera.
-
I can confirm that at least on an OS X built using the instructions on the "how to build on Mac OS X" has an issue with the entry.S positions given to the loader. I have to add 0x11A0 to my core start position for it to find the right location.
I fully expect that position to change depending on how much padding it decided to add for various reasons. That said I'm ignoring it for the moment in favor of other jobs.
HarpoMa
-
Anyone know the history of how the following lines were determined for boot.c in the SX10 camera?
*(int*)0x1930=(int)taskCreateHook; //CHECK
*(int*)0x1934=(int)taskCreateHook2; //CHECK
*(int*)(0x25BC+4)= (*(int*)0xC0220134)&1 ? 0x2000000 : 0x1000000; //Orginal comment replacement of sub_FF8218C8 for correct power-on.
My main question is what function FF8218C8 was. I'm trying to find the equivalent in the SD780. Also how was 1930 and 1934 determined?
Thanks,
Harpo
modify - I'm gonna start using the sd990 as a reference due to the comments inside. Very nice work.
-
Anyone know the history of how the following lines were determined for boot.c in the SX10 camera?
*(int*)0x1930=(int)taskCreateHook; //CHECK
*(int*)0x1934=(int)taskCreateHook2; //CHECK
For the initial research, see here (http://chdk.setepontos.com/index.php/topic,234.msg1619.html#msg1619), although it didn't work at that time. Eventually it did however, see here (http://chdk.setepontos.com/index.php/topic,2900.msg29614.html#msg29614) and here (http://chdk.setepontos.com/index.php/topic,2972.msg30712.html#msg30712).
*(int*)(0x25BC+4)= (*(int*)0xC0220134)&1 ? 0x2000000 : 0x1000000; //Orginal comment replacement of sub_FF8218C8 for correct power-on.
My main question is what function FF8218C8 was. I'm trying to find the equivalent in the SD780.
Why don't you look at the disasm and find out? Otherwise, and before reyalp has time to step in and enlighten you, maybe his comments (ixus980_sd990, boot()) can help...
// similar to SX10 (but no +4 and values are >> 8) via sub_FF849EB0.
// Search on 0x12345678 finds function called by this
*(int*)(0x2588)= (*(int*)0xC02200F8)&1 ? 0x200000 : 0x100000; // replacement of sub_FF8219D8 for correct power-on.
-
I have tried to find the function sub_FF8218C8 but I think that was copied from another boot.c and the position has changed. I have started reading the threads you mentioned and there is a lot of help there so I'm gonna follow up on the IRQ handlers that 0x1930/34 seem to relate to.
Thanks,
Harpo
-
Well done HarpoMa!
-
I have tried to find the function sub_FF8218C8 but I think that was copied from another boot.c and the position has changed. I have started reading the threads you mentioned and there is a lot of help there so I'm gonna follow up on the IRQ handlers that 0x1930/34 seem to relate to.
You should be able to figure out if the 1930/34 are correct by searching for the constants in both an existing firmware (e.g. SX10) and you new one, and comparing how they are used. If you are using IDA, just search for sequence of bytes, 00001930
Or you can just try it. If it doesn't work, you know it's wrong. The other thing that could be wrong is the offset subtracted from p in taskCreateHook. You can probably find that by comparing the code as described above.
edit:
Is there a dump for this uploaded somewhere ?
-
There will be a dump shortly. I have some space I'm gonna start placing stuff for my attempts.
-
For webspace you can upload file on www.megaupload.com (http://www.megaupload.com)
Great work!!! :)
-
@HarpMa: Is it possible for you to upload your current version to the svn-server? Because I think the sd1200 I am working on is similar to sd780.
-
I'll post it to my site but as for placing in svn i think it's too early. Doesn't get very far yet. But for reference I can make it available...
Harpo
-
I do not suggest anyone other then a developer even look at this link. It will ONLY show your a logo.
{modified - removed URL since topic top now includes it}
Also, don't do a make clean. If you do then the stubs are likely going to break. I have not followed multiple guidelines on the making of this.
-
[Off-Topic - but I don't know where to direct this question. Promise to keep it short.]
After the last weekend and quite a lot of videos I realized that there is no auto-focus while taking a video. I couldn't belief this and called Canon today. Support employee #1 supposed my cam to be defective and advised me to send my camera to a local hardware contractor. Contractor #1 told me that this is totally normal. Called Canon again. Support employee #2 confirmed this. And stated, that this is true for many/most Canon cams. I still can't believe this.
(Meanwhile I found the Video Parameter: AF key that might be a workaround)
Can someone confirm, that this cam can't auto-focus while taking a video?
Jens
-
Yes.
It looks strange but it's true and is clearly stated in Users Manual.
AFAIK it can be fixed for other camera models with CHDK.
-
Yes.
It looks strange but it's true and is clearly stated in Users Manual.
AFAIK it can be fixed for other camera models with CHDK.
I read the manual before I bought the cam. Didn't get that.
Now keeping my fingers crossed a bit more, while waiting for a beta firmware,
Jens
-
With my SD1200IS udumper is not working, because the sequence of bytes 0000 0000 0000 0000 0000 0003 ... followed by adresses greater than MIN_ADDRESS (firmware jumps) has not been found:
#define MIN_ADDRESS 0xFF810000
...
for (i=0x1900;i<0xF0000;i+=4) {
if ((*(unsigned int*)(i+0x34)==0) &&
(*(unsigned int*)(i+0x38)==0) &&
(*(unsigned int*)(i+0x3C)==3) &&
(*(unsigned int*)(i+0x4C)>MIN_ADDRESS) &&
(*(unsigned int*)(i+0x50)>MIN_ADDRESS) )
{
...
}
}Any ideas modifying the udumper to work with SD780IS? Then I would like to try it on my SD1200IS.
-
I never used the udumper for the SD780. It may help to take the FW for the sd780 and look for the pattern of bytes around the functions required to fopen/fwrite/fflush/fclose Not certain if you can perform them that early in the boot cycle but might be worth a try. Note of course that the SD1200 will NOT have the same position for the functions. Only the pattern might match.
For the SD780 I dumped the first firmware with the blinker program (ie serially blink the firmware to the LED) For the second FW dump (8M version) I used the fopen/fwrite/fflush/fclose.
-
Could you publish the code you where able to dump the 8MB firmware with fopen/fwrite/fflush/fclose? It will be a try for my SD1200IS.
-
I think you misunderstand. My code for dumping came after I already had a version of it and therefore I simply made a certain key in CHDK dump the firmware with those function.....
fopen()
loop from 0xff800000
fwrite(a byte)
next loop
fflush()
fclose()
So if you can find those 4 functions and if the canon camera lets you actually run those at the time in udumper then you can strip out the functions in udumper and add the fwrite loop.
fyi - I have never found a function wr() in my canon fw that actually lets me call it like udumper wants...
Harpo
-
Have a look at http://chdk.setepontos.com/index.php/topic,221.msg3245.html#msg3245 (http://chdk.setepontos.com/index.php/topic,221.msg3245.html#msg3245) to see what jeff666's writes about the "wr"-function which stands for "WriteSDCard".
Meanwhile I verified, that my SD1200IS finds the signature, but calling the function do nothing. In the attachment you will find my full code compiling it with dryos.bat
-
Interesting read. Explains why I never found a wr function. However, that said I still have never had any success with udumper. I blinked it out.
The code you provided looks very similar (exact maybe) with what I tried with udumper but also for me it fails to exit the wr() function.
Harpo
-
Still have my fingers crossed Harpo. Happy that you're still working on the 780. Good luck.
-
Anyone have any suggestions for an ALTernate ALT key? The SD780 lacks a print key and this is the mapping. Any suggestions?
{ 0, KEY_UP , 0x00000008 },
{ 0, KEY_DOWN , 0x00000004 },
{ 0, KEY_LEFT , 0x00000001 },
{ 0, KEY_RIGHT , 0x00000002 },
{ 1, KEY_SET , 0x00004000 },
{ 1, KEY_PLAY , 0x00080000 },
{ 1, KEY_MENU , 0x00000800 },
{ 2, KEY_SHOOT_FULL , 0x00001001 },
{ 2, KEY_SHOOT_HALF , 0x00000001 },
{ 2, KEY_ZOOM_IN , 0x00004000 },
{ 2, KEY_ZOOM_OUT , 0x00002000 },
{ 2, KEY_PRINT , 0x00000040 }, //doesn't exist
{ 2, KEY_DISPLAY , 0x00000040 }, //swapped for print atm
I've thought about using display (as seen above) but there are canon menus that use DISP as an access key. I've thought about using a combo of KEY_SET + KEY_MENU but that pops up the Canon clock which kinda gets annoying.
Maybe KEY_ZOOM_IN/OUT + KEY_DISPLAY?
Thoughts on this?
Thanks,
Harpo
-
I got the German version (aka IXUS 100) with firmware 1.0.0.0. Nothing happens when having PS.FI2 in the root of my SD card.
Is there now an easy way to dump my firmware as well? How can I upgrade?
Doesn't the Wiki miss an entry of a accelerometer in the specifications (pics get rotated when rotating the camera).
-
How about shoot-half + set?. I'm thinking if people have already set up the positioning and framing of their camera, this key combo should do nothing to change it (if they have AEL and AFL set). I don't recall any functions in the chdk menus that require shoot-half + set. Zoom+display seems a bit fiddly because you might accidentally change the zoom, which of course disengages AFL and AEL.
Anyone have any suggestions for an ALTernate ALT key? The SD780 lacks a print key and this is the mapping. Any suggestions?
{ 0, KEY_UP , 0x00000008 },
{ 0, KEY_DOWN , 0x00000004 },
{ 0, KEY_LEFT , 0x00000001 },
{ 0, KEY_RIGHT , 0x00000002 },
{ 1, KEY_SET , 0x00004000 },
{ 1, KEY_PLAY , 0x00080000 },
{ 1, KEY_MENU , 0x00000800 },
{ 2, KEY_SHOOT_FULL , 0x00001001 },
{ 2, KEY_SHOOT_HALF , 0x00000001 },
{ 2, KEY_ZOOM_IN , 0x00004000 },
{ 2, KEY_ZOOM_OUT , 0x00002000 },
{ 2, KEY_PRINT , 0x00000040 }, //doesn't exist
{ 2, KEY_DISPLAY , 0x00000040 }, //swapped for print atm
I've thought about using display (as seen above) but there are canon menus that use DISP as an access key. I've thought about using a combo of KEY_SET + KEY_MENU but that pops up the Canon clock which kinda gets annoying.
Maybe KEY_ZOOM_IN/OUT + KEY_DISPLAY?
Thoughts on this?
Thanks,
Harpo
-
Maybe long-press MENU ?
-
Place the PS.FI2 in the root of the card. Start with the PLAY button. Goto menu and select firmware upgrade. This will load the new PS.FI2 file.
And for the easy dump of FW nope.
And for the missing entry you are correct. I had forgotten about that (not that I put the specs on there) but it may be an interesting feature avenue in CHDK.
I got the German version (aka IXUS 100) with firmware 1.0.0.0. Nothing happens when having PS.FI2 in the root of my SD card.
Is there now an easy way to dump my firmware as well? How can I upgrade?
Doesn't the Wiki miss an entry of a accelerometer in the specifications (pics get rotated when rotating the camera).
-
Thank you. Now that I read the FAQ more closely, I know a fw upgrade has to be started manually - my last camera (Pentax Optio S) behaved differently. Also it didn't pretend a false fw version unless persuaded (vers.req) - I also have 1.00C as I know now.
To make up for my former mistake I updated the Wiki about that accelerometer.
-
hey thx for your work. i want to ask how long it will take that u finish your work. i think the exact time can't say anybody but maybe you think that it will be finished in 3 weeks or 2 month?
-
Hi NooB here, maybe a dumb question but I just got the alpha version loaded to my camera. But it wont let me go from CHDK menu to shoot without shutting off my camera. Any suggestions. (First canon camera, first time using CHDK) Very cool stuff though
-
That's because it's not implemented yet.
PS:
Thanks Harpo for your efforts!
-
How about shoot-half + set?. I'm thinking if people have already set up the positioning and framing of their camera, this key combo should do nothing to change it (if they have AEL and AFL set). I don't recall any functions in the chdk menus that require shoot-half + set. Zoom+display seems a bit fiddly because you might accidentally change the zoom, which of course disengages AFL and AEL.
I don't think any combo involving half-shoot to be a good idea, since it would cause the lens to extend if you are in "play mode". I like to adjust every option first, then change to "rec mode".
I liked fe50's idea, it's a single button, so you don't need two hands, and it's intuitive. The only downside would be if you first enter Canon's menu, then you see CHDK's OSD. So it would be a menu over another menu, it could get confusing. But that's a minor annoyance, since you could just press menu once, then long-press.
Aren't there any other cameras without the "print" button with CHDK working?
-
I'll answer the various questions above.
I agree to what you say about the half-shoot solution. It does work but causes interface issues. ALT is used in many places. :( I'm thinking either making long-menu or long-display enter the ALT mode. I'll check out the other cameras and see if any have no-print buttons.
As for the questions of time lines... I think intial work will be a couple to three more weeks (provided life doesn't get in the way). After that it's hard to say. This is my first port and I imagine bugs persist for a while.
As for the firmware it is very young and not worth testing with at all. It was simply a proof that I'm actually working on it. LOL I'll post a newer firmware tommorow that actually does stuff....
Harpo
-
very good work HarpoMa!! today i bought ixus100 and i need chdk for this camera :) i don't know how i can help because i not have idea of programing,...
Sorry for my inglish, i'm spanish... xD
-
Today is a sad day for me... I stopped being lazy just to find out my camera has firmware 1.00b. Tested today's pre alpha anyway, and nothing. Camera just turns off, and won't turn back on until batteries are removed. I know there is at least 1 version of CHDK that work on firmwares with a different letter (my old camera, SD1000), but I don't think I should keep my hopes up, right?
I don't know anything about porting, and until I graduate in December, I won't even try to learn. Maybe by then there will be an easier way to extract the firmware other than by blinking.
In any case, keep it up
-
sorry but i'm very stupid...how i can build pre-alpha build xD?
-
i test pre-alpha chdk for ixus100 and it run correctly but crashes continously and the most features don't run
Good job HarpoMa
-
Unfortunately I've got FW1.00B. Pre-alpha behaved as voodoolady described. Tried the modified udumper that was reported to work on the SX200, but no joy.
-
If either of you 1.00B fw users can dump your firmware I will try to make an appropriate 1.00B build.
Harpo
-
sorry but i'm very stupid...how i can build pre-alpha build xD?
In the wiki under development you will find build methods.
Harpo
-
thanks HarpoMa, i tested pre-alpha but don't run any function...
God work
-
I'm useless at hardware hacks. Unless people have figured out a software-only method for dumping from the SD780, I'm not going to be of much help. Seems weird that the modified udumper only works with the SX200 and none of the other new cams.
If either of you 1.00B fw users can dump your firmware I will try to make an appropriate 1.00B build.
Harpo
-
I'll answer the various questions above.
I agree to what you say about the half-shoot solution. It does work but causes interface issues. ALT is used in many places. :( I'm thinking either making long-menu or long-display enter the ALT mode. I'll check out the other cameras and see if any have no-print buttons.
As for the questions of time lines... I think intial work will be a couple to three more weeks (provided life doesn't get in the way). After that it's hard to say. This is my first port and I imagine bugs persist for a while.
As for the firmware it is very young and not worth testing with at all. It was simply a proof that I'm actually working on it. LOL I'll post a newer firmware tommorow that actually does stuff....
Note that some cameras let you choose your alt button, search for CAM_ADJUSTABLE_ALT_BUTTON in the code.
One idea I had is using the play button. You could have a long press do the original function. Requiring a long press to get to alt mode is more annoying IMO, because you frequently want to get into alt and quickly change something.
My reasoning (based on using the SD990, I'm assuming the ixus 100 works the same way) is: In play mode, the canon behavior is also weird and mostly useless. It shuts down only if the lens is already retracted. In record mode, holding down the button slightly longer to go to play wouldn't be a big deal.
Downside, this could be very confusing for new users.
-
what is the status of the port of ixus100 HarpoMa?
I'm very impatient xD
thank you
-
what is the status of the port of ixus100 HarpoMa?
I'm very impatient xD
thank you
There is no point in being impatient or even stating it. The port status is always updated in the first post of this thread. If you need more then that I'm sorry but there is no more. If this still does not help feel free to return in 6 months. I'm sure by then a stable release will be done.
Harpo
-
There is no point in being impatient or even stating it. The port status is always updated in the first post of this thread. If you need more then that I'm sorry but there is no more. If this still does not help feel free to return in 6 months. I'm sure by then a stable release will be done.
Harpo
Well said!
-
This is probably better addressed in the development forum
Ok. I have my new port dumping (sd780) a really raw image. However even rawtherapee does not open it... How do I determine if the file that is being dumped is valid in any way? The raw is 12-bit. I've read that I may need to add a new setup to dcraw for my new camera? Should I drop RAW entirely and use DNG for determining if things are going ok?
I'm a little confused how I should debug a RAW output that has no format. LOL
Any advise or links are appreciated.
If you just want a quick look to see if the image is right, there are some programs you can load it into. For example, using irfanview you can use "open as->raw file" and then set the parameters you think are right for your cam. If you have the right buffer in CHDK and the right parameters, you'll see an image.
You can also write a very simple program that takes the 12bpp packed it into something more common (like 8 or 16 bit raw which you can then load as a greyscale in photoshop or gimp). I've attached the one I used in the sd990 port.
For actual shooting, I'd probably just go with DNG, although you could certainly hack dcraw if you want.
-
Thx. I will head in that direction for debugging it.
Harpo
-
I wanted to thank you for the suggestion of irfanview. I can now actually see the raw file and amazing but it has the image I took. LOL
Harpo
-
Hi.
I have tried the V3 firmware and want to report my experience:
Storing of RAW works but as already said.. no program recognizes the file.
Saving to DNG also works once "badpixel.bin" is present.
For badpixel.bin creation I used badpixel.lua which worked after some retries, but I don't know if the content contains correct badpixel data or not.
Additionally I have tried a simple lua script which did not work.
Lua script:
--[[
@title Test Lua Script
]]
function forceRecordMode()
repeat
if get_mode() == false then
cls()
print("Run in Record mode!")
sleep(3000)
cls()
exit_alt()
sleep(1000)
end
until get_mode() == true
end
function fastShoot()
press("shoot_half")
print("shooting...")
press("shoot_full")
release("shoot_full")
release("shoot_half")
repeat
sleep(1)
until get_shooting() ~= true
end
forceRecordMode()
fastShoot()
Function forceRecordMode() works but function fastShoot() doesn't work (no picture is taken) however completes without an error.
Anyway.. keep up the good work.
-
@Quikee,
Thx for trying it out. Your observations are 100%. I only started looking at the scripts last night. Turns out my kbd.c was missing the code (i wondered what it was for) that would implement scripted actions. LOL
The badpixel.lua will work as you said until I release v4. As you thought it is not valid data but is required for DNG output to work. You can try irfanview if you want to see the raw file but DNG is easier.
I'll get forceRecordMode lua working tonight and release v4. Then you can try it again.
Again thx and things should be better soon. It's still pre-alpha so most things don't work at all. It's really just a pretty gui atm.
Harpo
-
It's been a bit but I'm looking for SD780 testers now. If you want to test please create a post and submit your bugs. There are tons of stuff thats wrong i'm sure but I'll just work out each bug and hopefully it covers more then just that bug.
I prefer to have people create a single post and update it as bugs are fixed and retested. So if you could follow that style it will help me greatly. As bugs are fixed just use the strikeout style.
As always the first post has the latest info on status on build info. For your convienence i will place it here too...
Pre-Alpha Firmware (v5 updated Sept 19, 2009) (must rename ps.fi2) - PS.FI2 (http://chdk.mydev.ca/IXUS100_SD780/PS_prealpha_v5.FI2) (Note: ALT is DISP key & DISP key is long held DISP)
Thx.
HarpoMa
-
I will start testing on thursday, as soon as my camera gets back to me. If I manage to build this ;/
Right now I'm getting:
-> main.elf
../platform/ixus100_sd780/libplatform.a: could not read symbols: File format not recognized
collect2: ld returned 1 exit status
make[1]: *** [main.elf] Error 1
make: *** [all-recursive] Error 1
I'm building with:
gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3
Any help appreciated. Also, if someone could send me pre-built package, this would be cool. Thanks!
-
I will test as much things as I can as soon as I get my Ixus back - which is unfortunately not before Monday.
I am glad you got movie overrides to work because the default bitrate of around 20kbit/s is just overkill. I have reencoded the videos and got an acceptable quality at almost 1/10 of the size of the original.
-
I'm building with:
gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3
Any help appreciated. Also, if someone could send me pre-built package, this would be cool. Thanks!
Looks like you are ending up with a mix of arm and non-arm tools. Note that CHDK is picky about the toolchain, you can't just use someone generic ARM cross compiler, you need to either build it yourself or use one of the pre-built ones specifically configured for CHDK. Then you need to set your path and other environment variables so that is used for the entire build process.
-
@mstawick
also make sure you're not using binutils 2.19 or greater
wim
-
I just started testing
* On video the the optical zoom will zoom in then the digital zoom will take over
But when you zoom out only the digital works. When it gets to optical zoom i get a "!"
-
The current source is not upto date. Just use the PS.FI2 for now...
Harpo
I will start testing on thursday, as soon as my camera gets back to me. If I manage to build this ;/
Right now I'm getting:
-> main.elf
../platform/ixus100_sd780/libplatform.a: could not read symbols: File format not recognized
collect2: ld returned 1 exit status
make[1]: *** [main.elf] Error 1
make: *** [all-recursive] Error 1
I'm building with:
gcc (Ubuntu 4.3.3-5ubuntu4) 4.3.3
Any help appreciated. Also, if someone could send me pre-built package, this would be cool. Thanks!
-
OK, thanks for support. BTW, I finally managed to build it under Windows using chdk-shell.
-
Hi, I've been following this thread since the first post, and registered just now to help testing, although i'm new to CHDK and have never used it before. But i bought the Ixus 100 having in mind that someone would hopefully make a port.
And HarpoMa, you did a great job so far. Thx for that! :D
Since i'm new to CHDK i'm just getting started, but there are 2 issues i noticed so far:
- Not possible to switch between original canon modes auto and program while CHDK is loaded
- Exif data is not correct when using overrides
But i'm sure you are aware of that. ;)
Looking forward get myself into scripting, but i have not tested that yet, cause you haven't touched that by now, as stated in your first post.
Great work so far, keep going. :)
-
@Duke,
Feel free to try anything. I haven't specifically touched scripting but that doesn't mean it doesn't work. Lots of area is generic and works once the base port is working. If you do end up testing it just edit your original post and I'll watch for any changes.
Harpo
-
Issues I found:
- If "fast Ev switch" is enabled the Ev switching is bound to the same values as self timer (down).
- Self timer is not recognized as continuous mode which makes it unusable for bracketing.
- Could not get badpixel removal to work. I have a bad pixel and used badpixel file to set the coordinates of the pixel using DNG to determine the coordinate in an (raw) image editor.
- Remaining video time in video mode is not shown if enabled.
This is for now...
-
Two more (small?) issues:
- in video mode the AF Key doesn't work (I thought it did on my first test...)
- CHDK menu exits if cam autofocus detects something
But still I'm absolutely impressed by your great work Harpo! :-) *bow down*
Jens
-
I was able to successfully load alpha V5, I'll put bugs here.
-kap
-
Bug list:
=====
No new ones.
These were copied by HarpoMa to the summary, so I 'removed' them:
* Cannot open RAW (even in IrfanView),
* Cannot open DNG in LightRoom, Photoshop; IrfanView opens,
* Menu sometimes dissappears (even in 'P' mode, when camera doesn't autofocus); i'm not sure exactly at what conditions this happens,
* The camera (canon-generic OSD while taking the shot) shows fastest time as 1/1500 (even if override is set higher) and the highest ISO as 8000 (same gets written in EXIF). I have compared shots taken with ISO8000 and ISO1600 - no difference. I don't know what to think about it. Either the real highest ISO is like 1600 or something doesn't quite work with override. Sorry if I have written something totally retarded,
* In "shutterspeed enum type" = "Factor" the longest time is 15". In "Ev step" is 64". Is this correct? I was hoping for longer,
* Bracketing doesn't work with custom timer. It does work with manual continuous shooting same as quikee (2),
* SUGGESTION perhaps Ev quick switching would be better with zoom-in / zoom-out controls with alt active; also navigation through menu would be easier with zoom-keys, or is it only me?
-
i've never used canons and i'm very happy with chdk! Thanks you for your job.
I found a bug. When i make movie and use optical zoom, after 3.0x (when digital zoom comes) i can't bring it back to 1.0x -it just stops ant 3.0x
-
it's possible av overrides in ixus100 with chdk??
-
nope, ixus100 doesn't have mechanical aperture - just ND filter. this sucks, but can't do anything with it.
-
ok, thanks
-
and it's possible record video with more than 30 fps ??? ( slow motion )
Sorry for my bad english...
-
nope, ixus100 doesn't have mechanical aperture - just ND filter. this sucks, but can't do anything with it.
I just want to see if I'm understanding this correctly, are you saying there is NO manual aperture control for this camera?
Thanks,
-kap
-
nope, ixus100 doesn't have mechanical aperture - just ND filter. this sucks, but can't do anything with it.
I just want to see if I'm understanding this correctly, are you saying there is NO manual aperture control for this camera?
Absolutely correct; the IXUS (SDxxx) series - and also some of the cheaper A series cameras - don't have a real aperture (iris diaphragm).
-
i have a problem. i made my 2gb sd card bootable and now i have a fat16 partition named chdk and a fat32 partition named camcard. i copied the newest ps.fi2 file into the root directory of the fat16 partition but i have got no firmware update button to click in the menu when i'm in the play mode.
the fat32 partition of the sd card is empty and on the fat16 partition there is only ver.req and ps.fi2
i'm sure i made a mistake but i dont know where.can anybody help me. i want to help to find issues in the chdk
note: i have version 1.00c
-
i have a problem. i made my 2gb sd card bootable and now i have a fat16 partition named chdk and a fat32 partition named camcard. i copied the newest ps.fi2 file into the root directory of the fat16 partition but i have got no firmware update button to click in the menu when i'm in the play mode.
the fat32 partition of the sd card is empty and on the fat16 partition there is only ver.req and ps.fi2
i'm sure i made a mistake but i dont know where.can anybody help me. i want to help to find issues in the chdk
note: i have version 1.00c
There's no need for partitioning a 2GB SD card !
Partitioning is only needed when you wanto the autostart with a card bigger than 4GB.
Just format your 2GB SD card in the camera (up to 2GB the fs is FAT16 by default),
then copy the diskboot.bin and PS.FI2 files to the card's root folder.
Power on the camera with the PLAYBACK button (the one with the blue [>]),
start CHDK with the Canon firmware update menu item (you'll see this item only when you power on in
playback mode, i.e. the lens is retracted).
Now you can select "Make card bootable" from the CHDK menu (in Miscellaneous -- Make card bootable...).
Lock the card, CHDK now should start automatically...
-
no way..i formated the sd card with the camera.then i copied the newest ps.fi2 file and the diskboot.bin file from the pre-alpha build on the first page and started the camera with the play button the lens was retracted. but i can't find the update item in the settings.
then i tried this one:
http://chdk.wikia.com/wiki/FAQ#Q._How_do_I_get_CHDK_onto_my_camera.27s_SD_memory_card.3F (http://chdk.wikia.com/wiki/FAQ#Q._How_do_I_get_CHDK_onto_my_camera.27s_SD_memory_card.3F)
here it says that i also have to copy the chdk folder in the root directory, so i copied the chdk folder into the root directory but nothing happened.i've tried all this with locked card and unlocked card but it is the same
-
I thought that only method to load Chdk on ixus100 was via firmware upgrade trick. Did something change?
Twista:
just format the card with fat16, put PS.FI2 and diskboot.bin there. Then press play, menu, and firmware update should be at the very bottom. That's how it works for me.
-
it's possible record video with more fps than 30? (slow motion)
-
i tried it several times but in my menu there is no firm update item, i dont understand it.
i'm on mac os..is this a problem?
-
i'm on mac os..is this a problem?
quite likely, yes.
here's the FAQ for mac: http://chdk.wikia.com/wiki/FAQ/Mac (http://chdk.wikia.com/wiki/FAQ/Mac)
hth,
wim
-
yeah i tried this before and now i tried it again. but when i put the diskboot.bin into the root directory AND lock the card the camera wont start-whats this?
when i unlock the card the camera starts but then i cant update the firmware because there is no update item
-
@twista
have you also read the "Still having Trouble?" section (almost end of page) ?
edit: and what card (size) are you using ?
@drakon
it's possible record video with more fps than 30? (slow motion)
CHDK can not change the FPS or the codec used for video (edit: hardware limitation)
hth,
wim
-
@whim: thx the "still having trouble" post solves my problem. sometimes mac is not good :)
Issues:
-sometimes the chdk menu closes down
-in the left bottom there is a grey stripe/balk(where ALT stands)
-when i zoom i.e. 4x in video mode the zoom wont get back (another said this before i think)
-
thx whim :)
-
@twista
make no mistake, LoseDows is every bit as bad... it's just that it is too stupid to pull this kind of stunts on FAT file systems :D
wim
in the left bottom there is a grey stripe/balk(where ALT stands)
that could well be the 'space remaining' bar, check:
main menu -> OSD parameters -> Filespace -> Show Space Bar
yours is probably set to 'Horizont.' , set to 'Don't' to get rid of it ("balk"enende :D )
-
@mstawick - At present ps.fi2 is the only way (although I found my issue and a fix will be shortly here)
@everyone else - I won't get to look at any of the bugs until the weekend - working on finding some debug info atm.
-
* Menu sometimes dissappears (even in 'P' mode, when camera doesn't autofocus); i'm not sure exactly at what conditions this happens,
It appears that in "Auto" mode the menu disappears not when autofocusing but when the shooting mode is switched automatically (for example from Sunny to Macro).
In "P" mode menu disappears when a face is detected.
The obvious solution would be (if that's possible) to disable automatic mode switching and face detection while in menu.
-
I never use face detection, and still menu disappears. BTW. it's a minor problem, as the menu is still there, just needs to be redisplayed - ex. by up/down button.
-
I never use face detection, and still menu disappears. BTW. it's a minor problem, as the menu is still there, just needs to be redisplayed - ex. by up/down button.
This is normal on all CHDK ports. A canon screen update erases the CHDK display.
-
@quikee & @mstawick -
I'm trying to understand the Ev bug you reported.
If "fast Ev switch" is enabled the Ev switching is bound to the same values as self timer (down).
Do you mean that when "fast Ev switch" is enabled that you cannot use it when you are using the self timer in CHDK or in the regular canon firmware? My experience seems to indicate that it does work but is awkward. IE, the up button brings up the timer screen. I tried it out and despite bringing up the timer screen it does actually move the Ev setting.
Is this your suggestion that it's most a usability bug then a functional bug? I agree if that is what you are saying.
I think I will make the Ev quick change <alt>+zoom instead as suggested but want to make certain there is not a different bug.
Self timer is not recognized as continuous mode which makes it unusable for bracketing.
Can you expand on this. I'm new to CHDK functions and I don't know what this really means. If you walk me thru what you did and why its wrong that would be great.
Bracketing doesn't work with custom timer. It does work with manual continuous shooting same as quikee (2),
This too. I'm not certain.
Once I better understand I'll either fix the underlying issue or move the +/- bracketing to the <alt>+zoom.
Thanks,
Harpo
-
Bracketing doesn't work with custom timer. It does work with manual continuous shooting same as quikee (2),
This too. I'm not certain.
Once I better understand I'll either fix the underlying issue or move the +/- bracketing to the <alt>+zoom.
This may be similar to the sx200, where the propcases values used in each case have changed slightly. See the recent sx200 related checkins
http://tools.assembla.com/chdk/changeset/804 (http://tools.assembla.com/chdk/changeset/804) change to generic/shooting.c and core/raw.c
and
http://tools.assembla.com/chdk/changeset/805 (http://tools.assembla.com/chdk/changeset/805)
If this is the case, please make a note of it on the wiki http://chdk.wikia.com/wiki/Propertycase (http://chdk.wikia.com/wiki/Propertycase)
edit: this is discussed in the sx200 thread starting around page 27 http://chdk.setepontos.com/index.php/topic,3994.390.html (http://chdk.setepontos.com/index.php/topic,3994.390.html) but it's mixed with a lot of other stuff ;)
-
@reyalp
Does 102 only change while shooting? 223 follows as documented for the SX200. 102 changes I cannot see on screen but a dump of all propertyCase values during the shooting shows the 102 property becoming 1 at times. Is this what the SX200 does?
Harpo
-
Does 102 only change while shooting? 223 follows as documented for the SX200. 102 changes I cannot see on screen but a dump of all propertyCase values during the shooting shows the 102 property becoming 1 at times. Is this what the SX200 does?
I'm not sure, I don't own a propset 2 camera.
-
@Harpo
Is this your suggestion that it's most a usability bug then a functional bug? I agree if that is what you are saying.
Yes - it's a usability bug. When you press 'down' button to decrease Ev, also the timer menu appears. Then you have to wait for menu to dissappear before further decreasing Ev, otherwise you set timer on. So it becomes slow Ev switching rather than fast :)
Self timer is not recognized as continuous mode which makes it unusable for bracketing.
Bracketing doesn't work with custom timer. It does work with manual continuous shooting same as quikee (2),
Can you expand on this. I'm new to CHDK functions and I don't know what this really means. If you walk me thru what you did and why its wrong that would be great.
CHDK has a function of auto bracketing - when it is set, and you are shooting in continuous mode (literally - canon menu gives you choice between 'Single shot' and 'Continuous') the following shots get different shot params, ex. Ev. Lets say first shot gets Ev=0, second Ev=+1, third Ev=-1. Now this works when you set the camera to shoot in 'Continuous' mode and hold the trigger by yourself. It would be nice if it also worked for timer set to take ex. 3 pictures. I hope I managed to explain the case.
-
hello.
i have firmware version 1.00B... is it possible to mount the actual chdk version? i tried with formating a 4gb sdhc-card, copying diskboot.bin and ps.fi2 in the root of the card, started my cam with the play button, menu and then firmware update.so far so good, but when i press "ok" for the firmware update, my cam turns black and responds only when i remove the battery.
another question: do i have to copy the chdk folder on the card?
edit: i dont use a mac...
-
@hektor
See the earlier posts in this thread. This version will not work for you, but if you manage to dump the firmware, I think that Harpo said that he might make required changes.
-
unfortunately i dont have the knowledge and time to do this. otherwise i would dump immediately...
-
Sadly without someone with 1.00B dumping the firmware it will never be supported. (Or sending their camera to me...LOL)
-
Like I said before, I'm graduating this December, and untill then, I'll be pretty busy. After that, if nobody else managed to get 1.00B out of their cameras, I will give it a shot.
-
FWIWI, doing a new sub from an existing completed port is usually straightforward. See http://chdk.wikia.com/wiki/Adding_support_of_a_new_firmware_version (http://chdk.wikia.com/wiki/Adding_support_of_a_new_firmware_version)
-
Does CHDK bracketing work only for RAW capture? Is bracketing of JPG (other then native canon fw) done by script?
-
Does CHDK bracketing work only for RAW capture? Is bracketing of JPG (other then native canon fw) done by script?
No, bracketing works whether or not you have raw enabled.
-
-
Can someone confirm that when doing zooming in a movie that when returning from digital zoom (reentering optical zoom) that you must stop the zoom lever and then continue.
IE - When on the SD780 I zoom to 12x (3 optical * 4 digital); when returning to 0 zoom i have to let the lever alone at the boundary of the optical and digital zooms? If this is not the case on other cameras I have a bug to fix otherwise I don't. LOL
Thanks,
Harpo
-
This one is missing on bug-list:
- in video mode the (half-pressed) AF Key doesn't work.
As far as I know, a half-pressed AF key should trigger an auto-focus run in (hacked!) video mode.
Jens
-
Can someone confirm that when doing zooming in a movie that when returning from digital zoom (reentering optical zoom) that you must stop the zoom lever and then continue.
Works that way on my cam! It would be nice if it also stopped when zooming-in. Right now it pauses for a moment, and than digital zoom kicks in. Do you think you could add an option to block digital zoom in video mode? There is such a function for photo-shooting.
And I think that you have introduced a new BUG - when shooting picture in RAW format, the camera shuts down after saving the picture on the card. Only RAW is saved, without JPG.
-
@mstawick - There is a canon fw item for disabling the digital zoom. Is there a reason that does not fit your need? If so I'll look to adding an option for disabling digital zoom in video.
I also agree I have added a new bug in the raw processing. LOL must have been when i merge in 810 changes. I'll take a look tonight and release v7. I was using all non-raw during my bracketing testing.
-
@Harpo
Sorry, I'm retarded ;) I disabled digital zoom being in shooting mode, then switched to video-recording mode. I thought that it was a global setting. Everything is cool now, that I disabled digital zoom in video-recording mode. I hate digital zoom, it should have never been invented >:(
It's extremely cool that you managed to fix autobooting - loading firmware every time you want to take a photo would be a bit annoying.
-
-
Warning, newbie question ahead.... is there an alpha for the 780is to try yet? If not, any guesses when one will be available? A functioning beta? I'm mostly interested in using it to do time lapse recording. Very excited to enable that function with this camera. As others, I'm very available to test!
best wishes,
Paul Lundahl
eMotion studios
http://www.emotionstudios.com (http://www.emotionstudios.com)
-
Post #1 has everything you should need.
-
Hi, bugreport:
- Switch to AUTO mode is not working with the custom firmware in record mode. Switch between MOVIE and PROGRAM works
-
Hi, bugreport:
- Switch to AUTO mode is not working with the custom firmware in record mode. Switch between MOVIE and PROGRAM works
Sorry, Duke already mentioned this...
-
Do you really need this stupid automode? :)
ps
Will it be possible to control ISO in movie mode?
-
Do you really need this stupid automode? :)
I don't.
But sometimes my wife also wants to use the camera...
-
Is there any way to manually adjust the flash brightness level?
I get lots of pictures that turn out too bright.
Thanks
-
@kiserian
You can control flash power and I do believe it even works. "Power of flash" under picture options.
-
Sorry, I know this is a really dumb question, but can anyone assist me in loading the CHDK file onto my camera? I've tried a bunch of ways with no success, and I've had a hard time applying the instructions for the rest of the cameras to mine.
Any assistance would be a big help. I think I'm just missing something small.
-
The method is always the same. Either you will use the diskboot.bin or the ps.fi2 Have you looked at the wiki .. http://chdk.wikia.com/wiki/CHDK_for_Dummies (http://chdk.wikia.com/wiki/CHDK_for_Dummies) Are you using a SD780, if so then you must get both of the files in post #1 and copy to card. If you use diskboot.bin you must use card tricks to make your SD card bootable.
Harpo
-
Yeah, I am using the sd780. I've looked at the instructions, but I can't seem to do it properly. Once I have the files on the SD card, how do I activate it? I'm using a mac, btw.
Also, I see there is the alpha build, as well as diskboot.bin and the ps. file. Which one do I use? I even tried using the script that can do it for you for macs with no success...
Thanks for the quick response.
-
Yeah, I am using the sd780. I've looked at the instructions, but I can't seem to do it properly. Once I have the files on the SD card, how do I activate it? I'm using a mac, btw.
Hi, jtrick33
Fiirst of all did you try firmware update method, http://chdk.wikia.com/wiki/%22firmware_update_method%22 (http://chdk.wikia.com/wiki/%22firmware_update_method%22)
If you don't see "Firm Update" on the Canon menu, then you will have to go back to http://chdk.wikia.com/wiki/FAQ/Mac (http://chdk.wikia.com/wiki/FAQ/Mac)
particularly, http://chdk.wikia.com/wiki/FAQ/Mac#Still_Having_Trouble.3F (http://chdk.wikia.com/wiki/FAQ/Mac#Still_Having_Trouble.3F)
HTH, Cheers.
-
I tried to do the Mac FAQ to the best of my ability, but I'm still not getting anything about updating the firmware..
I tried the script installer again, as well as doing it manually.
I still can't figure out why I can't get the thing to load properly....any chance someone might be able to throw together a simple step by step? I'm totally new at this.
Thanks for everyone's help!!!
-
Yeah the Mac always places the wrong case and extensions if I recall correctly.
-
What's the best way to go about fixing that??
Did everyone who has it on their camera just follow the instructions as written?
-
What's the best way to go about fixing that??
The best way to fix it is to understand the information you have been given.
Did everyone who has it on their camera just follow the instructions as written?
Essentially, yes. All the required information is there.
This thread is for development, not basic install help. The install process does not depend on which camera you have, and has nothing to do with the specific port.
The manual loading method is extremely simple. All you have to do is
1) copy the files to the root of your SD card. If using a Mac, make sure that it doesn't do stupid magic behind your back http://chdk.wikia.com/wiki/FAQ/Mac#Still_Having_Trouble.3F (http://chdk.wikia.com/wiki/FAQ/Mac#Still_Having_Trouble.3F) 99% of Mac users problems are caused by this.
2) insert the card and start the camera in play mode
3) press the menu button, and scroll down to "firm update"
If you continue to have problems, please start a new thread in http://chdk.setepontos.com/index.php/board,34.0.html (http://chdk.setepontos.com/index.php/board,34.0.html)
describe exactly which instructions you followed, and what the result was. Just saying "I tried to follow the FAQ and it didn't work" doesn't give enough information for anyone to help you. The install process is known to work. If it doesn't work for you you are doing something wrong. If you want help, you have to give us enough information to figure out what you did wrong.
-
@jtrick33,
Can you tell us which size SD card you are trying with? and post at http://chdk.setepontos.com/index.php/board,34.0.html, (http://chdk.setepontos.com/index.php/board,34.0.html,)
(General Discussion and Assistance)
edit: reyalp was quicker :)
-
Just tested out the Pre-Alpha Firmware (v7 updated Sept 30, 2009) on my IXUS 100 IS and it is very promising! The menus were glitchy and I was unable to open the CRW file, have not tested DNG yet, but i am impressed.
-
Oh my god reyalp, I don't know why, but the four step instructions you laid out totally worked. I was going through those long instructions about partitioning etc. Thank you so much for your help. Right to the point...Love it.
-
Is the modified udumper working on the SD780? I'd like to try it on my 1.00B camera.
-
Never tried. But you can try it and tell us. :)
-
I tried the diskboot.bin from http://chdk.setepontos.com/index.php/topic,4095.msg39924.html#msg39924 (http://chdk.setepontos.com/index.php/topic,4095.msg39924.html#msg39924) and couldn't get anything.
I'm not sure how universal these modified udumpers are, or how easily they can be adapted to different cameras.
-
We've figured out the diskboot code, but the udumper code itself probably needs adjustment.
whatever changes worked in this thread http://chdk.setepontos.com/index.php/topic,4310.15.html (http://chdk.setepontos.com/index.php/topic,4310.15.html) may be applicable.
-
@reyalp - heads up
New palette seems to be required for the SD780 - I've matched the colors somewhat to name but any suggestions other then "seem to pick the right #"?
Also note that SCREEN_COLOR from the gui_bench.c will need to be moved because 0xF7 is white for me. :(
-----
#elif CAM_BITMAP_PALETTE==4
#define COLOR_TRANSPARENT 0x00
#define COLOR_WHITE 0x01 //lots to pick from...
#define COLOR_RED 0x75
#define COLOR_GREY 0x15
#define COLOR_GREEN 0xC3
#define COLOR_BLUE_LT 0x7B
#define COLOR_BLUE 0x8C
#define COLOR_YELLOW 0x52
#define COLOR_BLACK 0xFF
#define COLOR_BG 0x44
#define COLOR_FG COLOR_WHITE
#define COLOR_SELECTED_BG COLOR_RED
#define COLOR_SELECTED_FG COLOR_WHITE
#define COLOR_ALT_BG 0xD4
#define COLOR_SPLASH_RED 0x75
#define COLOR_SPLASH_PINK 0x60
#define COLOR_SPLASH_GREY 0x15
#define SCREEN_COLOR COLOR_SPLASH_GREY
-
@reyalp - heads up
New palette seems to be required for the SD780 - I've matched the colors somewhat to name but any suggestions other then "seem to pick the right #"?
Not really. If you (or one of the other testers) has another CHDK camera, you can try to find the best match by comparing them side by side. Really it doesn't matter much as long as all the displays are legible.
Also note that SCREEN_COLOR from the gui_bench.c will need to be moved because 0xF7 is white for me. :(
Everything that uses hard coded color constants should be centralized in the palette ifdefs. Note that SCREEN_COLOR is defined separately in multiple files, and the games have several other hard coded defines ;)
I apparently missed a bunch of stuff when I did the SD990
-
hm.. i tried to make dng and irfan says that size of picture is only
1988 x 1488 Pixels (2.96 MPixels) (4:3)
i guess it's not ok.
-
hm.. i tried to make dng and irfan says that size of picture is only
1988 x 1488 Pixels (2.96 MPixels) (4:3)
i guess it's not ok.
I guess your guess is wrong... ;)
They have about 2 megapixels, compared to 8 megapixels in the jpeg files. I do not think it's a probem of "Raw Photo Processor",
Many viewers / image processing tools shows either 1/2 the image or only a small thumbnail of RAW files by default due to performance/faster response...e.g. in XNView: "Camera RAW: half size / full size / thumbnail only"
--> There's also such a setting for RAW images in Irfanview !
-
Do we gain any more details with RAW images besides uncompressed images (e.g. more bit depth and so on)?
-
deleted
-
2 fe50
mmmkay :)
You are defenitly right! I've found options. Now it's 3976 x 2976. Thanks
2 JustMe2
Irfan shows that picture has 24 bit (hm my Nikon's nef has 12.. ;( )
There is lot of noise in dng. But Photoshop+Imegenomic Noiseware is much better than antinoise algorithm in ixus100
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg11.imageshack.us%2Fimg11%2F9284%2Fdngcanon.jpg&hash=1f0a8631ffc9d363885f89478e9ad912)
-
There is lot of noise in dng. But Photoshop+Imegenomic Noiseware is much better than antinoise algorithm in ixus100
Are you able to open DNG from ixus 100 in photoshop? Does it 'just' work, or do you use some plugin for this?
-
No, unfortunatly i can't do it.
First i open dng in irfanview --> Save as tiff --> Open in PS (or open as camera raw in ps)
-
@Jestik: Thank you for your comparison.
You could test whether DNG has really more information (more bits) when you shoot in a bright spot with a dark area. When you lighten up that area (adjust contrast or something) there should be a slight difference.
-
The raw is only 12bit so I imagine the DNG has to be similar. :)
-
hm.. i always thought that RAW can be 12 or 14 bit. But, ok, it doesn't matter :)
i think in cameras with such small sensor RAW can't be panacea, but it something really helps when i need to correct shadows and highlight.
Anyway many thanks to HapoMa.
-
It can be all sorts but alas the sensor only gives 12 bit (vs 10 bit for earlier SDs)
Harpo
-
I have just noticed that all of my DNG photos have a black stripe, few-pixels wide on one side. Is it just my camera, or do you guys also get it? On jpg there is no stripe.
-
2 mstawick
on the left side of the picture? If so, then i have it
-
on the left side of the picture? If so, then i have it
Yes, exactly.
-
I have just noticed that all of my DNG photos have a black stripe, few-pixels wide on one side. Is it just my camera, or do you guys also get it? On jpg there is no stripe.
Yes, I have it also.
-
I have a 16 GB card and wanted to use 2 partitions (first - bootable 16 MB FAT16, second - main partition with the rest of the space and formatted FAT32). When I power up CHKD it doesn't detect the second partition at all (in "misc. stuff -> swap partitions" says the card has only one partition). Does this work already?
Additionally I tried "Make card bootable" and "Create card with 2 partitions" and both resulted in camera shutdown. But at least it didn't destroy any data. :)
-
@quikee
from the first post in this thread:
* Include multipartition/boot from SDHC support.
Progress: Ignored so far
hth,
wim
-
@quikee
from the first post in this thread:
* Include multipartition/boot from SDHC support.
Progress: Ignored so far
hth,
wim
I acutally looked there but missed it. At least I can now report that it does not work. :)
-
I'll include the black stripe as a bug to fix...
-
Just purchased 2 SD780-IS for stereo movie recording. I've successfully installed the pre-alpha. Oh boy, oh boy, oh boy. Keep up the great work HarpoMa and other contributors. I'll chime in again if I have something to contribute.
-
I hope there is continous development in the background, altough the forum is not updated recenlty.
Anyway, UP to this topic.
-
Still working - but slow due to life.
-
Still working - but slow due to life.
Thanks!
-
HarpoMa, thanks for all the hard work so far! I'm amazed at the skills of all you CHDK developers; wish I could program at that level. C on Unix is all I know.
Got some questions for the SD 780 pre-alpha build:
Does this work if you're loading onto an SDHC card as opposed to an SD card?
Is the procedure the same as when I put the CHDK software onto my SD 400, which was downloading the appropriate build based on certain firmware, then using "Card Tricks" to make the software auto-start when i turn on the camera.
Does this build have the video paramater "Video Mode" where you can set it to "Bitrate" mode and have the camera record video at constant "1 X", "2 X", "3 X" bitrate levels?
If the above question is yes, would this work with the SD 780, HD (H.264) video mode. That is, the ability to record HD video at constant (desired) bitrate?
Keep up the good work! Thanks!
-
SD or SDHD it matters not.
Don't know exactly the prodecure but if you make the card bootable in cardtricks and then copy the file to DISKBOOT.BIN it will boot when locked. If you name the PS.FI2 then select firmware upgrade it will work.
No bitrate per say but there is a quality setting that affects bitrate. Yes it works nicely with regards to the H.264 720p mode. You can't force a desired bitrate only quality.
Harpo
-
Harpoma,
I'm really excited to see how this develops. Please let the non-developer users know how we can help you in any way.
I have a 780is and am running the CHDK on a Mac. Mostly interested in using the CHDK hack for time lapse recording scripts (Ultra script) and stereoscopic filmmaking.
If we can run any testing or beta that would help your process let us know.
Thanks!
Paul Lundahl
creative director
eMotion studios
-
You can test and report based on last build.
-
Does anyone know how similar the SD780 code is to the SD940? The SD940 is a newer camera with an improved lens. The appearance and features seem similar. I'm hoping some of the porting effort going into the SD780 could carry over to the SD940.
-
Does anyone know how similar the SD780 code is to the SD940? The SD940 is a newer camera with an improved lens. The appearance and features seem similar. I'm hoping some of the porting effort going into the SD780 could carry over to the SD940.
Each camera needs it's own port. It can help to have a similar camera of the same generation to refer to, but the SD940 is probably closer to the sd980 (both use a newer version of DryOS)
-
I want to see if blinking works on my 1.00B SD780. Having trouble getting the packages required. HarpoMa, do you have them handy to be posted somewhere?
-
@wasabi1023
I'll post my blinker stuff (however it really depends on a lot). If I was to blink a camera again I would use the sound card osilloscope methods talked about elsewhere. This method is a lot more controllable and you can determine the timing required between bits a lot easier. I was extemely lucky with my blink to serial port.
Harpo
-
You really shouldn't have to blink to get a dump of a different firmware version of one that is already known. The differences are normally very minor, hacking up udumper or an existing CHDK loader to write a full dump should be quite a bit easier than blinking.
-
I'm a developer . I want to help you to port the chdk to Ixus 100 is if is possible ... i don't know exactly what i need to start to help your project ?! ... onother question ... i see that there're some tips to use chdk and rc reciver by usb to control the cam remotly is this features supported by your port now ?
Best Regards
Roberto
-
The autorun works well with the DISKBOOT.BIN file listed as an attachment to the first post, however when I compile this file myself using the zip of the source code that is also in the first post and put it on an SD card it doesn't boot CHDK on the camera. When I turn on the camera the screen just stays black and the lens doesn't extend. What am I doing wrong?
The funny thing is, my own compiled PS.FI2 file this loads with no problem on the camera.
I am using binutils < 2.19 and I have tried setting the execute flag on the file. This is all in a gcc cygwin environment.
Thanks.
-
You need to encode with the correct dancingbits version, which should be mentioned somewhere in this thread chdkess
-
Hi, in the zip file in the first post the define is set for dancing bits as USE_ENCODED_DISKBOOT=2 which is the correct version of dancing bits for the IXUS 100. When I compile it even says it is using the right version:
main.c -> main.o
-> main.elf
main.elf -> main.bin
<< Leaving loader/ixus100_sd780/resetcode
entry.S -> entry.o
main.c -> main.o
blobs.S -> blobs.o
-> main.elf
main.elf -> main.bin
<< Leaving loader/ixus100_sd780
<< Leaving loader
>> Entering to CHDK
-> LUALIB/GEN/propset1.lua
-> LUALIB/GEN/propset2.lua
<< Leaving CHDK
-> PS.FI2
Saving ./bin/PS.FI2
Done
dance -> DISKBOOT.BIN ver 2
**** Firmware creation completed successfully
As I say, the PS.FI2 works fine but the DISKBOOT.BIN which is compiled at the same time isn't. Something fishy is going on with the dancingbits encoding.
-
Maybe i'm completely wrong, but i would guess that the source code linked in the first post is older. It says V3 and the binaries are stated as V7.
As far as i remember the diskboot method was not working back in Version 3.
-
Hi Duke, thanks for your reply. That explains it. Harpoma do you need a hand in porting? If so I know C so can help out but I can't see the IXUS 100 code in trunk.
Chdkess
-
Just been disconnected. The best thing people can do is submit bug reports on the current binaries. So far it's been very bare. I base my work on bug reports. I don't feel confident to submit to svn until I have more bug fixes.
I will post the latest source so people can rebuild if desired.
Harpo
-
Just been disconnected. The best thing people can do is submit bug reports on the current binaries. So far it's been very bare. I base my work on bug reports. I don't feel confident to submit to svn until I have more bug fixes.
I will post the latest source so people can rebuild if desired.
CHDK is GPL*, so in general, if you release a binary, you should release the corresponding source. This will also help in the cases where people abandon a partly finished port.
I would not worry too much about having all the bugs fixed before it goes into SVN. It's easier to collaborate when everyone can see the current source. If there are major outstanding bugs, we can leave it out of the autobuild.
* Given the nature of the source, one could argue that this isn't valid, but l don't want to get into that here. It was clearly the intent of the original authors that their own original code be under the GPL.
-
I've read these comments of yours before on other posts. As for SVN thats more your call then mine as you can submit to SVN and I cannot. I won't argue the GPL because I agree the souce should be available I've just been lazy. If you would prefer I can delete the binary and rerelease once I have time.
Each version of the binary and souce is noted in post #1 btw. It is clear that the last binary is not from the last source. If this is unacceptable please say so and I will always make certain to keep them in sync. As I clean up the build it take more time then I like to spend doing a joint source / binary release.
Harpo
-
If this is unacceptable please say so and I will always make certain to keep them in sync.
I wouldn't worry to much about this. I sometimes post test builds without source for the same reason. OTOH, we have had a number of people abandon ports part way through, without posting their final source (and in some cases without posting any source at all), so I like to get people to post it as much as possible.
That said, if you set things up right, posting a source patch with each build shouldn't be much additional work. It's quite easy to generate a patch from your current working copy. Just svn add all the new source files (not the object files etc), and svn diff > patchfile. In tortoise you can right click "create patch". You can svn add even if you can't commit.
-
--removed as I misread the prior post....
-
Hi! :)
I've successfully gotten this CHDK running on a European Ixus 100IS (the Mac tips helped - you really have to do all of them, including deletion of extended attributes) ... looks nice!
Since this is my first CHDK try, I don't know what to test (is there something like a page with a 'Testsuite' that once can walk through to confirm everything works as expected?)
what I'm missing is the Zebra display - doesn't seem to be there.
The BASIC interpreter seems to be working, although the hdr-stack script (http://chdk.wikia.com/wiki/UBASIC/Scripts:_HDR_with_stacking (http://chdk.wikia.com/wiki/UBASIC/Scripts:_HDR_with_stacking)) I tried seems to have problems - it's taking quite a lot of pictures, and it doesn't seem to be able to change the exposure setting after changing it the first time ...
I trigger it using ALT-Shoot with the exposure menu on screen - I guess it would be required to turn of the '<ALT>' mode, but then the script stops running. Maybe I misunderstand something - or there is still a problem. This would be my main usecase for CHDK, though :) I don't know what else is possible and will probably only discover later ...
I can test etc., just let me know what I shall do :)
Please advise
count
-
Fab. I'll add those items to the list. I hope to be back to normal schedule this week and I'll be back here again.
Harpo
-
just get USB control.. and or a timer great work!!!! thanks!!!
-
I don't get the bit about the GPL compliance required? GPL requires you to provide the sourcecode & buildscripts - is that's what 0.7b is, and nothing else? Or does it give me anything else than 0.7? A quick changelog on updates would be nice :) I'm basically holding my breath ;)
-
In case you're interested, I think I've found the following addresses:
Mount_FileSystem 0xFF862020
Remount_FileSystem 0xFF862134
-
one more question: will it be possible to fix iso in the mobie mode?
-
@chdkess - thx I'll add them in.
@count - 0.7b is my latest build possible. As for change logs thats what post #1 is...
@jestik - I don't know what you mean really - If you expand on what is broke I'll fix it but understand that I cannot fix it if I don't know how to repeat it. If you also provide how to verify the fix that would be good too.
You will be happy to know that I'm back to this project now so you will actually see some more progress vs what has occured as of late. :)
Harpo
-
I think you will find the source files will not compile.
It first stops with errors caused by \platform\makefile_sub.inc :-
34: Extraneous text after 'else'
40: only one 'else' per conditional.
-
It compiles in my environment but that certainly does not imply it will build in any other. I build on a Vista box and if I recall Vista is not supported in the build tree. I have made changes to make inc that certainly are not likely to be supported in the build tree.
But because I certainly don't want to hang my hat on memory I will build it tonight and verify. I don't suggest anyone actually use my source but since I am required to release it I have.
Harpo
Edit: Yes I looked at the file that is complaining and it's all related to Vista build. So if you want to build this build then you will want to have enough C++ knowledge to fix it. Likely a simple replacement of the .inc file from the real tree will make it work. However as this is NOT a submission to SVN i don't plan to fix it. This is a release of my build source and not for the average person to use.
-
OK, I can get as far as compiling boot.c and then there are a couple of syntax errors.
At the bottom of the file are :-
LDR R1, [R5,#0x68] (not in quotes)
BLX R1 (not in quotes)
Are these meant to be commented-out ?
-
HarpoMa
hm.. sorry for my english.
I was meant to say not "fix iso" but "set iso".
when i'm shooting video there is a lot of noise in shadows, because, as i understand, the camera is trying to use auto iso --> high iso
will it be possible to set iso manualy for example to 100 or 200?
-
@jestik - I will look and see.
@Microfunguy - Give me a day or so and I'll put out a better copy of the source. I had forgotten I was mid-multi partition setup. I was unable to get a SD card to make 2 partitions so I couldn't finish it.
Harpo
-
This is a great model to work on since it is compact and has pretty good quality HD video recording. Enabling optical zoom during HD recording via CHDK would really make this a unique camera. Thanks for all the work on this.
-
Well, I have been able to port this to SDM with only minor issues.
The code for briefly overriding DISPLAY button when used as the ALT-exit button does not seem to work.
The functions 'kbd_get_autoclicked_key()' and 'kbd_get_held_key()' are identical.
I tried to compare with a compile of the CHDK-version source-code but get many errors about using hardware FP or using FPA instructions.
-
@HarpoMa
I build on a Vista box and if I recall Vista is not supported in the build tree
CHDK-Shell supports Vista and Windows 7 since version 2.22, released in August (current is version 2.47)
if you prefer a command line environment, i've also added the GCC 4.4.0 kit as a separate download
on my drop.io (= the same as currently included with full versions of CHDK-Shell)
http://drop.io/gcc_for_chdkshell/asset/gcc440env-forchdk-sfx-exe (http://drop.io/gcc_for_chdkshell/asset/gcc440env-forchdk-sfx-exe)
hth,
wim
-
2 sivalley
Hm..why you say "would"? it has this function with CHDK
-
2 sivalley
Hm..why you say "would"? it has this function with CHDK
I think it even has zoom during video mode without chdk. Maybe he means auto focus during video recording. But I think the lack of auto focus during video recording is a limitation in the hardware.
-
@whim
When I started to setup my build environment Vista wasn't supported. I haven't bothered to update since then.
Harpo
-
@Microfunguy
Can't comment on the FP / FPA thing don't know what it is.
As for the two functions being identical....hmmm seems a bit of a mystery to me but I'm sure it made sence at the time...
Harpo
-
I'm sure it made sence at the time...
I am saying that the CHDK binary works but my version using your published source-code does not :-
if (kbd_get_held_key() == KEY_PRINT) isHeldDisp=1;
if (isHeldDisp != 1)
{
if (kbd_process() == 0)
{
physw_status[0] = kbd_new_state[0];
physw_status[1] = kbd_new_state[1];
physw_status[2] = (physw_status[2] & (~KEYS_MASK2)) |
(kbd_new_state[2] & KEYS_MASK2);
physw_status[2] = physw_status[2] & ~SD_READONLY_FLAG;
}
else
{
// override keys
physw_status[0] = (kbd_new_state[0] & (~KEYS_MASK0)) |
(kbd_mod_state[0] & KEYS_MASK0);
physw_status[1] = (kbd_new_state[1] & (~KEYS_MASK1)) |
(kbd_mod_state[1] & KEYS_MASK1);
physw_status[2] = (physw_status[2] & (~KEYS_MASK2)) |
(kbd_mod_state[2] & KEYS_MASK2); //fix needed as below
physw_status[2] = physw_status[2] & ~SD_READONLY_FLAG;
}
}
else
{
isHeldDisp = 0;
*mmio2 = *mmio2 & ~(0x00000040);
}
etc
long kbd_get_held_key()
{
static long last_kbd_time = 0, press_count = 0;
register long key, t;
key=kbd_get_clicked_key();
if (key)
{
last_kbd_key = key;
press_count = 0;
last_kbd_time = get_tick_count();
return 0;
}
else
{
if (last_kbd_key && kbd_is_key_pressed(last_kbd_key))
{
t = get_tick_count();
if (t-last_kbd_time>((press_count)?175:500))
{
++press_count;
last_kbd_time = t;
return last_kbd_key;
}
else
{
return 0;
}
}
else
{
last_kbd_key = 0;
return 0;
}
}
}
Can you publish the code that you currently use ?
David
-
Not certain what doesn't work for you.
You have a current dump of my entire build environment (as of my work prior to yesterday). You mentioned you had to "fix" stuff maybe it broke during that process.
As I have said before it would be unwise to use my code in it's current state. If you insist on adding it to SDM right now you are likely going to waste a lot of time. Certainly that is your choice but you are on your own for any issues that arn't also in my build.
Harpo
-
I am simply asking you if the keyboard code to handle DISPLAY button is correct in the published source.
I have other things working, including edge-overlay and zebra.
You can see your code that I am using above
Is that what you use in the working build ?
-
You have the code from my latest build (minus support for partitions). The keyboard handling code hasn't change for quite some time. Explain... how are you using the DISP key? Explicit please and I'll try to assist.
harpo
-
We are only referring to the key code, it is a very localised issue.
The tester is using the DISP key to enter ALT mode (as it is an alias for the Print key).
When he tries to leave ALT mode by pressing the DISP key he has to be VERY fast or the normal Canon action will occur.
i.e. the screen will blank.
Your code attempts to avoid this problem.
The tester claims it does not work as expected.
Normally, I do not try to port until a version has been 'officially' released.
With the ixus100 I allowed myself to be persuaded to do it immediately.
It will not happen again.
-
Ahh I understand.... Please send me the kbd.c you are using (in full pls)
The heldDISP is actually for multitasking the DISP key as ALT & DISP. ALT is a single normal press and DISP is a long held press of DISP. ( I think you know this ) The key
{ 2, KEY_PRINT , 0x00000040 }, //doesn't exist
{ 2, KEY_DISPLAY , 0x00000040 }, //swapped for print atm
mapping works fine for the single press as listed in this order.
So the heldDISP is used to emulate a DISP key by allowing a long hold of DISP to mean DISP. So I think the mapping above has been swapped around as a first guess. But send the kbd.c in full and i'll look. It is not actually to avoid any problem as you describe but rather to add a "new" key as the sd100 has no print key. I'm noting that new cameras are having lesss and less keys.
Harpo
-
Thanks, I will do that now.
I want to get this camera off my back and spend December on other things !
David
-
I have sent file to your email address.
David
-
The code as sent to me is broke. This will not correctly handle the DISP long held correctly. The code that is commented out is exactly the code required to handle long DISP and to NOT process the short DISP as DISP. It would seem to me that what your tester is seeing is exactly what they should expect to see given this code snippet...
// if (isHeldDisp != 1)
// {
if (kbd_process() == 0)
{
physw_status[0] = kbd_new_state[0];
physw_status[1] = kbd_new_state[1];
physw_status[2] = (physw_status[2] & (~KEYS_MASK2)) |
(kbd_new_state[2] & KEYS_MASK2);
physw_status[2] = physw_status[2] & ~SD_READONLY_FLAG;
}
else
{
// override keys
physw_status[0] = (kbd_new_state[0] & (~KEYS_MASK0)) |
(kbd_mod_state[0] & KEYS_MASK0);
physw_status[1] = (kbd_new_state[1] & (~KEYS_MASK1)) |
(kbd_mod_state[1] & KEYS_MASK1);
physw_status[2] = (physw_status[2] & (~KEYS_MASK2)) |
(kbd_mod_state[2] & KEYS_MASK2); //fix needed as below
physw_status[2] = physw_status[2] & ~SD_READONLY_FLAG;
if (switch_override == 1)
{
physw_status[1] = (physw_status[1] & (~SWITCH_MASK1)) | (switch_mod_state[1] & SWITCH_MASK1); // set relevant bits to '0' then add new pattern
physw_status[2] = (physw_status[2] & (~SWITCH_MASK2)) | (switch_mod_state[2] & SWITCH_MASK2); // set relevant bits to '0' then add new pattern
}
}
/*
}
else
{
isHeldDisp = 0;
*mmio2 = *mmio2 & ~(0x00000040);
}
*/
-
No, that was not commented-out when I sent it to the tester.
I only did that later.
-
You seem to have made a copy of kbd_get_autoclicked_key with the intention of creating kbd_get_held_key.
-
Well I'm gonna go with the classic.... "It works for me it must be something you have changed." I am still thinking that the tester or builder has commented out some of the important code. As for the function that is the same I think I just didn't need to change anything. BUT I will rebuild my code tonight and verify 100% that I have no DISP/ALT issue.
Harpo
-
OK, thanks.
Maybe he is simply pressing the button for too long.
He did say that it only works if you press for a VERY short time.
As for the function that is the same I think I just didn't need to change anything.
Then why have two identical functions ?
David
-
Feel free to delete one. There isn't always a reason sometimes you just think you need it (intention as you say). When I release the code formally I'll probably delete it too. But as it uses a static variable I may choose to change the various variables to ensure use of one doesn't affect the other.
Harpo
-
I will enable the relevant code and ask him to check again.
I don't entirely understand kbd_get_held_key() , I will have to study it.
David
-
Did you alter the two time values that determine which mode the button is used for or are they 175 and 500 msec ?
Incidentally, I think tick_count only has a resolution of 10 msecs.
David
-
Yes my working code that I'm keeping from everyone has the correct timings. I'm hiding it from everyone to allow my build time to rule them all.......
But seriously you have the latest code (minus partition support). I still beleive there is a translation issue to SDM. BUT i will try it at home tonight to verify 100%.
-
Interesting problem that may be linked to the kbd_get_held_key code.
With SDM in ALT mode, a brief press of SET turns screen displays on/off.
A longer press turns edge-overlay on/off.
It also crashes the IXUS100 !
Of course, it may have nothing to do with that code.
-
Ok. I have compiled my compile here...
DISP (quick) turns on ALT mode. A press of SET then brings up Select script file... (as expected) A press of DISP (quick) then exits ALT mode.
DISP (hold) while in playback executes a normal DISP (canon level) repeats if I repeat
So I consider this a SDM integration issue and not a chdk issue. That said I don't expect my chdk build to currently follow the best standards or such. Maybe my code violates some rules and if it didn't it wouldn't break SDM. However at this point I can't debug SDM and continue my own CHDK work.
Sorry.
Harpo
-
So, did you verify this and did you define it ? :-
volatile long *mmio2 = (void*)0xE240; //VERIFY SD780 Used to override long held DISP
// Needs to be #DEFINE
-
Yes in my super secret keep from Microfunguy build I have defined and verified everything. I'm keeping for whim and reyalp all my really good stuff.
Lets just end this chain of questions and you can just ask yourself the questions and just assume that my answer will either be "it's not done, it works for me, or it's a SDM thing not a chdk thing". I don't want to be rude but I'm starting to find your questions rude and certainly bordering on accusatory. You have the code you can do as you wish with it but I am not responcible for your ability to code, port, ect.
Except for my super secret build of course.....that version has all the funguy stuff.
Harpo
-
Thanks for your 'interesting' reply Jason Harp.
-
Your welcome David.
-
Hi Jason, how's the development going ?
I've just played with some Lua, shutter speed and bracketing in continuous mode and everything is nice, but there are some strange things like: menu is disappearing randomly (mentioned), sometimes CHDK fails to load with last time configuration (I can send it to you if this will help you) and histogram is all messed up...
Is it possible to disable CHDK in AUTO mode, when you shoot in auto you don't really need CHDK, so i think, the best way of repairing it is to disable it...
I would really like to help, so i will try to find new bugs...
Good luck with BASIC, Lua and RAW (i need them most).
Thanks HarpoMa !!!
-
I've actually been doing stuff on it so I will look at your points of need. I put out a diff of the source yesterday but I'll put out a binary tonight.
If you can detail your issues with BASIC, Lua, and RAW it will give me a list to go off. RAW should work but maybe some small detail needs attention.
Anyways don't be afraid to list any and all issues and i'll just knock them down one-by-one....
Also post #1 always has the update to builds so feel free to reread it often.
Harpo
-
Great I will try the new version up !
At the weekend I will shoot some RAW, test some Scripts and search for bugs (e.g. What causes it not to boot up with my old configuration) and post them...
P.S. I have some ideas of using Image Stabilizer in video mode: We could make stereographic 15fps video, by shooting in 30fps but every frame shifting lenses right or left, I wonder if that shift would be enough. But that's for future development :)
Keep up the good work :)
Ignas
-
Hi Jason, how's the development going ?
I've just played with some Lua, shutter speed and bracketing in continuous mode and everything is nice, but there are some strange things like: menu is disappearing randomly (mentioned),
This is probably normal: http://chdk.kernreaktor.org/mantis/view.php?id=275 (http://chdk.kernreaktor.org/mantis/view.php?id=275)
and histogram is all messed up...
Messed up how ? If it displays wrong data, this usually means the live viewport address is wrong. In this case, zebra and edge overlay should also be wrong.
Is it possible to disable CHDK in AUTO mode, when you shoot in auto you don't really need CHDK, so i think, the best way of repairing it is to disable it...
Unless you turn on overrides or raw or something like that, CHDK should have no effect on normal shooting, in auto mode or any other mode. You can set exceptions for raw.
I would really like to help, so i will try to find new bugs...
Good luck with BASIC, Lua and RAW (i need them most).
Be sure you read the sticky threads in the raw forum (or earlier posts on the subject in this thread) before reporting problems with raw ;)
-
I thought it would be interesting to try to compile HarpoMan's ixus100 code.
I installed GrAnd's windows environment and TortoiseSVN.
I checked-out CHDK 853.
I successfully compiled CHDK for another camera.
I renamed HarpoMan's diff.txt file to 'ixus100.diff' and at root directory on the command-line typed :-
patch -p0 < ixus100.diff.
Error messages multiple times :-
"Reversed (or previously applied) patch detected! Assume -R? [n]
Pressed return
Apply anyway[n] yes"
Many other error messages 'hunks failed'and rejects saved.
Hunk#2 succeeded at 244 with fuzz.
No ixus100 subfolder created.
The build for other camera no longer works.
Has anyone else managed to patch this or know what I am doing wrong ?
-
Maybe I should just release a full source instead of the patch. Would that work best?
-
Yes, that would be great and make it far easier for me.
Thanks !
Werner
-
You patch is a mess. Please don't include binary files, or files irrelevant to the source.
You also appear to have a bunch of changes that are from the trunk, not your own changes. If you want to track the trunk (which you should), you need to update your working copy, resolve any conflicts, and make the diff against that.
If you are using windows, I highly suggest using tortoise.
-
I'm using eclipse but I obviously have not got the team/patch/diff tracking perfect. I'll just put out the source in non-diff and try again later on the diff.
Harpo
-
I would like to open a RAW file recorded with the ixus100 using irfanview - which RAW settings in irfanview need to be set so I can see a correct decoded image?
thanks
Werner
-
I would like to open a RAW file recorded with the ixus100 using irfanview - which RAW settings in irfanview need to be set so I can see a correct decoded image?
You cannot get a usable decoding of CHDK raw with irfanview. You can use it to check whether an image is there, but you aren't going to be able to do anything else with it. To open it, you need to use "open as", "raw file", and then input the correct dimenstion, and selected 12bpp packed. Bayer or grayscale doesn't matter, because irfanview assumes the wrong byte order and there is no option to change this. For further questions regarding CHDK raw, see the raw forum. This is not an ixus100 specific issue.
-
I was wondering if it were possible, in video recording mode, to drop the FPS to 24.
I know something similar to this has been mentioned earlier, and it was stated that the fps couldn't be changed to slow-motion (really fast fps) because of a hardware limitation, but I hope that dropping the FPS to arbitrary framerates would be possible. Though I would completely understand if it couldn't be done.
I really like that 'film look'
-
If anyone wants to try a pre-release version of SDM 1.82 for the IXUS100, you can get it here :-
http://www.zshare.net/download/697998660c918d04/ (http://www.zshare.net/download/697998660c918d04/)
Official release on Sunday.
Thanks to Jason Harp for porting to CHDK.
-
I was wondering if it were possible, in video recording mode, to drop the FPS to 24.
..
I really like that 'film look'
The impression i got reading the forum is that the CHDK can't change the FPS
-
Quick Note:
i have been using Picturenaut 3.0 to open my raw files and convert them to .tiff or .ppm Works quite well for what im using it for. its free so thats a plus
-
i have been using Picturenaut 3.0 to open my raw files
I tried picturnout as well but when trying to load a RAW file the program says 'Cannot decode file' Do I need to make some special settings to be able to load them?
Werner
-
i have been using Picturenaut 3.0 to open my raw files
I tried picturnout as well but when trying to load a RAW file the program says 'Cannot decode file' Do I need to make some special settings to be able to load them?
Werner
I dont do anything special. I have the RAW file extension set to be .DNG and it works just fine.
-
Raw Therapee can open dng files from our canon
-
Hello, i don't know is it only for me, but 1.8 version is more bugged than the last one:
Bracketing, shutter override doesn't work - all the 'Extra Photo Operations' tab doesn't work.
But overrall view is better, menu is not that jerky and boot from memory card is great (but i'm not using it, becouse sometimes I just need an AUTO mode)...
I believe the new version will be better:
If anyone wants to try a pre-release version of SDM 1.82 for the IXUS100...
Official release on Sunday.
So keep up the good work...
P.S. The most needed Set_focus doesn't work... Please, add those addresses.
-
I am not sure .. are your comments above for the CHDK release or the SDM 1.82 release on the website ?
-
It's about v8, I haven't tried the SDM 1.82 release yet... I will wait for official release.
-
Theres a review for the 780 on the Canon website that says he's running CHDK on his but I don't see that its ported yet on here. Am I missing it or is he lying?
-
@cole91
Could be one of the pre-alpha versions, check the 1st post in this thread http://chdk.setepontos.com/index.php/topic,3995.msg37547.html#msg37547 (http://chdk.setepontos.com/index.php/topic,3995.msg37547.html#msg37547)
Also, do you have a link ? there's many Canon sites & pages ...
cheers,
wim
PS ... and welcome to the forum !
-
@whim
Apparently I'm going crazy. On the canonusa.com page for the 780is just yesterday before I posted on here I was reading the reviews on it and the second review was a guy talking about how its a great camera if you put CHDK on it and how now he can shoot RAW and all this about CHDK, but just now when I went to get you the link, the review is gone. Unless, Canon isn't a big fan of you guys and CHDK? I'm supposing now that they saw that and deleted it because they don't want people finding out or something? It must be because I know it was there yesterday.
Thanks for the heads up though.
Cole
-
Funnily enough, i do think they're fans of CHDK - it will certainly not hurt their sales, will it ?
If they really hated CHDK, they would have tried to shut it down by now, IMHO
cheers,
wim
-
Funnily enough, i do think they're fans of CHDK - it will certainly not hurt their sales, will it ?
If they really hated CHDK, they would have tried to shut it down by now, IMHO
My guess is that canon as an entity doesn't have a coherent position, but I can see them not wanting it mentioned on their own site (which could be seen as endorsing it), even if they don't have a problem with CHDK existing.
Google finds quite a few mentions in the reviews http://www.google.com/#q=site:canon.com+chdk&hl=en&safe=off&filter=0 (http://www.google.com/#q=site:canon.com+chdk&hl=en&safe=off&filter=0) (note that canons links change, so google won't necessarily take you to the page the actual review was on)
-
That's very true. It probably coaxes a lot more tech savvy people into some of the point and shoots when they find out about CHDK and shooting RAW and what not. But yeah @reyalp makes a good point.
-
I feel rather silly asking this, but how do I go about getting all of this 'assembled' for my camera? I've got the files in the first post, but I don't know how I go about getting the CHDK directory on the camera. (my CHDK experience consists of installing it on a fully supported camera, and using it there) I've got the source for CHDK downloaded from SVN, and the patch, which I'm assuming I apply to the source, and then build like the instructions say? (patching stuff from SVN makes me nervous, as it could've changed since your version) Can I just grab a CHDK directory from the old camera and use these binaries instead? (I noticed there were no executables in the CHDK directory, and could quite possibly just be information and scripts) if not, I'm not really sure where to apply this patch...
Thanks for listening to my newb-ramble, it's a bit late and I probably missed something obvious. Got my arm cross-compiler set up though, just in case.
-
@boondaburrah
just grab a full version off the Autobuild server (any cam will do), put it on your card, and then
replace DISKBOOT.BIN & PS.FI2 with the ones from post #1
hth,
wim
-
@whim
I had a feeling it might be that simple, thanks. (and thanks to who ever made the design descision that makes it that simple)
-
-
This may be a result of the lua scripting being incomplete, but I can't get the badpixel.lua script to run. It always states that I need to be in record mode, even when I am, and then it turns alt mode off, and I can't get back into the CHDK menus without restarting the camera. (I'm trying to get DNG support working) I read on the main website that I could fool it by putting a dummy badpixel.bin file in the CHDK directory, but I don't know the structure of these files to make one, and just having the file won't do it. Would anybody happen to know how I could go about making one of these dummy files, I'm cool with editing out the bad pixels myself once I find them.
EDIT:
Nevermind, I just removed the part of the script that checked for record mode, and it ran fine. I don't know if the badpixel.bin is correct, but it lets me enable DNG raw mode now.
-
This means that playrec_mode (or whatever else is used to detect this state on this port) is incorrect.
-
First off I would like to thank the innovators, coders and porters who make all of this possible, especially you HarpoMa even though it seems as if you may have taken the holidays off from this project :) I am new to CHDK, but I would just like to report that I am having the same issues as ignasx with the 1.8 firmware. The extra photo operations seem to be completely non-functional. I only used the previous pre-alpha version for a short time, but it seemed to be more functional than 1.8 even though the menu system was definitely more glitchy. Since I am new to CHDK I just wanted to make sure that it isn't just me and that these issues are known. Thanks
Hello, i don't know is it only for me, but 1.8 version is more bugged than the last one:
Bracketing, shutter override doesn't work - all the 'Extra Photo Operations' tab doesn't work.
But overrall view is better, menu is not that jerky and boot from memory card is great (but i'm not using it, becouse sometimes I just need an AUTO mode)...
-
Does anyone have any input regarding the Remote Capabilities of this camera with this build? I'm trying to use USB but not much luck.. Thanks for all the work!!!!! :lol
-
I'm also having issues with reading the RAW files in Photoshop. I have no problems with my EOS. any hints would be great..
-
I also can not seem to get the Extra Photo Operations to work. And I can not get most of the OSD's to show..very few seem to work...
-
I take it all back I had the wrong build... still testing..:)
-
Somewhat off topic: Z-bars and USB push buttons are now availiable for the IXUS 100 IS (Europe) / PowerShot SD780 IS here:
http://www.digi-dat.de/produkte/index_eng.html#zbarcanon (http://www.digi-dat.de/produkte/index_eng.html#zbarcanon)
-
I'm trying to use USB but not much luck
It works with the version you can get here : http://stereo.jpn.org/eng/sdm/index.htm (http://stereo.jpn.org/eng/sdm/index.htm)
Just replace or rename your existing DISKBOOT.BIN.
-
This may be a result of the lua scripting being incomplete, but I can't get the badpixel.lua script to run. It always states that I need to be in record mode, even when I am, and then it turns alt mode off, and I can't get back into the CHDK menus without restarting the camera. (I'm trying to get DNG support working) I read on the main website that I could fool it by putting a dummy badpixel.bin file in the CHDK directory, but I don't know the structure of these files to make one, and just having the file won't do it. Would anybody happen to know how I could go about making one of these dummy files, I'm cool with editing out the bad pixels myself once I find them.
EDIT:
Nevermind, I just removed the part of the script that checked for record mode, and it ran fine. I don't know if the badpixel.bin is correct, but it lets me enable DNG raw mode now.
How much did you delete from the script? is it possible to upload the edited one for us others who have the same problem?
-
How much did you delete from the script? is it possible to upload the edited one for us others who have the same problem?
I deleted this part:
repeat
if get_mode() == false then
cls()
print("Run in Record Mode!")
sleep(3000)
cls()
exit_alt()
sleep(1000)
end
until get_mode() == true
cls()
This of course causes the camera to not check if it's in recording mode before it tries to take some shots to get the badpixel data, so make sure you're in record mode before you run it! I don't know what happens if you don't! Also, when you run the script, it doesn't actually save the badpixel.bin file until you press "FUNC/SET" at the end. I didn't get this at first because the camera overwrites the screen at the end and the output disappears before I can read it. If you think it worked, then go ahead and press "FUNC/SET" and then check if the file was created.
As a side note, my camera only seems to save RAW some of the time. I can always tell, too, because the camera doesn't "think" for nearly long enough to save the DNG. I'm not sure what happens here. I also can't seem to get the shutter speed overrides to work, but I think this might be user error on my part. Same with video quality, it always seems to ignore the value. This could be a new bug, but I'm not sure
Side note on RAW:
On mac, I can get DNGs to open in preview, but they all look blue (as if the blue channel was set to 100%) I can pass them through dcraw though, and everything's fine and looking as it should (except that line of black pixels, but that doesn't bother me)
As always though, great work HarpoMa, my camera is already much more functional then when I got it.
-
What can I do to help? I'm a software engineer with a brand new SD780 that I'm itching to send up a kite. If someone could point me to the basics (compiler for PC, source files, how to load/test, etc.) I will contribute all I can. Thanks.
-
@WhoDat
This link should get you started http://chdk.wikia.com/wiki/For_Developers (http://chdk.wikia.com/wiki/For_Developers)
hth,
wim
[edit: @fe50: gotcha this time :D]
-
Hello & welcome, WhoDat !
If someone could point me to the basics (compiler for PC, source files, how to load/test, etc.) I will contribute all I can.
You'll find all informations here: http://chdk.wikia.com/wiki/For_Developers; with MS Windows, you can use whim's CHDK-Shell (http://chdk.wikia.com/wiki/Chdkshell) (dl the sources, edit, patch/diff, compile).
*Edit: LOL - 8 seconds too late :D
-
Wow, great job on this port!
The Applescript method works, I just tested it out in the video mode and I can use the optical zoom. Yay! Time to download some scripts and play around...
Thanks to everyone who's worked on this!
-
Is anyone else having trouble with 'bracketing in continuous mode'? I'm trying to take consecutive pictures with different exp settings but when I enable bracketing at 1EV steps with +/- type and try to take the pictures in continuous mode, they all come out with the same exposure. I have tried both manually in continuous mode and using custom timer but both ways I get multiple identical pictures with no changes in exposure.. any idea what I might be doing wrong? or is there maybe some other trick I need to use or option I need to enable to get this to work properly? Thanks again, great work with the port!
-
Hello & welcome, jmy88 !
I have tried both manually in continuous mode and using custom timer but both ways I get multiple identical pictures with no changes in exposure..
You should see
BRACKET: +/-
TV: 1EV
on your OSD - do you ?
-
Hello fe50, thanks for your response
I do not see those.. at which point should they appear?
All I do is go into Extra Photo Operations and turn on exposure bracketing in continuous mode at 1EV type +/- then turn my camera on continous shot and hold down the shutter to take numerous photos (at this point there is a yellow number that counts up in the top right corner, but no text like you mentioned appears).. but when I look at my photos afterwards they all have the same exposure setting as if bracketing is still not on. Any ideas?
-
I do not see those.. at which point should they appear?
...it should appear when you switch the camera to continuous or timer mode.
"Counter" in the top right corner:
With the default configuration the time (clock) is visible in the top right, after half-pressing the shutter the OSD shows the seconds...
(CHDK menu: [OSD parameters] - [Clock] - [@shutter half-press show]: Seconds )
-
Im having the exact same problem, I dont see any of that on my OSD when in normal mode, half press, or full press. I have played with several scripts also trying to get any sort of bracketing but no luck. Except manually changing the exposure. But that is taking too long and i am getting too much movement of subjects in between exposures. If i have to wait till a full or beta version thats no problem.
Thanks everyone for all your hard work
-
Hmm it does not come up when I switch to continuous or timer mode.. is there anything you can think of that I may be doing wrong or any other setting that may be interfering with it and preventing the bracketing feature from working?
-
I do not see those.. at which point should they appear?
Maybe the osd functions are not enabled by default. You can enable each osd functions somewhere in the menu.
BTW around when could this built goes to automake server?
-
Thanks! I have the pre-alpha code running on my camera. I notice post #1 says the USB stuff is incomplete. I'd like to experiment with this, esp. remote shutter triggering, as well as trying some scripts (intervalometer of course). How do I make my own versions of diskboot.bin and ps.if2 to test out my changes? Do you have any testing requests I can do in exchange?
-
Ok I've been testing 1.82 for some time now..
I have a lot of problems getting the camera to start and shutdown properly.
I can run scripts. At least the ultra Intervalometer seems to run.
I can get the histogram on my Screen but no other OSD's
I can not read the RAW files it is creating. I have no problems reading RAW files from my EOS..
with video I can use my zoom and it seems to work..
My camera shuts down often just goes black.
I've been playing with the usb control.. My guess is It just uses a simple switch and I'm trying to use a real canon camera switch and that wont work.
I've had no luck with Bracketing at all.
Shutter override seems to work.
is there a working file without the Stereo stuff ?
Thanks to all the great work!!!
-
is there a working file without the Stereo stuff ?
I assume that you are not saying these problems exist with the SDM version referred to ?
USB switch, edge outline, histograms, bracketing, zebra, etc all work.
-
Hi people,
I've been doing some tests with pre-alpha v8 chdk and 1.82 SDM versions
pre-alpha v8:
- I can't make the histogram works. Even I checked it to be displayed, it doesn't appear.
- I tried to override the shutter speed but it doesn't work.
- Sometimes, "alt icon" in the display appears like a white square, the word "alt" can't be read.
- As other testers have already said. Whole or a part of the menu sometimes dissapears..
SDM 1.82:
More or less I've the same problems that @srunyon1 have detected.
- It's really complicated to shutdown the camera. Sometimes goes black, but it doesn't shutdown. If you push on/off botton again, sometimes the camera shutdowns, and sometimes it turns on again.
- If I turn on the camera in AUTO mode, I can't switch it to manual or video mode. If I start the camera in P or in video mode, it switchs from one mode to others without problems.
- If I use the zoom in video mode, once I pass from optical to digital zoom I can't get back to optical zoom control. The zoom stucks in the limit from digital to optical and I can't get back to zero zoom.
- Finally. I cant make the play mode works. After take a picture, I cant watch it on the display. Pushing the play button makes the camera goes black.
One more question. It is not possible to override the aperture in this camera? or it hasn't been ported yet?
Hope my tests be useful for you.
Thank you for the excellent work you're developping!!!
-
It is not possible to override the aperture in this camera? or it hasn't been ported yet?
Can't override aperture on any ixus camera - they don't have an adjustable aperture, just a N(eutral)D(ensity) filter.
hth,
wim
-
SDM 1.82:
More or less I've the same problems that @srunyon1 have detected.
That version has been tested by a number of people before being released.
I can you list some problems that can be consistently reproduced and I will ask others to try them ?
-
Hi people,
I've been doing some tests with pre-alpha v8 chdk and 1.82 SDM versions
SDM 1.82:
More or less I've the same problems that @srunyon1 have detected.
Have you read the message on the SDM download page:
NOTE:The IXUS100, IXUS980 and SX200IS do not use the standard CFG file, they use a file with a numeric value after 'CFG'.
These must be copied to the card manually and should not be renamed. Use the files supplied in the CONFIGS folder.
I have no problems with my IXUS100
Frans
-
Ok I've been testing 1.82 for some time now..
I can not read the RAW files it is creating. I have no problems reading RAW files from my EOS..
http://chdk.setepontos.com/index.php/topic,1532.0.html (http://chdk.setepontos.com/index.php/topic,1532.0.html)
I've been playing with the usb control.. My guess is It just uses a simple switch and I'm trying to use a real canon camera switch and that wont work.
That's right, real Canon remotes don't work. You will need a simple homemade USB switch.
is there a working file without the Stereo stuff ?
No, just the pre-alpha version. HarpoMa posted his last message weeks ago, no idea if he is still working on a stable release.
Frans
-
Thank you fvdk. That was the point, I didn't read the message from sdm's forum. It's my fault, I had only followed the instructions given in chdk's forum about replace diskboot.bin. After copy the new configuration file, everything looks much better. If I find any bugs I'll report them as soon as possible. Thank you again.
-
Thank you fvdk.
I might add that Frans sells (very cheaply) a very neat, tiny USB switch :-
http://chdk.setepontos.com/index.php/topic,3631.msg33855.html#msg33855 (http://chdk.setepontos.com/index.php/topic,3631.msg33855.html#msg33855)
I use it all the time.
David
-
Hello fe50, thanks for your response
I do not see those.. at which point should they appear?
All I do is go into Extra Photo Operations and turn on exposure bracketing in continuous mode at 1EV type +/- then turn my camera on continous shot and hold down the shutter to take numerous photos (at this point there is a yellow number that counts up in the top right corner, but no text like you mentioned appears).. but when I look at my photos afterwards they all have the same exposure setting as if bracketing is still not on. Any ideas?
..is anyone aware of any possible fixes or reasons this bracketing may not be working? I had originally thought this may just be a problem everyone is having with this pre-alpha chdk but according to the first post and others here it appears that bracketing in continous mode actually does work for others both manually and with self-timer.. anyone have any insight as to how I may be able to get mine working?
Thanks again :D
-
Can anyone please give me a hint on how to build the prealpha v8?
I tried to apply the patch for trunk867 CHDK (had to merge sources manually and to fix dozens of problems). I failed to build the prealphav8 version (actually, I failed to link).
I also tried to apply patch for trunk799 (except for these files: core/gui_draw.h - revision 810, platform/generic/shooting.c - revision 804) [i took versions from the diff.txt file]. This time I failed to link the project.. again :(
Here is the linking problem:
-> main.elf
main.o: In function `core_spytask':
main.c:(.text+0xe0): undefined reference to `hook_raw_save_complete'
gui_draw.o: In function `draw_init':
gui_draw.c:(.text+0x9ee): undefined reference to `vid_get_bitmap_screen_width'
... (dozens of other errors)
Should I know these values to build? (I did not find them in diff.txt):
MEMBASEADDR
RESTARTSTART
MEMISOSTART
ROMBASEADDR
I had to add these dummy files to make the Makefile(s) happy:
platform/isux100_sd780/sub/Makefile
platform/isux100_sd780/sub/100a/Makefile
platform/isux100_sd780/sub/100a/makefile.inc
(please don't mind about "100a" -- I have "100c" :) )
What should I do to compile the project?..
Maybe it's time to commit into SVN?
Maybe it's better to give the zipped sources archive version instead of one diff file only?
-
I managed to compile the original source files, after some effort.
After successfully porting to SDM I deleted all of those files.
If you want, we can try going through the compilation process again and I can probably remember how to fix most things.
The first errors were in boot.c.
If you do try this, just post the first compiler errors that you get and we can work through them one-by-one.
-
[/quote]
Have you read the message on the SDM download page:
NOTE:The IXUS100, IXUS980 and SX200IS do not use the standard CFG file, they use a file with a numeric value after 'CFG'.
These must be copied to the card manually and should not be renamed. Use the files supplied in the CONFIGS folder.
I have no problems with my IXUS100
Frans
[/quote]
I copied CHDK.CFG5 L, LH, and R versions to the SDMINSTE.EXE folder, then used the SDM installer to write CHDK.CFG5 to the SD card (left camera), and had the same problems as srunyon1 and dlparis. A manual copy of the CFG5 file from the ixus_100\R folder seems to have solved the problem.
-
The SDM installer only knows about the normal CFG files, it does not know about these new ones.
Hence the need to manually copy them.
-
NOTE:The IXUS100, IXUS980 and SX200IS do not use the standard CFG file, they use a file with a numeric value after 'CFG'.
These must be copied to the card manually and should not be renamed. Use the files supplied in the CONFIGS folder.
I don't see how this would be true of the SX200, since it uses the same conf.c as the trunk with no special ifdefs that I can see ? I know for a fact it isn't true of the ixus 980, since I did that port. Perhaps you mean the SD980 (ixus200) ?
In any case, this is a terrible idea, and if some ports work this way it is wrong and they should be fixed.
Also, dryos cams have some issues with long file names, so even if they were to use different CFG file names (which they shouldn't) they shouldn't use this particular pattern.
-
I don't see how this would be true of the SX200, since it uses the same conf.c as the trunk with no special ifdefs that I can see ?
@reyalp,
you are correct, the sx200 uses the "standard" file name ( CCHDK.CFG )
Well it does on mine anyway (trunk 866).
OldGit
-
Do not get confused, fvdk is not referring to the 'official' CHDK version.
-
Kind of stupid question.
How to start CHDK on SD780 Camera?
I tried SD1100, did some programming, all works, want to experiment with SD780 now.
For SD110 I used Cardtricks and it all worked
SD780?
-
want to experiment with SD780 now.
Temporarily rename your existing DISKBOOT.BIN file and replace with IXUS100 version.
David
-
I placed DISKBOOT_prealpha_v8.bin and PS_prealpha_v8.FI2 onto SD card (4Gb)
CHDK starts, operates erraticaly, placed remote control script in SCRIPTS sub remots control script starts but does not work (same script works on SD1100)
What do I do wrong?
-
@Andrey
What do I do wrong?
You failed to read the 1st post properly
* BASIC scripting.
Progress: Ignored so far
* Lua scripting.
Progress: Some works default - Ignored so far
Running (pre)alpha versions of ports means you'll often see crashes and non-working features ...
If you want to do so anyway, please read the entire porting thread
HTH,
wim
-
What do I do wrong?
If you wish, you can try the version that you can get here : http://stereo.jpn.org/eng/sdm/index.htm (http://stereo.jpn.org/eng/sdm/index.htm)
-
What do I do wrong?
If you wish, you can try the version that you can get here : http://stereo.jpn.org/eng/sdm/index.htm (http://stereo.jpn.org/eng/sdm/index.htm)
Ok, http://stereo.jpn.org/eng/sdm/download.htm (http://stereo.jpn.org/eng/sdm/download.htm)
Followed instructions, installed SDM 1.82, copied into one folder (Common Files folder) files from .ZIP files Common Files.zip and 1.82-148-ixus100-100c-57.zip
Started sdminste.exe
Selected camera as right
Formatted card
Did NOT replace CFG file this time.
The trigger does not function as it did on SD1100: I press the button, it focuses ans shoots.
Here I press the button and camera focuses then LCD goes dark. To shoot I need to press second time.
Can I change something in settings to shoot from single press of the trigger?
-
Did NOT replace CFG file this time.
To use the SDM version, you HAVE to replace the CFG file, read the instructions on the SDM site.
Frans
-
There are three diffent modes.
Two are for synchronising a pair of cameras so that is not of interest to you.
In menu Bracketing/Overrides, set focus-mode to Manual.
It should now say FAST at the top of the screen.
As soon as you press the switch a photo will be taken.
If you use scripts, include the command 'sync-off' as your first command.
That means the script will not wait for you to release the switch.
-
This is awesome!
In menu Bracketing/Overrides, set focus-mode to Manual.
It should now say FAST at the top of the screen.
As soon as you press the switch a photo will be taken.
If you use scripts, include the command 'sync-off' as your first command.
That means the script will not wait for you to release the switch.
Thank you, I will try and let you know.
Is there a list of commands I can use for writing scripts?
To Frans
>> To use the SDM version, you HAVE to replace the CFG file, read the instructions on the SDM site.
To your experience, what difference will it make?
Right now it works with default .CFG file. And I think the screen is cleaner then when I changed to .CFG5.
Could that be? Not sure, just getting used of the environment etc.
You comments guys are greatly apprecialted. Hoping to evolve to the state when I can contribute something useful myself.
-
Is there a list of commands I can use for writing scripts?
Sure http://stereo.jpn.org/eng/sdm/ubasic.htm (http://stereo.jpn.org/eng/sdm/ubasic.htm)
Also read about the time-lapse bracketing function :-
http://stereo.jpn.org/eng/sdm/tlapse.htm (http://stereo.jpn.org/eng/sdm/tlapse.htm)
http://stereo.jpn.org/eng/sdm/tlapse2.htm (http://stereo.jpn.org/eng/sdm/tlapse2.htm)
and when you have time read the rest of the documentation.
-
I think the screen is cleaner then when I changed to .CFG5.
Could that be?
Actually, yes .. I do not like the CFG5 screen layout either.
However, use CFG5 and in menu Advanced\OSD Parameters\Layout editor you can change the position of all the screen elements.
-
This is awesome!
To your experience, what difference will it make?
Right now it works with default .CFG file. And I think the screen is cleaner then when I changed to .CFG5.
Could that be? Not sure, just getting used of the environment etc.
I have no idea what the actual differences are, maybe David can explain.
However, with the standard chdk config you might find some unusual behavior like the camera not starting/shutting down normally. I assume the special cfg is there for a reason :D
Frans
-
I have no idea what the actual differences are, maybe David can explain.
It allows the CFG editor to work correctly with the different colour palettes that cameras have.
Not an ideal solution, it will change one day.
David
-
Some good news, some bad news:
Good news: I got script with remote control to run!!
Bad news: with SDM software installed I can not upload images to PC! Any advice what to do?
Note regarding configuration files: I got CHDK.CFG5 file installed on the card automatically ... not clear how but i see it there in directory CHDK. There are two filesnow: CHDK.CFG and CHDK.CFG5. And I definitely did not place second configuration file there manually! ?
-
Bad news: with SDM software installed I can not upload images to PC! Any advice what to do?
Note regarding configuration files: I got CHDK.CFG5 file installed on the card automatically ... not clear how but i see it there in directory CHDK. There are two filesnow: CHDK.CFG and CHDK.CFG5. And I definitely did not place second configuration file there manually! ?
In Advanced menu -> Serial Comms -> Disable USD Download
The CHDK.CFG5 is probably saved by the camera.
-
Is there any chance that an intervalometer script would work with this alpha? I'm guessing that the answer is not but...
-
In Advanced menu -> Serial Comms -> Disable USD Download
That worked, thank you! Only the camera hangs after the transfer ... need to work further with it
-
I just bought this camera and would like to help get CHDK working with it. Could anyone explain where we are at the moment? Is there anything I could do as someone with very limited coding skills?
Cheers!
-
I just bought this camera and would like to help get CHDK working with it. Could anyone explain where we are at the moment? Is there anything I could do as someone with very limited coding skills?
Cheers!
As far as I know, the latest pre-alpha binary is in the first post, but HarpoMa seems to stopped developing it further.
I think the ultimate goal would be to include this version into the automake server, and having frequent CHDK release from it.
But my coding skills are also very limited, so it would be very nice that someone with better skills could take care on the prealpha source and make it into the "normal" tree. Hopefully it will happen some time.
-
Is it possible to autofocus while filming in video mode?and limit while balancing?
Video 720p: (http://www.youtube.com/watch?v=5zG_y-rhqGA&fmt=22)
-
USB remote Cable is clever idea however the need to use external power source (batteries) to trigger USB detection somewhat complicates construction of such cable. For users of SD780 (or any cameras with HDMI connectors in it) source of power can be taken from the camera itself, hence no need to use batteries.
In HDMI connector Pin 17 is negative, Pin 18 is +5V. Use these pins instead of battery terminals.
(I tried to insert schematic and images of physical implementation but did not find how to do it if images are on my harddrive. I will be happy to add it if someone tell me how.)
-
Using SDM with Eye-Fi:
How can I make SDM work with Eye-Fi?
Eye-Fi is SD card with embedded Wi-Fi: www.eyefi.co.jp (http://www.eyefi.co.jp)
This card works with SD780 without SDM, but I can not make SDM working with this card because there is no physical lock on the card, hence SDM does not boot.
-
I can not make SDM working with this card because there is no physical lock on the card, hence SDM does not boot.
Since SDM only support the autostart loading mechanism (with diskboot.bin), the only way is to do a "hardware mod", i.e. to cut a notch on the correct position...
-> http://chdk.setepontos.com/index.php/topic,1340.msg24023.html#msg24023 (http://chdk.setepontos.com/index.php/topic,1340.msg24023.html#msg24023)
-
Trying to find command to set DIGITAL Zoom. Is there any? Specifically for SD780.
Thank you.
-
Since SDM only support the autostart loading mechanism (with diskboot.bin), the only way is to do a "hardware mod", i.e. to cut a notch on the correct position...
-> http://chdk.setepontos.com/index.php/topic,1340.msg24023.html#msg24023 (http://chdk.setepontos.com/index.php/topic,1340.msg24023.html#msg24023)
Thank you fe50. I will cut a slot, let you know what happens.
-
Trying to find command to set DIGITAL Zoom. Is there any?
No.
I do not think that CHDK has a command for digital zoom either.
If you find that it does, let me know.
David
-
Post removed
-
Hello, I cannot get CHDK to work on my SD card.
I run Ubuntu - and I followed Andrew Hazelden's instructions from this blogpost:
http://www.andrewhazelden.com/2010/01/loading-chdk-on-canon-powershot-sd780.html (http://www.andrewhazelden.com/2010/01/loading-chdk-on-canon-powershot-sd780.html)
Upom making the card bootable, renaming the files, and turning it to 'LOCK' position, when I insert the card into the IXUS 100IS I get a single message: 'Card locked!'
I cannot take any photos while this message displays, and if I unlock the card and restart the camera then it operates with the usual Canon firmware.
-
Hello & welcome, yegga !
when I insert the card into the IXUS 100IS I get a single message: 'Card locked!'
Then CHDK is not loaded...maybe
- the card is not FAT12 or FAT16 formatted (FAT32 won't work with the automatic start mechanism)
- the card is not CHDK-bootable ("BOOTDISK" at offset 040h)
- the file "diskboot.bin" is not placed in the card's root or the file is not named correctly
- you're using a card with a size of > 4GB; in this case the card must be partitioned...
You should also be able to load CHDK manually - just copy the PS.FI2 file to the card, start the camera in playback mode (with unlocked card), enter the Canon menu & select "Firmware update"...this should work on all cards/filesystems.
-
Eye-Fi Card with SDM:
I installed SDM, cut slot in the Card - it works OK.
Had to modify card reader to write to modified card.
-
I'm a bit depressed because I can't join in the fun with my 1.00B camera :( Tested the available ps.fi2 and diskboot.bin files, but the camera just won't work (no lights when turned on, goes dead on manual firmware update, needs battery removed to reset).
At this point, if I managed to get a hardware-based firmware dump, would it be difficult to create a 1.00B CHDK version? If someone could provide instructions for doing the hardware-based dump, I wouldn't be able to do it myself, but I probably have friends who can.
-
You can try the g11 udumper to dump the firmware: http://chdk.setepontos.com/index.php/topic,4647.msg46175.html#msg46175 (http://chdk.setepontos.com/index.php/topic,4647.msg46175.html#msg46175)
-
Unfortunately, no joy on the g11 udumper. Same response as the old udumper (no light, nothing in empty.dum).
-
Oh yes, the SD780IS needs another diskboot.bin encoding as the g11. I encoded now the diskboot.bin with dancingbits option 2, so the sd780is should at least boot this file. So please try again with the attached file, maybe we have more luck this time. ;)
-
Hi. I'm a real newbie, please bear with me. I finally got CHDK to work with my SD780. I had to search around before finding that running badpixel at least once enabled dng saving, now get some beautiful RAW's on this camera. GIMP works good with GraphicConverter on the Mac to see and adjust files. Can't seem to get Adobe CS4 to see the pictures unless I first save them as Tiff's. I've been trying to bracket shots, and with badpixel running, can get two sets of shots with different TV settings, but with badpixel the camera always takes two shots. What I get is two sets of three pictures, each set of three having a different setting. I've read that with continuous mode and bracketting you should be able to set, say, three shots, and have it bracket values, but can't seem to make it work yet. Is there a default lua script just to fire the camera? Might seem like a silly question, but lua scripts seem to work better than uBasic, can't get them to work at all, and yes, I have read through the post, I realize that little has been looked at there. I think if I had a lua script that fired the camera with a wait, to prevent movement, it would then go to the custom timer and do it's thing, then would bracket three shots. I'm not sure if that makes much sense, just a thought I had.
I find the menus to be very stable for the most part, found that I get really stable menu in review mode, or with a very short press to the power button, which also gives review mode, and if I change things there, it saves changes for the next time I fire up all the way, helped when I tried a script that put me into an endless loop.
Please let me say, to everyone working on this, AWESOME! Just the ability of getting RAW on this little camera is a great improvement to me. I appreciate the work you are all doing!
-
SDM:
Can I edit SDM installation? I would like to change in itial appearance and adjust the settings when SDM is booted. (Not by adjusting settings using the script as i do it now. )
Also, did anybody work with Dave Mitchell's Configuration Editor? This is great idea but I could not make it work.
-
Can I edit SDM installation? I would like to change in itial appearance and adjust the settings when SDM is booted.
What settings do you mean ?
You can change positions with the layout editor and there are menu options to turn the header and splashscreen off.
did anybody work with Dave Mitchell's Configuration Editor? This is great idea but I could not make it work.
It works fine.
Did you read the following (in bold letters in the download instructions) ? :-
NOTE:The IXUS100, IXUS980 and SX200IS do not use the standard CFG file, they use a file with a numeric value after 'CFG'.
These must be copied to the card manually and should not be renamed. Use the files supplied in the CONFIGS folder.
Alternatively, do not use the supplied CFG file and rename or delete any existing CHDK.CFG (not CCHDK.CFG) file.
-
Oh yes, the SD780IS needs another diskboot.bin encoding as the g11. I encoded now the diskboot.bin with dancingbits option 2, so the sd780is should at least boot this file. So please try again with the attached file, maybe we have more luck this time. ;)
Sadly, although the AF lamp and flash indicator light turn on now, there is still nothing written into empty.dum... But this is the first time I've seen the camera actually react to any of the files I've tried so far. The 1.00B camera is proving quite frustrating.
-
Damned... If both LEDs show up, that means that the dumper found the BOOTDISK signature and also a function pointer that could be possible the WriteSDCard function. I compared the functions of the SD780 1.0C dump with the G11 functions, and there are almost the same. I am wondering that it is not working... :blink:
Do you checked the empty.dum file with the Cardtricks "string" function or by viewing with a hexeditor? I am asking, because the dump will start somewhere in the middle of the empty.dum file, and not from byte 0. So it is possible to overlook the dump if you take only a quick view with the hexeditor on the first KBs.
-
Do you checked the empty.dum file with the Cardtricks "string" function or by viewing with a hexeditor? I am asking, because the dump will start somewhere in the middle of the empty.dum file, and not from byte 0. So it is possible to overlook the dump if you take only a quick view with the hexeditor on the first KBs.
Also remember udumper doesn't know anything about the filesystem at all. If the card wasn't freshly formatted with empty.dum as one of the first files created, the dump might not be inside the file at all. If you are on a *nix system, you can just dd the sectors that udumper would write to.
ISTR some cameras have needed more or less of the RAM zeroed for WriteSDCard to work.
-
SD780 - access to physical buttons and swithces
Is there a list of names for physical buttons and switches for SD780?
1. I need to create certain functionality when some buttons are pressed
(and specifically, I need to add power down when 'Power' button is pressed. For whatever reason my power down button does not work when camera operates in ALT mode)
2. I need to block the buttons I do not use, meaning pressing these buttons results in n o action.
-
SD780 - cleaning the display
How to clean the display entirely from over-writes.
I use cls command and it cleans everything but 'x2' at the top of the LCD for digital zoom and ALT at the bottom. Also there is focusing rectangle. I want them all OFF!
Is it any way to do it?
-
SD780 - digital zoom. Reply to Microfunguy
I have indication that digital zoom can be set in ... DISKBOOT.BIN file?
When I use my SDM SD card it sets digital zoom to x2. (It does it every time on start up. I guess I set it manually at some point and it became written to the card)
If I start camera without the card digital zoom is set to x1 - no magnification.
Unfortunately i do not know what to write to set digital zoom. Any suggestions?
-
Deleted
-
Hey, great work! Keep going!
I managed to run "Pre-Alpha Firmware (v8 updated Dec. 3, 2009)" on mine. Functionality seems to be as described.
Things I (also) noticed:
- menu disappears in shooting-mode when AI-Focus engages
- RAW files cannot be read (tried with Camera RAW, irfan-view, just read the CHDK & RAW thread, will try this)
- when I try to enable DNG it tells me that badpixel.bin is missing
(badpixel.lua does not seem to work, only says "Run in record mode" ... which I did. Any ideas?!
fixed by uncommenting the loop that checks for record mode, see post on page 19 by Boondaburrah)
- histogram doesn't work when set to "Always" (when set to "Shoot" it works, but seems to hang after a while)
- in display-mode, the "alt icon" appears as a white rectangle (maybe identical text-colour?!)
Will be happy to do more specific testing if required.
Again, great work guys!
-
I have indication that digital zoom can be set in ... DISKBOOT.BIN file?
What do you mean ?
When I use my SDM SD card it sets digital zoom to x2. (It does it every time on start up. I guess I set it manually at some point and it became written to the card)
There is no function that sets digital zoom.
What happens if you delete or temporarily rename the CFG file ?
-
Hey, great work! Keep going!
I managed to run "Pre-Alpha Firmware (v8 updated Dec. 3, 2009)" on mine. Functionality seems to be as described.
Things I (also) noticed:
- menu disappears in shooting-mode when AI-Focus engages
- RAW files cannot be read (tried with Camera RAW, irfan-view, just read the CHDK & RAW thread, will try this)
- when I try to enable DNG it tells me that badpixel.bin is missing
(badpixel.lua does not seem to work, only says "Run in record mode" ... which I did. Any ideas?!)
- histogram doesn't work when set to "Always" (when set to "Shoot" it works, but seems to hang after a while)
- in display-mode, the "alt icon" appears as a white rectangle (maybe identical text-colour?!)
Will be happy to do more specific testing if required.
Again, great work guys!
See the post on page 19 of this forum, by Boondaburrah, once you remove the piece he mentions in a text editor and reload to your camera, then you can run it with alt, just make sure to read the message it gives you after, I didn't and it took me a few trues before I saw that you have to press SET after. Gives some great RAW files. I am on a Mac and can read them with Gimp, and GraphicConverter. If you do as well, make sure to start GraphicConverter before Gimp, and then open the files in Gimp, and GC will filter it first and you can set white balance, etc, in a preview, before the image opens. I also get the white square in display mode, but hadn't thought too much about it, just assumed, rightly, that chdk was running then. Besides the white square, the menus seem very stable in display mode, they don't just disappear like they do in record mode.
-
- when I try to enable DNG it tells me that badpixel.bin is missing
(badpixel.lua does not seem to work, only says "Run in record mode" ... which I did. Any ideas?!)
See the post on page 19 of this forum, by Boondaburrah, once you remove the piece he mentions in a text editor and reload to your camera, then you can run it with alt, just make sure to read the message it gives you after, I didn't and it took me a few trues before I saw that you have to press SET after.
Thanks, danstr & Boondaburrah! Hadn't yet made my way back through the thread quite far enough. Erasing the loop was the thing I was thinking about myself already, though I assumed it's vital to check for the state... but true, if you make sure it is in record yourself then you don't need to worry. Can write DNG now, not quite sure yet what to use for the workflow, though.
-
Nice work!
Finally something to play with. I will do some tests next week and maybe give some bug reports.
Keep up the good work!
A proper CHDK on my favorite cam would be awesome.
-
Hey guys i got a problem. I replaced the v8 diskboot and ps2 and can load the chdk on my ixus. But i can not use override shutter speed. I tried everything but it will not work. Where is my mistake? With v5 it worked very well
-
But i can not use override shutter speed. I tried everything but it will not work. Where is my mistake? With v5 it worked very well
Check your settings...
"Disable Overrides" (not [on]),
"Override Shutter speed" + "Value Factor" / Shutterspeed enum type"
(e.g. with "Shutter speed enum type" set to [Ev Step], you also have to enable the override by setting a "Value factor")
You should also use a clean CHDK config file -> rename or delete \CHDK\cchdk.cfg on the SD card, a new config file with default values will be created on the next CHDK start.
-
i renamed the cchdk.cfg file. then i set
disable overides to off/disable
include autoiso&bracketing is on
override shutter speed is 6
value factor is 1
shutterspeed enum type is ev step
but it only shots with standard settings like iso250 f3.2 1/60 it doesn't matter what the shutter speed is :S
-
override shutter speed is 6
but it only shots with standard specifications like iso250 f3.2 1/60 it doenst matter what the shutter speed is :S
"Shutter speed" 6 ? - i guess you mean 6.3
Your settings seem to be correct; you should see TV:6.3 on the CHDK OSD when the override is active.
What camera mode do you use ? - try M mode, no continuous mode
BTW - don't forget: by default, the settings will be reset on power off ("Clear override values @start" menu entry)
You could also try the SDM version: http://stereo.jpn.org/eng/sdm/download.htm (http://stereo.jpn.org/eng/sdm/download.htm)
-
sry you're right it was 6.3 shutter speed
i can't see any TV:6:3 on the osd
i use the manual mode in the middle. above is automatic and under the manual mode is the movie mode
maybe i should format the sd card and copy everything new. maybe there are some old files from v5 who are crashing with the new diskboot und ps2 file?
i'll try to get the sdm version on the sd card when i got some time
-
So I got it running in manual mode.
The OSD hides itself very often which is quite annoying.
And how can I record videos with CHDK running? If I set the switch to video mode it still records images.
-
thanks for the efforts so far. i hope the work is still in progress for this camera model.
i managed to save DNGs, but i can't open them with Photoshop CS4. any idea on how to do that? Picasa and Irfanview are able to open the DNGs.
-
Oh HarpoMa, where are you?
I come here every day hoping to see the v9 update or the first BETA... :(
Are you having troubles? We need you!
I really appreciate what you have done! Thank you for your hard work!
Ignas
-
Oh HarpoMa, where are you?
I come here every day hoping to see the v9 update or the first BETA... :(
Are you having troubles? We need you!
I really appreciate what you have done! Thank you for your hard work!
Ignas
I second this. I also check back here often to see any improvement, but so far, nothing.
-
I'm working on zebra atm. When I get that finished I will release a 875 patch and the new firmwares.
Harpo
-
:D Thank you, HarpoMa, very good to hear from you!
-
Since it appears zebra will take a lot more work than I thought I will post this 875 patch that adds SD780 support. Don't be surprised if zebra crashes.
Harpo
-
Sorry for the noob question, HarpoMa, how and to what do I apply this patch?
Dan :blink:
-
It is unlikely that you will want to use this. This would be for developers only. I will release a firmware on post #1 that you can place directly on the camera for actual use.
Harpo
-
Thanks, and thanks for the quick reply. :) With the resolution on this camera, I am really looking forward to when it hits beta or final stages. I appreciate the amount of work that's been going into the port!
Dan
-
Since it appears zebra will take a lot more work than I thought I will post this 875 patch that adds SD780 support. Don't be surprised if zebra crashes.
The Ixus100 / SD780 1.00c port is in the CHDK trunk now, binaries are available from the Autobuild server (http://mighty-hoernsche.de/chdk/). (SVN changeset #876 (http://tools.assembla.com/chdk/changeset/876/))
@HarpoMa
To add your patch to the trunk, i've made some small modifications:
- modemap (main.c (http://tools.assembla.com/chdk/browser/trunk/platform/ixus100_sd780/main.c?rev=876)) line 50
- added notes.txt
- main makefile preparations for AB server
- camera.h layout, needs some more clean-up
- stub files added
-
Thanks for the BETA! Do most of the points on the first post still apply? ie: scripts, ignored stuff, etc?
Regards,
Dan
-
I'll do an update of the first page this weekend with the details of work.
-
:DMuch appreciated. Will try it out when I get home and have the camera in hand again. :lol
Dan
-
I downloaded the latest beta (877) today and copied onto the sd card. But after "firmware update" the screen goes black, and the chdk is not starting.
I need to remove battery to make the camera working again with stock firmware.
Prealpha version downloaded from post 1 is still working ok.
-
Great to see there's some more progress on this. Been using CHDK lots and looking forward to a stable version.
I downloaded the latest beta (877) today and copied onto the sd card. But after "firmware update" the screen goes black, and the chdk is not starting.
I need to remove battery to make the camera working again with stock firmware.
Prealpha version downloaded from post 1 is still working ok.
Same here.
-
Damned... If both LEDs show up, that means that the dumper found the BOOTDISK signature and also a function pointer that could be possible the WriteSDCard function. I compared the functions of the SD780 1.0C dump with the G11 functions, and there are almost the same. I am wondering that it is not working... :blink:
@ERR99
I have the 1.00B too and tried to dump it. I tried the DISKBOOT.BIN you provided and both LEDs lit up. I had formatted the card with a 20MB fat16 and filled it with zeros and only copied the DISKBOOT.BIN over. The md5sum of the FAT16 partition before and after it was run in the camera showed it was exactly the same :-(
-
I'll try the 877 myself and see what the deal is..... I confirm that it's not working from the autobuild server. I will check it out from svn and see if I can build a working copy....
Harpo
-
@fe50 - I don't pretend to understand how this would occur but I'll tell you what I found.
The stubs_entry.S that you generated for the sd780 seems to have a consistent offset in their location.
The 4th digit is always off by 1. So for AllocateMemory 0xffa3df5c is correct but the file has 0xffa4df5c....
I think it's because I included some padding in the front of the firmware dump....My padding is exactly the size of the offset.
I have attached the working stubs_entry.S
Harpo
Mine:
// !!! THIS FILE IS GENERATED. DO NOT EDIT. !!!
#include "stubs_asm.h"
NSTUB(AllocateMemory, 0xffa3df5c)
NSTUB(AllocateUncacheableMemory, 0xff827448)
NSTUB(Close, 0xff823c98)
NSTUB(CreateTask, 0xff81afac)
NSTUB(DeleteFile_Fut, 0xff823544)
// ERROR: EnterToCompensationEVF is not found!
NSTUB(ExecuteEventProcedure, 0xff86a590)
// ERROR: ExitFromCompensationEVF is not found!
// Best match: 57%
NSTUB(ExitTask, 0xff81b23c)
NSTUB(Fclose_Fut, 0xff8236c0)
NSTUB(Feof_Fut, 0xff8238ac)
NSTUB(Fflush_Fut, 0xff8238e8)
NSTUB(Fgets_Fut, 0xff823814)
NSTUB(Fopen_Fut, 0xff823680)
NSTUB(Fread_Fut, 0xff82376c)
NSTUB(FreeMemory, 0xffa3df54)
Yours
NSTUB(AllocateMemory, 0xffa4df5c)
NSTUB(AllocateUncacheableMemory, 0xff837448)
NSTUB(Close, 0xff833c98)
NSTUB(CreateTask, 0xff82afac)
NSTUB(DeleteFile_Fut, 0xff833544)
// ERROR: EnterToCompensationEVF is not found!
NSTUB(ExecuteEventProcedure, 0xff87a590)
// ERROR: ExitFromCompensationEVF is not found!
// Best match: 57%
NSTUB(ExitTask, 0xff82b23c)
NSTUB(Fclose_Fut, 0xff8336c0)
NSTUB(Feof_Fut, 0xff8338ac)
NSTUB(Fflush_Fut, 0xff8338e8)
NSTUB(Fgets_Fut, 0xff833814)
NSTUB(Fopen_Fut, 0xff833680)
NSTUB(Fread_Fut, 0xff83376c)
NSTUB(FreeMemory, 0xffa4df54)
-
The stubs_entry.S that you generated for the sd780 seems to have a consistent offset in their location.
The 4th digit is always off by 1. So for AllocateMemory 0xffa3df5c is correct but the file has 0xffa4df5c....
I think it's because I included some padding in the front of the firmware dump....My padding is exactly the size of the offset.
Yes, that makes sense :)
I used a dump from my collection, without a check, just let the build process create the stub files.
I'm on the run now, but i'll check & update the dump and commit the correct stubs to the SVN repository this evening.
-
Hello, I've tried the SVN Autobuild:
Tried out the Override shutter speed with 128s value and my yard was almoust clear as day with ISO 80 :D Thanks !
Tried TV bracketing - works like a charm, but still little slow when goes around few loops...
ND filter - OK
etc.
Bugs:
Video shot with CHDK shows as "Unidentified image" in Preview mode, but computer plays it normally...
DNG files turns out like this:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg38.imageshack.us%2Fimg38%2F3973%2Fdng.png&hash=9fc47da79818010edc5a41f883a04da3)
In the menu, next to OSD parameters sometimes CHDK shows this:
[ 6528 = 0x00080006 ]
[ 6512 = 0x00000000 ]
[ 6496 = 0x00000000 ]
Nothing more for now...
Good luck, bye!
-
@HarpoMa:
SVN updated with corrected stubs_entry.S, also replaced the sd780 1.00c dump in chdkdumps2 with a cleaned one.
-
I tried the 878 build, get the same type of colored distortion in the raw files, tweaked the ult_intvl script because the parameters could not be saved , but was able to get bracketed tv working with custom timer. The jpg files are definitely bracketed by 1 ev which is what I shot, but no joy with the raw. Haven't tried motion detection yet, but bad_pixel.lua worked without any adjusting. Raw was working in the past, I remember getting some really nice sunrise shots, don't know what's changed there. I also get the numbers flashing but only while moving up in the menus, doesn't happen while moving down.
Looks promising, looking forward to a raw fix.
Keep up the awesome work, HarpoMa
Dan
-
Raw file issue confirmed and I now know the issue (Seems I left my head somewhere else) - Movie issue doesn't appear for me. I see a regular image for mine. I'll see what I can see and get back to you.
I'll do some more qa for a release the minor patch.
Harpo
-
I'm having a problem getting this to work.
I have an SD780 with GM1.00B.
I downloaded this file
ixus100_sd780-100c-0.9.9-878-full_BETA.zip
unzipped it and put it in the root of my FAT16 formatted card.
I power the camera on in playback, I hit menu, I do a firmware upgrade, but, at that point, the screen goes black and nothing happens until I remove the battery.
Any help?
Thanks!
-
Hello & welcome, lexluthor !
I have an SD780 with GM1.00B. <---> ixus100_sd780-100c-0.9.9-878-full_BETA.zip
There's no 1.00B CHDK for your camera until now ;)
-
Hello & welcome, lexluthor !
I have an SD780 with GM1.00B. <---> ixus100_sd780-100c-0.9.9-878-full_BETA.zip
There's no 1.00B CHDK for your camera until now ;)
Wow, that stinks. So I have an older firmware in my camera?
There's no way to get CHDK to work on it?
-
Very sorry to be a pest. Is raw fixed, or will it be posted here when it is? Just don't want to keep downloading and re-installing until I know. :-[
Thanks,
Dan
-
@danstr - Nope not yet. Watch this thread and when it is it will be posted here.
Jason
-
O.K. Thanks Jason,
Dan
-
My bugreport with 878:
1: Switch from manual to Auto mode and back is not working. I need to turn off the camera, switch to auto mode, and turn back on.
2: When in auto mode, and the background of the AUTO logo in the upper left screen turns blue, the chdk osd font color also turns blue.
I know that AUTO mode seems not too important for chdk users, but I need it becouse of the WAF (Woman Acceptance Factor)
-
Is there any possible way to upgrade my camera to firmware version 1.00C?
And if I can't, then there's no way to use CHDK?
-
1.00C is not available as a FW upgrade from Canon so the answer sadly is no. If anyone ever dumps the FW from a 1.00B then I will try to make a 1.00B version.
Harpo
-
1.00C is not available as a FW upgrade from Canon so the answer sadly is no. If anyone ever dumps the FW from a 1.00B then I will try to make a 1.00B version.
Harpo
Well is there any way to take the .bin dump of 1.00C from the first post here and load that onto the camera? I guess there must be some sort of firmware upgrade utility? Sounds a bit risky, but maybe people have done it?
If not, is it difficult to make a dump of 1.00B? If it's not too complicated, I'd be happy to give that a shot.
-
Nope on the firmware update method. It would be a bad idea to even attempt it.
As for dumps and porting I won't begin to repeat what the wiki so nicely says. http://chdk.wikia.com/wiki/For_Developers (http://chdk.wikia.com/wiki/For_Developers)
It really is dependent on your skills. I will try to get a version of udumper working on the 1.00C and if I can then it likely will dump the 1.00B but no certainty or timeline on this.
I am focused on a stable beta build atm.
Harpo
-
I understand. I don't think I'll try doing the dump myself. I probably could, but it's probably not worth it, though those added features are nice.
Thanks.
-
Hey guys i got a problem. I replaced the v8 diskboot and ps2 and can load the chdk on my ixus. But i can not use override shutter speed. I tried everything but it will not work. Where is my mistake? With v5 it worked very well
disable overides to off/disable
include autoiso&bracketing is on
override shutter speed is 6.3
value factor is 1
shutterspeed enum type is ev step
but it only shots with standard settings like iso250 f3.2 1/60 it doesn't matter what the shutter speed is :S
i got stillt the same problem. i installed chdk with the script for macs. i can run chdk, but when i set the value factor of the override shutter speed to 1 it does not change the settings and shots photos with iso400 f3.2 1/40
is there a problem with the v8 diskboot.bin and ps.fi2 files?
-
I would say yes given the fact that people are saying so. You might try the autobuild instead.
Harpo
-
I would say yes given the fact that people are saying so. You might try the autobuild instead.
Harpo
thanks the autobuild seems to work
-
I've had and 1.00B. I'm new to the project. The udumper does not work, thus I decided to dump it by blinking. I used a BPW 40 photo-diode (they had no 96 anymore). Because the blinker code did not worked for me, I've developed my own code.
I've succeeded blinking the firmware out, actually the beginning. As the battery went empty, it completely bricked my camera (impossible to power it on again). I've just received it back from warranty, but they upgraded my firmware to 1.00C. Thus I can not blink the rest of it. Here I'm posting what I have. I hope it's enough.
Otherwise, I'll be happy to help someone who wants to try it. I also had to learn everything since beginning.
I've dumped 6185989 Bytes, start a address ff810000 until ffdf6405. I hope I did it right.
I will post my source code as soon as I've cleaned it. I will also try to make udumper work.
IXUS 100IS 1.00B (https://file.tsaitgaist.info/www/?a=d&i=q6TvFff9Fd)
-
Thx. I will look at this and see if I can make a blind 1.00B version....Looks great but won't fully know until I get home tonight.
Sadly it looks like good portions are corrupt. Did you employ CRC checks of any sort?
I will try to create enough of a boot to read the FW and write to a file.....
Harpo
-
Thanks guys. It'd be great if you could pull it off. I'll keep checking in.
-
I did not used any CRC. I wanted to implement this feature a bit later. I dumped with the first version of my program, just to try if it worked.
I dumped the firmware in several pieces (the file in the previous post was the assembly of them)
here the originals (https://file.tsaitgaist.info/www/?a=d&i=SSjCfqgsGP).
-
Would it be difficult to get the required hardware from a radioshack to do the blinking for the 1.00B? I'm a total novice, but I can follow instructions, especially if you already have blinking code that works.
-
@wasabi1023 - This URL will help answer that question. A lot of people have done a lot of things but this URL gives a nice overall set of methods. 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)
-
I couldn't figure out the software part of the photodiode-to-soundcard method. I don't compile stuff on a regular basis (windows user), so I don't know how to get the environment correct for the source code to compile correctly. The readme.txt that came with the source is in some foreign language.
-
ixus100_sd780-100c-0.9.9-879-full_BETA.zip
works! yeah :D
-
@cricker
Yes, it's very nice to have chdk for the sd780, although check your raw files, I'm still getting the line pattern as posted previously. I look forward to the stable Beta that HarpoMa is working on. I have three other Canon p&s cameras with varying stages of chdk on, and am happy there is so much effort going into this one. I think it's a great little ( emphasis on little) camera to have all those extra features.
Dan
-
Hi.
I am new here and casually using the chdk_sd780_prealpha_v3 since October 2009 for DNGs with my girls cam; but mostly with manual firmware update - WAF as Benoe said.
New ixus100_sd780-100c-0.9.9-880-full_BETA doesnt write DNGs at all.
ixus100_sd780-100c-0.9.9-878-full_BETA and ixus100_sd780-100c-0.9.9-879-full_BETA did the same sixties wallpaper DNGs danstr describedand ignasx showed.
-
On post #384, Jason said he would post here when Raw is fixed. I am assuming that stuff like this is not easy, having gotten not much further than "Hello World" in my many attempts to learn programming. I am waiting patiently ;) for the capabilities to be extended for this camera, having owned it now for about a year. In the meantime I have an SX200 with the same resolution, also chdk enhanced, it's just a little bulky to haul around in a pocket all the time.
Regards, Dan
-
@danstr - Thx. I will release a binary this weekend just for you. :) How do you like the sx200? I think I will get a SX210 once they come out.
-
@HarpoMa
Thanks, Jason, :xmas
I like the SX200, I was looking at the SX210, but liked the features and reviews of the 200. It's got a great zoom. The pictures are very nice, the only thing is some barrel distortion is very noticeable at wide angle, can be corrected in Photoshop, just have to be careful composing shots due to having to crop after. I was combining features while away at a seismic camp this winter. In March it got warmer, and there was snow melting off the trailer roof, so I cranked the shutter speed up, as well as upping the flash, put the camera on a tripod with intervalometer set for 5 to 7 second intervals, focused on water drops hitting the ground, and left it for a while. Usually averaged 1 in 3 or four shots of fairly nice droplet splashes, with autofocus got some nice, clear shots. Usually got about 300 or so shots before the batteries died. It's all fun 8)
Dan
-
Hy, i'm a new member, i had a sd 780 (ixus 100is) camera with the firmware 1.00b. I have seen that the beta porting is only for the 1.00c firmware, i wish to know if it is possible to upgrade the firmware to 1.00c and how if is possible. I know that there is no official upgrade from canon for this camera...
Thank You
-
No canon fw upgrade exists ATM. I am working on trying to get a 1.00b blind port but i don't have a great firmware dump. :( If you can provide a fw dump of the 1.00b then I can likely get you a port.
harpo
-
No canon fw upgrade exists ATM. I am working on trying to get a 1.00b blind port but i don't have a great firmware dump. :( If you can provide a fw dump of the 1.00b then I can likely get you a port.
harpo
ok in the next days i will read the instructions and i will try to dump the firmware, i don't know anything but i'm a web developer so i hope i will do it
-
Hi all
Seem to have made a 4gb card work on my Mac and got the Canon 100is to shoot a few raw/dng pics. :)
What can I do with the dng files in OS X, Win or Linux?
Will they display/convert or is it still in progress?
Can I make a real 5 pic HDR yet?
Sorry for the questions if all this is still very much in beta.
Thanks very much for all the hard work. :)
-
Patch for fixing RAW/DNG (with correct colour profile noless), addition of a palette (sadly SD780 is also different) and a fix of the UP button spitting messages to screen. This also cleans up camera.h SD780 section considerably.
-
@Hux
The build you are using has a bug in RAW/DNG so you can't use them atm. The patch I've uploaded has the fix but it could be a few days before it's entered into the autobuild. (a guess as it depends on the schedule of people who can enter in such changes)
Once the fix is in you can use the DNG native on the mac (at least in 10.6 you can) They are simply higher detail versions that become the eventual JPG (if anyone wants to correct my layman answer please do)
"Can I make a real 5 pic HDR yet?" Sadly I don't know much about this question.
Harpo
-
Patch for fixing RAW/DNG (with correct colour profile noless), addition of a palette (sadly SD780 is also different) and a fix of the UP button spitting messages to screen. This also cleans up camera.h SD780 section considerably.
Thx, commited to the trunk, changeset #881 (http://tools.assembla.com/chdk/changeset/881/).
Can I make a real 5 pic HDR yet?
First: Hello & welcome :)
If braketing in continuous mode is working on the SD780, you can easily do it like described here:
--> Scriptless Tv bracketing (http://chdk.setepontos.com/index.php/topic,2143.msg19864.html#msg19864) (also: http://chdk.setepontos.com/index.php/topic,2972.msg37704.html#msg37704 (http://chdk.setepontos.com/index.php/topic,2972.msg37704.html#msg37704))
To build the HDR images you need a appropriate software, you'll find some links here:
--> CHDK wikia: Software - Stacking & HDR (http://chdk.wikia.com/wiki/Software#Stacking_.26_HDR)
The new #881 Autobuild download package should be available from the Autobuild Server in ~ 20 minutes...
-
:xmas @HarpoMa
Awesome, Jason :D It's great to have raw again. And on my Macbook, they open right up in PS4, no intermediary programs needed. Greatly appreciated!
I do notice that script parameter values are not saved, ie: ultra_intervalometer on my other cameras switching to parameter set 1 from 0 will save my settings in 0, on this camera that doesn't happen, not a great big deal, just have to set those values each time before using. I use that script with a setting of one for single shots, so just changed the default value in the script. And I know... they're called Beta for a reason. I am very happy to have so much more to do with this camera! Great job!
Thank you, Jason,
Dan
-
I doubt script parameter values are specific to the sd780. Are you certain there is not a "clear settings" on boot option turned on? If you know different then mail me a copy of the script and I'll test with it.
Harpo
-
The thing is, it occurs inside the script, without leaving the parameter menu, so clearing override values(which is not set) shouldn't affect it, the camera has not been shut off.
This is the script:
rem Author - Keoeeit
rem Written for S-Series
rem Should be okay on others
rem Use Endless mode with caution
rem See documentation for important info
rem first version
@title Ultra Intervalometer
@param a Delay 1st Shot (Mins)
@default a 0
@param b Delay 1st Shot (Secs)
@default b 0
@param c Number of Shots
@default c 5
@param d Interval (Minutes)
@default d 0
@param e Interval (Seconds)
@default e 0
@param f Interval (10th Seconds)
@default f 5
@param g Endless? No=0 Yes=1
@default g 0
p=a*60000+b*1000
t=d*60000+e*1000+f*100
if c<1 then let c=5
if t<100 then let t=100
if g<0 then let g=0
if g>1 then let g=1
if p<0 then let p=0
z=t*c
y=p+z
print "1 Cycle Time:", y/60000; "min", y%60000/1000; "sec"
goto "interval"
:interval
if p>0 then gosub "pause"
print "Shot 1 of", c
shoot
if c=1 then end
for n=2 to c
sleep t
print "Shot", n, "of", c
shoot
next n
if g=1 then goto "interval" else end
:pause
n=(a*60)+b
for m=1 to n
q=n-m
print "Intvl Begins:", q/60; "min", q%60; "sec"
sleep 930
next m
return
What happens is that when I load script from file, I get the normal menu, split into two part, the bottom part having the parameters to be set, the top part having the line with:
parameters set (0), and if you set your values in the bottom part, and then switch to parameters set (1), and switch back, the values I picked in set(0) should still be saved, but they revert to defaults.
It works on my other cameras, but not on this one.
Just noted something else, while I was checking the script thing, if in auto mode, I hold down the power switch for a bit while chdk is active, my settings change on screen from auto to macro symbol. I don't know if that is a normal function, and I just never saw it before.
Sorry if this stuff sounds picky, I am really happy with what there is right now, just trying to help with any testing.
Regards,
Dan
-
Hi,
short question: does this CHDK for 100IX support continuous mode?
The standard menu does not offer a continuous mode and as far as I understood, this is a prerequ for the CHDK continuous mode.
(I would like to take a picture every x seconds, auto mode, no change in the settings like Tv, Av, ISO....)
Best regards,
Rainer
-
Hello & welcome, husel !
short question: does this CHDK for 100IX support continuous mode?
The standard menu does not offer a continuous mode and as far as I understood, this is a prerequ for the CHDK continuous mode.
Continuous mode is a Canon camera mode available on all Powershots (also on the Ixus series), available in M mode.
(I would like to take a picture every x seconds, auto mode, no change in the settings like Tv, Av, ISO....)
For this an intervalometer script can be used, e.g. this (http://chdk.wikia.com/wiki/LUA#Minimalistic_Intervalometer) or this (http://chdk.wikia.com/wiki/LUA#yet_another_accurate_intervalometer) one, also a script like this (http://chdk.wikia.com/wiki/User:Fe50#double_intervalometer).
A CHDK script runs in any camera mode, also in Auto mode...
-
I've tried the 882 version, and as always I accidentally loaded it from AUTO mode, please do something about it!!!
So after restarting my camera in P mode:
I noticed that: when AWB is balancing, then preview lags a little bit, so some part of code needs some cleaning...
BASIC script with Focus control still crashes and turns off... (This script: http://armanbohn.com/blog/?p=93 (http://armanbohn.com/blog/?p=93))
Motion Detection WORKS!!! Hooray!!!
The Unidentified image bug I mentioned before still exist, but it only shows up in 640 and 320 mode.
RAW is working (even shows up in Photo Shop), I'm not sure, but it looks like Bad pixel removal doesn't work, tomorrow I will try to make a new badpixel.bin
Regards, Ignas
-
@ignasx - No idea what you are talking about in your first comment. You are welcome to fix the issue if you are in such a dire need for it. Second comment you need more clarity. "AWB is balancing..." I don't know specifically what you are refering to. RAW/DNG does take a bit to write an image is that what you are talking about?
BASIC script - I'll look at that.
Unidentified image - I'll see what I can see now that I know it's only under certain modes.
Bad pixel - one day I will test it.
Harpo
-
@danstr - no problems I'm happy to fix stuff I certainly don't use much of the functions of chdk so I don't know what all is broke all the time. I will address this issue when I manage to find why it's an issue. LOL
-
@HarpoMa
Thanks Jason, really it's only an issue in that different preferences can't be saved as a set of preferences. The script's default settings can be changed when saving the script on the computer, it just means saving a separate script for each set of differing parameters, instead of being able to save different parameter sets within the script as is usually the case. To be honest, I haven't tried the latest build on my other cameras, it may be chdk related, not sd780 related. Build 881 on my sd890 saves the parameters. I'll let you know what I find.
(edit) The script parameters are saved on my sd890 with build 882, but not on the sd780, I even tried the script by placing it in the main script folder thinking that might make some difference, I'm not sure why I thought that.
The sd780 does work with multipartition on an 8GB card, in regards to needing verifying on your first post. Except for the issue I mentioned, basic scripts work, and I notice I no longer need to remove the bit in Lua scripts that I had to before, the part that checks for recording, badpixel.lua worked "right out of the package".
I also notice that the numbers do not show anymore when scrolling up in the menus as well.
Nice job! :D
Dan
-
Hi all - 1st post on the forums but been lurking for a while now. Just wanted to say that as a complete newbie, I've successfully loaded the beta and it works great.
Still getting to grips with all the functions, but already just having the shutter speed override is amazing.
HarpoMa et al.... legends, the lot of you!!! Thank you!
-
-
Another silly question...
On the sx200 I can use zoom while taking photos in chdk. Any idea if that can be implemented in the sd780? AFAIK the other cameras probably don't do this, I've tried chdk on 5 in all, and the sx200 is the only one I own that I can do this on.
This is more of a side note than an actual request, Jason.
Dan
-
@danstr - Can you describe more of the "zoom during photo" As I don't have an sx200 I don't know what precisely you refer. You don't mean movie because I know that works. If its a script that where I'll be heading next so just provide the script you use and I'll debug with it.
@gonzalito - I don't know if it's possible but one of these days I will try to get further into the movie stuff. I have done some research (and have likely caused the unidentified image bug) in the process. :)
-
@HarpoMa
Not a script, and not in movie mode, just taking photos on the sx200, the zoom works, it might have something to do with the motor Canon uses in that camera. In CHDK on the sx200 you can sort of half push the zoom lever that surrounds the shutter button, and zoom in and out to shoot pictures. If you push all the way side ways, it steps in small increments. Kinda handy, actually. That camera has the print button, and that is the alt button, so you don't have to back out of CHDK, zoom and then press print to get alt again, like I have to with other cameras, or disp on the sd780, it just works while in alt.
Be kind of neat to add that capability to chdk for all cameras. Maybe the sx200 porting enabled it somehow?
Dan
-
Thanks a lot for your effort, HarpoMa :)
I also wanted to ask you about "Video quality" option. In SD400, i.e. , members saw see big improvements in picture quality and data rate when increasing this option (to full 99%). Would you work on that feature in the SD780?
Thanks again!
-
No canon fw upgrade exists ATM. I am working on trying to get a 1.00b blind port but i don't have a great firmware dump. :( If you can provide a fw dump of the 1.00b then I can likely get you a port.
harpo
Hi, I tried several time today to dump my 1.00b firmware without any results, I used the udumper into cardtricks and checking the process carrefully, but nothing dumped... any help or any other method?
The procedure wich I followed:
1 Create the udumper card from cardtricks using dryos as system
2 Locked the card
3 Insert the card in the camera and switch on it by pressing the preview button (the green arrow)
I tried several times putting in and out the battery each time but every time that I switch on the camera the message "card locked" will appear, I wait 60 seconds but the file is always empty (full of zeros)
Thank You
-
Thanks a lot for your effort, HarpoMa :)
I also wanted to ask you about "Video quality" option. In SD400, i.e. , members saw see big improvements in picture quality and data rate when increasing this option (to full 99%). Would you work on that feature in the SD780?
Thanks again!
Have you tried the video options? I think you will find it already does video quality overrides.
-
@bugmenot - Sadly udumper does not work for the sd780. Only way is blink it out to a serial port/sound card. Yes you blink a little light very fast. LOL
Likely you will not want to but it's an option.
-
:xmas @HarpoMa
Awesome, Jason :D It's great to have raw again. And on my Macbook, they open right up in PS4, no intermediary programs needed. Greatly appreciated!
I do notice that script parameter values are not saved, ie: ultra_intervalometer on my other cameras switching to parameter set 1 from 0 will save my settings in 0, on this camera that doesn't happen, not a great big deal, just have to set those values each time before using. I use that script with a setting of one for single shots, so just changed the default value in the script. And I know... they're called Beta for a reason. I am very happy to have so much more to do with this camera! Great job!
Thank you, Jason,
Dan
I can't open a RAW in PS4? I'm new to CHDK so there may be some settings in CHDK that I don't have right. I have downloaded and installed #882 from http://mighty-hoernsche.de/. (http://mighty-hoernsche.de/.) Raw is turned on and CRW files are saved to my SDHC card, but when I try to open them up in Photoshop CS4 I get the error: "Could not complete your request because it's not the right kind of document"?
Any ideas what I need to do to get RAW working...?
-
You need to review the wiki and beginners guides. DNG requires RAW and DNG to be on. Auto start requires you to setup the card with cardtricks and have the card locked.
Harpo
-
Yeah I've got Auto start working OK, but didn't realize that both RAW and DNG needed to be on. I'll try that and have another look at the wiki and beginners guides.
-
Thanks a lot for your big job HarpoMa!!! I really enjoie the new features. DNG opens as well on Photoshop CS3 with no problems. But in video mode raw and dng are disabled and in the menu there is no exemption point about videos. I don't mind much at the moment, I'm just wondering.
-
Why would you expect to see RAW/DNG in video mode? Don't expect anything RAW/DNG in video.
Jason
-
-
I expected DNG in video mode because the guidelines mention at RAW parameters, that you can disable RAW at video mode among other exeptions. In my menu I find the exeptions, but not the video mode.
-
Thought this was the place to ask beginers questions. Can you please guide me where the beginners guide is located?
All I know, if I generate a DNG and it's on my SD card, PS4 cannot open the DNG, which is weird. Beginner or not.
Thanks,
Bart
You need to review the wiki and beginners guides. DNG requires RAW and DNG to be on. Auto start requires you to setup the card with cardtricks and have the card locked.
Harpo
-
Hi Bart
Are you sure, that you use the newest Beta version? It changed sometimes aroung the weekend and with the older version RAW/DNG didn't work. Took me some time to find out as well..... but now I have no more problems.
-
-
Thanks Maina,
Must have been using the "old" version then, since I downloaded it somwhere this weekend. To soon apparently. Will try the current one. Thanks again!
Edit: done, and it works!!! Thanks again!!
Kind regards,
Bart
Hi Bart
Are you sure, that you use the newest Beta version? It changed sometimes aroung the weekend and with the older version RAW/DNG didn't work. Took me some time to find out as well..... but now I have no more problems.
-
@HarpoMa
:) Jason, just want to say thanks for all the effort!
Dan
-
HarpoMa great to see you back! Multipartition boot works perfectly, very nice.
For the sd780 is video users: When shooting video in 720p HD using video quality overrides, I can only go to ~70 before getting memory card buffer errors. I'm using Sandisk Ultra class4 2GB card, but results are nearly identical for a class6 kingston card. Default setting works fine, so the default must be lower than the standard ~84 that I read elsewhere is similar to the canon's internal default. Anyone have an idea what the default canon level video quality is when shooting 720p? Also, what is the highest video quality override you guys can use (and with what SD card) during 720p video recording? I'm just wondering what it will take to get to max quality 99 for 720p video with this little camera.
Thanks,
Steve
-
@the_rev - Also note that some people have reported that the override for video quality has a CHDK bug and sometime it doesn't take effect. I have seen odd things happen and it is an item I have on the "Verify" list. Also note that there are a lot of assumptions about the quality number in the code (if I recall the comments from the code correctly). The "99" quality number is not actually the number used but rather a percentage of an internal value that is assumed to be the max. If people are actually going to post "their" number it would be greater use if they were to post it under the benchmark area of the wiki.
PLEASE read the benchmark info carefully and follow it precisely.
Thanks,
Harpo
-
@jensemann - In video mode the (half-pressed) AF Key doesn't work.
It does work now. :D :D :D
Harpo, you're the man!
-
Thanks jason, I'm having a lot of fun with all the new possibilities with my ixus 100IS !
The focus doesn't work, when I change the focus in the chdk menu the screen turns black. I tried different numbers, but always the same result.
Also I can't change the button to or from AUTO modus, while the camera is on.
Any ideas about that?
maina
-
A reminder to everyone. Please read the recent posts and post #1 before posting your questions. They are likely answered there. This is a BETA build and things are untested and broken in places. Feel free to post but I don't want to answer the same questions over and over if I can avoid it.
@maina - Focus setting is untested and I will look at that after I finish the FW dumping research. As for AUTO to manual switching that is a known issue.
I mean no rudeness in this but I would appreciate everyone doing their job and I'll continue to do mine to the best of my ability. Thx.
Harpo
-
after I finish the FW dumping research
Jason, is dumping 1.00b FW in your plans? ???
Thanks in advance.-
-
Plans? - Yes Will i succeed who knows. I don't own a 1.00b fw camera so I am trying to find a way for udump to work on my 1.00c so that I can give it to a 1.00b owner.
-
Great, Jason... Count on me to test it on my 1.00b camera... And thanks again for your effort and dedication... Regards!
-
I have been trying to get the remote USB feature to work on this camera with no avail. Remote is enabled in the CHDK software. I have tried a few different scripts. I have tried 3 volts, 4.6 volts, and 5 volts directly from a USB port. I am positive my wiring is correct according to the wiki diagram (using the red and black wires with the correct polarity). Is there something I am missing? Is there a certain script that others know work? This is a feature I am very interested in and I am not sure where to go from here.
-
I would be very surprised if it worked. You might try the SDM build of microfunguy I beleive he cleaned up the sd780 for his build. I however have never tested usb remote on the sd780 and would be surprised if it worked yet.
-
Ah, ok. This makes a lot more sense now. I did read his posts about it "working" but didn't fully realize it was a separate build. Well, for the record, it doesn't seem to work. ;) No rush. I will wait on building my cable and wireless remotes until I know what kind of voltage it wants to see though I could assume that his build would work the same way voltage level wise.
In any case, thank you for your effort on this project. I feel like my camera has super powers with just the beta.
-
I would be very surprised if it worked. You might try the SDM build of microfunguy I beleive he cleaned up the sd780 for his build. I however have never tested usb remote on the sd780 and would be surprised if it worked yet.
Yes, with SDM the USB remote works perfectly.
-
I would be very surprised if it worked. You might try the SDM build
Jason,
#define USB_MASK (0x80000)
-
LOL. I'll make that change.
-
-
Where can I find the override aperture option in 100c?
-
Where can I find the override aperture option in 100c?
The IXUS 100 / SD780 do not have a real aperture, only a ND filter - as all other Ixus series cameras; so there's no Av CHDK override, only a ND filter override.
-
I'm moving my thread over here from the main discussion line:
Hi, i've finally managed to try and install CHDK (ixus100_sd780-100c-0.9.9-885-full_BETA) on my SD780IS camera.
Everything seems to be working fine, i can access the menu, run scripts, etc. etc.
The problem is that when i try to shoot the camera focus and then freezes: the lens stays out but everything else seems to be turned off. I can get the camera to respond by power cycling or by pressing the display button (the camera seems to boot from scratch when i use the display button, showing the CHDK splash page).
Also, one thing i forgot to mention in the other thread: the vers.req and ver.req files don't work: either i'm pressing the wrong buttons (i doubt it) or something's not working correctly, all i can manage to get is the clock ticking.
Any idea on why is this happening and what can i do to solve the problem or help debugging?
To answer to Jason / HarpoMa:
The CHDK firmware i installed is 1.00C and i'm not in ALT mode when shooting, when in ALT mode i can see the scripts running correctly.
Thanks!
Marcello
-
Follow the instructions on this page http://chdk.wikia.com/wiki/SD780IS (http://chdk.wikia.com/wiki/SD780IS) with regards to getting the version of the camera. I know the build works beyond what you are experiencing. I'm concerned that if you have a new camera it may have a newer firmware. So you need to confirm you have camera firmware 1.00C.
Now that I've written that there is one thing that you might find would cause this.... Did you turn on Zebra? If you did turn it off. Zebra is known to crash the sd780 at present.
Harpo
-
Hi, i checked and it actually was the zebra option. I initially turned it on and then forgot about it.
My bad! ;)
I checked the camera firmware and it is indeed 1.00C so i can confirm that zebra causes crashes.
Thanks for your help!
M
-
I really appreciate the work on this camera, but can't make the ND filter override work. Have others? If so is there something I might have missed in the setup?
-
How do you know that it does not work ?
What I mean is ... how do you know what the Canon firmware intended to do before you tried to override it ?
David
-
@ap1414 - ND Filter does work. Go to overrides and turn on ND Filter. The filter does not engage until 1/2 shutter press
Harpo
-
How do you know that it does not work ?
What I mean is ... how do you know what the Canon firmware intended to do before you tried to override it ?
David
Without the override, in P mode at wide angle, the firmware selects 1/80 f9. At that point I'd rather stay at f3.2 with a faster shutter but with "ND Filter:Out" showing in red on the display the camera still selects 1/80 f9, so it doesn't seem to be having any effect
-
@ap1414 - I'm still new with chdk but I beleive you will find that a lot of the canon screens lie when we do things it doesn't expect. For instance you are overriding ND. If the camera put it out itself it would adjust it. So basic rule is this....if you override then canon doesn't know about it.
Anyone with more info have a better way of saying this?
Harpo
-
I have asked an SDM user to test it.
I cannot remember if the indicated 'aperture' changes when you half-press.
Of course, you have to be overriding in the opposite sense to what the Canon firmware intends to do.
Indoors, that will mean forcing the ND in, outdoors in bright light that means forcing it out.
-
I'm hoping that there a combination of settings that will persuade the camera to select a faster shutter automatically eg 1/640 f3.2 instead of the standard 1/80 f9, but maybe that's not possible
-
I'm hoping that there a combination of settings that will persuade the camera to select a faster shutter automatically eg 1/640 f3.2 instead of the standard 1/80 f9, but maybe that's not possible
It is not only possible, it is the 'ND constant exposure' option in SDM's Bracketing/Overrides menu.
It is used by kite aerial photographers to force a shutter speed 8x faster than 'normal'.
David
-
If this is a question about the sd780 running SDM please move the discussion to the SDM subforum.
Thanks,
Harpo
-
I think you misunderstand.
I am trying to help a CHDK user who cannot get the ND override to work.
By asking one of my SDM IXUS100 users to test ND override we will at least know if the firmware address of the function is correct.
-
I think you misunderstand.
I am trying to help a CHDK user who cannot get the ND override to work.
By asking one of my SDM IXUS100 users to test ND override we will at least know if the firmware address of the function is correct.
Many thanks for your help. Is what I'm I'm looking for - forcing a faster shutter speed by keeping the ND filter out - a function in SDM rather than CHDK? If so I should try SDM
-
@ap1414 - I don't think it's strictly a SDM function but it does appear that his build might have it at present. They are seperate builds however. So if there is an issue on the sd780 build I can certainly try to fix it. However if your using the SD780 SDM build only Microfunguy can likely help you.
I try to keep my sd780 port thread clean if I can. Certainly if you find a bug in the non-SDM build here is the place to complain about it.
Harpo
-
With CHDK, you should be able to force the ND filter out only if the Canon firmware intended to force it in, as it would in bright light outdoors.
CHDK does not change the shutter-speed to compensate so the exposure would be incorrect.
In fact, CHDK does not test what the Canon firmware intends to do first.
Anyway, let us wait until I get a reply from the tester.
David
-
@Microfunguy - The ND override works as I detail in a post above yours. http://chdk.setepontos.com/index.php/topic,3995.msg48448.html#msg48448. (http://chdk.setepontos.com/index.php/topic,3995.msg48448.html#msg48448.) Everytime you mention SDM in this thread it muddies the support of the sd780 port build that is not SDM. So I would greatly appreciate it if when you answer questions you don't give SDM details like
"It is not only possible, it is the 'ND constant exposure' option in SDM's Bracketing/Overrides menu."
Thanks,
Harpo
-
So, when ap414 says:-
"I'm hoping that there a combination of settings that will persuade the camera to select a faster shutter automatically eg 1/640 f3.2 instead of the standard 1/80 f9, but maybe that's not possible"
You want me to say "that is not possible with CHDK" rather than "that is not possible with CHDK but is supported by SDM" ?
Notice that ap414 is requiring a constant-exposure mode.
1/80 @ f9 is equivalent to 1/640 @ f3.2.
-
Yes that would be very clear. Then if they still want to work with the chdk they can stay here and the thread is clean and if they want to move over to the sd780 sdm build they can move to a sdm specific thread.
The biggest problem I face is that I'm a computer guy not a photographer. So often I don't know what people are talking about when they speak photo terms. :( Worse than that I don't know chdk enough yet to know if thats a special feature or just a bug or a misunderstanding. I also don't know SDM. Basically I'm messed either way.
Jason
-
Well, the tester says that the 'aperture' did change when the ND filter was forced in.
I have asked for more details, but that will be tomorrow morning now.
The addresses of the ND filter in/out functions are the same as in CHDK.
-
Any news on 1.00b or is that just not going to happen?
-
@lexluthor - Sadly I have had no success in getting 1.00c to use the write function. This mean that 1.00b still would require blinking. I haven't given up all hope but I'm pulled in a lot of directions at present.
-
Sorry, still a noobie.
I tried to test the 1.00c build by loading it on my 1 GB Sandisk Ultra II SD card via Card Tricks. Also made the card bootable, and put the card in the lock position as required in the past to make the card bootable. Took the card down to my local Best Buy to test it out on the SD 780. Camera mode would not turn on/power on. Playback mode works and shows the CHDK splash screen, but there were no images to view. Best Buy staff advised me that since the SD card is in the lock position, it will not allow the camera to be in picture/video mode,, and the lens does not come out.
Is this true or am I doing something wrong.
-
Camera mode would not turn on/power on. Playback mode works and shows the CHDK splash screen
With CHDK, newer cameras always startup in playback mode, that's a side effect of the way CHDK works.
Just press or half-press the shutter button once to switch to record mode !
On some cameras holding the power button for ~1 second starts directly into record mode, i don't know whether this will work on the SD780...
-
Holding power will work on the SD780 as mentioned by fe50
-
I asked the tester :-
" and if you then take a photo (ND constant exposure mode Off), is the
photo incorrect exposure (it will be darker or lighter)."
He replied :-
"correct it is darker - exposure and shutter speed are equal to ND filter off"
The Canon firmware does not 'know' about the ND override so the displayed aperture value is the same.
Take a photo with CHDK and ND override, it should be too dark or too light.
-
I asked the tester :-
" and if you then take a photo (ND constant exposure mode Off), is the
photo incorrect exposure (it will be darker or lighter)."
He replied :-
"correct it is darker - exposure and shutter speed are equal to ND filter off"
The Canon firmware does not 'know' about the ND override so the displayed aperture value is the same.
Take a photo with CHDK and ND override, it should be too dark or too light.
Thank you. I understand how CHDK ND filter override works now. SDM "ND contant exposure" gives me what I really wanted, except that it doesn't seem to work with 8gb cards.
-
Thank you very much!
Where can I find the override aperture option in 100c?
The IXUS 100 / SD780 do not have a real aperture, only a ND filter - as all other Ixus series cameras; so there's no Av CHDK override, only a ND filter override.
-
Holding power will work on the SD780 as mentioned by fe50
Thank you fe50 and HarpoMa are correct. I eventually bought the SD780 because of the helpful feedback you provided. Noticed when I used an empty 2GB card, space available shows 963 MB. Is this an error, or is the 1 GB being utilized for something else?
Thanks
-
Noticed when I used an empty 2GB card, space available shows 963 MB. Is this an error, or is the 1 GB being utilized for something else?
CHDK only uses less than 2MB...is the card partitioned, e.g on a Mac ?
You can format the card in the camera, then copy the CHDK files...
-
If a MAC is involved then it likely what happened to me.... You have a trash can on the SD card taking up the missing space. Do as fe50 says and you will know....
-
Hi all,
I'm trying to compile the latest svn "trunk" chdk on OSX for the IXUS100 for a special near space ballooning project but I'm having some troubles, make you can help me. The image for the IXUS100 fails to compile with the following errors. Others compile fine. Here:
[...]
gui.c -> gui.o
-> main.elf
[...]
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: Warning: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_fixunssfsi.o) does not support interworking, whereas main.elf does
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_divsi3.o)(__divsi3): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(main.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_addsubdf3.o)(__floatsidf): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(wrappers.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_muldivdf3.o)(__divdf3): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(wrappers.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_muldivdf3.o)(__muldf3): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(wrappers.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_fixdfsi.o)(__fixdfsi): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(wrappers.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_udivsi3.o)(__udivsi3): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(wrappers.o): arm call to thumb
../platform/ixus100_sd780/libplatform.a(kbd.o): In function `save_rom_log':
kbd.c:(.text+0x24): undefined reference to `no symbol'
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_addsubsf3.o)(__floatsisf): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(shooting.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_muldivsf3.o)(__mulsf3): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(shooting.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_cmpsf2.o)(__gtsf2): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(shooting.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_muldivsf3.o)(__divsf3): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(shooting.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_addsubdf3.o)(__extendsfdf2): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(shooting.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_truncdfsf2.o)(__truncdfsf2): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(shooting.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_addsubdf3.o)(__adddf3): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(shooting.o): arm call to thumb
/opt/local/lib/gcc/arm-elf/4.3.2/../../../../arm-elf/bin/ld: /opt/local/lib/gcc/arm-elf/4.3.2/thumb/libgcc.a(_fixsfsi.o)(__fixsfsi): warning: interworking not enabled.
first occurrence: ../platform/ixus100_sd780/libplatform.a(shooting.o): arm call to thumb
../platform/ixus100_sd780/sub/100c/libplatformsub.a(capt_seq.o): In function `loc_FF899D30':
capt_seq.c:(.text+0x718): undefined reference to `no symbol'
../platform/ixus100_sd780/sub/100c/libplatformsub.a(capt_seq.o): In function `loc_FF899E10':
capt_seq.c:(.text+0x7d8): undefined reference to `no symbol'
../platform/ixus100_sd780/sub/100c/libplatformsub.a(capt_seq.o): In function `loc_FF8976E8':
capt_seq.c:(.text+0xd4c): undefined reference to `no symbol'
../platform/ixus100_sd780/sub/100c/libplatformsub.a(capt_seq.o): In function `loc_FF897740':
capt_seq.c:(.text+0xd78): undefined reference to `no symbol'
../platform/ixus100_sd780/sub/100c/libplatformsub.a(capt_seq.o):capt_seq.c:(.text+0xd9c): more undefined references to `no symbol' follow
collect2: ld returned 1 exit status
make[1]: *** [main.elf] Error 1
make: *** [all-recursive] Error 1
root@mbpcelso:trunk(r885 *) #
I using the right tools, gcc-mp-4.3 and arm-elf-gcc-4.3.2 compiled from macports as suggested here http://chdk.wikia.com/wiki/Compiling_CHDK_under_Mac_OS_X (http://chdk.wikia.com/wiki/Compiling_CHDK_under_Mac_OS_X)
Also, I searched and searched for an answer with no luck.
Also, do you think that these patches to add mode dial support http://www.zenoshrdlu.com/kapstuff/zchdk.html (http://www.zenoshrdlu.com/kapstuff/zchdk.html) could be applied to the IXUS100 or is there a h/w limitation in the camera that you're aware?
Many thanks in advance for any help.
-
Your toolchain is not built correctly.
Mode override is in the trunk, I suggest using that.
-
@celso - I have tried to build on the Mac and have had no real success to date. I have had a correct tool chain and found that even when correct it would lead to a faulty binary. I strongly suggest you not use the Mac as a build platform.
Harpo
-
@HarpoMa @reyalp Thanks! I'll try it with a Linux server later.
With the current build found in the official repository, is it possible somehow to change from photo to video mode in a script and vice-versa? I'm still scrapping through all the docs but it isn't clear for me.
-
@HarpoMa @reyalp Thanks! I'll try it with a Linux server later.
With the current build found in the official repository, is it possible somehow to change from photo to video mode in a script and vice-versa? I'm still scrapping through all the docs but it isn't clear for me.
This is now a standard feature, so it should be. See http://chdk.wikia.com/wiki/CHDK_firmware_usage/MoreBest#set_capture_mode.28modenum.29 (http://chdk.wikia.com/wiki/CHDK_firmware_usage/MoreBest#set_capture_mode.28modenum.29) and http://chdk.wikia.com/wiki/LUA/Scripts:Standard/Lualib/Capmode (http://chdk.wikia.com/wiki/LUA/Scripts:Standard/Lualib/Capmode)
-
@reyalp @all
Thanks all for the help. A few hours later banging my head with the sd100 valid modes and propcases dumps I managed to code a lua script with everything I need, including switching from photo mode to video mode and overriding some values.
The only thing left is turning the lcd display off to save power but I don't it's possible while the script is running, is it?
tks
-
The only thing left is turning the lcd display off to save power but I don't it's possible while the script is running, is it?
On most cameras, you can do this by pressing the DISP button between shots (from script, if you want).
You can also turn the backlight off in CHDK (if implemented in the port), but this doesn't actually save much power. Same goes for using the AV plug to turn the display off. The ccd+ live view + display hardware seem to be what draws the power.
-
@reyalp On the IXUS 100, the DISP button is used to activate the ALT mode and I can't seem to change this on the menus. I know you can press the ALT mode key for more time to activate it's original function but it doesn't work too, I tried it. Anyways, I don't think the DISP button works in the video mode, even if CHDK isn't loaded.
Do you know how can I turn the backlight off? It's a propcase var? Can't seem to find it http://chdk.wikia.com/wiki/PropertyCase (http://chdk.wikia.com/wiki/PropertyCase)
-
Using script to simulate a disp press should give you the original function in any case.
Anyways, I don't think the DISP button works in the video mode, even if CHDK isn't loaded.
In video mode, you won't get much power saving since the sensor is still running constantly.
Do you know how can I turn the backlight off? It's a propcase var? Can't seem to find it
http://chdk.wikia.com/wiki/CHDK_firmware_usage/MoreBest#set_backlight.28.29 (http://chdk.wikia.com/wiki/CHDK_firmware_usage/MoreBest#set_backlight.28.29)
I haven't checked whether it is implemented on your camera.
-
Using script to simulate a disp press should give you the original function in any case.
Do you know how can I turn the backlight off? It's a propcase var? Can't seem to find it
http://chdk.wikia.com/wiki/CHDK_firmware_usage/MoreBest#set_backlight.28.29 (http://chdk.wikia.com/wiki/CHDK_firmware_usage/MoreBest#set_backlight.28.29)
I haven't checked whether it is implemented on your camera.
Worked nicely, thanks. Although it keeps turning the backlight on everytime you change the camera mode or the moment you shoot the photo, it does keeps off most of the time so it's a #win.
By the way, we're using CHDK in a near space balloon project here in Portugal, I'll make sure to mention you guys and your great work everytime I can.
Tks again
-
@harpoman - Could you please create and post a patch of the sd780 svn trunk against your build _when_
a)you have the experimental PTP remoting support active, and
b)hopefully have the example of firmware dump using fopen/fwrite/fflush/fclose active (or supporting routine at least present in source). (Do the routines have standard C prototype and usage?)
I'm interested in those details for possible comparison and use with sd1200 1.00c firmware.
(As best I can tell none of the trunk, this thread, or the PTP thread seems to include the details the patch could provide. I've tried to review all of those areas over the past several days, but may have overlooked.)
TIA.
-
@dh - In regards to the fopen/fwrite.... I used the _Fut functions. I'm not in front of my code atm but I seem to recall that the (platform) kbd.c has some of my debug code that used them to dump various parts of the code/variables/ect. In regards to PTP i'll place it on the list but I'm hesitant to implement PTP in it as it appears they are trying to standardise the basic set of PTP functions. I'll review the PTP thread and see if they have come to a final decision on the minimal set and what will go in the baseline.
Harpo
-
I'm not looking for PTP to be implemented in trunk (for your SD780 effort nor anything else), at the moment. You commented in PTP thread that you found it great for debugging.
I'm hoping I might find it similarly useful in working on sd1200, without having to do the grunt work you've already completed (or at least making my grunt-work a little lighter.)
As such, I expect a patch of your develpment build containing that functionality against what you have in trunk, would rather clearly highlight items that might be of use for debugging and PTP functionality in particular, as I do actually desire it for remote capture use, as well (presuming it will serve my needs, which I won't really know until I've tried - and the sd1200, with its currently incomplete port, is what I have closest at hand.)
While I don't know what the vendors's firmware version numbering scheme is between cameras, it appears that (having done a little exploration) the sd780 1.00C bears some significant similarities to the sd1200 1.00C.
Will be appreciative of whatever you have in hand or can quickly produce.
Thanks.
-
Hi all
Would this script work http://chdk.wikia.com/wiki/UBASIC/Scripts:_Bracketing_and_EV_correction (http://chdk.wikia.com/wiki/UBASIC/Scripts:_Bracketing_and_EV_correction)
But with a Digic change get_prop to 208?
Thanks very much
-
This is great work on the sd780! I have a question about the battery, has anyone found or made an external battery pack for this cam? I have tried with limited success as it seems to be very picky on the exact power requirements. Any help would be greatly appreciated!
-
I'm not looking for PTP to be implemented in trunk (for your SD780 effort nor anything else), at the moment. You commented in PTP thread that you found it great for debugging.
...snip...
I believe I have found what I was hoping for with one of ewavr's posted patches for the sx200.
If it does not turn out to be as I think, I may return here and repeat my request, but for now consider my request for a posted patch with PTP withdrawn.
Thanks.
-
Has anyone used the set_zoom_rel command in scripting for the SD780? I've tried, and it works, but often it causes the camera to spontaneously shut down (leaving the lens extended). I've tried adding sleep commands after the set_zoom_rel command (up to 2000 ms), and it seems to help, but even with the 2 second sleeps, I get occasional shutdowns.
Below is a script that recreates the problem. It's a pretty simple script (and not very useful), but it's a stripped-down version that recreate the problem by just using the left and right buttons to control zoom. I use autoboot, so when it gets into the script, I press "set" to take a picture, and then press the "right" button to zoom in. Sometimes it shuts down on the first zoom, sometimes on the second. I've also tried zooming in (outside of the script) and then zooming in with the script, to similar results.
====================
@title Testing set_zoom_rel
rem
rem Initialize snapshot counter
b=0
while 1
wait_click
is_key k "left"
if k=1 then gosub "zoom_out"
is_key k "right"
if k=1 then gosub "zoom_in"
is_key k "set"
if k=1 then gosub "snapshot"
wend
end
:snapshot
print "shoot: ";b
press "shoot_full"
sleep 1500
release "shoot_full"
release "shoot_half"
b=b+1
return
:zoom_in
print "zoom in"
set_zoom_rel 1
sleep 2000
return
:zoom_out
print "zoom out"
set_zoom_rel -1
sleep 2000
return
return
=====================
Any suggestions would be greatly appreciated. Thanks!
-
Its a Beta build so I would assume it's a bug somewhere.
Harpo
-
On gmt may 4, 2010 approx 3:00am+/-, the firmware dump at:
http://chdk.mydev.ca/IXUS100_SD780/8M_SD780_100C_fw.zip (http://chdk.mydev.ca/IXUS100_SD780/8M_SD780_100C_fw.zip)
linked to from:
http://chdk.wikia.com/wiki/SD780IS (http://chdk.wikia.com/wiki/SD780IS)
appears to contain an extra 65536 bytes on the front (so 8M plus 65536 bytes.)
It might be helpful to some to either remove the leading extra bytes, or perhaps at least make a note of that in close proximity to the link.
-
i have a question regarding the "custom auto iso" feature I'm using the latest build @889.
my settings are:
enable custom auto iso-[.]
min shutter speed ----- [1/60s]
UF ----------------------- [1]
ISF ---------------------- [1]
Max ISO HI ------------ [20]
Max ISO Auto ---------- [20]
min ISO ---------------- [10]
Are the settings fixed once i set them?
I'm under the impression my shutter speed should not go below 1/60s
and the iso should never go below 10 or above 200. in low lighting conditions this seems ignored unless the flash is enabled.
Thanks HarpoMa for all the great work Cool
-
I tested it on my camera and discovered a few things.
first, the motion tracking scripts only work when the screen in on. And, there is no way to make the screen stay on for longer than 3 minutes
Second, The dual boot on an 8 gb card works.
third, Overiding the auto focus causes the camera to shut down.
Otherwise it is really nice.
-
I tested it on my camera and discovered a few things.
first, the motion tracking scripts only work when the screen in on.
The sensor is turned off when the display is turned off.
And, there is no way to make the screen stay on for longer than 3 minutes
In a fully functional port, CHDK can override this.
-
The following should be added to stubs_entry_2.S :-
NHSTUB(strrchr,0xFF99F3CC)
-
The following should be added to stubs_entry_2.S :-
NHSTUB(strrchr,0xFF99F3CC)
Thanks, added.
-
Hello everybody,
I apologize if this question has already been answered: is remote shooting supported on the IXUS 100? I have successfully installed the firmware on my camera, and done everything that is written here: http://chdk.wikia.com/wiki/USB_Remote_Cable. (http://chdk.wikia.com/wiki/USB_Remote_Cable.) Still, nothing happens when I operate the remote trigger.
Thanks in advance!
-
I'm not sure why this happens, but every time I compile this with the CHDK Shell, I get this message, I only compile for four cameras and the other three don't generate any kind of error log:
========== C:\CHDK\TRUNK\TRUNK894\BIN\LOGS\ERR-IXUS100_SD780-100C.TXT ==========
boot.c: In function 'taskCreateHook':
boot.c:36: warning: comparison between pointer and integer
boot.c:43: warning: assignment makes integer from pointer without a cast
boot.c: In function 'dumpCF90_SD7802':
boot.c:144: warning: implicit declaration of function 'Fopen_Fut'
boot.c:145: warning: implicit declaration of function 'Fwrite_Fut'
boot.c:146: warning: implicit declaration of function 'Fflush_Fut'
boot.c:147: warning: implicit declaration of function 'Fclose_Fut'
boot.c: In function 'task_blinker':
boot.c:191: warning: implicit declaration of function 'draw_txt_string'
wrappers.c: In function 'OpLog_Get':
wrappers.c:23: warning: implicit declaration of function '_OpLog_Get'
kbd.c: In function 'dumpProps':
kbd.c:216: warning: implicit declaration of function 'Fopen_Fut'
kbd.c:219: warning: implicit declaration of function 'sprintf'
kbd.c:219: warning: incompatible implicit declaration of built-in function 'sprintf'
kbd.c:220: warning: implicit declaration of function 'Fwrite_Fut'
kbd.c:220: warning: implicit declaration of function 'strlen'
kbd.c:220: warning: incompatible implicit declaration of built-in function 'strlen'
kbd.c:222: warning: implicit declaration of function 'Fflush_Fut'
kbd.c:223: warning: implicit declaration of function 'Fclose_Fut'
kbd.c: In function 'dump1900_SD780':
kbd.c:258: warning: incompatible implicit declaration of built-in function 'sprintf'
kbd.c:262: warning: incompatible implicit declaration of built-in function 'sprintf'
kbd.c:267: warning: incompatible implicit declaration of built-in function 'sprintf'
kbd.c: In function 'my_kbd_read_keys':
kbd.c:377: warning: implicit declaration of function 'draw_txt_string'
Any ideas, anyone?
Dan
-
I'm not sure why this happens, but every time I compile this with the CHDK Shell, I get this message, I only compile for four cameras and the other three don't generate any kind of error log:
All of those are warnings in the platform specific parts of the port. Those specific warnings look like they are related to debugging code, nothing serious. Just means there's some cruft that could be cleaned up.
-
I saw here somebody who wants to take dump of 1.00B firmware for IXUS 100 IS...
The only method to do this is blinker interface.
Here it is ready to use diskboot.ini files.
In attached zip archieve:
"blinker orange" is for dumping from 0xFF80000 by Right Side Indicator Light (0xC0220128)
"blinker orange 2" is for dumping from 0xFFA0000 by Right Side Indicator Light (0xC0220128)
"blinker focus" is for dumping from 0xFF80000 by Auto-focus LED (0xC0223030)
"blinker focus 2" is for dumping from 0xFF80000 by Auto-focus LED (0xC0223030)
"java focus" is for dumping from 0xFFC0000 by Auto-focus LED (0xC0223030)
Files made from http://chdk.setepontos.com/index.php?action=dlattach;topic=3547.0;attach=3563 (http://chdk.setepontos.com/index.php?action=dlattach;topic=3547.0;attach=3563) discribed at 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)
Unfortunately I don't have other devices to make full dump.
P.S. It's obsolet message. Read new message http://chdk.setepontos.com/index.php/topic,3995.msg51012.html#msg51012 (http://chdk.setepontos.com/index.php/topic,3995.msg51012.html#msg51012)
-
@reyalp
Thank you, I thought something like that might be the case, but it is nice to have it confirmed.
Dan
-
Can any ixus100 owners comment if this looks like the palette on your camera:
playback http://picasaweb.google.com/reyalp/CHDK#5476894477559640882 (http://picasaweb.google.com/reyalp/CHDK#5476894477559640882)
record http://picasaweb.google.com/reyalp/CHDK#5476894491871949746 (http://picasaweb.google.com/reyalp/CHDK#5476894491871949746)
Some are transparent so they may look different.
-
@reyalp
Yes, that palette looks very much like what is on my sd780, I am running build 890 at the moment.
Dan
-
Are the warnings for the platform or core kbd.c ?
If the platform, have you added #include lolevel.h to your kbd.c and boot.c files ?
-
@Microfunguy
I haven't added anything to anything. I downloaded CHDK Shell, and followed the directions to download the source files. I normally just download the latest builds, but wanted to see if I could follow the instructions well enough to get the Shell running. Like I said, I haven't changed anything.
Dan
-
I made diskboot.bin for dumping using soundcard input described here http://chdk.wikia.com/index.php?title=Special:Outbound&f=Porting_the_CHDK&u=http%3A%2F%2Fdrop.io%2Fchdkdevelopment%2Fasset%2Fby-grand-blinker-rar-rar (http://chdk.wikia.com/index.php?title=Special:Outbound&f=Porting_the_CHDK&u=http%3A%2F%2Fdrop.io%2Fchdkdevelopment%2Fasset%2Fby-grand-blinker-rar-rar)
"audio blink 1" is for dumping 4096 Kbytes from 0xFF800000
"audio blink 2" is for dumping 4096 Kbytes from 0xFFC00000
P.S. It's obsolet message. Read new message http://chdk.setepontos.com/index.php/topic,3995.msg51012.html#msg51012 (http://chdk.setepontos.com/index.php/topic,3995.msg51012.html#msg51012)
-
I saw here somebody who wants to take dump of 1.00B firmware for IXUS 100 IS...
The only method to do this is blinker interface.
Here it is ready to use diskboot.ini files.
In attached zip archieve:
"blinker orange" is for dumping from 0xFF80000 by Right Side Indicator Light (0xC0220128)
"blinker orange 2" is for dumping from 0xFFA0000 by Right Side Indicator Light (0xC0220128)
"blinker focus" is for dumping from 0xFF80000 by Auto-focus LED (0xC0223030)
"blinker focus 2" is for dumping from 0xFF80000 by Auto-focus LED (0xC0223030)
"java focus" is for dumping from 0xFFC0000 by Auto-focus LED (0xC0223030)
Files made from http://chdk.setepontos.com/index.php?action=dlattach;topic=3547.0;attach=3563 (http://chdk.setepontos.com/index.php?action=dlattach;topic=3547.0;attach=3563) discribed at 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)
Unfortunately I don't have other devices to make full dump.
I used blinker focus 2 to make a dump on my 1.00B camera. The others gave regular signal patterns, as did the newer audio blink 1 and 2 versions. The whole dump only took 22 minutes, so I'm not sure what I got. I repeated a couple times, and the waveform looks the same. The raw signal can be found here:
http://drop.io/3rqzwli (http://drop.io/3rqzwli)
Recording was done at 16 bit, 96 kHz on audacity, and it was exported to 8 bit unsigned PCM headerless. I tried adc.exe on it, and it told me sync error and gave me a dump file 214 kb long, which didn't seem promising.
-
Here it is complete solution for dumping firmware that contains directories with diskboot.bin files:
"audio slow 1" dumps 4096 Kbytes starting from 0xFF800000 on slow speed ( 2:20 hours )
"audio slow 2" dumps 4096 Kbytes starting from 0xFFC00000 on slow speed ( 2:20 hours )
After booting one of this diskboot.bin right side indicator light (RSIL) will turn on and flash LED will blink. You mush start recording audio file before RSIL turns off. When all 4096 Kbytes already send RSIL turns on and flash LED turns off. Stop recording audio file. Recording length is about one hour.
Before recording audio file turn of all sound extenders, auto level controls and other sound modifiers if any present in your system. Turn on discretization 96000Hz mono.
Save resulting file in RAW (header less) format using "unsigned 8 bit PCM" into somename.raw file.
Execute "adcslow.exe somename.raw". If there was some errors like "SYNC ERROR" that's right. If it is a lot of errors than you must tune your fotodiode and/or sound system recording.
And finally execute "dec128.exe"
You can execute "adcslow" and "dec128" as many times as you need, resulting file "dump.dat" not overwrites only appends and corrects.
P.S. Using this kit I made dump described in message http://chdk.setepontos.com/index.php/topic,3995.msg51091.html#msg51091 (http://chdk.setepontos.com/index.php/topic,3995.msg51091.html#msg51091)
-
Here it is complete solution for dumping firmware that contains directories with diskboot.bin files:
"audio fast 1" dumps 4096 Kbytes starting from 0xFF800000 on fast speed
"audio fast 2" dumps 4096 Kbytes starting from 0xFFC00000 on fast speed
"audio slow 1" dumps 4096 Kbytes starting from 0xFF800000 on slow speed
"audio slow 2" dumps 4096 Kbytes starting from 0xFFC00000 on slow speed
After booting one of this diskboot.bin right side indicator light (RSIL) will turn on and flash LED will blink. You mush start recording audio file before RSIL turns off. When all 4096 Kbytes already send RSIL turns on and flash LED turns off. Stop recording audio file. Recording length is about one hour.
Before recording audio file turn of all sound extenders, auto level controls and other sound modifiers if any present in your system. Turn on discretization 96000Hz mono.
Save resulting file in RAW (header less) format using "unsigned 8 bit PCM" into somename.raw file.
Execute "adcslow.exe somename.raw" if you used slow diskboot.bin or "adcslow.exe somename.raw" if you used fast diskboot.bin . If there was some errors like "SYNC ERROR" that's right. If it is a lot of errors than you must tune your fotodiode and/or sound system recording or use slow version.
And finally execute "dec.exe"
You can execute "adc" and "dec" as many times as you need, resulting file "dump.dat" not overwrites only appends and corrects.
I have a new blink using audio slow 2. The blink took about 1 hr 45 minutes before lapsing into a continuous string of 11111111 (till the 2 hr 10 minute mark when I turned off the camera), so I chopped it off at 1 hr 46 minutes. adcslow.exe is still giving me continuous sync errors. The whole raw file is about 600 MB. I made a ten-minute sample clip which compressed to 28 mb, available here
http://drop.io/gs8trzy (http://drop.io/gs8trzy)
Once again, 8-bit unsigned PCM. I have no discretization function on my program. But the waveform looks pretty good, except it's upside down compared to the picture found here
http://chdk.wikia.com/wiki/Porting_the_CHDK (http://chdk.wikia.com/wiki/Porting_the_CHDK)
If anyone wants the whole raw, I'll have to split it into a multi-part archive to upload. Better if someone can look at the sample and tell me how to turn this big raw file into a small dump file. I have no programming knowledge, however.
-
I have a new blink using audio slow 2. The blink took about 1 hr 45 minutes before lapsing into a continuous string of 11111111 (till the 2 hr 10 minute mark when I turned off the camera), so I chopped it off at 1 hr 46 minutes. adcslow.exe is still giving me continuous sync errors. The whole raw file is about 600 MB. I made a ten-minute sample clip which compressed to 28 mb, available here
http://drop.io/gs8trzy (http://drop.io/gs8trzy)
You have inversed form of signal in this filel. Try to fix it by reversing fotodiod or something else.
For testing purposes record short samples (about 2-3 minutes) and try how works "adcslow" on them.
Only if it's ok record full sample.
P.S. You can change discretization in audacity by changing project frequency in lower left angle of window.
-
i can not seem to get my usb remote working, have read/followed all instructions. does anyone know if this feature works on this camera yet, or am i doing something wrong?
-
Here it is complete clean dump of IXUS 100 IS / PowerShot SD780 IS firmware 1.00B http://drop.io/ixus100_sd780_100b (http://drop.io/ixus100_sd780_100b)
Could you use it for making CHDK ?
-
Here it is complete clean dump of IXUS 100 IS / PowerShot SD780 IS firmware 1.00B http://drop.io/ixus100_sd780_100b (http://drop.io/ixus100_sd780_100b)
This dump has some leading stuff you should cut off to load it in IDA with the usual addresses.
A firmware dump for DryOS driven cameras normally start like in the attached picture...
*EDIT:
Uploaded this dump - cleaned manually - to the CHDK dumps repository...
Added the Ixus 100 / SD780 1.00B dump from this post (http://chdk.setepontos.com/index.php/topic,3995.msg51091.html#msg51091) (8MB full dump, by bakulev) to the drop.io - chdkdumps2 (http://drop.io/chdkdumps2) backup archive.
http://drop.io/chdkdumps2/asset/ixus100-sd780-100b-7z
Thx to the 'dumpers' & uploaders !
-
I will start a 1.00B this weekend if IDA likes it.
Harpo
-
That'd be great. Still hoping for a 1.00b version!
-
hello to everybody.
Exuse me if I ask something naive but I'm very new at chdk.
I'd like to buy a ixus100is for my nephew and I was wondering if the actual chdk firmware version for the ixus100is supports AEB.
Moreover it seems to me that there are 2 versions of the ixus100is firmware: 1.00c and 1.00b ..and till now there's chdk only for 1.00c. Considering that I'm going to buy a new ixus100is in an italian online store, is it likely I could get a camera with 1.00b firmware version?
many thanks for the replies
galock
-
Hello & welcome, galock !
I'd like to buy a ixus100is for my nephew and I was wondering if the actual chdk firmware version for the ixus100is supports AEB.
AEB is a Canon feature which is natively only available on the more expensive cameras like the G or SX series..
...but any CHDK driven camera can do the same, better, with a much wider Ev range & unlimited settings: either with "bracketing in continuous mode" or with a script !
* http://chdk.wikia.com/wiki/CHDK_User_Manual#Bracketing_in_continuous_mode (http://chdk.wikia.com/wiki/CHDK_User_Manual#Bracketing_in_continuous_mode)
* http://chdk.setepontos.com/index.php/topic,2143.msg19864.html#msg19864 (http://chdk.setepontos.com/index.php/topic,2143.msg19864.html#msg19864)
* http://chdk.setepontos.com/index.php/topic,2972.msg37704.html#msg37704 (http://chdk.setepontos.com/index.php/topic,2972.msg37704.html#msg37704)
Moreover it seems to me that there are 2 versions of the ixus100is firmware: 1.00c and 1.00b ..and till now there's chdk only for 1.00c. Considering that I'm going to buy a new ixus100is in an italian online store, is it likely I could get a camera with 1.00b firmware version?
It may be likely, but nobody knows... maybe you want to check the firmware in the store - just take a SD card with a file named "ver.req" in the root folder with you, maybe you can test the camera before you buy it:
--> http://chdk.wikia.com/wiki/SX100IS#Version_information (http://chdk.wikia.com/wiki/SX100IS#Version_information) (how to check the fw version)
-
Does dual-partitioning work on this camera ?
David
-
Yes, dual partitioning does work.
Dan
-
Yes, dual partitioning does work.
Thanks Dan.
My SDM build must be incorrect or the user is doing something wrong.
David
-
It's possibly the latter, our IT guy used to complain about pebkac... problem exists between keyboard and chair... ;)
-
AEB is a Canon feature which is natively only available on the more expensive cameras like the G or SX series..
...but any CHDK driven camera can do the same, better, with a much wider Ev range & unlimited settings: either with "bracketing in continuous mode" or with a script !
manu thanks for the reply :-) anyway do you confirm me that the actual porting of the ixus 100 supports aeb?
thanks again
-
I do see some changes to the boot code since I first ported to SDM.
Dan, could you do a quick test ?
Temporarily replace DISKBOOT.BIN on the first partition of a dual-partition card with this version :-
http://www.zshare.net/download/769870092d918db8/ (http://www.zshare.net/download/769870092d918db8/)
After it boots (hopefully) just take a couple of photos by directly pressing the shutter button.
Does it work ?
David
-
@Microfunguy
Did as you asked, it booted and took pictures, seems to work, just no splash screen. Sorry for the delay, I was at work.
Dan
-
it booted and took pictures, seems to work
Thanks.
,just no splash screen.
It has been removed to save memory and because of the limitations of record/playback palettes of various cameras (especially recent ones).
Did you see '1.84' in giant letters ?
It does not display on all cameras, must be a boot timing issue.
David
-
@Microfunguy
Yes, I did see the big 1.84, I was just looking thru the menus as well, no issues there either.
Dan
-
@Harpoma,
Just wanted to let you know that parameters changed in scripting now is working, as well. Good job!
Dan
-
@Microfunguy
Yes, I did see the big 1.84, I was just looking thru the menus as well, no issues there either.
Dan
OK, thanks.
Incidentally, in the SDM Script menu you will see four blank lines.
That is where the descriptions from up to ten parameter sets are displayed.
The sets are browsed with the left/right buttons.
See details here :- http://stereo.jpn.org/eng/sdm/ubasic.htm (http://stereo.jpn.org/eng/sdm/ubasic.htm)
-
Is 1.00B in the works? Can't wait to try it out, even some alpha version.
-
Is 1.00B in the works? Can't wait to try it out, even some alpha version.
+1
-
Hi,
I got my new ixus 100 few days ago but can't figure how to store thing for building a user menu, any idea?
And I'm very interested into building a rear curtain function if possible. I don't know lots about programming for CHDK but can do assembler JAVA and C.
Does anyone know how to implement such a function?
I tried prop_case 64 but it is not working with this camera.
Another awsome feature will be to have pseudo manual focus to switch to hyperfocal focus mode, I'm trying to understand a bit more about CHDK and will let people know if I manage to do this with a script.
Thank a lot,
Wallace.
-
Hi all,
Ok I've found thatt half-shutter press saves item in user menu and the zoom lever can organise them which is cool.
Sadly the focus distance makes my camera crash...
The AEB works perfectly :)
Does anyone know what is the probem on focus distance override?
as I sais before I can code some things but don't really know where to start looking for...
Peace,
W.
-
I guess there's been some recent activity here, but I'm a new SD780 owner and having a hard time finding any clear documentation on using CHDK with this camera.
I have the energy and background as a tech writer to perhaps put together some clear, concise documentation, but I can't find the information myself.
I know people are using the software with this model successfully, but where do they find the instructions?
The standard instuctions fail because the SD780 doesn't have the 'shortcut' button, and the DISP button is used instead to access ALT menu where the CHDK settings reside, but I can't reliably control the camera and usually the screen ends up going black and I'm lost.
Where do I start?
-
Aside from the general CHDK documentation i think this thread is pretty much it. You can always ask HarpoMa, the person that is performing the port, questions directly.
-
What is the recommended way to create the bad pixel file for the SD780? The show_bad_b app does not support the SD780 and I cannot seem to run the script on the camera to generate the file. Can someone please provide the instruction necessary to create the file? Thanks,
-
What is the recommended way to create the bad pixel file for the SD780? The show_bad_b app does not support the SD780 and I cannot seem to run the script on the camera to generate the file. Can someone please provide the instruction necessary to create the file? Thanks,
You need to run the script. If you tell us what happens when you try to run it, maybe someone can help you.
The camera must be in picture taking mode to run the script.
-
When I navigate to the test directory that contains the badpixel.lua and select it. I then get another page with several options, but I cannot find anything that actually looks like a way to execute the script. I'm sure this is very basic, but I do not see the way to run the script.
-
You need to select the script, leave the menu (but stay in CHDK alt mode), and then press the shutter to run the script.
-
Hi HarpoMa - first, thanks for your incredible work in getting this running on the 100IS! Second, I have a small suggestion/request. I am finding the file browser very hard to read. I understand the colours might be hard-coded into core/gui_fselect.c. Not sure if this is a CHDK-wide default or specific to this camera, but would it be possible to use some combination with more foreground/background contrast in the next release? Otherwise I might try recompiling it myself.
-
On holiday ATM but when I return I will add that to my long list of required fixes.
Harpo
-
Hello HarpoMa,
I too would love to see a 1.00b Port for the SD780is. The work you did for the 1.00c and the features look completely incredible. Are the b and c firmware dumps very dissimilar?
skywagon
-
Hello HarpoMa,
I too would love to see a 1.00b Port for the SD780is. The work you did for the 1.00c and the features look completely incredible. Are the b and c firmware dumps very dissimilar?
skywagon
I just popped back in to see if there was any update on 1.00b, but I guess not.
Is that just not going to happen?
-
Hi all,
i'm a very newbie and i read few post yet; anyway...
I loaded CHDK on my Powershot Sd780/Ixus100is.
I notice that:
1) CRW files saved (18.653.760 byte each, or 17,7mb) are empty, i mean blank, no pixel, no image, then picture browsers say 0.00 pixel and show black screen.
2) no able to run the script "badpixel.lua" needed for saving in DNG.
- I loaded CHDK through CardTricks on 4gb and 128mb card formatted in FAT16 but it happens the same.
- Version of my camera firmware is 100c (GM 1.00c), as requested.
- Version of CHDK is 0.9.9-926 ("ixus100_sd780-100c-0.9.9-926-full_BETA.zip").
What have i done wrong?
Thank you in advance for any advice you can give me,
Leo
(PS. congrats to guys that made this great device!)
-
1) CRW files saved (18.653.760 byte each, or 17,7mb) are empty, i mean blank, no pixel, no image, then picture browsers say 0.00 pixel and show black screen.
To view CHDK RAW images the viewer must support them, most viewers/apps do not work directly with CHDK RAWs...
--> Read the sticky threads in the RAW Shooting and Processing (http://chdk.setepontos.com/index.php/board,15.0.html) section
--> Try other programs, e.g. DCRAW-based ones; maybe XNView, RawTherapee or Picasa can open the SD780's RAWs.
2) no able to run the script "badpixel.lua" needed for saving in DNG.
You should be a bit more precise - what does not work, do you get an error message ?
-
Hello fe50, thank you so much for reply me.
I read various wiki stuff and posts related to my topics in the section you linked to me, then i tried to apply suggestions but nothing fixed...
Now i am just able to see my empty raw files also in camera as "not identified images".
I did set RAW as IMG_xxx.CR2, CRW_xxx.CRW and other combinations, setting even in and out jpg directory.
Then i tested DNG4PS2, FastStone, XnView, Picasa and maybe other browsers: no way; always the same pictures (almost 18mb each) with no pixels.
Moreover i did follow your post about running the badpixel script but the only result is to wait a while and notice to having shoot twice (an overexposed jpg and a blank/black CR2); i figure that plugin for DNG doesn't load until the basic RAW will work correctly (by my sensation).
Do you think i can do something more?
Many thanks - Leo
(ps. i hope to be enough clear despite english is not my language)
-
Hello,
I am trying to get CHDK to work on my 4gb memory card. The files load onto the card just fine and the camera recognizes the firmware (or at least the splash image shows up), but the lens does not zoom out and the camera sits in the image review mode with "No image" on screen. Any ideas on what I am doing wrong?
I'm currently using OS X 10.6.4 and used SDMInst with the latest build.
EDIT: After tinkering around I discovered that CHDK is indeed working, as I was able to navigate the menus, yet the camera refuses to enter Record mode.
-
-
Hi firequall. In reply to your question, on my SD780IS camera with CHDK after you turn the camera on with the power button it goes into review mode. You then have to press the shutter button down to get the camera to pop out the lens and switch to record mode.
Andrew
Hello,
I am trying to get CHDK to work on my 4gb memory card. The files load onto the card just fine and the camera recognizes the firmware (or at least the splash image shows up), but the lens does not zoom out and the camera sits in the image review mode with "No image" on screen. Any ideas on what I am doing wrong?
I'm currently using OS X 10.6.4 and used SDMInst with the latest build.
EDIT: After tinkering around I discovered that CHDK is indeed working, as I was able to navigate the menus, yet the camera refuses to enter Record mode.
-
Hi folks,
I don't know if this was mentioned before, but I get some strange behaviour.
When CHDK is loaded and I try to take a picture the camera shuts down sometimes. No picture is taken.
Other CHDK stuff seems to work properly, like intervalometer scripts, which take photos without shutting down.
Is this a bug or am I doing something wrong?
-
http://www.andrewhazelden.com/blog/2010/09/calibrating-canon-sd780is-chdk-raw-dng-images-using-an-adobe-camera-profile/ (http://www.andrewhazelden.com/blog/2010/09/calibrating-canon-sd780is-chdk-raw-dng-images-using-an-adobe-camera-profile/)
I just created a custom Adobe RAW Camera Profile for Canon Powershot SD780IS and IXUS 100 IS cameras running the CHDK Beta. This works with Adobe Photoshop and Adobe Lightroom on Mac OS X and Windows. This camera profile works with the DNG images saved by the CHDK Beta.
In the past I was scared away from doing much with CHDK's DNG images due to the weird color cast that can be seen if you use a program like Preview on Mac OS X to view DNG images. With the new color profile and either Adobe Photoshop or Adobe Lightroom you can get fast and consistent results from your DNG files.
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fwww.andrewhazelden.com%2Fblog%2Fwp-content%2Fuploads%2F2010%2F09%2F3.custom_profile_in_lightroom-560x315.png&hash=89a7109508aada24d7df75756bffdd8d)
I created the custom profile using the Adobe Labs DNG Camera Profile program and calibrated the profile by photographing a color test chart and did extensive manual tweaking. This is my first time using the DNG Camera Profile program to create a custom Camera Profile and so I am interested in any feedback, suggestions, tips, etc... you may have to offer.
Andrew
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fwww.andrewhazelden.com%2Fblog%2Fwp-content%2Fuploads%2F2010%2F09%2F5.DNG-Profile-Editor-560x270.png&hash=328be7b4198dc41b9b267d64bc2c47ac)
-
Andrew, nice work.
Have you seen my call to add DNG profiles to the CHDK Wiki (http://chdk.setepontos.com/index.php/topic,5576.msg54656.html#msg54656)?
If you've got a good profile, very soon we should be able to get CHDK to embed it in DNGs directly in the camera.
-
--edit -- I guess colour profiles != colour matrix? I had confused the two.
Harpo
-
The DNG profiles (I try to avoid the term "colour profiles" to avoid confusion with ICC profiles) contain two colour matrices, plus a bunch more adjustments.
So the colour matrices can be regarded as extremely simplified profiles.
-
Hi folks,
I don't know if this was mentioned before, but I get some strange behaviour.
When CHDK is loaded and I try to take a picture the camera shuts down sometimes. No picture is taken.
Other CHDK stuff seems to work properly, like intervalometer scripts, which take photos without shutting down.
Is this a bug or am I doing something wrong?
I think you turned on zebra bars which don't work right now with the BETA build of CHDK for the SD780IS.
Try this fix:
1. Turn the camera on and wait for the camera to enter review mode.
2. Tap the DISP button to enter the ALT mode.
3. Bring up the CHDK Menu and select Zebra Parameters. Make sure the option Draw Zebra is de-selected.
4. Exit the CHDK menus and turn off the ALT mode.
5. From the review mode screen, press the shutter button to switch to record mode.
The LCD screen should show a live preview and the CHDK should work normally.
Andrew
-
http://www.andrewhazelden.com/blog/2010/09/calibrating-canon-sd780is-chdk-raw-dng-images-using-an-adobe-camera-profile/ (http://www.andrewhazelden.com/blog/2010/09/calibrating-canon-sd780is-chdk-raw-dng-images-using-an-adobe-camera-profile/)
Thanks so much for putting info about the SD780 online. I have a couple of posts on an SD780 thread in the RAW forum where I report my attempts to figure out parameters for distortion and CA correction for this camera. I will check out your blog with great interest.
Colour management is a mystery to me. I only use Linux so have no access to Adobe apps. Naively running the DNG files through the free dcraw command line converter appears to give me results quite similar to the Canon JPEGs, although I have not experimented very much (and also have crappy colour vision).
Last week I tried out the camera in its underwater housing. No CHDK as I figured Canon's UW setting was the best bet. In fact the pictures out of camera were quite disappointing - combination of turbidity and sunlight I think. They came up better with the Imagemagick 'enrich' filter, but I wish I had the DNGs to work with.
-
I've tried applying the same OSD / zebra fixes to this camera as d10, sd990, ixus95.
I'm not sure if this will work, since the bitmap buffer is claimed to be 960px, but anyway, here's a test build:
http://drop.io/reyalp_chdk/asset/ixus100-sd780-100c-0-9-9-osdtest-1-zip (http://drop.io/reyalp_chdk/asset/ixus100-sd780-100c-0-9-9-osdtest-1-zip)
and diff if anyone is interested:
http://drop.io/reyalp_chdk/asset/ixus100-osdtest-1-patch (http://drop.io/reyalp_chdk/asset/ixus100-osdtest-1-patch)
-
I've tried applying the same OSD / zebra fixes to this camera as d10, sd990, ixus95.
I'm not sure if this will work, since the bitmap buffer is claimed to be 960px, but anyway, here's a test build:
http://drop.io/reyalp_chdk/asset/ixus100-sd780-100c-0-9-9-osdtest-1-zip (http://drop.io/reyalp_chdk/asset/ixus100-sd780-100c-0-9-9-osdtest-1-zip)
and diff if anyone is interested:
http://drop.io/reyalp_chdk/asset/ixus100-osdtest-1-patch (http://drop.io/reyalp_chdk/asset/ixus100-osdtest-1-patch)
I just downloaded your test build and tried it on my SD780 IS camera. The zebra bar feature still causes the camera to hang. On the upside though, the CHDK startup logo doesn't look squashed anymore and the menu text and icons appear larger and easier to read.
-
I've tried applying the same OSD / zebra fixes to this camera as d10, sd990, ixus95.
I'm not sure if this will work, since the bitmap buffer is claimed to be 960px, but anyway, here's a test build:
http://drop.io/reyalp_chdk/asset/ixus100-sd780-100c-0-9-9-osdtest-1-zip (http://drop.io/reyalp_chdk/asset/ixus100-sd780-100c-0-9-9-osdtest-1-zip)
and diff if anyone is interested:
http://drop.io/reyalp_chdk/asset/ixus100-osdtest-1-patch (http://drop.io/reyalp_chdk/asset/ixus100-osdtest-1-patch)
I just downloaded your test build and tried it on my SD780 IS camera. The zebra bar feature still causes the camera to hang. On the upside though, the CHDK startup logo doesn't look squashed anymore and the menu text and icons appear larger and easier to read.
That may be a free memory issue, can you check what the memory info item in the chdk misc menu shows ?
You could try edge overlay too. If the edges line up, then the fix is good regardless of zebra (but it could run out of memory the same)
-
The new edge overlay code works well and the edges line up with the photo properly. Also, the new build has 130774 bytes of free memory at startup. After taking a photo with edge overlays turned on I have 98344 bytes free.
The old build had 126888 bytes of free memory.
New Edge Overlays:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fwww.andrewhazelden.com%2Ffiles%2F2010%2FSeptember%2FCHDK_0.9.9%2Fnew_edge_overlays.jpg&hash=b2e451b79c4dfdd0da97c84b6bdc5192)
Old Edge Overlays:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fwww.andrewhazelden.com%2Ffiles%2F2010%2FSeptember%2FCHDK_0.9.9%2Fold_edge_overlays.jpg&hash=bbf96de739ad40f024b25f8fa7b0ef7e)
-
My experiences with edge overlay is the same as andrewhazelden's.
Free memory for me after startup: 213632 bytes
After enabling edge overlay, and displaying it once on the screen: 181168 bytes
Btw, do you see any chance that the following will be fixed for this camera:
"switch from manual to Auto mode and back is not working. I need to turn off the camera, switch to auto mode, and turn back on."
This is the only thing keeps me run CHDK with the update firmware option, and not as boot.
-
Great, from edge overlay we can say that screen layout is correct.
The memory size difference may be because I have games and calender disabled in my build (but I'm using the original windows toolchain which makes bigger binaries). 130k is fairly marginal for zebra... it is enough for the buffers, but then the camera will try to allocate some for something else, fail, and shut down with an assert. We can try sx20 style, which will be a bit uglier but may work...
@benoe:
I have no idea about that, sorry.
edit:
test build http://drop.io/reyalp_chdk/asset/ixus100-sd780-100c-0-9-9-osdtest-2-zip (http://drop.io/reyalp_chdk/asset/ixus100-sd780-100c-0-9-9-osdtest-2-zip)
Only difference is adding
#define CAM_ZEBRA_NOBUF 1
-
edit:
test build http://drop.io/reyalp_chdk/asset/ixus100-sd780-100c-0-9-9-osdtest-2-zip (http://drop.io/reyalp_chdk/asset/ixus100-sd780-100c-0-9-9-osdtest-2-zip)
Only difference is adding
#define CAM_ZEBRA_NOBUF 1
The different zebra bar modes seem to work fine on my camera now with 0.9.9-osdtest-2 build. On startup the camera has 133544 bytes free. After taking a photo with Zebra bars on, the camera has 99416 bytes free.
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fwww.andrewhazelden.com%2Ffiles%2F2010%2FSeptember%2FCHDK_0.9.9%2Fzebra_bars_work.jpg&hash=944489eb029d088bb2b1fb2c1799de2b)
-
I'm using the original windows toolchain which makes bigger binaries
That is interesting.
So, what is the recommended setup for creating smaller binaries ?
David
-
So, what is the recommended setup for creating smaller binaries ?
I believe the state of art in terms of size is a gcc 4.5.x toolchain. I'm still using gcc 3 too myself, tried to build a 4.5.x a while back but failed miserably (to build gcc on ubuntu karmic, that is...).
For windows there are binaries of gcc 4.5.1 available at http://drop.io/gcc_for_chdkshell (http://drop.io/gcc_for_chdkshell).
-
For windows there are binaries of gcc 4.5.1 available at http://drop.io/gcc_for_chdkshell (http://drop.io/gcc_for_chdkshell).
Thanks.
I will think about it but I hate this compiling 'business'.
It can only end in tears !
In the 'early' days my compilations suddenly failed simply because I had installed a Logitech webcam.
Luckily, GrAnd reported the solution that was posted on a Russian forum.
-
I believe the state of art in terms of size is a gcc 4.5.x toolchain. I'm still using gcc 3 too myself, tried to build a 4.5.x a while back but failed miserably (to build gcc on ubuntu karmic, that is...).
For windows there are binaries of gcc 4.5.1 available at http://drop.io/gcc_for_chdkshell (http://drop.io/gcc_for_chdkshell).
The international Autobuild Server runs gcc 4.4.3 under linux (Debian).
-
The different zebra bar modes seem to work fine on my camera now with 0.9.9-osdtest-2 build. On startup the camera has 133544 bytes free. After taking a photo with Zebra bars on, the camera has 99416 bytes free.
Ok, I'll check in this version. It's normal for some memory to be consumed by taking the first time you take a photo, even if zebra is disabled.
-
... I believe the state of art in terms of size is a gcc 4.5.x toolchain ...
Just to warn you guys that currently GCC 4.5.1 (at least the one I built) fails on 5 (or 4 if
not counting duplicates) out of the current 116 firmwares: A2000-100C, G11_100F, G11_100J,
G11_100K (= dup of 100J) and IXUS100_SD780-100C. Interestingly, G11-100L compiles without warnings.
I'm fairly sure this is due to more rigid error checking from the linker. I also PM'ed ultimA for a
second opinion, he was the first to report he got 4.5.1 to compile CHDK successfully:
http://chdk.setepontos.com/index.php/topic,4348.msg53187.html#msg53187 (http://chdk.setepontos.com/index.php/topic,4348.msg53187.html#msg53187), but no reply so far ...
wim
-
Just to warn you guys
I am even more convinced now not to bother.
As a matter of interest, do you know how much smaller the smallest build is compared with the largest ?
Anything substantial like 25% smaller ?
-
Anything substantial like 25% smaller ?
nowhere near, about 17-18 kB for 3.4.6 -> 4.5.1
about 14.5 kB for 3.4.6 -> 4.4.0
Savings tend to be a fixed amount of kB, so % will vary, I'd say maybe 6 - 7 %,
at the expense of at least double the compile time.
hth,
wim
-
any chance the usb remote can be applied to this build as it works on sdm build thanks
-
USB remote for ixus100 is also available in CHDK-DE.
Download binaries (http://www.wirklemms.de/chdk/forum/autobuild.php)
Changeset (http://tools.assembla.com/chdkde/changeset/360) source code
-
Hello,
I'm trying to do my SD card self bootable, but when I go to the CHDK menu and I press the option "make sd card bootable..." nothing happens.
Anyway, after pressing the option, as I didn't know if it worked, I extracted the card, locked it and try to power on the camera with it and gives me a card error.
What am I doing wrong?
Mi SD card es a SDHC of 8gb and is in FAT 32.
-
Hello & welcome, DFA !
I'm trying to do my SD card self bootable, but when I go to the CHDK menu and I press the option "make sd card bootable..." nothing happens.
...
Mi SD card es a SDHC of 8gb and is in FAT 32.
The CHDK autostart feature (with a CHDK-bootable card) only work with FAT12 / FAT16 partitions.
You may use your 8GB part with the default single partition and start CHDK manually,
if you want to use the CHDK autostart method you have to partition your card...
* http://chdk.wikia.com/wiki/Bootable_SD_card (http://chdk.wikia.com/wiki/Bootable_SD_card)
* http://chdk.setepontos.com/index.php/topic,2468.msg30911.html#msg30911 (http://chdk.setepontos.com/index.php/topic,2468.msg30911.html#msg30911)
* http://chdk.setepontos.com/index.php/topic,2468.msg36022.html#msg36022 (http://chdk.setepontos.com/index.php/topic,2468.msg36022.html#msg36022)
* http://chdk.setepontos.com/index.php/topic,3910.msg36763.html#msg36763 (http://chdk.setepontos.com/index.php/topic,3910.msg36763.html#msg36763)
-
Thanks fe50.
I read all this, and I see that I have to make 2 partitions in my card, one small with FAT16, and other bigger with FAT32.
But after reading that windows has problems to read 2 partitions in a SD Card (is that true?) and I have to swap partitions every time I want to transfer images to my PC...
I'm thinking in:
1. buying a 4GB card to format in FAT16 and work with it when I want CHDK.
It will work in this way in my IXUS 100? (Because the default card format of this camera is FAT32)
Is there any problem in working in FAT16 with the hole 4gb card? in speed or something?
2. Or make the two partitions, one small in FAT16 and the bigger in FAT32.
In this way, Do I have to swap the partitions to read the card from a card reader or can I use the camera plugged to transfer the images, right?
What people do?
-
1. buying a 4GB card to format in FAT16 and work with it when I want CHDK.
It will work in this way in my IXUS 100? (Because the default card format of this camera is FAT32)
Yes, but you have to format the card with a card reader to use FAT16 (the camera will format cards > 2GB with FAT32 by default).
Is there any problem in working in FAT16 with the hole 4gb card? in speed or something?
No, no problems/issues.
2. Or make the two partitions, one small in FAT16 and the bigger in FAT32.
In this way, Do I have to swap the partitions to read the card from a card reader or can I use the camera plugged to transfer the images, right?
You can transfer the images as usual with the USB cable (note: you may need to disable the CHDK remote feature in the CHDK Remote Parameter" menu (http://chdk.wikia.com/wiki/CHDK_User_Manual#Remote_Parameters)),
you can also swap the partitions from the CHDK menu (http://chdk.wikia.com/wiki/CHDK_User_Manual#Swap_partitions (http://chdk.wikia.com/wiki/CHDK_User_Manual#Swap_partitions))...
-
A question about CHDK on video.
1. The quality can be increased to a 100. Has anyone seen an increase in bitrate due to this, or shot a resolution chart to confirm that it works ?
2. Is there a way to force aperture priority mode in video - so we can set the shutter to 1/60 while shooting, or even use fully manual controls in video ?
3. Any chance that we can get other framerates i.e. 25P, 50P, 60P ?
-
There is a reference in this forum to someone who did tests.
Conclusion was they made no difference, just increased file size.
JOhn Hart on the Yahoo SDM Group reported something similar.
You cannot set arbitrary framerates.
Most important for you, 57 cameras (or even two) cannot be accurately synchronised.
-
There is a reference in this forum to someone who did tests.
Here it is :-
http://chdk.setepontos.com/index.php?topic=520.msg54487#msg54487 (http://chdk.setepontos.com/index.php?topic=520.msg54487#msg54487)
-
I've been using CHDK on my SD780 for quite a while, and have been mostly pleased with everything it's been able to do for me.
However, after testing CHDK on at least two, probably three SD780s, I haven't yet found one able to use CHDK's manual focus setting. When the subject distance value is set, it used to crash the camera, but now it simply focuses as it would normally. I've tried this with Subject Distance bracketing, as well as simply setting the subject distance, but I haven't yet captured a picture with CHDK and this camera with the focus set as I wanted it.
This really is annoying...is something being done about it, am I the only one experiencing this problem, or is this new to you people?
!Noah!
-
I have been using it for two months or so and so far its really great.
I have some problems though
- I can't get an exposure past 1/1500 or 15 seconds
- I can't get auto boot to work (Some help on this would be much appreciated)
Is there a max card size for auto boot I have a 4GB and a 16GB, both work with CDHK
-
-
Hello,
I have the same issue as Flutterbudget.
When I use focusing on my IXUS 100 IS camera crashed.
I've tried reinstall CHDK but issue wasn't fixed.
Most of all other features works fine.
Is somebody has this issue? / How it can be fixed?
-
-
-
Ok I've just recently tried CHDK out after finding out I can use >4GB after all with the partition swap method, looks to be pretty handy for those of us with a IXUS100.
Id like a little help though, so I should say Im a complete novice really when it comes to cameras but tech minded.
Ok so a few questions if anyone could answer them for me :) :
1) How do I change shooting modes when not in playback mode?
2) With "Video Mode" set to quality every attempt has resulted in a 2 second vid(stops recording by itself), is there something I'm missing or is it a known issue?
--"Default" seems to work fine.
3) Is there anything I can do to reduce noise on indoor videos? Im not expecting crystal clear but I seem to get alot more noise on mine than most other indoor examples I've seen on this camera, could my particular camera be getting hot too quick or something?
--Daytime/outdoor videos look as good as I expected(again from examples I've seen elsewhere).
-
-
-
-
I'm very interested in testing and having a working DHCK port for my camera!
I actually got a big chunk of the porting work done last week. Busy working on another camera right now but once I get a break, I'll finish up the SD780 fw 100b - some time this month most likely.
-
Awesome!
-
I'm very interested in testing and having a working DHCK port for my camera!
I actually got a big chunk of the porting work done last week. Busy working on another camera right now but once I get a break, I'll finish up the SD780 fw 100b - some time this month most likely.
I just got my SD780 IS and I just found out that it has 1.00B firmware :(
I shouldve checked the firmware version first, but it was on clearance so too hard to pass.
I dont know what is involved in the testing end, but Ill be happy to test it out if someone can get the port for 1.00B going. Coming from DSLR, only having JPEGs is like... i dunno how to explain it.
-
Coming from DSLR, only having JPEGs is like... i dunno how to explain it.
One way to help explain it might be to search the various threads in this forum about the limitations of CHDK RAW for P&S cameras. If you are use to a DSLR, you might not realize how much post processing is needed for CHDK RAW files, especially "wide angle" shots.
-
@dagokun & voodoolady & Cloud : Okay - here's the first attempt at port to the 1.00b firmware for the IXUS100_SD780.
CHDK IXUS100_SD780 Beta 1 (http://www.box.net/shared/1630sm7j2xmjv3ckki4e)
Its basically at the point where, if I actually owned a SD780, I would load it on the camera to see what it does.
At a minimum, I put code at the start of the boot code to turn on the Auto Focus lamp. If things don't work for you, does the AF lamp come on briefly at least ?
NOTE : "SD card lock" boot method only.
-
It works, the autofocus lamp turns on! (note to testers, don't turn the camera on with the autofocus lamp aiming directly to your eyes! Ouch!)
I tested turning the camera on with the PLAY button and the ON/OFF buton, and in the 3 shooting modes (auto, program and video), 6 combinations total. Every time, the only thing that happens is that the autofocus lamp turns on. No reaction on the other LEDs or the LCD. The camera freezes with the lamp on, and must remove battery to reset.
Like you said, the only way to run the code it to have the card bootable and locked. Otherwise, the "upgrade firmware" option is abscent.
-
Beta 2 - found an address jump wrong in boot.c. Let's see how this works ?
http://www.box.net/shared/x3q038ygu3fzlcf5qu55 (http://www.box.net/shared/x3q038ygu3fzlcf5qu55)
-
Beta 2 bahaves just like beta 1
-
Beta 2 bahaves just like beta 1.
Its now time to do this the hard way so here's a version with almost everything turned off (for now).
IXUS100-SD780 fw 1.00b Beta 3 (http://www.box.net/shared/o6yxpdhsdk4y52hx316f)
The yellow LED beside the viewfinder should blink rapidly at least once and hopefully several times. Please let me know how many times it blinks ? (or if the blinking is too fast to count)
-
It worked. It blinks very fast, but using another camera to record it and playing it frame by frame I can see it blinking 3 times.
-
It worked. It blinks very fast, but using another camera to record it and playing it frame by frame I can see it blinking 3 times.
Did it blink 3 times and then go to the regular Canon startup / menu stuff (i.e. camera works like it did before). Did you see the CHDK logo for a few seconds if so ?
UPDATE : version with slower blink - please confirm the 3 blinks as its hard to see how that can happen in the code http://www.box.net/shared/yjj40591yz19bzppqum8 (http://www.box.net/shared/yjj40591yz19bzppqum8)
-
Blinking about 10x slower, so it definitely blinks 3 times, with autofocus lamp on, then camera stays frozen just like before. No other activity on LCD or any other LEDs.
-
Blinking about 10x slower, so it definitely blinks 3 times, with autofocus lamp on, then camera stays frozen just like before. No other activity on LCD or any other LEDs.
Great - that helps a lot. I'll do some digging - doing this without a camera to test with is painful. As long as I can feed you updates to test, I'll keep going. This is not my first time through this by any means.
-
Beta 5 : this version should blink the AF led and yellow LED once and then boot the normal Canon software.
http://www.box.net/shared/fq14zf59yorv9g3cq1z4 (http://www.box.net/shared/fq14zf59yorv9g3cq1z4)
UPDATE : voodoolady and I worked on this via IRC with no luck. Time for some sleep and a fresh look tomorrrow.
-
Beta 6 : Found a couple of small things that might make a difference and changed the LED pattern.
SD780-1.00b beta 6 (http://www.box.net/shared/q5zc8bo590xlz9ndk8s2)
-
Beta 7 : Rebuilt against latest trunk update - might have been some experimental stuff from my other projects interfering with the previous builds? Changed the LED pattern again to help isolate the problem
SD780-1.00b beta 7 (http://www.box.net/shared/z436j55y6spc7avk2et7)
-
Beta 8 : I'm afraid I might not be able to make this work. So I've taken out all the LED blinking code and triple checked that the boot.c task is the same as the 1.00c code (except where addresses have shifted). I'm out of ideas at this point if this does not boot.
Here's my last try for now - let me know if it works ?
IXUS100-SD780 fw 1.00b Beta 8 (http://www.box.net/shared/85el3r7isfqfoph6gg44)
-
Beta 8a : same code but with boot() module following current coding convention rather than the older style used with the 1.00C port. I put the AF Led blink back at the start to so that you know it at least loads.
IXUS100-SD780 fw 1.00b beta 8a (http://www.box.net/shared/fk1nyqfp33yguqsph2vu)
Frankly, I need more help here - at least 3 people have been downloading these beta releases but only voodoolady has been helping out by providing feedback.
-
Hey, good job, Waterwings!! This time you've done it, beta 8 boots into CHDK! You posted the beta 8a version while I was writing my test results, I'll test them now, but here's what I got with beta 8.
Camera boots normally with chdk spalsh screen. All the menus are there, but with a constant message on the screen (message from the normal firmware, behind the CHDK menu) of "Memory card error". What I tested so far is:
On playback mode, even though there are pictures on the mem card, the camera doesn't display any of them, just a black screen with the mentioned error message.
If I boot on record mode, the screen starts black with the error message, and the lens won't extend until I half-press the shutter button. Then I have everything you would expect from a camera with chdk (normal menu, alt menu, button, zoom, etc behavior), but with the error message on the top portion of the display, and the inability to take pictures.
So I tried downloading any script that would take pictures to test how writing on the card would be. Whenever I select "Load script from file...", the Script selection window is broken somehow. It's like it's transparent, as in I can see the script options of the previous menu behind the new window's frame. Thus I can't select any file (even when pressing down and select a few times, hoping the file selection was still there, just not visible). Even when renaming the new script to "default.bas" the camera would still just display the default script message.
Then I changed any value on the settings to see if it would stick. I checked the "Clear videoparams on Start" box, but that setting returned to the default (unchecked) value on a new boot. Lastly I tried removing the SD card, unlocking it and putting it back in (without shutting the camera off), but it didn't change anything.
-
Camera boots normally with chdk spalsh screen. All the menus are there, but with a constant message on the screen (message from the normal firmware, behind the CHDK menu) of "Memory card error". What I tested so far is:
Does the CHDK logo appear right away when the LCD lights up or after two or three seconds ?
-
Actually there is no logo, just a red rectangle with the CHDK version, build date and camera model. It appears less than 0,5 (half) second after the LCD lights up, so I would call that "right away".
-
Actually there is no logo, just a red rectangle with the CHDK version, build date and camera model. It appears less than 0,5 (half) second after the LCD lights up, so I would call that "right away".
okay - we can work on the logo later - did the 8A version also work ?
-
Beta 9 : cleaned up the FAT32 code inherited from the 1.00c. Hopefully that will fix the invalid SD card problem. The logo is stored on the card, so if CHDK can't read the card then you won't see the round logo - just the text box (which is generated in the code)
IXUS100-SD780 firmware 1.00B - beta 9 (http://www.box.net/shared/vg8vqii09xl2dx19fp8k)
-
Beta9 did fix some of the reading and writing to the card. The logo shows up on splashscreen, and also the icons on alt menu (they weren't present on beta8). No more "card error" message, you can see the pictures already on the SD card. Changes to photo and video params are recorded and kept if I reboot the camera.
The problem now is that whenever I try to take a picture (normally or through a script) or record video, the camera dies (shuts everything off with the lens extended). It's not necessary to remove the battery though, you can turn it back on normally.
-
The problem now is that whenever I try to take a picture (normally or through a script) or record video, the camera dies (shuts everything off with the lens extended). It's not necessary to remove the battery though, you can turn it back on normally.
Huge progress !!! I was pretty much ready to give up on this. The shooting thing is a new problem - or rather a problem we could not see because we could not boot at all. I'm out of time right now but I'll look into it at some point this week.
Update : I've attached the source contents of the platform/ixus100_sd780/sub/100b directory here in case I don't get back to this and somebody else wants to look at it.
-
Beta 10 : Found a few minutes to clean up capt_seq.c. This should work a lot better.
IXUS100-SD780 fw 1.00B Beta 10 (http://www.box.net/shared/o2ltzm5bhqt9mi84lcpo)
-
I've been away from home most of this sunday, so I haven't had the chance to test it thoroughly, but what I can say now is that the pictures are being properly recorded to the SD card :) ! Hurray!
Now the bugs: It doesn't matter if I turn the camera on with the playback or the on/off button, it always starts on playback mode. That's probably normal CHDK behavior, but I haven't used it in such a while that I can't be sure.
The only real issue I found so far is a strange behavior when I enter record mode (half-pressing shutter button). When I enter record mode and the record switch is set to full automatic, I can't change it to Program or Video mode. If I enter record mode and the switch is set to Program , I can switch between that and Video, but not to full automatic. And if I enter record mode with the switch set to Video, I can only alternate between Video and Program, but not Full Auto.
-
The Auto mode switching bug also exists with the 1.00C CHDK build for the SD780 IS.
The only real issue I found so far is a strange behavior when I enter record mode (half-pressing shutter button). When I enter record mode and the record switch is set to full automatic, I can't change it to Program or Video mode. If I enter record mode and the switch is set to Program , I can switch between that and Video, but not to full automatic. And if I enter record mode with the switch set to Video, I can only alternate between Video and Program, but not Full Auto.
-
Now the bugs: It doesn't matter if I turn the camera on with the playback or the on/off button, it always starts on playback mode. That's probably normal CHDK behavior, but I haven't used it in such a while that I can't be sure.
Try holding the on/off button down for more than 1 second - standard CHDK behaviour is for it to enter shoot mode at that point.
The only real issue I found so far is a strange behavior when I enter record mode (half-pressing shutter button). When I enter record mode and the record switch is set to full automatic, I can't change it to Program or Video mode. If I enter record mode and the switch is set to Program , I can switch between that and Video, but not to full automatic. And if I enter record mode with the switch set to Video, I can only alternate between Video and Program, but not Full Auto.
Sounds like an issue with the SD780 port in general. Sorry, but at this point, I'm not going to tackle that.
-
-
Frankly, I need more help here - at least 3 people have been downloading these beta releases but only voodoolady has been helping out by providing feedback.
Sorry waterwingz, my computer has been down for a while. I will download the Beta 10 and see what i can find from there. Im having a small problem trying to format and make the card bootable as i have a 16GB card... I guess ill have to make a 4 GB partition or load it manually to test.
I have heard about the multi partition on CHDK, but has that been implemented already? If so i can check on that too.
Anyways, i will report back again. Thank you waterwingz for all the effort and helping us with 1.00B
-
Sorry waterwingz, my computer has been down for a while. I will download the Beta 10 and see what i can find from there. Im having a small problem trying to format and make the card bootable as i have a 16GB card... I guess ill have to make a 4 GB partition or load it manually to test.
I have heard about the multi partition on CHDK, but has that been implemented already? If so i can check on that too.
Anyways, i will report back again. Thank you waterwingz for all the effort and helping us with 1.00B
Take a look here : http://chdk.wikia.com/wiki/Bootable_SD_card (http://chdk.wikia.com/wiki/Bootable_SD_card). Follow the instructions for sdminste.exe. http://stereo.jpn.org/eng/sdm/quick.htm (http://stereo.jpn.org/eng/sdm/quick.htm)
-
Thank you for the links waterwingz.
I followed the instructions and got the dual partition working on my 16 GB card. :D
It seems to load properly
I didnt have much time to really understand how to use CHDK, but i noticed one thing...
When I do half-press and focus on the object, default OSD information disappears and doesnt come back until I go into the menu or something. It seems to lose the default camera informations and not the ones displayed by the CHDK (eg. # of shots left, mode, resolution, flash, etc.). Is this normal?
Ill keep testing and report back.
-
I didnt have much time to really understand how to use CHDK, but i noticed one thing...
When I do half-press and focus on the object, default OSD information disappears and doesnt come back until I go into the menu or something. It seems to lose the default camera informations and not the ones displayed by the CHDK (eg. # of shots left, mode, resolution, flash, etc.). Is this normal?
Screen refresh for CHDK OSD and menu information is a problem with CHDK on many cameras in shooting mode. Recently, philmoz has improved this a bit for some cameras but it has not been implemented on all cameras. So for now, what you are seeing is normal for the SD780.
-
Thank you for the clarification waterwingz.
Im sorry if I keep posting some problems that are already known to CHDK.
Ill keep reading up on CHDK and hopefully I will stop doing that soon.
Anyways, I was testing the video mode a little bit and found something.
When I set the Video Mode = Quality and then made the Video Quality = "99" under Video Parameters,
a red "!" shows up and the video recording stops after 1 sec. Even if I lower the Video quality (e.g. 80), same thing happens.
This may be just due to my memory card as I am using Sandisk Class 2, however I tested this card to have stable write speed at ~6.6 MB/s and read speed ~ 18.2 MB/s using H2testw v1.4.
I am wondering if someone else can test this (possibly on a higher class card) and check the video recording is working in Quality mode.
-
Hi. I just wanted to mention that on the 1.00C CHDK build for the SD780 IS increasing the video quality mode just seems to increase the data rate without any noticeable visual improvement in video image quality. It might be a similar issue on the FW1.00B CHDK version too.
When I set the Video Mode = Quality and then made the Video Quality = "99" under Video Parameters,
a red "!" shows up and the video recording stops after 1 sec. Even if I lower the Video quality (e.g. 80), same thing happens.
This may be just due to my memory card as I am using Sandisk Class 2, however I tested this card to have stable write speed at ~6.6 MB/s and read speed ~ 18.2 MB/s using H2testw v1.4.
I am wondering if someone else can test this (possibly on a higher class card) and check the video recording is working in Quality mode.
-
Im sorry if I keep posting some problems that are already known to CHDK.
Ill keep reading up on CHDK and hopefully I will stop doing that soon.
Don't feel you have to apologize - there is no way for anyone to know every quirk of CHDK. When I suggested that a problem is well known, I'm only pointing out that is not an issue with the specific port so not something easily fixed (at least by me).
Having said that, it now appears that the disappearing menu problem can be easily solved - I'll post an update shortly.
When I set the Video Mode = Quality and then made the Video Quality = "99" under Video Parameters,
a red "!" shows up and the video recording stops after 1 sec. Even if I lower the Video quality (e.g. 80), same thing happens.
This may be just due to my memory card as I am using Sandisk Class 2, however I tested this card to have stable write speed at ~6.6 MB/s and read speed ~ 18.2 MB/s using H2testw v1.4.
You are on the right path I think. Even though your memory card might seem fast enough, experience says it needs to be quite a bit faster to allow the camera processor some time to work on the video. It seems the camera wants to write in very fast bursts rather than a slower continuous rate that the card could handle. Or at least that's my best theory.
For a class 2 card, I've seen reports of max usable quaility levels around 70. And your little camera might even be slower. Does it work at 50 or 60 - just to make sure the code runs ?
-
UPDATES for the IXUS100-SD780
Here's a couple of links for the two new releases for the IXUS100-SD780. Both versions should now have the "dissappearing menu when shooting" problem fixed.
I also updated the 1.00c to match the newer 1.00b.
IXUS100-SD780 firmware 1.00B]http://www.box.net/shared/n0564jl6y3o6o6v5qca5] IXUS100-SD780 firmware 1.00B (http://www.box.net/shared/n0564jl6y3o6o6v5qca5)
IXUS100-SD780 firmware 1.00C]http://www.box.net/shared/on0x5qi1xf9uf885muql] IXUS100-SD780 firmware 1.00C (http://www.box.net/shared/on0x5qi1xf9uf885muql)
If I get feedback that both of these versions work properly, I'll submit to the autobuild server.
UPDATE 2: now available from the autobuild server
UPDATE : I've attached a patch file suitable for submission for inclusion in the trunk. Worth having in case I don't get back here and somebody wants to pick this up down the road. Or if we get some testing information for the 1.00B & 1.00C suggesting this update works as promised.
-
UPDATES for the IXUS100-SD780
Here's a couple of links for the two new releases for the IXUS100-SD780. Both versions should now have the "dissappearing menu when shooting" problem fixed.
I also updated the 1.00c to match the newer 1.00b.
IXUS100-SD780 firmware 1.00B]http://www.box.net/shared/n0564jl6y3o6o6v5qca5] IXUS100-SD780 firmware 1.00B (http://www.box.net/shared/n0564jl6y3o6o6v5qca5)
IXUS100-SD780 firmware 1.00C]http://www.box.net/shared/on0x5qi1xf9uf885muql] IXUS100-SD780 firmware 1.00C (http://www.box.net/shared/on0x5qi1xf9uf885muql)
If I get feedback that both of these versions work properly, I'll submit to the autobuild server.
UPDATE : I've attached a patch file suitable for submission for inclusion in the trunk. Worth having in case I don't get back here and somebody wants to pick this up down the road. Or if we get some testing information for the 1.00B & 1.00C suggesting this update works as promised.
I just tested the 1.00B version, Canon and CHDK OSD remains on the screen.
I also checked the video parameters as you suggested. I took the video in QUALITY mode set at 50 and 60, it seems to be working fine. I changed the quality to 70 and the camera showed a red "!" so maybe you are right that my card/camera is too slow for recording at higher quality. Ill get a class 10 card and test later.
again, thank you for spending the time to help us with 1.00B firmware.
-
It would be good to hear that the 1.00C version works too. Then I can submit the patch file for inclusion in the autobuild.
IXUS100-SD780 firmware 1.00C (http://www.box.net/shared/on0x5qi1xf9uf885muql)
UPDATE : Link deleted - now in autobuild server.
-
I just wanted to mention that the new CHDK build that waterwingz created for SD780IS 100c cameras fixes the disappearing OSD Menus problem.
However, I noticed that when I upgraded to the latest build CHDK fails to create the badpixel.bin file and reports an error after taking two photos during the badpixel creation process. My camera is a SD780IS 1.00C. The problem also occurs with the July 31, 2011 ixus100_sd780-100c-0.9.9-1258-full_BETA.zip build.
The error message is:
badpixel.bin failed.
Please try again.
On my previously installed version of CHDK (build 0.9.9-1143) the "Create badpixel.bin" menu item worked fine. Back in April 2011 I even did a blog post about creating CHDK raw DNG images (http://www.andrewhazelden.com/blog/2011/04/enabling-raw-dng-images-with-chdk/).
Here is the version info for an older CHDK build that successfully created badpixel.bin files:
Ver: 0.9.9-1143
Date: April 13, 2011
Camera: ixus100_sd780
FW: 100c
For testing purposes I unzipped a fresh copy of the old April 13, 2011 CHDK 0.9.9-1143 build and tried it on my camera and was able to properly create a badpixel.bin file using the Raw Parameters "Create Badpixel.bin" command. It worked normally and reports:
badpixel.bin created
bad pixel count: 6484
Regards,
Andrew
-
the "badpixel.bin failed." message happens when the counts don't match between images. Sometimes this can happen due to changing conditions, like the sensor warming up between shots. That's why it says try again.
If the latest version really fails all the time, that would be odd. Something unexpectedly modifying raw buffer memory could cause this I guess.
-
I can confirm that the patch is working!
I tested with SD780 - Firmware 1.00B.
It is an improvement, no disappearing menu and I can switch between the menus. Video mode is available now, too.
Thank you waterwingz.
-
I've been away this last week, but it's nice to return and see this thread back to full activity. Tonight I'll download the latest release and experiment for a while.
-
However, I noticed that when I upgraded to the latest build CHDK fails to create the badpixel.bin file and reports an error after taking two photos during the badpixel creation process. My camera is a SD780IS 1.00C. The problem also occurs with the July 31, 2011 ixus100_sd780-100c-0.9.9-1258-full_BETA.zip build.
I tested to create badpixel.bin using the 1.00B firmaware version and it is working. It took 2 pics and then created the badpixel file. I was able to turn on the DNG format with no problem after that. Not sure if there is a problem with the 1.00C version???
-
Well since I have also a IXUS100IS version 100C among my camera collection I can perform a badpixel :blink: test.
Q: Will latest autobuild be OK or do you want me to test a specific version? Then I'll report back the result.
-
Well since I have also a IXUS100IS version 100C among my camera collection I can perform a badpixel :blink: test.
Q: Will latest autobuild be OK or do you want me to test a specific version? Then I'll report back the result.
Try the latest version.
-
Tested on ixus100_sd780 FW Vers 100c 0.9.9-1286 Aug 8 2011 22:16:51 (GCC 4.4.3)
Ran the badpixel LUA script, got some result. Script ran but could not find any badpixel.bin on my SD although it stated it wrote the file and I had 255 bad pixels. I do however had two files CRW_0155.CRW and CRW_0156.CRW in the directory /DCIM/100CANON/
Since I've never had a need to use the badpixeltest I'll read through http://www.andrewhazelden.com/blog/2010/02/enabling-chdk-raw-images-on-the-canon-sd780is/ (http://www.andrewhazelden.com/blog/2010/02/enabling-chdk-raw-images-on-the-canon-sd780is/) then see if I can get more results.
BTW how do I know if I have the correct badpixel.lua file?
-
Actually you want to use the built-in Create badpixel.bin feature in the RAW menu. You no longer need to use the .lua script. I wrote an updated blog post here Enabling RAW DNG Images With CHDK (http://www.andrewhazelden.com/blog/2011/04/enabling-raw-dng-images-with-chdk/).
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fwww.andrewhazelden.com%2Fblog%2Fwp-content%2Fuploads%2F2011%2F04%2F3.1.create_badpixel.bin_-560x420.png&hash=292f354815061dc8807bf79ce2d2bd80)
Tested on ixus100_sd780 FW Vers 100c 0.9.9-1286 Aug 8 2011 22:16:51 (GCC 4.4.3)
Ran the badpixel LUA script, got some result. Script ran but could not find any badpixel.bin on my SD although it stated it wrote the file and I had 255 bad pixels. I do however had two files CRW_0155.CRW and CRW_0156.CRW in the directory /DCIM/100CANON/
Since I've never had a need to use the badpixeltest I'll read through http://www.andrewhazelden.com/blog/2010/02/enabling-chdk-raw-images-on-the-canon-sd780is/ (http://www.andrewhazelden.com/blog/2010/02/enabling-chdk-raw-images-on-the-canon-sd780is/) then see if I can get more results.
BTW how do I know if I have the correct badpixel.lua file?
-
Thanks, tested Tested on ixus100_sd780 FW Vers 100c 0.9.9-1286 Aug 8 2011 22:16:51 (GCC 4.4.3) with the build in badpixel routine. And indeed I got a ~1.2.6Kb badpixel.bin file. Examined with a Hex editor, looks right since the file probably contains positions in 4Bytes then filesize / 4 gives the about bad pixels ~3200bad pixels. If more help testing the badpixel routine let me know.
Still very happy the firmware for this version is created, thank to all!
-
Is it possible to turn off both leds during the exposure?
I am making Night Time Lapse with 30 second exposure and I have a light leak in the upper left corner of the frame, I thing that the leds are bleeding inside the camera.
Thanks
Xenio
-
Hi Xeno.
That looks like standard CCD dark noise that becomes visible during long exposures. You can reduce this issue by using techniques like dark frame subtraction.
Here is a link that shows examples of dark noise in images:
http://photo.net/learn/dark_noise/ (http://photo.net/learn/dark_noise/)
Regards,
Andrew
Is it possible to turn off both leds during the exposure?
I am making Night Time Lapse with 30 second exposure and I have a light leak in the upper left corner of the frame, I thing that the leds are bleeding inside the camera.
Thanks
Xenio
-
Yep I was using 1600 iso and there is a lot of digital noise, but the problem I have in the picture is the purple area indicated by the arrow.
It isn't a standard high iso noise, it is an area where there is light getting into it. I was thinking a light bleeding inside from the LCD or the LED because the ixus100 with a long exposure keep the leds blinking and the LCD is on.
Would be nice if CHDK could controls this LEDs and keep it of :D
This is what I've got:
Night Time Lapse Test (http://vimeo.com/29521867)
You can see a purple area in the top right border, in the hires photo is much more visible.
Thanks
Xenio
-
That is amp glow ,not the light from the Led diode,you need dark frame.
-
Sorry if this has been discussed before, I wasn't able to find anything about it.
Is there any way to remove the video time limit? I know it can only go up to 4gb, but is there a way to make it so that it automatically starts a new video right after that if I put the two clips together they would be seamless?
Thanks
-
Sorry if this has been discussed before, I wasn't able to find anything about it.
Did you try a few different search terms on this forum ? Its not the greatest search engine in the world but this question comes up every three or four weeks.
Is there any way to remove the video time limit? I know it can only go up to 4gb, but is there a way to make it so that it automatically starts a new video right after that if I put the two clips together they would be seamless?
http://chdk.setepontos.com/index.php?topic=6507.msg69015 (http://chdk.setepontos.com/index.php?topic=6507.msg69015)
-
Update : the ixus100_sd780 now supports letting the user select his <ALT> key. The options are the DISP key or the Play key - and the default is the Play key.
-
Update : the ixus100_sd780 has been converted to use enhanced colors via a custom palette in the 1.2.0 branch (http://mighty-hoernsche.de/trunk/).
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FgVHgKsb.jpg&hash=2d5b61ce89fb37f82a63c3f4b2532d5e)
(image & testing credits to andrewhazelden (http://chdk.setepontos.com/index.php?action=profile;u=12040))
-
Does setting CHDK noise reduction to ON eliminate hot pixels as claimed here http://friguron.wordpress.com/2012/02/27/dead-pixels-in-my-ixus-digital-camera-and-a-fix-using-chdk/ (http://friguron.wordpress.com/2012/02/27/dead-pixels-in-my-ixus-digital-camera-and-a-fix-using-chdk/) even for exposures shorter than one second on this camera ?
-
Does setting CHDK noise reduction to ON eliminate hot pixels as claimed here http://friguron.wordpress.com/2012/02/27/dead-pixels-in-my-ixus-digital-camera-and-a-fix-using-chdk/ (http://friguron.wordpress.com/2012/02/27/dead-pixels-in-my-ixus-digital-camera-and-a-fix-using-chdk/) even for exposures shorter than one second on this camera ?
This is probably in the wrong thread but AFAIK it should work as describe in that article.
-
This is probably in the wrong thread
Sorry, I forgot to mention, this specifically refers to the IXUS100.
A user said neither the SDM or CHDK versions worked like that.
If so, either the ram address is incorrect or that article is incorrect.
-
This is probably in the wrong thread
Sorry, I forgot to mention, this specifically refers to the IXUS100.
A user said neither the SDM or CHDK versions worked like that.
If so, either the ram address is incorrect or that article is incorrect.
Easy enough to check - ask your user to take two 30 second exposures - one with dark frame on and the other with dark frame off. Observe whether the total save time is 60 seconds or 30 and you'll know if they have hooked the right address in capt_seq.c I assume that the SDM code for capt_seq.c is just lifted from the CHDK port so results should be the same.
-
If so, either the ram address is incorrect or that article is incorrect.
The RAM address is fine but the hook in capt_seq.c is commented out for both firmware versions.
Also, "wait_until_remote_button_is_released()" is also commented out so precision sync is not possible with this camera.
I just posted to this effect in the SDM Yahoo group - if your user wants it fixed he/she will need to come here and help with the testing.
-
if your user wants it fixed he/she will need to come here and help with the testing.
Here I am, and surely I will help with the testing ;-)!
Best regards und thank you for your support,
Christoph
-
Here I am, and surely I will help with the testing ;-)!
Welcome. Anticipating your arrival, I took a look at some comparable ports to the IXUS100. The D10 has the same hooks as the IXUS100 in the same place but they are not commented out. So we would be pretty safe to try that.
Here's both firmware versions for CHDK 1.2.0 - SD card lock booting only.
100b> https://www.box.com/s/bruj531up48y31oiup7f (https://www.box.com/s/bruj531up48y31oiup7f)
100c> https://www.box.com/s/mrddiduz06m3p5aa38m6 (https://www.box.com/s/mrddiduz06m3p5aa38m6)
You can check the noise reduction by shooting for 10 seconds with it Off and On. With it On, you should get a 20 second shooting time, with it Off you should get 10 seconds.
You can check the USB remote precision sync by inserting a long sync delay and observing if the shutter delays firing after the remote is released for that amount of time.
-
Thank you! For firmware 100C the dark frame reduction works. If I activate it, the camera processes 10 seconds after 10 seconds shutter time and removes all the hotpixel. The other function seems to work, too; I had set the delay to 3 seconds.
Best regards,
Christoph
-
Patch to correct keyboard behavior, errors were reported here (http://chdk.setepontos.com/index.php?topic=9986.msg118975#msg118975).
- Set KEY_PLAYBACK as default ALT key, KEY_DISPLAY as the second option
- Remove KEY_POWER from KEYMASK1
-
Patch to correct keyboard behavior, errors were reported here (http://chdk.setepontos.com/index.php?topic=9986.msg118975#msg118975).
- Set KEY_PLAYBACK as default ALT key, KEY_DISPLAY as the second option
- Remove KEY_POWER from KEYMASK1
Tested to be working fine. Play is ALT key now and I can power the cam off while in ALT mode. Thanks.
-
Thanks. Changes committed to trunk, changeset 3799 (https://www.assembla.com/code/chdk/subversion/commit/3799)