EOS M3 porting

pigeonhill

Re: EOS M3 porting

« Reply #600 on: 24 / July / 2019, 02:54:53 »

Advertisements

@c_joerg

ML call is this

focus(num_steps[, step_size=2[, wait=true[, delay]]])
Moves the focus motor a specified number of steps.
Only works in LiveView.
Parameters:

num_steps int How many steps to move the focus motor (signed).
step_size int Allowed values: 1, 2 or 3.
Step 1 may give finer movements, but may get stuck or may be very slow on some lenses. (default 2)
wait bool Wait until each focus command finishes, before queueing others.
wait=false may give smoother movements, but may no longer return accurate status for each command, and is known to crash on some cameras. The exact behavior may be camera- or lens-dependent.
Do not disable it without a good reason! (default true)
delay int Delay between focus commands (ms)
With wait=true, the delay is after each focus command is executed (as reported by Canon firmware).
With wait=false, the delay is after each focus command is started (without waiting for it to finish).
(default 0 if wait=true, 30ms if wait=false)
(optional)
Returns:

bool whether the operation was successful or not.

Logged

pigeonhill

Re: EOS M3 porting

« Reply #601 on: 27 / July / 2019, 14:13:49 »

This is a beta release of a simple landscape focus and exposure bracketing script for the M3.
The script makes use of the thin lens equation.
Exposure bracketing is based on the Zero Nose strategy, ie the ETTR base exposure plus a ZN exposure at, say, 2Ev or 3Ev or 4Ev from the base.
Focus stacking can be based on two strategies: from the current position or from focus minimum.
You can selected a dark frame bookend.
You can decide to switch the screen off.
You can select the overlap blur in microns.
Finally, you can select the infinity focus, ie at 2-3 times H.
The beta release can be found here: https://gist.github.com/pigeonhill/cdf25239bae6a4343e6431fb4c10c849

« Last Edit: 27 / July / 2019, 14:39:24 by pigeonhill »

Logged

pigeonhill

Re: EOS M3 porting

« Reply #602 on: 03 / August / 2019, 01:50:49 »

In case someone is using my M3 focus and exposure bracketing script: here is an update
https://gist.github.com/pigeonhill/cdf25239bae6a4343e6431fb4c10c849

Logged

pigeonhill

Re: EOS M3 porting

« Reply #603 on: 05 / August / 2019, 15:29:42 »

Another update

This time I've added in a split, thin lens model, which better handles bracketing from close up.

For instance the minimum focus distance on the 11-22mm is 150mm, which is measured from the sensor.

All depth of field distances, on the other hand, are measured from the front principal plane, which we don't know

The split thin lens approach attempts to address tis, ie see here: http://photography.grayheron.net/2019/05/splitting-things-apart.html

To add your lens, simply run the script to get the lens name, then add the required info to the script.

The latest version is, as usual, here: https://gist.github.com/pigeonhill/cdf25239bae6a4343e6431fb4c10c849

Logged

reyalp

12200

Re: EOS M3 porting

« Reply #604 on: 05 / August / 2019, 16:01:00 »

Quote from: pigeonhill on 05 / August / 2019, 15:29:42

To add your lens, simply run the script to get the lens name, then add the required info to the script.

Note the lens name function address is only valid for firmware 120f.

The corresponding function for firmware 101a is fc2f3fc3

In general, any firmware address (other than memory mapped hardware addresses like frame buffers, LED control etc) should be assumed to be firmware specific unless confirmed otherwise from disassembly or testing.

Also FYI, error() in Lua terminates execution of the script, so there's no need to also return.

Logged

Don't forget what the H stands for.