Messages

Sorry, been doing a bit of testing.

Tried 5D3 with two different cables to connect Cam to the Max X unit. 

Max X connects at 1080p24.

Tried cables on my EOS M to a monitor, and the HDMI out of the cam comes through ok, with or without ML being loaded, ie SET pressed at start up.

I've just got myself a Hollyland Mars X HDMI wireless transmitter to use with my photography, ie not videography, ie as an experiment, having convinced myself it will work.

https://www.hollyland-tech.com/products/detail-39.html

The use case is mainly with my 5D3 and composing the scene and controlling the camera, Canon and ML side, when the camera is low, on the ground or LV is not easily viewable. All the time using my iPad or iPhone as a wireless monitor, ie rather than the  camera's LV.

After a few hours playing with it, it does indeed seem to work on the 5D3, and I'll write up and report on my experiences as soon as I can.

The device connects at 1080p24, ie as shown on the Mars X unit.

My problem is I can't seem to get the EOS M to be recognised by the Mars X unit.

I've tried forcing HDMI in ML, ie on and off, and I've set the EOS M to 24 FPS.

Remember I'm in photo mode in this use case.

Can any of the video gurus suggest what I might be doing wrong, ie so that the Mars X works on the 5D3 but not the EOS M. 

Maybe, sadly, it simply doesn't work with the EOS M :-(

Cheers

Garry

Only one person at a time can edit.

As I found out today.

I'll wait awhile and then add anything I can.

I'll stop using  in the future.

Over and out.

Maybe better to change the silent dng/mlv code so it works the same as when recording with mlv_lite?

Please don't break the silent module for us humble photographers 

If someone is going to look at the silent module, then maybe a chance to tweak a few things, eg get EXIF working and the ability to change image file name via Lua 

@ichthys

I think I see what you are saying and, of course, that post is old.

I personally would now not call key.press inside the key event handler.

Instead I would set a flag and call key.press in, say, the shoot_task event handler, as I do in my MUSIC script, https://gist.github.com/pigeonhill/7b02d3dcadddbc703940778d74cd7af2?ts=4

@ichthys

As that post was originated by me, but tweaked by @a1ex I'll restrict my comment to within my ignorance.

I thought variables listed in a function call were defined as local.

But, I'm most probably wrong, as my ignorance continues to grow as a learn more about Lua 😀

@Audionut

That version is the one I've been running my MUSIC developments on and apart from the Expo Sim bug (reported to @a1ex https://www.magiclantern.fm/forum/index.php?topic=25743.msg233664;topicseen#msg233664), things look OK...so far 

In today's post about MUSIC I'm pleased to discuss/demonstrate use case 7, ie silent FRSP bracketing; which is a tool I use in, say, cathedrals/churches or anywhere camera noise would be unacceptable.

https://photography.grayheron.net/2021/01/music-use-case-7-full-resolution-silent.html

In addition to flagging that I've tweaked MUSIC to make the Quick Access (QA) more robust and fixing a couple of bugs, I'm going to highlight a few things that will need changing as you use MUSIC on different cameras.

But first, a big 'hats off' to the ML developers, especially a1ex.

Why?

Because trying to get a piece of code/script running on different cameras is a nightmare!

Although I'm only trying to get things running on a EOS 5D3 and an M. I'm sure I would go insane if I was trying to get one of my scripts running on every camera that can run ML.

Some of the reasons why it's difficult to ensure code/scripts are cross platform compatible are:
* Not all cameras have the same buttons/keys
* Some cameras have touch screens some don't
* Not all cameras respond identically to Lua commands, eg setting ISO seems to be different on my 5D3 compared to my M, ie on my 5D3 is I ask for ISO 800 in Lua, I get that, on my my M I get a sightly different ISO, eg 1000.

So, as I say, kudos to all the main developers.

Now a word on the EOS M and tweaking my MUSIC script for your camera.

On the 5D3 MUSIC script I recommend setting double half shutter as the ETTR trigger, then setting the QA button to SET, and the hand held use case (ISO invariance) ISO trigger to 1600.

Whereas on the EOS M MUSIC script I recommend setting SET as the ETTR trigger, then setting the QA button as one finger touch, and the hand held (ISO invariance) ISO trigger at 800 (although you will likely get 1000).

On other cameras you will need to explore the options yourself. I've added comments in the script (at the beginning) to help you adjust script settings for your camera.

Bottom line: I realise that I'm likely the only lucky person on the planet using MUSIC and DOFIS :-) :-)

However, as I have said elsewhere, I write my scripts for myself, but openly share my work/thoughts/pain!

Bottom-Bottom line: stay safe and away from the mutating pestilence and ever increasing stupidity in the World!

Looks like I can't switch off the ML owned long SET press on the EOSM, so I've moved to using the touch feature on the EOSM.

I've just got another 'new' EOSM and am setting it up with the lates Lua fix.

Tested my DOFIS and MUSIC scripts, all ok.

But I can't turn off the long SET simulated Q feature, that I thought was in the junkie menu, that I can't find.

I need access to the SET, as my script uses a long press here, that I need to control.

Can anyone suggest how to switch off the long SET Q in the EOSM.

Cheers

Garry

Yeah, we are building the bridge while crossing it.

All the above potentially suggests the need for a 'new' taxonomy ?

We have those that focus on: Video; those on photography; those on Lua; and the cross-interest ML core developers.

Beyond my pay grade to sort out ;-) :-)

Another use case added: this time a Zero Noise bracketing scheme: https://photography.grayheron.net/2021/01/music-extending-its-repertory.html

@a1ex

I'm content I can hand hold bracket from LV, ie my MUSIC script does this for me.  That is the image to image delay is not an issue.

BTW I'm just about to uplift MUSIC with a new use case, ie zero noise bracketing, which I find a great strategy, ie base shutter & base shutter + 4Ev.

Cheers

Garry

@a1ex

If that's the case, bad news - it can't be done easily

I thought you might say that 

As for the use case it is being able to use Lua to moderate normal shutter action outside of LV. That is the feature would allow the user to intercept the 'normal' shutter and use Lua to then control image capture, eg bracketing etc.

There are many times I wish to handhold bracketing, but looking through the optical viewfinder, ie not LV, especially on a 5D3 in bright sunlight.

@Danne

Good point and I'll try and remember to do this in the future ;-)

Regarding my Lua scripting, as you know I script for myself, but freely share on this forum for others to use as they see fit.

I have no idea if others are using Lua like I do, ie to help with photography. I see a lot of video stuff, but not that much photography related discussion.

As I've said before, I think Lua scripting is the star in ML.

Cheers and stay away from the (mutating) pestilence and (increasing) stupidity in the world

Garry

@a1ex

Forgive me if this has been asked by someone before, especially by me 

When using the keypress event handler, I can't seem to hijack the full shutter and unpress full shutter, ie even when I return false, the shutter still operates, both in LV and non LV mode.

Is there a way in Lua to hijack the Canon full shutter?

Cheers

Garry

A real hardware bug!   

In this post I've added two new features to MUSIC: https://photography.grayheron.net/2021/01/music-now-with-use-case-ui.html

A new dynamic UI, based on 6 use cases, and (optimum) handheld exposure bracketing.

@a1ex

You really know how to embarrass someone 

Your memory is phenomenal!

I have a workaround.

Fully understand this is not a priority matter, especially for you.

Cheers and stay safe

Garry

@a1ex

In the script I'm playing with I wish to hijack the SET and UNPRESS_SET keys, so I can use these with a long press, ie use normally if the press/unpress is less that x seconds, or use differently if longer than x seconds.

All is OK, other than the ETTR remains triggered by a SET, no matter what I do.

That is, the ETTR triggered by SET seems to circumvent the key event handler, eg if I use the following, ETTR still triggers off of SET:

Code Select Expand

if kk == KEY.SET or kk== KEY.UNPRESS_SET then
    return false
end

Is this intentional or a 'bug'?

Cheers

Garry

A few words on camera compatibility and MUSIC: https://photography.grayheron.net/2021/01/music-camera-compatability.html

Bottom line: MUSIC, and DOFIS, will run on any camera, but there are a couple of things to look out for.

In this post, I'm releasing a silent exposure bracketing feature in MUSIC:

https://photography.grayheron.net/2021/01/music-exposure-bracketing-with-frsp.html

As usual I welcome any feedback to make MUSIC 'better'.