CHDK Forum
CHDK Development => General Discussion and Assistance => DryOS Development => Topic started by: c10ud on 08 / October / 2010, 11:37:56
-
Link to wiki: http://chdk.wikia.com/wiki/SD1300IS (http://chdk.wikia.com/wiki/SD1300IS)
Hello there,
today i got this camera and decided to start having fun with chdk doing a port to this platform.
I started looking into the boot process with an eye on the "new" dryos boot process basing on a480, and after some hours i've been able to achieve a "normal" boot copying the assembler code from the original firmware disasm and commenting out chdk task creation (i am new to chdk porting :)).
camera specs (mine has FIRMWARE 1.00D (http://drop.io/IXUS105_100D)):#31f4
PLATFORMID=12788
PLATFORMOS=dryos
MEMBASEADDR=0x1900
RESTARTSTART=0x50000
MEMISOSTART=0x12e9fc
ROMBASEADDR=0xFFC00000
NEED_ENCODED_DISKBOOT=4
Now i have to start looking into stubs that finsig didn't found, unfortunately i don't have IDA so i guess it will take a while before i can properly boot with spytask enabled. If someone else wanna take a look/contribute, just ask and i will upload what i did so far somewhere.
Greets
-
i got spytask running correctly without crashing the camera, however no gui is showed yet, i need to fix sub/100d/lib.c :)
-
meanwhile, here's the loader: http://www.zshare.net/download/813624206aa0ce68/ (http://www.zshare.net/download/813624206aa0ce68/)
include/camera.h (relevant parts, copied from other cameras): http://ixus105.pastebin.com/gaicf6KV (http://ixus105.pastebin.com/gaicf6KV)
sub/100d/stubs_auto.S: http://ixus105.pastebin.com/9ZsTup5N (http://ixus105.pastebin.com/9ZsTup5N)
sub/100d/stubs_entry.S: http://ixus105.pastebin.com/Xg1bPhgU (http://ixus105.pastebin.com/Xg1bPhgU)
sub/100d/stubs_entry_2.S: http://ixus105.pastebin.com/rD0dd3en (http://ixus105.pastebin.com/rD0dd3en)
sub/100d/stubs_min.S: http://ixus105.pastebin.com/TmDtwuhJ (http://ixus105.pastebin.com/TmDtwuhJ)
sub/100d/boot.c : http://ixus105.pastebin.com/NhHPgijs (http://ixus105.pastebin.com/NhHPgijs)
sub/100d/lib.c : http://ixus105.pastebin.com/d7XU2buV (http://ixus105.pastebin.com/d7XU2buV)
core_spytask is running correctly (well, camera doesn't crash at least) as i found some wrong stubs and corrected.
Some random questions:
- Why the camera doesn't power on if i keep my finger on the power button? It does, without this chdk build (and does in other cameras chdk)
- The (small) gui isn't showing up, am i missing something?
- the mkdirs in core_spytask seem not working (shouldn't they create those directories on boot, if not present?), however i've double-checked the stub address and it seems fine.
- i don't know how to find some lib.c values, eg: void *vid_get_viewport_live_fb(){
void **fb=(void **)0x2180; // 0x2150 or 0x2180 for SX200 TODO: find this for ixus105 and void *vid_get_viewport_fb_d(){
int x=(*(int*)(0x2670+0x58)); // ffc56514: e59f81f8 ldr r8, [pc, #504] ; ffc56714: (00002670)
// (0x58 at FF8594F0 for SX200) TODO: find this for ixus105
return (void*) (x ? x : 0xFFC00000) ;
}
-
i think i can partially answer myself saying that i must implement init_file_modules_task() that should correctly start the spytask? if so, do i need the entire chain or i can stop to the first part?
-
Hello c10ud!
I have an IXUS105 too (firmware 1.00D). I'm new here, and I'm also a rookie in CHDK porting :D
It's very nice to see this thread created! Good work!
Unfortunately, I'm quite busy these days (I hope it will go better in a few weeks...), but I'll try to help as much as I can !
Best,
A.
-
i think i can partially answer myself saying that i must implement init_file_modules_task() that should correctly start the spytask? if so, do i need the entire chain or i can stop to the first part?
If you mean core_spytask_can_start, this only signals spytask that it doesn't need to way. Otherwise, it uses a hardcoded delay (although I guess this might not be long enough).
The live viewport stuff isn't essential for getting the port running, you can return null and CHDK will operate correctly.
- Why the camera doesn't power on if i keep my finger on the power button? It does, without this chdk build (and does in other cameras chdk)
I think something to do with this ?
"BL sub_ffc24320\n" // removed in other ports, but if i remove it, camera crashes!
[/quote]
Look inside this function, maybe some part of it still needs to be done.
-
Hello c10ud!
I have an IXUS105 too (firmware 1.00D). I'm new here, and I'm also a rookie in CHDK porting :D
It's very nice to see this thread created! Good work!
Unfortunately, I'm quite busy these days (I hope it will go better in a few weeks...), but I'll try to help as much as I can !
Best,
A.
great!
i think i can partially answer myself saying that i must implement init_file_modules_task() that should correctly start the spytask? if so, do i need the entire chain or i can stop to the first part?
If you mean core_spytask_can_start, this only signals spytask that it doesn't need to way. Otherwise, it uses a hardcoded delay (although I guess this might not be long enough).
The live viewport stuff isn't essential for getting the port running, you can return null and CHDK will operate correctly.
about core_spytask_can_start: yes i've seen it's starting after a little while (or i wouldn't get something running in background, i guess :p), my bad
live viewport: i was just wondering where those values came from, anyway still ain't getting chdk logo to show, i must be missing something
- Why the camera doesn't power on if i keep my finger on the power button? It does, without this chdk build (and does in other cameras chdk)
I think something to do with this ?
"BL sub_ffc24320\n" // removed in other ports, but if i remove it, camera crashes!
[/quote]
Look inside this function, maybe some part of it still needs to be done.
my bad, forgot the +4 in *(int*)(0x221c+4)= (*(int*)0xc0220024)&1 ? 0x200000 : 0x100000; // replacement for correct power-on. ffc477a0 now it works as expected:)
-
live viewport: i was just wondering where those values came from, anyway still ain't getting chdk logo to show, i must be missing something
The OSD (including logo) is on the bitmap buffer, not the live view. Incorrect values of the live view will not affect ability to display the OSD
-
live viewport: i was just wondering where those values came from, anyway still ain't getting chdk logo to show, i must be missing something
The OSD (including logo) is on the bitmap buffer, not the live view. Incorrect values of the live view will not affect ability to display the OSD
i know that, i badly written my sentence, they're actually two different ones:
- i don't know how to find those live values (__future__)
- i don't know why i am not getting the logo
meanwhile, i found this:
//ffcd60d8: e3a00e2d mov r0, #720 ; 0x2d0
//ffcd60dc: e3a010f0 mov r1, #240 ; 0xf0
long vid_get_bitmap_buffer_width() { return 720; }
long vid_get_bitmap_buffer_height() { return 240; }
i am now experimenting with draw functions in gui init code. there must be somethign wrong..
-
actually, i found out that adding
case GUI_MODE_NONE:
gui_draw_osd();
draw_txt_string(20, 14, "<OSD>", MAKE_COLOR(COLOR_ALT_BG, COLOR_FG));draw_txt_string(20, 14, "<OSD>", MAKE_COLOR(COLOR_ALT_BG, COLOR_FG));in gui_redraw.c shows correctly the string in the screen.
i'm starting to think in some bug that prevents the logo from being loaded (and mkdirs from main.c to be successful :)) i'll try to find the stubs that may fail here. (or locked sd card ?)
-
got logo to show, by forcing an high value of gui_splash
gui_splash = 30; //(conf.splash_show)?SPLASH_TIME:0;seems like the stubs were correct after all :)
now i'll try to hack into kbd in order to see if i can get the ALT menu :)
-
chdk menu up and running, yeah! :)
-
Excellent.
I hope the chdk gurus will provide all the help you may need.
I'm especially interested in taking pictures in RAW.
Unfortunately I can't help because I'm such a big noob.
Keep up the great work.
-
i'll upload the code somewhere anytime soon so others can take advantage of having a sort-of-working source (histo and edge seem working althrough i'm no expert in this field:)), meanwhile i'll try to hijack the capture task so we can use shoot();
-
two small issues i'm facing:
- i keep getting Raw disabled, even if i enable it from the menu, any clue on why?
- shoot() lua script doesn't seem to work, any clue on where to take a look in order to debug it?
-
two small issues i'm facing:
- i keep getting Raw disabled, even if i enable it from the menu, any clue on why?
Do you mean raw works, but then gets mysteriously disabled ? That's usually the shortcut key.
- shoot() lua script doesn't seem to work, any clue on where to take a look in order to debug it?
Not with out some indication of how it fails. Incorrect propcase values could be the cause, AFAIK newer cameras use a new propset. You can look at core/kbd.c to see what shoot() is doing.
-
well the capt_seq seems fine but camera doesn't shoot (doesn't go further the shoot_half), and on screen i get the "raw disabled" message..
i need to take a look at props then, since they're unmodified..i'll try to complete exp_drv_task first though.
(today i tried to post a nice diff in github, but man, i lost some time on git-svn and i couldn't get it work the way i wanted :) i guess i'll just go for the usual nice tgz as soon as i complete this task.. heh)
-
exposure override now working, i'm too tired for today but i'll upload capt_seq.c since i fear losing it! lol!
http://ixus105.pastebin.com/ZL8tR3GJ (http://ixus105.pastebin.com/ZL8tR3GJ)
-
well the capt_seq seems fine but camera doesn't shoot (doesn't go further the shoot_half),
This sounds like wrong propcases, it isn't detecting that shooting is ready. capt_seq isn't going to be related to this.
and on screen i get the "raw disabled" message..
If your modemap or some variables are wrong, raw exceptions may get confused.
-
Thanks reyalp for your answers. I'll now upload a version that "compiles and run, at least" so others can try it out and possibly give a hand fixing what's broken :)
LINK (CODE): http://drop.io/ixus105_sd1300 (http://drop.io/ixus105_sd1300)
FIRM DUMP: http://drop.io/IXUS105_100D (http://drop.io/IXUS105_100D)
*** Features known BROKEN or NOT supported:
- shoot() script
- general scripts (untested, some crashers happen)
- zebra
- raw
*** Other issues:
- shooting with chdk loaded seems always overriding ss to 1sec
-
c10ud,
since sx210 and this cam are the same os version r0043 maybe they should share propset
this is the ony I'm using and all the overrides work
#define PROPCASE_DRIVE_MODE 102
#define PROPCASE_FOCUS_MODE 133 // seems 0 allways??
#define PROPCASE_FLASH_MODE 143 //ASM1989 looks like moves from 2 no flash, to 1 yes flash
#define PROPCASE_FLASH_FIRE 122 //ASM1989 looks like moves from 0 if flash is closed to 1 if its open
#define PROPCASE_FLASH_MANUAL_OUTPUT 141 //ASM1989 looks like moves from 0 to 2
#define PROPCASE_FLASH_ADJUST_MODE 121 //ASM1989 dont know allways 1 ????
#define PROPCASE_USER_TV 266 //ASM1989 looks like
#define PROPCASE_TV 264 //ASM1989 looks like
#define PROPCASE_USER_AV 26 //ASM1989 looks like
#define PROPCASE_AV 23
#define PROPCASE_MIN_AV 25
#define PROPCASE_SV 249 //ASM1989 Testesd OK
#define PROPCASE_DELTA_SV 79 //was 79TESTED with 71 with no sucess
#define PROPCASE_SV_MARKET 248 //ASM1989 Testesd OK
#define PROPCASE_BV 34
#define PROPCASE_SUBJECT_DIST1 247 //ASM1989 looks like not sure
#define PROPCASE_SUBJECT_DIST2 65 //ASM1989 looks like not sure
#define PROPCASE_ISO_MODE 149 //ASM1989 looks like
#define PROPCASE_SHOOTING 208 //ASM1989 looks like
#define PROPCASE_IS_FLASH_READY 210 //ASM1989 looks like
#define PROPCASE_OVEREXPOSURE 103 //ASM1989 looks like 0 perfect exposure up to 300 overexposure, from 64000 to 0 underexposure
#define PROPCASE_SHOOTING_MODE 49 //ASM1989 looks like cahges when mode changes...
#define PROPCASE_IS_MODE 145 //ASM1989 looks like only chages 0,1,2,3,4
#define PROPCASE_QUALITY 57 //ASM1989 looks like only chages 1, 2
#define PROPCASE_RESOLUTION 220 //ASM1989 looks like only chages 0, 1....8 wide
#define PROPCASE_EV_CORRECTION_1 107 //ASM1989 looks like on P mode goes from 65344 to 0 to 192
#define PROPCASE_EV_CORRECTION_2 209 //ASM1989 looks like on P mode goes from 65344 to 0 to 192
#define PROPCASE_ORIENTATION_SENSOR 221 //ASM1989 looks like values 0 270 or 90
#define PROPCASE_DIGITAL_ZOOM_STATE 94
#define PROPCASE_DIGITAL_ZOOM_POSITION 95
#define PROPCASE_DISPLAY_MODE 105 // allways 0 ???
#define PROPCASE_BRACKET_MODE 29
#define PROPCASE_FLASH_SYNC_CURTAIN 64 //ASM1989 dont know allways 0 ??? anyway sx210 dosnt seam to have one
#define PROPCASE_METERING_MODE 155 //ASM1989 could be goes from 0 1 2
#define PROPCASE_WB_ADJ 271 // Not sure number changes, but sure prop 270 changes from 0,1,2....
//#define PROPCASE_ASPECT_RATIO 294
#define PROPCASE_ASPECT_RATIO 215 // ASM1989 Testing
#define PROPCASE_TIMER_MODE 225 //ASM1989 looks like only chages 0, 1, 2
#define PROPCASE_OPTICAL_ZOOM_POSITION 197 //ASM1989 looks like
#endif
-
isn't that propset3? if i set that in camera.h overrides seem not working anymore though..
-
No some has changed, at least in sx210, get all the code if you need it here http://es.drop.io/chdk_sx210_rc (http://es.drop.io/chdk_sx210_rc)
I have all the overrides working (except ISO override having the flash activated)
anyway check out also if you have the right stub for apexus2 , I try to check it, but with the 4MB bin posted I was unable to get to ffd8f4b8 it ends at FFC0FFF8 , do you have the 8MB bin file?
-
with your new propset, compiler is complaining because of missing propcases: PROPCASE_REAL_FOCUS_MODE and PROPCASE_FOCUS_STATE. does this propcase require some special modification of generic/shooting.c or some include/camera.h? i'm now trying with the same settings as sx210 but no luck..?
-
i used a 4mb dump found on chdk wiki page.. maybe i posted the wrong link..?
edit: it's also here http://drop.io/chdkdumps3 (http://drop.io/chdkdumps3)
-
I dont use PROPCASE_REAL_FOCUS_MODE and PROPCASE_FOCUS_STATE
make a text search through the trunk to find it, or include them manually to make it compile
This is your bin : ixus105_sd1300_100d.7z ?
-
i'm now seeing that i'm using a very old version of trunk, and that part has been removed. i'll try to modify that part and compile to see what will happen
yes, that's the bin firm
-
uhm, with latest trunk - and new propset - overrides seem working, still no luck with scripts though. there also must be some wrong stub regarding file handling, i get a crasher when choosing Load script from file..
-
could be, most of the issues come from wrong stubs, compare them to the sx210, since most of the code and calls will be simillar, also dont take for good the auto stubs.
Does you ISO override work with the flash enabled? it is the only issue with overrides I have in the sx210
-
didn't try that yet. however here's a strange thing about the shoot() script:
i tracked down the problem that's hanging that script in core/kbd.c to KBD_STACK_PUSH(SCRIPT_WAIT_EXPHIST);
KBD_STACK_PUSH(SCRIPT_PR_WAIT_EXPHIST); in kbd_sched_shoot(). Looking at the process_script() function i see that SCRIPT_PR_WAIT_EXPHIST is handled like this case SCRIPT_PR_WAIT_EXPHIST: {
if (shooting_in_progress() || mvideo) {
state_expos_recalculated = 0;
histogram_restart();
kbd_int_stack_ptr-=1; // pop op.
}
return;
} If i change the if to an if(1), shooting works. So i investigated shooting_in_progress() in platform/generic/shooting.c, that just returns the value of a propertyint shooting_in_progress()
{
int t = 0;
_GetPropertyCase(PROPCASE_SHOOTING, &t, sizeof(&t));
return t != 0;
}
in propset3, which is what i'm currently using, that's mapped to #define PROPCASE_SHOOTING 208 and showing the debug props osd i see that 208 effectively changes from 0 to 1 on manual shoot_half.
Any clue?
-
c10ud - i guess it's the same prop as in waldo's S95 port:
Here's something odd I just noticed. The uBasic shoot function did not work on the S95. I tracked this to the PROPCASE_SHOOTING always being 0, so I assumed that the property case address was wrong. I searched through all the property cases and found what seems to be PROPCASE_SHOOTING located at 303. I cannot find a reference to this address in the code or on the forum, so I guess they changed it on this camera. Patching this address in my code makes the shoot function work.
If Canon is going to change these addresses more often, it seems like this is a camera-dependent thing that belongs in the Platform/camera directory, but the current code structure puts this information in trunk/include. It seems a bit cumbersome to create a new propset each time anything changes for one particular camera.
-
thanks Fe for the quick response.
In my case i see 303 remains 0, but 301 changes from 0 to 1 like the usual 208 does.
I did more testing, seems like if i start the shoot() script it hangs, but if i click the shoot_half button (yes, manually finger-on-button) then the script is executed and terminated correctly (!!!) i'll recheck kbd.c, i guess it's a wrong shoo_half value at this point...
-
physw_status[2] when nothing is pressed is 207c0b. Pressing shoot_half manually gets it to 203c0b. However, when camera is ready to shoot (you see canon-osd with chosen sspeed, iso, etc.) it changes again to 203c0f.
I defined shoot_half as { 2, KEY_SHOOT_HALF , 0x00004000 }, do you think i am missing something here?
-
meh. just discovered that shoot_half mustn't go into the keymask. shoot script is now fixed.
-
ok, new source available in http://drop.io/ixus105_sd1300 (http://drop.io/ixus105_sd1300) just download ixus105_0.2.zip and have fun.
I added ptp stuff for easier debug of some stuff, since it's in trunk now.. :)
This version has shoot() fixed, zoom fixed, fl should be ok, gui ok, etc.
tested:
- loading, drawing
- some lua stuff
- exp override
current issues/unfeatures:
- load script = camera shutdown
- save raw = camera shutdown (some stub must be wrong)
- no video override
- edge overlay works but disappears soon
- zebra doesn't seem to be working
- some other overrides does not seem to work correctly
-
so i was trying to find the right values for vid_get_viewport_live_fb(), and come up with
void *vid_get_viewport_live_fb()
{
void **fb=(void **)0x43f8;
unsigned char buff = *((unsigned char*)0x4270);
if (buff == 0) buff = 2; else buff--;
return fb[buff];
}
basing myself on my findings, then i asked for some disasm help and found this nice values
ROM:FFCBC250 dword_FFCBC250 DCD 0x1001043 ; DATA XREF: sub_FFCBBCF8+8r
ROM:FFCBC254 dword_FFCBC254 DCD 0x4270 ; DATA XREF: sub_FFCBBCF8+4r
ROM:FFCBC254 ; sub_FFCBBDC4+4r ...
ROM:FFCBC258 off_FFCBC258 DCD unk_FFEAEC38 ; DATA XREF: sub_FFCBBDC4+8r
ROM:FFCBC258 ; sub_FFCBC6E0+2Cr
ROM:FFCBC25C dword_FFCBC25C DCD 0x665FC ; DATA XREF: sub_FFCBBEB0+4r
ROM:FFCBC25C ; _sub_FFCBBF04__LiveImage.c__812+558r ...
ROM:FFCBC260 dword_FFCBC260 DCD 0x665A8 ; DATA XREF: _sub_FFCBBF04__LiveImage.c__812+18r
ROM:FFCBC260 ; _sub_FFCBBF04__LiveImage.c__812+38r ...
ROM:FFCBC264 aLiveimage_c DCB "LiveImage.c",0 ; DATA XREF: _sub_FFCBBF04__LiveImage.c__812+80o
ROM:FFCBC264 ; _sub_FFCBCA58__LiveImage.c__0+44o ...
ROM:FFCBC270 dword_FFCBC270 DCD 0x4408 ; DATA XREF: _sub_FFCBBF04__LiveImage.c__812+90r
ROM:FFCBC270 ; _sub_FFCBBF04__LiveImage.c__812+180r
ROM:FFCBC274 dword_FFCBC274 DCD 0x43F8 ; DATA XREF: _sub_FFCBBF04__LiveImage.c__812+A8r
ROM:FFCBC278 dword_FFCBC278 DCD 0x4430 ; DATA XREF: _sub_FFCBBF04__LiveImage.c__812+230r
ROM:FFCBC27C dword_FFCBC27C DCD 0x4428 ; DATA XREF: _sub_FFCBBF04__LiveImage.c__812+260r
ROM:FFCBC280 dword_FFCBC280 DCD 0x4420 ; DATA XREF: _sub_FFCBBF04__LiveImage.c__812+294r
the LiveImage routine is like this http://ixus105.pastebin.com/KHNsaGpR (http://ixus105.pastebin.com/KHNsaGpR) so i guess the 4270 value is correct. though i don't get a valid image (and i still have no clue on where to find buffer width, width and height of the viewfinder)
any thoughts?
-
welp, just tried to load this onto my SD1300 with a bootable card made with CardTricks and got the dreaded "Lens Error. Will shut down automatically". I've tried taking out the battery, restarting, nothing. The lens stay extended and the camera won't turn on other than showing this message. I was using the 2nd version of this hack when this all went down. I've tried removing the card, reinstalling batteries, etc, and I can't get the error fixed.
Any ideas?
-
no idea, what were you doing exactly? (so i can try it maybe)
edit: btw, i think you should return it to assistance, i don't think it's because of chdk
-
update: the next day I tried to turn on the camera with a different SD card inserted and it started up fine. strange.
should anyone be able to download the ixus105_0.2.zip file and play around with what has been done to start a CHDK hack on this device?
-
i'm using it for my tests and it's working good, however features are still broken - do you have the same firm version?
-
I've currently got firmware version 1.0.0.0 loaded on the sd1300
I'm aware that many features aren't functioning, but what I really want is exposure override anyways. Timelapse would be a nice bonus ;)
-
ok, new source available in http://drop.io/ixus105_sd1300 (http://drop.io/ixus105_sd1300) just download ixus105_0.2.zip and have fun.
I added ptp stuff for easier debug of some stuff, since it's in trunk now.. :)
This version has shoot() fixed, zoom fixed, fl should be ok, gui ok, etc.
tested:
- loading, drawing
- some lua stuff
- exp override
current issues/unfeatures:
- load script = camera shutdown
- save raw = camera shutdown (some stub must be wrong)
- no video override
- edge overlay works but disappears soon
- zebra doesn't seem to be working
- some other overrides does not seem to work correctly
When attempting to compile from your files, a few problems occurred.
V1 of your files include the camera .h modifications, which are not included in v2, btw.
Once adding the camera.h modifications, attempts to compile are met with:
In file included from ubasic.c:51:0:
../../include/platform.h:45:6: error: #error unknown camera processor
In file included from ubasic.c:53:0:
../../include/camera.h:3152:3: error: #error camera type not defined
In file included from ../../include/stdlib.h:1:0,
from ubasic.c:55:
../../include/camera.h:3152:3: error: #error camera type not defined
ubasic.c: In function 'factor':
ubasic.c:306:27: error: 'PROPCASE_FOCUS_MODE' undeclared (first use in this func
tion)
ubasic.c:306:27: note: each undeclared identifier is reported only once for each
function it appears in
ubasic.c:310:27: error: 'PROPCASE_DISPLAY_MODE' undeclared (first use in this fu
nction)
ubasic.c:314:27: error: 'PROPCASE_FLASH_MODE' undeclared (first use in this func
tion)
ubasic.c:318:27: error: 'PROPCASE_SHOOTING' undeclared (first use in this functi
on)
ubasic.c:322:27: error: 'PROPCASE_IS_FLASH_READY' undeclared (first use in this
function)
ubasic.c:326:27: error: 'PROPCASE_IS_MODE' undeclared (first use in this functio
n)
ubasic.c:330:27: error: 'PROPCASE_EV_CORRECTION_1' undeclared (first use in this
function)
ubasic.c:334:27: error: 'PROPCASE_RESOLUTION' undeclared (first use in this func
tion)
ubasic.c:338:27: error: 'PROPCASE_QUALITY' undeclared (first use in this functio
n)
ubasic.c:342:27: error: 'PROPCASE_ORIENTATION_SENSOR' undeclared (first use in t
his function)
ubasic.c: In function 'set_ev_statement':
ubasic.c:1897:29: error: 'PROPCASE_EV_CORRECTION_1' undeclared (first use in thi
s function)
ubasic.c:1898:29: error: 'PROPCASE_EV_CORRECTION_2' undeclared (first use in thi
s function)
ubasic.c: In function 'set_resolution_statement':
ubasic.c:1930:21: error: 'PROPCASE_RESOLUTION' undeclared (first use in this fun
ction)
ubasic.c: In function 'set_quality_statement':
ubasic.c:1939:21: error: 'PROPCASE_QUALITY' undeclared (first use in this functi
on)
C:\CHDK\gcc451\bin\gmake.exe[2]: *** [ubasic.o] Error 1
C:\CHDK\gcc451\bin\gmake.exe[1]: *** [all-recursive] Error 1
gmake: *** [all-recursive] Error 1
Can you help shed some light on this error? Thanks for your hard work on this, I'm hoping to get automated shooting working soon (timelapse functionality I guess).
-
hello,
this is what i've added in include/camera.h
#elif defined (CAMERA_ixus105_sd1300)
#define CAM_DRYOS_2_3_R39 1
#define CAM_PROPSET 3
#define CAM_DRYOS 1
#define CAM_RAW_ROWPIX 4080
#define CAM_RAW_ROWS 3048
#undef CAM_CAN_SD_OVER_NOT_IN_MF
#undef CAM_CAN_UNLOCK_OPTICAL_ZOOM_IN_VIDEO
#define CAM_HAS_VIDEO_BUTTON 1
#define CAM_VIDEO_QUALITY_ONLY 1
#undef CAM_VIDEO_CONTROL
#define CAM_MULTIPART 1
#undef CAM_USE_ZOOM_FOR_MF
#undef CAM_HAS_ERASE_BUTTON
#define CAM_SHOW_OSD_IN_SHOOT_MENU 1
#define CAM_EXT_TV_RANGE 1
#define CAM_HAS_ND_FILTER 1
// pattern
#define cam_CFAPattern 0x02010100 // Red Green Green Blue
// color
#define CAM_COLORMATRIX1 \
827547, 1000000, -290458, 1000000, -126086, 1000000, \
-12829, 1000000, 530507, 1000000, 50537, 1000000, \
5181, 1000000, 48183, 1000000, 245014, 1000000
#define cam_CalibrationIlluminant1 1 // Daylight
// cropping
#define CAM_JPEG_WIDTH 3648
#define CAM_JPEG_HEIGHT 2736
#define CAM_ACTIVE_AREA_X1 6
#define CAM_ACTIVE_AREA_Y1 12
#define CAM_ACTIVE_AREA_X2 3690
#define CAM_ACTIVE_AREA_Y2 2772
// camera name
#define PARAM_CAMERA_NAME 4 // parameter number for GetParameterData
#undef CAM_SENSOR_BITS_PER_PIXEL
#undef CAM_WHITE_LEVEL
#undef CAM_BLACK_LEVEL
#define CAM_SENSOR_BITS_PER_PIXEL 12
#define CAM_WHITE_LEVEL ((1<<CAM_SENSOR_BITS_PER_PIXEL)-1)
#define CAM_BLACK_LEVEL 127
//nandoide sept-2009
#undef CAM_USES_ASPECT_CORRECTION
#undef CAM_USES_ASPECT_YCORRECTION
#define CAM_USES_ASPECT_CORRECTION 1 //camera uses the modified graphics primitives to map screens an viewports to buffers more sized
#define CAM_USES_ASPECT_YCORRECTION 0 //only uses mappings on x coordinate
//default mappings
#undef ASPECT_XCORRECTION
#define ASPECT_XCORRECTION(x) ( ( ((x)<<3) + (x) ) >>2 ) //correction x*screen_buffer_width/screen_width = x*720/320 = x*9/4 = (x<<3 + x)>>2
//grids
#undef ASPECT_GRID_XCORRECTION
#define ASPECT_GRID_XCORRECTION(x) ( ((x)<<3)/9 ) //grids are designed on a 360x240 basis and screen is 320x240, we need x*320/360=x*8/9
#undef ASPECT_GRID_YCORRECTION
#define ASPECT_GRID_YCORRECTION(y) ( (y) ) //y correction for grids made on a 360x240 As the buffer is 720x240 we have no correction here.
//viewport
#undef ASPECT_VIEWPORT_XCORRECTION
#define ASPECT_VIEWPORT_XCORRECTION(x) ASPECT_GRID_XCORRECTION(x) //viewport is 360x240 and screen 320x240, we need x*320/360=x*8/9, equal than grids, used by edgeoverlay
#undef ASPECT_VIEWPORT_YCORRECTION
#define ASPECT_VIEWPORT_YCORRECTION(y) ( (y) )
#undef EDGE_HMARGIN
#define EDGE_HMARGIN 20
//games mappings
#undef GAMES_SCREEN_WIDTH
#undef GAMES_SCREEN_HEIGHT
#define GAMES_SCREEN_WIDTH 360
#define GAMES_SCREEN_HEIGHT 240
#undef ASPECT_GAMES_XCORRECTION
#define ASPECT_GAMES_XCORRECTION(x) ( ((x)<<1) )
#undef ASPECT_GAMES_YCORRECTION
#define ASPECT_GAMES_YCORRECTION(y) ( (y) ) //none
#define CAM_SYNCH 1
#define CAM_CHDK_PTP 1
also,
Index: core/kbd.c
===================================================================
--- core/kbd.c (revision 957)
+++ core/kbd.c (local copy)
@@ -111,7 +111,7 @@
static int nTxtbl[]={0,3,6,9,13,16,20,23};
#endif
-#if defined(CAMERA_ixus870_sd880)
+#if defined(CAMERA_ixus870_sd880) || defined(CAMERA_ixus105_sd1300)
#define ZSTEP_TABLE_SIZE 10
static int nTxtbl[]={0,1,2,3,4,5,6,7,8,9};
#endifand
Index: makefile.inc
===================================================================
--- makefile.inc (revision 957)
+++ makefile.inc (local copy)
@@ -238,6 +238,9 @@
#PLATFORM=a2000
#PLATFORMSUB=100c
+#PLATFORM=ixus105_sd1300
+#PLATFORMSUB=100d
+
#PLATFORM=ixus100_sd780
#PLATFORMSUB=100c
please notice i did the port against revision 957, i'm not sure it will work with latest trunk as i've seen there've been lots of modifications
-
Thanks for the reply. It does not seem to work with the latest 997 release, so I'll dig up an older copy of 957. Thanks!
-
I was actually able to compile it under 997 but had to remove the ptp from the spytask, and also there was no camera_set_led function defined under your lib.c .
I can only get it to boot using autoboot... can't find the "update firmware" option.
-
I've sat down some more to try to get into the code, but being just a basic c++ coder, I'm not used to handling this much code. Most things make sense, but there are a few things that are confusing such as the location for the file browser code. Is that located in one of the LUA files, or what?
2 questions, if I may.
1. When attempting to use the default.bas script (if it loads on startup at all) it appears to be throwing an error of some sort, as a orange text block appears in the lower left corner. Unfortunately, it;s just an orange block, and no text is visible. Do you know why this is? I've attempted to change the color settings for the OSD and nothing makes this valuable information visible.
2. There seems to be a general issue with the file browser, not just loading scripts. Attempting to use the file browser, or load anything (grids, etc) seems to crash the camera. Any ideas on where to start on diagnostics for this file browser functionality? I've spent an hour and a half trying to read about this issue and came up with nothing. If I knew where the file browser code was, I may be able to strip it down to where I could start seeing where it's crashing the camera. I've tried basic things such as clearing everything outta the script directory, moving the script directory to the root, etc, but the file browser still kills the camera.
To be honest, I don't even need the file browser functionality, since I can adjust the default.bas script to fit my needs for aerial photography, since the camera is pretty much dedicated to that use. If you could assist with #1 this would aid me greatly in this pursuit. Thanks for your work thus far.
-
glad you solved... and yes, i didn't look into "update firmware" feature since i was ok with autoboot, sorry
about the issues you have found: i think there's some wrong stub address.. (see platform/ixus105/100d/stubs_*) the only way i know if test the BIN, indentify which call might be wrong and search in the disasm'd code if that's the right address for the defined call.. i gave up on that one since i almost went crazy for the shoot script issue :p
edit: since it happens when loading the file browser, you should check the code where it's crashing. you can "guess" or maybe use a ROMLOG (but, you should search the forums on how to get it, i only followed the "guess what's wrong" path..:s)
also: i think the square is because of wrong colors in the palette (background same as the text's) but i wouldn't know how to change this either (i'm a first-time porter :))
-
Hi,
There is a lot of informations.
So:
1. What do we have actually?
2. What is working and what is not working?
3. Where may we get the files?
4. What is missing before seeing chdk officially supporting 1300IS?
Thanks,
-
Hi, I just read about this project in the latest iEEE Spectrum magazine, and I have an IXUS105 so am very keen to get this working.
Looks like great work by c10ud so far.
I've only got as far as finding out my Firmware Version GM1.00D (1.0.0.0), Adj Ver.006.010
On Canon IXUS 105
P-ID:31F4 PAL D
-
Yeah, does anyone have a working build going? Would anyone mind compiling the latest build and posting it here? Thanks!
-
Where may I get a 100D drop. I tried at drop.io and it is always saying the service is discontinued...
-
Where may I get a 100D drop. I tried at drop.io and it is always saying the service is discontinued...
You can obtain a dump yourself using http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper (http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper)
See http://chdk.wikia.com/wiki/Canon_Basic (http://chdk.wikia.com/wiki/Canon_Basic) and http://chdk.wikia.com/wiki/Canon_Basic/Card_Setup (http://chdk.wikia.com/wiki/Canon_Basic/Card_Setup) for how to prepare a canon script disk.
Note that a dump is only useful if you are a programmer wanting to do a port. If you are, you should read http://chdk.wikia.com/wiki/Adding_support_for_a_new_camera (http://chdk.wikia.com/wiki/Adding_support_for_a_new_camera) and also check out http://chdk.wikia.com/wiki/For_Developers (http://chdk.wikia.com/wiki/For_Developers)
-
http://www.box.net/chdk/6/55272271/536017391 (http://www.box.net/chdk/6/55272271/536017391)
Firmware dump for 105
http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot)
Compiled for 105
http://www.filedropper.com/107_1 (http://www.filedropper.com/107_1)
Dumped my 107
Build for 105 even works with some glitches on ixus 107
(original firmware icons drawed over chdk's
menu not cleared: draws osd menu over previous screen)
Hope someone look at dump...
-
Hi,
Where may I get a 100D drop. I tried at drop.io and it is always saying the service is discontinued...
You can obtain a dump yourself using http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper (http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper)
See http://chdk.wikia.com/wiki/Canon_Basic (http://chdk.wikia.com/wiki/Canon_Basic) and http://chdk.wikia.com/wiki/Canon_Basic/Card_Setup (http://chdk.wikia.com/wiki/Canon_Basic/Card_Setup) for how to prepare a canon script disk.
Note that a dump is only useful if you are a programmer wanting to do a port. If you are, you should read http://chdk.wikia.com/wiki/Adding_support_for_a_new_camera (http://chdk.wikia.com/wiki/Adding_support_for_a_new_camera) and also check out http://chdk.wikia.com/wiki/For_Developers (http://chdk.wikia.com/wiki/For_Developers)
No, I am not a developper but I have some knowledges. Actually it is not port and I will need it before march for a project. So unless someone is working on a build and it will be available in a near future, I think the best I can do is giving a try.
Thanks,
-
Hi,
http://www.box.net/chdk/6/55272271/536017391 (http://www.box.net/chdk/6/55272271/536017391)
Firmware dump for 105
http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot)
Compiled for 105
http://www.filedropper.com/107_1 (http://www.filedropper.com/107_1)
Dumped my 107
Build for 105 even works with some glitches on ixus 107
(original firmware icons drawed over chdk's
menu not cleared: draws osd menu over previous screen)
Hope someone look at dump...
Are you working to port it?
Thanks,
-
Hi,
http://www.box.net/chdk/6/55272271/536017391 (http://www.box.net/chdk/6/55272271/536017391)
Firmware dump for 105
http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot)
Compiled for 105
http://www.filedropper.com/107_1 (http://www.filedropper.com/107_1)
Dumped my 107
Build for 105 even works with some glitches on ixus 107
(original firmware icons drawed over chdk's
menu not cleared: draws osd menu over previous screen)
Hope someone look at dump...
Are you working to port it?
Thanks,
Sorry I'm not working on it.
-
Hi,
http://www.box.net/chdk/6/55272271/536017391 (http://www.box.net/chdk/6/55272271/536017391)
Firmware dump for 105
http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot)
Compiled for 105
http://www.filedropper.com/107_1 (http://www.filedropper.com/107_1)
Dumped my 107
Build for 105 even works with some glitches on ixus 107
(original firmware icons drawed over chdk's
menu not cleared: draws osd menu over previous screen)
Hope someone look at dump...
Are you working to port it?
Thanks,
Sorry I'm not working on it.
I am not able to download the compiled 105. Would you post another URL?
Thanks,
-
Hi,
http://www.box.net/chdk/6/55272271/536017391 (http://www.box.net/chdk/6/55272271/536017391)
Firmware dump for 105
http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot)
Compiled for 105
http://www.filedropper.com/107_1 (http://www.filedropper.com/107_1)
Dumped my 107
Build for 105 even works with some glitches on ixus 107
(original firmware icons drawed over chdk's
menu not cleared: draws osd menu over previous screen)
Hope someone look at dump...
Are you working to port it?
Thanks,
Sorry I'm not working on it.
I am not able to download the compiled 105. Would you post another URL?
Thanks,
Paste http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot) in your browser.
Quoted links are broken.
-
Hi,
Is it correct if the download file is a diskboot.bin?
What is working with this build?
Thanks,
-
Hi,
Is it correct if the download file is a diskboot.bin?
What is working with this build?
Thanks,
Yes just rename it to diskboot.bin
I just compiled c10ud's code.
That will obviously work on 105.
-
Hi,
The file is already name diskboot.bin.
Do you have any idea what is actually working?
Do you know if it will be officially port to chdk soon?
Thanks,
-
i don't have the camera anymore, so i don't think i can improve further the port, sorry
-
Hi,
Is it correct if the download file is a diskboot.bin?
What is working with this build?
Thanks,
Yes just rename it to diskboot.bin
I just compiled c10ud's code.
That will obviously work on 105.
Do you have the uncompile script just because I am curious?
-
i don't have the camera anymore, so i don't think i can improve further the port, sorry
What is working and what is not? Is it possible to get the uncompile script?
-
here's my latest post on the topic:
ok, new source available in http://drop.io/ixus105_sd1300 (http://drop.io/ixus105_sd1300) just download ixus105_0.2.zip and have fun.
I added ptp stuff for easier debug of some stuff, since it's in trunk now.. :)
This version has shoot() fixed, zoom fixed, fl should be ok, gui ok, etc.
tested:
- loading, drawing
- some lua stuff
- exp override
current issues/unfeatures:
- load script = camera shutdown
- save raw = camera shutdown (some stub must be wrong)
- no video override
- edge overlay works but disappears soon
- zebra doesn't seem to be working
- some other overrides does not seem to work correctly
however please notice that i built the code with an old chdk svn version, so it may need a bit of refactor for getting this camera running with latest trunk.
as for the "uncompile" script, what exactly do you mean? i used this script for getting the disassembled firmware: http://chdk.wikia.com/wiki/GPL:disassemble.pl (http://chdk.wikia.com/wiki/GPL:disassemble.pl) and some IDA later
-
Hi,
I am a newbie but what I understand is if something got compile, it is because you start from something uncompile. May be a text file, your code. This is what I mean. Actually, I have the firmware drop and the bin file. But not your coding.
Thanks
-
trunk_ixus105.zip - 0.03MB (http://www.zshare.net/download/84229843a3fa6cbc/)
-
Hi,
I just tried the diskboot.bin
1. With card tricks -->format+make disk bootable
2. Copy the download from here diskboot.bin
3. Create CHDK directory and SCRIPTS subdirectory--> Actually, I have no script but later.
4. WRITE Protect the SDCard
5. Put it inside the camera
6. Press the play button and nothing. The camera did not power on at all.
There is no PS.FIR file.
Any idea?
Thanks,
-
6. Press the play button and nothing. The camera did not power on at all.
This usually means the wrong diskboot for the camera. Are you sure your ixus105 has the same canon firmware version this was built for ?
-
Hi,
I used this one.
www.box.net/chdk/6/55272271/536017391 (http://www.box.net/chdk/6/55272271/536017391) took higher in this thread
1. With Camera version tool, I get Powershot SD1300 IS/IXUS 105/IXY200F Version 100D
2. How can I be sure?? Any other suggestion?
Thanks,
-
http://www.box.net/chdk/6/55272271/536017391 (http://www.box.net/chdk/6/55272271/536017391)
Firmware dump for 105
http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot)
Compiled for 105
Is the compile for 105 D?
-
http://www.box.net/chdk/6/55272271/536017391 (http://www.box.net/chdk/6/55272271/536017391)
Firmware dump for 105
http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot)
Compiled for 105
Is the compile for 105 D?
http://www.filedropper.com/chdk (http://www.filedropper.com/chdk)
Recompiled. Just extract them in SD Card's root directory.
In caminfo.txt you will find ixus105_sd1300-100d (dryos, #12788): MEMISOSIZE used: 0x46292
-
http://www.box.net/chdk/6/55272271/536017391 (http://www.box.net/chdk/6/55272271/536017391)
Firmware dump for 105
http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot)
Compiled for 105
Is the compile for 105 D?
http://www.filedropper.com/chdk (http://www.filedropper.com/chdk)
Recompiled. Just extract them in SD Card's root directory.
In caminfo.txt you will find ixus105_sd1300-100d (dryos, #12788): MEMISOSIZE used: 0x46292
ok, I just gave it a try. I get a memory card error.
Then on the display, I am reading :
CHDK raw
CHDK Firmnware 'chdk 0.9.9'
Build Dec 23 2010 22:27:27
And nothing more.
Any explanation?
Do you have the uncompile chdk?
Do you have any working scripts?
-
Seems to work here: well, to be more accurate, I have the splash screen, and I can browse menus).
I didn't test the functions yet, as I'm not sure to have fully understand what is working exactly hehe :)
@C10ud:
1. Many thanks for your work :)
2. You talked about "shoot()", some LUA stuff and PTP. Could you explain a bit ?
PS: I also have the same bug you describe when attempting to load a script... In fact, I'm trying to find a way to make some automatic "recursive" shooting (for timelapse...).
Any help is appreciated; thanks again !
-
Seems to work here: well, to be more accurate, I have the splash screen, and I can browse menus).
I didn't test the functions yet, as I'm not sure to have fully understand what is working exactly hehe :)
Any help is appreciated; thanks again !
What kind of sd card are you using? I will try another card.
I need it because, I will use it in a sounding balloon.
-
This one:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fwww.fotodiscountworld.com%2Fcatalog%2Fimages%2Fsandisk%25204gb%2520sd%2520Ultra%2520ii%2520www.jpg&hash=cd0e5b296d97b4c634b0e78f571e0ea2)
-
Did you used cardtrick to format your disk?
-
Yes, I followed the tutorial, format with Cardtricks, make bootable etc
-
ok, I reformat the card and i see no more "card error".
1. Where is the ALT button??
2. On the OSD screen, I see "calc" and then there is a small window with "0000 KB/s" and under it: "-00:00:00" then nothing more. How do I get to the menu?
Do you have the samething on your side? I am using a 4GB SDHC Card Nexxtech.
-
@siocnarf
FAQ Q.19 (http://chdk.wikia.com/wiki/FAQ#Q._What_are_the_key_settings_and_shortcuts.3F) says:
Q. What are the key settings and shortcuts?
A. Here is a list of important key settings and shortcuts. Have a look at the firmware usage guide for detailed explanations. Note that you can press and hold down certain keys to simulate pressing this key multiple times, just like your PC keyboard.
camera-specific key settings:
* Enter <ALT> mode:
- direct print button for A and IXUS/SD-series cams
- user selectable button for S-series * ( shortcut by default )
* See the Firmware Usage pages of <ALT> mode and/or Miscellaneous Menu on how to select and use the button of your choice for entering and exiting <ALT> mode.
..................
<lots more keys described>
HTH,
wim
-
With "DISP" key, <alt> appears at the bottom of the window, then "func set" displays the main menu.
-
http://www.box.net/chdk/6/55272271/536017391 (http://www.box.net/chdk/6/55272271/536017391)
Firmware dump for 105
http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot)
Compiled for 105
http://www.filedropper.com/107_1 (http://www.filedropper.com/107_1)
Dumped my 107
Build for 105 even works with some glitches on ixus 107
(original firmware icons drawed over chdk's
menu not cleared: draws osd menu over previous screen)
Hope someone look at dump...
Do you have the files after the firmware is disassemble?
-
Do you have the files after the firmware is disassemble?
See http://chdk.wikia.com/wiki/Loading_dump_to_IDA (http://chdk.wikia.com/wiki/Loading_dump_to_IDA) and http://chdk.wikia.com/wiki/GPL_Tools (http://chdk.wikia.com/wiki/GPL_Tools)
-
IDA 5.0 is free but it does not seems to be enough for that problem.
I am not a GPL specialist but they do not seems to be as efficient as IDA. But some peoples have actually disassemble it so I suppose the easiest way would be to get the disassemble files and then start from it.
-
But some peoples have actually disassemble it so I suppose the easiest way would be to get the disassemble files and then start from it.
What files are you looking for ? IDA files would do you no good unless you had the correct version of IDA. An objdump form binutils is easy to get, if you can't follow the instructions on http://chdk.wikia.com/wiki/GPL_Disassembling (http://chdk.wikia.com/wiki/GPL_Disassembling) you are certainly not going to do anything useful with the output.
You might also be interested in that http://chdk.setepontos.com/index.php?topic=5100.0 (http://chdk.setepontos.com/index.php?topic=5100.0)
-
Seems to work here: well, to be more accurate, I have the splash screen, and I can browse menus).
I didn't test the functions yet, as I'm not sure to have fully understand what is working exactly hehe :)
@C10ud:
1. Many thanks for your work :)
2. You talked about "shoot()", some LUA stuff and PTP. Could you explain a bit ?
PS: I also have the same bug you describe when attempting to load a script... In fact, I'm trying to find a way to make some automatic "recursive" shooting (for timelapse...).
Any help is appreciated; thanks again !
Were you succesfull running a script to making a timelapse with this version?
-
But some peoples have actually disassemble it so I suppose the easiest way would be to get the disassemble files and then start from it.
What files are you looking for ? IDA files would do you no good unless you had the correct version of IDA. An objdump form binutils is easy to get, if you can't follow the instructions on http://chdk.wikia.com/wiki/GPL_Disassembling (http://chdk.wikia.com/wiki/GPL_Disassembling) you are certainly not going to do anything useful with the output.
You might also be interested in that http://chdk.setepontos.com/index.php?topic=5100.0 (http://chdk.setepontos.com/index.php?topic=5100.0)
I am thinking the guy who wrote that documentation was working with linux.
So the commands below are not working under windows:
strings -t x dump.bin > dump.strings
hexdump -C dump.bin > dump.hex
arm-linux-gnu-objdump -m arm -b binary -D dump.bin > dump.dis
What would be the correct commandlines under windows??
-
But some peoples have actually disassemble it so I suppose the easiest way would be to get the disassemble files and then start from it.
What files are you looking for ? IDA files would do you no good unless you had the correct version of IDA. An objdump form binutils is easy to get, if you can't follow the instructions on http://chdk.wikia.com/wiki/GPL_Disassembling (http://chdk.wikia.com/wiki/GPL_Disassembling) you are certainly not going to do anything useful with the output.
You might also be interested in that http://chdk.setepontos.com/index.php?topic=5100.0 (http://chdk.setepontos.com/index.php?topic=5100.0)
I am thinking the guy who wrote that documentation was working with linux.
So the commands below are not working under windows:
strings -t x dump.bin > dump.strings
hexdump -C dump.bin > dump.hex
arm-linux-gnu-objdump -m arm -b binary -D dump.bin > dump.dis
What would be the correct commandlines under windows??
The first two are common utilities, you can find them in cygwin, mingw etc.
The other is part of the GCC binutils, you'll need an arm version to use it. In the pre-compiled GCC 3 toolchain available on the wiki, it's called arm-elf-objdump
-
Seems to work here: well, to be more accurate, I have the splash screen, and I can browse menus).
I didn't test the functions yet, as I'm not sure to have fully understand what is working exactly hehe :)
@C10ud:
1. Many thanks for your work :)
2. You talked about "shoot()", some LUA stuff and PTP. Could you explain a bit ?
PS: I also have the same bug you describe when attempting to load a script... In fact, I'm trying to find a way to make some automatic "recursive" shooting (for timelapse...).
Any help is appreciated; thanks again !
Were you succesfull running a script to making a timelapse with this version?
Nope... and well, didn't have time to test anything lately.
Got an answer from c10ud:
hello, i didn't see your post but with lua, shoot and ptp i am referring to the fact that when doing the basic port, i couldn't test if chdk lua scripts were working (e.g. intervalometer, etc.). so i enabled the ptp extension when building my chdk for ixus105 and executed some test script through USB (as seen in CHDK PTP thread). the "shoot()" script basically snaps a picture, so it helps testing if a) keyboard works (button press/release) b) scripts work Smiley
unfortunately i haven't been able to get what was wrong with running scripts from the camera (i suspect some wrong function address in stubs_entry*.S regarding some string-or-directory-related function)..
So, maybe I'll try through PTP sooner or later.
-
I installed GNUARM and it is installing Cygwin DLL... Do I need installing Cygwin? Is it a windows version?
-
Hi,
1. I installed GNUARM for windows.
2. From the wiki:
In this toybox we have:
arm-elf-objcopy | arm-linux-gnu-objcopy
arm-elf-objdump | arm-linux-gnu-objdump
Here we go:
strings -t x dump.bin > dump.strings
hexdump -C dump.bin > dump.hex
arm-linux-gnu-objdump -m arm -b binary -D dump.bin > dump.dis
3. I tried running
strings -t x dump.bin > dump.strings
hexdump -C dump.bin > dump.hex
but found they did not work.
I ran: arm-elf-strings.exe -t x primary.bin > dump.strings and got no errors. Is it the samething as running strings -t x dump.bin > dump.strings ??
4. About hexdump -C dump.bin > dump.hex
I did not found a way running it??
Thanks,
-
Trust me, if you don't understand how to use a simple program like "strings (http://linux.about.com/library/cmd/blcmdl1_strings.htm)", it is highly unlikely disassembly will be of any use to you.
Here's an example what you would get if you had it working
PRIMARY.BIN: file format binary
Disassembly of section .data:
00000000 <.data>:
0: ea000001 b 0xc
4: 6e6f6167 powvsez f6, f7, f7
8: 796f7369 stmvcdb pc!, {r0, r3, r5, r6, r8, r9, ip, sp, lr}^
c: e59f1150 ldr r1, [pc, #336] ; 0x164
10: e3a00000 mov r0, #0 ; 0x0
14: e5810000 str r0, [r1]
18: e3a01078 mov r1, #120 ; 0x78
1c: ee011f10 mcr 15, 0, r1, cr1, cr0, {0}
20: e3a01000 mov r1, #0 ; 0x0
24: ee071f9a mcr 15, 0, r1, cr7, cr10, {4}
28: ee071f15 mcr 15, 0, r1, cr7, cr5, {0}
2c: ee071f16 mcr 15, 0, r1, cr7, cr6, {0}
30: e3a0003d mov r0, #61 ; 0x3d
-
Trust me, if you don't understand how to use a simple program like "strings (http://linux.about.com/library/cmd/blcmdl1_strings.htm)", it is highly unlikely disassembly will be of any use to you.
Here's an example what you would get if you had it working
PRIMARY.BIN: file format binary
Disassembly of section .data:
00000000 <.data>:
0: ea000001 b 0xc
4: 6e6f6167 powvsez f6, f7, f7
8: 796f7369 stmvcdb pc!, {r0, r3, r5, r6, r8, r9, ip, sp, lr}^
c: e59f1150 ldr r1, [pc, #336] ; 0x164
10: e3a00000 mov r0, #0 ; 0x0
14: e5810000 str r0, [r1]
18: e3a01078 mov r1, #120 ; 0x78
1c: ee011f10 mcr 15, 0, r1, cr1, cr0, {0}
20: e3a01000 mov r1, #0 ; 0x0
24: ee071f9a mcr 15, 0, r1, cr7, cr10, {4}
28: ee071f15 mcr 15, 0, r1, cr7, cr5, {0}
2c: ee071f16 mcr 15, 0, r1, cr7, cr6, {0}
30: e3a0003d mov r0, #61 ; 0x3d
I am believing you. But as I read on the wiki, "if the chdk is not existing then why not doing it yourself". If what you are saying is don't try helping or learning if you don't know then I believe soon or later CHDK will die. What you need is more programmer, more people with knowledge. I am giving a try to learn and doing better. Instead, I woulld like reading: "If you have some knowledge but not enough to do the job, the chdk will help you learn and document it". Actually, I have time to read and try...
Unless a better programmer than me would like port that camera...
-
I am believing you. But as I read on the wiki, "if the chdk is not existing then why not doing it yourself". If what you are saying is don't try helping or learning if you don't know then I believe soon or later CHDK will die. What you need is more programmer, more people with knowledge. I am giving a try to learn and doing better.
I'm trying to give you a realistic idea of what is involved. I'm willing to help (you can check my posting history, I do occasionally help people...), but you have to be able to figure stuff out on your own too. No amount of hand holding is a substitute for this. No one can "just tell you what to do" you have to understand what you are doing. If I had the time, I could tell you every little command line option, and give you exact links to all the tools, but I would have to google for them, and as soon as something didn't work, you'd be stuck again.
Trying to guide someone who has no idea what they are doing through the process would be more work than doing the port.
It's nothing personal, but if you can't use google to figure out how to run a simple command line program, then you aren't equipped to do a port. You should not expect the CHDK forum to teach you basic computer use, or basic programming.
You can teach yourself to be a programmer, but it is a very large undertaking. I was a CS TA many years ago, and in my experience, most of the students would have needed at least a year worth of courses before they had any chance of making a CHDK port.
-
any news plz ?
thank you for your efforts on this port.
-
Still working on it...
-
In an SDM build, I have most things working including edge overlay, scripts, file browser, etc.
Don't have Tv override working or any SDM features that use the live and playback buffers.
CHDK porters will need the following :-
NHSTUB(strcat, 0xFFC841C8) // below EXPORT eventproc_export_atol
NHSTUB(readfastdir, 0xFFE09088) // some way above aReadfdir_c
NHSTUB(ReadFastDir, 0xFFE09088)
NHSTUB(qsort, 0xFFE5BCD4) // long way below LDR R0,[R1,#unk_FFFFFFF8]!
NHSTUB(closedir, 0xFFE08EE4) // above opendir
NHSTUB(closefastdir, 0xFFE08EE4) // above opendir
NHSTUB(LEDDrive, 0xFFD1C3B0) // eventproc_export_LEDDrive
NHSTUB(PT_PlaySound, 0xFFC65DA4) // ;LOCATION: AudioHandle.c:500
NHSTUB(TurnOffBackLight, 0xFFC7F83C) // "TurnOffBackLight"
NHSTUB(TurnOnBackLight, 0xFFC7F854) // "TurnOnBackLight"
NHSTUB(SetFileTimeStamp, 0xffc26df0) // below EXPORT eventproc_export_Lseek
NHSTUB(PutInNdFilter, 0xFFE18F4C) // NdActuator.c
NHSTUB(PutOutNdFilter, 0xFFE18F70)
-
What is an SDM build? May I give a try to your build?
-
What is an SDM build?
http://stereo.jpn.org/eng/sdm/index.htm (http://stereo.jpn.org/eng/sdm/index.htm)
May I give a try to your build?
Sure, just give me a few minutes to upload it.
Here you are :-
http://www.zshare.net/download/862181726bd08b95/ (http://www.zshare.net/download/862181726bd08b95/)
It will boot into Record mode.
-
Is it your intention to fully port it to chdk?
-
Is it your intention to fully port it to chdk?
No.
All of these tasks would keep me occupied 24 hours of the day.
You should also download this :-
http://stereo.jpn.org/eng/sdm/file/common_files.zip (http://stereo.jpn.org/eng/sdm/file/common_files.zip)
Make sure you have the default script time_lapse.bas in the SCRIPTS folder.
-
Hi,
What is missing to port it to chdk?
What should I do with all those files?
Any good intervalometer script?
How does it works?? I am trying to correctly navigate on the interface but with little success.
Thanks,
-
Copy the CHDK folder and subfolders to your card.
On booting, the resident script should be time_lapse.bas.
Enter ALT mode and start the script.
Further details here http://stereo.jpn.org/eng/sdm/tlapse.htm (http://stereo.jpn.org/eng/sdm/tlapse.htm) and here http://stereo.jpn.org/eng/sdm/tlapse2.htm (http://stereo.jpn.org/eng/sdm/tlapse2.htm)
remember, I do not have any overrides working at present.
I have no idea what you need to port to CHDK, I have never done it.
You certainly need to correct the stubs values I have given above,
-
When I start it, I see autostart; how do I remove the autostart?
Will it work only with 2 cameras or if I need only one camera, it will work correctly?
May I get your sources files?
-
Disable it in the Scripts menu.
It most definitely works with just one camera, it is not just for stereo or multiple cameras.
The source files are released when the official SDM 1.85 is released.
I am happy to give you advice on porting to CHDK but I am not an expert at compiling.
Have you managed to compile a CHDK version ?
-
How do I get to the script menu? Once the autostart is appearing, I cannot get in the script menu :(
Finally! When I get to the menu/scripts then load time lapse, the script is not starting there is not picture under DCIM. Do I need something to start the script? ???
-
In the Scripts menu, disable Autostart.
Load the script.
Move the cursor down past the spaces to the script parameters.
What are the first three parameters ?
Press MENU to Exit the Script menu but stay in ALT mode.
Fully press the shutter button to start the script.
What do you see displayed on the screen ?
-
"In the Scripts menu, disable Autostart."
Done
Load the script.
Done. I am loading tlaps.bas
Move the cursor down past the spaces to the script parameters
.
Done
What are the first three parameters ?
0-0 and 7
Press MENU to Exit the Script menu but stay in ALT mode.
Done
"Fully press the shutter button to start the script."
Done
What do you see displayed on the screen ?
Time-lapse 1/60 <ALT> ISO 250
Some writing is appearing may be a fraction of second on the screen and disappearing.
Then no picture at all is taken.
I reformat the disk and reinstall everything. Then I noticed "single shot mode" at the top of the window. What is the firmware version? I am using 100D.
During a test a saw on the screen a camera for may be 1 second then I was thinkging a picture was taken but I found nothing on the camera.
-
The IXUS105 tester will be available after 18:00 GMT.
I will ask him to confirm that the scripts works OK.
From his previous comments, it seems that he has indeed (accidentally) run this script.
-
On which forum?
-
He is not on a forum.
He is someone who has contacted me directly.
EDIT
I can confirm there is a problem with the IXUS105 running the script, probably the option to lock focus after the first image.
Will investigate.
-
To save time, if you want to test this yourself I can post test builds until 1:00 GMT.
-
I can but here it is 1729 EST or 2229 GMT so by the time I will be able...
-
The first thing that happens is that the shutter is half-pressed so that the camera autofocuses.
You should see an led light.
Normally, the focus is then locked.
In this build I have disabled the AFLock function (even though the stubs addresses look correct).
http://www.zshare.net/download/862655573378d291/ (http://www.zshare.net/download/862655573378d291/)
-
-
AFLOCK is autofocus lock.
Progress is very, very slow during the week, especially with different time-zones.
Anyway, try this version http://www.zshare.net/download/863084123190e1b4/ (http://www.zshare.net/download/863084123190e1b4/)
You will see three lines of text on the left and one on the right.
Press the shutter button to exit the script.
Next, try this version http://www.zshare.net/download/86308437080406c3/ (http://www.zshare.net/download/86308437080406c3/)
Do you still see text displayed until you stop the script or does it disappear immediately ?
-
Progress is very, very slow during the week, especially with different time-zones.
I understand. As I appreciate your collaboration, I will work as much as possible to make it work.
Anyway, try this version http://www.zshare.net/download/863084123190e1b4/ (http://www.zshare.net/download/863084123190e1b4/)
OK, format and fully reinstall
You will see three lines of text on the left and one on the right.
I read 10 00:01:40:25 then 3 and Hello Imre !
lol
Next, try this version http://www.zshare.net/download/86308437080406c3/ (http://www.zshare.net/download/86308437080406c3/)
Do you still see text displayed until you stop the script or does it disappear immediately ?
10 00:01:40:25
3 1205
Hello!
The script is remaining until the end
Event after the interruption the script is remaining.
-
@siocnarf
See you are online earlier than usual.
I will upload a test build in a few minutes.
Here you are http://www.zshare.net/download/863533508fbca0e7/ (http://www.zshare.net/download/863533508fbca0e7/)
Does the 'Secs' display update every second ?
In Script menu, does the time-of-day update every second ?
-
my child was online. :)
Bad build.
The len is going out but the display is shutting down. Nothing to do with that.
May be to get faster we may plan a moment we will be both in front of our computer at the same time and use windows live to chat directly.
Here I am GMT -5
-
This build should get you started : http://www.zshare.net/download/86396272b718870f/ (http://www.zshare.net/download/86396272b718870f/)
But before you play with time-lapse, please do this simple test ..
In menu Advanced\Debug parameters enable display of Propcases and set page to 2.
Exit menu.
At wide-angle setting, note value 23 when you half-press the shutter.
It is probably 294.
Now, point the camera VERY close to a VERY bright light.
You should hear the ND filter click into position.
Note the value of 23 when you half-press the shutter.
Normally, I would expect it to be about 580 but the European tester did not find any change.
That would be unheard of.
Repeat at all zoom settings.
The difference in value 23 with filter in and out will be a constant val;ue.
Please report the values.
This is for a function that YOU most definitely need.
-
-
If you are online now I will respond.
-
I am but at the office not at home.
-
OK, let me make a few comments before I continue with the European tester later.
The time-lapse script works, he tested it.
It does not last minutes .. with the default settings it takes three photos at five second intervals.
If you HALF PRESS the shutter and you are not in ALT or MENU mode PropSet 23 WILL change .. it has been tested.
It is a number that defines the effective aperture.
Your camera does not have a mechanical aperture, it has a neutral-density filter that may be swung into or out off position.
PropSet 23 value tells me what position the filter is in.
I need this information so that we can force a high shutter speed for KAP.
Blanking the screen between shots is one of the time-lapse options.
-
Thanks,
I will do the test this evening as I don't have the cameras at work :)
I agree the script is working. No doubt a great job was done.
What is propset 23?
1. What is the ND Filter?
2. There is an error message after 3 minutes of inactivity and the camera shutdown.
3. I am french canadian so it may happens I don't understand what you mean or your language is too "much technical" This is why I might ask for more details. I will cooperate as much as it is possible and as much as you would like me to help. I really appreciate your help.
-
I should have said Propcase.
It means 'property case' .. a strange phrase that refers to numbers that denote various properties of the camera :-
http://chdk.wikia.com/wiki/PropertyCase (http://chdk.wikia.com/wiki/PropertyCase)
An ND filter is a 'neutral density' filter .. Google it.
In the Canon menu, you must have set Shutdown time to three minutes.
See page 116 in the camera manual.
-
There is only one more test that needs to be done.
The European tester can do it tomorrow afternoon if necessary.
However, you may like to try the test.
If you HALF PRESS the shutter and you are not in ALT or MENU mode Propcase 23 WILL change .. it has been tested, see image below.
value 23 will be different at each zoom setting.
Indoors, it is assumed the filter is swung out of position.
I know all the PropCase 23 values for each zoom position with the filter out.
I am now asking you to point the camera at a VERY bright light so that you hear the filter click into position.
What is value 23 ?
Repeat at each zoom position.
It is possible that it does not change, but extremely unlikely.
It has never happened with any other camera.
-
I have the same values as on your screenshot. What do you mean by for each zoom position?
-
This version allows you to set a high shutter speed by forcing the ND filter out :-
http://www.zshare.net/download/864740035b3dd2d2/ (http://www.zshare.net/download/864740035b3dd2d2/)
-
Do I need doing something to enable it by default?
Would it be possible to make it support sdcard bigger than 4Gb?
-
We can only set a higher shutter speed by forcing the ND filter out (if
Canon software intended forcing it in).
Indoors, the ND filter will be out anyway so we will force it in for testing.
SDM will force the shutter speed to be 8x longer than normal.
So, take a photo.
In Bracketing\Overrides menu, force ND filter in and select 'constant
exposure' mode.
Take a photo.
The shutter speed should be longer but the exposure should still be correct.
(outdoors, this is useful for blurring flowing water).
Tomorrow, in bright light, try forcing ND filter out.
Shutter-speed will be 8x faster.
Remember, the photo EXIF information will not show the overriden shutter-speed.
I am trying to add dual-partition support but I cannot get a script called asmify.sh to work on my PC.
I type sh.exe and then ./asmify.sh ixus105.asm ixus105.txt.
The file asmify.sh is simply opened.
It is required to convert an IDA assembly file into a form suitable for compilation.
Don't worry about what the above means, it is intended for others !
-
:D I am happy to have you help me!
From your different contact do you have some with photograph knowledge who might suggest me what settings might be the best to take some near space pictures. I assume a trip of 4 hour and the objective is an altitude of 100 000 feets. The lauch is schedule for mid june.
-
For now, you can start by searching this Forum for suitable posts.
There have been maybe six or so.
-
I was looking for disabling the flash and not found where is the option. Also I was looking for disabling LCD as LCD is not really shut down during the time delay as the histogram is making it appearing.
Any idea?
-
I was looking for disabling the flash
That is simply a canon option, you probably press the left/right/up or down button to select.
I was looking for disabling LCD
that is an option in the time-lapse script.
Look at the script parameters in the Script menu.
-
Would it be good to activate ND filter on a sounding balloon?
-
Well, there is plenty of light, the Canon firmware will have swung the filter in, the balloon could be moving violently so by forcing the filter out the shutter speed will be 8x faster.
-
About the LCD display:
1. The LCD display is off
2. A picture is taken
3. The histogram appear with a small picture of what was taken and other information
4. The LCD come off and so on
In fact I did not found an option to just turn off the display. I found a blanck screen option but it does not turn off the display.
Would it be possible to just make it off? I uncheck the histogram under hist zebra menu and nothing changed.
-
Dual-partition ready for testing.
See separate thread posted some time ago.
-
I will test as soon as I will be back at home.
LCD display? Later?
-
Yes, I will go offline at 1:00 GMT.
-
The latest build with large SD card is working perfectly.
May we do something to shutdown properly the LCD?
-
I was hoping that at weekends the time-zone difference would be less of a problem.
Have you chosen the option in the time-lapse parameters to blank the screen ?
Before that, there is one piece of information that I need.
Temporarily rename DISKBOOT.BIN and load the CHDK version.
Use "Debug Parameters -> Debug data display -> Params" to verify PARAM_FILE_COUNTER (parameter is a long number which increase with every shot).
http://chdk.setepontos.com/index.php?topic=5034.msg56934#msg56934 (http://chdk.setepontos.com/index.php?topic=5034.msg56934#msg56934)
Is the number related to file-counter at 0x38 or 0x3A ?
-
There is no chdk version. The link you provide me is 1400IS mine is a 1300IS. Blanck screen=1
I tried using a chdk version but as soon as I provide the params value the camera shutdown continually everytime. Si I cannot make your test.
-
Blanck screen=1
So, does the time-lapse script blank the screen between shots ?
-
Only when the picture is taken then the screen become blank for may be 1 second only.
-
I will ask someone else to test it tomorrow.
-
A little movie of what I get. Just for making you believing me :)
DSCF4559.7z - 16.30MB (http://www.zshare.net/download/865705943853fd4d/)
-
Try running this script :-
@title backlight
line_1 " Backlight Off"
sleep_for_seconds 3
set_backlight 0
sleep_for_seconds 5
set_backlight 1
end
Does it blank the screen ?
-
The display blank the screen. So what is the conclusion? Did you saw the attachment on the previous post? When I stopped the screen the screen remain blanck so I need to shutdown then turn on the camera again to get the display working.
What is the solution?
-
Well, exactly the same function is used in the time-lapse.
That function calls the appropriate canon firmware function so that must be correct.
Try again with a ten second interval between shots and make sure image review is disabled in the Canon menu.
I did not see the countdown counters displayed in your movie.
What is the text on a blue background on the left of the screen ?
-
Can you use this build http://www.zshare.net/download/866115952244db2c/ (http://www.zshare.net/download/866115952244db2c/)
In RAW menu, enable saving of RAW + DNG header.
take a single photo.
Upload the CRW and HDR file that you will find in folder 100CANON\CRW.
-
Try again with a ten second interval between shots and make sure image review is disabled in the Canon menu.
Better without the image review but at the moment the picture is taken then the LCD come up. In fact the shutdown is only for 2 seconds.
The Text in blue is APF or AFL not sure because there is a battery meter.
crw_hdr.7z - 13.64MB (http://www.zshare.net/download/86617517b7854a4d/)
-
In fact the shutdown is only for 2 seconds.
What happens for the other eight seconds ?
Problem is, this code is common to all cameras, it is not specific to the IXUS105.
It is difficult to see what can be changed.
The Text in blue is APF or AFL
It is 'AFL' (autofocus locked).
Anyway, use this build http://www.zshare.net/download/866605748849379f/ (http://www.zshare.net/download/866605748849379f/)
I would enable blank screen in the actual script in case you forget to enable it in the Script menu.
I have changed this slightly, you can see the initial countdown .. the screen is blanked after the first shot.
-
What happens for the other eight seconds ?
The LCD screen power on showing the countdown.
I will give a try later today. Thanks for your help.
-
The screen is blank only when the picture is taken. Immediately after the screen come up until the next picture is taken.
The count down is appearing only at the first picture.
The problem is still existing. :'(
I am reading the scripts:
@title Time-lapse
@param a first delay minutes
@default a 0
@param b first delay seconds
@default b 10
@param c shoot interval minutes
@default c 0
@param d shoot interval seconds
@default d 10
@param e number of repeats
@default e 3
@param f endless mode N/Y 0/1
@default f 1
@param g single/cont/time/burst
@default g 0
@param h Tv exposures
@default h 3
@param i Focus exposures
@default i 3
@param j bracket Tv/foc/Both 0/2
@default j 0
@param k light/dark/alternate 0/1/2
@default k 2
@param l num of 1/3 EV steps
@default l 3
@param m equal/auto/digi 0-2
@default m 0
@param n focus-step
@default n 50
@param p digiscope focus ref
@default p 500
@param q blank screen N/Y 0/1
@default q 1
@param r shutdown N/Auto/USB 0/1/2
@default r 0
@param s save stack N/Y 0/1
@default s 0
@param t Sunrise mode
@default t 0
@param u TXT/CSV 0/1
@default u 0
time_lapse a, b, c, d, e, f, g, h, i, j, k, l, m, n, p, q, r, s, t, u
end
Where are the commandlines? You are calling time_lapse.bas with the parameters but in time_lapse.bas there is no command??
-
Where are the commandlines?
'time_lapse' is the one and only command required.
-
Does the other european testers have the same result as me?
-
Yes.
There is little that I can do about it, it works on all other cameras.
I blank the screen after every shot.
Maybe it is a timing issue and I try to blank too soon after image capture.
I assume image-review is still Off ?
I will do more tests today.
The version you have also saves RAW plus a separate DNG header.
I will give further details later.
You may like to try getting the colours correct.
-
There is little that I can do about it, it works on all other cameras.
I blank the screen after every shot.
Is the script working in a loop? So may be it shutdown the LCD, take the picture then not shutting down, take the picture?
I f I put the code:
line_1 " Backlight Off"
sleep_for_seconds 3
set_backlight 0
sleep_for_seconds 5
set_backlight 1
Just before the time_lapse commandline would it solve the issue?
Maybe it is a timing issue and I try to blank too soon after image capture.
May be
I assume image-review is still Off ?
Yes
The version you have also saves RAW plus a separate DNG header.
What is a DNG header?
-
What is a DNG header?
It is a small file containing information about the image.
When you 'join' the raw sensor data to it you get a DNG image that can be opened with many programmes.
With SDM, we 'join' the files together on the PC (Windows or Mac).
This makes shooting in RAW mode faster.
Just before the time_lapse commandline would it solve the issue?
You tell me, you have the camera, I do not.
-
You tell me, you have the camera, I do not
I will give a try this evening at home.
I noticed there is frequently build update. Are they available on the web?
-
I will give a try this evening at home.
You will need further information before you try.
I noticed there is frequently build update. Are they available on the web?
SDM 1.85 released this weekend, even if blank_screen not working.
-
But about the 1300IS (Ixus 105) build?
-
Including the IXUS105 and S95.
-
Are you saying we sill stop working on that problem at the weekend?
Even in your script:
set_backlight 0--> Turn the backlight off
set_backlight 1--> Did not turn backlight on.
-
.
-
set_backlight 1--> Did not turn backlight on.
Try including a delay after that before ending the script.
-
Use this new build http://www.zshare.net/download/86703185e6e71739/ (http://www.zshare.net/download/86703185e6e71739/)
It attempts to turn-off the backlight in other parts of the code.
-
You may also like to try the DNG conversion.
Download this file http://www.zshare.net/download/86706280c69ba049/ (http://www.zshare.net/download/86706280c69ba049/)
Ideally, you would use a high-speed card that has just been low-level formatted.
First, delete all files that are in your DCIM folder.
In RAW menu, enable 'Save RAW + DNG header'.
Take a number of photos.
After each shot, 'DNG' will briefly be replaced by the file-saving time in msec.
As a matter of interest, what value is it on average ?
Copy the entire DCIM folder to a location on your PC that has a pathname that does not contain spaces.
e.g. D:\SDM
Also, make a backup copy of the DCIM folder as files will be changed in the PC version.
Create folder \DCIM\200CANON on your PC and move folder DCIM\100CANON\CRW to it.
There should not be a CRW folder remaining in 100CANON.
(at the moment, SDM is unable to get the current folder number using code similar to philmoz's SX30).
Copy process.bat and swap_bytes.exe to folder DCIM.
Finally, install IrfanView complete with plugins.
IrfanView is assumed to be installed in folder C:\Program Files\irfanView and named i_view32.exe.
Double-click process.bat.
Ignore the message regarding RAW files, that is for 'slit' images and there are none in your folders.
If you have done it correctly, DNG files will be created and displayed as a slideshow.
The source files are deleted (!)
Good luck !
Too bad about the colours, that is a job for you http://chdk.wikia.com/wiki/DNG4PS-2/Calibration (http://chdk.wikia.com/wiki/DNG4PS-2/Calibration)
Porting cameras requires a commitment of time by testers :)
-
set_backlight 1--> Did not turn backlight on.
Try including a delay after that before ending the script.
OK doing the test with the delay at the end.
I put 10 seconds. However the LCD did not light up at all even after the last timer.
Use this new build http://www.zshare.net/download/86703185e6e71739/ (http://www.zshare.net/download/86703185e6e71739/)
It attempts to turn-off the backlight in other parts of the code.
Not working well. There a battery meter like flashing. The backlight is not working better.
Porting cameras requires a commitment of time by testers
I will need more time. May be later this evening. What is the usefullness of this procedure?
-
What procedure ?
Porters usually have access to the camera.
I do not have this camera, I rely on testers.
No testing, no port.
-
I know I know :)
-
You may also like to try the DNG conversion.
Download this file http://www.zshare.net/download/86706280c69ba049/ (http://www.zshare.net/download/86706280c69ba049/)
Ideally, you would use a high-speed card that has just been low-level formatted.
First, delete all files that are in your DCIM folder.
In RAW menu, enable 'Save RAW + DNG header'.
Take a number of photos.
After each shot, 'DNG' will briefly be replaced by the file-saving time in msec.
As a matter of interest, what value is it on average ?
From 2238 to 2260
If you have done it correctly, DNG files will be created and displayed as a slideshow.
The source files are deleted (!)
Truely interesting but the batch is not working under windows 7 64 bits >:(
In result.txt, you will find the execution result of your batch. I would recommend rename it as process.cmd instead as process.bat as .bat was for 16 bit OS and CMD is more 32 bit OS.
Too bad about the colours, that is a job for you http://chdk.wikia.com/wiki/DNG4PS-2/Calibration (http://chdk.wikia.com/wiki/DNG4PS-2/Calibration)
Porting cameras requires a commitment of time by testers
I just gave it a try. When I select the CRW file, I get an error message and it does not find the corresponding jpg.
-
From 2238 to 2260
Not bad, but the S95 with SanDisk Extreme III saves raw data in slightly less than one second.
the batch is not working under windows 7 64 bits
A little more information would be helpful.
At which point does it fail ?
For example, comment-out 'swap_bytes' to see if that is the problem.
When I select the CRW file, I get an error message and it does not find the corresponding jpg.
Again, it would help to know the error message.
Put the JPG wherever DNG4PS2 expects to find it, I have not studied this procedure myself yet.
-
Are you saying we sill stop working on that problem at the weekend?
Yes, no further work of any kind will be done.
-
Why not working on that last issue? It is not I don't want to help you but since a week I had a lot of problem and less time (birthday, family problem, etc...) I hope doing more test this evening.
Again be sure, I want doing what you are asking for as test but it is just a time problem. Sincerely, I would like solve the backlight issue.
-
i think about getting an ixus105, can you tell me what the status of the port is? i read this thread but just to clarify, these things do work fine so far?:
saving raw files, adjusting shutter lag, scripts, basic functionality(setting iso,flash,browsing pics...)
so the camera works fine with chdk for everyday use?
Are there any news on the backlight issue? i'm worried about it draining the battery too, is it very hard to fix?
Also, where can i get the latest sdm code? I'm currently installing the chdk toolchain, maybe i can help with porting a little, if coding for a camera is not too hard for me :)
-
Hi,
Yes everything is working with SDM. Just go to Stereo DataMaker web site and download it. Actually the backlight issue was solved as the autostart problem.
Thanks,
-
I've installed CHDK on my Ixus 105. All the thins work.
But there is a problem when i try to use the "Ultra Intervalometer".
If i use single shot, the camera is blocked while taking the first image and the LED is on.
If i use serial shot, the camera is blocked while taking the first image and the led is blinking green/orange.
Do i something wrong?
-
What is the Ultraintervalometer doing more than the one coming with SDM? You should ask microfungy but I am very curious. Which firmware are you using?
-
I downloaded the version from the Stereo DataMaker website. But there is only the "DISKBOOT.BIN".
But where can i find the other files from the CHDK?
Maybe i got old CHDK files. The Diskoot is version 1.85.
I can't find a interval script in the scripts folder. but i have downloaded another timelapse script. but there is the same problem.
-
I downloaded the version from the Stereo DataMaker website. But there is only the "DISKBOOT.BIN".
But where can i find the other files from the CHDK?
Maybe i got old CHDK files. The Diskoot is version 1.85.
I can't find a interval script in the scripts folder. but i have downloaded another timelapse script. but there is the same problem.
On the SDM download page, it says:
Download the firmware version below for your camera and also 'Common_Files.zip'
That's the zip that contains all the other files.
-
Thanks, it works great now :D
-
i tried installing it by extracting both zips to the root of the sdcard, but on the camera the 'update firmware' option doesn't show up.
is the only way to use sdm to use autoboot? if so, does the camera support dual-partition/8gb sdcards?
-
is the only way to use sdm to use autoboot?
Yes.
if so, does the camera support dual-partition/8gb sdcards?
Well, it should but I do not remeber receiving any feedback about this.
It is a feature that member 'siocnarf' was interested in.
-
Hi,
The multi partition is working correctly. I am using a 8Gb card with no problem at all.
Thanks,
-
yep just installed it, though i'd prefer having an option to load it manually since it makes the camera slower (and i have to constantly press a button on start otherwise it turns off again)
also, i enabled raw saving, but when i try to open these with ufraw it says "unsupported file format"
-
i have to constantly press a button on start otherwise it turns off again)
can you explain, no-one has reported such a 'problem'?
The camera automatically switches to Record mode.
You need to convert to DNG : http://stereo.jpn.org/eng/sdm/dng.htm (http://stereo.jpn.org/eng/sdm/dng.htm)
Group member zeno also provides the following support that you may find easier :
http://www.zenoshrdlu.com/sdmdng/ (http://www.zenoshrdlu.com/sdmdng/)
-
i have to constantly press a button on start otherwise it turns off again)
can you explain, no-one has reported such a 'problem'?
The camera automatically switches to Record mode.
i can't reproduce it now anymore ;)
the camera turned on, displayed the canon logo/ the led flashed, and then the camera turned off again..
unless i pressed the right button several times while starting(guess others work too) to switch through the images. then it stayed on and loaded sdm
maybe it had something to do with the amount of pictures??, couldn't think of anything else i changed
You need to convert to DNG : http://stereo.jpn.org/eng/sdm/dng.htm (http://stereo.jpn.org/eng/sdm/dng.htm)
Group member zeno also provides the following support that you may find easier :
http://www.zenoshrdlu.com/sdmdng/ (http://www.zenoshrdlu.com/sdmdng/)
is there some tool for linux, too? i tried ufraw,dcraw,iraw, but so far no success :/
-
the camera turned on, displayed the canon logo/ the led flashed, and then the camera turned off again..
This seems to be happening for quite a few cameras (http://chdk.setepontos.com/index.php?topic=6179.0 (http://chdk.setepontos.com/index.php?topic=6179.0)).
A fix is in the current code base; but needs to be enabled and tested for each camera affected.
Phil.
-
ok i figured out a way to do it on linux by looking at your batch script and using wine :)
wine swap_bytes.exe STR_0037.CRW
cat STR_0037.HDR STR_0037.CRW > test.dng
colours in the dng are not right, but except for that it worked fine
-
colours in the dng are not right
Use this version http://www.zshare.net/download/88688950dc1588b6/ (http://www.zshare.net/download/88688950dc1588b6/)
You will still need to tweak the colours.
I don't know about Linux, but this is the normal procedure :-
http://code.google.com/p/dng4ps2/wiki/HowToCalculateCM (http://code.google.com/p/dng4ps2/wiki/HowToCalculateCM)
http://chdk.wikia.com/wiki/DNG4PS-2/Calibration (http://chdk.wikia.com/wiki/DNG4PS-2/Calibration)
If you decide and succeed in doing it, please post the matrix values.
-
Hi everyone!
I'm new here, I'm an owner of an Ixus 105 and I've recently heard of CHDK. The idea of adding new functionalities to te camera sounds fantastic! However, the wiki says our camera is not supported. I've read the thread and first of all I want to thank the people who has invested their time in this. Now I have to say that despite all the posts and contributions, my little knowledge makes me not having understood many things.
My question is: What is the current development status? Can I add new functionalities to my Ixus 105? I'd be interested in making raw pictures, time-lapses, and some kind of bracketing in order to compose HDR pictures.
I hope someone could answer this basic doubts. Thank you!
-
Also, I'm a little bit confused with SDM. As long as I understand it is intended to get stereographic pictures from two cameras. But I see the Ixus 105 is supported and CHDK seems to come in the package.. is this the Ixus 105 CHDK or is it really not supported as stated in the Wiki? I'm confused..
Thank you!
-
i somehow disabled the sdm osd (can only see the script name when i press alt).
i can get it back temporarily by holding 'func set' and selecting 'single cam', but how can i enable it permanently again?
EDIT: nevermind, i found it.. button display, then func set :)
also, is it possible to upload files to the cam via ptp?
@ironfox:
sdm is a modified version of chdk with focus on creating stereo images, so the camera code may be ported to chdk in a later version http://chdk.wikia.com/wiki/SpecialBuilds (http://chdk.wikia.com/wiki/SpecialBuilds)
(don't know if there might be problems with some 'native'-chdk scripts on sdm, but raw images,timelapses and motion detection work fine on my cam :)
-
Thank you dex, this afternoon I followed the pdf guide included in SDM common_files.zip and succesfully installed SDM into my Ixus 105. I told the installer that the SD card was for the left camera, locked the card and it worked! hehe
I still need to read a lot so that to understand so many menus, but I think I actually made a couple of time-lapses and RAW images ;) I was also able to see the live histogram, that's incredible! I only wonder why the camera was continuously emitting a noise, as if the autofocus was always working, and why a couple of times the menus disappeared, but I guess I only need practise.
By the way, a little doubt, if SDM is a modified version of CHDK, how is it that SDM exists for Ixus 105 before CHDK?
-
I only wonder why the camera was continuously emitting a noise
Never heard of that problem, can you give more information on how to reproduce it ?
if SDM is a modified version of CHDK, how is it that SDM exists for Ixus 105 before CHDK?
Basically, there is code that is common to all cameras (core) and code that is different for each camera (platform).
The SDM and CHDK core codes are different.
As long as the CHDK platform code is available (even if not officially) it is possible for SDM to support the camera.
David
-
is it possible to upload files to the cam via ptp?
For now, you can use WIA-Loader http://stereo.jpn.org/eng/sdm/upload.htm (http://stereo.jpn.org/eng/sdm/upload.htm)
sdm is a modified version of chdk with focus on creating stereo images
SDM has many other convenient features, not just support for photography with multiple cameras.
-
Never heard of that problem, can you give more information on how to reproduce it ?
Well, from the moment I turned on the camera it did a combination of two of the usual sounds without SDM: the one that does when autofocusing (button half-pressed), and the one that does when changing from play mode to live view (opening the lens cover I guess). What seemed strange to me was that these two sounds didn't stop at any moment, the camera kept sounding and sounding. But I'm very new to this, so it may just be one of the SDM features that I still don't know, enabled by default.
Basically, there is code that is common to all cameras (core) and code that is different for each camera (platform).
The SDM and CHDK core codes are different.
As long as the CHDK platform code is available (even if not officially) it is possible for SDM to support the camera.
Ok, so is there an unofficial CHDK for Ixus 105? Is it related with your uploads early in this post? I only want to enable RAW, bracketing and time-lapses.. Which one would you recommend to me, SDM or CHDK?
Thank you for your help!
-
it did a combination of two of the usual sounds without SDM:
.... it may just be one of the SDM features that I still don't know, enabled by default.
That does not make sense.
You have said that it makes the sound without SDM.
Ok, so is there an unofficial CHDK for Ixus 105?
There must be, search the thread.
I only want to enable RAW, bracketing and time-lapses.. Which one would you recommend to me, SDM or CHDK?
Well, I know SDM does all three, no idea about the unofficial CHDK version .. try both, it is just a different DISKBOOT.BIN.
If you use the CHDK folder supplied with Common_files.zip, time_lapse.bas will be the default script.
-
That does not make sense.
You have said that it makes the sound without SDM.
It does make sense, I've told you what the difference with and without SDM is. However, as I've said it might be one of the SDM features I still don't know, which is enabled by default and produces the continuous sound. I wouldn't give it more importance until I found out more.
Well, I know SDM does all three, no idea about the unofficial CHDK version .. try both, it is just a different DISKBOOT.BIN.
If you use the CHDK folder supplied with Common_files.zip, time_lapse.bas will be the default script.
Thank you! this is useful information for me, if SDM does all three then there's no need for me to search and install the unofficial CHDK.
-
Hi again, I've been trying SDM a little these days, and although I've achieved some time-lapses, sometimes I get confused with stereo functionalities I don't need. That's why I decided to try the unofficial CHDK.
Well, I know SDM does all three, no idea about the unofficial CHDK version .. try both, it is just a different DISKBOOT.BIN.
I searched back the thread and downloaded the following DISKBOOT.BIN
Use this new build http://www.zshare.net/download/86703185e6e71739/ (http://www.zshare.net/download/86703185e6e71739/)
It attempts to turn-off the backlight in other parts of the code.
However, after changing the file I'm still getting SDM with exactly the same menus. What am I doing wrong?
-
I try to use a bracketing script on my ixus 105
But noone does work, so i tried to write my own:
@title bracketing
@param a Steps
@default a 32
get_tv96 v
v = v - a
v = v - a
set_tv96 v
shoot
v = v + a
set_tv96 v
shoot
v = v + a
set_tv96 v
shoot
v = v + a
set_tv96 v
shoot
v = v + a
set_tv96 v
shoot
end
but this doesn't work.
The camera "freezes" everytime i try to execute this.
What is going wrong?
-
Hi there,
sorry but i have a question which is probably very easy for you to answer me.
I have a ixus 105 /sd1300 100b Camera and want to make a high altitude (space balloon) project with it. This means i need no take RAW images with a interval of 10 seconds.
Currently i have a powershot canon a480. This is very easy together with the chdk package.
I read that the SDM is somehow able to give me a similar possibility. Is this true, if yes what exactly i have to to.
I would relly appreciate the steps to use my ixus for my next outstanding space balloon project.
If you are interested in my first lauch have a look here (http://spaceballonswitzerland.blogspot.com/ (http://spaceballonswitzerland.blogspot.com/))
It's awesome
thx Fabian form switzerland
-
Hello and welcome Fabian .
The 100b is not yet supported.
I will try to do it later today.
David
-
Hello and welcome Fabian .
The 100b is not yet supported.
I will try to do it later today.
Hey david, thx for the quick reply. It would be so nice
When you could do it. Is it a big change to
another firmware?
This means that i would be able to override
the shutterspeed and the 10 sec speed.
Have a good one.
David
-
Hello and welcome Fabian .
The 100b is not yet supported.
I will try to do it later today.
Hey david, thx for the quick reply. It would be so nice
When you could do it. Is it a big change to
another firmware?
This means that i would be able to override
the shutterspeed and the 10 sec speed.
Have a good one.
David
-
i have just looked and there is no beta CHDK code for 100b or even a firmware dump.
Send me a personal message with an email contact address.
David
-
Hi again, I've been trying SDM a little these days, and although I've achieved some time-lapses, sometimes I get confused with stereo functionalities I don't need. That's why I decided to try the unofficial CHDK.
Well, I know SDM does all three, no idea about the unofficial CHDK version .. try both, it is just a different DISKBOOT.BIN.
I searched back the thread and downloaded the following DISKBOOT.BIN
Use this new build http://www.zshare.net/download/86703185e6e71739/ (http://www.zshare.net/download/86703185e6e71739/)
It attempts to turn-off the backlight in other parts of the code.
However, after changing the file I'm still getting SDM with exactly the same menus. What am I doing wrong?
i guess this was the post with chdk beta: http://chdk.setepontos.com/index.php?topic=5720.msg58435#msg58435 (http://chdk.setepontos.com/index.php?topic=5720.msg58435#msg58435) , but the link mentioned there is dead now :/
http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot)
-
i guess this was the post with chdk beta: http://chdk.setepontos.com/index.php?topic=5720.msg58435#msg58435 (http://chdk.setepontos.com/index.php?topic=5720.msg58435#msg58435) , but the link mentioned there is dead now :/
http://www.filedropper.com/diskboot (http://www.filedropper.com/diskboot)
Thank you dex, shame of the broken link. Doesn't anyone have the CHDK DISKBOOT.BIN stored on his hard drive? It would be great to have it online again.
By the way, I'm trying to use SDM these days and... it's just fantastic, or it'd be if I knew how to use all options hehe, now I'm trying to make some Tv bracketing without the camera stopping with a "Memory card error", I guess there are some options I still have to change.
-
I'm trying to make some Tv bracketing without the camera stopping with a "Memory card error"
The interval between shots is probably too short for the speed of the memory card that you are using.
General SDM information here http://stereo.jpn.org/eng/sdm/index.htm (http://stereo.jpn.org/eng/sdm/index.htm)
-
I've been trying SDM ... sometimes I get confused with stereo functionalities I don't need.
Can you give a bit more information about that ?
You can change the header at the top of the screen, see the options in the Stereo menu.
-
The interval between shots is probably too short for the speed of the memory card that you are using.
That's the first thing I thought, and thus changed the repeat interval to 25s, but it hangs anyway when doing the 3 continuous shots of each repeat. Can I somehow increase the period between shots of a same repeat? I mean, the interval in the time-lapse script changes the time between repeats, but if in each repeat, the camera shots 3, 5, 7... or whatever number of continuous photos, how can I prevent it from doing it too quickly?
Can you give a bit more information about that ?
You can change the header at the top of the screen, see the options in the Stereo menu.
It's just I'm new with all this stuff! ;) Later or sooner I will understand these features, or move to CHDK if that works for me, it's all about reading documentation and taking some photos with the card locked! hehe
Thank you again for you help!
-
Can I somehow increase the period between shots of a same repeat?
No, but I may look at that and upload a new version sometime.
It is still caused by a memory card that is not fast enough.
You should also low-level format the card first.
The colours of the DNG are now far better in the unreleased version.
-
I was looking to use the SDM build since there is not a CHDK build yet but I noticed the only SDM build is for firmware 100d. My firmware is 100c. Is it easy to port between different firmware versions of the same camera version or is that difficult?
-
No, but I may look at that and upload a new version sometime.
It is still caused by a memory card that is not fast enough.
You should also low-level format the card first.
Yes, it must be the memory card. It is a 4GB SDHC but I bought it in China very cheap... even with a low-level format it gives the error. Sometimes all the pictures get actually saved despite the error, sometimes one is corrupt, etc. so I would really appreciate this option of increasing the time between shots.
The colours of the DNG are now far better in the unreleased version.
Great! Looking forward to the release then ;)
-
Looking forward to the release then
This recent version should be OK http://www.zshare.net/download/89336474d993e670/ (http://www.zshare.net/download/89336474d993e670/)
-
Is it easy to port between different firmware versions of the same camera version or is that difficult?
Without having the camera available it is a lot of work, tedious and requires good, constant co-operation with the tester.
-
The 100b is not yet supported.
Here is the build for IXUS105 100B :-
http://www.zshare.net/download/8961058264d1ded1/ (http://www.zshare.net/download/8961058264d1ded1/)
-
IMy firmware is 100c.
Are you still reading this thread ?
If so, I may be able to help.
-
Hi have a Canon IXUS 105 with 1.00D firmware and SDM running on it.
I'm trying to work on a script to ZOOM during VIDEO. The problem is that the camera HANGS after three to four zooms, basically after 2 minutes of operation.
I have concluded (and I might be wrong) that the camera tries to re-focus or autofocus after every zoom. I tried putting on AFL and it gets removed on every zoom. Therefore its confirmed that the camera tries to autofocus after every zoom.
Is there a way to STOP the camera from AUTOFOCUSING after EVERY ZOOM?
Perhaps I'm wrong in the problem in the first place, maybe its some other issue.
Pasting the script below for you guys to check it out if possible:
@title SH Zoom and Focus video
s=7
z=s
set_sync 0 0 0 0
get_prop 12 q
if q=0 then set_prop 12 1
press "shoot_half"
sleep 800
click "shoot_full"
:loop
wait_click
if is_key "zoom_in" then goto "in"
if is_key "zoom_out" then goto "out"
if is_key "up" then goto "up"
if is_key "down" then goto "down"
if is_key "left" then goto "left"
if is_key "right" then goto "right"
if is_key "shoot_half" then goto "changestep"
if is_key "shoot_full" then goto "xend"
if is_key "menu" then goto "menu"
goto "loop"
:changestep
if s>8 then s=1 else s=s+1
z=s
print "step: ",z
goto "loop"
:up
set_focus 65535
print "focus: ", get_focus
goto "loop"
:down
set_focus 0
print "focus: ", get_focus
goto "loop"
:left
set_zoom_speed 100
c=15
do
c=c-1
press "shoot_half"
print "Waiting: ", c
until c=0
print "Done!"
set_zoom_to 0
c=15
do
c=c-1
press "shoot_half"
print "Waiting: ", c
until c=0
print "Done!"
goto "loop"
:right
set_zoom_speed 100
c=15
do
c=c-1
press "shoot_half"
print "Waiting: ", c
until c=0
print "Done!"
set_zoom_to 9
c=15
do
c=c-1
press "shoot_half"
print "Waiting: ", c
until c=0
print "Done!"
goto "loop"
:in
set_zoom_speed 100
get_zoom r
t=r+z
c=15
do
c=c-1
press "shoot_half"
print "Waiting: ", c
until c=0
print "Done!"
if t>8 then print "Full ZOOM or step too HI." else set_zoom_rel z
c=15
do
c=c-1
press "shoot_half"
print "Waiting: ", c
until c=0
print "Done!"
print "zoom in: ", r
goto "loop"
:out
set_zoom_speed 100
get_zoom r
t=r-z
c=15
do
c=c-1
press "shoot_half"
print "Waiting: ", c
until c=0
print "Done!"
if t<1 then print "Fully WIDE or step too LO." else set_zoom_rel -z
c=15
do
c=c-1
press "shoot_half"
print "Waiting: ", c
until c=0
print "Done!"
print "zoom out: ", r
goto "loop"
:menu
set_prop 12 0
end
:xend
press "shoot_full"
set_prop 12 0
end
-
i tried your script, and i get the same problem, freeze+camera crash after 3-4 zooms
tried with these settings:
override focus: enabled
focus setting: man
focus mode: manual
chdk seems to have this feature built-in, would it be possible to add this to sdm, too? :)
-
chdk seems to have this feature built-in, would it be possible to add this to sdm, too? :)
Just to be clear, are you saying this works with a CHDK IXUS105 100D build ?
(zoom speed does not do anything, as with a number of other cameras).
David
-
chdk seems to have this feature built-in, would it be possible to add this to sdm, too? :)
Just to be clear, are you saying this works with a CHDK IXUS105 100D build ?
(zoom speed does not do anything, as with a number of other cameras).
David
no i meant that with chdk it's possible to use zooming in videos without having to use a script, or am i incorrect?
can you point me to where i can get this chdk ixus105 100d build? i searched back in the thread and could only find a dead link :/
-
Implementing optical zoom is normally straightforward.
However, in the original CHDK port it is disabled in two places.
I have now enabled it.
I would guess it still crashes, if so it just means the address of a certain Canon firmware function is incorrect.
So, try this build http://www.zshare.net/download/8973323294a66f56/ (http://www.zshare.net/download/8973323294a66f56/) and operate the zoom lever while recording a movie.
-
Implementing optical zoom is normally straightforward.
However, in the original CHDK port it is disabled in two places.
I have now enabled it.
I would guess it still crashes, if so it just means the address of a certain Canon firmware function is incorrect.
So, try this build http://www.zshare.net/download/8973323294a66f56/ (http://www.zshare.net/download/8973323294a66f56/) and operate the zoom lever while recording a movie.
tried to zoom during movie (without script), but nothing happens
with the script, it crashes after zooming once
-
OK, I need to find the correct firmware address.
The CHDK build that was originally posted does not support it at all.
-
Try this build http://www.zshare.net/download/897356249dd06acf/ (http://www.zshare.net/download/897356249dd06acf/)
-
Try this build http://www.zshare.net/download/897356249dd06acf/ (http://www.zshare.net/download/897356249dd06acf/)
thanks, with this one it works fine :) except just one thing.. could you also add refocusing? :) (also tried the script again it still crashes)
-
Where exactly in the script does it crash ?
Please pinpoint the location.
-
Where exactly in the script does it crash ?
Please pinpoint the location.
i've set "step: " to 1 by half-pressing shutter a few times. then i pressed zoom in, it counts down and the last thing displayed is "Done!"
guess it may be that command? :
(line 129) if t>8 then print "Full ZOOM or step too HI." else set_zoom_rel z
-
set_zoom_rel z
Write a simple script to test that command.
-
First of all I would like to say that MICROFUNGUY is a GENIUS!
The build of SDM microfunguy just posted WORKS. Therefore the need of the script that i created is eliminated. The optical zoom in video works perfectly. I had the camera shut down only ONCE during testing with the new SDM build however all other times it worked like a charm, tested by zooming in and out constantly upto 12 mins in video.
The REFOCUSING or MANUAL FOCUS also works perfectly if you OVERRIDE FOCUS and change it to MAN. Therefore MANUAL FOCUS during video WORKS.
On a sidenote, if you are still testing the script I pasted, I think the reason why it does not work properly if because when it zooms in and out it tries to AUTOFOCUS. But I dont care anymore, because MICROFUNGUY's version of SDM fixed it all.
I would like to ask MICROFUNGUY, if its ok, can you tell us HOW you fixed it? I would really appreciate it if you would tell us what exact changes you made in the SDM build to achieve optical zoom.
Thank you so much.
I would be regularly reading this and MICROFUNGUY and other developers, I'm willing to test for you.
-
can you tell us HOW you fixed it?
It is one of the easiest features to implement.
In camera.h, you have to define zoom during movie is enabled for IXUS105, or more accurately that it is not disabled.
Then, at a certain point in the movie_record task you jump to function unlock_optical_zoom().
That uses Canon firmware function UnsetZoomForMovie.
In the CHDK build that had not been found so the CHDK porter pointed to a 'null sub', a function that does not do anything !
-
Some Requests:
1- While SHOOTING VIDEO, if I go into ALT MENU and go into SDM MENU by pressing MENU, the SDM MENU comes up. I make changes 'on the fly', however the image of the menu REMAINS PASTED on the screen, therefore obstructing the view of the recording video. IS THERE A WAY to make the SDM MENU go away after I'm done using it while I'm recording video?
2- Is it possible to control APERTURE and EV during video shoot?
3- Is it possible to SAVE the changes made in SDM MENU so that upon restart of camera the settings REMAIN?
-
can you tell us HOW you fixed it?
It is one of the easiest features to implement.
In camera.h, you have to define zoom during movie is enabled for IXUS105, or more accurately that it is not disabled.
Then, at a certain point in the movie_record task you jump to function unlock_optical_zoom().
That uses Canon firmware function UnsetZoomForMovie.
In the CHDK build that had not been found so the CHDK porter pointed to a 'null sub', a function that does not do anything !
If you could, could you tell me where this camera.h is located? I tried finding this file and could not.
I suspect its within DISKBOOT.BIN. Is there any program to edit DISKBOOT.BIN? I've got experience in programming so if you'd just point me towards an IDE or something that is available for editing SDM it would be a great help and I could contribute as well. :)
-
if you'd just point me towards an IDE or something that is available for editing SDM it would be a great help and I could contribute as well. :)
With all due respect, it is obvious from your comments that you do not realise what is involved.
You have to download the SDM source code and setup a means of compiling it (known as a 'tool chain').
The file camera.h is in folder 'include' in the SDM source.
-
IS THERE A WAY to make the SDM MENU go away after I'm done using it while I'm recording video?
I have never tried that, I will look at the code but not tonight.
Is it possible to control APERTURE and EV during video shoot?
No, and the IXUS105 does not have an aperture.
Is it possible to SAVE the changes made in SDM MENU so that upon restart of camera the settings REMAIN?
Yes they are saved in file CHDK.CFGx in CHDK folder (where 'x' is a number).
-
Got it, hc
if you'd just point me towards an IDE or something that is available for editing SDM it would be a great help and I could contribute as well. :)
With all due respect, it is obvious from your comments that you do not realise what is involved.
You have to download the SDM source code and setup a means of compiling it (known as a 'tool chain').
The file camera.h is in folder 'include' in the SDM source.
Got it! Cheers :)
-
IS THERE A WAY to make the SDM MENU go away after I'm done using it while I'm recording video?
I have never tried that, I will look at the code but not tonight.
Is it possible to control APERTURE and EV during video shoot?
No, and the IXUS105 does not have an aperture.
Is it possible to SAVE the changes made in SDM MENU so that upon restart of camera the settings REMAIN?
Yes they are saved in file CHDK.CFGx in CHDK folder (where 'x' is a number).
1. If I change the aperture settings then it seems to change it from F2.8 to F8.0 no matter how much or how less you increment it. OR am I wrong, is F refering to something other than aperture? You are therefore certain that there is NO APERTURE SETTINGS in ixus 105?
2. You've already been very kind answering my questions, but I'd like to ask anyway, the build of SDM you posted, the one that has ZOOM working, would it be ok if I ask for its source code as well, so that I could try manipulating it further, starting with the optical zoom enabled superb build of yours.
3. Looking forward to you looking into that MENU being stuck on screen during video. I normally press DISP and then FUNC SET to get out of it, but during video this is not possible.
Cheers
-
You are therefore certain that there is NO APERTURE SETTINGS in ixus 105?
There is no aperture on ANY ixus.
HOWEVER, the following is missing from the IXUS105 entry in camera.h :-
#undef CAM_HAS_IRIS_DIAPHRAGM
That will prevent aperture override options being shown.
You've already been very kind answering my questions
I think that is what forums are for :)
would it be ok if I ask for its source code as well
Yes, but as this is work in progress and not a released build, download the source for SDM 1.85 and I will then tell you the changes.
David
-
You are therefore certain that there is NO APERTURE SETTINGS in ixus 105?
There is no aperture on ANY ixus.
HOWEVER, the following is missing from the IXUS105 entry in camera.h :-
#undef CAM_HAS_IRIS_DIAPHRAGM
That will prevent aperture override options being shown.
You've already been very kind answering my questions
I think that is what forums are for :)
would it be ok if I ask for its source code as well
Yes, but as this is work in progress and not a released build, download the source for SDM 1.85 and I will then tell you the changes.
David
Fair enough, I look forward to the final released version.
On a sidenote I have also noticed that your version of SDM has minimized (though not eradicated) the problem of camera not starting up properly when turning it on, as in sometimes it just gets stuck and turns off with lens half stuck.
As I said the problem is not eliminated, I was thinking, it seems to 'turn on' nicely if I keep the on button pressed while turning the camera on. In normal circumstances, i.e without SDM installed, one flick of on button would turn camera on, which is nice and smooth, and I would like that perhaps in the future version.
However as a further sidenote, I find this 'problem' good in a way, since it minimizes the chances of camera turning on accidently while in the camera bag. Though chances are rare, but if it does ever happen, a cheap camera like IXUS 105 would certainly get the dreaded 'lens error'.
I have also noted that turning the camera on in P mode allows the smoothest turn on process, while doing so in AUTO makes it hang most of the time. Note that even in P it still does hang while turning on at times.
EDIT: I did a bit of research after writing this and came across http://chdk.setepontos.com/index.php?topic=6179.60 (http://chdk.setepontos.com/index.php?topic=6179.60) I wonder if this CAM_STARTUP_CRASH_FILE_OPEN_FIX can be incorporated into SDM for ixus 105?
-
I wonder if this CAM_STARTUP_CRASH_FILE_OPEN_FIX can be incorporated into SDM for ixus 105?
Try it http://www.zshare.net/download/89771686394565ae/ (http://www.zshare.net/download/89771686394565ae/)
-
I wonder if this CAM_STARTUP_CRASH_FILE_OPEN_FIX can be incorporated into SDM for ixus 105?
Try it http://www.zshare.net/download/89771686394565ae/ (http://www.zshare.net/download/89771686394565ae/)
I tested the build you posted above and the result is:
1. The menu being 'stuck in place' problem is still NOT fixed. Currently in P or AUTO its easy to get out of SDM menu by pressing DISP and then SET buttons, which brings Canons inbuilt menu up. However during VIDEO RECORDING, all Canon inbuilt menus are disabled, therefore DISP and SET does nothing, even if you are out of ALT menu by pressing DISP once.
I suggest that there should be an EXIT option in SDM menu so that upon pressing that, the screen would be cleared or refreshed. This would help if SDM menu is accessed during video recording and during P and auto mode as well.
2. The camera crash on startup problem is minimized but NOT eliminated. It did hang atleast 10 times during startup. Most of the times it turns on fine if you keep the ON button pressed for upto 1 to 2 seconds. Behavior noted:
-If you press the on button once, screen flickers nothing happens, camera turns off.
-If you press the on button once, at times it turns on in PLAY mode.
-If you KEEP THE ON BUTTON PRESSED for upto 1 to 2 seconds, the camera turns on but then hangs and turns off, at times leaving the lens zoomed extended. Note that this happens 1 in approximately 5 times.
-If you KEEP THE ON BUTTON PRESSED for upto 1 to 2 seconds, the camera turns on successfully.
-Note that I have also tried to turn off the splash screen however it does not seem to make a difference.
The second problem of hanging during startup is certainly better now, and is not as bothersome as the first problem of menu being stuck in place, and an EXIT option on main SDM menu allowing the user to quit the SDM menu and preferably simultaneously also quit the ALT menu would be a very welcome addition.
Thanks for your effort Microfunguy. :)
-
I was also wondering if the following can be done:
1. Allow recording of 720p videos?
2. Muting of mic during optical zoom in video, and automatically un-muting after zoom level is reached?
3. Manual Auto-Refocusing after optical zoom in video. What I mean by 'Manual Auto-Refocusing' is that currently after optical zoom I do Manual Focus by overriding it in SDM, however can there be an option to 'force' the camera manually by pressing a button to Auto focus again after the zoom?
Cheers.
-
1. Allow recording of 720p videos?
No.
2. Muting of mic during optical zoom in video, and automatically un-muting after zoom level is reached?
As far as I know muting has not been done for any IXUS.
Anyway, you have the source code (for some reason) so you try.
3. Manual Auto-Refocusing after optical zoom in video.
I am afraid there is a backlog of people asking me to do too many things.
Time to call a halt ....
However, the boot problem really need fixing if possible.
In Stereo menu, have you enabled the 'extend lens' option ?
If so, just start the camera with a brief press of the power button.
When it crashes, check what the ROMLOG says.
-
1. Allow recording of 720p videos?
No.
2. Muting of mic during optical zoom in video, and automatically un-muting after zoom level is reached?
As far as I know muting has not been done for any IXUS.
Anyway, you have the source code (for some reason) so you try.
3. Manual Auto-Refocusing after optical zoom in video.
I am afraid there is a backlog of people asking me to do too many things.
Time to call a halt ....
However, the boot problem really need fixing if possible.
In Stereo menu, have you enabled the 'extend lens' option ?
If so, just start the camera with a brief press of the power button.
When it crashes, check what the ROMLOG says.
Microfunguy,
Thanks for the reply. I still havent gotten around to trying out the source code. Even if I do it will take me quite some time to learn, and I'll eventually get there to help you guys by contributing bits.
I understand about you being busy, seem some of your other threads, seems like you're working on a lot of stuff.
About MUTING the microfone, I think its enabled in CHDK. So theoretically it should be possible. Not a big deal though.
About CRASHING, I tried the extended zoom enabled / disabled, still the problem persists. However I have noted it starts up best in AUTO mode, when you keep button pressed for 1 to 2 seconds. So that will do for now. I also noticed that the latest build in which you attempted to fix this crash problem is no different from previous build, that is, turning cam on in AUTO mode by pressing for 1 to 2 seconds works fine in build 5 as well. I will class this problem as 99% solved!
However WHAT I WOULD LIKE FROM YOU, whenever you get the time ofcourse, is to look into creating an EXIT option in the SDM menu so that the user can exit from it and the SDM menu goes off the screen. Pressing MENU again does indeed exit it from the menu, but, the image of menu remains pasted. There is also the problem is SDM menu being there but vanishing randomly, then then you press up and down key and it comes back into view and you realise you're indeed still in the SDM menu. This is definitely something that needs to be solved.
Thanks for your efforts :)
-
I still havent gotten around to trying out the source code.
Hmmm ... now why is that ... maybe you are busy with other things ? :)
About MUTING the microfone, I think its enabled in CHDK.
Tell me which IXUS camera it is enabled for, any one will do.
creating an EXIT option in the SDM menu
Problem is, that works fine with my A620 and the code is not camera dependent.
Do you have a CHDK build that you can test ?
Someone needs to upload that build somewhere.
There is also the problem is SDM menu being there but vanishing randomly, then then you press up and down key and it comes back into view and you realise you're indeed still in the SDM menu. This is definitely something that needs to be solved.
I think that is a general CHDK\SDM problem that has never been solved.
-
There is also the problem is SDM menu being there but vanishing randomly, then then you press up and down key and it comes back into view and you realise you're indeed still in the SDM menu. This is definitely something that needs to be solved.
You yourself just described a trivial workaround, so no, it does not need to be solved. It would be nice to solve.
As Microfunguy says, this applies to all CHDK/SDM ports to some degree. Various people have made improvements on some models, sorting out which ones could be applied generically would be a worthwhile contribution from anyone who wants take the time.
-
There is also the problem is SDM menu being there but vanishing randomly, then then you press up and down key and it comes back into view and you realise you're indeed still in the SDM menu. This is definitely something that needs to be solved.
You yourself just described a trivial workaround, so no, it does not need to be solved. It would be nice to solve.
As Microfunguy says, this applies to all CHDK/SDM ports to some degree. Various people have made improvements on some models, sorting out which ones could be applied generically would be a worthwhile contribution from anyone who wants take the time.
Hi reyalp,
The problem of menu disappearing would be, as you put it, 'nice to solve'. HOWEVER, the problem that I was refering to when saying 'definitely needs to be solved', is the problem of SDM menu being stuck is place if you try to access it while the video recording is on.
Reyalp I also refer you to http://chdk.kernreaktor.org/mantis/view.php?id=260 (http://chdk.kernreaktor.org/mantis/view.php?id=260) where it says you have RESOLVED the issue for 870 IS. I noticed you had an issue with Autofocus during video, so you are certain there is no way to autofocus during video recording?
I refer you to http://chdk.setepontos.com/index.php/topic,1988.0 (http://chdk.setepontos.com/index.php/topic,1988.0) where the talk is on about how tilting the camera makes the canon firmware intercept and redraw the screen therefore wiping the SDM / CHDK menu off the screen. This PROBLEM might be the solution to my problem!
I was also wondering if its possible to change the EV 'on the fly' while video is recording?
-
I still havent gotten around to trying out the source code.
Hmmm ... now why is that ... maybe you are busy with other things ? :)
About MUTING the microfone, I think its enabled in CHDK.
Tell me which IXUS camera it is enabled for, any one will do.
creating an EXIT option in the SDM menu
Problem is, that works fine with my A620 and the code is not camera dependent.
Do you have a CHDK build that you can test ?
Someone needs to upload that build somewhere.
There is also the problem is SDM menu being there but vanishing randomly, then then you press up and down key and it comes back into view and you realise you're indeed still in the SDM menu. This is definitely something that needs to be solved.
I think that is a general CHDK\SDM problem that has never been solved.
Thanks for the reply Microfunguy,
Been lookin at the source code, whoever wrote it must be a genius. I'm only an ASP.NET web application developer, so its the first time I've really looked into this sort of code. However, because I'm so in love with my new camera, I'm dedicating quite some time to get the hang of it. I still havent gotten around to understanding how to 'compile' SDM, however that is something I will figure out on my own. You probably wont see much contribution from me for some time, but I'm very persistent and eventually I'll get the hang.
REGARDING MUTING SOUND, I refer you to your own post (first one) http://chdk.setepontos.com/index.php?topic=1817.0 (http://chdk.setepontos.com/index.php?topic=1817.0) where you say something like "Mute sound during movie zooming (Ewavr).", this was sometime in 2008. However not to worry if it can't be fixed. I actually quite like the zooming sound for some reason!
REGARDING EXIT OPTION IN SDM MENU, you say it works in your A620. Do you mean to say that if you are recording a video and you access SDM menu, you are easily able to exit from it and have it removed from the screen? If so, what exactly do you do to exit from the menu?
I refer you to your own video on youtube http://www.youtube.com/watch?v=XlXc7LfED7w# (http://www.youtube.com/watch?v=XlXc7LfED7w#) where you press the MENU button to exit the menu, and it beautifully exits! Thats something that does not happen in my case. The image of menu remains stuck, but I'm infact out of the menu. In your video watch 1:42 to 1:48 where you press the MENU button to exit.
I wonder what could be causing this in my IXUS 105. Perhaps the screen does not get refreshed?
I also refer you to http://tools.assembla.com/chdk/browser/trunk/lib/ubasic/camera_functions.c?rev=899 (http://tools.assembla.com/chdk/browser/trunk/lib/ubasic/camera_functions.c?rev=899) where there is a console_redraw() function. Perhaps this might lead to a resolve?
I WANT TO TEST A BUILD WITH ALL #UNDEF changed to #DEFINE, I was looking at it and came across that optical zoom option that was undef'd for ixus105 in the camera.h. I couldnt help notice that a few other things are also undef'd there. My question is, if we enable everything, as in leave none with an undef, then would good things happen to my camera, or would bad things happen?
For example under #elif defined (CAMERA_ixus105) you got lots of undefs like:
#undef CAM_HAS_MANUAL_FOCUS
#undef CAM_CAN_UNLOCK_OPTICAL_ZOOM_IN_VIDEO
#define CAM_VIDEO_QUALITY_ONLY 1
#undef CAM_VIDEO_CONTROL
#undef CAM_USE_ZOOM_FOR_MF
#undef CAM_HAS_ERASE_BUTTON
#define CAM_SHOW_OSD_IN_SHOOT_MENU 1
Now I was wondering since I still havent figured out the compliation process, if you could, whenever you have the time at your disposal ofcourse, change all the undefs to define not only in #elif defined (CAMERA_ixus105) but also in Default Values up top. What I'm asking is that could you provide me with a build with EVERYTHING ENABLED FOR IXUS 105 and I'll test it and let you know the effect it has. For example there is this one #undef CAM_VIDEO_CONTROL that I'm curious about, maybe it will unleash a whole lot of more goodies (including muting during zoom)?
Cheers.
-
I still havent gotten around to understanding how to 'compile' SDM
Others can give you better advice about that, in particular member 'whim'.
REGARDING MUTING SOUND, I refer you to your own post
You have the source code and you can look at the CHDK code, where do you see mute zoom implemented for an IXUS ?
For the A620 look right at the bottom of this page http://tools.assembla.com/chdk/browser/trunk/platform/a620/sub/100f/movie_rec.c (http://tools.assembla.com/chdk/browser/trunk/platform/a620/sub/100f/movie_rec.c)
Now look in a similar movie task location for any IXUS.
If so, what exactly do you do to exit from the menu?
I refer you to your own video on youtube http://www.youtube.com/watch?v=XlXc7LfED7w# (http://www.youtube.com/watch?v=XlXc7LfED7w#) where you press the MENU button to exit the menu, and it beautifully exits!
I think you have answered your own question.
I wonder what could be causing this in my IXUS 105.
I have no idea, I do not have an IXUS105 to play with.
if we enable everything, as in leave none with an undef, then would good things happen to my camera
No.
or would bad things happen?
Yes.
#undef CAM_CAN_UNLOCK_OPTICAL_ZOOM_IN_VIDEO
Defining that option would not magically make it work.
The CHDK porter had not found the Canon firmware address for that function, that is why he disabled it.
I found the address of the function so enabled it.
could you provide me with a build with EVERYTHING ENABLED FOR IXUS 105
No, this is silly, honestly ... you do not appreciate what it does.
You need to study the code.
That is what I did, starting from scratch, three years ago and still do not have anywhere near the depth of understanding of some people in this forum.
-
Look at line 544 here http://tools.assembla.com/chdk/browser/trunk/platform/ixus860_sd870/sub/100c/movie_rec.c (http://tools.assembla.com/chdk/browser/trunk/platform/ixus860_sd870/sub/100c/movie_rec.c) for the IXUS860.
It did not work.
-
Reyalp I also refer you to http://chdk.kernreaktor.org/mantis/view.php?id=260 (http://chdk.kernreaktor.org/mantis/view.php?id=260) where it says you have RESOLVED the issue for 870 IS.
This is what I mean by "worked around by various people".
Resolved in this case means I applied the patches provided by mweerden. If you think the same code is applicable to your camera in some way, you are welcome to use it.
I noticed you had an issue with Autofocus during video, so you are certain there is no way to autofocus during video recording?
Huh ? mweerden provided a patch to fix AF in video for that particular port (a port he did originally). I just applied the patch.
-
I still havent gotten around to understanding how to 'compile' SDM
Others can give you better advice about that, in particular member 'whim'.
REGARDING MUTING SOUND, I refer you to your own post
You have the source code and you can look at the CHDK code, where do you see mute zoom implemented for an IXUS ?
For the A620 look right at the bottom of this page http://tools.assembla.com/chdk/browser/trunk/platform/a620/sub/100f/movie_rec.c (http://tools.assembla.com/chdk/browser/trunk/platform/a620/sub/100f/movie_rec.c)
Now look in a similar movie task location for any IXUS.
If so, what exactly do you do to exit from the menu?
I refer you to your own video on youtube http://www.youtube.com/watch?v=XlXc7LfED7w# (http://www.youtube.com/watch?v=XlXc7LfED7w#) where you press the MENU button to exit the menu, and it beautifully exits!
I think you have answered your own question.
I wonder what could be causing this in my IXUS 105.
I have no idea, I do not have an IXUS105 to play with.
if we enable everything, as in leave none with an undef, then would good things happen to my camera
No.
or would bad things happen?
Yes.
#undef CAM_CAN_UNLOCK_OPTICAL_ZOOM_IN_VIDEO
Defining that option would not magically make it work.
The CHDK porter had not found the Canon firmware address for that function, that is why he disabled it.
I found the address of the function so enabled it.
could you provide me with a build with EVERYTHING ENABLED FOR IXUS 105
No, this is silly, honestly ... you do not appreciate what it does.
You need to study the code.
That is what I did, starting from scratch, three years ago and still do not have anywhere near the depth of understanding of some people in this forum.
Microfunguy,
Thanks for the reply.
You have convinced me about no mute issue.
You have convinced me about enabling all options.
The camera being stuck on startup is temporarily resolved by starting it in AUTO mode.
Now only one issue is left for now that I'm still bothering with:
SDM menu image being stuck in place after exiting from menu by pressing MENU button like you do in your video.
To resolve this issue I made a silly little script:
@title SH1981 Refresh Console
print "refreshing"
console_redraw 1
sleep 800
print "refreshed"
end
However it seems to freeze the camera. Well theoretically it does what its supposed to do since you got to restart the camera, haha!
Anyhow I made another observation. In HIST/VIDEO main menu there are two checkboxes (I forgot what they are called since camera is on charge right now) but they were something like refresh original screen and refresh OSD, they are at the bottom of the menu.
This gives me a clue that it would indeed be possible to somehow refresh the screen thus cleaning all imprints of SDM menu left behind. As I mentioned, this problem affects me most when I have video recording on and I want to access the SDM menu. I found a temporary fix for it in P and AUTO mode by keeping DISP button pressed for 2 seconds.
-
Reyalp I also refer you to http://chdk.kernreaktor.org/mantis/view.php?id=260 (http://chdk.kernreaktor.org/mantis/view.php?id=260) where it says you have RESOLVED the issue for 870 IS.
This is what I mean by "worked around by various people".
Resolved in this case means I applied the patches provided by mweerden. If you think the same code is applicable to your camera in some way, you are welcome to use it.
I noticed you had an issue with Autofocus during video, so you are certain there is no way to autofocus during video recording?
Huh ? mweerden provided a patch to fix AF in video for that particular port (a port he did originally). I just applied the patch.
Ah, my apologies reyalp. Anyway that proves that both these problems, of AF during video recording and menu image getting stuck are solvable.
-
Ah, my apologies reyalp. Anyway that proves that both these problems, of AF during video recording and menu image getting stuck are solvable.
Solved on one camera does not necessarily mean solvable on other cameras.
-
Ah, my apologies reyalp. Anyway that proves that both these problems, of AF during video recording and menu image getting stuck are solvable.
Solved on one camera does not necessarily mean solvable on other cameras.
Messaged mweerden bloke...keeping fingers crossed, lets hope it 'can' be solved on my beloved ixus 105 :) Ofcourse microfunguy, the genius, might look at it as well :)
-
Microfun guy,
I wrote to mweerden as suggested by reyalp regarding the following issues:
1. AF during video recording
2. Menu image stuck and screen not refreshed after exiting from SDM menu.
Here is what he replied:
Well, I don't think I solved menus being stuck. Actually, I did the opposite. Wink The menu disappeared because the firmware was "redrawing" (its image without the menu) when it wasn't supposed to be. I'm not sure I can help you with your problem.
As for the AF, all I seem to have done is define CAM_AF_SCAN_DURING_VIDEO_RECORD and found the firmware functions the compiler said were missing (MakeAFScan and ExpCtrlTool_StartContiAE, it seems).
Quote
I wrote a little script
...
However it does not do anything except hang the camera.
This seems to suggest that certain code is not right for your camera. Most likely vid_bitmap_refresh(). This might be related to why your menu sticks. The changes I made for the "other" menu problem were in the same function. Crucial was a lock counter that had to be handled properly (see my first patch and the discussion in the bugtracker). If not done properly you might lock or unlock too many times and the firmware will still think it can not draw when the menu is closed. (The _RefreshPhysicalScreen(1) typically called in the function doubles as unlock.)
Hope this helps.
I hope this would lead to a solution :)
-
Microfunguy,
In your build 6 you seem to have removed the option of OVERRIDE APERTURE. I understand that IXUS 105 has no aperture, however, for some reason, changing the value make the setting go to F8.0 and made the photo visibly darker, while setting it to OFF made the photo visibly lighter.
In your build 5 it is present. I was wondering if in your next build, you could add the option back in. :)
-
You are asking me to fix far too many things at the same time, you have no idea how much work this takes.
Anyway, back to your script.
console_redraw is not supported with current SDM release.
I have now added it but have no idea if it works with IXUS105.
Try this build http://www.zshare.net/download/898740311a203a59/ (http://www.zshare.net/download/898740311a203a59/)
Some stubs addresses seem to be incorrect in the CHDK build, I have changed to this :-
NHSTUB(ScreenLock, 0xFFD8E370)
NHSTUB(ScreenUnlock, 0xFFD8CFBC)
NHSTUB(RefreshPhysicalScreen,0xFFD8CFBC)
vid_bitmap_refresh() is defined as a 'weak' function.
In other words, you can override it with your own code.
The CHDK porter has used :-
void vid_bitmap_refresh()
{
extern int enabled_refresh_physical_screen;
enabled_refresh_physical_screen=1;
_RefreshPhysicalScreen(1);
}
Not sure where 'enabled_refresh_physical_screen' is used, cannot even find its external declaration.
-
Not sure where 'enabled_refresh_physical_screen' is used, cannot even find its external declaration.
It is a variable in the firmware (see stubs_min.S). It seems to act as a lock counter; only when the value is 0 (after unlocking) the firmware will redraw the screen.
NHSTUB(ScreenUnlock, 0xFFD8CFBC)
NHSTUB(RefreshPhysicalScreen,0xFFD8CFBC)
void vid_bitmap_refresh()
{
extern int enabled_refresh_physical_screen;
enabled_refresh_physical_screen=1;
_RefreshPhysicalScreen(1);
}
Here you seem to see what I mentioned. ScreenUnlock and RefreshPhysicalScreen have the seem address; removing the lock and redrawing the display are combined in one function. So if you want to just do the redrawing, you'll have to make sure you return the locking mechanism back to its original state. That doesn't seem to happen here with the result that you probably unlock too many times.
For my port I made it:
void vid_bitmap_refresh()
{
extern int enabled_refresh_physical_screen; // screen lock counter
int old_val = enabled_refresh_physical_screen;
if ( old_val == 0 )
{
_ScreenLock(); // make sure code is called at least once
} else {
enabled_refresh_physical_screen=1; // forces actual redraw
}
_RefreshPhysicalScreen(1); // unlock/refresh
// restore original situation
if ( old_val > 0 )
{
_ScreenLock();
enabled_refresh_physical_screen = old_val;
}
}
-
I deliberately made the addresses of UnLock and RefreshPhysicalScreen the same based on comments in some recent ports.
Earlier ports seem to have two different addresses, rightly or wrongly.
If you are interested, the IXUS105 100D firmware is here http://www.zshare.net/download/89876685b06c807b/ (http://www.zshare.net/download/89876685b06c807b/)
I had better check stubs_min.s for that variable.
EDIT
The CHDK porter has :-
DEF(enabled_refresh_physical_screen, 0x7724+0x30) // @ffd8cfd0
How do we confirm that is correct ?
sub_FFD8CFBC ; CODE XREF: sub_FFD8D020+20p
; _sub_FFD8E1E4__Window.c__0+20p
var_18 = -0x18
var_14 = -0x14
var_10 = -0x10
STMFD SP!, {R1-R5,LR}
ADR R1, aScreenunlock ; "ScreenUnLock"
MOV R0, #0x60
BL _sub_FFC6DEC8__CameraLog.c__237 ; LOCATION: CameraLog.c:237
BL sub_FFD8C5B0
LDR R4, =0x7724
CMP R0, #0
BEQ loc_FFD8D008
ADD R1, SP, #0x18+var_14
ADD R0, SP, #0x18+var_10
BL sub_FFC84014
BL sub_FFD8C5C0
LDR R3, [SP,#0x18+var_14]
MOV R2, #0
STR R3, [SP,#0x18+var_18]
LDR R0, [R4,#4]
LDR R3, [SP,#0x18+var_10]
MOV R1, #0
BL sub_FFD8CC34
loc_FFD8D008 ; CODE XREF: sub_FFD8CFBC+1Cj
LDR R0, [R4,#0x1C]
LDR R1, [R4]
BL sub_FFC83EB8
BL sub_FFD8C61C
LDMFD SP!, {R1-R5,LR}
B sub_FFC83F94
; End of function sub_FFD8CFBC
-
If you are interested, the IXUS105 100D firmware is here http://www.zshare.net/download/89876685b06c807b/ (http://www.zshare.net/download/89876685b06c807b/)
DEF(enabled_refresh_physical_screen, 0x7724+0x30) // @ffd8cfd0
How do we confirm that is correct ?
Compare with similar already finished ports?
I've had a look and based on what I know I would say that enabled_refresh_physical_screen is actually at 0x7724+0x20. This is pretty clear when looking at ScreenLock.
Also note that this doesn't seem clear at all in the function at 0xFFD8CFBC. However, the function below it (at 0xFFD8D020) looks very similar to ScreenLock. In fact, this seems to be ScreenUnlock. It calls the function at 0xFFD8CFBC when the lock counter becomes 0, so that suggests that 0xFFD8CFBC is a RefreshPhysicalScreen that doesn't unlock.
With a bit of luck, changing the addresses for ScreenUnlock and enabled_refresh_physical_screen should fix things.
Edit: This also means that the implementation of vid_bitmap_refresh can probably be removed. Setting the lock counter should not be needed (and is possibly even harmful).
-
Thanks, that makes sense.
I will upload a build for our friend to try.
-
I still havent gotten around to understanding how to 'compile' SDM
Others can give you better advice about that, in particular member 'whim'.
Maybe this (http://chdk.setepontos.com/index.php?topic=845.msg66235#msg66235) is of interest ?
Download support for SDM *) For the moment, this is manual, select
'Import SDM' (in 'Branches..' dialog) to initiate checking; if a
newer version is found, it will be automatically downloaded, unpacked
and lightly post processed (mostly renaming, but will also add
missing /tools directory). In case 'Branches..' is greyed out,
make sure you have 'Allow Internet' checked; in case of a missing
'Import SDM' button, the radio button for 'trunk' must be selected
first (left of the logo)
*) Once downloaded, it can also be compiled, of course, see attached pic ...
cheers,
wim
-
@mweerden
Just to be clear, if we are not overriding vid_bitmap_refresh() why does it matter if ScreenUnlock and enabled_refresh_physical_screen are incorrect as they are not used by any other code anyway ?
-
Just to be clear, if we are not overriding vid_bitmap_refresh() why does it matter if ScreenUnlock and enabled_refresh_physical_screen are incorrect as they are not used by any other code anyway ?
If you are not overriding it then enabled_refresh_physical_screen will indeed not be used. (But should still get the right value if it remains in stubs_min.S, I'd say.)
However, ScreenUnlock should be changed and used in an override of vid_turn_on_updates (instead of RefreshPhysicalScreen, if that's there now).
-
ScreenUnlock should be changed and used in an override of vid_turn_on_updates (instead of RefreshPhysicalScreen, if that's there now).
SDM does not use it.
CHDK calls it from gui_kbd_leave() but the weak version is an empty function.
It only seems to be implemented for a few cameras.
What is the reason for it ?
-
@sh1981
Try this version http://www.zshare.net/download/89881954bd69715d/ (http://www.zshare.net/download/89881954bd69715d/)
-
SDM does not use it.
CHDK calls it from gui_kbd_leave() but the weak version is an empty function.
It only seems to be implemented for a few cameras.
What is the reason for it ?
I'm guessing it is because older cameras don't have it or need it. My camera does need it. Otherwise you get things like disappearing menus when the firmware decides to draw something (e.g. when I turn my camera sideways in playback mode).
-
you get things like disappearing menus when the firmware decides to draw something (e.g. when I turn my camera sideways in playback mode).
As it is only called from gui_kbd_leave() how does it help with that problem ?
EDIT
I guess the keyboard code is being entered and exited every 1/100 sec ... most of the time.
-
As it is only called from gui_kbd_leave() how does it help with that problem ?
If I'm not mistaken, gui_kbd_enter() and gui_kbd_leave() are the function to enter/leave ALT mode (see the "gui_mode =" statements).
-
Yes, but how does that help redrawing the menus if you turn the camera on its side ?
-
Yes, but how does that help redrawing the menus if you turn the camera on its side ?
You don't need to. It stops the firmware from removing the menu. (It will only redraw the shown photo, but that uses a different buffer. Just as the live preview doesn't erase the menu.)
-
I still havent gotten around to understanding how to 'compile' SDM
Others can give you better advice about that, in particular member 'whim'.
Maybe this (http://chdk.setepontos.com/index.php?topic=845.msg66235#msg66235) is of interest ?
Download support for SDM *) For the moment, this is manual, select
'Import SDM' (in 'Branches..' dialog) to initiate checking; if a
newer version is found, it will be automatically downloaded, unpacked
and lightly post processed (mostly renaming, but will also add
missing /tools directory). In case 'Branches..' is greyed out,
make sure you have 'Allow Internet' checked; in case of a missing
'Import SDM' button, the radio button for 'trunk' must be selected
first (left of the logo)
*) Once downloaded, it can also be compiled, of course, see attached pic ...
cheers,
wim
Cheers whim, ill have a look at it :)
-
@sh1981
Try this version http://www.zshare.net/download/89881954bd69715d/ (http://www.zshare.net/download/89881954bd69715d/)
@microfunguy,
Just tried it.
1. The problem of menu image being stuck in place even after pressing MENU persists. Like i mentioned, in normal P and AUTO mode I can evade this problem by long press of DISP button, but this method does not work while video recording is on and SDM menu is accessed.
2. The menu is now certainly very stable, that is, it does not vanish at random times. However note that this problem is only fixed in P mode, in AUTO mode due to face recognition stuff, it still removes it.
This problem number 2 is nice to be fixed but is not vital for me and does not bother me too much. However I class problem number 1, that of menu image being stuck as a big issue.
Would love it if you'd put back that aperture override you removed in build 6, but thats upto you, I liked the way it made it go to F.8 and produced darker images for some reason (although I agree it has no aperture but somehow it did make that effect on pictures).
Really appreciate the work you've put in :)
-
@microfunguy,
Just had a silly idea which might lead to a temporary solution for menu image being stuck in video mode.
There is a file called SDM.rbf which apparently selects the font for the menu.
Now consider this, we somehow make another copy of this SDM.rbf, name it something like INVISIBLE.rbf, and it would have transparent font, transparent background, and another file SMALL.rbf with extremely small font with transparent background.
As a result, while recording in video mode, I could select this font to temporarily exit the menu image thus gaining the full screen visual again without obstruction of the SDM menu.
Trouble is I cant seem to figure out how to edit .rbf file.
Cheers.
-
Trouble is I cant seem to figure out how to edit .rbf file.
Learn to programme, you have the rest of your life .. probably more years than I do :)
I will try adding certain code when ALT mode is entered and exited.
We will see if that makes any difference.
-
Trouble is I cant seem to figure out how to edit .rbf file.
Learn to programme, you have the rest of your life .. probably more years than I do :)
I will try adding certain code when ALT mode is entered and exited.
We will see if that makes any difference.
Finally managed to edit RBF with RBFEditor and err...the plan backfired. It did indeed make the font small but..the screen now got plastered with image of that file explorer which you use to select the RBF file. o well. :/
-
i am not doing any more tonight, try this version http://www.zshare.net/download/8988852507cf6e09/ (http://www.zshare.net/download/8988852507cf6e09/)
@mweerden
In gui_kbd_enter and gui_kbd_leave I added calls to vid_turn_off_updates() and vid_turn_on_updates().
void vid_turn_off_updates()
{
_ScreenLock();
}
void vid_turn_on_updates()
{
_ScreenUnLock();
}
and
NHSTUB(ScreenLock, 0xFFD8E370)
NHSTUB(ScreenUnLock, 0xFFD8D020)
-
i am not doing any more tonight, try this version http://www.zshare.net/download/8988852507cf6e09/ (http://www.zshare.net/download/8988852507cf6e09/)
@mweerden
In gui_kbd_enter and gui_kbd_leave I added calls to vid_turn_off_updates() and vid_turn_on_updates().
void vid_turn_off_updates()
{
_ScreenLock();
}
void vid_turn_on_updates()
{
_ScreenUnLock();
}
and
NHSTUB(ScreenLock, 0xFFD8E370)
NHSTUB(ScreenUnLock, 0xFFD8D020)
@microfunguy,
Just tried it and I'm afriad no, it does not fix the problem of menu image being stuck in place even after exiting it from SDM menu while video recording is on.
I had another thought. There is a little red number counter on top right corner that comes up when you are in SDM menu. Using zoom level, it increments and decrements. I have a hunch it was designed to increase and decrease the menu font. If I am right, then this thing does not work in my IXUS 105. IF it did work, perhaps this would temporarily solve the issue since I could temporarily just reduce the menu font size while I'm recording a video and increase it while recording video to access menu for anything.
-
I have a hunch it was designed to increase and decrease the menu font.
No, it allows you to set the increment value for menu items.
-
Do you see a frame counter at the bottom of the screen in movie mode ?
-
I have a hunch it was designed to increase and decrease the menu font.
No, it allows you to set the increment value for menu items.
@Microfunguy,
Right ok. Got another idea. How about if you enable the canon inbuilt MENU that is accessible by pressing MENU. You enable this during video recording. In normal circumstances, i.e P or AUTO mode, the user would press DISP to exit from ALT menu, then he would press MENU to bring up Canon MENU. Then he would exit from Canon Menu by pressing Menu and that would erase image of SDM menu that was left plastered. This is one of the methods I use to get rid of the image of SDM menu.
Now consider this... while video recording is ON, all Canon inbuilt menus are naturally disabled. How about you enable Canon Menu, so that I follow the same procedure as above, i.e exit from ALT menu by pressing DISP, then press MENU to bring up Canon Menu to get rid of SDM menu image during video recording.
-
Do you see a frame counter at the bottom of the screen in movie mode ?
Bottom right corner, a constantly incrementing counter, yes. Thats the only thing I see at 'bottom' while movie recording is ON.
-
It is 1:30 a.m., I will look at it 'tomorrow'.
-
It is 1:30 a.m., I will look at it 'tomorrow'.
Yea I know, I'm from cornwall myself, pretty late heh... thanks for all your help mate... by the way, who invented stereodatamaker? I have a feeling it was you (might be wrong). You ought to be like..famous :)
-
Is there any way to override the ISO to 6400? I ask this because I just noticed, if I change mode to LOW LIGHT it takes the ISO up to 6400.
-
Finally managed to edit RBF with RBFEditor and err...the plan backfired. It did indeed make the font small but..the screen now got plastered with image of that file explorer which you use to select the RBF file. o well. :/
This makes me wonder if RefreshPhysicalScreen ever works.
Right ok. Got another idea. How about...
If it's not possible to fix in a "proper" manner, you can always just set every pixel to full transparency in vid_bitmap_refresh.
-
Finally managed to edit RBF with RBFEditor and err...the plan backfired. It did indeed make the font small but..the screen now got plastered with image of that file explorer which you use to select the RBF file. o well. :/
This makes me wonder if RefreshPhysicalScreen ever works.
Right ok. Got another idea. How about...
If it's not possible to fix in a "proper" manner, you can always just set every pixel to full transparency in vid_bitmap_refresh.
Great, a temporary fix is fine for me. :)
-
A Roundup of my Issues
Menu Image being Stuck in Video Recording Importance: High
I suppose if nothing else can be done, if the menu font or transparency can be made to set manually somehow then the problem could be resolved temporarily. Can this be done?
Aperture Importance: High
Microfunguy removed aperture after build 5. I understand aperture does not exist in IXUS however let me share some pictures I took in build 5. Note that I have not zoomed the lens in or out between taking the two pictures.
I'd like to know why there is a difference if aperture does not exist?
With F/8
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi53.tinypic.com%2F2s0ecu9.jpg&hash=200a6e088cf33ba3e31d198fa0d99806)
With F/2.8
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi53.tinypic.com%2F2ptyste.jpg&hash=a77139e704fbfa0aca9f813f9a8803bf)
Manually setting ISO Importance: High
I cant seem to find manual setting for ISO in SDM. I noticed that if I change camera mode to Low-Light it forces upto ISO 6400. Can this be done manually in SDM?
Taken at ISO 6400
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi54.tinypic.com%2F29zon5u.jpg&hash=f1eaccaf2a2d8329a2bc10f8537273b5)
Pausing Video Recording Importance: Low
Its a common feature in mobile phone camera where you can temporarily pause the video recording. Can this be done in SDM?
Autofocus during Video Importance: Low
I wonder if this is do-able, or simply cant be achieved for IXUS 105?
-
Microfunguy removed aperture after build 5. I understand aperture does not exist in IXUS however let me share some pictures I took in build 5. Note that I have not zoomed the lens in or out between taking the two pictures.
It sounds like it's putting in the ND filter. There's already an ND override, which is the correct thing to use to for that.
On most cameras IIRC the aperture propcase doesn't affect the ND, but maybe ixus105 is special. The SD990 had manual "aperture" control in the canon firmware which actually controlled the ND, but I don't remember if you could set that with propcases.
FWIW, fancy formatting is unlikely to make people more inclined to help you.
-
Microfunguy removed aperture after build 5. I understand aperture does not exist in IXUS however let me share some pictures I took in build 5. Note that I have not zoomed the lens in or out between taking the two pictures.
It sounds like it's putting in the ND filter. There's already an ND override, which is the correct thing to use to for that.
On most cameras IIRC the aperture propcase doesn't affect the ND, but maybe ixus105 is special. The SD990 had manual "aperture" control in the canon firmware which actually controlled the ND, but I don't remember if you could set that with propcases.
FWIW, fancy formatting is unlikely to make people more inclined to help you.
Well thats why I posted the pictures and if you download them you can probably see the F8 and F2.8 in the properties of that file too. Still havent looked at ND filter in detail though I did give it a try.
Fancy formatting was just my silly attempt at trying to make a round-up summary. haha. I suppose thats why I got the 'rookie' status! Gotta love that 'marquee' effect! :)
-
Well thats why I posted the pictures and if you download them you can probably see the F8 and F2.8 in the properties of that file too. Still havent looked at ND filter in detail though I did give it a try.
It is completely normal for the ND filter value to be included in the aperture recorded in the exif.
-
Outdoors, or pointing at a VERY bright light indoors, take a photo at f2.8 with that previous build.
Override aperture to f8 and take photo again.
If the light is bright enough I am quite sure the photos will be identical (because the Canon firmware will have forced the ND filter in).
-
Outdoors, or pointing at a VERY bright light indoors, take a photo at f2.8 with that previous build.
Override aperture to f8 and take photo again.
If the light is bright enough I am quite sure the photos will be identical (because the Canon firmware will have forced the ND filter in).
Indeed, I tried taking photo of a lightblub, same shutter speed, and the photos were nearly identical. It came out toally white in case of 2.8 however for 8.0 it showed a tiny little bit of lamp shade color (blue).
Note: Tested a bit later with ND Filter set to OUT and photos had visible difference as described above at 2.8 and 8.0. However took two with ND Filter set to IN and photos had NO difference with aperture settings.
I still havent figured out where the ISO override settings are...would love to take an ISO 15 photo..
@Microfunguy, the build I am using is 5. Its the most stable build so far.
-
Discovered another little thing, if I set the cam to LOW LIGHT then override shutter to like 1/2500 n set the cam to continuous mode, it takes pretty fast photos, however some photos end up with 'unidentified photo' error.
I was wondering...
1. Is it possible to override the MP? because low light mode shoots in 2 megapixel, i was wondering if we could manually set it to 2MP..or even 1MP.
2. Ofcourse secondly I was wondering about the ISO so that we could manually set to 6400..currently i set it like that by pointing it towards a dark place.
-
Just noticed why Im getting that unidentified image error in play mode. It cause I was shooting in continuous mode. But the real question is , why? Note that there is nothing wrong with image, the error just shows once.
O well, can live with it :)
-
I still havent figured out where the ISO override settings are...would love to take an ISO 15 photo..
SDM does not support ISO override.
If ISO 15 really worked why do you suppose Canon do not enable it.
Search the forum for discussions of ISO override and show me evidence ISO 15 works.
-
I was wondering...
No need to wonder, you have the camera, you have the source code, you have whim's tool and I presume you have all the time in the World ... don't you ?
I am willing to try to fix menu in movie mode and then the rest is your problem.
I need to confirm _RefreshPhysicalScreen works.
The function draw_restore() uses that and is used throughout the code.
In ALT mode, click the left/right buttons.
Do you browse a series of onscreen displays ?
Does exit from menu work in all shooting modes except movie ?
-
I still havent figured out where the ISO override settings are...would love to take an ISO 15 photo..
SDM does not support ISO override.
If ISO 15 really worked why do you suppose Canon do not enable it.
Search the forum for discussions of ISO override and show me evidence ISO 15 works.
Here is the evidence for low ISO: http://www.youtube.com/watch?v=aSb8OYoKWSw# (http://www.youtube.com/watch?v=aSb8OYoKWSw#)
About the high ISO, i.e 6400, which is accessible in LOW LIGHT mode of canon, are you certain it cannot be overridden by SDM? Perhaps the functionality is not there yet, but its worth having it on things to look out for during development.
-
I was wondering...
No need to wonder, you have the camera, you have the source code, you have whim's tool and I presume you have all the time in the World ... don't you ?
I am willing to try to fix menu in movie mode and then the rest is your problem.
I need to confirm _RefreshPhysicalScreen works.
The function draw_restore() uses that and is used throughout the code.
In ALT mode, click the left/right buttons.
Do you browse a series of onscreen displays ?
Does exit from menu work in all shooting modes except movie ?
Yes I can browse the onscreen displays with left/right. Their image gets stuck as well.
No the exit from menu does not work in other shooting modes, only if u keep the DISP button pressed which basically clears everything off the screen.
Note that exit of the menu in theory works everywhere, including video recording, the issue is of the image being plastered on the screen.
About me having all the time in the world, I do have about 2 months off from work.
This camera is my first camera, as in, ever. Buying it I had only three things in mind, low shutter speed (15 secs), excellent photo quality, and zoom during video. When you enabled the optical zoom for me, that got me real excited. I suppose what I wanted from the camera, I've got it now.
I post my little findings here so that, well, whenever you, or anyone else for that matter, have the time, can look into it and perhaps incorporate it into SDM. Its quite a popular little camera and I should think it would benefit a lot of people. Ofcourse I'm ever willing to test whenever I'm needed.
-
I was also 'wondering' (yep, again), that panasonic FH20 seems to have something called a smart zoom or something. You can like zoom upto 16x with its 8x lens. How does that work? Any chances of that functionality being incorporated into SDM?
-
Midnight is a little late for me to be doing anything else today.
-
I was looking onto the RAW files created by SDM.
Managed to convert them into DNG format, viewed them using Irfanview, they seem to 'work'.
However, DNG seems to be well, Abobe Digital Negative format. So I was wondering, if they can be edited, or rather 'optimized' in a free software. I can't afford to buy Adobe. :(
Edit: Solution
Seems you can download GIMP ...a photo editor thats free..and UFRAW plugin... also got SDMDNG.zip that would convert the CRW to DNG. Still playin around with it. Havnet really figured out what 'benefits' the RAW can give me, but will get there.
-
Try this build http://www.zshare.net/download/899810327d58a3ff/ (http://www.zshare.net/download/899810327d58a3ff/)
-
Here is the evidence for low ISO:
You are joking, a little compressed YouTube video !
Read this :-
http://chdk.setepontos.com/index.php?topic=5641.msg57160#msg57160 (http://chdk.setepontos.com/index.php?topic=5641.msg57160#msg57160)
Anyway, I am not doing ISO override.
-
There is a problem with this SDM on "Bracketing/Overrides".
I set "Tv bracket val..." to [3 Ev] and "Bracketing ty..." to [3 times]
i set my IXUS105 to A/E Lock, and set to continous shooting mode.
When i press shortly the shutter, the camera takes only 1 photo (0 Ev) . Next time +3 Ev, then -3 Ev, +6 Ev, -6 Ev +9 Ev...
When i press longer, it takes photos until i release (0 Ev, +3 Ev, -3 Ev, +6 Ev, -6 Ev, +9 Ev,..)
When i set the camera to custom timer, 0sec, 3times. The camerea shoots 3 photos with 0 eV
-
You need to use the remote switch.
Incidentally, do you have the problem of menu not disappearing when you exit ?
-
Ok i will try with a remote switch.
I had the problem, but don't know which verison. Now with SDM_1.86_IXUS105_100d_9 the menu disappears how it should.
-
Try this build http://www.zshare.net/download/899810327d58a3ff/ (http://www.zshare.net/download/899810327d58a3ff/)
Works perfectly, the problem of menu image being plastered on screen is FIXED. Works even in video recording. Cheers :)
-
Here is the evidence for low ISO:
You are joking, a little compressed YouTube video !
Read this :-
http://chdk.setepontos.com/index.php?topic=5641.msg57160#msg57160 (http://chdk.setepontos.com/index.php?topic=5641.msg57160#msg57160)
Anyway, I am not doing ISO override.
Youve convinced me! :)
-
You need to use the remote switch.
Incidentally, do you have the problem of menu not disappearing when you exit ?
What is a remote switch?
I tried bracketing as well but it does not change the EV value it changes the shutter speed...perhaps thats what its supposed to do?
When I do custom timer sync option enabled, shouldnt it bracket when I put on a custom timer of 10 photos ? If not then I was wondering if there is anyway to bracket with custom timer?
-
What is a remote switch?
http://www.flickr.com/photos/fvdk3d/sets/72157624151791739/ (http://www.flickr.com/photos/fvdk3d/sets/72157624151791739/)
http://www.digi-dat.de/produkte/index_eng.html#SDM_flash (http://www.digi-dat.de/produkte/index_eng.html#SDM_flash)
http://www.gentles.ltd.uk/gentstereo/sdm.htm (http://www.gentles.ltd.uk/gentstereo/sdm.htm)
Ebay Item number: 120610809251
I tried bracketing as well but it does not change the EV value it changes the shutter speed...perhaps thats what its supposed to do?
Correct.
When I do custom timer sync option enabled, shouldnt it bracket when I put on a custom timer of 10 photos ?
'Custom timer Tv-bracketing mode (with USB switch)' at http://stereo.jpn.org/eng/sdm/capture.htm (http://stereo.jpn.org/eng/sdm/capture.htm)
-
Is there any way to turn off the AF assist beam when you got a custom timer on?
-
What is a remote switch?
http://www.flickr.com/photos/fvdk3d/sets/72157624151791739/ (http://www.flickr.com/photos/fvdk3d/sets/72157624151791739/)
http://www.digi-dat.de/produkte/index_eng.html#SDM_flash (http://www.digi-dat.de/produkte/index_eng.html#SDM_flash)
http://www.gentles.ltd.uk/gentstereo/sdm.htm (http://www.gentles.ltd.uk/gentstereo/sdm.htm)
Ebay Item number: 120610809251
I tried bracketing as well but it does not change the EV value it changes the shutter speed...perhaps thats what its supposed to do?
Correct.
When I do custom timer sync option enabled, shouldnt it bracket when I put on a custom timer of 10 photos ?
'Custom timer Tv-bracketing mode (with USB switch)' at http://stereo.jpn.org/eng/sdm/capture.htm (http://stereo.jpn.org/eng/sdm/capture.htm)
Understood. However what I was trying was trying to bracket with custom timer on... I suppose http://stereo.jpn.org/eng/sdm/tlapse.htm (http://stereo.jpn.org/eng/sdm/tlapse.htm) seems to be one way.
-
Well, I must say, I've been having quite a bit of fun with SDM. Havent tried the stereo thing yet, but the RAW images, high and low shutter speed, the optical zoom, amazing!
Was wondering about a few things...suppose they're a bit of 'general' questions but...I'll ask anyway since its related to IXUS 105...
1. You got this setting for BITRATE in video mode. I was playing around with QUALITY set to 99% and although it did not really help the quality, but it did make the file really big. So my question is, what is the optimal QUALITY setting? What is the optimum BITRATE setting? And shall I set it at BITRATE or QUALITY? Currently, after having that traumatic experience of getting a 100MB file after 7 mins of video, ive set it to 0.25 BITRATE. Is this what canon default is?
2. Been shooting in RAW and I realised that if I set it to say ISO 80 (lowest ISO) and put the shutter speed relatively high 1/30 to 1/50 in order to get an action freezing doors, INDOORS, I get a very dim photo, understandably. So I went into RAWTHERAPEE and tweaked the RAW a bit, and ended up with a very noisy photo. Now I took another photo, this time with ISO bumped to 800, let the shutter speed remain relative high at 1/30 to 1/50 and went into RAWTHERAPEE, and quite understandably, there was noise in the photo. However, after tweaking, the result was better than what I had in the first scenario when I had a low ISO but high shutter.
My conclusion was that its better to have a HIGH ISO than a LOW ISO and HIGH SHUTTER SPEED. My question is, am I right in my conclusion?
3. Refering to what I said above in (2), I would want to know what would be the ideal, or well, close to ideal ISO, SHUTTER SPEED and well we wont talk about APERTURE since its always at 2.8, while taking photos INDOORS without flash. I realised, and I might be wrong, that if I set the camera at AUTO and save the photos in RAW, I can later on tweak them to achieve relatively good results.
Is this the best approach to taking photos indoors without flash, i.e setting cam at AUTO and saving as RAW?
4. Ive noticed in certain situations the camera itself puts itself in F8.0 mode. If it does not have an aperture, why does it do it? If it does not do it, why does it lie to me? What is it actually doing? Is it doing that ND filter thing that someone mentioned here earlier?
-
1. You got this setting for BITRATE in video mode. I was playing around with QUALITY set to 99% and although it did not really help the quality, but it did make the file really big. So my question is, what is the optimal QUALITY setting? What is the optimum BITRATE setting? And shall I set it at BITRATE or QUALITY? Currently, after having that traumatic experience of getting a 100MB file after 7 mins of video, ive set it to 0.25 BITRATE. Is this what canon default is?
Just leave the override off to get default. See also http://chdk.setepontos.com/index.php?topic=6006.0 (http://chdk.setepontos.com/index.php?topic=6006.0) ... file size grows, visible quality not so much.
Is it doing that ND filter thing that someone mentioned here earlier?
Yes, this is the ND filter.
-
1. You got this setting for BITRATE in video mode. I was playing around with QUALITY set to 99% and although it did not really help the quality, but it did make the file really big. So my question is, what is the optimal QUALITY setting? What is the optimum BITRATE setting? And shall I set it at BITRATE or QUALITY? Currently, after having that traumatic experience of getting a 100MB file after 7 mins of video, ive set it to 0.25 BITRATE. Is this what canon default is?
Just leave the override off to get default. See also http://chdk.setepontos.com/index.php?topic=6006.0 (http://chdk.setepontos.com/index.php?topic=6006.0) ... file size grows, visible quality not so much.
Is it doing that ND filter thing that someone mentioned here earlier?
Yes, this is the ND filter.
Checked out the thread, I agree with it.
-
Have you managed to create DNG from the raw and header files as described on SDM website ?
http://stereo.jpn.org/eng/sdm/dng.htm (http://stereo.jpn.org/eng/sdm/dng.htm)
-
Have you managed to create DNG from the raw and header files as described on SDM website ?
http://stereo.jpn.org/eng/sdm/dng.htm (http://stereo.jpn.org/eng/sdm/dng.htm)
If you're asking me, yes I have. I use sdmdng.zip that I downloaded from, well I cant remember, probably from the link you pasted. Then I use rawtherapee.
I must add, overwhelming settings its got, however Ive gotten enough hang of it to bring out life from overexposed bits, and reducing noise in high ISO photos.
Overall RAW is a pain really, it doesnt do much for me if I'm shooting in daylight. The only point it does help is when shooting indoors without flash. However I know, I'm not advanced enough to realise its full potential.
Gonna go to newquay and try out the telescope they got at beach to see my luck with digiscoping next.
-
I know, I'm not advanced enough to realise its full potential.
Maybe it does not have much potential on small-sensor 10/12 bit cameras ?
I guess others will have to decide for themselves.
-
I know, I'm not advanced enough to realise its full potential.
Maybe it does not have much potential on small-sensor 10/12 bit cameras ?
I guess others will have to decide for themselves.
Wasted half an hour trying to tweak a photo. Taken at 1/15 f/2.8 ISO 800 no flash...basically it was camera full AUTO mode, I changed nothing at all, camera selected it all.
This is the RAW after editing in rawtherapee
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi54.tinypic.com%2F9tkaar.jpg&hash=e45e497b0e335befdfe223d59b7add37)
This is the jpeg saved by the camera
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi51.tinypic.com%2F27yu7uo.jpg&hash=31d09381e5f06a3a913a9c189f3a10cf)
As is evident, the jpeg produced by the camera is far better than the RAW I tweaked, even my cat agrees.
Now there are a few points to be noted here:
- I'm an amateur, its my first camera.
- I spent half an hour trying to mess with this thing.
I would say, majority of the people would be like me. People professional at handling RAW convertors would be few.
What I would like, is a software, that would 'take' the jpeg produced by the camera, which is good enough, and then tweak it itself to produce a 'better' image out of the RAW. Kind of like clicking 'auto adjust settings' in any ordinary photo editing software like irfanview and getting a bit better saturation and a bit more brightness.
I could, and probably would, spend some time learning how to convert RAW into a jpeg better than camera jpeg. That would be 'good for me', however, it wont benefit the majority, since at this point they would probably give up and stick with the jpeg produced by the camera. However I know as a fact that RAW does have the potential to bring out some details in overexposed areas and reduce noise in photos.
On a sidenote I must say my IXUS 105 produced a good result with ISO 800 even!
So coming back to the issue of searching for a magic software that would take the jpeg from camera into perspective and then automatically tweak it to produce a better image, I did a bit of research and read about DPP or something, some sorta software shipped with canons to edit CR2 files. It apparently takes the camera profile or something. My question is, is something like that possible with 'free' softwares?
EDIT: I just noticed another thing, the jpeg from RAW seems to be bigger than the jpeg right from the camera. Notice how more of the curtain is visible, more of the bottle is visible, the dumbell is visible while in the camera produced jpeg does not have them all. Hmm... ;)
-
As is evident, the jpeg produced by the camera is far better than the RAW I tweaked, even my cat agrees.
Yes. It is only through the heroic image processing that any of these things produce images that aren't complete [admin: avoid swearing please].
The only reason to use raw is if you think your software can turn the [admin: avoid swearing please] from the sensor into not-[admin: avoid swearing please] image better than Canons software can. Canons software is quite good, as you have noticed...
EDIT: I just noticed another thing, the jpeg from RAW seems to be bigger than the jpeg right from the camera. Notice how more of the curtain is visible, more of the bottle is visible, the dumbell is visible while in the camera produced jpeg does not have them all. Hmm... ;)
Yes, jpeg doesn't use the full buffer.
You can see another piece of DSP magic (not entirely unrelated to the above) in there: notice how much the line where the floor and wall meet curves in the raw, and how much straighter it is in the jpeg.
-
I have IXUS 105 / SD1300 IS (firmware 100C). Two quick questions:
1. can the firmware be upgraded to 100D? (not likely based on my search)
2. could someone make some changes and recompile the current 100D version of SDM for 100C?
-
Just leave the override off to get default. See also http://chdk.setepontos.com/index.php?topic=6006.0 (http://chdk.setepontos.com/index.php?topic=6006.0) ... file size grows, visible quality not so much.
@reyalp / (or anyone)
I just checked, and I cant find a way to get the overrides OFF. Apparently there are only two options, bitrate or quality, no OFF. According to http://chdk.wikia.com/wiki/CHDK_for_Dummies#CHDK_Video_features (http://chdk.wikia.com/wiki/CHDK_for_Dummies#CHDK_Video_features) as well, there are only two options. According to your thread http://chdk.setepontos.com/index.php?topic=6006.0 (http://chdk.setepontos.com/index.php?topic=6006.0) you also mention about 'default', however I cant find this 'default' setting.
On the link I just pasted it says 1x is near to canons default. Okay, I'll believe that for a while, but what mode does canon originally operate on, bitrate or quality?
I would also like to know a bit about this statement on the CHDK link I pasted above: Quality means the Canon will record your motion at a constant quality. It means that, if necessary, the camera, by itself, will increase or decrease the compression rate to mantain the video quality constant.
I'd like to know what it means. What is it that the camera is basing the quality on? So lets say, in normal circumstances with Canon default without SDM, if the camera sees an apple, it would automatically drop the bitrate, however with SDM quality override at say 84% it would maintain a constant bitrate at say 1X even though it should drop it to 0.25 after seeing an apple. I want to know what this 'apple' is that determines the quality.
-
Oh, I didn't realize ixus105 was an MJPEG+.AVI camera. Most recent cameras use H264+.MOV. These do the override somewhat differently and only have "default" and "quality" options. I think bitrate 1 should correspond to the default setting if the port was done correctly, but I'm not completely sure.
-
Oh, I didn't realize ixus105 was an MJPEG+.AVI camera. Most recent cameras use H264+.MOV. These do the override somewhat differently and only have "default" and "quality" options. I think bitrate 1 should correspond to the default setting if the port was done correctly, but I'm not completely sure.
Right, cheers. So you say these new cameras only have 'default' and 'quality'. Makes me think even more about my 'apple' problem I mentioned earlier. This means Canon by default sets to quality and not bitrate?
Therefore if Canon (I'm assuming) chooses quality by default, what quality does it choose? I remember in your thread you said you're not sure about 84%.
Under what circumstances does it increase the bitrate when set to quality? I have a feeling it 'reduces' bitrate if the camera is kept still and the scene is stagnant.
-
Right, cheers. So you say these new cameras only have 'default' and 'quality'. Makes me think even more about my 'apple' problem I mentioned earlier. This means Canon by default sets to quality and not bitrate?
No, what CHDK does on H264 cameras is not a useful basis to infer anything about what Canon does on MJPEG cameras. The codec and all the related code (both in CHDK and the original firmware) is completely different.
Therefore if Canon (I'm assuming) chooses quality by default, what quality does it choose? I remember in your thread you said you're not sure about 84%.
You would have to dig into the code to meaningfully speculate about any of this.
-
1. can the firmware be upgraded to 100D? (not likely based on my search)
Essentially, no. As you suspected.
2. could someone make some changes and recompile the current 100D version of SDM for 100C?
Apparently its being worked on. As with everything volunteer, no ETA promised.
-
1. can the firmware be upgraded to 100D? (not likely based on my search)
Essentially, no. As you suspected.
2. could someone make some changes and recompile the current 100D version of SDM for 100C?
Apparently its being worked on. As with everything volunteer, no ETA promised.
According to http://www.canon.co.jp/imaging/IXUS/IXUS_Firmware.html (http://www.canon.co.jp/imaging/IXUS/IXUS_Firmware.html) and microfunguys video http://www.youtube.com/watch?v=XlXc7LfED7w# (http://www.youtube.com/watch?v=XlXc7LfED7w#) firmware CAN be updated.
Perhaps http://chdk.wikia.com/wiki/CHDK-PT_:_A_tool_for_porting_different_firmware_versions_on_the_same_camera (http://chdk.wikia.com/wiki/CHDK-PT_:_A_tool_for_porting_different_firmware_versions_on_the_same_camera) and http://chdk.wikia.com/wiki/SD1300IS#Firmware_info (http://chdk.wikia.com/wiki/SD1300IS#Firmware_info) and http://www.box.net/chdk/1/55272271 (http://www.box.net/chdk/1/55272271) would help too.
However I havent found any update firmware option in the ixus 105 canon menu.
-
According to http://www.canon.co.jp/imaging/IXUS/IXUS_Firmware.html (http://www.canon.co.jp/imaging/IXUS/IXUS_Firmware.html) and microfunguys video http://www.youtube.com/watch?v=XlXc7LfED7w# (http://www.youtube.com/watch?v=XlXc7LfED7w#) firmware CAN be updated.
I keep getting corrected on this. Yes, it is technically possible to upgrade firmware on Canon cameras. However, Canon does not usually provide the necessary files to do so. And the firmware dump files used for CHDK development are not suitable for that purpose.
Your attached video shows SDM being loaded via Canon's "firmware update" method. It does not show the camera firmware itself being updated.
Also, that is a really old web page - check out the Windows 3.1 interface. The camera shown is a 1M pixel unit from 10 years ago.
Perhaps http://chdk.wikia.com/wiki/CHDK-PT_:_A_tool_for_porting_different_firmware_versions_on_the_same_camera (http://chdk.wikia.com/wiki/CHDK-PT_:_A_tool_for_porting_different_firmware_versions_on_the_same_camera) and http://chdk.wikia.com/wiki/SD1300IS#Firmware_info (http://chdk.wikia.com/wiki/SD1300IS#Firmware_info) and http://www.box.net/chdk/1/55272271 (http://www.box.net/chdk/1/55272271) would help too.
Definitely not - but I guess I should change the title of the CHDK-PT wiki page if its causing confusion.
-
According to http://www.canon.co.jp/imaging/IXUS/IXUS_Firmware.html (http://www.canon.co.jp/imaging/IXUS/IXUS_Firmware.html) and microfunguys video http://www.youtube.com/watch?v=XlXc7LfED7w# (http://www.youtube.com/watch?v=XlXc7LfED7w#) firmware CAN be updated.
I keep getting corrected on this. Yes, it is technically possible to upgrade firmware on Canon cameras. However, Canon does not usually provide the necessary files to do so. And the firmware dump files used for CHDK development are not suitable for that purpose.
Also, that is a really old web page - check out the Windows 3.1 interface. The camera shown is a 1M pixel unit from 10 years ago.
Perhaps http://chdk.wikia.com/wiki/CHDK-PT_:_A_tool_for_porting_different_firmware_versions_on_the_same_camera (http://chdk.wikia.com/wiki/CHDK-PT_:_A_tool_for_porting_different_firmware_versions_on_the_same_camera) and http://chdk.wikia.com/wiki/SD1300IS#Firmware_info (http://chdk.wikia.com/wiki/SD1300IS#Firmware_info) and http://www.box.net/chdk/1/55272271 (http://www.box.net/chdk/1/55272271) would help too.
Definitely not - but I guess I should change the title of the CHDK-PT wiki page if its causing confusion.
Well I guess since youre a senior member, you would most certainly be right. Yep, putting it in the CHDK-PT wiki page would help. So glad my camera turned out to be 1.00D by some miracle. lol
-
could someone make some changes and recompile the current 100D version of SDM for 100C?
That will be available very soon.
-
Thank you all for the responses and the great work!
I used CHDK on SD600 and SD770 (borrowed). They worked wonderfully! Will try CHDK with 4GB eye-fi card on SD1300 100C when it is available.
Thanks again!
-
Well I guess since youre a senior member, you would most certainly be right. Yep, putting it in the CHDK-PT wiki page would help. So glad my camera turned out to be 1.00D by some miracle. lol
Just to clarify, the titles (newbie, senior member, guru member) just reflect post count. Waterwingz is right because he knows what he's talking about, not because he's posted a lot ;)
-
Will try CHDK with 4GB eye-fi card on SD1300 100C when it is available.
Get a 100C build here http://www.zshare.net/download/902798705d1d1c04/ (http://www.zshare.net/download/902798705d1d1c04/)
-
@microfunguy / everyone,
Check my script below for INTRAVALOMETER. It works fine except I can't figure out how to TURN OFF LCD while the camera is shooting.
I tried set_backlight 0 , it does work, however when the camera saves the jpeg or gets ready to focus / shoot, the LCD comes back on.
Some have proposed ideas where you get_prop like
rem Turning off LCD display
get_prop 105 e
if c<>0 & e<>2 then
for n=0 to (2-e)
click "display"
next n
endif
Others have given idea of a black screensaver.
However MICROFUNGUY, since you fixed the problem of SDM menu image being stuck, can you use your knowledge to temporarily let a black screen cover the length of the screen, to give the image that the LCD is off? Since the image bug has the ability to be literally plastered, therefore I believe shutter activity or camera saving the jpeg wont affect the black screen.
The second problem with the script is that it simply wont work unless I take a photo in normal P mode or AUTO mode, and then turn to ALT menu and run the script. I tried making the script focus and then take a shot then wait then start the iteration, but that didnt help.
As you can see currently I have REM'd it to remind myself to take a shot first before running the script, and for LCD I would insert the AV wire. However both these solutions are not feasible really.
Here is the script:
rem sh1981
rem Intervalometer with AF
rem Canon IXUS 105 / SD 1300
rem SHOOT cmd enables AF before every shot
rem Put in A/V plug in cam to turn off LCD
@title Intervalometer with AF
@param a Interval (Minutes)
@default a 0
@param b Interval (Seconds)
@default b 0
@param c Interval (10th Seconds)
@default c 0
t=a*60000+b*1000+c*100
n=1
print "IMPORTANT: TAKE PHOTO 1st!"
print "Take photo in P mode,"
print "then ALT, then run script. "
sleep 1500
goto "shot"
:shot
print "Shot number", n
shoot
n=n+1
sleep t
goto "shot"
-
Copy attached sh.bas to your SCRIPTS folder.
Copy sh1.txt to PARAMS folder.
You can make your own sh2.txt to sh9.txt.
You can set Endless mode to Yes.
Load script and use left/right buttons in Script menu to select parameter set 1.
-
Copy attached sh.bas to your SCRIPTS folder.
Copy sh1.txt to PARAMS folder.
You can make your own sh2.txt to sh9.txt.
You can set Endless mode to Yes.
Load script and use left/right buttons in Script menu to select parameter set 1.
Cheers, it solves the problem of having to take a photo before running the script.
However it does not solve the problem of LCD off. It does turn the lcd off, however it comes on again, basically a lot of blinking. Which I must say is even more distracting than having it left on!
There is also a TvB flag that has come up on the screen. Dont know where that came from. I got a feeling its shutter speed ..bracketing, where do I turn it off from?
Perhaps the only solution is to make a sort of screen saver as suggested here http://chdk.kernreaktor.org/mantis/bug_view_page.php?bug_id=65&history=1 (http://chdk.kernreaktor.org/mantis/bug_view_page.php?bug_id=65&history=1) and I was just thinking, that perhaps the bug that you fixed earlier can be re-used to make a sort of image that gets stuck on screen which is black in color.
My aim here is not to really save battery life, but to really have a black screen, or give an illusion of it, if you know what I mean. Ofcourse having the LCD off properly would be best since it would save battery.
Anyway cheers microfunguy cause your script is definitely better with more options and I'll play around with them.
-
Yes, in Bracketing/Overrides menu make sure the EV's are set to '0' (that turns off bracketing).
On my camera, the screen turns on only for a fraction of a second.
Have you turned off the Canon review mode ?
In menu Advanced\DEbug parameters, enable disable of MISCellaneous values.
Plug something into the A/V socket.
Does one of the displayed values consistently change ?
If so, what are the two values ?
EDIT
Of course, to see the values when the plug is inserted you will have to plugin an external display !
-
Microfunguy,
The 100C build loads correctly and your Intervalometer script works great! Tried some motion detection scripts and played with the parameters in them; the camera freezes a lot. :-) No big deal, continue trying different things.
Thank you very much for the 100C build!
-
Copy attached sh.bas to your SCRIPTS folder.
Copy sh1.txt to PARAMS folder.
You can make your own sh2.txt to sh9.txt.
You can set Endless mode to Yes.
Load script and use left/right buttons in Script menu to select parameter set 1.
@microfunguy,
Yes, my camera has same behavior, it 'flickers' the screen for a fraction of a second. However I want it to be totally off. Perhaps the solution could be plastering a black image on the screen?
Yes, I did turn EV in bracketing off, however the script brings it up again. Note that all values in script are set to 0 (except backlight and for endless shooting).
Yes, Canon Review mode if OFF.
Yes, enabled misc values, plugged in the AV into the telly, the values changed as follows
Value 1: (1)57d447c8
Value 2: 384830(1-3)0(8)9
Value 3: 10(3-2)7c0(f)b
Note that above, the values in brackets are what changed in the place. E.g in case of value 3, the first 3 digits are 107, later on they became 103 and sometimes 102. Similarly in Value 1, first 3 values i.e 57d at times changed to 17d.
Also note that the script at times (rarely) jammed, leaving the camera blank with orange and green led flashing. This usually happened when you ENDED the script.
Therefore so far the conclusion is that LED cannot be fully turned off and flickers for a fraction of a second, but the problem of script starting smoothly is solved, and I dont have a take a test photo before running the script.
I was also playing around with motion detection script and LED cannot be turned off in that either. Any idea if LED can be totally turned off in the following script if possible?
rem Fudgey's Fast/Slow/Video Motion Detector with masks. For models with no video button.
rem See MDFB-080914.txt for documentation.
rem Modified to support 'show sample points' option and turn-off synch mode (SDM 1.82 and later)
@title Fast MD 080914
@param a Columns
@default a 3
@param b Rows
@default b 3
@param c Threshold (0-255)
@default c 10
@param g Burst/Review/Video time (s)
@default g 0
@param d Compare Interval (ms)
@default d 7
@param h Pixel Step (pixels)
@default h 40
@param f Channel (0U,1Y,2V,3R,4G,5B)
@default f 1
@param n Timeout (10s of seconds)
@default n 30
@param e Trigger Delay (0.1 sec)
@default e 5
@param q Show sample points
@default q 1
@param r Show sample cells
@default r 1
@param i Masking (0=No 1=Mask 2=Use)
@default i 0
@param j - Mask Columns Left
@default j 0
@param k - Mask Columns Right
@default k 0
@param l - Mask Rows Top
@default l 0
@param m - Mask Rows Bottom
@default m 0
@param o Shoot fast=0,slow=1,test=2
@default o 2
if a<1 then a=1
if b<1 then b=1
if i<0 then i=0
if i>2 then i=2
if j<0 then j=0
if k<0 then k=0
if l<0 then l=0
if m<0 then m=0
if j>a then j=a
if k>a then k=a
if l>b then l=b
if m>b then m=b
if g<0 then g=0
if f<0 then f=1
if f>5 then f=1
if f=0 then print "Channel: U chroma"
if f=1 then print "Channel: Luminance"
if f=2 then print "Channel: V chroma"
if f=3 then print "Channel: Red"
if f=4 then print "Channel: Green"
if f=5 then print "Channel: Blue"
if n<1 then n=1
if q<0 then q=0
if q>0 then q=32
if r<0 then r=0
e=e*100
g=g*1000
n=n*10000
set_sync 0 0 0 0
P=get_video_button
if P=1 then goto "VideoButtonError"
P=get_mode
if P=1 then goto "PlayModeError"
rem get_mode returns 2 if a we are in video mode (and the camera has no video button)
if P=2 then p=1 else p=0
P=get_flash_mode
if P=2 then goto "SkipFlashWarning"
print "WARNING: Flash is not"
print "disabled. May cause "
print "odd behavior. "
:SkipFlashWarning
if o=0 and p=1 then goto "fast_video_md"
if o=1 and p=1 then goto "slow_video_md"
if o=1 and p=0 then goto "slow_md"
if o=2 then goto "test_md"
print "Fast react photo MD"
:fast_md_loop
t=0
do
release "shoot_half"
press "shoot_half"
do
P=get_shooting
until P=1
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, 9+q, h, e
until t>0
let X=get_tick_count
:contloop1
let U=get_tick_count
let V=(U-X)
if V<g then goto "contloop1"
release "shoot_full"
release "shoot_half"
do
P=get_shooting
until P<>1
goto "fast_md_loop"
:slow_md
rem print "Slow react photo MD"
:slow_md_loop
t=0
do
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, q, h, e
until t>0
if g>0 then goto "contshoot2" else shoot
goto "slow_md_loop"
:contshoot2
press "shoot_full"
let X=get_tick_count
:contloop2
let U=get_tick_count
let V=(U-X)
if V<g then goto "contloop2"
release "shoot_full"
release "shoot_half"
do
P=get_shooting
until P<>1
goto "slow_md_loop"
:fast_video_md
if g<1 then g=1000
print "Fast react video MD"
:fast_video_md_loop
t=0
do
release "shoot_half"
press "shoot_half"
sleep 1000
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, 9+q, h, e
until t>0
rem press "shoot_full" was done by md_detect_motion
print "starting video record"
sleep 300
release "shoot_full"
let X=get_tick_count
:fastvideowaitloop
let U=get_tick_count
let V=(U-X)
if V<g then goto "fastvideowaitloop"
click "shoot_full"
print "ending video record"
rem Need to wait or shoot_half won't work and loop will work like slow react loop:
sleep 1000
goto "fast_video_md_loop"
:slow_video_md
if g<1 then g=1000
rem Focusing takes time => add a second to make length argument a bit more accurate.
g=g+1000
print "Slow react video MD"
:slow_video_md_loop
t=0
do
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, q, h, e
until t>0
press "shoot_full"
sleep 300
release "shoot_full"
print "starting video record"
let X=get_tick_count
:slowvideowaitloop
let U=get_tick_count
let V=(U-X)
if V<g then goto "slowvideowaitloop"
click "shoot_full"
print "ending video record"
goto "slow_video_md_loop"
:test_md
print "MD test, no shooting."
N=0
:test_md_loop
t=0
do
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, q, h, e
until t>0
N=N+1
print t, "cells, trigger ", N
goto "test_md_loop"
:PlayModeError
print "MDFB script ERROR:"
print "Not in REC mode, exiting."
end
:VideoButtonError
print "MDFB script ERROR:"
print "Incompatible camera! Try"
print "MDFB VideoButtonModels"
print "version."
end
-
Before looking at motion detection, when you plug A/V into a TV I need to know if ONE character of one of the values immediately changes and stays changed.
I am not interested in values that randomly change.
-
@sh1981 : I'm enjoying following your posts on this thread but they would be a bit easier to read if you could maybe use the "Insert Code" tool so that they are not so long ? No big deal.
rem Fudgey's Fast/Slow/Video Motion Detector with masks. For models with no video button.
rem See MDFB-080914.txt for documentation.
rem Modified to support 'show sample points' option and turn-off synch mode (SDM 1.82 and later)
@title Fast MD 080914
@param a Columns
@default a 3
@param b Rows
@default b 3
@param c Threshold (0-255)
@default c 10
@param g Burst/Review/Video time (s)
@default g 0
@param d Compare Interval (ms)
@default d 7
@param h Pixel Step (pixels)
@default h 40
@param f Channel (0U,1Y,2V,3R,4G,5B)
@default f 1
@param n Timeout (10s of seconds)
@default n 30
@param e Trigger Delay (0.1 sec)
@default e 5
@param q Show sample points
@default q 1
@param r Show sample cells
@default r 1
@param i Masking (0=No 1=Mask 2=Use)
@default i 0
@param j - Mask Columns Left
@default j 0
@param k - Mask Columns Right
@default k 0
@param l - Mask Rows Top
@default l 0
@param m - Mask Rows Bottom
@default m 0
@param o Shoot fast=0,slow=1,test=2
@default o 2
if a<1 then a=1
if b<1 then b=1
if i<0 then i=0
if i>2 then i=2
if j<0 then j=0
if k<0 then k=0
if l<0 then l=0
if m<0 then m=0
if j>a then j=a
if k>a then k=a
if l>b then l=b
if m>b then m=b
if g<0 then g=0
if f<0 then f=1
if f>5 then f=1
if f=0 then print "Channel: U chroma"
if f=1 then print "Channel: Luminance"
if f=2 then print "Channel: V chroma"
if f=3 then print "Channel: Red"
if f=4 then print "Channel: Green"
if f=5 then print "Channel: Blue"
if n<1 then n=1
if q<0 then q=0
if q>0 then q=32
if r<0 then r=0
e=e*100
g=g*1000
n=n*10000
set_sync 0 0 0 0
P=get_video_button
if P=1 then goto "VideoButtonError"
P=get_mode
if P=1 then goto "PlayModeError"
rem get_mode returns 2 if a we are in video mode (and the camera has no video button)
if P=2 then p=1 else p=0
P=get_flash_mode
if P=2 then goto "SkipFlashWarning"
print "WARNING: Flash is not"
print "disabled. May cause "
print "odd behavior. "
:SkipFlashWarning
if o=0 and p=1 then goto "fast_video_md"
if o=1 and p=1 then goto "slow_video_md"
if o=1 and p=0 then goto "slow_md"
if o=2 then goto "test_md"
print "Fast react photo MD"
:fast_md_loop
t=0
do
release "shoot_half"
press "shoot_half"
do
P=get_shooting
until P=1
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, 9+q, h, e
until t>0
let X=get_tick_count
:contloop1
let U=get_tick_count
let V=(U-X)
if V<g then goto "contloop1"
release "shoot_full"
release "shoot_half"
do
P=get_shooting
until P<>1
goto "fast_md_loop"
:slow_md
rem print "Slow react photo MD"
:slow_md_loop
t=0
do
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, q, h, e
until t>0
if g>0 then goto "contshoot2" else shoot
goto "slow_md_loop"
:contshoot2
press "shoot_full"
let X=get_tick_count
:contloop2
let U=get_tick_count
let V=(U-X)
if V<g then goto "contloop2"
release "shoot_full"
release "shoot_half"
do
P=get_shooting
until P<>1
goto "slow_md_loop"
:fast_video_md
if g<1 then g=1000
print "Fast react video MD"
:fast_video_md_loop
t=0
do
release "shoot_half"
press "shoot_half"
sleep 1000
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, 9+q, h, e
until t>0
rem press "shoot_full" was done by md_detect_motion
print "starting video record"
sleep 300
release "shoot_full"
let X=get_tick_count
:fastvideowaitloop
let U=get_tick_count
let V=(U-X)
if V<g then goto "fastvideowaitloop"
click "shoot_full"
print "ending video record"
rem Need to wait or shoot_half won't work and loop will work like slow react loop:
sleep 1000
goto "fast_video_md_loop"
:slow_video_md
if g<1 then g=1000
rem Focusing takes time => add a second to make length argument a bit more accurate.
g=g+1000
print "Slow react video MD"
:slow_video_md_loop
t=0
do
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, q, h, e
until t>0
press "shoot_full"
sleep 300
release "shoot_full"
print "starting video record"
let X=get_tick_count
:slowvideowaitloop
let U=get_tick_count
let V=(U-X)
if V<g then goto "slowvideowaitloop"
click "shoot_full"
print "ending video record"
goto "slow_video_md_loop"
:test_md
print "MD test, no shooting."
N=0
:test_md_loop
t=0
do
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, q, h, e
until t>0
N=N+1
print t, "cells, trigger ", N
goto "test_md_loop"
:PlayModeError
print "MDFB script ERROR:"
print "Not in REC mode, exiting."
end
:VideoButtonError
print "MDFB script ERROR:"
print "Incompatible camera! Try"
print "MDFB VideoButtonModels"
print "version."
end
Thanks !
-
@sh1981 : I'm enjoying following your posts on this thread but they would be a bit easier to read if you could maybe use the "Insert Code" tool so that they are not so long ? No big deal.
rem Fudgey's Fast/Slow/Video Motion Detector with masks. For models with no video button.
rem See MDFB-080914.txt for documentation.
rem Modified to support 'show sample points' option and turn-off synch mode (SDM 1.82 and later)
@title Fast MD 080914
@param a Columns
@default a 3
@param b Rows
@default b 3
@param c Threshold (0-255)
@default c 10
@param g Burst/Review/Video time (s)
@default g 0
@param d Compare Interval (ms)
@default d 7
@param h Pixel Step (pixels)
@default h 40
@param f Channel (0U,1Y,2V,3R,4G,5B)
@default f 1
@param n Timeout (10s of seconds)
@default n 30
@param e Trigger Delay (0.1 sec)
@default e 5
@param q Show sample points
@default q 1
@param r Show sample cells
@default r 1
@param i Masking (0=No 1=Mask 2=Use)
@default i 0
@param j - Mask Columns Left
@default j 0
@param k - Mask Columns Right
@default k 0
@param l - Mask Rows Top
@default l 0
@param m - Mask Rows Bottom
@default m 0
@param o Shoot fast=0,slow=1,test=2
@default o 2
if a<1 then a=1
if b<1 then b=1
if i<0 then i=0
if i>2 then i=2
if j<0 then j=0
if k<0 then k=0
if l<0 then l=0
if m<0 then m=0
if j>a then j=a
if k>a then k=a
if l>b then l=b
if m>b then m=b
if g<0 then g=0
if f<0 then f=1
if f>5 then f=1
if f=0 then print "Channel: U chroma"
if f=1 then print "Channel: Luminance"
if f=2 then print "Channel: V chroma"
if f=3 then print "Channel: Red"
if f=4 then print "Channel: Green"
if f=5 then print "Channel: Blue"
if n<1 then n=1
if q<0 then q=0
if q>0 then q=32
if r<0 then r=0
e=e*100
g=g*1000
n=n*10000
set_sync 0 0 0 0
P=get_video_button
if P=1 then goto "VideoButtonError"
P=get_mode
if P=1 then goto "PlayModeError"
rem get_mode returns 2 if a we are in video mode (and the camera has no video button)
if P=2 then p=1 else p=0
P=get_flash_mode
if P=2 then goto "SkipFlashWarning"
print "WARNING: Flash is not"
print "disabled. May cause "
print "odd behavior. "
:SkipFlashWarning
if o=0 and p=1 then goto "fast_video_md"
if o=1 and p=1 then goto "slow_video_md"
if o=1 and p=0 then goto "slow_md"
if o=2 then goto "test_md"
print "Fast react photo MD"
:fast_md_loop
t=0
do
release "shoot_half"
press "shoot_half"
do
P=get_shooting
until P=1
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, 9+q, h, e
until t>0
let X=get_tick_count
:contloop1
let U=get_tick_count
let V=(U-X)
if V<g then goto "contloop1"
release "shoot_full"
release "shoot_half"
do
P=get_shooting
until P<>1
goto "fast_md_loop"
:slow_md
rem print "Slow react photo MD"
:slow_md_loop
t=0
do
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, q, h, e
until t>0
if g>0 then goto "contshoot2" else shoot
goto "slow_md_loop"
:contshoot2
press "shoot_full"
let X=get_tick_count
:contloop2
let U=get_tick_count
let V=(U-X)
if V<g then goto "contloop2"
release "shoot_full"
release "shoot_half"
do
P=get_shooting
until P<>1
goto "slow_md_loop"
:fast_video_md
if g<1 then g=1000
print "Fast react video MD"
:fast_video_md_loop
t=0
do
release "shoot_half"
press "shoot_half"
sleep 1000
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, 9+q, h, e
until t>0
rem press "shoot_full" was done by md_detect_motion
print "starting video record"
sleep 300
release "shoot_full"
let X=get_tick_count
:fastvideowaitloop
let U=get_tick_count
let V=(U-X)
if V<g then goto "fastvideowaitloop"
click "shoot_full"
print "ending video record"
rem Need to wait or shoot_half won't work and loop will work like slow react loop:
sleep 1000
goto "fast_video_md_loop"
:slow_video_md
if g<1 then g=1000
rem Focusing takes time => add a second to make length argument a bit more accurate.
g=g+1000
print "Slow react video MD"
:slow_video_md_loop
t=0
do
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, q, h, e
until t>0
press "shoot_full"
sleep 300
release "shoot_full"
print "starting video record"
let X=get_tick_count
:slowvideowaitloop
let U=get_tick_count
let V=(U-X)
if V<g then goto "slowvideowaitloop"
click "shoot_full"
print "ending video record"
goto "slow_video_md_loop"
:test_md
print "MD test, no shooting."
N=0
:test_md_loop
t=0
do
md_detect_motion a, b, f, n, d, c, r, t, i, j+1, l+1, a-k, b-m, q, h, e
until t>0
N=N+1
print t, "cells, trigger ", N
goto "test_md_loop"
:PlayModeError
print "MDFB script ERROR:"
print "Not in REC mode, exiting."
end
:VideoButtonError
print "MDFB script ERROR:"
print "Incompatible camera! Try"
print "MDFB VideoButtonModels"
print "version."
end
Thanks !
Arrite mate, thanks for the advice, I'm a bit new so I usually just write in that Quick Reply box down there. I'll do it like you've said from now on. :)
-
Before looking at motion detection, when you plug A/V into a TV I need to know if ONE character of one of the values immediately changes and stays changed.
I am not interested in values that randomly change.
Right, so I gather you want me to do it in this order
-Turn the camera on
-Get into ALT mode
-Run the intervalometer script
-While the script is running, plug the AV jack in the camera and telly
-See which one character changes, and REMAINS changed.
I'll follow the above steps and tell the results.
If I got any of the steps above wrong do correct me and I'll do it again.
Cheers.
-
No ALT mode or scripts.
Just plug in.
-
@microfunguy
I've posted two videos
http://www.yourfilelink.com/get.php?fid=672954 (http://www.yourfilelink.com/get.php?fid=672954)
http://www.yourfilelink.com/get.php?fid=672955 (http://www.yourfilelink.com/get.php?fid=672955)
Took them with my cellfone camera so not exceptional quality.
In first one you can see the cam hang problem as well at end of script, that i was talkin about. you can also see the flicker of the screen towards the end.
In second video I just plugged in the AV like you said.
The value that changes is VALUE 1, see how there are 3 values, 0, 1 and 2, its the value 1 that changes between pluggin in the AV and taking it out.
On the Telly, the Value 1: 384830** where first * alternates between (0-3) and second * alternates between (8-9)
On the Cam, the Value 1: 38e870** where first * alternates between (0-3) and second * alternates between (8-9)
Therefore I can safely say that only characters 3 and 5 are changing, notice on on cam its e for character 3 and on telly its 4 for character 3. Similarly character 5 becomes 7 on cam and 3 on telly. This is the way they REMAIN, i.e they do not 'randomly change'.
Hope that helps.
-
Quick question, is it possible to turn off sound recording during video recording?
-
Quick question, is it possible to turn off sound recording during video recording?
Quick answer: No !
-
Yes, in Bracketing/Overrides menu make sure the EV's are set to '0' (that turns off bracketing).
On my camera, the screen turns on only for a fraction of a second.
Have you turned off the Canon review mode ?
In menu Advanced\DEbug parameters, enable disable of MISCellaneous values.
Plug something into the A/V socket.
Does one of the displayed values consistently change ?
If so, what are the two values ?
EDIT
Of course, to see the values when the plug is inserted you will have to plugin an external display !
When I use the script and set LCD off, the LCD is off all the time. Even after I stop the script, the LCD stays off.
I don't have disable of MISCellaneous values option. I have show Misc. values. Tried both enable and disable; didn't notice any value changes when plugged into TV.
-
I was also playing around with motion detection script and LED cannot be turned off in that either. Any idea if LED can be totally turned off in the following script if possible?
The only way to turn LCD off, state in the readme file, is to plug in the AV cable.
-
Yes, in Bracketing/Overrides menu make sure the EV's are set to '0' (that turns off bracketing).
On my camera, the screen turns on only for a fraction of a second.
Have you turned off the Canon review mode ?
In menu Advanced\DEbug parameters, enable disable of MISCellaneous values.
Plug something into the A/V socket.
Does one of the displayed values consistently change ?
If so, what are the two values ?
EDIT
Of course, to see the values when the plug is inserted you will have to plugin an external display !
When I use the script and set LCD off, the LCD is off all the time. Even after I stop the script, the LCD stays off.
I don't have disable of MISCellaneous values option. I have show Misc. values. Tried both enable and disable; didn't notice any value changes when plugged into TV.
And you have an IXUS 105?
Funny cause with mine the screen flickers, like it shows at the end of the first video I posted.
-
And you have an IXUS 105?
Funny cause with mine the screen flickers, like it shows at the end of the first video I posted.
[/quote]
Yes, IXUS 105 100C.
I just noticed flickers with slow shutter speed at 1". At higher shutter speed, I didn't see flickers.
-
Tried both enable and disable; didn't notice any value changes when plugged into TV.
That is unusual.
If a value really did change I could make a uBasic command to do the same.
There again, if the screen only comes on VERY briefly there is no need to do anything.
-
That is unusual.
If a value really did change I could make a uBasic command to do the same.
There again, if the screen only comes on VERY briefly there is no need to do anything.
[/quote]
I didn't see any values on screen. Just the normal lcd screen.
-
btw, the motion detection is working with MDFB-080914.bas. I added 10 seconds sleep after the shot(s), so the Eye-Fi card can transfer the pictures.
-
the motion detection is working with MDFB-080914.bas.
You should be using MD_SDM.bas, it has enhanced features such as sample point display, no-motion detection, spotmeter display of brightness and RGB values, etc.
-
Tried both enable and disable; didn't notice any value changes when plugged into TV.
That is unusual.
If a value really did change I could make a uBasic command to do the same.
There again, if the screen only comes on VERY briefly there is no need to do anything.
@microfunguy,
I wrote earlier how the values changed. The value 1 after enabling Misc Values in Debug changes as I had posted.
I also pasted video showing changes in values, as well as showing the flicker of screen.
There IS a need to do something about the flicker, at least in my opinion. The flicker defeats the purpose of LCD off. Currently I just plug in the AV wire. When without an AV wire, I leave the LCD ON, because theres really no point of a flickering screen which neither lets you see whats on the screen, nor properly turns the LCD off.
Ofcourse it will depend on you if you feel the need to fix the flicker, as for me my temporary solution is to plug in a small AV jack, which is an inefficient but effective solution. :)
-
I wrote earlier how the values changed.
You certainly did.
Download this version http://www.zshare.net/download/90435412594d14a6/ (http://www.zshare.net/download/90435412594d14a6/)
Plug-in the A/V lead.
Does the camera screen stay ON ?
-
You should be using MD_SDM.bas, it has enhanced features such as sample point display, no-motion detection, spotmeter display of brightness and RGB values, etc.
The MD_SDM.bas in Common_Files.zip is the same as MDFB-080914.bas. I can't find the updated one.
Two questions:
1. can you manually load 100C? I can auto load it, but the firm update option from Manu is no longer showing. I think you need PS.FI2 file for manual load.
2. where can you find the Property values for SD1300? I like to use SET/GET_PROP to Read/Set Property of continuous shooting.
Thanks!
-
The MD_SDM.bas in Common_Files.zip is the same as MDFB-080914.bas. I can't find the updated one.
If so, it should support sample points and there should be a note at the top saying it is an amended version of fudgey's script/
1. can you manually load 100C?
No, SDM does not support manual loading.
When it is officially released someone would have to port it to CHDK and try to add that option.
2. where can you find the Property values for SD1300?
If the original CHDK build is correct, it should be this one :
http://tools.assembla.com/chdk/browser/trunk/include/propset3.h (http://tools.assembla.com/chdk/browser/trunk/include/propset3.h)
Are you saying you can set the camera to continuous shooting ?
To save time waiting for 'sh1981' can you perform the above test with this build ? :-
http://www.zshare.net/download/904638448b305ba8/ (http://www.zshare.net/download/904638448b305ba8/)
-
@microfunguy,
First of all I must say this... this is the best build so far!!!!
I'm really impressed. I noticed:
-The camera now turns on and off smoothly not only in AUTO but also in P and VIDEO mode!
-The SDM menu leaves 0 imprints, as before, although the problem was solved, it still left a tiny bit very seldom.
-Optical zoom in video works.
Therefore I can safely say it fixes the above three problems, which for me, were the biggest problems.
However, to answer your questions:
When I plug in the AV wire, the camera screen turns OFF as the telly screen comes ON, and vice versa. Can be seen here http://www.easy-share.com/1915599631/MOV0083A.3gp (http://www.easy-share.com/1915599631/MOV0083A.3gp)
I have also attached 2 photos with this post, the one ending in 370A shows the telly screen, and one ending in 368A shows the camera screen. As you might notice, the values of value 1 do change, as I posted earlier.
Whatever you've done in this build, I dont know, but what I do know is that it makes the camera run smooth, the menus come and go like they should, as if they're a part of canon menu system. The Camera also turns off and on smoothly.
Really impressed.
-
Quote
1. can you manually load 100C?
No, SDM does not support manual loading.
@microfunguy
SDM can be loaded manually if a PS.FI2 file is created using the fi2enc tool http://chdk.setepontos.com/index.php?topic=2995.75 (http://chdk.setepontos.com/index.php?topic=2995.75)
It may be possible to create PS.FI2 files during compilation (see Wiki for details) but I have not tried
Best,
Colin
-
@microfunguy,
Heres a snap of the camera misc values, a bit clearer photo, took it from my wife's cellfone this time... lol
-
this is the best build so far!!!!
I have not done anything, except disable extended memory.
Browse the OSD's in ALT mode, how much memory is available ?
Do the same with the previous build.
I cannot be bothered doing any more work on screen blanking.
You have the source code, you have Whim's tool, do it yourself.
-
this is the best build so far!!!!
I have not done anything, except disable extended memory.
Browse the OSD's in ALT mode, how much memory is available ?
Do the same with the previous build.
I cannot be bothered doing any more work on screen blanking.
You have the source code, you have Whim's tool, do it yourself.
How do I find out how much memory I have available?
You dont need to work on screen blanking if you dont want to, I said earlier as well that the temporary solution of plugging in AV wire works fine for me and I can live with that :)
-
How do I find out how much memory I have available?
Browse the OSD's in ALT mode ... using the left/right buttons.
And yes, each OSD is separated by a blank from other OSD's.
-
How do I find out how much memory I have available?
Browse the OSD's in ALT mode ... using the left/right buttons.
And yes, each OSD is separated by a blank from other OSD's.
new vers:
98% 3734M
memory 726888
batt 3.926V
old vers:
98% 3734M
memory 3442576
batt 3.926V
by the way it only comes in auto mode...no wonder it took me a bit to figure it out
what does this mean? whats MEMORY here? is it some sort of camera inbuilt memory? what affect does it have?
-
by the way it only comes in auto mode...no wonder it took me a bit to figure it out
Never heard of that before.
what does this mean? whats MEMORY here? is it some sort of camera inbuilt memory?
It is the amount of memory available to CHDK\SDM.
The old version had far more memory available, known as extended memory.
what affect does it have?
On cameras that do not have much memory, edge overlay and zebra may not work.
In addition, inverted image playback and stereo playback of images may not work on SDM.
-
by the way it only comes in auto mode...no wonder it took me a bit to figure it out
Never heard of that before.
what does this mean? whats MEMORY here? is it some sort of camera inbuilt memory?
It is the amount of memory available to CHDK\SDM.
The old version had far more memory available, known as extended memory.
what affect does it have?
On cameras that do not have much memory, edge overlay and zebra may not work.
In addition, inverted image playback and stereo playback of images may not work on SDM.
The memory OSD menu only shows in AUTO mode, this holds true for both old and new version. May not have heard it before, but its true.
Zebra works.
Edge overlay works, although it gives red dots all over screen if i point it to the light, a bit less dots if i point at darkness, is that how its supposed to be?
No idea about inverted image playback, I could help you check that if you tell me how to access this option. I dont have another camera so no hope of 'stereo' images for me.
So anyway, disabled extended memory sure fixes the problems I mentioned in my earlier post. Perhaps the camera itself didnt have much left over and thats why it wouldnt start in P mode smoothly. Whatever it is mate, it works, and works wonderfully!
-
I have realised that the perfect way to turn on the camera smoothly without the lens jamming / camera hanging is to press the power on button once, then then flick the shoot button half way lightly.
This method turns the camera on smoothly in both builds.
I have further realised that in old build (the one with expanded memory), while in video recording, if you go into ALT menu and then SDM menu, and then load script file browser, the image does go away after you press MENU button, however after you press DISP button to get out of ALT menu, and then press DISP button again to enter ALT menu again, the old image of file browser + sdm menu comes up.
This above mentioned problem does NOT occur in the new build, I tested this at least 15 times.
-
I also realised that in both versions, if you turn the camera on in P mode, and then QUICKLY take a picture, the camera hangs. Note that canon startup image and SDM startup image both are DISABLED.
However also note that this behavior does not occur in video or AUTO mode under similar circumstances as above. Both these allow you to shoot as soon as camera is on.
This is NOT something that in my opinion NEEDS to be fixed, but would ADD to the smooth functioning.
-
After doing a bit of lookin around it seems EXMEM is having problems with other cams too... http://chdk.setepontos.com/index.php?topic=4348.1215 (http://chdk.setepontos.com/index.php?topic=4348.1215)
Tried shooting DNG today as well and that also works with the new vers.
-
@sh1981
I am rather busy at the moment, but some quick comments.
In Edge Overlay mode point the camera at something that has a simple, clear outline such as a sheet of paper or monitor screen.
You should see an outline around the subject, not random dots.
In Stereo menu, enable Inverted playback.
Switch to playback mode and browse the images.
They should quickly invert.
You can certainly take stereo photos with one camera, more details later.
-
@sh1981
I am rather busy at the moment, but some quick comments.
In Edge Overlay mode point the camera at something that has a simple, clear outline such as a sheet of paper or monitor screen.
You should see an outline around the subject, not random dots.
In Stereo menu, enable Inverted playback.
Switch to playback mode and browse the images.
They should quickly invert.
You can certainly take stereo photos with one camera, more details later.
I cant find Inverted Playback in Stereo menu.
-
I cant find Inverted Playback in Stereo menu.
It seems that I have disabled it for the IXUS105.
Too bad.
-
@microfunguy,
Here is the paper (actually a tissue)
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi56.tinypic.com%2F2r3e2yt.jpg&hash=7acde3d942119e69361274e60479b4c1)
Here is me taking the photo with OLD build
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi56.tinypic.com%2F9q8w1w.jpg&hash=83ff68856e32c17d141051213dd38212)
Here is the result of edge overlay with OLD build
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi51.tinypic.com%2F2e1suvm.jpg&hash=faf10cf10f79a57b4042a8a2c5ef2273)
Here you can see that the option is of Inverted Playback is visible in Stereo menu of old build
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi53.tinypic.com%2Foihbur.jpg&hash=8cb1d51265b2eee16b2077427594eb74)
Here you can see that the option of Inverted Playback is MISSING in Stereo menu of new build
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi56.tinypic.com%2F10omjbr.jpg&hash=95fb3b4e35b1b35996eb4af821abd970)
Here is the Edge Overlay with NEW build
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi55.tinypic.com%2F653ho4.jpg&hash=f4779f586428104f7d4f5617c0654156)
I would like to add here that I tried Inverted Playback in OLD build, where its visible, and I dont know what its supposed to do, but it doesnt 'invert' any photos, rather makes them jam for a bit. If i tilt the camera, they show sideways, like normal. I dont see no difference in Playback with this option enabled.
If you have disabled it in the new build, what else have you disabled here?
-
Played around with both old and new vers again (hope my battery door doesnt fall off) and found out:
-the best way to turn cam on smoothly is to disabled SDM logo and canon startup logo and then press PLAY and then press shutter half way.
-best way to turn cam off is to press PLAY 2 times.
-the performance of edge overlay, RAW, and everything else (that I tried), seems to be similar, EXCEPT that of menu image being stuck, which in old versions case it does get stuck at times and multiple pressing of DISP removes it temporarily. However it NEVER occurs in new vers. The menu in new vers works so smooth it makes me think SDM is a part of the camera!
Is there any way to turn on / off extended memory manually?
-
Hi, I made this little script to turn off LCD while video is shooting.
The problem I am facing is, that I want to somehow 'free' the MENU button while the script is running, as I need to use MENU button in ALT mode to enter SDM menu while the script is on. Everything else works as planned.
Any idea how to do that?
Alternatively can someone shed some light on how to bring the SDM menu up by a ubasic command? If I could 'call' the SDM Menu upon pressing Menu key, that would help.
Also is there any way to turn off LCD in SDM through some inbuilt command (i.e not by using a ubasic script)?
Here is the script:
rem sh1981
rem Video with LCD off
rem Canon IXUS 105 / SD 1300
rem Put in A/V plug in cam to turn off LCD
@title Video with LCD off
l=0
click "shoot_half"
sleep 1000
click "shoot_full"
:loop
print "Shoot Half to turn LCD"
print "Off or On. DISP to"
print "enable Zoom and Focus."
wait_click
if is_key "shoot_half" then goto "bk_light"
goto "loop"
:bk_light
if l=1 then goto "turn_light_on"
if l=0 then goto "turn_light_off"
:turn_light_on
set_backlight 1
l=0
goto "loop"
:turn_light_off
set_backlight 0
l=1
goto "loop"
-
LCD Off / On During Video Recording Script
This script now works perfectly for IXUS 105.
How to Use:
Start shooting the video normally.
Press DISP to go into ALT menu and Shoot Full run the script.
Press Shoot Half to turn LCD on or off.
If you need to access SDM menu, press MENU once, wait for a second, press MENU again.
Pressing MENU will basically end script, so if you need it again during video recording, remain or go into ALT menu and Shoot Full to run script.
While script is on, Shoot Full will end the script, but sometimes leaves the screen blank, if this happens, Shoot Full again and Half Shoot to turn LCD on. I have not found a way around this so best is to end the script with MENU button. Not only is pressing MENU cleaner, but its also the reason why I wanted the stop the script in the first place, i.e to access SDM Menu while script is running.
Note that to use optical zoom, manual focus etc, you would have to press DISP to exit ALT menu and then respectively perform the zoom etc operation. I would recommend pressing MENU first to disable script before exiting ALT menu.
Purpose of the Script:
Saves battery during video recording.
Recording Video with LCD off is neat!
rem sh1981
rem LCD on off
rem Canon IXUS 105 / SD 1300
@title LCD on off
l=0
:loop
print "Shoot Half - On/Off LCD"
print "Menu Key - Disb.Script."
print "To Access DISP/SDM/ALT/MENU"
wait_click
if is_key "shoot_half" then goto "bk_light"
if is_key "menu" then goto "menu_access"
goto "loop"
:bk_light
if l=1 then goto "turn_light_on"
if l=0 then goto "turn_light_off"
:turn_light_on
set_backlight 1
l=0
goto "loop"
:turn_light_off
set_backlight 0
l=1
goto "loop"
:menu_access
set_backlight 1
sleep 1000
end
-
-
-
@microfunguy,
Any chance of having a user defined timestamp font in SDM? Something on the lines of http://chdk.setepontos.com/index.php?topic=1367.60 (http://chdk.setepontos.com/index.php?topic=1367.60)
-
disable_main_flash
enable_main_flash
set_resolution
get_resolution
Hope that helps.
Thank you!
There are four differenct sets of property case values identified. I think I'm using a wrong one. BTW,
disable_main_flash
enable_main_flash
set_resolution
get_resolution
Didn't work.
-
@microfunguy,
In the Time-Lapse script, is it possible to make it such that pressing MENU button will end the script, instead of full shoot?
The reason why I feel there is a need for it is that quite seldom the script hangs when I try to STOP the script, probably because the camera is in process of focusing, or saving.
Since it is just using this command
time_lapse a, b, c, d, e, f, g, h, i, j, k, l, m, n, p, q, r, s, t, u
I was wondering if 'behind the scenes' its possible to tweak another parameter into it, say parameter z, that would be something like
@param z menu button ends script N/Y 0/1
@default z 1
Is that possible?
I found that stopping a script with Menu button does not hang the script, I realised this in my video recording lcd on off script I posted earlier.
-
I am busy with another project at present so will answer recent questions some other time.
Looking at my notes, the IXUS105 tester reported nearly everything working, including edge overlay.
I am not saying sh1981 is mistaken, but someone has given me incorrect information.
-
I am busy with another project at present so will answer recent questions some other time.
Looking at my notes, the IXUS105 tester reported nearly everything working, including edge overlay.
I am not saying sh1981 is mistaken, but someone has given me incorrect information.
@microfunguy,
Since I posted photos of me doing the paper test you specified with edge overlay, so the evidence is clear. Unless ofcourse I was meant to tweak some other settings in edge overlay, which I didnt, I just simply enabled it and it comes up with red dots in form of a square, as shown in the photos I posted.
You can answer whenever you are free to do so, can be a week, can be a year, I'm very patient :)
I will however keep on posting my findings as I think it would eventually help made SDM better.
On a sidenote, I discovered yesterday that if you stop any script while the green led is flashing, it seems to stop fine. For e.g with time-lapse I was moaning about in my previous post, I realised that if I stop the script while the green led is off, it seems to hang the camera when I stop the script by pressing the full shoot. I also alternatively realised in my own lcd off on script that pressing menu button instead overrides this limitation. So a mechanism in which you either stop the script by pressing menu key instead of full shoot, or stopping script from full shoot only when green/red led is on, should fix the problem of camera hanging while stopping a script.
-
@microfunguy,
Regarding inverted playback look here as well, someone else has reported same problem with SDM
http://www.youtube.com/watch?v=DHZrbDMcrYE&feature=player_embedded# (http://www.youtube.com/watch?v=DHZrbDMcrYE&feature=player_embedded#)
http://www.youtube.com/watch?v=DmSJUI8Tzp4&NR=1# (http://www.youtube.com/watch?v=DmSJUI8Tzp4&NR=1#)
I also dont really know the purpose of inverted playback really. Why would anyone want to playback inverted, unless they're hanging upside down :lol
-
Hi,
Is it recommended to use SDM build or latest build in this topic? I am mostly interested in RAW format, and Av override (if possible?). Thanks.
-
Hello and welcome.
You can use both.
Put both DISKBOOT.BIN's on your card and temporarily rename the one you are not using.
The IXUS105 does not have an aperture.
-
Hi,
Is it recommended to use SDM build or latest build in this topic? I am mostly interested in RAW format, and Av override (if possible?). Thanks.
I prefer this build http://www.zshare.net/download/90435412594d14a6/ (http://www.zshare.net/download/90435412594d14a6/)
Apparently it does not have extended memory. The SDM menu works more smoothly in this one, at least with me. Would appreciate it if you would try this build as well after you've tried the normal SDM from the site, and tell me if you notice a difference in the way menu comes on and off the screen.
-
Why would anyone want to playback inverted
Well now ....
For stereo photography of subjects at 'normal' distances, the spacing of the two camera lenses should be the same as human eyes, about 65 to 75mm.
All of the SDM supported cameras have lenses that are offset from centre so to get the lenses closer together you can mount one camera upside down on something called a Z-bar.
Using the USB remote switch, SDM can playback the paired images.
However, one camera will need the playback image inverted so that it is the correct way up !
By crossing your eyes, you can then see the images in stereo !
-
Why would anyone want to playback inverted
Well now ....
For stereo photography of subjects at 'normal' distances, the spacing of the two camera lenses should be the same as human eyes, about 65 to 75mm.
All of the SDM supported cameras have lenses that are offset from centre so to get the lenses closer together you can mount one camera upside down on something called a Z-bar.
Using the USB remote switch, SDM can playback the paired images.
However, one camera will need the playback image inverted so that it is the correct way up !
By crossing your eyes, you can then see the images in stereo !
I see, interesting stuff, will try it someday. Unfortunately in the latest build you have removed Inverted Playback, but dont worry about it, I aint bothered about it right now anyway, I'm just so glad the menu works smoothly in the latest build :)
-
I just cant help but wonder why we can't bump the ISO to 6400, when, in Low Light mode, canon itself can manage ISO 6400.
Perhaps there is a way to do this?
I would also like to do ISO bracketing, something on the lines of http://chdk.wikia.com/wiki/UBASIC/Scripts/CanonA640:_ISO_Bracketing (http://chdk.wikia.com/wiki/UBASIC/Scripts/CanonA640:_ISO_Bracketing) however with more higher ISO options such as ISO 6400.
I also wonder, since canon itself can sometimes take a photo at ISO 120, ISO 250 etc, is it possible to change this setting through a ubasic / or otherwise, script?
-
I just cant help but wonder why we can't bump the ISO to 6400, when, in Low Light mode, canon itself can manage ISO 6400.
Don't step in the marketing. The highest Canon ISO settings are not sensor gain like the normal ones.
-
There are four differenct sets of property case values identified. I think I'm using a wrong one. BTW,
disable_main_flash
enable_main_flash
set_resolution
get_resolution
Didn't work.
Can you give more information about all of this and exactly what you did ?
-
I bought another SD1300 (this time for my girlfriend, the first one I gave to my mother). this is just an awesome little cheap camera.
back to topic: in the wiki the information says CHDK is not available on this cam yet. but in this topic there are some links. I would like to ask if in any of these builds the FILE BROWSER feature is working. could you please point me to the right one (if any)?
thanks,
-
hi guys. new here. i have an ixus 105. how do i take photos in raw format. secondly, if you have any suggestions on how to improve results from my camera please chip in. thanks.
-
hi guys. new here. i have an ixus 105. how do i take photos in raw format. secondly, if you have any suggestions on how to improve results from my camera please chip in. thanks.
Well, a good place to start might be here :
CHDK_for_Dummies (http://chdk.wikia.com/wiki/CHDK_for_Dummies) or CHDK_User_Manual (http://chdk.wikia.com/wiki/CHDK_User_Manual)
And when you are done with that, take a look at : Raw (http://chdk.wikia.com/wiki/Raw)
-
I bought another SD1300 (this time for my girlfriend, the first one I gave to my mother). this is just an awesome little cheap camera.
back to topic: in the wiki the information says CHDK is not available on this cam yet. but in this topic there are some links. I would like to ask if in any of these builds the FILE BROWSER feature is working. could you please point me to the right one (if any)?
thanks,
The last link you find in this topic is in my opinion the best one.
The file browser works in all builds.
-
hi guys. new here. i have an ixus 105. how do i take photos in raw format. secondly, if you have any suggestions on how to improve results from my camera please chip in. thanks.
Raw photos can be taken by simply enabling RAW in the first option of the SDM menu, and then subsequently going into RAW and enabling it.
Once you have the RAW file, you will need a program called DNG4PS (I hope I'm correct), with which you will convert them into DNG format.
Once in DNG format you will be able to edit them in a program such as RAWTHERAPEE or, my personal favorite, UFRAW which you got to install with GIMP.
However I'd like to say that the results you get with RAW are in my humble opinion, not very impressive. But that might be because I'm not a professional. I'm guessing you're not a professional either, since you had to ask all this.
Therefore, since you asked on how to improve results from your camera, my suggesstion is:
- Shoot in highest quality jpeg, forget RAW for now.
- Shoot in highest Megapixel.
- Play with the metering modes, spot, evaluative etc, they make the difference between a good photo and a bad one.
- Play with FOLIAGE mode, it brings out nice colors.
- Enable Vivid Color mode in P mode.
- Enable iConstract in P mode.
- Use AUTO mode when shooting faces indoors without a flash. For some reason, pictures taken in AUTO of people, indoors, without flash, come better. Unless you change to SPOT metering in P mode.
-When shooting indoors with flash, force ISO 80 in P mode. It will guarantee good quality photos.
- When shooting indoors with flash, force ISO 200 in P mode and use SLOW SYNCHRO flash to capture details of background.
- To focus on one thing indoors, leaving all background dim, use SPOT with NORMAL FLASH.
- Use FOLIAGE outdoors.
- When taking photos of buildings etc at night, overrider shutter speed via SDM or use Long Shutter mode.
- When taking photos in a fast moving car or bus, override shutter speed to something like 1/600 via SDM.
-Cover flash indoors with a piece of tissue, folded double, and change flash to slow synchro, ISO 200, for a nice photo that brings out vivid colors.
These are of course, my own personal observations, and usually bring out the best results for me.
Edit: I love this program called Neat Image, might want to give it a try. Removes noise, sharpens. Best to correct images taken in ISO 800.
-
Once you have the RAW file, you will need a program called DNG4PS (I hope I'm correct)
No, you do not : http://stereo.jpn.org/eng/sdm/dng.htm (http://stereo.jpn.org/eng/sdm/dng.htm)
-
Once you have the RAW file, you will need a program called DNG4PS (I hope I'm correct)
No, you do not : http://stereo.jpn.org/eng/sdm/dng.htm (http://stereo.jpn.org/eng/sdm/dng.htm)
Far as I can see, both do the same thing, DNG4PS has a simple interface, makes it easier for me. http://chdk.wikia.com/wiki/DNG4PS-2 (http://chdk.wikia.com/wiki/DNG4PS-2)
-
thanks guys. now where do i get this SDM for IXUS 105?
-
thanks guys. now where do i get this SDM for IXUS 105?
Follow instructions here: http://stereo.jpn.org/eng/sdm/download.htm (http://stereo.jpn.org/eng/sdm/download.htm)
Then (optional), download this http://www.zshare.net/download/90435412594d14a6/ (http://www.zshare.net/download/90435412594d14a6/) and replace the DISKBOOT.BIN on ur memory card. I find this version most stable.
Microfunguy is the big guru here, he occassionally makes updates and uploads them on this thread for ixus 105. All you have to do is replace the DISKBOOT.BIN file in the root directory of your camera SD card with the updated DISKBOOT.BIN (such as the one posted above by microfunguy hosted on zshare).
You can make your own UBASIC scripts too, look here http://stereo.jpn.org/eng/sdm/docs.htm (http://stereo.jpn.org/eng/sdm/docs.htm) and http://stereo.jpn.org/eng/sdm/ubasic.htm (http://stereo.jpn.org/eng/sdm/ubasic.htm)
Oh and, if I were you, I'd get a little tripod, available from poundland for a quid, and also a waterproof underwater housing for ixus 105. Not that I ever do go underwater, hell I cant even swim, but it does help in the rain and dust. Can get it for a quid on ebay...http://cgi.ebay.co.uk/Underwater-Waterproof-Case-Bag-Pouch-Digital-Camera-/260791516647?pt=UK_Camera_Cases_Bags_Covers&hash=item3cb862bde7 (http://cgi.ebay.co.uk/Underwater-Waterproof-Case-Bag-Pouch-Digital-Camera-/260791516647?pt=UK_Camera_Cases_Bags_Covers&hash=item3cb862bde7)
A lens cleaning kit, hama costs 3 quid, would be nice too, but dont clean the lens too much and I prefer the lens tissue rather than the microfibre cloth. Also grab yourself a hard camera case from poundland for a quid.
Have fun :)
-
awesome. thanks man. you guys are really helpful. :D
-
what is Poundland?
Best
Colin
-
what is Poundland?
You, me and sh1981 are all in the UK :- http://www.poundland.co.uk/ (http://www.poundland.co.uk/)
-
The last link you find in this topic is in my opinion the best one.
The file browser works in all builds.
thanks sh1981! I will get this file and join the testers group.
-
Hmmm...i'm having a bit of an issue. I have an SD1300IS firmware 1.00C, I'm using "SDM_1.86_IXUS105_100c_2.zip" I keep getting insufficient space on card error. I have an 8gb sdhc card and i've followed the directions to the tee
Edit: a little bit more info: using a 2gb sd card sdm works perfectly (awesome tool, thanks microfunguy and anybody else involved in the project). I've read the documentation and know that cards over 4gb are a bit more of a hassle to deal with because it needs to be partitioned, but i've been reading that others have been having success with 8gb cards so I don't understand. http://chdk.setepontos.com/index.php?topic=6108.0 (http://chdk.setepontos.com/index.php?topic=6108.0) i've tried the fixes in this thread but still nothing.
-
While shooting a VIDEO, is it possible to change the EV with SDM?
I understand that prior to shooting, you can set the EV by pressing up button, however I want to do this WHILE I am recording.
Basically I want to increase the brightness in low light situations.
-
Hello and welcome.
i've followed the directions to the tee
Just remind us, in some detail, EXACTLY what you have done.
-
Hello and welcome.
Just remind us, in some detail, EXACTLY what you have done.
Hi, thank you. I edited my post and then saw that you had replied. To begin with, I downloaded the diskboot.bin for my firmware version 100C and the common files, I went to the configs directory and moved over three files from CONFIGS>config_eng>IXUS_105>SDM_install folder to the main folder. I then ran sdminste.exe. From there I clicked 'New Install' and followed the instructions until it told me that it was done, and to lock the card and it would autoboot. I inserted the locked card in the camera and it said Insufficient space on card. From there I started searching for fixes and tried a few things from this thread http://chdk.setepontos.com/index.php?topic=6108.0 (http://chdk.setepontos.com/index.php?topic=6108.0) to no avail. I hope I haven't forgotten anything
-
OK, the only file you really need to start is DISKBOOT.BIN and that should be on the small partition.
The CHDK folder and subfolders should be on the large partition.
Insert your card in the reader and start sdminst.exe.
Which partition is the first, the small one or the large one ?
Ideally, post a screenshot.
-
Here is a screenshot (https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi.imgur.com%2F9ngpW.png&hash=e5fa7eccde411a27181cb9eb27c9f7f9)
The small partition is first and seems to have the following folders (https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FrzT4c.png&hash=a9e139ecccf9f610f80d851fd3c1e593)
I swapped partitions and the larger partition seems to have the folders CHDK and DCIM
-
(nice screenshots, what capture device are you using ?)
Move the three folders from the small to large partition.
Not that it should make any difference but try booting again.
-
Screenshots were just taken using alt+prtscn then pasted into paint, windows 7 must make it look nice :)
Moving the folders still gives me the same Insufficient space on card message. I've been using SDM with a 2gb card and it is really cool, now I just need to start playing around to begin understanding all the options
-
My brain was not in gear, I was getting confused with screenshots of the camera !
The code is on a drive that is normally in a USB caddy that I am using for something else at present.
I will fit the drive and check.
Cannot remember if partitions were supported in 100c or been tested.
-
.
-
Is it possible to use TIME LAPSE to capture short bursts of videos?
Edit, found the solution, pretty easy, turn to Video Mode and then run the script.
Also can something like this http://chdk.setepontos.com/index.php?topic=1075.0 (http://chdk.setepontos.com/index.php?topic=1075.0) be done for ixus 105? That is, overriding ISO/TV in video mode? Would work just like a camcorder then!
-
Another thing, any possibility of connecting an external flash via the USB port to the ixus 105, and then instead of firing internal flash, send some sort of command via SDM to trigger the external flash connected visa USB port of camera?
-
Has anyone confirmed that it works or not ?
I should have been more clear.
I am asking 'thinkviv' if he has checked the thread for comments about dual partitions ?
-
I went through the thread in its entirety twice, once yesterday and again today to make sure I didn't miss anything. I haven't seen any comment with the same or similar issues as I am experiencing.
-
No, but has anyone confirmed they have used dual partitioning ?
-
can something like this http://chdk.setepontos.com/index.php?topic=1075.0 (http://chdk.setepontos.com/index.php?topic=1075.0) be done for ixus 105? That is, overriding ISO/TV in video mode?
If it can, that is experimental work that needs to be done by a developer with access to the camera.
I am willing to try to fix problems with existing features only.
-
any possibility of connecting an external flash via the USB port to the ixus 105
No, buy one of these instead :-
http://www.gentles.ltd.uk/gentstereo/sdm.htm (http://www.gentles.ltd.uk/gentstereo/sdm.htm)
-
No, but has anyone confirmed they have used dual partitioning ?
Yes, one poster confirmed that the dual partitions worked with his camera. However that poster has a different firmware version (not sure if that matters)
Hi,
The multi partition is working correctly. I am using a 8Gb card with no problem at all.
Thanks,
-
Yes, I remember now, siocnarf is going to attach his camera to a balloon.
If the code had errors it would crash your camera.
Is the 2MB partition formatted FAT16 ?
-
the 2mb partition reads as FAT12
-
and you have locked the card and SDM boots and you can access the menus, etc ?
-
yes sir. SDM loads up and I can access all the menus, it just says Insufficient space on card and beeps several times if i try to take a photo.
-
Delete all files from the large partition.
Make sure DISKBOOT.BIN is the only file on the first partition.
Boot the camera.
Now, turn the camera off.
Is folder CHDK on the small or large partition ?
-
Ok, the only thing on the card was the DISKBOOT.BIN on the small partition. Three folders(CHDK,SDM,DCIM) were created when the camera turned on, all are on the small 2MB partition. The large partition is blank
-
OK, I will have to look at the partition code.
It may or may not be 'tonight'.
-
any possibility of connecting an external flash via the USB port to the ixus 105
No, buy one of these instead :-
http://www.gentles.ltd.uk/gentstereo/sdm.htm (http://www.gentles.ltd.uk/gentstereo/sdm.htm)
Cheers, looks nice. I'm trying to get hold of something like an IR flashlight that would turn on at night if motion is detected, then coupled with the MD script, it can be used as a cheap CCTV with night vision. Well, I know I'd have to remove that little strip over CCD to get true nightvision but something like this device opens up the possibility of having an IR LED flash attached that would fire with the MD script.
Just a dream, dont think I'll get far without much knowledge of electronics but o well, I might succeed. lol
-
You can buy battery-operated wireless passive infra-red detectors that send a signal to a receiver.
That can switch +5V to the camera USB and take a photo.
From Hong Kong you can buy IR led security lights that use more than 100 led's.
Don't even think about removing the IR-blocking filter.
Focus will change and it is almost impossible to avoid getting dust on the sensor.
You camera is fairly sensitive to IR even with the filter.
Try pointing a TV remote at the camera.
-
@thinkviv
As you are online, just to say that I have checked the code and it looks OK.
I will now check the date of the uploaded 100c version.
If necessary, I will upload latest version.
-
Alright, cool. Strange how it's only me having this issue
-
@thinkviv
Past my bedtime, but first try this : http://www.zshare.net/download/91023013934bd390/ (http://www.zshare.net/download/91023013934bd390/)
-
The updated file has the same problem
-
No, but has anyone confirmed they have used dual partitioning ?
Lots of traffic on different threads in the forum. Using cards 4G and larger (via dual partition) seems to be causing problems for lots of people - including me. I have several 2G cards that work fine - I don't seem to be smart enough to follow the various and sundry instructions for dual partition use of my 8G cards though.
I'll predict this will be a subject of interest on this forum for weeks to come.
EDIT : With a little help from philmoz, I got past the PEBKAC part. Seems I did not realize the sdminste.exe format exercise required you to do a two pass thing - create two partitions with the Create Partition button, format the FAT16 partition with the Format button AND THEN use the Swap Partition button to enable the FAT32 partition so that you can Format it as well. Somewhere in there your also need to use the Make Bootable button and also copy the CHDK zip file to both partitions.
-
No, but has anyone confirmed they have used dual partitioning ?
Lots of traffic on different threads in the forum. Using cards 4G and larger (via dual partition) seems to be causing problems for lots of people - including me. I have several 2G cards that work fine - I don't seem to be smart enough to follow the various and sundry instructions for dual partition use of my 8G cards though.
I'll predict this will be a subject of interest on this forum for weeks to come.
4G and larger? I got 4GB works fine. Didnt do any dual partition and all.
I was just thinking, perhaps not relevant, but would it have anything to do with that extended memory thing. Cause when @microfunguy gave the build with extended memory disabled, it seems to fix a lot of 'little' issues for me. Basically SDM ran more smoothly.
-
You can buy battery-operated wireless passive infra-red detectors that send a signal to a receiver.
That can switch +5V to the camera USB and take a photo.
From Hong Kong you can buy IR led security lights that use more than 100 led's.
Don't even think about removing the IR-blocking filter.
Focus will change and it is almost impossible to avoid getting dust on the sensor.
You camera is fairly sensitive to IR even with the filter.
Try pointing a TV remote at the camera.
Thanks, thats helpful. I'll look into that.
I did come across this one little IR sensor light you're meant to install in a dark closet and all, and it turns on as soon as it detects movement.
Theoretically with something like that in place, I wouldnt need to mess around with the camera at all really! The MD script will automatically fire as soon as the LED's light up on the IR sensor, as the 'scene will change' for the camera.
I wouldnt dream of removing the IR - filter from the camera. Way too risky. Might do it on a cheap webcam I got just to see the results.
-
I was wondering if this is possible...
Sometimes you need to quickly take out your camera and take a photo, not wanting to waste that perfect moment.
Having SDM installed slightly increases camera load up time.
Is it possible that SDM can be modified so that you might be able to select an option, say 'Quick Startup Photo', and the camera would take a photo as soon as its started up, loading only 'half' of SDM to quicken the load process. If you turn that option off, SDM would load as normal, taking its sweet time, and therefore allowing all functionality.
How about it? :)
-
I was wondering if this is possible...
Summer is starting (in the Northern hemisphere), I am not spending time on adding requested features.
-
copy the CHDK zip file to both partitions.
The zip file ?
Do you mean the contents of the zip file ?
They only need to be on the large partition 9apart from DISKBOOT.BIN).
-
The updated file has the same problem
You have formatted the large partition ?
(extended memory is disabled in the updated file).
-
At first I simply replaced the DISKBOOT.BIN file with the new one, deleted the folders on the small and large paritions and tried it. When I got the Insufficient space on card message I ran sdminste.exe and did a new install with the new DISKBOOT.BIN file
-
Can I ask again, did you format the large partition FAT32 ?
-
Yes it was formatted FAT32
-
At first I simply replaced the DISKBOOT.BIN file with the new one, deleted the folders on the small and large paritions and tried it. When I got the Insufficient space on card message I ran sdminste.exe and did a new install with the new DISKBOOT.BIN file
Sounds like init_file_modules_task isn't getting called to swap to the large partition.
@Microfunguy
Try adding '*(int*)0x193C=(int)taskHook;' in boot.c in addition to the existing '*(int*)0x1938=(int)taskHook;' line (set both).
I needed to do this on the G12 and SX30 to get dual partitions to work.
Phil.
-
I was wondering if this is possible...
Summer is starting (in the Northern hemisphere), I am not spending time on adding requested features.
umm..you could take your laptop out with ya lol
yea ok fairnuff, i'll remind ya again in winters :)
-
umm..you could take your laptop out with ya lol
yea ok fairnuff, i'll remind ya again in winters :)
I cannot possibly afford a lap top.
First the bad news ...
My relatives will be travelling to Cornwall for a holiday.
The good news ...
I will not be joining them :)
-
umm..you could take your laptop out with ya lol
yea ok fairnuff, i'll remind ya again in winters :)
I cannot possibly afford a lap top.
First the bad news ...
My relatives will be travelling to Cornwall for a holiday.
The good news ...
I will not be joining them :)
Nice... I'll be travelling in a couple of weeks to Pakistan to see my mum.
I'll report if SDM survives 50 C temp in Islamabad. lol
-
Try adding '*(int*)0x193C=(int)taskHook;' in boot.c in addition to the existing '*(int*)0x1938=(int)taskHook;' line (set both).
Here you are http://www.zshare.net/download/91040178e0bfd464/ (http://www.zshare.net/download/91040178e0bfd464/)
In a word, what is required to enable dual partition support ?
100d also contains this :
*(int*)(0x221c+4)= (*(int*)0xc0220024)&1 ? 0x200000 : 0x100000; // replacement for correct power-on. ffc477a0
Not sure what is needed for 100c.
David
-
I'll report if SDM survives 50 C temp in Islamabad. lol
25C is my limit.
-
Try adding '*(int*)0x193C=(int)taskHook;' in boot.c in addition to the existing '*(int*)0x1938=(int)taskHook;' line (set both).
Here you are http://www.zshare.net/download/91040178e0bfd464/ (http://www.zshare.net/download/91040178e0bfd464/)
In a word, what is required to enable dual partition support ?
DataGhost's mods to init_file_modules_task examines the MBR (master boot record). If it finds a large FAT32 partition it tries to fool the firmware into believing that the large partition was the one booted from not the small FAT16 partition.
It's a hack and for it to work the CHDK version of init_file_modules_task has to get executed instead of the firmware version - once the firmware code runs it's too late and you can't use the large partition.
The taskHook function is what tries to ensure that the CHDK code gets run instead of the firmware code - where you hook it in (0x1938, 0x193C, ...) seems to be camera dependent and requires some experimenting to get right.
100d also contains this :
*(int*)(0x221c+4)= (*(int*)0xc0220024)&1 ? 0x200000 : 0x100000; // replacement for correct power-on. ffc477a0
Not sure what is needed for 100c.
David
That line is used to figure whether to start the camera in playback or record mode - if you hold down the on/off button until the CHDK startup code gets to this line then you will boot in record mode, otherwise it boots into playback mode.
You need this as well in all versions to get the startup logic to work.
Phil.
-
Still getting the same message and folders are being created on the small partition
-
try this version http://www.zshare.net/download/91041502f921f067/ (http://www.zshare.net/download/91041502f921f067/)
-
try this version http://www.zshare.net/download/91041502f921f067/ (http://www.zshare.net/download/91041502f921f067/)
SUCCESS!!! I'm not getting the error and SDM is loaded up! Woohooo...
-
I knew it would :)
@philmoz
the hacked branches from init_file_modules_task were all in place ... except the top one which was still the Canon original.
-
@microfunguy,
Got a problem...
The AUTOSTART option in script menu works intermittently. Very annoying. I click on AUTOSTART button, it fires up the script. (I'm using the time lapse script btw). Then I turn the cam off and on and it wont autostart the script. However, sometimes, 1 times out of 20, it would.
Why is this happening? I did change to older build as well to test and does the same thing. RESET all options, still does it.
My computer seems to have a nasty virus though. Could that have something to do with it? (wouldnt think so).
I have also noticed that when I press AUTOSTART, it fires up the script, I end it with FULL SHOOT and then when I get out of ALT menu, and then try to bring up canon menu by pressing MENU, it does not show up and picture freezes until I press MENU again.
Does this happen with you or anyone else? Try stopping and starting AUTOSTART feature 5 or so times.
Another point to note is that there are two CFG files in CHDK folder, is this normal?
EDIT: After messing around with it for quite some time, I seem to have found a temporary solution.
To turn on AUTOSTART:
- Select the AUTOSTART option by keeping the SET button PRESSED for at least 2 seconds.
- The script will automatically try to fire (which, by the way, it should not)
- After those 2 seconds, press FULL SHOOT to stop the script.
- Press MENU again while in ALT mode and go back to SCRIPTING MENU.
- Once in SCRIPTING MENU press SET to select AUTOSTART, notice that this time, the script will not automatically fire.
- Turn the cam off, then on, and the script will autostart.
To turn off AUTOSTART:
- Select the AUTOSTART option by keeping the SET button PRESSED for at least 2 seconds.
- The radio button in AUTOSTART option will blink. In the end press SET once more to make sure the radio button is unselected (if it was selected by the time you took your finger off while keeping it pressed for 2 seconds).
- Turn the cam off, then on, and the script will not autostart.
Note: I reset cameras canon settings as well as SDM settings. (It did not make a spec of difference) The only thing that 'works' is above method.
Question:
Why this behavior? Is it only me who is experiencing this?
-
I'm planning to buy a spare battery from ebay for my ixus 105, so it would be a NB-6L.
I was wondering, if I get one with a high mAh value, such as 1500 mAh, would that be ok? Wont cause no problems would it?
-
I'm planning to buy a spare battery from ebay for my ixus 105, so it would be a NB-6L. I was wondering, if I get one with a high mAh value, such as 1500 mAh, would that be ok? Wont cause no problems would it?
Not unless they repeal Ohm's law. (http://en.wikipedia.org/wiki/Ohm%27s_law)
-
@sh1981
Try Autostart with this version http://www.zshare.net/download/912364022b4e4014/ (http://www.zshare.net/download/912364022b4e4014/)
-
-
-
@sh1981
Try Autostart with this version http://www.zshare.net/download/912364022b4e4014/ (http://www.zshare.net/download/912364022b4e4014/)
Works perfectly!
I've grown so fond of your (or whoever the credit goes to) Time Lapse script that I have it on Autostart all the time now. Turn the cam on, it starts shooting away. With ND filter OUT it shoots even faster I've noticed.
I'm still not sure what ND exposure compensation does?
You might want to, whenever its convenient for your of course, look at this slight glitch with the camera starting. You see, when I start up the camera, I flick the power on button, and it turns on in PLAY mode. Then I press half shoot, and the camera fires up in record mode. Thats fine, totally fine, however sometimes the first flick of the power button does NOT turn the camera on in PLAY mode, it just flashes the green LED and turns off. Sometimes it does this 3 or 4 times.
You might say, keep the power button pressed. That works, starts the camera in record mode straight, however, not always. Infact, it most of the time turns off with lens half extended.
That is why I never ever keep the power button pressed, I always press PLAY button and then half shoot, or I press power button and then half shoot to turn the camera on in record mode.
It's a little glitch that I can, and have been living with. However someday if you fix it, it would make my main use of the camera even easier, which is to turn it on and take as many photos as I can at the fastest shutter speed I can manage, and the Time Lapse script does the job perfect.
Anyway thanks again for fixing the Autostart, wonderful job :)
Cheers :)
-
I'm still not sure what ND exposure compensation does?
If the Canon firmware intended to swing the filter in and SDM decides to swing it out, the photo would be overexposed unless the shutter speed was made faster.
That is what the exposure compensation does.
You might say, keep the power button pressed.
No, I would say have you tried setting the 'Exten Lens' option in the Stereo menu.
Does that not automatically switch you into Record mode ?
-
@microfunguy
Watch this video: MOV0084A.3gp - 5.92MB (http://www.zshare.net/download/9125945692c6a5c0/)
I begin with the camera in AUTO mode.
The lens extended option is ON at this point.
At around 1:37 I turn lens extended option OFF.
The camera is still in AUTO mode.
I then move onto P mode, lens extended off.
I then move onto VIDEO mode, lens extended off.
During the end I try to hold on the power on button for move than 1 second, and the lens gets stuck.
I hold the power on button again and the lens retracts and the camera turns on fine this time.
Some points to note:
- Most of the time the camera turns on fine if I have lens extended option off, canon logo off, SDM logo ON. This is the setting I normally follow.
- It might be a figment of my imagination but, I seem to have noticed that if the camera is started in play mode and the image displayed is a high ISO image such as one taken at ISO 400 or ISO 800, the camera turns on fine most of the time.
- The problem occurs only randomly, as is evident from the video.
- The camera turns on fine, most times, in AUTO mode. In short, AUTO mode seems to cause least trouble.
- Keeping button pressed is a hit and miss, most of the times the lens gets stuck though, regardless of AUTO mode or not.
- Lens extended on or off does not seem to have much of an effect on the behavior.
Final words:
I didnt initially bother too much about this problem or stress on it because I consider it a blessing in disguise, in the sense that I always put it in P mode when I turn cam off and then put it in the camera case. This is because I know it will have trouble firing up in case a button gets pressed!
However it becomes a problem when you're out and about and you miss that picture perfect moment cause the camera wont fire up. lol
My workaround to this problem is to quickly flick the power button and pump the half shoot and pray it turns on! Most of the time it does luckily. :P
-
You are misunderstanding the 'Extend Lens' option.
When it is enabled, if you briefly press the power button to boot the camera it should automatically switch to Record mode.
-
@microfunguy
Watch this video: MOV0084A.3gp - 5.92MB (http://www.zshare.net/download/9125945692c6a5c0/)
I begin with the camera in AUTO mode.
The lens extended option is ON at this point.
At around 1:37 I turn lens extended option OFF.
The camera is still in AUTO mode.
I then move onto P mode, lens extended off.
I then move onto VIDEO mode, lens extended off.
During the end I try to hold on the power on button for move than 1 second, and the lens gets stuck.
I hold the power on button again and the lens retracts and the camera turns on fine this time.
Some points to note:
- Most of the time the camera turns on fine if I have lens extended option off, canon logo off, SDM logo ON. This is the setting I normally follow.
- It might be a figment of my imagination but, I seem to have noticed that if the camera is started in play mode and the image displayed is a high ISO image such as one taken at ISO 400 or ISO 800, the camera turns on fine most of the time.
- The problem occurs only randomly, as is evident from the video.
- The camera turns on fine, most times, in AUTO mode. In short, AUTO mode seems to cause least trouble.
- Keeping button pressed is a hit and miss, most of the times the lens gets stuck though, regardless of AUTO mode or not.
- Lens extended on or off does not seem to have much of an effect on the behavior.
Final words:
I didnt initially bother too much about this problem or stress on it because I consider it a blessing in disguise, in the sense that I always put it in P mode when I turn cam off and then put it in the camera case. This is because I know it will have trouble firing up in case a button gets pressed!
However it becomes a problem when you're out and about and you miss that picture perfect moment cause the camera wont fire up. lol
My workaround to this problem is to quickly flick the power button and pump the half shoot and pray it turns on! Most of the time it does luckily. :P
Sounds like the startup crash problem experienced by a quite a few cameras now:
http://chdk.setepontos.com/index.php?topic=6179.0 (http://chdk.setepontos.com/index.php?topic=6179.0)
Unfortunately the ixus105 hasn't been added to the CHDK main code base so you can't try building CHDK with the fix enabled.
Phil.
-
You are misunderstanding the 'Extend Lens' option.
When it is enabled, if you briefly press the power button to boot the camera it should automatically switch to Record mode.
No, I do not believe I'm misunderstanding it.
It does what you say it should do, you can see it in the start of the video I posted as well. When the video start, you will see that, eventually after pressing the power on button 3 or 4 times, the camera comes to life in play mode, then goes into record mode, automatically, thats cause the lens extended option is enabled.
Therefore the lens extended option is doing what its supposed to do just fine.
Problem is with the camera starting up in the first place.
If I'm still misunderstanding, do correct me. :)
-
@microfunguy
Watch this video: MOV0084A.3gp - 5.92MB (http://www.zshare.net/download/9125945692c6a5c0/)
I begin with the camera in AUTO mode.
The lens extended option is ON at this point.
At around 1:37 I turn lens extended option OFF.
The camera is still in AUTO mode.
I then move onto P mode, lens extended off.
I then move onto VIDEO mode, lens extended off.
During the end I try to hold on the power on button for move than 1 second, and the lens gets stuck.
I hold the power on button again and the lens retracts and the camera turns on fine this time.
Some points to note:
- Most of the time the camera turns on fine if I have lens extended option off, canon logo off, SDM logo ON. This is the setting I normally follow.
- It might be a figment of my imagination but, I seem to have noticed that if the camera is started in play mode and the image displayed is a high ISO image such as one taken at ISO 400 or ISO 800, the camera turns on fine most of the time.
- The problem occurs only randomly, as is evident from the video.
- The camera turns on fine, most times, in AUTO mode. In short, AUTO mode seems to cause least trouble.
- Keeping button pressed is a hit and miss, most of the times the lens gets stuck though, regardless of AUTO mode or not.
- Lens extended on or off does not seem to have much of an effect on the behavior.
Final words:
I didnt initially bother too much about this problem or stress on it because I consider it a blessing in disguise, in the sense that I always put it in P mode when I turn cam off and then put it in the camera case. This is because I know it will have trouble firing up in case a button gets pressed!
However it becomes a problem when you're out and about and you miss that picture perfect moment cause the camera wont fire up. lol
My workaround to this problem is to quickly flick the power button and pump the half shoot and pray it turns on! Most of the time it does luckily. :P
Sounds like the startup crash problem experienced by a quite a few cameras now:
http://chdk.setepontos.com/index.php?topic=6179.0 (http://chdk.setepontos.com/index.php?topic=6179.0)
Unfortunately the ixus105 hasn't been added to the CHDK main code base so you can't try building CHDK with the fix enabled.
Phil.
Looked at your thread, certainly the fact that when the memory card has less photos seems to cause the problem less. However, its not entirely true. I just now, a few hours after posting my video, tried it 25 times and it turns on fine everytime.
If I read correct, on your thread, after the FIX, people are having problems with RAW.
The problem is not serious enough for RAW to be sacrificed. I can live with it. It occurs I'd say 30% of the time, has its mood-swings, as if my wife wasn't enough.
Having said that, I'm sure microfunguy would come up with some fix for SDM :)
-
Sounds like the startup crash problem experienced by a quite a few cameras now:
i have #defined that fix in camera.h.
I assume it is not necessary to include a default #undef at the top of camera.h ?
-
Looked at your thread, certainly the fact that when the memory card has less photos seems to cause the problem less. However, its not entirely true. I just now, a few hours after posting my video, tried it 25 times and it turns on fine everytime.
If I read correct, on your thread, after the FIX, people are having problems with RAW.
The problem is not serious enough for RAW to be sacrificed. I can live with it. It occurs I'd say 30% of the time, has its mood-swings, as if my wife wasn't enough.
Having said that, I'm sure microfunguy would come up with some fix for SDM :)
The fix is currently in place for the G12, SX30, SX20, SX130is, S95, IXUS120, A495 and A590 and there are no reported problems with RAW files. Some of the workarounds developed during the investigation affected RAW; but the current fix does not.
The symptoms are random as you are experiencing (I also had long periods where the problem never occurred) which is what made it difficult to diagnose and fix.
The fix is quite simple and affects only the 'open' function in platform/generic/wrappers.c so could probably be added to SDM fairly easily.
Phil.
-
Sounds like the startup crash problem experienced by a quite a few cameras now:
i have #defined that fix in camera.h.
I assume it is not necessary to include a default #undef at the top of camera.h ?
Did you also include the change to platform/generic/wrappers.c for the 'open' function?
This is where the fix resides, the #define just enables it.
Phil.
-
Any progress on the startup crash so far? :)
-
Any progress on the startup crash so far? :)
No, I have been very busy.
It is probably better if you contact me with an email address.
Your holiday is getting near ...
-
Any progress on the startup crash so far? :)
No, I have been very busy.
It is probably better if you contact me with an email address.
Your holiday is getting near ...
yep, off in 10 days now. thats ok, take your time, just dont forget poor ixus 105 lol
-
Got a slight...issue
What I'm trying to do is take photos outside, in the sun, blur free, while walking or in a moving vehicle.
To achieve this I tried the following:
Try 1: I bumped up the shutter speed to 1/1000, set ISO to AUTO.
Try 2: I bumped up the shutter speed to 1/1000, set ISO to AUTO. Set exposure compensation ON.
Try 3: I bumped up the shutter speed to 1/1000, set ISO to AUTO. Set exposure compensation ON. Set ND filter OUT.
Problem:
On every try, though I achieved my target of blur free photos, but only in 70% of the case. The shutter speed intermittently went down, sometimes to 1/250.
What I want is the shutter speed to remain constant, no matter what.
Perhaps I've failed to understand what exposure compensation does in first place. Perhaps its got nothing to do with it at all.
Anyhow, how do I get high shutter speed at all times, without the camera interfering?
-
how do I get high shutter speed at all times, without the camera interfering?
I guess that is not urgently needed to photograph your granny in the bright light of India :)
When the shutter speed gets over about 1/1500, the Canon firmware will swing the ND filter into position and reduce the shutter speed by about a factor of 8x.
In the Bracketing\Overrides menu, force the ND filter OUT and select constant exposure mode.
Does that help ?
Hmmm .. reading your post again that seems to be what you mean by 'exposure compensation'.
I do have new uBasic commands, used as follows :-
set_max_iso 400
shoot_fast_at 1/2000
I can post a build, remind me of your firmware version.
-
how do I get high shutter speed at all times, without the camera interfering?
I guess that is not urgently needed to photograph your granny in the bright light of India :)
When the shutter speed gets over about 1/1500, the Canon firmware will swing the ND filter into position and reduce the shutter speed by about a factor of 8x.
In the Bracketing\Overrides menu, force the ND filter OUT and select constant exposure mode.
Does that help ?
Hmmm .. reading your post again that seems to be what you mean by 'exposure compensation'.
I do have new uBasic commands, used as follows :-
set_max_iso 400
shoot_fast_at 1/2000
I can post a build, remind me of your firmware version.
lol...that granny comment made me laugh... its not india, its Pakistan, indians don't buy Canon.
Yes, I meant ND constant exposure, apologies for that.
Yes, I've tried, as I mentioned in Try 3, ND constant exposure selected, ND filter OUT.
However, I shall try again.
Would appreciate the new build.
Firmware version is 100.D
By the way I bought this waterproof bag from ebay for a real bargain, cost me 1p plus 99p postage n packaging. A few days back, was taking photos in the rain, and this problem I mentioned quite some time back, with the time-lapse script, which makes it 'stuck' if its stopped while the green / red led is NOT blinking, kicked in. The camera jammed inside the case and started making a beeping sound. I had to take the battery out, and to do that, with the lens stuck extended, i had to cut open my 1p waterproof bag with a pair of scissors, hence making me lose my precious 1p. Dont worry, I wont sue you ;)
-
Tried it second time like I said, shutter override 1/800, ND constant exposure ON, ND filter OUT. Took most at 1/800, some at around 1/1500, and 3 of them came out at 1/40 ISO 80!!!
However, the ones at 1/40 still came out looking pretty much like others.
So could it be wrong EXIF information the camera is giving out, and in reality the shutter speed is 1/800?
OR, is the shutter speed override ineffective when ND constant exposure is on or when ND filter is OUT or IN.
-
indians don't buy Canon.
Did not know that, if true.
Would appreciate the new build.
Here you are http://www.zshare.net/download/920831479dc6a25e/ (http://www.zshare.net/download/920831479dc6a25e/)
The command 'shoot_fast_at' has an optional second parameter that returns the success or not of fast shutter.
If it succeeded, the value will be the negative of the ISO used.
If not, it will be the actual shutter speed.
e.g. 200 is 1/200 sec.
If you have a second parameter, there is an optional third parameter.
It can have any value.
It is to indicate if a previously computed brightness value should be used instead of actually measuring it for this photo.
It is intended for cameras attached to a balloon in the stratosphere and swinging up and down.
As per a Francesco Bonomi Lua script, it averages certain brightness readings.
Try this script :-
@title Shoot Fast
@param n Numerator
@default n 1
@param d Denominator thousandths
@default d 2
@param m Max iso
@default m 400
sync_off
set_max_iso_to m
sleep_for_seconds 2
shoot_fast_at n/d*1000 , b
if b < 0 then gosub "fast" else gosub "slow"
sleep_for_seconds 5
end
:fast
line_1 "#Fast shoot at",-b,"ISO"
return
:slow
line_1 "!shutter was 1/";b,"at max ISO"
return
So, shutter speed = n/d = 1/2000 sec default value.
Indoors, it will set the fastest shutter speed it can with ISO pushed to your maximum preferred value.
problem I mentioned quite some time back, with the time-lapse script
It is up to you to remind me after your holiday.
-
indians don't buy Canon.
Did not know that, if true.
Would appreciate the new build.
Here you are http://www.zshare.net/download/920831479dc6a25e/ (http://www.zshare.net/download/920831479dc6a25e/)
The command 'shoot_fast_at' has an optional second parameter that returns the success or not of fast shutter.
If it succeeded, the value will be the negative of the ISO used.
If not, it will be the actual shutter speed.
e.g. 200 is 1/200 sec.
If you have a second parameter, there is an optional third parameter.
It can have any value.
It is to indicate if a previously computed brightness value should be used instead of actually measuring it for this photo.
It is intended for cameras attached to a balloon in the stratosphere and swinging up and down.
As per a Francesco Bonomi Lua script, it averages certain brightness readings.
Try this script :-
@title Shoot Fast
@param n Numerator
@default n 1
@param d Denominator thousandths
@default d 2
@param m Max iso
@default m 400
sync_off
set_max_iso_to m
sleep_for_seconds 2
shoot_fast_at n/d*1000 , b
if b < 0 then gosub "fast" else gosub "slow"
sleep_for_seconds 5
end
:fast
line_1 "#Fast shoot at",-b,"ISO"
return
:slow
line_1 "!shutter was 1/";b,"at max ISO"
return
So, shutter speed = n/d = 1/2000 sec default value.
Indoors, it will set the fastest shutter speed it can with ISO pushed to your maximum preferred value.
problem I mentioned quite some time back, with the time-lapse script
It is up to you to remind me after your holiday.
Tried it, seems to work nicely.
Would like to act as an intervalometer (time lapse) with continuous shoot. I'll figure that out myself, i suppose its just a matter of making a loop in the script.
I never seem to get the FAST SHOOT message...at times I get something like shutter was 1/6200 ...but I couldnt get that Fast Shoot message...I mean under what circumstances could n/d*1000 be equal to 0 or less than 0 anyway?
I'm still in the process of trying it out.
Edit:
I tried some more and got it shooting at FAST SHOOT if I point it at the sky.
On one occassion it did shoot at 1/300 ISO 80.
Edit:
Changed the script to
@title Shoot Fast
@param n Numerator
@default n 1
@param d Denominator thousandths
@default d 4
@param m Max iso
@default m 400
sync_off
set_max_iso_to m
sleep_for_seconds 2
:start
shoot_fast_at n/d*1000 , b
if b < 0 then gosub "fast" else gosub "slow"
rem sleep_for_seconds 5
end
:fast
line_1 "#Fast shoot at",-b,"ISO"
gosub "start"
return
:slow
line_1 "!shutter was 1/";b,"at max ISO"
gosub "start"
return
Got a "uBASIC 15: stack full" message after a few photos.
A lot of times it takes photos at slower shutter speed than possible, as in it goes at ISO 80 and shutter 1/400 etc while it could be going at ISO 400.
Perhaps I'm just not using it right.
-
Try again but make sure no shutter-speed or ND filter overrides are enabled.
-
@microfunguy,
Of all the things in the world, I forget to pack my battery and charger! Feel like pullin all me hair out!
-
I guess that solves your problems .. for now.
I dont have enough hair to pull out .
-
Of all the things in the world, I forget to pack my battery and charger! Feel like pullin all me hair out!
Four words come to mind : Amazon.com and overnight delivery.
Or whatever the equivalent is in your part of the world.
How much did you spend on your vacation afterall ?
-
Hey, guys! I started reading the first couple of pages but decided it would be a good idea to make sure I'm in the right place before I go any further. I'll confess right now I'm rather technologically clueless, but my determination typically more than makes up for that deficiency...well, that and a good bit of patience from helpful others. :D
I have a Canon Powershot SD1300 IS. I tried running something called Acid to extract my firmware version but it shows that I don't have any I think?!
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi176.photobucket.com%2Falbums%2Fw166%2FLearningCurve2p2%2FHmmmm.jpg&hash=b162c5fd58a62eb01fc66f5414313fae)
Okay, so is it even possible for me to use the information here?
Thanks!
LC
-
Heck, no one can see that. I've cropped it and am trying again:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi176.photobucket.com%2Falbums%2Fw166%2FLearningCurve2p2%2Fcropped.jpg&hash=989e563c8ccc4c7763f21552f40f1813)
Also, I tried reloading the photo, checking and unchecking the various boxes, but I never got a Firmware Version to show up. :(
-
@learningcurve2p2
Normally the firmware version can be extracted from a photo's EXIF data, but the relevant entries
are often stripped by software loading them ... retry with a picture straight from the camera, as in
not having been opened in any software.
hope that helps,
wim
-
@learningcurve2p2
Normally the firmware version can be extracted from a photo's EXIF data, but the relevant entries
are often stripped by software loading them ... retry with a picture straight from the camera, as in
not having been opened in any software.
hope that helps,
wim
...or upload fresh image on a host service and send the link here and someone will help you find which version firmware you have
-
Is this okay?
http://i176.photobucket.com/albums/w166/LearningCurve2p2/002.jpg (http://i176.photobucket.com/albums/w166/LearningCurve2p2/002.jpg)
-
Unfortunately it is not good, the picture must be the original resolution as it is on the card in the camera, he must not be reduced like this (1024x768).
Upload an image from the card into the computer, compress with a program WinRar or any other instance and upload on MEGAUPLOAD.com and then send the link.
-
Unfortunately it is not good, the picture must be the original resolution as it is on the card in the camera, he must not be reduced like this (1024x768).
Upload an image from the card into the computer, compress with a program WinRar or any other instance and upload on MEGAUPLOAD.com and then send the link.
I understand theoretically but in practice I do not. I have a new picture on my card again now but as soon as I upload it the pc is going to pull it in using some software. It's then saved into my pictures directory. I still have the last one there as well. Do I then take it from there and compress it using WinRar? If not, then how do I get it to WinRar for it to be able to do it's thing without using the software my pc typically uses to put it onto my hard drive?
Thank goodness I confessed early that I am a technological dimwit! :-P
-
Upload image from My pictures, if the same resolution as selected in the camera, do not need to compress the file just send it to the MEGAUPLOAD.
-
If you have a card reader you use it to transfer images from card to computer.
-
If you have a card reader you use it to transfer images from card to computer.
Thanks, that's how I do it. Am I getting warmer?
http://www.megaupload.com/?d=0WI6925H (http://www.megaupload.com/?d=0WI6925H)
-
This is OK.
Firmware version: 100D
-
This is OK.
Firmware version: 100D
Woohooooo! Thanks much, blackhole!!
So having figured that out...have I come to the right place? If so, is there a cliff notes of what I need to do in order to get CHDK working for my camera or do I just need to start from the beginning and begin DL'ing (or whatever I'll need to do) in pieces?
Thanks,
LC
-
Unfortunately for your camera still not a fully functional CHDK.
Microfunguy has some version of SDM that is similar, so it is best to contact him for help.
-
Unfortunately for your camera still not a fully functional CHDK.
Microfunguy has some version of SDM that is similar, so it is best to contact him for help.
I will do. Thanks again for all of the help! You went WAY above and beyond. :-)
-
Microfunguy sent me a DL and said I might should check on the forum for how to prepare my SD card. I DL'ed the file but beyond that I'm not sure what to do. The file is DISKBOOT.BIN and it also came with a Stratos2.bas.txt file. Is this something someone in here can help with or do I need to find another thread to assist me from here?
Thanks,
LC
-
Download the firmware version for your camera and also 'Common Files.zip' from this link:
http://stereo.jpn.org/eng/sdm/download.htm (http://stereo.jpn.org/eng/sdm/download.htm)
Unzip all files into the same folder.
Read SDM-Basic Shooting pdf and follow the instructions.
Good luck!
-
Download the firmware version for your camera and also 'Common Files.zip' from this link:
http://stereo.jpn.org/eng/sdm/download.htm (http://stereo.jpn.org/eng/sdm/download.htm)
Unzip all files into the same folder.
Read SDM-Basic Shooting pdf and follow the instructions.
Good luck!
Haha, thanks for the luck and the compass! I'll let you know how it goes...
-
it also came with a Stratos2.bas.txt file.
That is only needed if you are sending a balloon to the edge of space !
In fact, in the last five hours such a balloon took-off from Las Vegas, avoided Area 51 restricted airspace and landed in some rugged mountains.
As I write this, recovery of the payload is awaited.
I hope Stratos2.bas worked OK :)
-
Haha, I probably won't need that one then! ;)
The camera looks different now when I turn it on so something obviously happened. :D The Basic_Shooting file doesn't have much in the way of using this for a single camera. Do you have any recommendations for where I might go to read up on how to access and utilize the new settings? I'm not certain if it's the same as CHDK or not...
Thanks so much!
LC
-
I recommend that time_lapse.bas is your normal resident script.
All info is here http://stereo.jpn.org/eng/sdm/index.htm (http://stereo.jpn.org/eng/sdm/index.htm)
However, to keep it simple, what do you want to do ?
-
I recommend that time_lapse.bas is your normal resident script.
All info is here http://stereo.jpn.org/eng/sdm/index.htm (http://stereo.jpn.org/eng/sdm/index.htm)
However, to keep it simple, what do you want to do ?
I'll do as you suggest (as soon as I read up on how to do it!).
Essentially I would like to learn to shoot in manual mode. I've read a bit about the various components that go into taking a good shot but reading =/ understanding. I'm not really sure what I will photograph most often as I'm just getting into photography. Rushing out and spending a fortune on a camera to get my feet wet doesn't make much sense. I'm a frugal perfectionist so the idea of purchasing something only to find that it wasn't an optimal choice for whatever direction I gravitate towards is a bit abhorrent.
For now I'll probably mostly be photographing nature, some architectural details, my kids (when their moods allow for it - lol)...
Oh, and I plan to shoot everything in RAW.
Thanks, MFG! I really appreciate all of the help!!
-
I'm a frugal perfectionist
Good, then you will not need (eventually) to take many photos.
Just the few worth taking.
As for raw, well on point-and-shoot cameras you may be disappointed, but that is another topic.
-
Another of my goals is to use as little post processing as possible, but I figure RAW gives me the most flexibility regardless. IDK if I'll ever get to the point of taking only a sparse few shots. Digital is free, other than the massive amounts of time you have to spend pouring through them deciding if shot A or B is better. I'll try to make you proud though...eventually. :D
-
I recommend that time_lapse.bas is your normal resident script.
All info is here http://stereo.jpn.org/eng/sdm/index.htm (http://stereo.jpn.org/eng/sdm/index.htm)
However, to keep it simple, what do you want to do ?
I'll do as you suggest (as soon as I read up on how to do it!).
Essentially I would like to learn to shoot in manual mode. I've read a bit about the various components that go into taking a good shot but reading =/ understanding. I'm not really sure what I will photograph most often as I'm just getting into photography. Rushing out and spending a fortune on a camera to get my feet wet doesn't make much sense. I'm a frugal perfectionist so the idea of purchasing something only to find that it wasn't an optimal choice for whatever direction I gravitate towards is a bit abhorrent.
For now I'll probably mostly be photographing nature, some architectural details, my kids (when their moods allow for it - lol)...
Oh, and I plan to shoot everything in RAW.
Thanks, MFG! I really appreciate all of the help!!
When you get a photo out of an IXUS 105 in RAW, it is so highly messed up that you'd probably end up giving up on it. However, having said that, if you do succeed in fixing the distortion, colors etc and making it look better than the jpeg the camera produces, make sure you do SHARE IT with us, or at least me, because I myself have always been interested in RAW but couldnt get far with this cam.
When you talk about shooting in manual mode, to me, three things come to mind, shutter speed, aperture and ISO. Well, SDM does not really let you change the ISO, so that option is gone, this cam also happens to have no aperture, so thats gone as well, so the only thing you're really left with is shutter speed. When it comes to shutter speed, it lets you shoot at 1/40,000 of a second, i.e you can theoretically shoot something like a F1 racecar as its whizzin by. You can also reduce shutter speed to 65 seconds, and I've used it a handful of times really, when I wanted to shoot some stars in the sky, then I got bored.
Where SDM, in my humble opinion, really helps is with the automated scripts. Motion detect, time-interval, LCD off etc are some of my favorites. Besides that it lets you zoom in and out during movie capture, which is very good.
You mentioned photographing nature, kids and architectural detail.
From my experience, its not SDM that really plays a part in all three, but your ability to judge the right settings (usually built in already). Say for example nature, if I were you, I'd choose the Foliage Mode. This would give me a nice contrast of colors as well as good enough ISO, i.e ISO 200. If I want a better photo of nature, I'd go on P mode, choose ISO 80 and then choose VIVID COLORS in the color mode. I would put the cam on tripod and turn image stablization OFF. I would also zoom in a little bit to fix the barrel distortion that any point and shoot camera with wide lens is prone to. If shooting through a window or a glass, I would zoom in full, for some reason it gives me clearer shots in this case. Note that I would have face detection OFF during all this and metering to weighted.
For kids, if shooting outdoors I would choose P mode with ISO 80 and override shutter to 1/250. I would then apply I-CONTRAST if needed. I just might choose UNDERWATER MODE at times, giving me fast shutter speed automatically. I would have face detection OFF if they are moving rapidly, and ON if stationary.
For kids, if shooting indoors, if they are stationary I would always choose AUTO mode with flash on AUTO. Face detection is ON by default in AUTO, there is nothing you can do about it, so I would choose this mode only if kids are stationary. Else, I would switch to PORTRAIT MODE, flash AUTO, face detection OFF, metering centered. I might bump ISO to 400 if they are moving very rapidly.
For architectural details, I would choose MACRO MODE and shoot without a flash. If with flash, I would put a tissue on flash, folded 3 times to diffuse the flash. I would choose max ISO 200 else detail will be lost substantially.
Note that all that I said is from my own personal experience. It might work for you, if you find I'm wrong, do share, I might learn a thing or two as well. :) Also, all the technical stuff I mentioned is already there in your camera manual.
Hope that helps.
-
@microfunguy,
Finally got my charger and battery!
Anyway about that camera-getting-stuck-while-turning-on problem, flicking on button and then repeatedly pressing FUNC/SET seems to turn it on fine. I can live with that.
Noticed that if I set shutter override to 65 secs, the overrides goes away after 1 photo, the radio button remains selected, but I have to turn cam on and off. Not to worry though, not like I have a 65 sec photo everyday.
-
REALLY helpful, sh1981! Thanks so much!!
I read through the SDM and felt a bit more confused rather than enlightened. It seemed like there were some gaps and I wasn't sure if it was just in my understanding or whether it was in the capabilities of SDM itself. After reading your post I'd guess it's some hybrid of the two.
I've been manually messing around with my camera for the past month or so. Some of the things you've mention I've stumbled upon by myself, like the Vivid color option for instance. Some of it though I haven't. I knew I couldn't change the aperture without SDM but was hoping I could with it. I guess not. Bummer because what I really wanted to be able to do was to learn to manually select the three you mentioned. Since they are interdependent when you take one away then your capability for growth towards understand how they interrelate is severely limited.
I'm not sure if you can answer this question or not but I'll ask to see -- if you cannot then perhaps someone else might be able to. If I had one of the P&S cameras which allowed the full functionality of CKDK would I be in better shape? I'm thinking that perhaps spending $100 or so might be worth it if it would allow me to DL CKDK and to change the aperture and whatnot. It's likely I could probably find a camera for dirt cheap on Craig's List or some such even. It's possible that all I'm doing is delaying the purchase of a more sophisticated camera but if I was able to be relatively proficient with the P&S then it might meet whatever needs I had well enough to get me quite a ways down the road. Do you have any thoughts on this?
One last question...I kept pressing buttons and whatnot in order to get the options on the camera to change but I felt as though I was mostly dumb-lucking it. Are there actual "instructions" for how to select the various options or even what they all mean?
Thanks again so much! I'm going to keep a copy of your post in a Word file I've been keeping so I can refer back to again as I better learn my head from a hole in the ground. :-D
-
I knew I couldn't change the aperture without SDM but was hoping I could with it.
A bit tricky when your camera does not have an aperture.
-
I knew I couldn't change the aperture without SDM but was hoping I could with it.
A bit tricky when your camera does not have an aperture.
RL LOL...I said I was technologically-challenged!! I thought perhaps SDM could add the functionality, just as it was adding the various other stuff it does. Thanks for clarifying though. :-)
-
Even at wide-angle (because it varies with focal length) your camera has an aperture equivalent to f20 on a 35mm camera.
Not being able to control depth-of-field with aperture is therefore not a problem.
Just the opposite, for small sensor camcorders people make devices to reduce the depth-of-field.
You can control exposure by swinging a neutral density filter into or out of position.
The image EXIF data records that as an aperture change, even though it is not.
It just describes how much the sensor illumination is changed by.
-
Even at wide-angle (because it varies with focal length) your camera has an aperture equivalent to f20 on a 35mm camera.
Not being able to control depth-of-field with aperture is therefore not a problem.
Just the opposite, for small sensor camcorders people make devices to reduce the depth-of-field.
You can control exposure by swinging a neutral density filter into or out of position.
The image EXIF data records that as an aperture change, even though it is not.
It just describes how much the sensor illumination is changed by.
Makes sense, MFG. Thanks!
-
REALLY helpful, sh1981! Thanks so much!!
I read through the SDM and felt a bit more ...
Thats right, it is a hybrid between knowing the basics of photography, knowing the functions available in your camera and SDM. SDM documentation is not written by a prize winning author, I agree, but its all about finding what you need to do really. For instance, I care about trying to make my camera zoom more than possible, so I looked into digiscoping. I wanted photos taken automatically without that annoying red light, so I looked into time-lapse. I wanted to turn my camera into a CCTV, so I looked into motion detection script. I wanted photos taken uniformly everytime I pointed towards the sky, so I looked into ND filter.
I've been manually messing around with my camera for the past month or so. Some of the things you've mention I've stumbled upon by myself, like the Vivid color option for instance. Some of it though I haven't. I knew I couldn't change the aperture without SDM but was hoping I could with it. I guess not. ...
If you really want growth, go for interchangable lens cameras, or bridge cameras. Look on http://snapsort.com (http://snapsort.com) . First of all you must understand that there are features of a camera that you are stuck with, forever, for example its maximum zoom, its sensor size etc. CHDK or SDM or anything for that matter will not be able to change that. If it could, we would have one single generic camera, perhaps we will someday in future.
Secondly, you wont be limited at all in this camera. The only limitation is aperture, and that also can be overridden by ND filter, which will allow you to darken or lighten the scene just as in a real aperture. What you will NOT be able to do is control depth of field. Here is an example of DOF http://en.wikipedia.org/wiki/File:Shallow_Depth_of_Field_with_Bokeh.jpg (http://en.wikipedia.org/wiki/File:Shallow_Depth_of_Field_with_Bokeh.jpg)
Even if you get say, a canon A3000 which is relatively cheap point n shoot, you might be able to control the aperture with CHDK, however, the maximum light will be almost the same as what an IXUS 105 would get. Aperture is like your iris, so lets say you got one eye without an eyelid and one eye with an eyelid. You open the eye with the eyelid, all the way, and you will let in maximum light. You uncover the eye without an eyelid and would you will still get the same light as the other eye. So say you get an A3000 or A2000 with an aperture (eyelid), and compare it with an ixus 105, if I'm not wrong, at their max they will both be letting in same amount of light based on their similar sensor size and lens construction. Did it ever occur to you that maybe canon did not put an aperture cause it was so unneccesary in a small point and shoot anyway? I mean you can achieve same results with an ND filter. So no good there. You will however be able to work the DOF with a camera having an aperture. If you really love the effect of background being blurred, as a last resort you just might be able to achieve it with some computer software tweaking afterward. Look here http://en.wikipedia.org/wiki/Focus_stacking (http://en.wikipedia.org/wiki/Focus_stacking) and here http://www.apple.com/downloads/macosx/aperture/editdepthoffield.html (http://www.apple.com/downloads/macosx/aperture/editdepthoffield.html) . So I dont think just because you cant control DOF on this cam you will be severely limited in your learning growth.
I'm not sure if you can answer this question or not but I'll ask to see -- if you cannot then perhaps someone else might be able to...
You will never be able to change aperture in any IXUS cameras because, they do not have one. As far as my knowledge goes, on G and A series, you can. If your need is to control DOF, go for something like G9 or A3000 or A2000.
You said 'whatever needs'. The needs need to be defined. Once you've done that, a site like snapsort should be your first visit. Why? Because there is more to camera hardware than software that matters. I'd ask questions like whats the sensor size? Is image stablization lens based or sensor shift? How many shots can you take with one battery charge? How long does it take for the camera to turn on before you can take photos else you might miss that magic moment. How many photos can it take in succession? Is the video 1080p or 480p?
You will realise that even if you get a high-end camera, be it canon, it might not support CHDK. CHDK is basically for enhancing capabilities of low end canon point n shoots really. You cant use it on canon DSLRs. So look here first http://chdk.wikia.com/wiki/Template:Supported_Cameras (http://chdk.wikia.com/wiki/Template:Supported_Cameras)
One last question...I kept pressing buttons and whatnot in order to get the options on the camera to change but I felt as though I was mostly dumb-lucking it. Are there actual "instructions" for how to select the various options or even what they all mean?
The manual booklet provided is abridged, look here for the detailed manual http://files.canon-europe.com/files/soft37742/manual/IXUS105_107_CUG_EN.pdf (http://files.canon-europe.com/files/soft37742/manual/IXUS105_107_CUG_EN.pdf)
Cameras are like cars, whether you're driving a merc or a fiat, you gotta know the road rules. I sit in a merc and I feel cold, what do I look for? Thats right, the heater. I want a photo of the sky, what do I look for? ND filter IN, shutter speed 1/200, ISO 80, and most of the time I get the shot that I want.
Let me give you another example. You seen those photos of race cars where the background seems blurred and the car is going full speed but is clearly in focus? I wondered how that happened. Heres what I did on my ixus 105 to achieve it. I set the image stablization mode to panning. I attached a rubber band to the bottom of my handheld tripod and held the band down by my foot. Then I 'panned' the camera as the car was passing by. I also set the cam to continuous shoot and kept iso to 400. The point is, I found out about stuff like IS mode panning and the rubberband trick only after I had the vision of taking a photo like of those racecars.
Thanks again so much! I'm going to keep a copy of your post in a Word file I've been keeping so I can refer back to again as I better learn my head from a hole in the ground. :-D
Thats ok, no need to thank me, I'm more amateur than you really. What led me to SDM was only my need to zoom in and out during movie capture which microfunguy helped me out with. As I wanted to do more stuff, like extending zoom (digiscoping), and that panning thing I mentioned above, as well as turning my cam into CCTV with motion detect and taking photos automatically (time lapse), I kept on coming back to learn more.
No matter how silly your question might appear to you, do ask it, I might learn a bit as well!
-
In fact, in the last five hours such a balloon took-off from Las Vegas, avoided Area 51 restricted airspace
Hmmm ... not quite ... this has caused some problems.
Waiting for return of payload.
Hope 'they' enjoy examining my script !
-
@microfunguy,
What script was it? Was it the same as the one you gave me, fast shoot one, cause that didn't work too well with me, maybe I gave up too early on it.
-
Well, it did a lot more than that one.
Anyway, you have not been forgotten, it is all about allocating time.
So, post specific problems.
-
Well, it did a lot more than that one.
May I try it?
-
May I try it?
Later.
First, you may like to see if PTP works on IXUS105 100c :- http://www.zshare.net/download/9322818670309a22/ (http://www.zshare.net/download/9322818670309a22/)
Find out how to install and test libusb and then turn on camera and switch to Playback mode.
If you do not hear the PTP 'On connect' event, enter ALT mode and press SET until you hear a beep and 'UL' (Upload) is displayed at bottom of screen.
In a DOS command window on your PC, type ptpcam --sdm.
Try the following :-
<conn> version
<conn> led 1
<conn> led 0
<conn> record
<conn> run beep
<conn> run beep 10
runs the beep background task and beeps every ten seconds.
It keeps running even if you close ptpcam and exit ALT mode on the camera.
So :-
<conn> run beep_off
<conn> play
<conn> q
-
May I try it?
Later.
First, you may like to see if PTP works on IXUS105 100c :- http://www.zshare.net/download/9322818670309a22/ (http://www.zshare.net/download/9322818670309a22/)
Find out how to install and test libusb and then turn on camera and switch to Playback mode.
If you do not hear the PTP 'On connect' event, enter ALT mode and press SET until you hear a beep and 'UL' (Upload) is displayed at bottom of screen.
In a DOS command window on your PC, type ptpcam --sdm.
Try the following :-
<conn> version
<conn> led 1
<conn> led 0
<conn> record
<conn> run beep
<conn> run beep 10
runs the beep background task and beeps every ten seconds.
It keeps running even if you close ptpcam and exit ALT mode on the camera.
So :-
<conn> run beep_off
<conn> play
<conn> q
I'm on 100.d
As far as I know, PTP only lets you transfer files from the cam to the pc...and it already does that. What new functionality would be added here?
Give me the 100d version and I'll try it out.
-
Give me the 100d version and I'll try it out.
http://www.zshare.net/download/93245009389068b9/ (http://www.zshare.net/download/93245009389068b9/)
-
Give me the 100d version and I'll try it out.
http://www.zshare.net/download/93245009389068b9/ (http://www.zshare.net/download/93245009389068b9/)
Tried installing libusb, there is no such command as ptpcam.
You need to provide me the exact link to this libusb and ptpcam.
Also as I asked specifically, tell me what new functionality will this add cause as far as I know, I'm already able to transfer photos from the cam to pc with sdm.
-
We can do all sorts of things.
But before I describe that we need to get it working.
First of all, see 'LibUSB driver for windows' here http://chdk.wikia.com/wiki/PTP_Extension (http://chdk.wikia.com/wiki/PTP_Extension) .
Ignore any message about replacing newer versions of drivers.
When that is working, you will hear an audible 'on connection' event when you attach to PC with camera in playback mode.
-
I'm very worried!
Got a E32 error on my camera.
To be specific here is what the camera says "a camera error was detected, will shut down automatically.. restart camera E32"
It does this after taking continuous photos, say 10 in a row, after about a minute.
Note that a day back I made a video while driving in the afternoon sun. Temperature was 39 degree C outside. I drove for more than half an hour. When I came home the camera was so hot I had to bring it back rolled in tissues.
Could that have something to do with it? I'm sure its not dust or anything as I'm pretty careful and I clean it once a month.
Dont advise me to take it to a canon repair centre.
Note that the camera does take photos fine, as long as its taking them (i.e for a minute or so), then it shows the E32 error and switches off. It can zoom in and out so I'm not entirely convinced its lens error.
Might the sun have blown the sensor? Could it be the humidity?
Help!
-
Temperature was 39 degree C outside.
Are you still in Pakistan ?
the camera was so hot I had to bring it back rolled in tissues.
Could that have something to do with it?
I would certainly think so.
Dont advise me to take it to a canon repair centre.
In that cast throw it in the bin.
Alternatively, it could be a good candidate for trying to override the warning by using the firmware function 'funnel' mentioned some days ago.
http://chdk.setepontos.com/index.php?topic=6725.msg71339#msg71339 (http://chdk.setepontos.com/index.php?topic=6725.msg71339#msg71339)
Of course, that could destroy the functioning of the camera.
the camera does take photos fine
Might the sun have blown the sensor?
???
Maybe it will recover when you bring it back to the UK.
-
Temperature was 39 degree C outside.
Are you still in Pakistan ?
the camera was so hot I had to bring it back rolled in tissues.
Could that have something to do with it?
I would certainly think so.
Dont advise me to take it to a canon repair centre.
In that cast throw it in the bin.
Alternatively, it could be a good candidate for trying to override the warning by using the firmware function 'funnel' mentioned some days ago.
http://chdk.setepontos.com/index.php?topic=6725.msg71339#msg71339 (http://chdk.setepontos.com/index.php?topic=6725.msg71339#msg71339)
Of course, that could destroy the functioning of the camera.
the camera does take photos fine
Might the sun have blown the sensor?
???
Maybe it will recover when you bring it back to the UK.
Yes I'm still in Pakistan, temperature that day must be at least 37 degrees and the aluminum body on the camera would have hiked it up to 45 at least, way past the 40 degrees recommended.
The camera shuts off in around 45 seconds with E32 error, even if left untouched. Note that this does NOT happen if in playback mode.
I carefully cleaned the lens casing, there was nothing stuck there. It is certainly NOT a lens error. I mimicked a lens error by blocking its path during extension, in that case it would give a lens error. This is something else.
@MICROFUNGUY,
The function by funnel you mentioned, can you integrate it for me? If it works I'll go so far as to say I'm even willing to pay you for it.
Sending it to a canon repair centre in Karachi from Islamabad would cost me loads, more than twice the cost of the camera itself. Coming back to UK right now is not an option, I have to remain here for next 2 months due to work.
The camera has not suffered any physical damage by dropping or by getting exposed to a lot of dust. I'm sure its not a lens related issue. Please look into it mate it'll mean a lot to me.
-
The function by funnel you mentioned, can you integrate it for me?
I will follow this in that separate thread so that funnel can respond publicly what is proposed.
It has never been tried before, we do not know what will happen.
-
The function by funnel you mentioned, can you integrate it for me?
I will follow this in that separate thread so that funnel can respond publicly what is proposed.
It has never been tried before, we do not know what will happen.
Thanks so much that will be great.
-
I was trying to bracket with Tv...1/3 EV values. Works fine in continuous mode if I do it manually, however I cant seem to figure out how to do it with time-lapse script.
-
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)
-
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)
Yea, I followed this from above:
A) Set camera to continuous-shooting mode
Set 'save stack' to '1', 'num of 1/3 EV steps' to '3', 'bracket exposures' to '3', 'single/cont/timer' to '1'.
Start script.
On completion, the approximate time required for one bracketing sequence will be indicated.
This is particularly useful when doing auto focus-bracketing.
In the CHDK/STACKS folder there will be a text file showing the Tv settings used for the bracketing sequence
However I only get a flashing orange led and then nothing. You know how those green numbers come up when you run the tlapse, they dont if I do these settings.
-
Copy-and-paste the time_lapse.bas parameters (practically the entire script !) here but change the parameter values to what you are using now.
-
Heres the code I'm using. Actaully, its sort of working now. You see what I was trying to achieve is to get the same effect one would get if you go into bracketing menu and set EV to 1/3 and then set TV to like 3 times and keep the shoot pressed.
All I wanted was to achieve the same as above with a script, after putting my cam on a tripod, cause as we all know, my IS is shot..lol
Anyway with below parameters I seem to achieve the same sort of bracketing.
@title Time-lapse
@param a first delay minutes
@default a 0
@param b first delay seconds
@default b 0
@param c shoot interval minutes
@default c 0
@param d shoot interval seconds
@default d 0
@param e number of repeats
@default e 0
@param f endless mode N/Y 0/1
@default f 1
@param g single/cont/time/burst
@default g 1
@param h Tv exposures
@default h 20
@param i Focus exposures
@default i 0
@param j bracket Tv/foc/Both 0/2
@default j 2
@param k light/dark/alternate 0/1/2
@default k 2
@param l num of 1/3 EV steps
@default l 1
@param m equal/auto/digi 0-2
@default m 0
@param n focus-step
@default n 0
@param p digiscope focus ref
@default p 0
@param q blank screen N/Y 0/1
@default q 0
@param r shutdown N/Auto/USB 0/1/2
@default r 0
@param s save stack N/Y 0/1
@default s 0
@param t Sunrise mode
@default t 0
@param u TXT/CSV 0/1
@default u 0
print "Stop Scr when LED"
print "is GREEN or"
print "is RED."
auto_focus_all
time_lapse a, b, c, d, e, f, g, h, i, j, k, l, m, n, p, q, r, s, t, u
end
Basically what I changed are:
endless - 1
single - 1
tv exp - 30
bracket tv - 2
light/dark - 2
num of 1/3 - 2
Also Ive noticed it takes 3 shots at a single Tv value, why 3? Why not 5?
Oh and setting @param j bracket Tv/foc/Both to 0 (tv) does nothing, it does what I said in an earlier post, i.e flash an orange and then does nothing.
If you can suggest any improvement so I get closest possible brackets, both light and dark, that would be great. Otherwise the above seem to do for now.
-
Tv exposures should be set to bracketing shots per shooting 'phase', say 3.
Bracket Tv/Focus/Both should be '0' for Tv bracketing.
Number of 1/3EV I would set to at least '3' (you have it set to '1').
The time-interval between each capture 'phase' is measured from the start of each group of shots.
So, we have to allow for the time it takes for capturing and storing the shots.
Try a shoot interval of 5 seconds.
You can also write :-
line_1 " Stop Scr when LED"
line_2 "#is GREEN or"
line_3 "!is RED."
(Notice the space before 'Stop').
-
Bracket Tv/Focus/Both should be '0' for Tv bracketing.
As I said earlier, setting it to 0 only flashes orange led momentarily and nothing is done.
-
@microfunguy, the latest file "SDM...19" has a major flaw. When in PLAYBACK mode it keeps on restarting after every 30 seconds. I didnt realise this earlier, but today, sharing photos with a friend it caused a major problem, rendering the playback mode literally useless.
Therefore I reverted back to the "SDM...18", the one that wont let me turn cam on in playback. This one, though is hell to start up if I forget to turn it off in LOW LIGHT MODE, does indeed let me go into playback AFTER I've been in record mode, and it lets me browse for as long as I want.
Therefore the version "SDM_1.86_IXUS105_100d_18" is so far the most stable one.
-
What happens if you only switch to PLAYBACK mode after longer than 30 seconds ?
-
What happens if you only switch to PLAYBACK mode after longer than 30 seconds ?
In that case it works fine.
However I'm still sticking to last version for now.
Also, in both versions, after going from playback mode back into record mode, it gives E32 error after 1 min. Think I might have mentioned this, not sure. Anyway my routine is to always switch cam off if I was in playback. This only happens if I was in record mode first, then in playback, then back in record, in this order only.
-
Later today I will make a version that only disables IS error if at least 30 seconds have passed AND you are in Record mode.
-
Later today I will make a version that only disables IS error if at least 30 seconds have passed AND you are in Record mode.
great, thanks :)
-
Try this version http://www.zshare.net/download/93716367a23fdef5/ (http://www.zshare.net/download/93716367a23fdef5/)
-
Try this version http://www.zshare.net/download/93716367a23fdef5/ (http://www.zshare.net/download/93716367a23fdef5/)
Brilliant! Does the job :)
-
Right, I will deal with your time-lapse problem later today or tomorrow.
-
Right, I will deal with your time-lapse problem later today or tomorrow.
Thats ok, its a shame I havent been able to figure out how to do such a ...seemingly simple thing.
Heres what I'm trying to do:
What I want to do is, put the camera on my window ledge, turn the lights off in my room, late at night, and I want to take HDR sequence photos starting from shutter speed 1" and ending at shutter speed 65". I want the closest possible difference between them, i.e EV 1/3 minimum.
Thats all really. Ive done this sorta thing before but I had my finger on the button all the time, I want to leave it alone with no custom timer light flashing.
-
I want to take HDR sequence photos starting from shutter speed 1" and ending at shutter speed 65". I want the closest possible difference between them, i.e EV 1/3 minimum.
Thats all really.
That is 20 (or is it 21 ?) exposures at 1/3EV interval and the camera in continuous shooting mode !
You realise that from just over one second, the camera also captures a black frame of equal duration ?
Total time for one sequence is double the sum of whatever the twenty times are.
The sum of 1,2,4,8,16,32 and 64 is 127.
Let us say with 1/3EV bracketing the sum is roughly 380.
Double that is 760 .. over 12 minutes.
Before we go any further, is this really what you are trying to do ?
-
@microfunguy,
Here is what I am trying to do:
I'm trying to take photos, lighter each time, starting from shutter speed 1 and ending at shutter speed 65. I intend to do this in the midnight, to capture the scene outside my window. My ultimate aim is to make an HDR with these captures.
Here is how I accomplish this currently, manually:
1. I go into SDM Menu by pressing DISP+MENU
2. I enter 'Bracket / Override' menu
3. I set Bracketing ty to [lighter]
4. I set Tv bracket val to [1/3 EV]
5. I take an elastic band with knot at one point of the loop
6. I put the band, making sure the knot is on top of the shoot button
7. I set the camera to continuous mode
8. I let it sit by the window till its completed.
What I would want:
I would want to accomplish what I have in the 'manual method' above, automatically. I'd like to do the same thing as above, minus the elastic band. Thats all.
-
Set bracketing type to 19.
Set shutter speed to 8 seconds.
Use this script :-
@title sh1981
start_continuous_sequence
wait_until_done
end_continuous_sequence
end
-
Set bracketing type to 19.
Set shutter speed to 8 seconds.
Use this script :-
@title sh1981
start_continuous_sequence
wait_until_done
end_continuous_sequence
end
Ok, will try soon.
A quick question,
I took a photo at shutter speed 1/1500
I took another one at shutter speed 1/40000
Surely there should be a hell of a big difference right? Surprisingly there was little to no difference.
Does SDM really hike the speed up to 1/40000 or is it not applicable to ixus 105?
-
Does SDM really hike the speed up to 1/40000 ?
Of course not, neither does CHDK, it is nonsense.
I only leave those settings in the menu because some people would complain if I did not.
-
Does SDM really hike the speed up to 1/40000 ?
Of course not, neither does CHDK, it is nonsense.
I only leave those settings in the menu because some people would complain if I did not.
Well after reading this http://chdk.wikia.com/wiki/Samples:_High-Speed_Shutter_%26_Flash-Sync (http://chdk.wikia.com/wiki/Samples:_High-Speed_Shutter_%26_Flash-Sync)
I got a little worried, and impressed.
You seem to be certainly right, as the speed goes max upto 1/1512. Thanks for clearing that up.
-
@microfunguy,
1. The script for continuous shoot, works perfectly, just as I wanted! Thank you.
2. After doing some further tests with high shutter speed, it appears that if I take a photo in the dark, with flash at shutter speed 1/1600, it comes out a bit, and I repeat, just a bit, lighter than if I take the same at Tv 1/40000. Therefore although the speed might go upto 1/40000, it does indeed seem to go higher than 1/1500.
-
Does what I wanted though.
-
Car caught fire today, good thing I managed to save my camera ;)
-
That is unfortunate.
maybe next time you could ..... do a bracketed HDR shot !
-
That is unfortunate.
maybe next time you could ..... do a bracketed HDR shot !
lol...absolutely, that background is way overexposed ;)
-
Hi everyone,
I recently bought an SD1300 and wanted to gain manual control over it, so I downloaded and installed SDM on my camera. It works fine and I'm able to access all the menus, however, I cannot find how to just control the shutter without affecting everything else on the camera, which is mainly why I downloaded SDM. Can someone clarify how for me, I'm really new to this software and still reading up on how to utilize all the features.
-Thanks
-
(never mind)
-
Hi everyone,
I recently bought an SD1300 and wanted to gain manual control over it, so I downloaded and installed SDM on my camera. It works fine and I'm able to access all the menus, however, I cannot find how to just control the shutter without affecting everything else on the camera, which is mainly why I downloaded SDM. Can someone clarify how for me, I'm really new to this software and still reading up on how to utilize all the features.
-Thanks
SDM menu --> Bracket/Override --> first option Override shutter selected, in second option select the speed.
-
Hi everyone,
I recently bought an SD1300 and wanted to gain manual control over it, so I downloaded and installed SDM on my camera. It works fine and I'm able to access all the menus, however, I cannot find how to just control the shutter without affecting everything else on the camera, which is mainly why I downloaded SDM. Can someone clarify how for me, I'm really new to this software and still reading up on how to utilize all the features.
-Thanks
SDM menu --> Bracket/Override --> first option Override shutter selected, in second option select the speed.
Alright it worked perfectly, thanks for the help. If you guys ever need me to test any builds let me know.
-
According to the guide on the SDM site, there's no way to manually control the aperture since there's no aperture diaphragm on this camera, correct?
-
According to the guide on the SDM site, there's no way to manually control the aperture since there's no aperture diaphragm on this camera, correct?
Yes
-
So is there any way to compensate for it if you are using a fast shutter, such as 1/1000?
-
So is there any way to compensate for it if you are using a fast shutter, such as 1/1000?
There is an ND filter. edit... well actually that would go in the opposite direction ;)
-
So is there any way to compensate for it if you are using a fast shutter, such as 1/1000?
Seems like you should be able to crank the ISO setting up to increase sensitivity ?
-
So is there any way to compensate for it if you are using a fast shutter, such as 1/1000?
Yes.
Select Force ND filter out and use Constant Exposure mode.
You cannot select a particular shutter speed but the shutter speed used can be faster (outdoors) than the Canon one if the light is bright enough.
-
So is there any way to compensate for it if you are using a fast shutter, such as 1/1000?
Yes.
Select Force ND filter out and use Constant Exposure mode.
You cannot select a particular shutter speed but the shutter speed used can be faster (outdoors) than the Canon one if the light is bright enough.
You mean by Constant Exposure Mode, the Long Shutter Mode?
-
You mean by Constant Exposure Mode, the Long Shutter Mode?
No, the option in Bracketing\Overrides menu.
-
You mean by Constant Exposure Mode, the Long Shutter Mode?
No, the option in Bracketing\Overrides menu.
Okay, it helped a little. Really wish there was a way to set the aperture though
-
So is there any way to compensate for it if you are using a fast shutter, such as 1/1000?
Seems like you should be able to crank the ISO setting up to increase sensitivity ?
On an IXUS 105 if you crank the ISO up to 1600, the delay between shots increases, a lot.
Even if you set it to 2 MP mode and 1600 ISO, it still takes a long time.
My guess is he is trying to do what I was trying to do a while back, i.e take photos outdoors, quickly, without blur, hence the 1/1000 speed.
What I did was set it to ISO 80 (since it shot faster that way), 12 MP (since it doesnt make a difference on speed), and set exposure compensation on, ND filter OUT.
Indoors, I switch to LOW LIGHT mode which, I dont know why, but shoots dramatically faster, but on 2MP and ISO 1600 to 3200, Tv 1/60, ND filter OFF.
-
You mean by Constant Exposure Mode, the Long Shutter Mode?
No, the option in Bracketing\Overrides menu.
Okay, it helped a little. Really wish there was a way to set the aperture though
Do you mean you wish there was a way to set the aperture in the sense as in make open it to the full, or to reduce it?
Its impossible for any aperture, or anything for that matter, to open up more than it physically can. By default it is open to max no matter what you do on IXUS 105.
So I'm guessing you want to reduce the aperture. You can simulate the effect with ND filter.
Do a little experiment. Set your camera Tv (shutter speed) to 1/6, and then, if you have a ceiling fan (kind of like what I posted a photo of a few posts back), turn the fan on full, and take a photo. It will have motion blur right?
Now, turn the flash on, let the Tv remain at 1/6, set the ISO to lowest i.e 80 which is bound to create even more motion blur, and take a photo. You would be surprised that the photo will be crisp.
In above example, without a flash you would need a real big aperture to be able to crank Tv upto 1/1000 in low light conditions to be able to freeze a fan, however if you dont have a big aperture, you can get relatively good results with a flash.
The point I was trying to make was, not having an aperture is not really a disadvantage, it can be fairly controlled using other methods. Even DOF, which is mostly thought to be an issue with this camera can be simulated using focus stacking (http://en.wikipedia.org/wiki/Focus_stacking (http://en.wikipedia.org/wiki/Focus_stacking))
-
Hi everyone!
I'm an absolute beginner with CHDK. I've bought my Sd1300 for about a year and has always wanted to increase its flexibilities. Can anyone tell me what has been working and what has not? How do I install it and if there's any risk of doing so? Thank you!
-
http://chdk.wikia.com/wiki/SD1300IS
(You can find some test versions on the porting thread below)
Where can I find and download a test version of CHDK for Canon IXUS 105 (Firmware Ver GM1.00D (1.0.0.0))?
Only SDM as a variant (i.e. is not present simply CHDK without SDM)?
P.S. The SDM contains not all functions which I know in CHDK. Though probably the IXUS 105 have a little functionality.
-
I have read through quite a bit of this thread, but I'm scratching my head a little..
I just got a SC1300 IS for Christmas and I am wanting the ability to shoot in RAW since I will be using this camera primarily for underwater photography. I don't want to fork up 6k for a 5dmkII and an ikelike case at the moment and I don't want to invest in a case for my 40d. This will have to hold me over..
I have already loaded the camera with SDM 1.85 and it seems to work fine in shooting in RAW, but I am having some difficulty opening the CRW file. I have the latest camera RAW installed for Photoshop CS4. I am able to open CR2 files from my 40d just fine. Is there a trick to this?
Thanks,
Jake
-
I have already loaded the camera with SDM 1.85 and it seems to work fine in shooting in RAW, but I am having some difficulty opening the CRW file. I have the latest camera RAW installed for Photoshop CS4. I am able to open CR2 files from my 40d just fine. Is there a trick to this?
This post might help : http://chdk.setepontos.com/index.php?topic=5691.msg78315#msg78315 (http://chdk.setepontos.com/index.php?topic=5691.msg78315#msg78315)
-
Doesn't these builds use SDM RAW routines? In that case, it would look more like this: http://stereo.jpn.org/eng/sdm/dng.htm (http://stereo.jpn.org/eng/sdm/dng.htm)
Or at least, I could not figure out any of the solutions listed on the CHDK wiki, so my raw files workflow involves swap_bytes, header concatenation, and importing the EXIF data from the corresponding JPG using exiftool.
-
I have already loaded the camera with SDM 1.85 and it seems to work fine in shooting in RAW, but I am having some difficulty opening the CRW file. I have the latest camera RAW installed for Photoshop CS4. I am able to open CR2 files from my 40d just fine. Is there a trick to this?
This post might help : http://chdk.setepontos.com/index.php?topic=5691.msg78315#msg78315 (http://chdk.setepontos.com/index.php?topic=5691.msg78315#msg78315)
Thanks for your reply. I will have to do some more research on this topic it looks like. Has anyone been able to open a RAW image from this camera?
-
Doesn't these builds use SDM RAW routines? In that case, it would look more like this: http://stereo.jpn.org/eng/sdm/dng.htm (http://stereo.jpn.org/eng/sdm/dng.htm)
Or at least, I could not figure out any of the solutions listed on the CHDK wiki, so my raw files workflow involves swap_bytes, header concatenation, and importing the EXIF data from the corresponding JPG using exiftool.
SDM was forked from CHDK many years ago. I am not familiar with the workflows in SDM but would not be surprised to find they are similiar but different. Perhaps microfunguy (the SDM maintainer) can comment ?
-
Thanks for your reply. I will have to do some more research on this topic it looks like. Has anyone been able to open a RAW image from this camera?
As this camera was never really ported to CHDK (although I seem to recall working with microfunguy to get basic CHDK functionality working so that he could do the SDM port about a year ago), you might be better off asking that question in the < SDM forum on Yahoo Groups (http://tech.groups.yahoo.com/group/StereoDataMaker/) >.
-
so I take it the answer is no.. at least for everyone in here...
-
ok.. so I was able to get DNG files from the CRW files using SDMdng ver 1.01 but the photos all come out with a magenta color..
-
ok.. so I was able to get DNG files from the CRW files using SDMdng ver 1.01 but the photos all come out with a magenta color..
Not sure that its your problem but if this was CHDK code then that happens when the cam_CFAPattern in platform_camera.h is wrong. As I understand it, there are only two choices :
#define cam_CFAPattern 0x01000201 // 0x01000201 = Green Blue Red Green
#define cam_CFAPattern 0x02010100 // 0x02010100 = Red Green Green Blue
Code needs to be recompiled to use the other pattern.
-
ok.. and how do I do that? :D
-
ok.. and how do I do that? :D
Ummm ... sorry - that was a CHDK answer. Maybe microfunguy can rebuild the SDM version for you (assuming that's the problem). From what I can tell, DNG is not a priority for the SDM world though ...
-
ok.. thanks.. I guess no one shoots RAW with this camera that uses SDM.
-
ok.. thanks.. I guess no one shoots RAW with this camera that uses SDM.
Do you have any s/w skills ? We could walk you through doing a CHDK port....
-
I can certainly try.. I have pretty extensive computer experience.. mostly hardware though.
And I can definitely follow directions. :)
-
I can certainly try.. I have pretty extensive computer experience.. mostly hardware though.
And I can definitely follow directions. :)
Well, you need to start here : http://chdk.wikia.com/wiki/For_Developers (http://chdk.wikia.com/wiki/For_Developers)
People here on the forum will stick with you if you have the time and patience.
-
Thanks..
Do you have this camera? What do you use?
-
Thanks..
Do you have this camera? What do you use?
Look at my sig line below. But I've "helped" with a few other ports .... including the SD1300 version David used.
-
In fact, in the last five hours such a balloon took-off from Las Vegas, avoided Area 51 restricted airspace
Hmmm ... not quite ... this has caused some problems.
Waiting for return of payload.
Hope 'they' enjoy examining my script !
Well, they enjoyed it so much the personel at Nellis Air Force base deleted all movies and high-altitude images leaving just two hundred of Las vegas.
Too bad I don't have any 'very little friends in very high places' !
The satellites of foreign governments will have acquired far higher resolution images, what is their problem, or is it just procedure ?
So, keep well away from Area 51 if you are thinking of launching a balloon in that area.
-
The satellites of foreign governments will have acquired far higher resolution images, what is their problem, or is it just procedure ?
Reconnaissance satellites fly in fixed, well defined orbits and it is relatively easy to determine when they will be overhead observing. Obviously, things that the satellites are not supposed to see are done when they are not overhead. A balloon hovering at altitude can have a very long "time over target" and a random arrival time. So you can see why it might be policy to delete pictures taken by such a balloon as a matter of standard practice.
-
ok.. so I was able to get DNG files from the CRW files using SDMdng ver 1.01 but the photos all come out with a magenta color..
1. Download http://stereo.jpn.org/eng/sdm/file/common_files.zip (http://stereo.jpn.org/eng/sdm/file/common_files.zip)
2. Put RAW file in new directory "...\CANON\CRW".
3. Run file "process.bat". It convert RAW to DNG.
4. Install "RawTherapee_WinXP_32_4.0.4.2". If your PC not have RAM 2GB then run setup with this command: msiexec /a RawTherapeeV40x86Setup.msi TARGETDIR=c:\RawTherapeeV40x86
5. Open DNG file in RawTherapee.
6. Go to tab "Color" (Alt+C) and adjust "Color Channels" Red Green Blue.
-
doesn't Photoshop have the ability to adjust color channels?
-
I have tried to fix jakedoza's magenta image problem by using existing colour matrix values from other cameras with the same-size sensor.
Namely, the A650,G9 and IXUS960 and the colour filter array order is Red Green Green Blue.
It makes no difference.
Highly unlikely the raw start address could be in error by exactly one line.
Did someone recently mention an Adobe utility that allowed you to determine the matrix values ?
David
-
doesn't Photoshop have the ability to adjust color channels?
My Photoshop doesn't support DNG files from this camera.
You can try "Adobe DNG Profile Editor".
-
You can try "Adobe DNG Profile Editor".
Thanks, I will play with that.
-
1. SDM 1.85 doesn't make a "dark-frame subtraction".
2. RAW is not saved when timer is used.
3. SDM not support Lua scripts.
4. IXUS 105 have 12MP, but RAW 10MP.
5. PhotoME program says that DNG has 12 bits per component.
6. If use "eLynx lab MSW" for demosaicing with method "Bin2X2" then output image resolution is 1842 x 1386 Pixels (2.55 MPixels).
7. DNG has a distortion.
8. The left and top areas of DNG, not exists in JPEG image.
9. The right and bottom areas of JPEG, not exists in DNG image. Why they are not in RAW?
Download "IXUS 105 RAW.zip" (RAW, JPEG, DNG) - 18.36MB from
mirrorcreator (http://mir.cr/JM1BGRA4)
rapidshare (https://www.rapidshare.com/files/2560611082/IXUS_105_RAW.zip)
depositfiles (http://depositfiles.com/files/m4r8ui8gk)
megashares (http://d01.megashares.com/dl/9lOEhJ2/IXUS_105_RAW.zip)
zshare (http://www.zshare.net/download/99227976f33ecd2f/)
filefactory (http://www.filefactory.com/file/c35adc1/n/IXUS_105_RAW.zip)
mediafire (http://www.mediafire.com/?1gkhqgxp0xppg7d)
freakshare (http://freakshare.com/files/e7p05tij/IXUS_105_RAW.zip.html)
What do you think about IXUS 105 RAW image problems?
-
Who know how-to normalize colour in RAW image (make it as in jpeg image)?
-
Who know how to normalize colour in RAW image (make it as in jpeg image)?
This is curious. AFAIK, this happens when the value of cam_CFAPattern in platform_camera.h is not set correctly. I have been told that there are only two valid choices, listed below.
#define cam_CFAPattern 0x01000201 // Green Blue Red Green
#define cam_CFAPattern 0x02010100 // Red Green Green Blue Changing this value requires recompilation of the source code.
And as this is an SDM release rather than CHDK, I'm not sure how much else we can do to help you here.
-
And as this is an SDM release rather than CHDK, I'm not sure how much else we can do to help you here.
As my earlier post says, I did try both colour-filter-array types.
Don't know if incorrect colour matrix values can give such an extreme magenta cast.
-
As my earlier post says, I did try both colour-filter-array types.
Don't know if incorrect colour matrix values can give such an extreme magenta cast.
I don't think there's any magic involved here. The sensor is the same as in the D10, A1100, etc. If the raw buffer address, its size, the raw dimensions and the raw bit-depth is correct, the raw should look fine. One more possible problem could be a wrong location for the raw hook. But since more than one working port from the same age exists, it shouldn't be hard to correct these, when needed.
for 1.00d:
char *hook_raw_image_addr()
{
return (char*) 0x41d64ecc; // "CRAW BUFF"
}
long hook_raw_size()
{
return 0x11E4EE0; // "CRAW BUFF SIZE"
}
#define cam_CFAPattern 0x01000201 // Green Blue Red Green
You could make this guess-work stop by publishing the platform/loader folder contents for this port... ::)
-
You could make this guess-work stop by publishing the platform/loader folder contents for this port... ::)
It was published one year ago :- http://stereo.jpn.org/eng/sdm/file/sdm.zip (http://stereo.jpn.org/eng/sdm/file/sdm.zip)
As I say, I have tried both CFA patterns since then.
-
As I say, I have tried both CFA patterns since then.
Use the correct mosaic type when you convert the raw, then the image is ok ;)
(DNG4PS-2 settings & DNG preview attached)
-
As I say, I have tried both CFA patterns since then.
Use the correct mosaic type when you convert the raw, then the image is ok ;)
This camera has a 12M sensor ;)
If the camera.h settings still use values of a 10M sensor then they need to be changed.
#define CAM_RAW_ROWPIX 4104 // 12 MP 12bpp
#define CAM_RAW_ROWS 3048
#define CAM_JPEG_WIDTH 4000
#define CAM_JPEG_HEIGHT 3000
#define CAM_ACTIVE_AREA_X1 0
#define CAM_ACTIVE_AREA_Y1 0
#define CAM_ACTIVE_AREA_X2 4104
#define CAM_ACTIVE_AREA_Y2 3048
The "active area" settings need to be adjusted. If I use the example provided by bazhuryan, I see different kinds of borders around the picture. If I chop all of them, the resulting dng dimensions will be smaller than the jpeg's. One could experiment with dng4ps2 to find the optimal values.
-
This camera has a 12M sensor ;)
I know, the CHDK porter had the wrong values.
I used some of these for recent tests :-
#define CAM_RAW_ROWPIX 4104
#define CAM_RAW_ROWS 3048
// #define cam_CFAPattern 0x01000201 // Green Blue Red Green
#define cam_CFAPattern 0x02010100 // Red Green Green Blue
/*
#define CAM_COLORMATRIX1 \
12724, 10000, -5061, 10000, -1934, 10000, \
-370, 10000, 7752, 10000, 2619, 10000, \
839, 10000, -233, 10000, 5750, 10000
*/
/*
// IXUS960,A650
#define CAM_COLORMATRIX1 \
913762, 1000000, -261578, 1000000, -135582, 1000000, \
-99049, 1000000, 1067089, 1000000, 61442, 1000000, \
48717, 1000000, 96802, 1000000, 412056, 1000000
*/
//G9
#define CAM_COLORMATRIX1 \
1679727, 1000000, 422803, 1000000, 803343, 1000000, \
220204, 1000000, 1784845, 1000000, -63290, 1000000, \
-282882, 1000000, -475034, 1000000, 4502592, 1000000
#define cam_CalibrationIlluminant1 1 // Daylight
// cropping
#define CAM_JPEG_WIDTH 4000
#define CAM_JPEG_HEIGHT 3000
#define CAM_ACTIVE_AREA_X1 48
#define CAM_ACTIVE_AREA_Y1 12
#define CAM_ACTIVE_AREA_X2 4080
#define CAM_ACTIVE_AREA_Y2 3036
-
I've experimented with the CAM_COLORMATRIX1 you appear to use, and got a "nice" result (both the CFA pattern and color matrix is wrong in this case).
Before that, I used a random camera's data to create a DNG4PS2 profile for the Ixus105, and the result was acceptable. So, what I could recommend is (since AGAIN, this sensor is used in multiple cameras)
from the D10:
#define CAM_COLORMATRIX1 \
14052, 10000, -5229, 10000, -1156, 10000, \
-1325, 10000, 9420, 10000, 2252, 10000, \
-498, 10000, 1957, 10000, 4116, 10000or from A1100:
#define CAM_COLORMATRIX1 \
793137, 1000000, -271722, 1000000, -113158, 1000000, \
-55013, 1000000, 541027, 1000000, 32394, 1000000, \
21921, 1000000, 71395, 1000000, 181847, 1000000
The second example was done with the D10 matrix (1.4052, -0.5229, -0.1156, -0.1325, 0.9420, 0.2252, -0.0498, 0.1957, 0.4116) and pattern, used IrfanView for a quick result.
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg52.imageshack.us%2Fimg52%2F3755%2Fraww.th.png&hash=c6954c83aa8bcb728baf57a796c964e7) (http://img52.imageshack.us/img52/3755/raww.png) (https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg856.imageshack.us%2Fimg856%2F9303%2Frawww.th.png&hash=ff281642f1e0a385518bf878ea1b4784) (http://img856.imageshack.us/img856/9303/rawww.png)
Now, some quotes...
You could make this guess-work stop by publishing the platform/loader folder contents for this port... ::)
It was published one year ago :- http://stereo.jpn.org/eng/sdm/file/sdm.zip (http://stereo.jpn.org/eng/sdm/file/sdm.zip)
As I say, I have tried both CFA patterns since then.
#define CAM_RAW_ROWPIX 4104
#define CAM_RAW_ROWS 3048
// pattern
#define cam_CFAPattern 0x02010100 // Red Green Green Blue
// color
#define CAM_COLORMATRIX1 \
827547, 1000000, -290458, 1000000, -126086, 1000000, \
-12829, 1000000, 530507, 1000000, 50537, 1000000, \
5181, 1000000, 48183, 1000000, 245014, 1000000
#define cam_CalibrationIlluminant1 1 // Daylight
// cropping
#define CAM_JPEG_WIDTH 3648
#define CAM_JPEG_HEIGHT 2736
#define CAM_ACTIVE_AREA_X1 6
#define CAM_ACTIVE_AREA_Y1 12
#define CAM_ACTIVE_AREA_X2 3690
#define CAM_ACTIVE_AREA_Y2 2772
I know, the CHDK porter had the wrong values.
I used some of these for recent tests :-
#define CAM_RAW_ROWPIX 4104
#define CAM_RAW_ROWS 3048
// #define cam_CFAPattern 0x01000201 // Green Blue Red Green
#define cam_CFAPattern 0x02010100 // Red Green Green Blue
/*
#define CAM_COLORMATRIX1 \
12724, 10000, -5061, 10000, -1934, 10000, \
-370, 10000, 7752, 10000, 2619, 10000, \
839, 10000, -233, 10000, 5750, 10000
*/
/*
// IXUS960,A650
#define CAM_COLORMATRIX1 \
913762, 1000000, -261578, 1000000, -135582, 1000000, \
-99049, 1000000, 1067089, 1000000, 61442, 1000000, \
48717, 1000000, 96802, 1000000, 412056, 1000000
*/
//G9
#define CAM_COLORMATRIX1 \
1679727, 1000000, 422803, 1000000, 803343, 1000000, \
220204, 1000000, 1784845, 1000000, -63290, 1000000, \
-282882, 1000000, -475034, 1000000, 4502592, 1000000
#define cam_CalibrationIlluminant1 1 // Daylight
// cropping
#define CAM_JPEG_WIDTH 4000
#define CAM_JPEG_HEIGHT 3000
#define CAM_ACTIVE_AREA_X1 48
#define CAM_ACTIVE_AREA_Y1 12
#define CAM_ACTIVE_AREA_X2 4080
#define CAM_ACTIVE_AREA_Y2 3036
-
New photo (RAW, number 2) for research:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg528.imageshack.us%2Fimg528%2F2603%2Fjpgfromcamerarecompress.png&hash=403c2a621c064c2ccf2c90937e0d4f14)
Download "IXUS 105 RAW Number 2.zip" (RAW, JPEG, DNG) - 16,9MB from
mirrorcreator (http://mir.cr/HA7DBE0R)
rapidshare (https://www.rapidshare.com/files/465816039/IXUS_105_RAW__Number_2.zip)
megashares (http://d01.megashares.com/dl/7MMbhJw/IXUS_105_RAW__Number_2.zip)
depositfiles (http://depositfiles.com/files/0ntgu65ez)
zshare (http://www.zshare.net/download/99248421cd9cbbf2/)
freakshare (http://freakshare.com/files/iut43v7o/IXUS_105_RAW__Number_2.zip.html)
uploadstation (http://www.uploadstation.com/file/C2u4Z62)
mediafire (http://www.mediafire.com/?8dwgxtbkgufuzps)
-
It is very late here now, I will compile a new build tomorrow.
Can you post a CRW and HDR file straight from the camera with running process.bat ?
-
Can you post a CRW and HDR file straight from the camera with running process.bat ?
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg268.imageshack.us%2Fimg268%2F926%2Frawandhdr.png&hash=837270a45492880264d558d187b1fd75)
Download "IXUS_105_RAW__Number_2_only_CRW.zip" (files: "raw.crw", "raw.hdr") - 13,5MB from
mirrorcreator (http://mir.cr/0QLWYRJO)
rapidshare (https://www.rapidshare.com/files/2557518577/IXUS_105_RAW__Number_2_only_CRW.zip)
megashares (http://d01.megashares.com/dl/43kA5YQ/IXUS_105_RAW__Number_2_only_CRW.zip)
depositfiles (http://depositfiles.com/files/zaxjs7h6d)
zshare (http://www.zshare.net/download/992495543f9c66fe/)
filefactory (http://www.filefactory.com/file/c356fb8/n/IXUS_105_RAW__Number_2_only_CRW.zip)
uploaded (http://ul.to/2anf2s4i)
freakshare (http://freakshare.com/files/skqqqula/IXUS_105_RAW__Number_2_only_CRW.zip.html)
-
here is a new build http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN (http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN)
and these are the values that I used :-
#define CAM_COLORMATRIX1 \
14052, 10000, -5229, 10000, -1156, 10000, \
-1325, 10000, 9420, 10000, 2252, 10000, \
-498, 10000, 1957, 10000, 4116, 10000
#define cam_CalibrationIlluminant1 21 // D65
#define CAM_RAW_ROWPIX 4104
#define CAM_RAW_ROWS 3048
#define CAM_JPEG_WIDTH 4000
#define CAM_JPEG_HEIGHT 3000
#define CAM_ACTIVE_AREA_X1 0
#define CAM_ACTIVE_AREA_Y1 0
#define CAM_ACTIVE_AREA_X2 4104
#define CAM_ACTIVE_AREA_Y2 3048
#undef CAM_SENSOR_BITS_PER_PIXEL
#undef CAM_WHITE_LEVEL
#undef CAM_BLACK_LEVEL
#define CAM_SENSOR_BITS_PER_PIXEL 12
#define CAM_WHITE_LEVEL ((1<<CAM_SENSOR_BITS_PER_PIXEL)-1)
#define CAM_BLACK_LEVEL 127
#define cam_CFAPattern 0x01000201 // Green Blue Red Green
-
and these are the values that I used :-
The JPEG dimensions and cropping values are incorrect (the cam is 12Mp, not 10).
-
The JPEG dimensions and cropping values are incorrect (the cam is 12Mp, not 10).
Yes, they were originally correct .. I was glancing at fe50's DNG4PS2 screenshots where the original 10MP values are shown.
The Dropbox build has been updated.
-
The Dropbox build has been updated.
New photo (RAW, number 3) made with SDM 1.86 for research:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg854.imageshack.us%2Fimg854%2F2603%2Fjpgfromcamerarecompress.png&hash=6391c8ff7ca9c429070f84b4183d2fee)
Download "IXUS 105 RAW Number 3.zip" (RAW, JPEG, DNG) - 18,7MB from
mirrorcreator (http://mir.cr/V70KCYBT)
uploaded (http://uploaded.to/file/l5yfpvax)
rapidshare (https://www.rapidshare.com/files/1307851121/IXUS_105_RAW__Number_3.zip)
megashares (http://d01.megashares.com/dl/kLW1QGF/IXUS_105_RAW__Number_3.zip)
depositfiles (http://depositfiles.com/files/8fostanc4)
zshare (http://www.zshare.net/download/99265891ba9540d3/)
freakshare (http://freakshare.com/files/2ehfimsu/IXUS_105_RAW__Number_3.zip.html)
uploadstation (http://www.uploadstation.com/file/AhvrMmZ)
-
http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN (http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN) - SDM 1.86 (MD5 = 901019fdcdb7270bce1fb740db2b8f86)
1. The "Av" setting doesn't exist in menu "Bracketing/Overrides" (SDM 1.85 has this setting). How to change aperture value in options of SDM 1.86?
2. In SDM 1.85 - CRW and HDR files are saved in "\DCIM\100CANON\CRW\", now in "\DCIM\CRW\".
3. Digits in file names of CRW and HDR files not equal to digits in JPG filename. Example: STR_1.CRW and IMG_2172.JPG.
4. Optical zoom works when recording video. But if he goes into digital zoom - it is impossible to return back to optical zoom.
-
1. The "Av" setting doesn't exist in menu "Bracketing/Overrides". How to change aperture value in options?
I would expect this camera does not have an adjustable iris, like most ixus/sd series.
-
1. The "Av" setting doesn't exist in menu "Bracketing/Overrides". How to change aperture value in options?
I would expect this camera does not have an adjustable iris, like most ixus/sd series.
"Av" setting exist in SDM 1.85 and work with value 8.0. Other values are not working (when optical zoom is 0).
-
1. The "Av" setting doesn't exist in menu "Bracketing/Overrides". How to change aperture value in options?
I would expect this camera does not have an adjustable iris, like most ixus/sd series.
"Av" setting exist in SDM 1.85 and work with value 8.0. Other values are not working (when optical zoom is 0).
Sounds like this might be changing the ND filter.
-
How to change aperture value in options of SDM 1.86?
Your camera does not have an aperture, that is why the menu option was removed.
In SDM 1.85 - CRW and HDR files are saved in "\DCIM\100CANON\CRW\", now in "\DCIM\CRW\".
It was found that on some cameras if the directory structure was too 'deep' it gave problems.
Digits in file names of CRW and HDR files not equal to digits in JPG filename.
They should be, it does not depend on camera model, I will check.
Optical zoom works when recording video. But if he goes into digital zoom - it is impossible to return back to optical zoom.
The initial CHDK port is done by a developer who has access to the camera.
I do not have access to the camera.Research the Group archives to see if this problem has occurred with any other cameras.
The raw image is not bad, a bit of a yellow cast.
The TIFF orientation tag in the header is '6' so I will assume you rotated the camera to your right (clockwise).
I will do cropping based on that.
-
This build applies cropping and uses the A1100 profile : http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN (http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN)
You will have to decide if you prefer this or the previous profile.
Any other adjustments will have to be made with the Adobe Profile Editor.
-
This build applies cropping and uses the A1100 profile : http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN (http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN)
You will have to decide if you prefer this or the previous profile.
Any other adjustments will have to be made with the Adobe Profile Editor.
Strange, colour again almost as in SDM 1.85.
New photo (RAW, number 4) for research:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg205.imageshack.us%2Fimg205%2F7269%2Fjpgfromcameraandraw.png&hash=5e7840a8d65b7f0e1cad6ccb831e1483)
-
OK, I will use the D10 profile and post in about five minutes.
Will tell you when it is available.
Here you are http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN (http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN)
-
OK, I will use the D10 profile and post in about five minutes.
Will tell you when it is available.
Here you are http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN (http://dl.dropbox.com/u/17639456/IXUS_105_100D.BIN)
IXUS_105_100D.BIN MD5 = 9e5f9a60047b9636ad3fa19929710b14
Changes in color were not found.
New photo (RAW, number 5) for research:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg708.imageshack.us%2Fimg708%2F7269%2Fjpgfromcameraandraw.png&hash=a417a788ae0127cd5a8a263442e580b3)
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg268.imageshack.us%2Fimg268%2F6821%2Frawafterdng4ps2.png&hash=d1eb614339f88774cefe4cf38058e9a1)
Download "IXUS 105 RAW Number 5.zip" (RAW, JPEG, DNG) - 20,1MB from
mirrorcreator (http://mir.cr/07OKNVRK)
depositfiles (http://depositfiles.com/files/98atcd7xm)
uploaded (http://ul.to/3iwl6dqt)
rapidshare (https://www.rapidshare.com/files/3908628532/IXUS_105_RAW__Number_5.zip)
zshare (http://www.zshare.net/download/992815346b8c64a4/)
load (http://www.load.to/4iWqy6fsLo/IXUS_105_RAW__Number_5.zip)
mediafire (http://www.mediafire.com/?j3swcq2oc9tc6v3)
freakshare (http://freakshare.com/files/6xj51htt/IXUS_105_RAW__Number_5.zip.html)
uploadstation (http://www.uploadstation.com/file/geWz53y)
-
i had better check the code, I did delete some commented-out parts.
How did you get DNG4PS2 to find the file in the folder ?
When I tried, it did not find any files ?
-
How did you get DNG4PS2 to find the file in the folder ?
When I tried, it did not find any files ?
You need a .jpg with the same name beside the raw.
-
Here are both the D10 and A1100 versions http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.zip (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.zip)
@srsa_4c Thanks, I will try that.
I assumed the jpg was only needed if you were using the EXIF info.
-
i had better check the code, I did delete some commented-out parts.
How did you get DNG4PS2 to find the file in the folder ?
When I tried, it did not find any files ?
See my settings of "dng4ps2-0.2.3-beta26.exe".
Color matrix #1
1.405200 -0.522900 -0.115600 -0.132500 0.942000 0.225200 -0.049800 0.195700 0.411600
-
Here are both the D10 and A1100 versions http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.zip (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.zip)
Research will be continued not earlier than in 18 hours.
-
Research will be continued not earlier than in 18 hours.
OK, but while it is still in my mind, your DNG4PS2 values are the same as D10 with one difference .. you are using 'standard Light A' whereas D10 is using 'D65' calibration illuminant.
-
Here are both the D10 and A1100 versions http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.zip (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.zip)
New photo (RAW, number 6, DISKBOOT.BIN.A1100 MD5 = 2eb241ef0936cf0cd16a5b736fae81c5) for research:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg442.imageshack.us%2Fimg442%2F5734%2Fa1100.png&hash=906e15cbade9460d9b43802119cd1b9b)
Download "IXUS_105_RAW__Number_6__DISKBOOT.BIN.A1100.zip" (RAW, JPEG, DNG) - 19,8MB from
mirrorcreator (http://mir.cr/NMALW3HT)
depositfiles (http://depositfiles.com/files/l4844ux2n)
uploaded (http://ul.to/ywxmr5ek)
rapidshare (https://www.rapidshare.com/files/2953478865/IXUS_105_RAW__Number_6__DISKBOOT.BIN.A1100.zip)
zshare (http://www.zshare.net/download/99305019c071c730/)
load (http://www.load.to/Lr2BOPxJCj/IXUS_105_RAW__Number_6__DISKBOOT.BIN.A1100.zip)
mediafire (http://www.mediafire.com/?qh5kpj4vqz01wbc)
freakshare (http://freakshare.com/files/x80lefiz/IXUS_105_RAW__Number_6__DISKBOOT.BIN.A1100.zip.html)
uploadstation (http://www.uploadstation.com/file/ASvrSqQ)
---------------------------------------------------
New photo (RAW, number 7, DISKBOOT.BIN.D10 MD5 = df18bcecded4b9a02fd0193224d663c0) for research:
Download "IXUS_105_RAW__Number_7__DISKBOOT.BIN.D10.zip" (RAW, JPEG, DNG) - 20,4MB from
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg850.imageshack.us%2Fimg850%2F2893%2Fd10i.png&hash=2e9586a06945fee81d2fb7b63813a7b5)
mirrorcreator (http://mir.cr/QIG41JLX)
zshare (http://www.zshare.net/download/993051266a541fae/)
depositfiles (http://depositfiles.com/files/95jec3wgq)
uploaded (http://ul.to/f1e45o7l)
rapidshare (https://www.rapidshare.com/files/2967192172/IXUS_105_RAW__Number_7__DISKBOOT.BIN.D10.zip)
mediafire (http://www.mediafire.com/?5yuyvpnvv651aa9)
load (http://www.load.to/VSGis3SxQE/IXUS_105_RAW__Number_7__DISKBOOT.BIN.D10.zip)
uploadstation (http://www.uploadstation.com/file/Rfs8Gbf)
-
4. Optical zoom works when recording video. But if he goes into digital zoom - it is impossible to return back to optical zoom.
This is a problem with several models. Philmoz found a way to fix this on a least one of his cameras but the fix was camera specific and not universal. Can't find the relevent posts right now - sorry.
-
Can't find the relevent posts right now - sorry.
Was it this ? :-
http://chdk.setepontos.com/index.php?topic=6560.msg69505;topicseen#msg69505 (http://chdk.setepontos.com/index.php?topic=6560.msg69505;topicseen#msg69505)
-
Mr.Baz,
none of this makes much sense, especially as one of the versions previously worked.
I will have my dinner and then compare the HDR files to see the differences.
-
Something has found out.
"Color Matrix #1" from HDR file (in message (http://chdk.setepontos.com/index.php?topic=5720.msg79809#msg79809)):
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg841.imageshack.us%2Fimg841%2F4550%2Fhdrcolormatrixsdm185.png&hash=4214fba88b40a06de1255aa168606577)
With this value the photo looks red:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg17.imageshack.us%2Fimg17%2F5274%2Fdngfromrawsdm185.png&hash=81c02a178b6aa8d6907cef21394f5815)
It occurs in SDM 1.85.
Interesting, Microfunguy has specified almost correct value of "Color Matrix". HDR file with normal value I have published in this message (http://chdk.setepontos.com/index.php?topic=5720.msg82288#msg82288).
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg20.imageshack.us%2Fimg20%2F2342%2Fhdrcolormatrixsdm186.png&hash=b898b893421130d551b19c63866776af)
I used mine CRW file from this message (http://chdk.setepontos.com/index.php?topic=5720.msg79809#msg79809). And HDR file from this message (http://chdk.setepontos.com/index.php?topic=5720.msg82288#msg82288).
Has connected HDR with CRW a file. Has processed them in swap_bytes.exe
Has as a result received RAW a file with colours which were as in this message (http://chdk.setepontos.com/index.php?topic=5720.msg82288#msg82288).
The ready image from different parts:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg855.imageshack.us%2Fimg855%2F9599%2Fdngfromraw.png&hash=2ceea9b425514eca7e344f38ce94e7c1)
It "Color Matrix #1" from DNG file:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg534.imageshack.us%2Fimg534%2F3592%2Fdngvalidcolormatrix.png&hash=16413569826164f26559ae6093d86c58)
Lightroom can open this DNG file.
All CRW files created in SDM 1.85 - are correct.
-
I will read your last message after this post.
Do you have a hex editor that allows you to change binary files ?
If so, change the following values in the HDR file for raw number 7 :-
0328 00 00 00 00
032C E8 0B 00 00
0330 08 10 00 00
In effect, that remove all cropping.
Now, make a new DNG file.
-
I have published in this message (http://chdk.setepontos.com/index.php?topic=5720.msg82288#msg82288).
I do not think the matrix values have made the difference.
In that HDR there is no cropping, I think that is what makes the difference.
-
If so, change the following values in the HDR file for raw number 7 :-
0328 00 00 00 00
032C E8 0B 00 00
0330 08 10 00 00
It is difficult to find a position in a file.
You can underline it in a PNG file (HDR file from this message (http://chdk.setepontos.com/index.php?topic=5720.msg82288#msg82288)).
-
That is not the HDR file.
-
Do not bother, wait a few minutes, I will post a new build.
-
That is not the HDR file.
Has replaced PNG file.
-
OK, try this : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
-
OK, try this : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
DISKBOOT.BIN.IXUS105.100D MD5 = b29fbd2b811b4d58be22700b7f4bf313.
New photo (RAW, №8) for research:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg837.imageshack.us%2Fimg837%2F7269%2Fjpgfromcameraandraw.png&hash=1d29f69dd9695f238a1973e87867e336)
Download "IXUS_105_RAW__Number_8_DISKBOOT.BIN.IXUS105.100D.zip" (RAW, JPEG, DNG) - 18,1MB from
mirrorcreator (http://mir.cr/S0EVGFX1)
-
New photo (RAW, №8) for research:
Nothing more that I can do.
The problem was caused by cropping on an odd-numbered line, they have to be even-numbered to suit the colour-filter array.
Let us try the A1100 colour profile anyway, I will post in a few minutes.
-
Here you are, the A1100 colour profile : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
-
Here you are, the A1100 colour profile : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
DISKBOOT.BIN.IXUS105.100D MD5 = 69841249f678bcb49332247e4988cb5c.
New photo (RAW, №9) for research:
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimg15.imageshack.us%2Fimg15%2F7269%2Fjpgfromcameraandraw.png&hash=4b8c30315ed40f92e4ecaab3717807be)
Download "IXUS_105_RAW__Number_9_A1100.DISKBOOT.BIN.IXUS105.100D.zip" (RAW, JPEG, DNG) - 18,1MB from
mirrorcreator (http://mir.cr/04GVC3XJ)
-
Nothing more that I can do.
I cannot just guess colour matrix values.
If you have access to a 24-colour chart you could use DNG4PS2 to create a matrix.
You can also try photographing the colour chart on a monitor.
It is not easy to do.
The programme often just tells you the errors are too big to proceeed.
Let us see if philmoz can give more information about the digital zoom problem.
-
Can't find the relevent posts right now - sorry.
Was it this ? :-
http://chdk.setepontos.com/index.php?topic=6560.msg69505;topicseen#msg69505 (http://chdk.setepontos.com/index.php?topic=6560.msg69505;topicseen#msg69505)
Might have been related - IIRC it was around the same time period. However, there were explicit postings about zoom in video getting stuck in digital mode and not being able to revert to the mechanical range. Something like this :
http://chdk.setepontos.com/index.php?topic=4335.msg69000#msg69000 (http://chdk.setepontos.com/index.php?topic=4335.msg69000#msg69000)
-
New photo (RAW, №9) for research:
If the letters on the carton are white, then the JPG image is slightly blue-green, it needs more red.
You need to include something that is white or neutral grey in the image.
-
Guess it starts at line 145 here http://trac.assembla.com/chdk/browser/trunk/platform/generic/wrappers.c (http://trac.assembla.com/chdk/browser/trunk/platform/generic/wrappers.c)
Getting a bit complicated to set the zoom.
-
Guess it starts at line 145 here http://trac.assembla.com/chdk/browser/trunk/platform/generic/wrappers.c (http://trac.assembla.com/chdk/browser/trunk/platform/generic/wrappers.c)
Getting a bit complicated to set the zoom.
Actually, I believe that refers to something quite different.
That zoom problem related to setting a zoom position manually from a script and crashing the camera when you tried. It was an interaction of some sort with autofocus. I tracked it here for a while :
http://chdk.setepontos.com/index.php?topic=7071.0 (http://chdk.setepontos.com/index.php?topic=7071.0)
Philmoz solved it for some cameras (his & my G10) but it is still an outstanding issue for the SD780, SD940 and SD980 and possibly others.
The zoom problem in this thread is different - it does not cause a crash. All that happens is that when CHDK enables mechanical zoom in video mode (a feature not available in the default Canon firmware - likely because the zoom noise gets into the audio track) it will zoom in until digital zoom takes over. Once you are in digital zoom range you can't get back to mechanical zoom range unless you stop recording.
-
New photo (RAW, №9) for research:
If the letters on the carton are white, then the JPG image is slightly blue-green, it needs more red.
Yes, in reality they are white.
-
Yes, in reality they are white.
In Adobe DNg Profile Editor, if you right-click on the 'white' letters it should correct them.
You can then save the profile.
-
It is not known why but SDM 1.86 rewrites existing HDR and CRW files.
All new CRW and HDR files are named - STR_0001.HDR and STR_0001.CRW.
There are no files STR_0002.HDR STR_0002.CRW and so on.
SDM 1.85 has no such problem.
-
All that happens is that when CHDK enables mechanical zoom in video mode (a feature not available in the default Canon firmware - likely because the zoom noise gets into the audio track) it will zoom in until digital zoom takes over. Once you are in digital zoom range you can't get back to mechanical zoom range unless you stop recording.
See core/gui.c, other_kbd_process() function, lines 2415-2419 (current release-1.0 version of the file).
Phil.
-
See core/gui.c, other_kbd_process() function, lines 2415-2419 (current release-1.0 version of the file).
@philmoz - thanks.
#if defined (CAMERA_s90) || defined (CAMERA_s95) || defined (CAMERA_g12) || defined (CAMERA_a3000)
if (x==0) zoom_status=ZOOM_OPTICAL_MAX; //ERR99: No zoom back from digital to optical zoom possible if set to medium
#else
if (x==0) zoom_status=ZOOM_OPTICAL_MEDIUM;
#endif
Do we decide which branch to take by testing what works for each camera on a trial&error basis ?
-
See if this fixes the zoom problem : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
-
See if this fixes the zoom problem : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
DISKBOOT.BIN.IXUS105.100D MD5 = 3c180fdbe4b1ac7bcd5569745a0fde20
The problem with optical zoom is not solved.
The problem comes when the zoom is increased to 4x (max optical value).
But if the recording started when the zoom was equal to 4x, then it can be reduced to min value without any problems.
-
I will test my S95 with and without the zoom fix.
-
Well, the fix works on my S95.
When you had reduced digital zoom to minimum amount, did you release the zoom lever and then operate it again to enter optical zoom ?
-
When you had reduced digital zoom to minimum amount, did you release the zoom lever and then operate it again to enter optical zoom ?
Not working. The zoom value is not reduced (=4x). Enter to optical zoom from digital - fail.
-
Let me try one more thing .....
-
Let me try one more thing .....
What is this thing?
-
Try this version : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
-
Try this version : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
Tested. Changes in the work were not found.
-
There is nothing more that I can do .
i have tried both 'fixes' for this problem.
-
3. Digits in file names of CRW and HDR files not equal to digits in JPG filename. Example: STR_1.CRW and IMG_2172.JPG.
On the IXUS105, how are image folders named, are they like 123CANON or are they based on calendar date ?
-
3. Digits in file names of CRW and HDR files not equal to digits in JPG filename. Example: STR_1.CRW and IMG_2172.JPG.
On the IXUS105, how are image folders named, are they like 123CANON or are they based on calendar date ?
Based on calendar date.
In options two variants "Create Folder":
1. Daily.
2. Monthly.
Sample "Monthly" folder names:
"109___12" Date: 1/12/11
"110___01" Date: 1/01/12
"111___02" Date: 1/02/12
"112___03" Date: 1/03/12
-
See if this fixes the file-numbering problem : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
@philmoz
Phil, are there any CHDK-ported cameras for which the zooming in video mode problem could not be fixed ?
If not, I cannot believe the IXUS105 is the only one.
Guess I could check firmware addresses of the zoom_busy, zoom_status and movie_status values.
-
See if this fixes the file-numbering problem : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
@philmoz
Phil, are there any CHDK-ported cameras for which the zooming in video mode problem could not be fixed ?
If not, I cannot believe the IXUS105 is the only one.
Guess I could check firmware addresses of the zoom_busy, zoom_status and movie_status values.
Hard to say if any other cameras are affected - problem reports are somewhat hit and miss.
Definitely check those values, the current CHDK signature finder should locate the correct addresses.
Phil.
-
See if this fixes the file-numbering problem : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
DISKBOOT.BIN.IXUS105.100D MD5 = 7c794474593c02dd4c2c424a3ecbe0d3
Now it works like this:
If the folder "\CRW\" is empty then the CRW and HDR file will be named - "STR_0001.*".
But the JPEG file will be have a different digits in filename (Sample: IMG_2171.JPG, STR_0001.CRW, STR_0001.HDR).
Next created CRW file will have the same digits as JPEG (Sample: IMG_2172.JPG, STR_2172.CRW, STR_2172.HDR).
But if delete the last created JPEG file then the new CRW will have the numbers "0001". At the same time the existing CRW file with this name will be overwritten (Sample: IMG_2174.JPG, STR_0001.CRW, STR_0001.HDR).
-
If the folder "\CRW\" is empty then the CRW and HDR file will be named - "STR_0001.*".
But the JPEG file will be have a different digits in filename (Sample: IMG_2171.JPG, STR_0001.CRW, STR_0001.HDR).
I don't think it is because the \CRW\ folder is empty.
That normally happens if they are no JPG's in your current Canon folder.
If you have at least one JPG in the folder the numbering should work fine.
The problem is caused by the Canon function that returns next image number not working properly on the first image after booting.
I do not know if CHDK has had the same problem.
I have not had time to look at every CHDK port or patch but I vaguely remember seeing in at least one build, mention of adding a delay in order to give the Canon firmware time to return the correct file number.
Can anyone remember which build that is mentioned in ?
-
If the folder "\CRW\" is empty then the CRW and HDR file will be named - "STR_0001.*".
But the JPEG file will be have a different digits in filename (Sample: IMG_2171.JPG, STR_0001.CRW, STR_0001.HDR).
That normally happens if they are no JPG's in your current Canon folder.
If you have at least one JPG in the folder the numbering should work fine.
Was at least 5 JPG files, and not one CRW, before shooting.
Badly that the new file rewrites the old with same name.
In SDM 1.85 I have not found this problem.
-
Was at least 5 JPG files, and not one CRW, before shooting.
After turning on the camera take one picture.
All photos after that should have the correct numbers.
Does that work ?
In SDM 1.85 I have not found this problem.
SDM 1.86 uses different code to support certain PTP functions.
However, I will look at the code and see if it can be fixed for the first RAW.
-
Try this version, works on my S95 and A620 : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
-
Try this version, works on my S95 and A620 : http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D (http://dl.dropbox.com/u/17639456/DISKBOOT.BIN.IXUS105.100D)
Checked. Error with incorrect names - resolved.
-
I found another bug. This problem was not in the SDM 1.85.
Description:
In the setting of the camera size of photo is set smaller than 12 megapixels. For example: 5MP.
But after a reboot, the camera takes pictures with a maximum resolution - 12 megapixels.
In the setting value is the same as before the reboot (example: 5MP).
The problem is "solved" by switching resolution on a different value and return it back.
Or switch to "show pictures" mode and return from it.
Possibly it SDM makes changes when it does the initialization, when the camera starts after turning on.
-
SDM 1.86 uses different code to support certain PTP functions.
Is it possible to get full access to the memory card file system via a camera connected to a computer?
-
Is it possible to get full access to the memory card file system via a camera connected to a computer?
Yes.
Contact me directly if you wish to test it.
-
Any further recent progress on this? BTW if you need another tester, point me to the latest version and I will give it a whirl.
-
As usual, the tester let me down.
Don't know why I bother.
By all means contact me directly with an email address.
David
-
Maybe it's too late or useless but today i ported ixus105's SDM code back into chdk so it could serve other people porting efforts or simply doesn't get lost.
git branch here: https://github.com/c10ud/CHDK/tree/ixus105 (https://github.com/c10ud/CHDK/tree/ixus105)
link to patch for current trunk: http://chdk.setepontos.com/index.php?topic=650.msg84777#msg84777 (http://chdk.setepontos.com/index.php?topic=650.msg84777#msg84777)
As said in that topic, my code is completely untested (apart from compiling) and meant for educational purposes mostly.
-
Thinks, I've added this to the trunk, with autobuild disabled. Here is a build of the current trunk code, in case anyone wants to try it.
edit:
build removed, since it clearly doesn't work. Anyone who wants to play with it should consult the source.
-
As usual, the tester let me down.
Greetings dear David!
I long time did not answer and was not engaged in testing CHDK/SDM because I had serious problems in real life. There was no time to be engaged in testing, even the forum has visited for the first time in two months.
In July I can probably continue testing. In May and June I do not have time for careful testing CHDK/SDM.
-
In July I can probably continue testing.
See you then.
-
See you then.
Actually, from a CHDK point of view, it would be more interesting to hear from some of the 26 people who downloaded the beta of CHDK for the SD1300 from the link (http://chdk.setepontos.com/index.php?topic=5720.msg84868#msg84868) posted above by reyalp.
-
Thinks, I've added this to the trunk, with autobuild disabled. Here is a build of the current trunk code, in case anyone wants to try it.
1. CHDK files has written on the microSD.
2. Turning on the camera.
3. The lens motor starts to work. Lens moving very slow. This is strange.
4. The lens is stuck.
5. The camera automatically turns off.
Result: Error lens. The lens does not move.
Reboot without the microSD does not help. The screen says that there was an error of the lens and the camera will automatically turn off.
-
Result: Error lens. The lens does not move.
This is an all too common problem with the zoom lens on P&S camera. Although your description of what happened seems to suggest its not caused by physical damage jamming the lens - which is what usually seems to cause this.
Reboot without the microSD does not help. The screen says that there was an error of the lens and the camera will automatically turn off.
Did you also pull the battery out for a couple of minutes ?
This is the best website I've found on fixing lens errors.
http://camerarepair.blogspot.com/2007/12/fixing-lens-error-on-digital-camera.html (http://camerarepair.blogspot.com/2007/12/fixing-lens-error-on-digital-camera.html)
You might need to start down near step 7, but I'd wait to see if anyone else posts some ideas.
-
Did you also pull the battery out for a couple of minutes ?
Yes, the camera was without the accumulator more than 120 minutes.
http://camerarepair.blogspot.com/2007/12/fixing-lens-error-on-digital-camera.html (http://camerarepair.blogspot.com/2007/12/fixing-lens-error-on-digital-camera.html)
You might need to start down near step 7, but I'd wait to see if anyone else posts some ideas.
Disassemble the camera?
The lens is not completely straightened (~90% of normal state), and was automatically blocked.
Why CHDK controls the lens motor when the camera turning on?
Can CHDK/(other software/"firmware") unlock the lens?
-
Did you also pull the battery out for a couple of minutes ?
Yes, the camera was without the accumulator more than 120 minutes.
http://camerarepair.blogspot.com/2007/12/fixing-lens-error-on-digital-camera.html (http://camerarepair.blogspot.com/2007/12/fixing-lens-error-on-digital-camera.html)
You might need to start down near step 7, but I'd wait to see if anyone else posts some ideas.
Disassemble the camera?
The lens is not completely straightened (~90% of normal state), and was automatically blocked.
Why CHDK controls the lens motor when the camera turning on?
Can CHDK/(other software/"firmware") unlock the lens?
Even if that build is experimental I tend to think you're a victim of an infortunate coincidence, here's why:
- I see many downloads of that build but noone posted any issue
- The platform-specific code is nothing more than SDM's while the other code is what's used in every other CHDK-trunk port -- there could be some minor #define discrepancy but that could be a cause of issues when using some particular feature, early boot is mostly platform-specific code.
However if someone else runs in the same issue then I'm wrong and the code is clearly dangerous, but so far in CHDK history this never happened if I'm not wrong (mostly coincidences and false positives).
P.S. In my CHDK experience i had lens errors caused by software (e.g. i had one issue with one camera that gave the error when plugging the PC USB cable) but they all got fixed by a simple power-cycle (without the SD card)
Too bad I don't have this camera so I cannot test this. I hope you do manage to restore your camera (you can just ask for Canon's assistance though)
greets
-
I tried ixus105_sd1300-100d-1.1.0-full.zip firmware today on my ixus 105 GM1.00D (1.0.0.0)
adj ver.006.010
mecha firm 3.01
When doing a firmware update, the screen devdes into 4 chdk logo's but does not actualy load the firmware.
my sd card is fat and made bootable. I wonder if i'm doing something wrong or if it's the firmware version that is not compatible?
edit: I tried with a Sandisk SDHC card and a 2 GB SD card. I used cardtricks in administrator modus and did not forget to lock the card.
When I now try to do a firmware update, 2 red dots apear on my screen (as when my screen was devided into 4 logo's) but without the logo's.
-
When doing a firmware update, the screen devdes into 4 chdk logo's but does not actualy load the firmware.
If you see 4 logos (like this http://chdk.setepontos.com/index.php?topic=2972.msg29795#msg29795 (http://chdk.setepontos.com/index.php?topic=2972.msg29795#msg29795) ), then CHDK is at least starting to load. Does the camera crash after that ? If not, what do you mean by "does not actually load the firmware" ?
-
That are indeed the 4 logo's.
But then nothing further hapens, when i tilt the camera, or press a button, the logo's disappear. The card is still locked after that. So somewhere the process halts.
I also can not bring up the ALT menu, witch I assume should be under the display button.
-
That are indeed the 4 logo's.
But then nothing further hapens, when i tilt the camera, or press a button, the logo's dissapear. The card is still locked after that. So somewhere the process halts.
No, if you see the logo and the camera doesn't crash, then at least some parts of CHDK are running.
If you see card locked, then the card lock override code isn't correct.
The "display" button should theoretically open the CHDK alt menu.
edit:
fixed typo.
-
When I turn the card lock off, i can still see the firmware update in the menu. I don't know if this is normal because i have no experience with the workings of chdk
-
When I turn the card lock off, i can still see the firmware update in the menu. I don't know if this is normal because i have no experience with the workings of chdk
The firmware update menu item appears if there is a ps.fi2 or equivalent file in the root of your SD card and you start the camera in the "playback" mode. At that point, CHDK has not been loaded on your system - you are running the original Canon firmware.
-
See you then.
Actually, from a CHDK point of view, it would be more interesting to hear from some of the 26 people who downloaded the beta of CHDK for the SD1300 from the link (http://chdk.setepontos.com/index.php?topic=5720.msg84868#msg84868) posted above by reyalp.
I did it 3 days before my kid mistook camera for rubber ducky so i will make attempt to clean it, but my experiences so far:
it shows startup logo, but no button combination brings up the CHDK menu and no signs of CHDK OSD like battery or temperature (so dancingbits are ok and offsets are right in some part)
Also lens crash was very common with SDM i.e 100% guaranteed if you try to zoom before SDM OSD is displayed, but sometimes also during prolonged use, easy cure if lens has crashed retracted is lightly clapping lens side of camera against own leg or pillow.
-
Today i got the ixus105 back, here's a test build (against trunk), i think it's ready for beta status (i will send a diff for trunk soon).
I tested quite everything and looks like it's working, the only thing missing is movie override.
edit: attachment removed, ixus105 is now in the autobuild
-
it looks like the generated DNGs have wrong colors, probably easy to fix in the camera defines, but if you know how to do it please you're welcome :) too tired atm
-
it looks like the generated DNGs have wrong colors, probably easy to fix in the camera defines, but if you know how to do it please you're welcome :) too tired atm
Tools included with SDM generated wrong DNG header too.
-
it looks like the generated DNGs have wrong colors ...
Error is found.
From DNG by CHDK (invalid color):
"CFA Pattern 2" = "[Red, Green], [Green, Blue]"
"Color Matrix" = "[0.827547, -0.290458, -0.126086], [-0.012829, 0.530507, 0.050537], [0.005181, 0.048183, 0.245014]"
From HDR by SDM (valid color):
"CFA Pattern 2" = "[Green, Blue], [Red, Green]"
"Color Matrix" = "[1.4052, -0.5229, -0.1156], [-0.1325, 0.942, 0.2252], [-0.0498, 0.1957, 0.4116]
-
thanks, so this patch would be correct?
--- a/platform/ixus105_sd1300/platform_camera.h
+++ b/platform/ixus105_sd1300/platform_camera.h
@@ -39,13 +39,13 @@
#define CAM_EXT_TV_RANGE 1
#define CAM_HAS_ND_FILTER 1
- // pattern // TODO:
- #define cam_CFAPattern 0x02010100 // Red Green Green Blue
- // color // TODO:
+ // pattern
+ #define cam_CFAPattern 0x01000201 // Green Blue Red Green
+ // color
#define CAM_COLORMATRIX1 \
- 827547, 1000000, -290458, 1000000, -126086, 1000000, \
- -12829, 1000000, 530507, 1000000, 50537, 1000000, \
- 5181, 1000000, 48183, 1000000, 245014, 1000000
+ 14052, 10000, -5229, 10000, -1156, 10000, \
+ -1325, 10000, 9420, 10000, 2252, 10000, \
+ -498, 10000, 1957, 10000, 4116, 10000
#define cam_CalibrationIlluminant1 1 // Daylight // TODO:
// cropping
-
thanks, so this patch would be correct?
...
"cam_CFAPattern" - correct.
"CAM_COLORMATRIX1" - seems to have no errors.
-
thanks, i'll ask for inclusion in the chdk trunk then :)
-
Hi everyone! I've returned after a lot of time in which I haven't had the Ixus 105. Now I have it again, and I'm doing lots of HDR photos and timelapses, as well as long exposures, and I want to thank very much all of you who have made it possible. This add-on on such a cheap camera makes it just amazing!
Well, I'm using SDM from the official download page, and now I see in previous posts that there's a new CHDK ported by c10ud. The only functionality I'm missing is shooting in RAW without that magenta predominance. Does the last post by bazhuryan mean that raw shooting works right in the c10ud CHDK?
-
The only functionality I'm missing is shooting in RAW without that magenta predominance. Does the last post by bazhuryan mean that raw shooting works right in the c10ud CHDK?
The patch for that was applied today - the download from the autobuild should pick it up overnight. Look for version 2098 or higher.
-
Wow, thank you very much!! you guys are amazing!!
Just one doubt waterwingz, when you say autobuild, you mean CHDK or SDM? If CHDK, will it appear for Ixus 105 here tonight? http://chdk.wikia.com/wiki/SD1300IS (http://chdk.wikia.com/wiki/SD1300IS)
-
Just one doubt waterwingz, when you say autobuild, you mean CHDK or SDM? If CHDK, will it appear for Ixus 105 here tonight?
CHDK is available (finally) for the ixus105_sd1300. I just checked the autobuild download page and its there.
http://chdk.wikia.com/wiki/SD1300IS (http://chdk.wikia.com/wiki/SD1300IS)
Fixed.
-
I added it to the ACID tables at noon today, so ACID will find and download it
-
Terrific guys. I've just downloaded and tried the stable branch and raw colors in CHDK are fine. It seems I've just returned at the exact moment! ;)
Once again, thank you for making this possible!
-
Guys,
EV bracketing is not working on my IXUS 105. I have tryed both versions of CHDK (stable and beta, actually both ALPHA). Its not implemented, or what?
I done everything i know on setting, I do it on my A590IS flawlessly, but on IXUS 105 the bracketed shots are with the same EV/ShutterSpeed (i have chosen 2EV +/- bracketing)
Also, there is no RAW files in bracketing mode, but I didn't disable RAW in bracketing mode....
-
It's strange because it works well for me. What is your firmware version?
-
Hi everyone. I am trying to get CHDK for my SD1300 camera (firmware 1.00c) which is supposed to be here:
http://www.zshare.net/download/902798705d1d1c04/ (http://www.zshare.net/download/902798705d1d1c04/)
But the link is not working anymore. Does anyone knows where can I get it?
Thank you,
Antonio.
-
Hi everyone, i have an ixus 107, with i think is the same thing as 105/SD1300 (firmware 1.00D) and i found that raw dng files come out cropped to 10mp. I have two examples taken at 28 and 112 mm, both on tripod and without IS. You can notice that in raws there isn't the right and bottom side.
Any idea about that?
Thank you for your great job! ;)
-
Examples @112mm
-
Hi everyone, i have an ixus 107, with i think is the same thing as 105/SD1300 (firmware 1.00D) and i found that raw dng files come out cropped to 10mp. I have two examples taken at 28 and 112 mm, both on tripod and without IS. You can notice that in raws there isn't the right and bottom side.
Any idea about that?
Thanks for the very clear examples.
It's not really possible for the actual raw to be narrower than the jpeg, if the raw width were wrong, the picture would be completely garbled.
However, it is possible that the active area and/or DNG default crop is wrong for this port, so this seems like the most likely explanation.
Looking at http://trac.assembla.com/chdk/browser/trunk/platform/ixus105_sd1300/platform_camera.h (http://trac.assembla.com/chdk/browser/trunk/platform/ixus105_sd1300/platform_camera.h) the active area seems suspiciously small compared to the raw dimensions. If you can upload a CHDK raw (not DNG) from the camera somewhere, someone can probably come up with better values.
-
Here is a raw file and the corresponding jpg
(please copy & paste if links doesn't work)
http://belluzz.altervista.org/forum/CRW_0469.CR2 (http://belluzz.altervista.org/forum/CRW_0469.CR2)
http://belluzz.altervista.org/forum/IMG_0469.JPG (http://belluzz.altervista.org/forum/IMG_0469.JPG)
-
Hi everyone, i have an ixus 107, with i think is the same thing as 105/SD1300 (firmware 1.00D) and i found that raw dng files come out cropped to 10mp.
If you look back in this porting thread (around March 2012), you'll find some discussion about this.
If you can run Win32 programs, here (http://chdk.setepontos.com/index.php?topic=7929.0) is a modified version of DNG4PS-2 that allows importing and exporting single camera definitions. I've attached an Ixus105 definition that can be imported with settings -> camera options -> import cam.
It's not proper, especially the color matrix values. You could play with the "active zone" values to see what part of the RAW is worth to keep. As I remember, it's a bit difficult to choose (there is some image data near the corners that is darker, but sort of usable). If you can come up with values that you find good enough, post them here (with example pictures if you want). DNG4PS-2 needs RAW files (CR2 in your case), not DNGs as input.
Why all this? As I don't own this camera, I don't want to be the one who chooses the "right" values.
-
Hi everyone, i have an ixus 107, with i think is the same thing as 105/SD1300 (firmware 1.00D) and i found that raw dng files come out cropped to 10mp.
If you look back in this porting thread (around March 2012), you'll find some discussion about this.
If you can run Win32 programs, here (http://chdk.setepontos.com/index.php?topic=7929.0) is a modified version of DNG4PS-2 that allows importing and exporting single camera definitions. I've attached an Ixus105 definition that can be imported with settings -> camera options -> import cam.
It's not proper, especially the color matrix values. You could play with the "active zone" values to see what part of the RAW is worth to keep. As I remember, it's a bit difficult to choose (there is some image data near the corners that is darker, but sort of usable). If you can come up with values that you find good enough, post them here (with example pictures if you want). DNG4PS-2 needs RAW files (CR2 in your case), not DNGs as input.
Why all this? As I don't own this camera, I don't want to be the one who chooses the "right" values.
I've usually found that the best way to do this is to set the mask boundaries to zero - all the way out to the sensor dimensions. Then look at the resulting images zoomed out to the pixel level to see where the actual active sensor are is. Don't worry about the corners - you will get lens vignetting there. Look for the clear point where the sensor is masked and has no image date.
Also, you may need to play with the sensor CFA pattern depending on where you set the image boundries to adjust for the dreaded purple image.
-
I've just figured out how to compile chdk, after a try with this values
#define CAM_ACTIVE_AREA_X1 0
#define CAM_ACTIVE_AREA_Y1 0
#define CAM_ACTIVE_AREA_X2 4104
#define CAM_ACTIVE_AREA_Y2 3048
i got this: http://belluzz.altervista.org/forum/CRW_0480.DNG (http://belluzz.altervista.org/forum/CRW_0480.DNG)
(taken with camera rotated 90° clockwise, sorry)
jpg: http://belluzz.altervista.org/forum/0480DNG.jpg (http://belluzz.altervista.org/forum/0480DNG.jpg)
Assuming a desired size of 4000x3000 (like original jpgs) a starting point could be an offset of
16px from left side
24px from top
88px from right
24px from bottom
Edit:
I've tried DNG4PS-2, but something goes wrong
Error: Can't find camera profile for this file
-
Assuming a desired size of 4000x3000 (like original jpgs)
The jpeg may crop out valid image information at the edges. Study the DNG file in full zoom mode at the center of the edges to determine where the actual limit of valid information is.
(sorry .. your download link was so slow ... 15 minutes to see the DNG file )
-
I've tried DNG4PS-2, but something goes wrong
Error: Can't find camera profile for this file
You either need a jpeg file beside the raw with the same number, or select Ixus 105 from the dropdown box (4104x3048) on the second tab (camera types) of the settings dialog. Of course you need to import the definition (or create one from scratch) before.
-
I've just figured out how to compile chdk, after a try with this values
#define CAM_ACTIVE_AREA_X1 0
#define CAM_ACTIVE_AREA_Y1 0
#define CAM_ACTIVE_AREA_X2 4104
#define CAM_ACTIVE_AREA_Y2 3048
i got this: http://belluzz.altervista.org/forum/CRW_0480.DNG (http://belluzz.altervista.org/forum/CRW_0480.DNG)
(taken with camera rotated 90° clockwise, sorry)
jpg: http://belluzz.altervista.org/forum/0480DNG.jpg (http://belluzz.altervista.org/forum/0480DNG.jpg)
Assuming a desired size of 4000x3000 (like original jpgs) a starting point could be an offset of
Desired size should be based on valid data, not jpeg size. Usually it's a bit larger. However, this points out another problem with the port, the jpeg size (which is used for the default DNG crop) is 3648x2736, while like your post, Canon specs say it's 4000x3000. Copy paste :'(
So you definitely want
#define CAM_JPEG_WIDTH 4000
#define CAM_JPEG_HEIGHT 3000
You probably have to fix the active area to at least be larger than this.
I converted your "cr2" with
rawconvert -12to8 -w=4104 -h=3048 -pgm CRW_0469.CR2 CRW_0469.PGM
opening the resulting PGM in gimp, I'd say
left: 0
top: 10 (or 9)
right: 32
bottom: 8 (or 7)
The "or" would include rows that have some data that isn't at the same level as the rest of the image. I've gone back and forth over whether these should be included or not, but with just one row on top and bottom, I'd be inclined to leave it out.
In chdk defines, this would be:
#define CAM_ACTIVE_AREA_X1 0
#define CAM_ACTIVE_AREA_Y1 10
#define CAM_ACTIVE_AREA_X2 4072
#define CAM_ACTIVE_AREA_Y2 3040
If you can try a build with these settings and report back, we can fix them in svn.
-
I've tested this values
#define CAM_JPEG_WIDTH 4000
#define CAM_JPEG_HEIGHT 3000
#define CAM_ACTIVE_AREA_X1 0
#define CAM_ACTIVE_AREA_Y1 10
#define CAM_ACTIVE_AREA_X2 4072
#define CAM_ACTIVE_AREA_Y2 3040
and they work well. The only problem i have noticed is that DNG default crop is shifted by a few pixels to the right compared to jpg (and i have not figured out how to view all the data in Adobe Camera Raw. Irfanview shows everything)
Here is an example taken at maximum zoom range, where no distortion correction is applied:
DNG
https://dl.dropbox.com/u/12336849/CRW_0488.DNG
jpeg
https://dl.dropbox.com/u/12336849/IMG_0488.JPG
CHDK RAW (actually is another shot, well aligned horizontally but slightly shifted vertically)
https://dl.dropbox.com/u/12336849/CRW_0489.CRW
-
Thanks for checking. I've checked in these values.
The only problem i have noticed is that DNG default crop is shifted by a few pixels to the right compared to jpg (and i have not figured out how to view all the data in Adobe Camera Raw. Irfanview shows everything)
Unfortunately, the current CHDK code just centers the default crop within the active area, so it won't necessarily line up with the Canon jpeg position exactly. This is a know defect, but there isn't really a way to fix it at this point.
-
Hey everyone!
I just wanted to drop by and say "thanks" to you guys for working to get CHDK on the SD1300. I can't actually use CHDK on my camera yet because I have firmware version 1.00C, but I still think it's pretty cool. :)
And while I don't know anything about what you guys are doing, if you need someone to test and say "hey I pressed this button and then x thing happened/went wrong" I might be able to help.
-
@like_whatever
I sent a PM (private message) with the link to a pre-alpha version for your ixus105 100c.
It seems that ixus105 is not completely ported. If there is any other beta tester available for ixus105, send your e-mail address to me via private message.
-
The correct active area for my ixus 105 fw 1.00d is
#define CAM_ACTIVE_AREA_X1 8
#define CAM_ACTIVE_AREA_Y1 22
#define CAM_ACTIVE_AREA_X2 4024
#define CAM_ACTIVE_AREA_Y2 3028
Pixels outside this area are either darker or lighter (as if these pixels have a different mask than those in the center), and are not usable.
-
On request the colors of the menu, splash screen and palette in chdk settings/color settings/draw palette
attached: splash and menu in play mode
-
attached palette in play mode
-
attached menu in rec mode and palette in rec mode
-
Some more info: fw 1.00d, no palette specified in platform_camera.h so using default palette1.
-
@casrap
Thanks for the report.
I'll use your movie_rec.c to port the same function in 100b and 100c. I'll post the patches in a couple of days.
About the colors, I think that is better to change the palette ;)
-
AFAIK changing the palette does not change the available colors, it only changes the selection from those colors for chdks output?
-
AFAIK changing the palette does not change the available colors, it only changes the selection from those colors for chdks output?
Correct. The choice of palette determines how CHDK maps the colors it wants to the camera's 256 byte array of values that hold the camera colors. Unfortunately, Canon changes that array between different modes (shooting, playback, menu, etc) so selecting a nice mapping in playback does not guarantee good looking colors in shooting mode.
Some of the more recent cameas have an option to overwrite unused values in the playback and record palettes so that nice colors can be selected.
-
Hi all,
during last days we were testing FW v 1.0b.
camera working with prepared CHDK patch version.
@nafraf - thank you
-
I found a bug that disables all overrides; when you select a self timer few of the overrides work and after one shot none of the overrides work. I fixed the bug, and nafraf kindly cleaned it up, ported it to 100b and will post the update to the autobuild svn and/or will ask for testers for the 100b version.
-
Patch to remove KEY_POWER from KEY_MASK0, bug reported here (http://chdk.setepontos.com/index.php?topic=9986.msg118975#msg118975).
-
Patch to remove KEY_POWER from KEY_MASK0, bug reported here (http://chdk.setepontos.com/index.php?topic=9986.msg118975#msg118975).
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 3800 (https://www.assembla.com/code/chdk/subversion/commit/3800)
-
Replying to post from the chdkptp thread, because this is almost certainly a porting issue:
in Full zoom: no distortions via chdkptp client, but distorted using init_usb_capture(1,0,0); and shoot();
Cam Model is IXUS 105.
This first image is taken using chdkptp client (remote shoot), exhibiting no distortion, the second has (note the bent edges).
I use a java library to take photos (relevant lines:https://github.com/acamilo/CHDK-PTP-Java/blob/master/src/main/java/chdk/ptp/java/camera/AbstractCamera.java#L389 (https://github.com/acamilo/CHDK-PTP-Java/blob/master/src/main/java/chdk/ptp/java/camera/AbstractCamera.java#L389)).
Why are the images distorted and what to do against it ?
What does your client do better ?
The difference is almost certainly related to the method used to set zoom rather than the client. The chdkptp GUI just sends click('zoom_in') or click('zoom_out') for each button press. Using script set_zoom lets you go directly to a specific zoom point, but in some ports the camera doesn't update it's distortion correction settings.
It is possible we can adjust the port to make set_zoom behave correctly.
Please post your canon firmware version. If no one else beats me to it, I'll try to post a test build in the next few days.
-
The difference is almost certainly related to the method used to set zoom rather than the client. The chdkptp GUI just sends click('zoom_in') or click('zoom_out') for each button press. Using script set_zoom lets you go directly to a specific zoom point, but in some ports the camera doesn't update it's distortion correction settings.
Good Hint! It seems. Using manual zoom, everything is fine, using set_zoom shows those distortions.
It is possible we can adjust the port to make set_zoom behave correctly.
Do you have any hint on how to do that? CHDK 1.5.0-4626 firmware 100d
-
Do you have any hint on how to do that? CHDK 1.5.0-4626 firmware 100d
If you want to try to modify the code yourself, look at ports which use CAM_USE_ALT_SET_ZOOM_POINT and CAM_USE_ALT_PT_MoveOpticalZoomAt in platform_camera.h (ixus140_elph130 is an example)
Note that enabling these may have other side effects, like causing the camera to crash after zoom, possibly depending on focus mode. Some cameras may need CAM_NEED_SET_ZOOM_DELAY to prevent crashes.
-
Here's a test build for ixus105_sd1300 100d, with CAM_NEED_SET_ZOOM_DELAY, CAM_USE_ALT_SET_ZOOM_POINT and CAM_USE_ALT_PT_MoveOpticalZoomAt
Please check whether this fixes (or reduces) the distortion problems, and whether it crashes if you use set_zoom to move through the whole zoom range.
-
Works great! Played around for 10mins zooming around, no issues so far.
(images are at 90% zoom). Left reyalp modif working, right CHDK 1.5.0 4659.
-
Works great! Played around for 10mins zooming around, no issues so far.
(images are at 90% zoom). Left reyalp modif working, right CHDK 1.5.0 4659.
@axoin
Thanks, I've checked this in for both 1.4 and 1.5
Can you check
1) Does the camera re-focus after you use set_zoom. If Continuous AF is enabled in the canon menu, please try with it off.
2) If you use AF lock (either set_aflock(1) or using regular Canon keys) and then use set_zoom, does it crash?
-
a). There is no setting for Continous AF.
In Auto Mode, it does refocus after set_zoom.
In P Mode it does not. This is the same behaviour as with stock firmware.
b). No it does not. You can zoom while it says AFL in the display and it doesn't crash. Works only in P though (as intended, says handbook). Looks fine :)
-
@srsa_4c Little did I know. While things in Rec mode look as if they can be improved upon, Play does not contain anything but grascale and shades of orange, how do I get CHDK Logo like Red into that?
-
This is what Rec can be made using what the palette as provided by the Canon FW.
// Record mode colors
unsigned char rec_colors[] =
{
COLOR_TRANSPARENT, // Placeholder for script colors
COLOR_BLACK, // Placeholder for script colors
0x01, // White
0x66, // Red
0x66, // Dark Red --- there is none this is the same red
0x1E, // Light Red --- there is none this is a dark orange
0x69, // Green
0x6B, // Dark Green
0x5F, // Light Green
0x61, // Blue
0x67, // Dark Blue
0x68, // Light Blue / Cyan
0x12, // Grey
0x16, // Dark Grey
0x0E, // Light Grey
0x60, // Yellow
0x4C, // Dark Yellow
0x6C, // Light Yellow
0xF1, // Transparent Dark Grey
0x41, // Magenta --- there is none this is an orange
};
-
Ok, what I posted yesterday for i105 in terms of simple Rec mode palette is much better as it actually relates to the camera, no idea where the stuff in the current port comes from. I get a green battery, display overlay and menus are legible. As soon as I press func that breaks as the palette changes, see attached. Can this be detected there seem to be ok colors in that case or will only a custom palette fix this? Where can I read about implementing such a custom palette?
One more thing, I figured I have a red, let's enable a zebra... Zebra floods half the screen with rubbish when it kicks in, can we fix that?
-
While things in Rec mode look as if they can be improved upon, Play does not contain anything but grascale and shades of orange, how do I get CHDK Logo like Red into that?
Not without injecting extra colors into that palette.
As soon as I press func that breaks as the palette changes, see attached.
If you bring up a Canon "dialog", the palette tends to change. Only a few ports handle that as supporting the plain rec and play mode is usually sufficient.
The simple method can't cope with this, injected colors are needed.
One more thing, I figured I have a red, let's enable a zebra... Zebra floods half the screen with rubbish when it kicks in, can we fix that?
Try removing these lines from platform/ixus105_sd1300/lib.c:
// Y multiplier for cameras with 480 pixel high viewports (CHDK code assumes 240)
int vid_get_viewport_yscale() {
return 2;
}
-
One more thing, I figured I have a red, let's enable a zebra... Zebra floods half the screen with rubbish when it kicks in, can we fix that?
Try removing these lines from platform/ixus105_sd1300/lib.c:
// Y multiplier for cameras with 480 pixel high viewports (CHDK code assumes 240)
int vid_get_viewport_yscale() {
return 2;
}
Did that, problem unchanged.
-
Did that, problem unchanged.
Adding that function to the a3200 port breaks zebra, exactly like on your picture. Make clean, rebuild and make sure you update diskboot/ps.fi2 on the card.
-
Did that, problem unchanged.
Adding that function to the a3200 port breaks zebra, exactly like on your picture. Make clean, rebuild and make sure you update diskboot/ps.fi2 on the card.
Ok, I was pretty sure I had done it as needed but still; stuff happens. So I downloaded a fresh trunk, built it, copied it on a fresh SD card, it did not have my palette alterations, I put those in and removed this from lib.c cleaned, rebuilt, updated card, platte fixed again, zebra still broken...
-
Replacing the viewport width height functions that are currently
int vid_get_viewport_width()
{
if ((mode_get() & MODE_MASK) == MODE_PLAY)
{
return 360;
}
extern int _GetVRAMHPixelsSize();
return _GetVRAMHPixelsSize() >> 1;
}
long vid_get_viewport_height()
{
if ((mode_get() & MODE_MASK) == MODE_PLAY)
{
return 240;
}
extern int _GetVRAMVPixelsSize();
return _GetVRAMVPixelsSize() >> 1;
}
with fixed values as used in the i100 port fixes zebra.
int vid_get_viewport_width()
{
return 360;
}
long vid_get_viewport_height()
{
return 240;
}
Adverse effects? Anything specific to test?
Note: what srsa_4c indicted to remove stayed out.
-
Adverse effects? Anything specific to test?
Live view via chdkptp, zebra, in various shooting modes and movie resolutions. If there are no significant problems, this could be made official.
-
Adverse effects? Anything specific to test?
Live view via chdkptp, zebra, in various shooting modes and movie resolutions. If there are no significant problems, this could be made official.
Thanks I'll try those and will report.
-
Adverse effects? Anything specific to test?
Live view via chdkptp, zebra, in various shooting modes and movie resolutions. If there are no significant problems, this could be made official.
Thanks I'll try those and will report.
@srsa_4c finally got around to test this more. CHDKPTP Live view is fine, shooting modes are fine, 640 video is fine - but 320 video has everything at an offset. The palette I quickly established for shooting mode is much closer to CHDK colors and works fine. Play is what it is... Anyway back to the video 320 problem... I said what I did was inspired by what I found on Ixus100 - that is in the lib.c files for the individual FWs. So, I tried that camera. It features 1280 640 and 320 video. The former two are fine. 320 shows the same problem as observed on Ixus 105. I wouldn't be surprised if more ports did...
-
See attached screen shots, literally.
We are looking at a TX1 camera box through an Ixus 100.
We have "EDGE:Live" on as other than a classic zebra it needs no over exposure.
Top image is video 640 and everything else looks like that.
The lower two images are video 320.
You can see how things get squeezed while the hight seems fine. The stuff on the right image half builds up and vanishes and continues that cycle forever.
-
320 shows the same problem as observed on Ixus 105. I wouldn't be surprised if more ports did...
Yes, it's likely that several ports have issues with some (perhaps less often used) modes, such as 320x240 video and stitch.
If other modes do work on this cam, that's already an improvement.
So, are these your changes:
- removal of vid_get_viewport_yscale()
- vid_get_viewport_width() and vid_get_viewport_height() returning a fixed value
- rec mode palette
?
-
320 shows the same problem as observed on Ixus 105. I wouldn't be surprised if more ports did...
Yes, it's likely that several ports have issues with some (perhaps less often used) modes, such as 320x240 video and stitch.
Ah stitch, didn't even think to try that one :) I fooled around with the width and height and found none fixes 320 video it's probabaly something like the y scaling but with x and only if 320 is active, beyond me to fix without effort.
If other modes do work on this cam, that's already an improvement.
So, are these your changes:
- removal of vid_get_viewport_yscale()
- vid_get_viewport_width() and vid_get_viewport_height() returning a fixed value
- rec mode palette
?
Yes that's a full account of 'em. 360x240 for the dimensions as posted, palette also as posted.
-
Yes that's a full account of 'em. 360x240 for the dimensions as posted, palette also as posted.
Committed in changeset 5303 (https://app.assembla.com/spaces/chdk/subversion/commits/5303). Can you check the official build (when it's available)?
I fooled around with the width and height and found none fixes 320 video it's probabaly something like the y scaling but with x and only if 320 is active, beyond me to fix without effort.
IIRC this mode only fills half the width in the buffer, it would require some more support code (there are some ports that handle this better, but I'm not sure it's worth the effort).
-
Can you check the official build (when it's available)?
I tested Release 5305 and it worked as expected.
-
I tested Release 5305 and it worked as expected.
Thanks.