Messages

@dmilligan

Thanks for the hint and I've tried it two ways: but no luck :-(

Code Select Expand

-- Test Script

require('keys')


function main()
    keys:start()
menu.block(true)
  while menu.visible do
task.yield(100)
local key = keys:getkey()
-- task.yield(100) - tried it here as well
if key == KEY.RATE then camera.shoot() end
  end

-- quit script
    menu.block(false)
    keys:stop()
end

keymenu = menu.new
{
    parent = "Audio",
    name = "Shoot",
    help = "Simply operates shutter",
    select = function(this) task.create(main) end,
}

BTW this is why it would be helpful for someone in the know, to help kickstart the rest of us in the art of scripting.

I had looked at the Pong example and it didn't have the task.yield(100) business.

I truly am not looking for personal help as I know everyone is busy.

As I said, I'll just wait until a few more post their scripts and adapt anything I see useful to my project.

Cheers

Garry

Yes...of course :-)

I've read and reread then many times.

I feel my weakest understanding is the basic syntax, ie how do you get DoF or move the lens etc.

I'll get there :-)

Cheers

Garry

Ok, I jumped in and tried adapting Walter's script. The function of the script is simply to take an image. But I can't seem to get it to work.

I hope some kind expert can nudge me in the right direction, as once I get this core script running, I feel I can make progress on more complex scripting.

Code Select Expand

-- Test Script

require('keys')

function main()
    keys:start()
menu.block(true)
  while menu.visible do
local key = keys:getkey()
if key == KEY.RATE then camera.shoot() end
  end

-- quit script
    menu.block(false)
    keys:stop()
end

keymenu = menu.new
{
    parent = "Audio",
    name = "Shoot",
    help = "Simply operates shutter",
    select = function(this) task.create(main) end,
}

Walter

Thanks for posting this as it helps people like me, who are keen to start scripting, but, bluntly not programmers and don't know Lua syntax etc.

The more people like me can see others' scripts, the quicker we will be able to write our own scripts.

It truly would be fantastic is someone could write a simple (couple of pages) ML-focused intro to Lua scripting, ie showing how to do all the 'common' things we will be looking to do, eg: set up menu, get focus position, change exposure, move lens focus, take an image, drive other ML functionality from within a script, eg set ETTR etc etc.

Once again: thanks for posting and I hope others do as well.

Cheers

Garry

@axelcine

Sorry, quite the opposite.

Macro bracketing is easy and already built into ML.

Macro bracketing is simply repeating a fixed lens refocus multiple times.

Landscape focus bracketing requires a little more programming :-)

Cheers

Garry

@dbalex

I, like many I'm sure, would welcome you publishing your progress. In fact I would welcome anyone publishing their experience with lua, especially 'doing' image capture.

I'm not a programmer but I'm good at bootstraping off others :-)

My project is to write an auto bracketing script that covers the entire DoF.

Cheers

Garry

There are many great tutorials on line for you to read and watch.

As for ML and focus stacking in landscape space, ie not macro, this post of mine may help: http://photography.grayheron.net/2015/06/could-this-be-optimum-focus-stacking.html

Matthew

I've written about my landscape stacking experiments, eg here: http://photography.grayheron.net/2015/05/magic-tweak.html

I have been waiting for the Lua scripting to become accessible to me, as I have a workflow for landscape focus stacking, which completely different to macro ficus stacking.

What I do is switch of diffraction corrected DoF, must use a lens that reports duistance etc, and manually focus to the nearest 'slice' of focus. Note the far DoF distance and refocus the near DoF to this, i.e. so it slightly overlaps. Keep repeating until the far DoF is infinity.

It should be simple to write a script to do this, i.e. step the lens through the sequence.

The above is different to macro stacking, where you repeat the same focus increment each time.

As I say, I'm waiting to personally be able to use the Lua scripting engine.

@NickZee

I'm sure others will add further comments, however, from what you have posted it looks normal to me. Remember what dual ISO is. Think of it as a 'normal' exposure interlaced with an over exposed one. This is why the interlaced looks over exposed. The Dual ISO capture should only be seen as a 'data gathering' stage, ie don't try and assess it from a quality perspective.

It is thus usual to have to boost the exposure and/or shadows in post and play around with whites/blacks, and of course noise reduction.

I personally use the ETTR + Dual ISO as a killer combination for still photography, ie I don't touch video.

BTW I have written about my ML experiences on my blog, which you are welcome to scan at photography.grayheron.net. Please note I write this blog for personal enjoyment and accept it is not always the best view of ML or photography :-)

Just a quick inquiry regarding progress.

Like many I'm eager to experiment with scripting, but I'm not adept enough at compiling my own (5D3-113 and 50D).

Could I politely ask if there will be any chance of seeing Lua scripting in the nightlies any time soon?

Cheers

Garry

Kris

Like you I'm always looking for the optimum ML workflow.

When bracketing I use the ML raw spotmeter set to Ev mode. This gives me optimum exposure metering to ensure the darkest area is metered perfectly.  I then simply use auto ETTR to capture the required brackets.

BTW I written about my ML experiments here: http://photography.grayheron.net

I believe the above achieves what you are trying to do, i.e. Full ETTL to ETTR coverage.

If you haven't looked at them: try these video tutorials.

http://lrtimelapse.com/tutorial/

@swinxx

Although I don't 'do' videography, I do use variable NDs, but to 'correct' for their weakness when used in the front of a lens, I, instead, use a variable at the rear of a lens.

This short post will explain: http://photography.grayheron.net/2015/06/further-le-experiments.html

@dfort

I think the question I had in my mind is, with Cygwin/MinGW-64 approach are you provided a tool to change code.

That is, can I access the ML code and the parsing etc is handled correctly?

One final thought is that if someone is using this approach: would they be able to video a demo for us non-coders who are trying to get into all this 'coding stuff'.

Cheers

Garry

@dfort

I for one truly hope that this becomes a functioning toolset.

I played around with compiling in the cloud and created my own 'versions' of ML using this approach.

I personally believe this is the real value of being able to compile.

I haven't yet tried the Cygwin/MinGW-64 approach, but will do so once it is clearer how I can take the latest nightly, tweak or add to the code and then compile.

As I read the above, this isn't fully clear to me yet: and this is a criticism of me, not you :-)

I just got my new 15mm F/4 1:1 Macro lens from Venus Lens and thought some of you may be interested in my early experiments, as I use ML to set the exposure and grab the (auto) brackets.

http://photography.grayheron.net/2015/09/further-experiments-in-wide-angle-macro.html

Sorry: I don't 'muck about' with video ;-)

@beauchampy

I'm 'only' a stills photographer, but have settled on using ETTR for most of my exposure setting, augmented by dual-ISO if the DR of the scene warrants it.

Following Clarke-Vision's advice, I'm careful about ETTRing and usually only do so at low ISOs.

For very high DRs I use the ML Ev Raw spotmeter to set the base zone/image on the dark area where I wish to see details, ie placing this at or around 0Ev, and then use auto bracketing to ensure the highlights are captured.

I have written about my ML experiences here: photography.grayheron.net

If you haven't read this, you may find this of value: http://www.clarkvision.com/articles/iso/

Only other thought is if you are also using ETTR,
As some times ETTR and dual will result in a dual with the same ISOs, eg 800/800.

This will. Of course, look like a non dual.

Look under the dual menu.

You can capture with dual as every other image, you may have this option selected?

@chadxo

All I can offer is to read through this link: http://www.magiclantern.fm/forum/index.php?topic=14725.0

I know this link has been posted before: but it represents good background.

http://learn.usa.canon.com/resources/articles/2011/af_microadjustment_article.shtml

You may wish to rerun your tests in RAW and with the ML Spot Ev meter.

Ev readings allow you to better link to camera settings, ie stops of change.