EOS M3 porting - page 39 - DryOS Development - CHDK Forum
« previous next »
Pages: 1 ... 34 35 36 37 38 [39] 40 41 42 43 44 ... 75   Go Down

EOS M3 porting

  • 746 Replies
  • 391080 Views
*

Offline lapser

  • *****
  • 1093
Re: EOS M3 porting
« Reply #380 on: 03 / July / 2017, 20:40:48 »
Advertisements
OK, I messed up. I guess I'm a little rusty after all this time! I was writing out of range sv values by mistake.

I changed props.SV to 354 and it worked for both exposure and exif. So the M3 propcase.SV should be changed to 354, like the G7.

But it's interesting that changing propcase 256 would change the exposure but not the exif data. Changing propcase 354 with my script in continuous mode (I don't use set_iso) doesn't change propcase 256, so they end up with different values. That doesn't seem to be a problem.
Logged
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos
*

Offline reyalp

  • ******
  • 14079
Re: EOS M3 porting
« Reply #381 on: 03 / July / 2017, 21:08:47 »
Quote from: lapser on 03 / July / 2017, 20:40:48
But it's interesting that changing propcase 256 would change the exposure but not the exif data. Changing propcase 354 with my script in continuous mode (I don't use set_iso) doesn't change propcase 256, so they end up with different values. That doesn't seem to be a problem.
Remember the actual override is done by setting SV_MARKET to the ISO_BASE value and using DELTA_SV. Setting SV is (mostly?) just for the exif and ISO related calculations.

edit:
I checked this in, trunk r4842

If setting ISO out of range causes a crash, it should be limited with CAM_MIN_ISO_OVERRIDE and CAM_MAX_ISO_OVERRIDE. Obviously this only applies to script and CHDK menu overrides, setting propcases directly is not limited.
« Last Edit: 03 / July / 2017, 21:27:00 by reyalp »
Logged
Don't forget what the H stands for.
*

Offline lapser

  • *****
  • 1093
Re: EOS M3 porting
« Reply #382 on: 03 / July / 2017, 21:32:19 »
Quote from: reyalp on 03 / July / 2017, 21:08:47
Remember the actual override is done by setting SV_MARKET to the ISO_BASE value and using DELTA_SV. Setting SV is (mostly?) just for the exif and ISO related calculations.
That makes sense. So changing propcase SV to 354 should work.
Logged
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos
*

Offline c_joerg

  • *****
  • 1248
Re: EOS M3 porting
« Reply #383 on: 04 / July / 2017, 05:54:57 »
Quote from: reyalp on 03 / July / 2017, 21:08:47
I checked this in, trunk r4842

Is there any reason why EOS M3/M10 is not under autobuild?
Logged
M100 100a, M3 121a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd
*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #384 on: 04 / July / 2017, 11:19:27 »
Quote from: reyalp on 03 / July / 2017, 21:08:47
I checked this in, trunk r4842

https://app.assembla.com/spaces/chdk-m3/subversion/commits/35

I forgot to exclude propset9.h file during latest core update...  :)

Maybe it's better to move propset*.h file to platform folder, because most modern cameras have their unique propsets?

« Last Edit: 04 / July / 2017, 11:35:58 by Ant »
Logged
*

Offline reyalp

  • ******
  • 14079
Re: EOS M3 porting
« Reply #385 on: 04 / July / 2017, 14:32:49 »
Quote from: Ant on 04 / July / 2017, 11:19:27
Maybe it's better to move propset*.h file to platform folder, because most modern cameras have their unique propsets?
Are you volunteering to maintain >140 distinct propset.h files?  ;)

If Canon actually starts making them unique for every camera, we'll have to deal with that, but I'm not convinced that has happened. We've had few ports recently, so they are more spread out over canon versions. G7 X and M3 seem to use the same values in most cases (as one would expect from the same dryos rev) but differ due to the interchangeable lens specifics.

Quote from: c_joerg on 04 / July / 2017, 05:54:57
Is there any reason why EOS M3/M10 is not under autobuild?
The developers of these ports have not added them or requested they be added.
Logged
Don't forget what the H stands for.
*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #386 on: 04 / July / 2017, 15:33:14 »
Quote from: reyalp on 04 / July / 2017, 14:32:49
If Canon actually starts making them unique for every camera, we'll have to deal with that, but I'm not convinced that has happened.
In fact we have 5 propsets for a few Digic6 cameras and 5 propsets for all other 130+ cameras.

Quote
The developers of these ports have not added them or requested they be added.
Feel free to add them. :D
Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: EOS M3 porting
« Reply #387 on: 04 / July / 2017, 15:52:00 »
According to reports, propset10 (originally added for the M10) seems to work for the in-progress Ixus175 port (differences are not established yet).
The M10 port is not considered stable due to
- the unsolved override issue (also affecting the M3, IIRC)
- the ugly PTP + modeswitch bug, discovered by axman
Logged
*

Offline Ant

  • *****
  • 509
Re: EOS M3 porting
« Reply #388 on: 04 / July / 2017, 16:27:23 »
Quote from: srsa_4c on 04 / July / 2017, 15:52:00
- the unsolved override issue (also affecting the M3, IIRC)
At the moment I found a problem with Tv overriding: it works not so exactly.
Logged
*

Offline lapser

  • *****
  • 1093
Re: EOS M3 porting
« Reply #389 on: 05 / July / 2017, 15:00:26 »
Quote from: Ant on 04 / July / 2017, 16:27:23
Quote from: srsa_4c on 04 / July / 2017, 15:52:00
- the unsolved override issue (also affecting the M3, IIRC)
At the moment I found a problem with Tv overriding: it works not so exactly.
I noticed that too, in single shot mode. But it works perfectly in continuous mode.

In single shot, set_tv96_direct(tv) doesn't save tv into the propcases immediately. It waits until the camera is ready. Maybe the camera isn't ready all the time with the EOS M3? Maybe the camera sets the tv propcases in a different task. You could try putting in a short delay in set_tv96 right before it sets the tv propcases to see if that makes a difference.
Logged
EOS-M3_120f / SX50_100b / SX260_101a / G1X_100g / D20_100b
https://www.youtube.com/user/DrLapser/videos
Pages: 1 ... 34 35 36 37 38 [39] 40 41 42 43 44 ... 75   Go Up
« previous next »
 

Related Topics