Mode dials and Playback pushbuttons

reyalp

14082

Re: Mode dials and Playback pushbuttons

« Reply #70 on: 27 / October / 2009, 16:48:46 »

Advertisements

Quote from: whoever on 27 / October / 2009, 13:21:39

Came at last to compiling and checking this out on Ixus950 (wow, is this what it looks today? Can barely recognize the menus...), and yes, testlev2.lua works as advertised. Except I changed "ModeDialToM" to "ModeDialToP", as there's no true M-mode here.

Thanks, what happens on the cameras with an M mode that's really P was one of the things I meant to ask about. I assume you tried it with ModeDialToM and it didn't work ?

Logged

Don't forget what the H stands for.

fe50

3147
IXUS50 & 860, SX10 Star WARs-Star RAWs

Re: Mode dials and Playback pushbuttons

« Reply #71 on: 27 / October / 2009, 17:18:43 »

@reyalP:
I guess it's the same on all IXUS cameras, the Ixus "Manual" M mode is in fact the P mode, so ModeDialToP should work.
It does so on my SD400 & SD870;
ModeDialToM is ignored on the SD870 (this camera just ignores invalid modes),
the SD400 powers off with extended lens (as with other invalid modes), the camera can be restarted with the power btn (i.e. no crash).

There's also a post about the M/P mode thing laying around somewhere here in the forum ...

Logged

-->FIRMWARE DUMPS<-- * Manual * Lua * me

Microfunguy

4037

Re: Mode dials and Playback pushbuttons

« Reply #72 on: 27 / October / 2009, 19:45:02 »

Quote from: reyalp on 27 / October / 2009, 03:00:25

Just to be clear, you mean selecting ModeDialToRec crashed ?

Yes.

Quote

If so, you could try switching the Mask option on this item.

Did not seem to make any difference.

Inserting video cable blanked screen, opening battery cover caused reboot and closing lens cover caused shutdown.

Logged

whoever

280
IXUS950

Re: Mode dials and Playback pushbuttons

« Reply #73 on: 28 / October / 2009, 03:40:00 »

@reyalP:
Overriding ModeDialToM doesn't crash Ixus950. It sets the mode (propset 49) to 32769, an otherwise impossible value. It feels like somewhat truncated P-mode -- e.g., missing auto-ISO and auto-flash options. Otherwise, nothing interesting/useful.

Logged

reyalp

14082

Re: Mode dials and Playback pushbuttons

« Reply #74 on: 28 / October / 2009, 03:57:36 »

Quote from: whoever on 28 / October / 2009, 03:40:00

@reyalP:
Overriding ModeDialToM doesn't crash Ixus950. It sets the mode (propset 49) to 32769, an otherwise impossible value. It feels like somewhat truncated P-mode -- e.g., missing auto-ISO and auto-flash options. Otherwise, nothing interesting/useful.

Right, it seems like this answers the question. On cameras where the "M" mode on the dial is functionally a "P" mode, canon uses "P" internally rather than changing the meaning of the "M" events. This is good.

Logged

Don't forget what the H stands for.

fudgey

1705
a570is

Re: Mode dials and Playback pushbuttons

« Reply #75 on: 28 / October / 2009, 17:37:15 »

Quote from: whoever on 27 / October / 2009, 13:21:39

Surely, there's another variable that does change in play mode. Here it is at 0x23AC, and its value is always 0xFFFF in play and something else otherwise. Not sure how to find it in general -- it is referenced in quite a few places that are not easily recognizable. Except perhaps for one particular piece of code that explicitly compares the value with 0xFFFF,

Code in a570 (at and near 0xffc18008) is very similar to ixus950, this variable is at 0x2344 for both a570 subs (100e and 101a). It's 0xFFFF in play, something else in rec as you mentioned.

Logged

reyalp

14082

Re: Mode dials and Playback pushbuttons

« Reply #76 on: 30 / October / 2009, 23:06:52 »

It looks like the playrec_mode variable discussed here http://chdk.setepontos.com/index.php/topic,2468.msg42274.html#msg42274 is present in most cameras (vxworks digic II through dryos digic IV) with the same values, so this looks like a good candidate to replace physw_status checks. It is also quite easy to find, e.g. string "MenuOut"

Logged

Don't forget what the H stands for.

fudgey

1705
a570is

Re: Mode dials and Playback pushbuttons

« Reply #77 on: 31 / October / 2009, 06:17:29 »

Quote from: reyalp on 30 / October / 2009, 23:06:52

It looks like the playrec_mode variable discussed here http://chdk.setepontos.com/index.php/topic,2468.msg42274.html#msg42274 is present in most cameras (vxworks digic II through dryos digic IV) with the same values, so this looks like a good candidate to replace physw_status checks. It is also quite easy to find, e.g. string "MenuOut"

a570 100e 0xC610 (found at ffeb3290 called near the end of function ffea5b98 SSAPI::MenuOut) behaves as playrec_mode described in the sx10 thread (except that it's not just movie position of the mode dial that makes the value go to 5 for a little while -- also M and KIDS&PETS and maybe others...AUTO does it sometimes with mem browser active so I guess it changes so quickly it's not always displayed (but e.g. Av or P never appear to make it go to 5).

Logged

Microfunguy

4037

Re: Mode dials and Playback pushbuttons

« Reply #78 on: 31 / October / 2009, 07:38:56 »

Quote from: fudgey on 31 / October / 2009, 06:17:29

a570 100e 0xC610 (found at ffeb3290 called near the end of function ffea5b98 SSAPI::MenuOut) behaves as playrec_mode

Well, I am not saying you are wrong but for switching the A570 100e to movie mode using a script, SDM uses the value 0x2348

As far as I know, that works on the A570.

Logged

fudgey

1705
a570is

Re: Mode dials and Playback pushbuttons

« Reply #79 on: 31 / October / 2009, 09:20:07 »

Quote from: Microfunguy on 31 / October / 2009, 07:38:56

Quote from: fudgey on 31 / October / 2009, 06:17:29

a570 100e 0xC610 (found at ffeb3290 called near the end of function ffea5b98 SSAPI::MenuOut) behaves as playrec_mode
Well, I am not saying you are wrong but for switching the A570 100e to movie mode using a script, SDM uses the value 0x2348

As far as I know, that works on the A570.

ewavr's mode_magic 0x2348 and playrec_mode 0xc610 are not the same thing. I have no clue what the purpose of either is in the camera, but playrec_mode always has a very small integer value whereas mode_magic seems to be 0xFFFFFFFF in PLAY mode and in REC mode somewhere around 0x1000 to 0x2000 depending on mode dial position.

What we're searching for here is a way for CHDK to reliably test whether the camera is in REC or PLAY mode. The problem with mode_magic is the same as with the existing phys_sw stuff: mode_magic remains 0xFFFFFFFF in REC mode if the switch is done using events... playrec_mode on the other hand doesn't get confused like this.

Logged