EOS M3 porting [M3] [EOS_M3]

c_joerg

srsa_4c
Can you get the displaytype in following cases (you can try rec & play mode, but they might be the same):
- LCD mode
- EVF mode
- HDMI mode

LCD => 10
EVF => 11
HDMI => 6
rec & play is the same...

srsa_4c

c_joerg
LCD => 10
EVF => 11
HDMI => 6
rec & play is the same...

Thanks. Try replacing update_screen_dimensions() in the port's lib.c with this:

void update_screen_dimensions() {
    // see sub_FC177FCA in 101a, sub_FC1780F2 in 120f for the values
    extern int displaytype;
    static int old_displaytype = -1;

    if (old_displaytype == displaytype) {
        return;
    }
    old_displaytype = displaytype;
    
    switch(displaytype) {
        case 0:
        case 3:
        case 4:
        case 5:
            // ?
            camera_screen.width = camera_screen.physical_width = camera_screen.buffer_width = 640;
            camera_screen.height = camera_screen.buffer_height = 480;
            camera_screen.size = camera_screen.buffer_size = 640*480;
            break;
        case 1:
        case 2:
        case 8:
        case 9:
            // tv-out (not implemented in hw)
            camera_screen.physical_width = camera_screen.width = 720;
            camera_screen.buffer_width = 736;
            camera_screen.height = camera_screen.buffer_height = 480;
            camera_screen.size = 720*480;
            camera_screen.buffer_size = 736*480;
            break;
        case 6:
        case 7:
            // hdmi
            camera_screen.width = camera_screen.physical_width = camera_screen.buffer_width = 960;
            camera_screen.height = camera_screen.buffer_height = 540;
            camera_screen.size = camera_screen.buffer_size = 960*540;
            break;
        case 10:
            // lcd
            camera_screen.physical_width = camera_screen.width = 720;
            camera_screen.buffer_width = 736;
            camera_screen.height = camera_screen.buffer_height = 480;
            camera_screen.size = 720*480;
            camera_screen.buffer_size = 736*480;
            break;
        case 11:
            // evf
            camera_screen.width = camera_screen.physical_width = camera_screen.buffer_width = 1024;
            camera_screen.height = camera_screen.buffer_height = 768;
            camera_screen.size = camera_screen.buffer_size = 1024*768;
            break;
    }
}

The values seem to be the same on both supported firmwares.

Side note: I think the overlay won't be 100% correct on hdmi/evf. I have a corrected version for my cameras somewhere, but did not check it in because some parts of CHDK (zebra?) can't handle high resolution.

c_joerg

srsa_4c
Try replacing update_screen_dimensions() in the port's lib.c with this:

I have not compiled CHDK yet but I guess I have to follow this:
https://chdk.fandom.com/wiki/CHDK-Shell

msl

The CHDK Shell is outdated and will not work anymore.

Try this: https://chdk.setepontos.com/d/12752 or http://forum.chdk-treff.de/viewtopic.php?f=7&t=3512

Program GUI => https://chdkde.app.box.com/s/kj6qz4rbio/file/365176816120

Use GCC 4.9.3 => https://chdkde.app.box.com/s/kj6qz4rbio/file/413803707369

msl

srsa_4c

c_joerg
I have not compiled CHDK yet

Oh. I thought you already made that step.
The file you need to edit is platform/m3/lib.c .

c_joerg

srsa_4c

c_joerg
I have not compiled CHDK yet
Oh. I thought you already made that step.
The file you need to edit is platform/m3/lib.c .

Not yet...
The number of my posts here belies my abilities 😉

c_joerg

srsa_4c
Try replacing update_screen_dimensions() in the port's lib.c with this:

It works very well 😀 😀 😀
thanks for supportâ€¦

srsa_4c

c_joerg
It works very well 😀 😀 😀
thanks for supportâ€¦

Glad to see it worked. I'll try to dig up my corrections and see if the menu size / off-center help screen issue can be improved.

c_joerg

I was wondering why the EVF has a different aspect ratio than the screen. Probably it is because cameras with different aspect ratio use the EVF (G1xII with 4: 3). I find it interesting that you can also use the area.

Why is the memory bar actually in the middle at the EVF? Presumably it is set with an absolute number of pixels from topâ€¦

pigeonhill

Looking to up my Lua scripting experience with the EOSM family.

I already have three EOSMs running ML: one for normal use with a cage and a handle; one IR converted; and one I use with a 645 back and 35mm 645 lens, ie sensor bracketing.

Apart from the EOSM2, the ML community are unlikely to be releasing other EOSMx cameras, ie because of the Digic class, so I thought I might look at a second hand EOSM3 and CHDK.

Could a kind EOSM3 user give me an update on where the EOSM3 CHDK rests at the moment, ie are things stable and is Lua accessible etc.

c_joerg

pigeonhill
Looking to up my Lua scripting experience with the EOSM family.
Could a kind EOSM3 user give me an update on where the EOSM3 CHDK rests at the moment, ie are things stable and is Lua accessible etc.

All my lua scripts are very stable on the EOS M3. I basically use them for time lapse. But also Focus Stacking works quite well

pigeonhill

@c_joerg

Many thanks for the confirmation.

BTW do know if CHDK Lua can drive the EOSM focus motors?

c_joerg

pigeonhill
BTW do know if CHDK Lua can drive the EOSM focus motors?

Do you mean EFM lens? Yes
https://chdk.setepontos.com/d/13756

pigeonhill

@c_joerg

Fantastic!
Just purchased an M3 on Camera Jungle 😀
It's good to know you are an M3 user 😉
Looking forward to scripting some of my 'stuff' on the M3, ie focus stacking script.
Cheers
Garry

pigeonhill

@c_joerg

Have taken a look at your script that logs the EOSM3 focus steps using call_event_proc("EFLensCom.MoveFocus",steps,speed): thanks for sharing.

While I wait for my â€˜newâ€™ M3 to arrive, I have a question that I hope you can answer.

I have not attempted to use call_event_proc("EFLensCom.MoveFocus",steps,speed) before, ie with my G7X or G1X; I wonder if using this proc call would be a better approach to controlling focus position than using set_focus(x). What do you think?

Also, do I assume the standard set_focus(x) works on the M3?

Hope you can throw some education my way 😉

Cheers

Garry

c_joerg

pigeonhill
I have not attempted to use call_event_proc("EFLensCom.MoveFocus",steps,speed) before, ie with my G7X or G1X; I wonder if using this proc call would be a better approach to controlling focus position than using set_focus(x). What do you think?

call_event_proc work only on EOS M, set_focus only on P&S cams.

The problem with call_event_proc is that you can not enter absolute distances.

The only distance information which you have is Focus Distance Upper und Lower in some very inaccurate steps.

Download M3M10_Focus.lua at Reply #30.

I'm also not quite clear what impact the speed has.

pigeonhill
Also, do I assume the standard set_focus(x) works on the M3?

pigeonhill

@c_joerg

Many thanks for the info.

Looks like I need to start learning how to use call_event_proc("EFLensCom.MoveFocus",steps,speed) to move the lens to a specified position that I calculate.

Cheers

Garry

c_joerg

pigeonhill
Looks like I need to start learning how to use call_event_proc("EFLensCom.MoveFocus",steps,speed) to move the lens to a specified position that I calculate.

I'm currently driving the focus manually to a specific position and then just moving a few steps forward for stacking. Ultimately, the interface to the EF lenses would have to be the same with an DSLR as with an EOS M. Everything that is possible with ML should also be possible with CHDK.

pigeonhill

@c_joerg

Thanks.

Iâ€™m assuming when calling call_event_proc("EFLensCom.MoveFocus",steps,speed) one can use positive and negative steps?

Also, what is the impact of using speed?

Also, when I looked at your tables for the 11-22 at 11mm, the data seem to indicate that there was no real advantage between using 1 or 10 steps, as the focus hadnâ€™t moved when using multiple 10 steps. Or is it that the focus does actually change and only the reporting (upper and lower) remains fixed.

If the focus really does change, then using step = 1 should allow fine focus control.

Or am I expecting too much?

c_joerg

pigeonhill
Iâ€™m assuming when calling call_event_proc("EFLensCom.MoveFocus",steps,speed) one can use positive and negative steps?

Yes.
You can also use call_event_proc("EFLensCom.FocusSearchFar") and call_event_proc("EFLensCom.FocusSearchNear")

pigeonhillAlso, what is the impact of using speed?

I donâ€™t know. May be you lose steps if the speed is to high-

pigeonhillAlso, when I looked at your tables for the 11-22 at 11mm, the data seem to indicate that there was no real advantage between using 1 or 10 steps, as the focus hadnâ€™t moved when using multiple 10 steps. Or is it that the focus does actually change and only the reporting (upper and lower) remains fixed.

The real focus changes with every step, but not the distance information.

pigeonhillIf the focus really does change, then using step = 1 should allow fine focus control.

Yes the focus changes with every stepâ€¦

« Previous Page Next Page »