EOS M3 porting

  • 311 Replies
  • 42205 Views
Re: EOS M3 porting
« Reply #290 on: 11 / February / 2017, 12:54:31 »
Advertisements
I’m missing the value from dof.focus on M3. Is this implemented yet?
It looks like that dof.focal_length and dof.eff_focal_length works fine.
The RAW EXIF includes Hyperfocal Distance and Focus Distance. I never notices this before.

There is some other interesting thing, which I found with
Code: [Select]
exiftool -h img_0001.cr2This is my first cam, with has time stamps with 1/100s resolution
Date/Time Original</td><td>2017:01:21 17:59:23.33
All my other cams have only 1s time stamps.
I also found a Camera Temperature. I was wondering, that the Camera Temperature was similar to optical Temperature and not to the sensor Temperature.

*

Offline Ant

  • ***
  • 213
Re: EOS M3 porting
« Reply #291 on: 11 / February / 2017, 13:24:51 »
I’m missing the value from dof.focus on M3. Is this implemented yet?

Most focus related features are not implemented yet.

Re: EOS M3 porting
« Reply #292 on: 14 / February / 2017, 11:57:00 »
Here is another thing I noticed at the M3.

Normally the aperture does not change between the shoots in rawopint (which is at least my other cameras so).

However, with the M3, the shutter is opened and closed with each shot. This is, however, only in single mode. This does not happen in the continuous mode. In continuous mode the aperture remains fixed in the set position.


Re: EOS M3 porting
« Reply #293 on: 15 / February / 2017, 02:51:38 »
Here is my first major run with the M3 and rawopint. I just held the camera against a monitor and played the following video:

/>
The video simply simulates the transition from day (255,255,255) to night (0,0,0) and vice versa in 35 minutes.

Basic data of the run:
Interval = 6s
Tv max = 3s
ISO min = 100
ISO max = 1600
EV shift -1EV (the m96 curve is not at 0 but at -96)

As you can see on the m96 curve, rawopint does exactly what you expect from it. In complete darkness there is, of course, an intrusion because at Tv = 3s and ISO = 1600 are not enough.

The run starts with Tv = 1/8s and ISO = 100. The algorithm then increases the exposure time to Tv = 3s. When the Tv = 3s is reached, the ISO value increases until finally it reaches the maximum value of ISO = 1600.
There are also no apparent abnormalities in the JPG. Interval and sleep also show no abnormalities.
Looks pretty perfect.  :) :) :)

I would like to thank all those who have made this possible. Good job.

By the use of the M3 (or M10) for time-lapse, one has now straight through the use of wide-angle objective completely new possibilities.


However, with the M3, the shutter is opened and closed with each shot. This is, however, only in single mode. This does not happen in the continuous mode. In continuous mode the aperture remains fixed in the set position.

Well, this could give you the chance, to make a “True Holy Grail” – 3-way auto ramping for time lapse transitions (Tv, ISO and Av).

https://lrtimelapse.com/tutorial/true-holy-grail-auto-ramping/



*

Online msl

  • *****
  • 1198
  • A720 IS, SX220 HS 1.01a
    • CHDK inside
Re: EOS M3 porting
« Reply #295 on: 18 / February / 2017, 09:57:55 »
Try the info button. This button is define as the display button in the CHDK source. And the display button is the alternative for cameras without zoom lever.

msl
German CHDK pages:  CHDK forum | CHDK inside | CHDK Twitter News by msl | Download CHDK-DE (Autobuild)
Note: SDM violates the GPL rules!

Re: EOS M3 porting
« Reply #296 on: 18 / February / 2017, 10:44:27 »
Try the info button. This button is define as the display button in the CHDK source. And the display button is the alternative for cameras without zoom lever.
It’s not the Info buttom. I tried it…
I tried every buttom again. It’s the ‘*’ buttom. I’m wondering, why I haven’t notice this before.

*

Online msl

  • *****
  • 1198
  • A720 IS, SX220 HS 1.01a
    • CHDK inside
Re: EOS M3 porting
« Reply #297 on: 18 / February / 2017, 11:01:14 »
I see it in the source code.

https://app.assembla.com/spaces/chdk/subversion/source/HEAD/trunk/platform/m3/kbd.c#ln21

AF lock => zoom out
AF adjust => zoom in

Not the right standard CHDK procedure, but a solution.

msl
German CHDK pages:  CHDK forum | CHDK inside | CHDK Twitter News by msl | Download CHDK-DE (Autobuild)
Note: SDM violates the GPL rules!



*

Offline Ant

  • ***
  • 213
Re: EOS M3 porting
« Reply #299 on: 22 / February / 2017, 08:51:29 »
IIRC you need to call function GetCameraInformationData. XML document will be found somewhere in RAM dump.

 

Related Topics