Menu

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.

Show posts Menu

Messages - garry23

#76
General Help Q&A / Re: Start up messages
February 08, 2021, 06:33:37 PM
Yes, keep switching console off, but it always comes back on at start up.
#77
Scripting Q&A / Re: MLU
February 08, 2021, 06:29:44 PM
Dream, Pray, Hope then Do  :)
#78
Scripting Q&A / Re: MLU
February 08, 2021, 06:06:40 PM
@a1ex

I am more than willing to support updating words, as I have been doing on the wiki terminology piece.

The issue is, I don't know what I don't know  ;)

I'm embarrassed to say I hadn't spotted the focus uplift.  >:(

I guess a point for the future is, that whenever code gets changed and uploaded to all, the code creator/changer should also look to changing any documentation. Easy to say, but not easy to impose.

Cheers

Garry
#79
General Help Q&A / Start up messages
February 08, 2021, 05:53:45 PM
All of a sudden the console always comes on at start up, ie something was triggering it: 5D3 latest Lua fix.

I have switched off all modules and still get this at start up, which confuses me:

image0w" border="0

Can anyone suggest what's going on?

I can't see how I have references to ETTR is I haven't loaded that module, and what's the intervalomter ref mean?
#80
Scripting Q&A / Re: MLU
February 08, 2021, 11:09:14 AM
Shock/horror.  :) :) :) :)

QuoteFocus distance and DOF info were available in lua_fix builds since early 2018. ML asks the MPU for a refresh, once every second.

vs

Quotefocus_distance
Get the current focus distance (in mm). Only updated in LiveView.
focus_distance int readonly
#81
Scripting Q&A / Re: MLU
February 08, 2021, 10:01:46 AM
@a1ex

Just a few more thoughts on MLU.

The current ML MLU seems to 'just' switch the Canon MLU feature on or off on my 5D3.

This means that for my shutter triggered, hand held bracketing use case, this means I get a shutter-up, image shutter-down, then I enter LV and get a shutter-up, then script runs bracket capture, then exit LV for a mirror down. Works, and I've coded it as an option in my script.

As long as we can't hijack the full shutter press, the above will have to do.

At the back of my mind is another weakness of the current ML-Canon set up: not being able to access focus info in non LV mode. The use case being using the VF and getting ML, ie a script, give you focus feedback.

Do you think it could be possible to remain in LV but do a mirror-down, so you can get the benefits of both modes, ie use the VF and keep getting focus info fed to Lua?

#82
General Help Q&A / Re: Err 70
February 07, 2021, 05:47:56 PM
@a1ex

Reformatted  :)

Fingers crossed.

Thanks

Garry
#83
General Help Q&A / Re: Err 70
February 07, 2021, 05:33:06 PM
Just switching the camera on.

Tried several times.

Pulled the battery and retried: same.

Pulled battery and card with ML on, then restarted: ok.

Reinserted ML card seems ok now.

As I say, I don't think I've ever had an error 70 message.

Fingers crossed all is ok now.
#84
General Help Q&A / Err 70
February 07, 2021, 05:20:29 PM
I posting this as I don't usually see Err 70 messages, but this occurred three times in a row, ie after pulling battery etc.

5D3 using latest Lua build.

Not sure if it's me causing it (eg one of my scripts) or core ML:

ASSERT: FALSE
at ./Memory/Memory.c:187, MetaCtg:9a90
lv:0 mode:3

MetaCtg stack: 18ef30 [18f500-18e500]
0xUNKNOWN  @ de48:18f4f8
0xUNKNOWN  @ 17bbc:18f4d0
0x000178B4 @ ff2b9dec:18f4b0
0xUNKNOWN  @ 178e4:18f4a0
0xUNKNOWN  @ 1796c:18f480
0xFF433360 @ ff4344f4:18f3e0
0xFF432128 @ ff4339a8:18f2d0
0xFF438ED0 @ ff4321c8:18f280
0xFF438A04 @ ff43936c:18f168
0xFF58F5B0 @ ff438a94:18f040
0xFF428918 @ ff58f5d4:18f018
0xFF428434 @ ff428a90:18efd8
0xFF58A5CC @ ff4286cc:18efa0
0x000099A0 @ 17fa8:18ef90
0x00001900 @ 9a8cMagic Lantern version : lua_fix.2020Dec28.5D3123
Mercurial changeset   : 7e5067c0a8cf (lua_fix) tip
Built on 2020-12-28 18:19:30 UTC by jenkins@nightly.
Free Memory  : 241K + 2935K
#85
Scripting API suggestions / Potential Lua API additions
February 07, 2021, 01:06:21 PM
This is my humble attempt to start a list of user requested API ideas/enhancements/additions to Lua.

I suggest anyone posting here attempt to suggest their idea in a format that mirrors the ML Lua API documentation (see mine in this post).

I suggest this thread is not the place to debate the worth or even practicality of the API suggestion. Let's leave that for another place, once a Lua API 'uplift project' gets going. This thread is about ideas/needs/wants. Having said that, I suggest anyone posting here think about their need or use case, ie let's try and be sensible ;-)

The following are a few of my personal suggestions to get us going (note I have deliberately kept formatting simple, ie not complicating the posts with HTML:

----
lv.spotmeter(x,y[,width=10[,height=10]]])
  Returns the currently spotmeter value at the LV x and y position
  Only works in LiveView.
Parameters:
  - x int LV x position of centre of spotmeter box
  - y int LV y position of centre of spotmeter box
  - width/height int size of spotmeter's width in LV units. Min = 5, Max = edge of LV_reached (x and y)
Returns:
  Requested spotmeter value, as set in the ML spotmeter menu, eg Ev units etc
----

----
lv.histo(x,y[,from=0)
  Returns the currently histogram % value between the requested x and y values
  Only works in LiveView.
Parameters:
  - x int histogram start (0,255)
  - y int histogram end (0,255)
  - from (0 or 1). 0 full LV, 1 from spotmeter box
Returns:
  Requested histogram % value
----

----
Camera.shutter.[class=raw].ettr
  Gets the current ETTR shutter value, according to the class selected
  Only works in LiveView, controlled by settings in ETTR menu
Parameters:
  - None
Returns:
  The shutter sub-class value according to the class used
----

----
lens.mf(value=0)
  Sets/gets manual focus, ie switches/overrides lens-set AF, ie MF on and off irrespective of lens physical setting
  Only works in LiveView
Parameters:
  - 1 = on, 0 = off
Returns:
  (bool) whether the operation was successful or not
----

----
camera.mlu(value=0)
  Sets/gets whether mirror is up or not
  Works outside of LV
Parameters:
  - 1 = up, 0 = down
Returns:
  MLU state
----

#86
Scripting Q&A / Re: MLU
February 07, 2021, 11:28:09 AM
I'll post something soon, ie to get things going.

Cheers

Garry
#87
Scripting Q&A / Re: MLU
February 07, 2021, 11:06:14 AM
@a1ex

Thanks for the LV suggestion, I'll look into that approach.

@Audionut

How about a new sticky link under scripting

QuoteA sticky topic with Lua API suggestions can be helpful, yes.
from a1ex
#88
Scripting Q&A / Re: MLU
February 07, 2021, 10:42:13 AM
@a1ex

Thumbs up for the FRSP vision  :)

My use case is when I'm handholding, eg super resolution bracketing or exposure bracketing, where I'm not in LV, ie using the VF.

But fully understand what you say and recognise ML priorities at the moment.

BTW I'm personally keeping a wish list of possible Lua API enhancements, I wonder if we should have a sticky link for capturing such API thoughts?
#89
Scripting Q&A / MLU
February 07, 2021, 10:09:45 AM
@a1ex

I'm trying to understand how ML's MLU work, eg on my 5D3, using the latest Lua fix build.

Seems to work ok in single shooting.

What I'm wondering is, would it be possible, from a Lua call, to enable it and activate it, ie move the mirror, then call shoot() as many times as needed, then switch off MLU, ie lower the mirror.

I appreciate this 'request' will need to be added to others and only enabled in the future when priorities allow. Just asking if you think it is possible.
#90
Scripting Corner / Re: MUlti Shot Image Capture script
February 06, 2021, 05:30:37 PM
A minor tweak to MUSIC to allow users to change a couple of camera/user specific settings:
https://photography.grayheron.net/2021/02/music-camerause-specific-settings.html
#91
@ChristianEOS

Just measured the unit for you, without cables, but with the inclosed battery, obviously: it's 118gms.
#92
Scripting Corner / Re: MUlti Shot Image Capture script
February 05, 2021, 04:00:54 PM
In this post I discuss Use Case 6: MUSIC's (optimum) hand held, exposure bracketing feature:

https://photography.grayheron.net/2021/02/music-use-case-6-handheld-optimum.html

In addition, I discuss the new shutter-triggered option in UC6; that allows you to access UC6 from a normal shutter, ie using the VF.

UC6 gives you three exposures when hand holding:
1. An ETTR (base) exposure for the highlights, at the lowest ISO you can use
2. A second exposure taken at the slowest shutter you can use and the lowest ISO, ie to maximise the photon capture
3. A third image at the slowest shutter, but at the ISOless setting you have set in the MUSIC script, eg ISO 1600 on my 5D3.
#94
Scripting Corner / Re: MUlti Shot Image Capture script
February 03, 2021, 03:36:01 PM
As hinted at above: a post on MUSIC's new Use Case 9: https://photography.grayheron.net/2021/02/music-use-case-9-auto-bracketing-from.html
#95
Scripting Corner / Re: MUlti Shot Image Capture script
February 03, 2021, 01:04:38 PM
I've just added a new use case to MUSIC, that I personally find useful.

The use case is taking a 'perfect' exposure bracket set from a shadow-set shutter.

I use the ML spotmeter in Ev mode to ensure the exposure in the shadow area of interest is OK.

I would normally then go to ML's advanced bracketing and set up for a 0 + ++ shot using Auto capture, which will take as many brackets as required, at the delta Ev I requested, until the 'ETTR' shutter has been reached/exceeded.

The 'downside' of using this approach is that I need to trawl through the ML screen to set things up and I can't get auto bookends, ie I would need to take an image of my hand, say, before I set ML's AB and then switch off AB to take another image of my hand.

Hence MUSIC Use Case 9.

The UC9 menu looks like this:

VRAM11" border="0

You can: set the required delta EV (1-4); request bookends or not, ie a dark frame either end of your bracket sequence; request a delay; you can switch on MUSIC's quick access mode, which will allow you to repeating run UC9 my simply doing a long press of the trigger button, eg SET on my 5D3 and 1-finger-press on my EOSM.

UC9 was a bit of a scripting challenge for me, so I'll say a few words here (but not on my blog) about how I 'hacked' things.

The two issues are how to make taking a bookend work with ML's script triggered Advanced Bracketing, and pausing the script  until AB has finished, then switch it off in the ML menu, ready for a bookend capture.

My (hacked) solution is that, if taking a front-end bookend, I wait until the card has registered it has captured the bookend. I then initiate AB and set an infinite loop to watch to see when AB has finished, using the fact that AB completes in play/review mode.

I'm sure the code gurus are pulling their hair out reading about my clumsy scripting: but it works  :)

BTW here is the relevant code snippet:


if use_case == 9 then -- exposure bracket from shadows-set shutter to an AB 'ETTR' shutter
local check = 0

if MUSIC_menu.submenu["Bookends?"].value == "yes" then
check = dryos.shooting_card.file_number
Bookends() -- insert bookend
repeat msleep(50) until dryos.shooting_card.file_number ~= check -- bookend captured, safe to start AB capture with correct shutter value
check = 0
end

msleep(MUSIC_menu.submenu["Delay"].value * 1000) -- user delay if requested

menu.set("Shoot","Advanced Bracket",1) -- set up ML AB for a shadows to 'ETTR' AB capture
menu.set("Advanced Bracket","Bracket type","Exposure (Tv,Ae)")
menu.set("Advanced Bracket","Frames","Autodetect")
menu.set("Advanced Bracket","EV increment",tostring(MUSIC_menu.submenu["Ev delta"].value).." EV")
menu.set("Advanced Bracket","Sequence","0 - --")

my_shoot() -- trigger advanced/auto bracketing

while true do -- wait until auto bracketing is finished: a bit hackish but works and slows you down :-)
if camera.gui.play then
check = dryos.shooting_card.file_number
end
sleep(2) -- there is a very small probability this time may not work, but a low prob I think
if camera.gui.play then -- still in play mode, so check if AB is finished
if dryos.shooting_card.file_number == check then break end
else
check = 0
end
end

menu.set("Shoot","Advanced Bracket",0) -- finished with AB

key.press(KEY.HALFSHUTTER) -- HS press to return to ML LV mode, ie from AB review screen, as AB finishes in review mode :-(
msleep(100)
key.press(KEY.UNPRESS_HALFSHUTTER)

repeat lv.resume() until lv.running -- just in case

Bookends() -- check if bookend needed
camera.shutter.ms = t_base
tidy_up() -- and exit use case 9 capture
return
end


Cheers, and stay safe and away from stupidity

Garry
#96
General Help Q&A / Re: Hollyland Mars X help
February 02, 2021, 05:52:52 PM
Ok, I've convinced myself that, like some other Canon cams, the EOSM's HDMI output is interlaced and not progressive like, say, the 5D3.

Damn!
#97
I thought some may be interested in my latest post on using the Hollyland Mars X from a 5D3 photographer's perspective:

https://photography.grayheron.net/2021/02/composing-wirelessly-on-5d3.html
#98
General Help Q&A / Re: Hollyland Mars X help
February 02, 2021, 08:31:31 AM
Can someone in the know confirm that the HDMI out on the EOS M is p rather than i

I've looked in the manual and all it says is 1080.

Thanks in anticipation.
#99
General Help Q&A / Re: Hollyland Mars X help
February 01, 2021, 08:20:20 PM
The Mars X says it is connecting at 1080p24 on the 5D3 and all is OK :-)

It's that little EOSM bugger that's annoying me ;-(

#100
General Help Q&A / Re: Hollyland Mars X help
February 01, 2021, 07:29:40 PM
Bhphotovideo site says this

QuoteCompatible cameras include the Canon EOS 5D Mark III, 5D Mark IV, 6D Mark II, EOS RP, and Canon pro camcorders and consumer camcorders; Sony a6600 series, a7 series, and a9 series cameras; Panasonic Lumix mirrorless cameras; FUJIFILM X series mirrorless cameras; and Nikon Z series mirrorless cameras. Note that the Mars X Transmitter is not compatible with cameras that record only interlaced video, such as the Canon 6D, 60D, 5D2, 80D, and 90D.