Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - garry23

Pages: [1] 2 3 ... 9
As I use ML in the technique, some may be interested in my latest bit of fun:

General Help Q&A / Auto Bracketing and highlights
« on: January 01, 2018, 07:06:34 PM »
I have a use case where I was hoping the auto bracketing would help.

Namely, set the exposure for the shadow capture and let the auto bracketing capture the highlights.

The scene has a high dynamic range and very bright light sources, which seem to create problems.

The problem I'm facing is that the auto bracketing stops short of addressing the very bright highlight, ie it is over exposed in that area in RAW.

Here is a zoomed in JPEG from LR:

The auto bracketing does not have any settings, like ETTR, I'm wondering if it would be helpful to give the user some control in the auto bracketing, eg how many stops to keep going after the ML algorithm thinks its finished.



Hardware and Accessories / Irix 11mm
« on: December 28, 2017, 12:11:20 PM »
Santa delivered this year and I'm now the proud owner of an Irix F/4 11mm Blackstone lens.

This lens has the widest FOV with the lowest distortion of any lens I'm aware of.

In case anyone is interested in this lens, I've posted a few insights on my blog:

Scripting Corner / Script UI
« on: December 19, 2017, 11:06:28 AM »
I'm writing this short post in the spirit of passing on my humble learning, in order to help others trying to script.

As 'the ML gurus' know I am far from a scripting expert, nevertheless, through a lot of experimentation, and guru support, I've picked up enough to 'get by' in scripting.

BTW I noticed lately a few 'negative' or 'curt' comments appearing on the forum, and this saddens me; as 'the gurus' give their time freely and people like me have a lot to learn from them. I hope others posting respect the hardwork of 'the gurus'.

As for the reason to post this entry, it was to feedback that scripting is all well and good,  ie getting the syntax and 'equations' right; however, a good script can be let down by a poor/weak User Interface (UI): which I think covers: usability and user experience.

Having now reached the 'script and maths' is right stage, I realized my two main scripts (The Focus Bar and The Toggler) were letting themselves down wrt their UI.

Of course I can only talk about this through my (old) eyes and how my brain works, but I was clear to me (pun intended) that the UI needed attention. For example, font size and font colours (foreground and background), plus message positioning.

I've therefore attempted to get a 'better' user experience and welcome any feedback on what I've tried to do.

The Toggler is at

The Focus Bar is at

Tutorials and Creative Uses / Extreme non-macro focus stacking
« on: December 13, 2017, 05:59:06 PM »
As I've spoken a lot about the technical side of my Focus Bar, ie using blur info, I thought I would give a simple demonstration.

In this case how the focus bar helped me capture a 12 image non-macro focus bracket set:

Scripting Q&A / Script termination
« on: December 11, 2017, 10:04:08 AM »
Hope someone can educate me.

At the moment one of my scripts, on loading for the first time, uses an IF-THEN-ELSE, which first detects that a lens is AF capable, and if it is it carries on with the script, ie loading variables, menus and function.

If the lens is not an AF one, the script simply shows a console message and does nothing else.

This means I need to put the main part of my script in the (main) IF-THEN-ELSE, like this:

Code: [Select]
IF test-true THEN
carry on with main script

Is there a way to put a test, up front in a script, that checks things and then doesn't load the script?



PS having been prompted by @dmilligan, I hope this is an X question, rather than a Y one  ;)

Scripting Q&A / Menu hidden query
« on: December 10, 2017, 11:03:55 AM »
@dmilligan @anyone

I wish to hide a menu item from users and am using the following:

Code: [Select]
            name = "update",
            help = "Not under user control",
            choices = {CON,COFF},
            value = COFF, -- start up default
            hidden = true

However, the menu item, ie update, remains shown.

Any ideas where I'm going wrong.



Scripting API suggestions / Menu Changed Property Handler
« on: December 09, 2017, 12:43:21 PM »
Use Case: look out for changes in a specific named menu or sub-menu.

Why: one script changes the state of another and this needs to be detected.

Suggested format: extend lua module property to handle the 'ML side' of life or even an event handler.

Scripting Q&A / Script state at camera switch off
« on: December 07, 2017, 07:53:10 PM »
Although I have picked up a bit of scripting knowledge, thanks to the help I've received on the ML Forum, the one area I'm weak in is io.

For example, what is the easiest/simplest way to have my script's 'state', ie as set in the script's menus, recorded like the menu states in the ML core, ie at camera switch off. So my script starts in the same configuration as I left it at camera switch off, rather than a hard coded state.

I would welcome some hints or pointers.



Scripting Corner / New version of Toggler
« on: December 05, 2017, 04:15:51 PM »
Just in case anyone else has found my Toggler script useful, here is an update that works with the latest Lua-fix nightly (Latest Build (2017-12-03 22:09)).

Although I wrote the Toggler for the EOSM, which is lean on buttons, the Toggler should work on other cameras using the Build above.

You can download Toggler from here:

Why use Toggler?

If you find yourself switching ML states a lot, then Toggler could help.

The script you download is configured to use the PLAY, INFO and MENU buttons:
 [MENU] = normal use of [MENU] if not in imode (interactive mode)
 [INFO] = normal use of [INFO] in not in imode
 [PLAY][PLAY] = normal use of [PLAY]
 [PLAY][MENU] = enter Toggler interactive mode
 In imode [PLAY] and [INFO] will toggle back and forwards through your ML condition states giving you an on-screen message
 In imode [MENU] will set that condition and leave interactive mode.
 In imode pressing any other key, eg [SET] (not [MENU], [INFO] or [PLAY]) will leave interactive mode

You can change the script to use other button combinations, ie that work better on your camera (the 'default' ones work well on the EOSM).

The script, as I've written it for my use, allows me to switch my Focus Bar on and off, switch the FB stacking mode on and off, open the ML menu, switch on ETTR or Auto-Bracketing and the list goes on.

As usual I welcome feedback, especially to make the Toggler idea better and make my coding better  ;)

Scripting API suggestions / ML Menu open()
« on: December 05, 2017, 03:34:02 PM »
We have close() to close the ML menu, but unless I've missed it, we don't have open(), ie to open the ML menu from a script.

On the next Lua fix update it would be great to see this feature.



Scripting Q&A / Loading scripts in order
« on: December 03, 2017, 10:52:30 AM »
I am running two EOSMs with two identical scripts.

But they respond differently and I believe it to be how the scripts are loaded, as I'm using keypress event handlers in both scripts.

On one camera script A is listed first and on the other script B.

Is there a simple way to ensure which scripts load first?



Scripting Q&A / Menu Interactions
« on: December 02, 2017, 09:36:27 AM »
I have two scripts running and I need to get one script interacting with another.

What I have tried, but it doesn't seem to work, is to simply get one script to change the menu settings of the other script. But nothing seems to happen.

Here is the code in one script, with Focus Bar being the ML menu created by the other script:

Code: [Select]
        if menu.get("Focus Bar","Focus Bar") == "ON" then
            menu.set("Focus Bar","Focus Bar","OFF")
        elseif menu.get("Focus Bar","Focus Bar") == "OFF" then
            menu.set("Focus Bar","Focus Bar","ON")

Is the problem that Lua can't change a script created ML Menu?



General Chat / Cage for EOSM
« on: December 01, 2017, 02:46:41 PM »
For those interested in what you can do with an EOSM, you may be interested in my lasted post:

General Help Q&A / 'New' EOSM Help!
« on: November 30, 2017, 06:38:45 PM »
Ok I know I'm sometimes stupid, but I'm at a loss.

Just got another EOSM and I've reset all camera settings, tried different lens and with and without ML card the focus distance remains fixed on one number.

Does anyone have any ideas, ie seen this before?



Scripting API suggestions / Lua Properties: additional property request
« on: November 28, 2017, 11:21:23 PM »
Using Lua property one can 'detect' changes in the shutter, aperture and ISO.

Could we also add a property to detect changes to focus distance and focal length?



Feature Requests / Mirror Lock-up
« on: November 16, 2017, 06:02:42 PM »
Currently we can control Mirror lock-up in two ways.

Always on responds as per Canon, i.e. Two shutter presses, with the first 'just' moving the mirror.

The second being a delay when using the intervalometer.

Some other cameras allow the shooter to select a delay between the mirror going up and the shutter activating; thus reducing mirror vibration issues when not in LV mode. 

So a thought. Can we introduce a user selectable delay in the ML mirror menu, say in 1/10 sec up to 1sec.

And/or bring in mirror control in Lua, unless it's there and I've missed it. My idea being, via the shutter property and/or keypress event, control the mirror and shutter through Lua.

@A1ex or anyone

I'm trying to make use of a long halfshutter and need to differentiate it from a LV AF action.

I thought I could use the Lua property handler, eg accessing LV_FOCUS_STATE or another LV_FOCUS property, ie to handle the AF condition.

But the LV_FOCUS property handler always seems to return 0.

Does this mean it is not yet exposed in Lua?



General Help Q&A / Help: EOSM Aperture/Exposure button
« on: November 03, 2017, 07:36:31 PM »
I've pulled my hair out all afternoon.

I have two EOSMs and one, all of a sudden, exhibited a strange behavior: the Aperture/Exposure button stopped functioning, ie I could not use it as a right toggle in menus (ML or Canon) and could not toggle between aperture and shutter.

I've tried different lens: no difference.

I've removed ML, via firmware reset: no difference.

Has anyone else had a similar problem and fixed it!



I have a script that draws to the screen and all is well, until I switch to Canon menus, eg INFO or MENU.

I'm detecting these screens via a property change, ie:

Code: [Select]
function property.GUI_STATE:handler(value)
    if value == 1 then
        fb_dirty = true
        fb_dirty = false

Both MENU and INFO return the value 1.

The issue I have is how to decouple me not (sic) drawing and the Canon side drawing MENU or INFO screens.

Has anyone worked out how to manage the Lua and Canon side graphics? That is cleanly doing one or the other.

Scripting API suggestions / [DONE - console.visible] Lua Console question
« on: October 30, 2017, 10:10:06 PM »
@A1ex or anyone

Is there a way to detect that the console is not showing, eg the start-up screen has finished.

General Help Q&A / 50mm strangeness
« on: October 09, 2017, 04:50:33 PM »
I just had a strange occurrence when using my 50mm 1.8 II, with my 5D3.

All my lenses work with my focus bar script, however, the 50mm generates an Err 70.

If I switch off my script all is OK.

Here is the CRASH LOG.

Code: [Select]
ASSERT: hLvJob->hJpegMemSuite
at ./Epp/Vram/VramStage.c:891, task Epp
lv:1 mode:3

Magic Lantern version : lua_fix.2017May01.5D3123
Mercurial changeset   : ea6d752aee38+744f5868a308+ (lua_fix) tip
Built on 2017-05-01 16:16:09 UTC by [email protected]
Free Memory  : 130K + 3399K

Does anyone have any ideas?



Scripting API suggestions / Display interactions
« on: September 28, 2017, 07:59:26 PM »

Hope you can help.

In my focus bar script I'm writing text to the screen then, when not required, erasing.

I erase by simply overwriting in the transparent color.

Unfortunately this negatively interactions with ML drawing, eg the spot meter.

Is there a way to deal with this, ie after I've erased then ML, eg the spotmeter, doesn't know I was writing at that point.

Hope this s clear.



General Help Q&A / Focus Distance
« on: September 25, 2017, 09:51:26 AM »

When I get a chance I will attempt to measure this myself, but until then, does anyone know th reference plane for the focus distance reporting?

That is the sensor or the lens principal plane?

I know it won't make that much difference in calculating depth of field etc, but I'm being picky ;-)



Scripting Corner / Documentation API
« on: September 10, 2017, 05:48:19 PM »
Don't know if anyone else has noticed, but the Lua API documentation is broken.

Pages: [1] 2 3 ... 9