5DMKIII 1.3.3 + Magic Lantern

Started by Kurtzva, February 24, 2016, 09:13:45 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Kurtzva

Hey guys,

Sorry if this has been asked, but I wasn't able to find any information through the regular routes.

I was wondering if a 1.3.3 version of Magic Lantern is in the works? Is it something that is possible? Or perhaps another thread I can follow for progress? Thanks!

Krisantelmo

Hi, sorry I cannot help you with this, as I have the same exact question. I've just bought 5dmark iii, and the only alternative that I've seen in forums is downgrading to an older firmware version. Hopefully someone will confirm this or help us out.

Btw, do you know what features we would lose if downgrading to an older version? thanks! :)


Kurtzva

1. Improves the AF controllability when shooting in Live View mode with a wide-angle lens (fixed focal length or zoom).
2. Corrects some incorrect indications on the "English" and "Russian" menu screens.

Very simple change log. I mean, honestly, downgrading isn't a big deal.. but I swear there is a screw loose in my head or something. The idea of downgrading just bothers the sh** out of me.

I read somewhere that 1.3.3 deliberately attempts to block ML? I wondering if that has any implications on a 1.3.3 version ML?

Thanks!

Walter Schulz

Quote from: Kurtzva on February 26, 2016, 03:34:38 AM
I read somewhere that 1.3.3 deliberately attempts to block ML?

I read somewhere pigs can fly.

chris_overseas

Quote from: Kurtzva on February 26, 2016, 03:34:38 AM
I read somewhere that 1.3.3 deliberately attempts to block ML? I wondering if that has any implications on a 1.3.3 version ML?

That was just unfounded speculation from people without much knowledge of the situation, based on the new check in 1.3.3 to prevent a straightforward downgrade to lower firmware versions. There is no deliberate attempt to block ML.

I made an initial port to 1.3.3 just over a year ago. It was fairly straightforward to get up and running initially and for the most part seemed to work fine. There was some flickering in the menus that was beyond my skill to resolve though so it's waiting on someone else to pick up where I left off before it's ready for a wider audience. Given the tiny differences between 1.2.3 and 1.3.3 I can't imagine finishing the 1.3.3 port is very high on the priority list however.

Here's my repo with the relevant changes:

https://bitbucket.org/chris_miller/magic-lantern/branch/5D3-133

My pull request (though I've since broken this when I recreated my own bitbucket repo above):

https://bitbucket.org/hudson/magic-lantern/pull-requests/605/support-for-5d3-firmware-133/diff
EOS R5 1.1.0 | Canon 16-35mm f4.0L | Tamron SP 24-70mm f/2.8 Di VC USD G2 | Canon 70-200mm f2.8L IS II | Canon 100-400mm f4.5-5.6L II | Canon 800mm f5.6L | Canon 100mm f2.8L macro | Sigma 14mm f/1.8 DG HSM Art | Yongnuo YN600EX-RT II

Kurtzva

Quote from: chris_overseas on February 26, 2016, 09:37:08 AM
That was just unfounded speculation from people without much knowledge of the situation, based on the new check in 1.3.3 to prevent a straightforward downgrade to lower firmware versions. There is no deliberate attempt to block ML.

I made an initial port to 1.3.3 just over a year ago. It was fairly straightforward to get up and running initially and for the most part seemed to work fine. There was some flickering in the menus that was beyond my skill to resolve though so it's waiting on someone else to pick up where I left off before it's ready for a wider audience. Given the tiny differences between 1.2.3 and 1.3.3 I can't imagine finishing the 1.3.3 port is very high on the priority list however.

Here's my repo with the relevant changes:

https://bitbucket.org/chris_miller/magic-lantern/branch/5D3-133

My pull request (though I've since broken this when I recreated my own bitbucket repo above):

https://bitbucket.org/hudson/magic-lantern/pull-requests/605/support-for-5d3-firmware-133/diff

Thanks for the clarification! I definitely won't pretend to be knowledgeable with any of it. I figured I'd get clarification from people who ACTUALLY did, after reading the article.

Awesome! Will check out your work!

Kurtzva

Anyone expecting a 1.3.3 ML, don't. It isn't really worth anyone's time to do so, nor is it of any real consequence to us.

I've just downgraded to 1.2.3 and got my ML back. I am now complete.

Kurtzva

Hey guys! Just a follow up question.

I've downgraded to 1.2.3 and realized that the ML version isn't nearly as recent as the one for 1.1.3. No nightly for 1.2.3 since December of last year. Is an update expected? Or is 1.2.3 a write-off too?

Walter Schulz

All active ports but 5D3.123 do have a robot builder: If there is *any* code change passed to "main branch" it will compile a new build for *all* the cams. And it really doesn't matter if the change doesn't affect a particular cam. And it doesn't stop here. In main branch you will find a tool called "cr2hdr" which is running on PCs only. If there is a code change -> New builds for all cams will be created.
5D3.123 port is not built by a robot but manually triggered by a1ex.

See https://builds.magiclantern.fm/jenkins/
and https://builds.magiclantern.fm/jenkins/job/5D3.113/changes
Each change is containing a small prefix telling which cam/module/... code is actually changed. You will find lots of changes for lua module recently but digging for changes dedicated to 5D3 will take you really back in time.



Kurtzva

Quote from: Walter Schulz on March 11, 2016, 05:47:05 AM
All active ports but 5D3.123 do have a robot builder: If there is *any* code change passed to "main branch" it will compile a new build for *all* the cams. And it really doesn't matter if the change doesn't affect a particular cam. And it doesn't stop here. In main branch you will find a tool called "cr2hdr" which is running on PCs only. If there is a code change -> New builds for all cams will be created.
5D3.123 port is not built by a robot but manually triggered by a1ex.

See https://builds.magiclantern.fm/jenkins/
and https://builds.magiclantern.fm/jenkins/job/5D3.113/changes
Each change is containing a small prefix telling which cam/module/... code is actually changed. You will find lots of changes for lua module recently but digging for changes dedicated to 5D3 will take you really back in time.





Hey! Thanks for the reply. I could be misunderstanding you. Are you saying that there hasn't been any changes made to ML specific to the 5DMKIII since December? Did I understand that correctly? If so, does that mean there are no improvements for the 5DMKIII with the latest nightlies? If ports are not done by a robot, but by A1ex, can a newer port be requested? Or does it even matter?

I ask because I'm noticing flicking when I adjust certain options. That could be as design, I'm not sure, but I never saw any kind of flickering when I was using ML on my 60D.

Thanks again for the reply!

Kurtzva

I think I might have misunderstood you.

After reviewing the change logs for the 1.2.3 nightlies and comparing to the 1.3.3 December build, it would appear that changes were made and, again, unless I'm not misreading, some features were improved/added. Perhaps they are not particular to the 5DMKIII, but an overall ML improvement?