Magic Lantern for 5D Mark III - Alpha 3 (1.1.3)

Started by a1ex, September 07, 2012, 04:51:40 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

a1ex


wintix

as there is now a larger userbase than just you alex and no problems seem to arise, are there any hopes to get 5d3 into a stable state?

a1ex

Yes, see the 7D thread, we want to release both updates at the same time. It will take a while, because we are a bit busy at work.

I still have some random issues like camera locking up on startup or not fully shutting down, so you'll have to take the battery out after each run.

eyeland

Daybreak broke me loose and brought me back...

sicetime

With the announcement of the 5d Mark III firmware update, scheduled for April 30th, how would that affect ML?

Are people excited for the update? Should users be wary of upgrading since it may not allow ML to work?

Love to hear the communities thoughts, and as always, thank you for your hard work!

http://www.canonrumors.com/2013/04/eos-5d-mark-iii-firmware-coming-april-30-2013

a1ex

ML only works on 1.1.3 for now, but you should be able to upgrade and downgrade.

If Canon likes us, we'll be able to update ML to work with the new firmware.

eyeland

Quote from: a1ex on April 22, 2013, 04:11:40 PM
(...)you should be able to upgrade and downgrade.

If Canon likes us, we'll be able to update ML to work with the new firmware.
Fingers crossed
Daybreak broke me loose and brought me back...

bryanfieldhouse

Quote from: a1ex on April 22, 2013, 04:11:40 PM
ML only works on 1.1.3 for now, but you should be able to upgrade and downgrade.

If Canon likes us, we'll be able to update ML to work with the new firmware.

If Canon were to somehow restrict/disable the ability to use Magic Lantern  :o it would be public suicide as I'm sure many users would think twice about buying Canon products in the future. Especially when the market has so many choices of products with the likes of Blackmagic etc..

I own a couple of 550d's and a 5DMKIII and Magic Lantern is the only thing that makes them anywhere near reliable to use on mission critical jobs.

Excellent work as always by everyone involved in ML development, looking forward to the weekly build.  8)

Bryan

sicetime

So i have been saving and seeing a few options. Should I save for extreme cf cards, or invest in something like an atomos ninja and straight to ssd.

There was a notion a while ago about the possibility of using photo jpeg and getting extreme resolution and bitrates from the 5d, is that no longer a pipe dream?

If I went the Atomos route, would I still be able to load ML through the SD and record with the Atomos Ninja? I am guessing there is no way to tell until next tuesday.

Thanks!

@!ex

I wanted to report a bug I found in the nightly build on my 5D mk3 (I know they are probably full of them, but I just thought I would contribute to working toward a stable release).

When I use the HDR feature set to auto in manual mode on the camera, if I switch lenses or change shutter time for my base, first exposure the auto exposures are out of order (supposed to b 0,+,-,++,-- ect). and the exposures aren't done correctly.  I can easily fix this by going back into the ML menu after I change lenses and turn the HDR feature on then off again.  Not sure you you have experienced this before.  Pretty small bug but repeatable.

Porter

In testing out the nightly build on my 5dmark III i enabled the bootflag on my camera. I was aware that i would need to run a boot enabled sd card but my problem now is that every time my camera auto powers off it takes around a sec to reboot which i assume is the camera looking for ML files to run. Now it may not sound like much of a delay but i am expecting my camera to focus and fire as soon as i pick it up. Last weekend at a shoot i missed several fleeting moments waiting for my DSLR to boot like a P&S.

A few pages back someone mentioned that they were able to disable the bootflag for the 5dmark III. Can someone please post the fir file to disable the bootflag or any other way to disable the flag? I do run ML on my 60D and i know that when you boot ML in manual mode you can change the top dial to disable the bootflag, i've tried every combination of boot and dial changes that i can think of to no avail.

Stedda

alex, new firmware was leaked early. I can post a link if you'd like to take a look at what Canon did.
5D Mark III -- 7D   SOLD -- EOS M 22mm 18-55mm STM -- Fuji X-T1 18-55 F2.8-F4 & 35 F1.4
Canon Glass   100L F2.8 IS -- 70-200L F4 -- 135L F2 -- 85 F1.8 -- 17-40L --  40 F2.8 -- 35 F2 IS  Sigma Glass  120-300 F2.8 OS -- 50 F1.4 -- 85 F1.4  Tamron Glass   24-70 2.8 VC   600EX-RT X3

a1ex

We can't even be certain if it's the final one, so just be patient until Canon publishes it.

Stedda

No worries, I'm in no rush just didn't know if it would help out.
5D Mark III -- 7D   SOLD -- EOS M 22mm 18-55mm STM -- Fuji X-T1 18-55 F2.8-F4 & 35 F1.4
Canon Glass   100L F2.8 IS -- 70-200L F4 -- 135L F2 -- 85 F1.8 -- 17-40L --  40 F2.8 -- 35 F2 IS  Sigma Glass  120-300 F2.8 OS -- 50 F1.4 -- 85 F1.4  Tamron Glass   24-70 2.8 VC   600EX-RT X3

tob

Here is the new firmware 1.2.1 for Canon 5D MK III

http://www.canonrumors.com/forum/index.php?topic=14486.msg262450#msg262450



Fir_tool 0.5 (20Mar2010)

fileLen = 0x111a6ac
---.fir header---
0x000: modelId = 0x80000285, 0x010: version = 1.2.1
0x020: checksum = 0x77b669ad
0x024: updater1 header = 0xb0
0x028: updater1 offset = 0x120
0x02c: updater2 offset = 0xffffffff
0x030: firmware offset = 0x1ef9c0
0x034: 0xffffffff
0x038: embedded file size = 0x111a6ac
0x03c: 0x0
0x040: sha1 seed = 0x9965fc33
0x044: 0x00000004 0x00000000 0x00000020 0x00000024 0x00000044 0x000000b0 0x001ef910
0x060: 0x1ef9c0
0x064: firmware length = 0xf2acec
0x068: updater1 hmac-sha1 = 9e2a03ab26c1684fa84d551742bb05430853f24a
0x088: firmware hmac-sha1 = ca21040939b0be86bb951def34e94495d8bc8791
---updater1 header---
0x0b0: updater1 length = 0x1ef8a0. starts at 0x120
0x0b4: 0x1ef8a0
0x0b8: 0x0
0x0bc: xor seed value = 0x5185d350
0x0c0: 6d7c5aaf752d55ac7041169fc22df3e8
0x0d0: 4123f04f138d246a6725ff86f8a1a4e0b40c1c04039abfca468c726f3fb853aa
0x0f0: 113aece6c503b5e41816aae331bba221
0x100: 4d4a9a1951db9782ec8ac5d06302bab7a9f57ce317d28818a7a2df08c6998618
0x120: --- updater1 (ciphered) ---
---firmware header---
0x1ef9c0: (+0x000), offset to decryption data = 0xc
0x1ef9c4: (+0x004), offset to encrypted data = 0x7c. starts at 0x1ef9c0
0x1ef9c8: (+0x008), total firmware length (including header) = 0xf2acec. starts at 0x1ef9c0
-
0x1ef9cc: (+0x00c), firmware length (encrypted part) = 0xf2ac70. starts at 0x1efa3c
0x1ef9d0: (+0x010), 0x00f2ac6c
0x1ef9d4: (+0x014), 0x0
0x1ef9d8: (+0x018), 0xe1b9b48f
0x1ef9dc: (+0x01c), 93b9ffeb652ce01794b33b30ae8dd219
0x1ef9ec: (+0x02c), fb38f38dd22403cb34b16f95dd4e8b3c5a2c4c59ad002098ebe6229a000c84e4
0x1efa0c: (+0x04c), 66c7d7b88a0bb332125f8278c874bd7c
0x1efa1c: (+0x05c), 6cd537a78be7c5e05fb76429c879932e9704aeaf2f96c2d973c18620bd01be4b
---firmware (encrypted)---
0x1efa3c: (+0x07c)

1%

I guess no 6D huh? Big frowns... the HDMI buffer is just like on digic IV cameras.

squig

Quote from: a1ex on April 26, 2013, 07:12:05 PM
We can't even be certain if it's the final one, so just be patient until Canon publishes it.

It should be, I heard they started installing the new firmware at Canon service centres last week. They did the same thing with the MK2 24p update, I went in to a service centre and got it a week before it was officially released.

Stedda

It was left on a SD card that had just come from Canon Service.

I knew you guys usually are on the look out for firmware other wise I wouldn't have mentioned it. Right now I don't need F8 focusing or HDMI out I'd rather have ML!
5D Mark III -- 7D   SOLD -- EOS M 22mm 18-55mm STM -- Fuji X-T1 18-55 F2.8-F4 & 35 F1.4
Canon Glass   100L F2.8 IS -- 70-200L F4 -- 135L F2 -- 85 F1.8 -- 17-40L --  40 F2.8 -- 35 F2 IS  Sigma Glass  120-300 F2.8 OS -- 50 F1.4 -- 85 F1.4  Tamron Glass   24-70 2.8 VC   600EX-RT X3

a1ex

Here's a snapshot from the current source code, so you can try the latest raw developments (DNG burst, RAW histogram) and pretty much everything from the nightly builds. The feedback from the early adopters who compiled from source code was positive, I've also ran the built-in tests, and it seems OK at first sight.

Download: autoexec.bin

You'll have to enable the bootflag with the developer FIR (first post), make the card bootable (eoscard) and copy the other files from the nightly zip. It works only on firmware 1.1.3.

I'll be offline for one week and hopefully I'll get some time to try all the stuff and fix the installer. If it goes well, the next step is to enable the nightly builds.

Stedda

Thanks for all your hard work and effort. Works like a charm and will be fun to play around with!
5D Mark III -- 7D   SOLD -- EOS M 22mm 18-55mm STM -- Fuji X-T1 18-55 F2.8-F4 & 35 F1.4
Canon Glass   100L F2.8 IS -- 70-200L F4 -- 135L F2 -- 85 F1.8 -- 17-40L --  40 F2.8 -- 35 F2 IS  Sigma Glass  120-300 F2.8 OS -- 50 F1.4 -- 85 F1.4  Tamron Glass   24-70 2.8 VC   600EX-RT X3

aaphotog

Can anyone provide a link with instructions on how to compile one of the nightly builds(with a mac) so that I can install on my 5d3?


a1ex

"You shall not alter, modify, disassemble, decompile or otherwise reverse engineer the Software and you also shall not have any third party to do so."

Sorry, folks.

Pelican

Quote from: a1ex on April 30, 2013, 09:10:37 AM
"You shall not alter, modify, disassemble, decompile or otherwise reverse engineer the Software and you also shall not have any third party to do so."

Sorry, folks.
What do you mean? Do you want to shut down the ML development?
EOS 7D Mark II, EOS 7D, EOS 5, EOS 100 + lenses (10mm to 300mm), 600EX, 550EX, YN600EX x 3
EOScard, EOS DSLR firmwares, ARMu, NiControl, etc.: http://pel.hu/down

a1ex

Just wait until Canon posts it without a non-RE clause.