SX10 recreview_hold

hiker_jon

284

« on: 26 / November / 2009, 00:38:39 »

Advertisements

Hi,
I have been investigating the recreview_hold mode on the SX10. It doesn't behave the way my other cameras (590,720) do. In fact it seems that something very strange is happening.

In recreview_hold mode pressing the alt key does not cause the text "<ALT>" to appear.
However, when in recreview_hold mode, if I hit the alt key the disp key no longer changes the display of the held image. If I hit the alt key again then the disp key works normally. So the alt key does work somewhat.

I thought maybe it was just the text that doesn't appear in recreview_hold mode.
So in Main.c just after the lines:

Code: [Select]

	if (state_shooting_progress != SHOOTING_PROGRESS_PROCESSING) {
	    if (((cnt++) & 3) == 0)
	        gui_redraw();

I put the following two lines:

Code: [Select]

	
        if(gui_get_mode() == GUI_MODE_ALT) started(); 
	else finished();

My added code causes the alt key to toggle the led.
This works fine in record and in play mode, but in recreview_hold mode the led does not go on.

I wonder if anyone has a guess for what is going on?

Logged

fudgey

1705
a570is

Re: SX10 recreview_hold

« Reply #1 on: 26 / November / 2009, 15:19:36 »

I never knew you were even supposed to be able to switch to ALT mode while already pressing down another key (or have I misunderstood the meaning of 'recreview_hold mode'?).

Anyway, what happens on each of these cameras when you do this without CHDK? I don't know whether the direct print button (or whatever it's been assigned to or whatever ALT is on these cams) should do anything, but at least you can verify that erase button works in the same manner for each of these cameras during review hold and consequently expect that the keyboard hardware of each camera is likely able to also detect the direct print button press (if that's what is ALT on all these cams) while shutter is being held down.

Logged

hiker_jon

284

Re: SX10 recreview_hold

« Reply #2 on: 26 / November / 2009, 17:28:51 »

Hi,

I should have explained more. Recreview_hold happens in record mode when you press the set key while the latest recorded image is still visible. The camera then "holds" that image in the LCD and you can zoom and pan in it just like play mode. A shutter half press cancels the hold. On my other cameras the ALT key works as normal while in recreview_hold. You can access the CHDK menu, etc. The SX10 is different. Although there is some evidence that the ALT key is working (it inhibits the disp, zoom, delete, menu keys), no "<ALT>" text appears, no CHDK menu comes up.
So there is some fundamental difference in the SX10 software that will not display CHDK text in that mode. In the different disp pages that you can toggle through Canon graphics do appear. So graphics are indeed possible in recreview_hold mode. I can't even get the LED to turn on in recreview_hold mode.

I need some knowledgeable CHDK person to explain why the inhibition of the keys works (I don't know where or how this is done), but apparently the core_spytask loop() in main.c is not being executed.

Jon

Quote from: fudgey on 26 / November / 2009, 15:19:36

I never knew you were even supposed to be able to switch to ALT mode while already pressing down another key (or have I misunderstood the meaning of 'recreview_hold mode'?).

Anyway, what happens on each of these cameras when you do this without CHDK? I don't know whether the direct print button (or whatever it's been assigned to or whatever ALT is on these cams) should do anything, but at least you can verify that erase button works in the same manner for each of these cameras during review hold and consequently expect that the keyboard hardware of each camera is likely able to also detect the direct print button press (if that's what is ALT on all these cams) while shutter is being held down.

Quote from: fudgey on 26 / November / 2009, 15:19:36

I never knew you were even supposed to be able to switch to ALT mode while already pressing down another key (or have I misunderstood the meaning of 'recreview_hold mode'?).

Anyway, what happens on each of these cameras when you do this without CHDK? I don't know whether the direct print button (or whatever it's been assigned to or whatever ALT is on these cams) should do anything, but at least you can verify that erase button works in the same manner for each of these cameras during review hold and consequently expect that the keyboard hardware of each camera is likely able to also detect the direct print button press (if that's what is ALT on all these cams) while shutter is being held down.

Quote from: fudgey on 26 / November / 2009, 15:19:36

I never knew you were even supposed to be able to switch to ALT mode while already pressing down another key (or have I misunderstood the meaning of 'recreview_hold mode'?).

Anyway, what happens on each of these cameras when you do this without CHDK? I don't know whether the direct print button (or whatever it's been assigned to or whatever ALT is on these cams) should do anything, but at least you can verify that erase button works in the same manner for each of these cameras during review hold and consequently expect that the keyboard hardware of each camera is likely able to also detect the direct print button press (if that's what is ALT on all these cams) while shutter is being held down.

Logged

fudgey

1705
a570is

Re: SX10 recreview_hold

« Reply #3 on: 28 / November / 2009, 12:11:47 »

Ah, never knew of that feature... live and learn

Are you sure (state_shooting_progress != SHOOTING_PROGRESS_PROCESSING) is true during rec review hold in sx10? CHDK updates it and this could be a symptom of those updates not working properly on sx10.

Are you able to successfully execute scripts even if you can't see what's going on (you could test with a script that writes to a file or one that blinks leds)?

Missing display could be caused by the camera using a different buffer (since this feature is very similar to play mode display, it would appear logical to use the play mode display buffers even if older cameras used rec buffers (I didn't check)).

Logged

hiker_jon

284

Re: SX10 recreview_hold

« Reply #4 on: 28 / November / 2009, 14:27:25 »

You are right! Thanks a lot!

state_shooting_progress == SHOOTING_PROGRESS_PROCESSING in recreview_hold mode.
So I added the line

Code: [Select]

if(recreview_hold) state_shooting_progress = SHOOTING_PROGRESS_DONE;

just before the test. Not sure if this is the right thing to do.

I can find only one place where
state_shooting_progress gets set to SHOOTING_PROGRESS_PROCESSING and that is in
raw_savefile(). Can't see how that is getting called if I am not saving raws.

Jon

Quote from: fudgey on 28 / November / 2009, 12:11:47

Ah, never knew of that feature... live and learn

Are you sure (state_shooting_progress != SHOOTING_PROGRESS_PROCESSING) is true during rec review hold in sx10? CHDK updates it and this could be a symptom of those updates not working properly on sx10.

Are you able to successfully execute scripts even if you can't see what's going on (you could test with a script that writes to a file or one that blinks leds)?

Missing display could be caused by the camera using a different buffer (since this feature is very similar to play mode display, it would appear logical to use the play mode display buffers even if older cameras used rec buffers (I didn't check)).

Logged

fudgey

1705
a570is

Re: SX10 recreview_hold

« Reply #5 on: 29 / November / 2009, 09:59:17 »

Quote from: hiker_jon on 28 / November / 2009, 14:27:25

I can find only one place where
state_shooting_progress gets set to SHOOTING_PROGRESS_PROCESSING and that is in
raw_savefile(). Can't see how that is getting called if I am not saving raws.

A bunch of stuff other than raw saving is done there too (things that need to be done in that stage of the shooting process like curves and script shot histogram). I suppose the name is misleading because all that other stuff was added later.

Logged

fudgey

1705
a570is

Re: SX10 recreview_hold

« Reply #6 on: 29 / November / 2009, 15:37:39 »

Oh, I just realised that CHDK doesn't even attempt to redraw GUI if SHOOTING_PROGRESS_PROCESSING is true, so that's obviously why you weren't getting the UI.

Does shooting_in_progress() work for sx10 at all (I suppose a lot of scripts, MDFB for one, wouldn't work if it didn't)? That's just a wrapper to PROPCASE_SHOOTING which could obviously behave differently compared to older cameras even if other stuff appeared to work.

Logged

ewavr

1057
A710IS

Re: SX10 recreview_hold

« Reply #7 on: 29 / November / 2009, 16:55:56 »

Quote from: fudgey on 29 / November / 2009, 15:37:39

Does shooting_in_progress() work for sx10 at all (I suppose a lot of scripts, MDFB for one, wouldn't work if it didn't)? That's just a wrapper to PROPCASE_SHOOTING which could obviously behave differently compared to older cameras even if other stuff appeared to work.

It seems that PROPCASE_SHOOTING (#206) has differnt behavior on SX10: it changes from 1 to 0 only after exiting from review mode (on my a710 it changes from 1 to 0 after entering review-hold mode).
What is MDFB? If this is "fast motion detection", on SX10 this script is working fine.

Logged

fudgey

1705
a570is

Re: SX10 recreview_hold

« Reply #8 on: 30 / November / 2009, 12:10:31 »

Quote from: ewavr on 29 / November / 2009, 16:55:56

What is MDFB? If this is "fast motion detection", on SX10 this script is working fine.

Yes, MD Fast Burst...it uses the get_shooting command (or equivalent get_prop commands depending on version) extensively.

Logged