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.

Messages - garry23

Pages: 1 2 [3] 4 5 ... 88
General Help Q&A / Quick Shooting Screen
« on: February 11, 2021, 08:11:14 PM »

I'm in the process of adding a feature to my focus bracketing script (DOFIS) that will provide user feedback in the Quick Shooting screen (on my 5D3).

However, I've noticed a strangeness, that could be a 'ML bug'.

Here is a screen capture:

VRAM9q" border="0

As you can see, I'm adding a bar at the top that shows some focus info and changes colour according to focus overlap with the previously taken image. In the above the bar is white, but it can also be red or green.

All seems OK, however, as you can see the ML enhanced battery value has taken on the colour of my bar, and the battery colour changes according to my bar's colour.

None of the other ML enhanced info fields, eg colour temp, changes, just the battery field.

Just thought I would let you know.



General Help Q&A / CBR Error
« on: February 09, 2021, 02:59:07 PM »

I get random console messages, ie not every time, saying "CBR Error not enough memory".

The script seems to keep running OK: 5D3 with latest Lua fix.

Without wishing to waste your time, have you any general guidance regarding this error message.



General Help Q&A / Re: Start up messages
« on: February 08, 2021, 08:27:42 PM »

Many thanks for the reassurance that there is nothing going ‘wrong’.



Scripting Q&A / Re: MLU
« on: February 08, 2021, 07:31:57 PM »

I’m embarrassed to admit that the focus info outside of LV missed me, reinforced by me continuing to read the old/current Lua documentation.

Agree with you about coders not being necessarily accountable for doc updates.

Not a straightforward thing to sort out when ML is a volunteer based community.

General Help Q&A / Re: Start up messages
« on: February 08, 2021, 06:58:09 PM »
OK an update.

As Walter said, if I switch the Debug console request off, obviously I don't get the console.

But with the console on, I see the messages, which just look wrong to me.

I get these if no script or no modules are loaded.

General Help Q&A / Re: Start up messages
« on: February 08, 2021, 06:41:56 PM »
Yes, I’ve tried multiple combinations and still get the messages above.

As I say, this started all of a sudden.

References to auto ETTR and intervalometer seem weird to me.

General Help Q&A / Re: Start up messages
« on: February 08, 2021, 06:33:37 PM »
Yes, keep switching console off, but it always comes back on at start up.

Scripting Q&A / Re: MLU
« on: February 08, 2021, 06:29:44 PM »
Dream, Pray, Hope then Do  :)

Scripting Q&A / Re: MLU
« on: February 08, 2021, 06:06:40 PM »

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.



General Help Q&A / Start up messages
« on: 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?

Scripting Q&A / Re: MLU
« on: February 08, 2021, 11:09:14 AM »
Shock/horror.  :) :) :) :)

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


Get the current focus distance (in mm). Only updated in LiveView.
focus_distance int readonly

Scripting Q&A / Re: MLU
« on: February 08, 2021, 10:01:46 AM »

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?

General Help Q&A / Re: Err 70
« on: February 07, 2021, 05:47:56 PM »

Reformatted  :)

Fingers crossed.



General Help Q&A / Re: Err 70
« on: 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.

General Help Q&A / Err 70
« on: 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:

Code: [Select]
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

Scripting API suggestions / Potential Lua API additions
« on: 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:

  Returns the currently spotmeter value at the LV x and y position
  Only works in LiveView.
  - 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)
  Requested spotmeter value, as set in the ML spotmeter menu, eg Ev units etc

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

  Gets the current ETTR shutter value, according to the class selected
  Only works in LiveView, controlled by settings in ETTR menu
  - None
  The shutter sub-class value according to the class used

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

  Sets/gets whether mirror is up or not
  Works outside of LV
  - 1 = up, 0 = down
  MLU state

Scripting Q&A / Re: MLU
« on: February 07, 2021, 11:28:09 AM »
I’ll post something soon, ie to get things going.



Scripting Q&A / Re: MLU
« on: February 07, 2021, 11:06:14 AM »

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


How about a new sticky link under scripting

A sticky topic with Lua API suggestions can be helpful, yes.
from a1ex

Scripting Q&A / Re: MLU
« on: February 07, 2021, 10:42:13 AM »

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?

Scripting Q&A / MLU
« on: February 07, 2021, 10:09:45 AM »

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.

Scripting Corner / Re: MUlti Shot Image Capture script
« on: February 06, 2021, 05:30:37 PM »
A minor tweak to MUSIC to allow users to change a couple of camera/user specific settings:


Just measured the unit for you, without cables, but with the inclosed battery, obviously: it’s 118gms.

Scripting Corner / Re: MUlti Shot Image Capture script
« on: February 05, 2021, 04:00:54 PM »
In this post I discuss Use Case 6: MUSIC's (optimum) hand held, exposure bracketing feature:

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.

Scripting Corner / Re: MUlti Shot Image Capture script
« on: February 03, 2021, 03:36:01 PM »
As hinted at above: a post on MUSIC's new Use Case 9:

Pages: 1 2 [3] 4 5 ... 88