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

#51
General Chat / Re: Any thoughts on this idea?
February 20, 2021, 02:24:37 PM
QuoteGunPatent.com  Marcio K • 15 hours ago
Not at all. This does not patent digital zoom. It patents using the optical zoom ring to control added digital zoom based on the position of the optical zoom ring. That graph up there shows it all. (I'm the inventor and patent attorney who wrote the patent).

Quoted from the OP link ;-)
#52
Scripting Q&A / Re: Extra delay script for intervalometer
February 20, 2021, 10:25:17 AM
QuoteOne thought, that I haven't tested, and @a1ex may say won't work is that you dynamically change the intervalometer settings via the event functional call, ie use a menu.set call to change the take a picture every value to whatever number you want, ie as your TL progresses.

Just tested this:

event.intervalometer = function(count) menu.set("Intervalometer","Take a pic every",count.."s") return end

It works, ie as a ramping function, but it seems to restart the intervalometers start delay but respects the count, ie the event doesn't appear to reset count. So, if you put the start delay to zero, you can certainly 'play around' with dynamically tweaking the TL times using the event call, ie achieve 'variable' TLs, even if you are not a Lua scripter.

Might be worth experimenting with, ie as a crude user controlled ramping approach.
#53
General Chat / Re: Any thoughts on this idea?
February 20, 2021, 08:03:51 AM
@IDA_ML

QuoteBy the way, ML on the EOS-M, the 100D, the 5D3 and other models too has this function already in the video mode.

Yes I know, that's why I posted the link, as I thought some may be interested in the claim of a 'new' idea ;-)
#55
Academic Corner / Photography on Mars ;-)
February 19, 2021, 02:38:05 PM
Just saw this posted over on DPR and thought some may like to read it as well.

https://link.springer.com/article/10.1007/s11214-020-00765-9
#56
Scripting Q&A / Re: Extra delay script for intervalometer
February 18, 2021, 10:32:29 PM
@surami

One thought, that I haven't tested, and @a1ex may say won't work is that you dynamically change the intervalometer settings via the event functional call, ie use a menu.set call to change the take a picture every value to whatever number you want, ie as your TL progresses. 

Of course a1ex may say this won't work, but it's a thought, unless resetting the take a picture every value resets things.
#57
Scripting Q&A / Re: Extra delay script for intervalometer
February 18, 2021, 06:57:12 PM
QuoteI need the gap to have enough time for moving the pant/tilt head and enough time to chill the whole setup on the tripod.

How about writing your own timelapse script?

#58
Scripting Q&A / Re: Extra delay script for intervalometer
February 18, 2021, 06:34:46 PM
Looks like your scripting is good, your Lua module is ok and, as @a1ex, explains, you 'just' need to adjust your workflow a bit  ;)
#59
Scripting Q&A / Re: Extra delay script for intervalometer
February 18, 2021, 09:39:20 AM
I tried the script on my 5D3 and all looks ok.

Are you running the latest Lua fix version for your Cam?

#60
Scripting Q&A / Re: Extra delay script for intervalometer
February 17, 2021, 12:01:10 AM
And, what's not working ?
#61
General Chat / Anamorphic lenses
February 16, 2021, 10:45:42 PM
I thought some may like to watch this?

https://youtu.be/bIhaItLnSR0
#62
Scripting Q&A / Re: Extra delay script for intervalometer
February 16, 2021, 10:05:40 PM
Events?
#63
Something for the landscape photographer in this post, which includes another minor tweak to DOFIS:

https://photography.grayheron.net/2021/02/a-few-thoughts-for-landscape.html

#66
Scripting Corner / EOSM Focus Reporting
February 12, 2021, 10:28:58 PM
@a1ex

Just reporting the following, using my latest DOFIS script with the latest Lua fix.

On the 5D3 all is OK, ie I can track focus, focal length and aperture outside of LV, ie when the Quick Shooting screen is showing.

On the EOSM when I go into the QS screen, focus doesn't update.

As I say, just reporting.

Cheers

Garry
#67
I'm pleased to release the 2021 version of DOFIS, that now provides focus information, eg infinity focusing and focus bracketing, outside of LV; so you can use your viewfinder and get focus info.

https://photography.grayheron.net/2021/02/dofis-2021-uplift.html

The DOFIS info is accessible via the Quick Shooting screen.

NOTE: as usual I've only been able to test this release of DOFIS, designed for non-mirrorless ML cameras, on my 5D3.
#68
General Help Q&A / Re: Quick Shooting Screen
February 12, 2021, 11:14:48 AM
...but only if I call my display.print in a specific area of the screen, ie top left.

Fun stuff  :)
#69
General Help Q&A / Re: Quick Shooting Screen
February 12, 2021, 10:51:34 AM
Have carried out more experiments and can control the effect.

In other words, whatever colour I use last in my function, seems to get written to the ML battery background colour.

Bottom line: I'm ignoring it as I can live with it changing colour.
#70
General Help Q&A / Quick Shooting Screen
February 11, 2021, 08:11:14 PM
@a1ex

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.

Cheers

Garry
#71
General Help Q&A / CBR Error
February 09, 2021, 02:59:07 PM
@a1ex

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.

Cheers

Garry
#72
General Help Q&A / Re: Start up messages
February 08, 2021, 08:27:42 PM
@a1ex

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

Cheers

Garry
#73
Scripting Q&A / Re: MLU
February 08, 2021, 07:31:57 PM
All

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.
#74
General Help Q&A / Re: Start up messages
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.
#75
General Help Q&A / Re: Start up messages
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.