Messages

Hello everybody,

it looks like EOS M3, M5, 5D MkIV and maybe 80D and 1D-X MkII can
get lens correction data in three different ways:
1) Included in onboard firmware
2) Uploaded vis EOS Utility
3) Delivered onboard newer lenses

Can anybody shed a light on the format of these correction profiles?

In another discussion elsewhere a user reported the Sigma 150-600
Contemporary to be recognized by his 5D MkIV in full text.
Maybe this lens doesn't make use of a fake lens ID anymore,
rpvided that the camera supports lens profile loading from the
lens itself.

This opens new possibilities in correcting uncoupled "dumb" lenses
inside the camera by maybe building a module loader for extra profiles.

I am not a programmer, just a user with sometimes wild ideas.

Does that make any sense?

Regards, Michael

Thank you. That is to the point and clears up a lot.

Gives me food for thought.

a1ex had a good post about new stable releases, but I can't find it atm.

There is a lot of information in this forum, and most of it is well hidden...... sigh.

In the end I don't know anything more than before I asked.

1) Is a unified version possible? (Could just as well be impossible for technical reasons I have no clue about)
2) What needs to be done to buold a unified version? (That could open the track for someone with more coding skills than me)

The beauty of a unified version for people owning more than
one model EOS cameras is clear, no?

Nobody?

Frustrating. Why not drop a few lines that might lead people to help
advancing the project, if there is something that can be done?

Formulating the problem often bears the solution in itself or sparks
a good idea in somebody how to solve it.

Browsing the changelogs of the latest nightlies for EOS M,
I realised that there were many entries related to 5D3
and other cameras, not only the M. So obviously there is
a lot of code that all platform versions have in common.

Is the *.fir file the only difference of all nightlies, or ist it more complex?

Would a unified version currently be possible?

If not, what is the problem, and how can any of us help to overcome it?

I have around 200 GB in cards, and I still find myself constantly
in need of a card because it either doesn't hold ML at all or the
wrong platform version for the camera in my hand.

I have 5D2, 5D3 and EOS M.

A unified ML variant covering the 5D Mk2/3 line would be great,
and a unified version for all cameras would be a dream.

At least this would kill a lot of organization overhead and
planning headache in the use of ML.

The limitation is not the card but the card interface of the camera, sadly so.

And yes, documentation (finding it, even more) is one of the sore points of this project.

So, whatever you can do will surely be very welcome.

I'd love to see stickies with platform specific manuals maintained by
small teams of maybe two or three people.

Since this needs volunteers to help and suggesting is not doing,
my help would be available for EOS M - if anybody cares.

Not that I have a plan yet how to start. Maybe a list of all menu
entries and their limitations that the platform sets explained?

Best practices on top?

Installation and uninstallation step by step?

Available as PDF for Download, maybe plus translations into
other languages? (German: Here.)

Anybody else on board? Suggestions, comments?

Lanparte makes power supply plates as well that take V-mount or Anton/Bauer gold mount
batteries on one side and offer 5V / 7,2V / 12V and D-tap plugs on the other side.
Plug a battery dummy into the 7,2V port and you have 100 Wh power for the camera.
The 12V port can power most external monitors, the 5V port can power anything that
needs USB power.

Yes, all these share the 100 Wh when you plug them all.

Also, for those shooting stills as well, 1.2.3 fixes the AFMA bug
that was there in 1.1.3.

Okay, looks like there might be a problem.

Obviously DotTune works different for some lenses.
I ran through all my lenses, and with these reports
above in mind I remember that only two lenses completed
very fast and with a result other than zero.

I will check again tomorrow some of the lenses with
the "all lenses" setting.

Enabling info screen didn't do it alone.
So I reset all camera settings and now it works perfect.

Thank you very much!

Lens ends up at -10 constantly.


Edit: Yes, I cleared custom functions for C.Fn4.

Not sure if I'm doing anything wrong.

DotTune gives me the spirits level tool blinking 3 times and then says
"Press INFO and try again".

EF 1.2/85mm L MkI on 5D Mk3 with 1.2.3. bleeding edge from March 31st.

Switched global draw off, C.Fn.4 off, manually focussed on target in
approx 4m distance in live view 10x zoom, then started the module.

Levels tool appears blinking three times, then it exits with the message above.

Any obvious user error?

Thanks, Michael

That's a known issue and currently not clear if this can be fixed.

More precise: Currently not.

At some point in the future we might see a new unified version that
will run on a number of cameras.

We have had that before, and if I interpret A1ex right, he is currently
using a unified version for at least both 5D Mk2 and 5D Mk3.

This will likely find it's way into a new unified version. Some time.
And don't ask when, it will be available when it is finished.
I'm pretty sure that not even A1ex can say when this will be.

As stated elsewhere before:

Install with an original Canon battery or a 3rd party battery
that is not requiring you to acknowledge using it,
OR hold your fingers still and wait until the installer finishes
in the background before acknowledging the use of this battery.

Now with ML available in the nightlies for 5D mk3 running 1.2.3 I have been
musing over the following:

Since there is not yet a unified version covering both the 5D Mk2 and the
5D Mk3 I have to make sure to keep track of which card holds which version
of ML and in which camera to put it.

What happens if I screw up and put a card with ML for the 5D Mk2 into the
5D Mk3 or vice versa?

Sure, I could test. But maybe somebody has wise advice without the possible
risk of testing.

Thanks in advance.

Michael

Installed to/from CF, seems to work without any issues.

Didn't test RAW, though, my cards are all too slow.

But all the other features I've missed so badly for such a
long time with 1.2.3 are there.

FULL BLISS!

Think I need to go for a fast CF on Monday.


I'm already in heaven. Now a unified version for both
5D Mk2 *and* 5D Mk3  and I'll never need to worry
which card holds which version of ML again.

Thank you, thank you, thank you!

Edit: Installing with a 3rd party battery that asks for
permission works if you don't try to acknowledge using
the battery.

A1ex posted in the thread regarding dumping firmware 1.2.3 that he was running a
version he built for 5.2 *AND* 5.3, IF I understood him right.

My impression is that it is possible from this statement, and likely the biggest
obstacle against a release unified version today is the 5.3 bootflag problem.

If anybody has an idea how to solve the bootflag problem - come forward!

Does that mean we are approaching a new unified that holds both 5D Mk2 and 5D Mk3?

Would be like x-mas, easter and birthday on one day......

Can someone set up a platform entry 5D3_1.2.3 for these new builds in the nightlies?

While making it user friendly takes ressources from development, it also frees
resources through preventing double and triple questions about ML in first place.

Thanks everybody for your great work.

Also: What needs to be done to solve the bootflag problem?
Laying out the problems regarding porting stubs and record restart
helped chris_miller and viciniusatique to contribute.

Maybe a quick word on this could be helpful.

Regards, Michael Quack

To encourage testing and feedback, here is a 5D3.123 build.

Thank you very much for that.

You should already have the bootflag enabled with the development firmware.

Is there a way to enable the bootflag without downgrading to firmware 1.1.3 before?

Regarding the advancements by Chris_overseas - can someone please
setup a new platform branch in the nightlies for 5D3-1.2.3?

I know it is far from even being Alpha, but I am willing to give it a shot.
The thing is just that I am too far away from programming to complie it myself.

I can offer to risk my camera and to test.

Thanks to Chris_overseas there is major advancement in support of the
current 1.2.3 firmware of the 5D3, a milestone in my eyes.

I am pretty confident that the boot flag issue can be solved as well,
and that the support of 1.2.3 will definitely bring in more people testing.

This in turn might bring a boost of interest and consequently attract more
developers.

Rumors about the death of ML are highly exaggerated, to say it this way.

Another one here.

I have also offered to put in a few hundred hours, provided someone
helps me get onto the horse.

I don't mind virtually copying a telephone book by hand, do the "dirty work"
as someone worded it. But I am no programmer, have long forgotten 99%
of the BASIC and PASCAL we had in school, back when there was no monitor
but a teletype instead.

About the rude answers (or no answers at all):
This is not a commercial project, nobody has any interest in customers,
and there is definitely no community management.

We have to take it like it is and get organised by ourselves.

The stupid thing though: Obviously most of what is asked will be read, even
if there is no answer or a rude answer. I myself have asked in three or four
places about proceedings for firmware 1.2.1 and have never received any
answer but instead a warning for posting duplicate questions.
I am now on moderated status and every time I contribute to this forum,
a moderator must make the effort to look into what I write and approve or decline.

Proper community management would have told me to dig out the stubs myself
after the first question, and point me to somebody who might be able and willing
to make me fit for the job.

Yes, your playground, your rules. But I think one could make life easier for
everybody and get more help in coming forward - even for those who are
not too much interested in firmware 1.2.3.

People hear about magic lantern, and whoever buys a 5D Mk3 now will have
1.2.3 on it. The questions will not die, they will grow. Let's work together
to relief the pressure from the kettle.

Hello everybody,

geggo wrote in:
http://www.magiclantern.fm/forum/index.php?topic=7486.msg64348#msg64348

"if someone digs out all the stubs (stubs.S, const.h, hardcoded stuff in modules) that are
necessary to work on v1.3.1 and makes a pull request, we will most likely switch to this revision.
until there is no help, you have to wait till alex or anyone else takes their time to do this."

I would be willing to put in a few hundred hours, but......  I am not a developer,
have long forgotten about the PASCAL and BASIC we had in school.

That said - IF it is work that can be learned in short term I'd still be willing to put in time.

Can anyone explain what exactly has to be done, and how I can maybe help in this,
even given my sparse understanding of code writing?

Thanks for any answers.

Michael

Another one. Theater production filming for DVDs. One camera straight onto
the stage for general overview and safety shot that you can always return to.
Serves as master sync track as well.
With already five cameras around and manned, auto restart on this stage
overview camera would  be very welcomed as a feature. Saves one hand.