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.

Topics - l_d_allan

Pages: [1] 2 3
Sorry if this has already by asked & answered ....

Is there a tutorial available with step-by-step instructions on getting "Hello, world!" to appear on the LCD of my Canon DLSR's (6d, 5dm2, 600d)?
  • Tool-chain involved, if any.
  • Setup on Windows 10 desktop, if any.
  • How to upload the Lua script to DSLR flash card. My speculation is that it would be similar to updating the ML code and/or modules.
  • How to access and launch the uploaded LUA code to see if it worked.
  • For extra credit, perhaps get a button to light up, or something to beep, or ???

    Please consider features related to "battery management"
    • Drain battery to [fill-in-the-blank] percent if over that state-of-charge (SOC).
      My understanding is that to "baby" Li-Ion batteries for longer life, they prefer to be stored at a SOC significantly less than 100%.
    • My K.I.S.S. practice has been to return from a photo event, upload the photos, and plug the batteries used into one or more chargers.
    • More than a few times, this non-professional doesn't take photos for several days or weeks, which is somewhat hard on the battery to sit at high SOC.
    • ...
    • Related feature request:
    • On/Off toggle to not allow battery to be in sleep state with the Power switch ON to go below [fill-in-the-blank] percent.
    • Can happen with Time-Lapses, which can also corrupt the SD card. Why do I know that?  :o
    • The intent is to diminish the occurrences of the battery getting to fully drained status.
      That can also be somewhat hard on the battery, especially if the battery stays at 0% for an extended period of time.
    • ...
    • Corner cases probably make this more complex than I realize.
      Wish this rusty embedded developer (not ARM) had the skills with the ML tool-chain to help implement, but alas, not. Mea culpa.
    • ...
    • A model to perhaps serve as a baseline to reverse engineer:
      My recently acquired Dell laptop has built-in Windows-10 battery management. It seems quite a bit improved since the last time it played with it with Win-7.
      It also has a Dell-specific app for somewhat more advanced battery management capabilities.

    Sorry if something equivalent has already been requested ... or if this rusty ML fan-boy isn't aware that it has already been implemented.

General Help Q&A / Errors encountered during running of cr2hdr-20bit.exe
« on: September 12, 2016, 03:24:41 PM »
Using 20bit version of cr2hdr-20bit.exe, and date-stamp seems to be: 2015-Nov-24

Following are warnings/errors produced during processing:

Last update: ab1e90c on 2015-11-24 09:50:10 UTC by a1ex:
cr2hdr: moved safeguard from medium_int_wirth to kth_smallest_i...

Active options:
--amaze-edge    : use ...
--cs2x2               : apply ...
--wb=graymax    : set ...
--compress    : Lossless DNG comrpession

Input file    : 160911q_3791_MefSteveGreen.CR2
Attempt to reload aborted
Compilation failed in require at C:/Perl/lib/ line 93.
Compilation failed in require at C:/Perl/lib/IO/ line 269.
BEGIN failed—compilation aborted at C:/Perl/lib/IO/ line 269.
Compilation failed in require at C:/Perl/lib/IO/ line 101.
BEGIN failed—compilation aborted at C:/Perl/lib/IO/ line 101.
Compilation failed in require at C:/Perl/lib/IO/ line 133.
BEGIN failed—compilation aborted at C:/Perl/lib/IO/ line 133.
Compilation failed in require at –e line 162.
**WARNING** Could not identify the camera from EXIF. Assuming 5d MARK III ... actual camera is 6d
... cr2hdr-20bit.exe proceeded and seemed to process OK

Also happened with following files (7 of 426 total .CR2 files)
Input file    : 160911q_3786_MefSteveGreen.CR2
Input file    : 160911q_3788_MefSteveGreen.CR2
Input file    : 160911q_3789_MefSteveGreen.CR2
Input file    : 160911q_3792_MefSteveGreen.CR2
Input file    : 160911q_3793_MefSteveGreen.CR2
Input file    : 160911q_3794_MefSteveGreen.CR2
Input file    : 160911q_3795_MefSteveGreen.CR2

To speed up processing and help keep the desktop computer responsive, I use cr2hdr-20bit.exe with 10 separate below-normal-priority threads in 10 command prompt windows (see next line). Only the first file for 7 of the batches had problems.

for %%n in (0 1 2 3 4 5 6 7 8 9) do start /belownormal for %%c in (1609???_???%%n_*.cr2) do cr2hdr-20bit --compress %%c

I'm hoping ML devs consider preparing a version for the recently announced 5D iv when it becomes generally available.

(and sorry if this is considered trolling).

Hmmm ... I wasn't able to create a "New Topic" in the "Camera Specific Discussion" sub-forum.

Scripting Corner / Beep when zoom lens is at specified focal length
« on: July 16, 2016, 07:39:20 PM »
On the DPR forum for Sony full frames, the issue of "focal length detents" came up. Silly?

Anyway, a member suggested a work-around of having a beep at a specified focal length. That prompted me to suggest it as a feature request to the ML gurus.

After all, if a camera can beep, and put the Focal Length in the EXIF, then it seems like "only magic" involving firmware-only. Correct?

The FR in the Sony forum specifically mentioned FL / 2 (such as 47mm for a 24-70mm zoom).

Obviously, low priority. It was my way of gushing about the ML Devs.  ;D

General Help Q&A / Appreciate help updating the Wikipedia entry for ML. Thx
« on: February 26, 2016, 03:22:27 AM »
I've attempted to update the Wikipedia entry for MagicLantern over the past year or so:

There are several {{citation needed}} warnings, and some information I believe to be accurate has been removed.

  • A version for the 6D is available, but less fully supported because none of the principal developers own the camera.[citation needed] Still true? Or is the 6d now a "1st class supported camera?"
  • A version for the mirror-less EOS M is less mature than fully supported cameras that one or more of the principal developers own.[citation needed] Still true?
  • Project policy is to not develop a version for the pro body 1 series like the 1Dx.
  • has Canon 5d3's available with Magic Lantern installed.

My 6d has gotten to the state of being semi-bricked, admittedly at least somewhat operator error. Assistance appreciated.

Sorry for the tl;dr ... I'm attempting to provide all hopefully relevant information, but it no doubt has extraneous info, may be incomplete, or reflect flawed memory (don't get old  :o )

  • Happened December 13. Was using the most recent build at the time from Nov, 2015 ... not the Dec 20, 2015 build which wasn't yet available
  • I'm not sure of the exact sequence, but the following is my best recollection .... sorry, in retrospect, should have kept log.
  • Canon OEM battery with "Recharge Performance 2 of 3" with 100% charge reported. I use either the Canon 5d2 or 6d OEM charger.
  • Happened during lengthy star-trail testing ... time-lapse + BULB stopped by battery going flat
  • Using ML BULB and Intervalometer with "unlimited 4 minute exposures". I've done this at least 50 times with no previous problems.
  • IIRC, the last file was semi-intact and could up uploaded with card-reader to desktop, but some visual glitches indicating corruption ...
  • Don't recall if this was the end of the star trails that night, or if I put in another LP-E6 battery to continue with making a "star trails pano"
  • I always start with the 6d OEM battery, but it is possible I was using a reputable non-OEM battery that has worked very well since I've owned it .... 3 of 3 "Recharge Performance" if that means anything for a non-OEM battery.
  • Recharged battery at home in Canon 6d OEM charger, and all seemed well. Re-installed battery.
  • Star trail ok, since you don't really need the final capture
  • At this point, everything seemed ok
  • 6d seemed bricked on next usage within day or so ... no activity light when turned ON. Did I forget to charge?
  • After 10 slow breathes, diagnosis was that battery was flat. Whew, but ...
  • Did some swapping of other LP-E6 batteries from Canon 5d2, along with other SD card from Canon T3i with ML.
  • Could get 6d to power up with no SD card, but not real reliably.
  • I was running late to get to a Christmas-related event, so I was less-than fully rational on diagnosis efforts. Sorry.
  • Later, 6d with formatted SD card from T3i (maybe by desktop in card-reader) seemed operational, without ML
  • Re-installed ML, not sure on which SD card.
  • Checked FAQ on ML "Camera Emergency Dept" sub-forum, and did the recommended steps ... maybe 2x.
  • I've read about, but not used the "Diagnostic Tools" in this sub-forum. At this point, the 6d is probably unable to run them yet. Is it ok to practice using the "Diagnostic Tools" on a a5d2 or T3i with fully functioning ML while or before working on the 6d?
  • Once before, I've dealt with an apparently bricked f.f. in the past that had ML installed, so at this point it didn't seem like a big deal, and no cause for panic. I don't recall if it was the 5d2 or 6d
  • FWIW: Note that on the DPR forums, I am probably one of the biggest fans of ML ... perhaps the biggest ... almost a fan-boy.
  • The 6d got back to working for a while ... all seemed ok (not sure whether using time-lapse, but pretty sure SD card had Nov, 2015 ML)
  • At this point, everything seemed ok again.
  • Next usage within a day or so ... battery dead again ... back to original semi-bricked
  • Powered off 6d with ML on possibly corrupted SD card seems to be draining battery.
  • When I remove the SD card and battery for 10 to 60+ seconds, 6d will power-on. May or may not work by putting in non-ML SD card with power left on.
  • Batteries other than the 6d OEM card seem to work better ... almost as if the 6d OEM battery has been corrupted somehow
  • IIRC, 6d is glitchy with non-ML SD card.
  • IIRC, powering up 6d with ML disabled (press SET during power up?) doesn't work.
  • With very busy Christmas season, I've been using my 5d2 with Nov, 2015 ML build  (just noticed Dec nightly build ... will install)
  • I regret and apologize that I haven't had the luxury of taking a coherent approach to diagnosis. Fortunately, I've got the 5d2, T3i, etc.

I would Greatly Appreciate help to take a rational, coherent approach to diagnosis and getting the 6d working ok again. It clearly isn't fully bricked, but not really usable, maybe even without ML.

At this point, this volunteer hobby'ist has tens of thousands of captures in my post-processing backlog from about a dozen unpaid Christmas related events. I'm hoping the fix is simple, like replace SD card, but it may not be. I will make every effort to work with anyone willing to help, and check this forum regularly for any replies.

5d2, Aug 19 nightly build (2015Aug19)
When I attempt to select Dual-ISO 100/1600, 100/3200 or 100/6400, I see the warning message:
"Consider using a less aggressive setting (e.g. 100/800)

The 5d2 seems to accept 100/1600, and shows 2.8 EV DR gained.

However, if I select 100/3200 or 100/6400, it seems to ignore those settings. The EV gain doesn't change. When I return to the higher menu, it continues to show 100/1600 rather than 100/3200 or 100/6400. When I "Q" back to the Dual-ISO pop-up, it does show 3200 or 6400 as the upper ISO.

Am I doing something wrong? Is this "as expected"?

IIRC, I used to be able to select 100/3200 and 100/6400 on the 5d2. I think the 6d implementation allows 100/3200 and 100/6400.

I've always been curious just how much Dual-ISO improved DR on my Canon DSLR's, especially my 6D.

Recently, I submitted a series of test RAW's to Bill Claff at He has developed software to calculate "Photographic Dynamic Range", which seems more or less related to DxoMark and numbers:

I'm rather fuzzy on just how Dual-ISO works, and I'm not all that confident I provided Mr. Claff with appropriate test RAW's. The very preliminary results are less than expected ... maybe 1.5 stops at 100/800.

If someone has the interest and time to get involved in this, that would be appreciated.

General Help Q&A / 6D and EFCS? Possible? Preferred settings?
« on: July 21, 2015, 03:30:32 PM »
My impression is that my 6d is capable of EFCS (electronic first curtain shutter), but I'm unclear on the preferred settings.

  • Is this associated with the "Silent" mode in the Canon "Drive" menu?
  • Is there a way to have a delay before the shutter activates, like 2 seconds or 10 seconds? That seems mutually exclusive.
  • Is there a way to use a remote to trigger the EFSC ... normally the "Drive" has to be 2 or 10 sec for the Remote to work. Or not?
  • My impression is that the 6d isn't prone to "shutter shock" like many mirrorless cameras (esp. Sony A7r?), but there still is some. Or not?
  • If EFCS is available, can I expect to be enough better at reduced vibration than Mirror-Up + 2 second delay? Or not worth it?
  • IIRC, there is Mode-1 and Mode-2, but I'm unclear on what they are for.

6D 1.1.6 with Build June-19

I notice that the "Allow Clipping" shows up as an "Advanced ..." option for ETTR. Then it is "forgotten" when you shut down the camera. You have to enable "Allow Clipping" the next time you start ML and use ETTR.

Is this "as intended"? Seems like "Allow Clipping" isn't really all that advanced of a setting compared to some other choices. In any case, it seems it ought to be "sticky" and remembered from shut-down to re-start.  Or not?

Am I doing something wrong (again)? Is there a way to accomplish this?

If this setting isn't "sticky", can that be a Feature Request so that it is "sticky" and remembered?


I'm been quite pleased with the use of cr2hdr.exe with Dual-ISO.

Sorry if this has been asked before, but I wanted to check if the version from 16+ months ago (Dec, 2013) is still the latest/greatest?

I've seen references to 20-bit versions, and mentions of beta's that have to be compiled to use.

Also, I can't tell from the file-names in the Bit-Bucket if they have anything to do with cr2hdr.exe. Is one of those an updated cr2hdr.exe?

Some other questions:
  • Does the cr2hdr plug-in to LightRoom add any functionality?
  • Is anyone experiencing the Previews in Adobe Bridge and ACR to be slow and hard to use?
  • In Adobe Bridge, the thumbnails have false-colors and can be rather grainy looking.
  • That's also true with using the SlideShow to try to figure out which images are keepers and rejects.
  • ...
  • Also, in ACR, it can be sloooooow for all the "instructions" to be applied to the image.
  • A normal image is almost instant when you go from one image to the next, as far as seeing what has been done to the image.
  • With a Dual-ISO image, it can take 5 to 10+ seconds for the post-processing to show up.
  • That seems most likely with "complicated instructions" like Gradients, Local-Adjustments, Radial-Filters, Masks, etc.
  • Overall, post-processing with Dual-ISO .dng's in ACR can be very sluggish.
  • Am I doing something wrong? Or is that "as expected"?

Nightly build: Jan 28, 2015

If it is of interest, here are the contents of:
Code: [Select]
at KernelDry\KerSem.c:306, task Fread
lv:0 mode:3

Magic Lantern version : Nightly.2015Jan29.5D2212
Mercurial changeset   : 703ee626326d (unified) tip
Built on 2015-01-28 23:10:03 UTC by
Free Memory  : 128K + 3991K
and ...
... difficult to copy/paste ... has null codes embedded in log000.log on almost every line ...
I can try again and make more of an effort to maybe replace null codes if it would help.
Code: [Select]
58th (of 3189 lines)
1524: 13169.205 [LVCFG] PROP_EFIC_TEMP 9

The camera had only been on several minutes at the most ... and not in LiveMode.

If helpful, I can open a "Bug Report".

It does seem like a possible bug to have the format of log000.log have lines with the format of ...
Code: [Select]
null-code contents \n
null-code contents \n
null-code contents \n

General Help Q&A / Bad links for nightly builds?
« on: February 09, 2015, 02:59:48 PM »
For the past several days, the links to download Nightly Builds for the 6d, 5d2, and 600d have been broken.
Win 7, IE 11.

It does appear to work with Chrome.

When I click on the "Download" button for Jan 28, 2015, I see a message about: Oops! This link appears to be broken

Am I doing something wrong?

With my 6d at ISO 100, RawDigger treats values of 13,236 and above as that channel being blown.

With Dual-ISO and 100/800, RawDigger treats values of 57,539 and above as blown.

Values in a "black trap" go as low as (0,0,0,0).

Is this "as expected"? My impression is "yes", but I wanted to check for sure.

From another thread:
Indeed, you will want to try the cr2hdr-20bit branch

My understanding is that Dual-ISO continues to be actively developed, and there have been various versions of cr2hdr.exe compiled during 2014.

However, is the version of cr2hdr.exe for Windows that was built on Dec 7, 2013 still the preferred version to use for non-developers? Or a different one?

I don't use RawDigger that often, but it can be Very handy at times.

I went to see if there was an update, and belatedly noticed that the developer released 1.0.x back in November, 2013, and it is no longer free. 30 day trial. 3 levels of capabilities with 3 prices.

Oh, well, it was good while it lasted (being free).

My impression is that ML devs and hard-core ML users have done a lot with RawDigger over the years.

Shucks, the beta doesn't work any more. Drat.

Firmware Version 1.1.4 incorporates the following fixes:
1.Fixes a phenomenon in which some images cannot be transferred to mobile devices running the EOS Remote app.
2.Corrects an error in the German language Feature Guide.
3.Corrects an error in the Korean language Feature Guide.

My understanding is that ML for the 6d won't work if the 6d has firmware 1.1.4 installed. Correct?

I really miss many of ML capabilities, including Intervalometer and enhanced Bulb.


  • Just finished phone ordering the Pro-100 at $298 (Sunday morning)
  • price on web is $398 ... $298 price is by phone only
  • Printer + included A3+ 13x19" paper results in $300 rebate (via AmEx reward card)
  • 866.614.7544 ...
  • $400 rebate if purchase qualifying camera on same receipt
  • For me ...  Canon PowerShoot S110 advanced point-n-shoot 1/1.7" sensor for $250 (semi-obsolete ... replaced by very similar S120)
  • so that makes me golden for the $400 rebate
  • before rebate ... $548
  • after $400 rebate ... $148
  • Obviously, the cost for oem ink will eat your wallet alive if you do much printing, unless you refill ink cartridges
  • FWIW: IIRC, CanonRumors had recent article that Canon would be replacing/updating/refreshing the Pro-1, Pro-10, and Pro-100 line ...

Feature Requests / [NO] Possible? work-around pseudo-MFA on Rebels?
« on: February 20, 2014, 06:52:10 PM »
I was wondering if it would be feasible to implement a work-around MFA (micro focus adjustment) for Rebels and XXd series cameras like the 60d that don't have MFA.

  • Many lenses communicate with the body to report distance to subject. I've noticed a rather coarse value in the EXIF and LCD.
  • How much resolution is there in the chip register for this value? Coarse (cm?) or fine (mm?) or very fine (less than mm?)
  • If the chip register value was very fine, perhaps the distance from 10x magnified LiveView (MLV) could be compared to the value reported by the AF point?
  • Example: Carefully focused MLV reports 2500.00 mm for 50mm lens, and AF also reports a value very close to 2500.00 mm. This would indicate the AF was accurate, and MFA=0 for this combination of body + lens.
  • However, suppose there was some threshold of difference that indicated front-focus or back focus?
  • ML might be able to calculate the equivalent "fudge factor" MFA, and tweak the AF accordingly.
  • Or not?

Been messing around with Dual_iso raws for the past week, this totally changes my shooting style! THANK YOU!!!

I've been using Dual-ISO for some months, and have been impressed also. And I'm also THANKFUL!!! to the devs.

I'd appreciate getting some details on changes you (and others) have made to your shooting style due to Dual-ISO. You may have "use cases" I'm unaware of, or my use of Dual-ISO may be less than "best practice".

I'm ending up with some files with the EXIF info indicating the "Camera Model" is "Canikon". Is anyone else encountering this?

My speculation is Canikon is a mix of Canon and Nikon when ExifTool or cr2hdr is confused with a possible "corner case". Or not?

I'm rusty with grep, but would a "grep" for "Canikon" in the ML or TL source code return any hits?

I'll also ask this question on the ExifTool forum.

So far, I don't have a repeatable sequence that causes this to happen. Sorry. I thought I'd check first before digging into the issue. It happens rather erratically ... maybe every 5th shooting session. I think it's happened 3 or 4 times in the past several months.

It seems to involve:
  • Shooting with both 5d2 and 6d, with one of them having a Samyang manual lenses with no EXIF for fstop or lens
  • I use ExifTool on the .cr2's to fill in this EXIF info when images from Samyang lenses are involved.
  • Seems to involve Dual-ISO, which also involves ExifTool
  • Problem could involve ExifTool, cr2hdr, or ... operator error on my part
  • There is a odd-ball work-flow involved, including multiple pass of ExifTool

General Chat / Canon getting patent of automated microfocusadjustment
« on: January 13, 2014, 02:34:26 AM »
Article from Canon Rumors:

I'm unclear what the engineering involves. I have no idea if it is similar or not to ML's implementation.

BTW: I've been wondering if the lower-end DSLR's (Rebels, 60d, etc.) could get a work-around micro-focus-adjustment capability by comparing a high-resolution distance difference between the distance reported by the AF point and LiveView. Or not?

General Help Q&A / HowTo? Make appropriate target for AFMA auto-dot-tune?
« on: January 11, 2014, 05:51:39 PM »
With my 6d and 5d2, I rarely, if ever, get a successful Dot-Tune AFMA.

There is almost always a warning:
"Double-check the Focus Target"

90%+ of the time, there is a value for AF micro-focus that seems valid ... mid-way between the left and right side of the focus confirmation squares ... such as
results in something like -3, for example, which seems valid.

This happens with both cameras, and all Canon EF lenses that I've tested, including 35mm f2 IS, 50mm f1.8ii, 24-105mm f4, etc. I get the focus set with LiveView and 10x magnification, then turn AF off and LiveView off.

I've tried several targets, like a red brick wall with almost white mortar, 19"x22" laser printer patterns for high contrast, outside in direct sun, inside in room with quite a bit of light from south facing window, etc.

Am I doing something wrong? Some setting I'm over-looking?

I did come across a post for the 6d that mentioned:
'In "INFO button display options" -> "Display shooting functions" has to be enabled'
but I'm unclear what that means.

Pages: [1] 2 3