Mode dials and Playback pushbuttons

[fudgey]

You've done some great work here reyalp, thank you!

I think I'd like 2+4 the most i.e. using CHDK mode values for ubasic and lua, and optionally an external (to save RAM) lua library that provides names for those values. Going through the modemap should be enough for sanity check for "hidden" modes (hidden modes that are found to be useful using lower level functions could then be added to the modemap).

Propcase->mode translation function doesn't probably need to be available to script writers (get_shooting_mode will just need to go through the modemap and return the CHDK mode number usable for set_shooting_mode), as long as it doesn't crash when modemap is buggy or incomplete?

Buggy modemaps don't really worry me that much, fixing those has been on the todo list for ages and this thing ought to make that finally more or less happen. Or do you think there's physical danger in switching to incorrect modes on some cameras?

[fe50]

@reyalP  playrec_mode works fine on the SD400 (#1 aka MODE_P is the Manual mode, as usual on the Ixus cameras)

Small test script:

Code: Lua

1. sleep(2000)
2.  
3. for i=0,11 do
4.   print("Switch to: "..i)
5.   set_capture_mode(i)
6.   print("done.")
7.   sleep(3000)
8. end  
9.  
10. --[[
11. MODE_DIGITAL_MACRO,       0 },
12. MODE_P,                   1 },
13. MODE_AUTO,                3 },
14. MODE_MY_COLORS,           4 },
15. MODE_PORTRAIT,            5 },
16. MODE_SCN_WATER,           6 },
17. MODE_SCN_PARTY,           7 },
18. MODE_SCN_CHILD,           8 },
19. MODE_SCN_NIGHT,           9 },
20. MODE_STITCH,             10 },
21. MODE_VIDEO_STD,          11 }
22. --]]
23.  

*Edit:
I personally prefer No. 1, easy to handle.
Maybe a lookup table / "translation table" for the different cameras could be helpful to write camera independent scripts - not for me, but for others

[ewavr]

playrec_mode works fine on the SD400 (#1 aka MODE_P is the Manual mode, as usual on the Ixus cameras)

And what is mode #2? "M" mode with custom exposure (1..15 s)?

[reyalp]

Propcase->mode translation function doesn't probably need to be available to script writers (get_shooting_mode will just need to go through the modemap and return the CHDK mode number usable for set_shooting_mode), as long as it doesn't crash when modemap is buggy or incomplete?

No, it wouldn't crash. There are some quirks though:
For example, I noted on SD990 that:

Setting the DP button as a shortcut to movie in canon menu gives a value of (current mode)+1024 while movie is recording, unless already in movie mode

I assume other cameras with a movie button do something similar.

In sx10 and sx1 we also have

Code: [Select]

{ MODE_VIDEO_STD,          2597   }, // video standby
{ MODE_VIDEO_STD,          3622   }, // video in progress
If set_capture_mode and get_capture_mode work in CHDK values, they have to deal with these somehow. Currently mod_get will just return 0 for the mode portion if the mode isn't in the map.

Buggy modemaps don't really worry me that much, fixing those has been on the todo list for ages and this thing ought to make that finally more or less happen. Or do you think there's physical danger in switching to incorrect modes on some cameras?

Only a crash at worst, I assume. In any case, I think most are fixed now. Some of the ones I thought were broken were the old cameras (like ixus40) that actually do use 1-n as mode values.

[mattkime]

I've added a650 info to the dial propcase values page. it seems that page needs to be reorganized if there is going to be so much variation between modes and values. i was thinking of putting everything into one table.

i can confirm that set_record and set_capture_mode work on the a650.

thanks!

[fe50]

And what is mode #2? "M" mode with custom exposure (1..15 s)?

Sorry ewavr, missed your post 

Yes, mode #2 seem to be M mode with "Long shutter" (not available from the Canon menu on the SD400);
the exposure in this mode #2 is 1", also shown on the Canon OSD.

[ewavr]

Yes, mode #2 seem to be M mode with "Long shutter" (not available from the Canon menu on the SD400);
the exposure in this mode #2 is 1", also shown on the Canon OSD.

According to ixus50 (russian) manual, this mode must be actviated from camera main menu (in 'M' mode). Exposure can be set from exposure compensation submenu by pressing 'menu' button. This is true for ixus700, but I don't have access to ixus50...

[fe50]

According to ixus50 (russian) manual, this mode must be actviated from camera main menu (in 'M' mode). Exposure can be set from exposure compensation submenu by pressing 'menu' button. This is true for ixus700, but I don't have access to ixus50...

Yes, correct, it must be enabled first with "Long Shutter" from the Canon menu.

[ewavr]

Is there a way to mask(disable/enable) some logical events (especially playback<->record switching)?
p.s. Built-in forum search cannot find "post_levent_to_ui". Very strange.

[reyalp]

Is there a way to mask(disable/enable) some logical events (especially playback<->record switching)?
p.s. Built-in forum search cannot find "post_levent_to_ui". Very strange.

You might experiment with set_levent_active. It seems to stop mode dial change events generated by the physical dial from being posted.

[reyalp]

done

[fudgey]

done

Holy awesomeness! 

[ewavr]

You might experiment with set_levent_active. It seems to stop mode dial change events generated by the physical dial from being posted.

Without success 

And about modemaps:
How about "C" ("C1", "C2") mode? Its value cannot be detected using propertycase browser (because it is disguised as one of other mode), but this mode can be set using lua set_capture_mode(_canon).
For example, for SX10 set_capture_mode_canon(8225) sets "C" mode.

[reyalp]

You might experiment with set_levent_active. It seems to stop mode dial change events generated by the physical dial from being posted.

Without success  

And about modemaps:
How about "C" ("C1", "C2") mode? Its value cannot be detected using propertycase browser (because it is disguised as one of other mode), but this mode can be set using lua set_capture_mode(_canon).
For example, for SX10 set_capture_mode_canon(8225) sets "C" mode.

I guess you can find the propcase value by using the event method of setting mode  (or looking at the table in ROM you mentioned) ?

We can add any that are useful and known to work to the CHDK modemap IMO.

If someone comes up with an automatic way to find the canon mode table on all cameras, maybe we can use that, but I'm not in a hurry to touch every camera again

Do all the modes in that list seem to be fully functional ? On a540, they are all known in the modemap already, no "hidden" modes.

edit:
on a540 this canon mode list is at FFD588D4, on sd990 it's at FFB49820

Another thing: not all possible PROPCASE_SHOOTING_MODE values are in there, for example, sx10 has
   { MODE_VIDEO_STD,          3622   }, // video in progress
which doesn't appear in the list, and SD990 adds 1024 to the mode value if you use the DP button to start video recording.

[ewavr]

At least we can verify modes map for some cameras ported by careless people  

ixus65:

static const CapturemodeMap modemap[] = {
    { MODE_AUTO,               6  },
    { MODE_P,                  1  },
    { MODE_TV,                 3  },  //?
    { MODE_AV,                 2  },  // ?
....

ROM:FF973AD4                 DCW 32774  
ROM:FF973AD6                 DCW 32772
ROM:FF973AD8                 DCW 33288
ROM:FF973ADA                 DCW 33290

P.S. It seems that modes map from a610 (with MODE_AUTO=6 also incorrectly copied to a630(0xFFD682D0), a640, ixus izoom