EOS M3 porting - page 8 - DryOS Development - CHDK Forum supplierdeeply

EOS M3 porting

  • 746 Replies
  • 401030 Views
*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #70 on: 25 / June / 2016, 16:16:20 »
Advertisements
I forgot about "_" prefix in function name - now corrected.

*

Offline reyalp

  • ******
  • 14089
Re: EOS M3 porting
« Reply #71 on: 25 / June / 2016, 16:17:27 »
Have you verified that propset 7 is correct for this cam?

There's some advice about propset verification in https://chdk.setepontos.com/index.php?topic=12418.msg127112#msg127112

Also note that propcase_shooting / get_shooting behavior is different in propset 7, see https://chdk.setepontos.com/index.php?topic=12692.msg126797#msg126797

If the propset is correct, this should work automatically with the workaround I added for g7x. If not, scripted shooting will probably not work right.
Don't forget what the H stands for.

*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #72 on: 25 / June / 2016, 16:24:52 »
Have you verified that propset 7 is correct for this cam?
Not yet, I guessed but scripts work...

*

Offline reyalp

  • ******
  • 14089
Re: EOS M3 porting
« Reply #73 on: 25 / June / 2016, 16:30:47 »
Have you verified that propset 7 is correct for this cam?
Not yet, I guessed but scripts work...
I'd suggest checking a few high and low number propcases manually, e.g. AV and TV

If those are right, then there's a high chance everything in between is OK.

Since this is the first interchangeable lens camera with CHDK support, checking the ones that depend on lens characteristics (like MIN_AV, OPTICAL_ZOOM_POSITION) would probably be a good idea.
Don't forget what the H stands for.


*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #74 on: 26 / June / 2016, 13:57:53 »
I checked some propsets - most of them are the same, but not all.
I shifted to the right numbers that I did not recognise.
« Last Edit: 26 / June / 2016, 14:58:42 by Ant »

*

Offline reyalp

  • ******
  • 14089
Re: EOS M3 porting
« Reply #75 on: 26 / June / 2016, 16:03:45 »
I checked some propsets - most of them are the same, but not all.
If any IDs have changed, then it needs to be a new propset.

It's pretty unusual for IDs to change, without shifting the following IDs. But I guess maybe we shouldn't be surprised if interchangeable lens is unusual...

Some comments

Quote
#define PROPCASE_BV                              4         // bracketing value?
BV is Apex Bv = brightness  value (in APEX*96 units). It should change depending on the absolute brightness of the scene.

Quote
#define PROPCASE_USER_AV                         29
On g7x both 30 and 29 contain the similar values. Does 30 NOT contain an Av value on EOS M3?

Quote
#define PROPCASE_SUBJECT_DIST2                      70         //
Should vary with focus distance

Quote
#define PROPCASE_DELTA_SV                        84         // TODO not certain
In canon auto ISO, DELTA_SV + SV_MARKET should equal the APEX96 value of displayed auto ISO value.

Quote
#define PROPCASE_SV_MARKET                       255
In manual ISO, should contain the APEX96 value of ISO setting.

Quote
#define PROPCASE_SV                                 354        // (philmoz, May 2011) - this value causes overrides to be saved in JPEG and shown on Canon OSD
In manual ISO, should contain the APEX96 value of current ISO, possibly offset by some constant from the MARKET value.

Quote
#define PROPCASE_TIMER_SHOTS                        384        // Number of shots for TIMER_MODE=Custom
Does the camera not allow you to set multiple shots in self timer mode?

Quote
#define PROPCASE_CUSTOM_BLUE                        182        // Canon Menu slide bar values: 255, 254, 0, 1, 2
...
These are for the "my colors" values, which I guess doesn't exist on M3? These are only information for scripts anyway.

Quote
#define PROPCASE_ORIENTATION_SENSOR                 228
Should be 0, 90, 270 depending on camera orientation

Quote
#define PROPCASE_OPTICAL_ZOOM_POSITION              204
Is there no propcase which changes with zoom position?
Don't forget what the H stands for.

*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #76 on: 28 / June / 2016, 14:36:21 »
Quote
Does 30 NOT contain an Av value on EOS M3?
30 contain not Av

Quote
Does the camera not allow you to set multiple shots in self timer mode?
I did not found this function/setup

Quote
Is there no propcase which changes with zoom position?
There is no one propcase which changes with zoom position.

Re: EOS M3 porting
« Reply #77 on: 04 / July / 2016, 23:13:58 »
Maybe check propset8.  I initially thought the sx60hs was 7, but it turned out it was 8.  Orientation sensor is a good one.


*

Offline reyalp

  • ******
  • 14089
Re: EOS M3 porting
« Reply #78 on: 07 / July / 2016, 00:14:01 »
Maybe check propset8.  I initially thought the sx60hs was 7, but it turned out it was 8.  Orientation sensor is a good one.
If the propcases ant listed as OK are correct, it can't be 8.

If things like focus mode, subject distance and zoom state don't exist as propcases, they will probably need to be faked something like I did for PROPCASE_SHOOTING on g7x.

Having them assigned to random unrelated IDs is likely to cause all kinds of problems. Ideally, a function or variable that returns and equivalent value should be used, but if one isn't found, a sane default can be returned.

The above only applies propcases that are actually required by the CHDK code. The stuff like the "My Colors" values are only there so they can referenced by name in Lua scripts, so not having them isn't a big deal. If they don't exist or aren't found, they should not be defined in propset.h though.
Don't forget what the H stands for.

*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #79 on: 07 / July / 2016, 00:35:00 »
Maybe check propset8. 
It is not 8.
Numbers that I did not recognise are shifted to the right.

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal