Messages

Yes, the 2000D, that's good. Please follow:

https://www.magiclantern.fm/forum/index.php?topic=16534.0

Once you got a rom dump, please provide me a link via private short message (no public links on forum!!!). There's several ways you can start porting. Also use the search for "qemu", "stubs" etc.

You will need to get comfortable with compiling, using bitbucket (creating branches etc.) and spending private time....

70D ist stubborn due to the dual pixel cmos AF. Some focusing features are not enabled. I can't remember myself what exactly was wrong but it had been reported as non working feature and is therefore disabled. You might give it a go and enable the feature and compile a new build to test it though.

My adapters exactly are able to do it the way it is described in the following pdf:

http://evtifeev.com/wp-content/files/manual/EMF_adapter_Canon_c.pdf

Default value for the lens is 50mm f1.4 we are talking about the micro adjustment for the attached lens. This is, as histor already stated, really needed as otherwise camera would do the focus confirmation "beep" and fool you to be in focus although not being in focus. I learned the lesson myself the hard way.

Anyways the chipped adapter is also my preferred solution as I don't shoot in Liveview. Point and autoshoot via ML once focus achieved. I can't tell the advantages when recording movies - that's never been my interest.

+1 for chipped adapters. I own some which allow also focus correction for nikon lenses.

I expect it to be 20MB/s. Same for 2000D but that one at least has the new sensor with 24MP which could be indeed useful with ML for photographers. Forget about it if raw video is your primary goal.

Just checked #230 and from my experiences I can tell you that each and every instruction @a1ex provided me was as precise as possible. That said, I sometimes needed to read it twice or thrice until I was able to follow it.

Thanks!

Nik, the build is only a tiny bit broken, the merge was *much* more painful.

Alex, yes, I recall #230   I have some of that done.  But I only just realised the names are branch names in Hudson repo!  qemu, new-dryos-task-hooks, lua_fix and patchmgr are all branches that should be merged into unified? 

Yes, I know that pain, drove me crazy handling "unsupported" branches.  As you realised there are lots of branches that should be merged into unified. Becoming familar with them requires you to compile and try out on your cam. You'l need some time but I can just confirm what @a1ex said in #230. You already did some major progress IMO. Please continue.

That progress report sounds good.

That has a reasonable chance to be related to where I'm seeing the crash.  Merge is complete but build is broken as now it depends on that stub.

+1. Don't give up.

EOS 250D isn't supported by ML.
Please contact Canon support or a local repair centre. You might try to reflash firmware 1.0.2 and see what happens. That's all.

[d]

wtd - what the duck
nice job, as always

....a decent 50D body with only less than 5K shutter counts directly from an original owner...

Wow, Sean, wish 'ya lots of fun with it. Should last forever with that shutter count cause it's also built like a tank.

Guess 5d4 will be one of the hardest ones to port. So a good base for other ports. Be Sure to expect Problems like dpaf Not working etc I know what I am talking about. 80d could be easiest to start with. Check previous posts in past from me. Once there's a base For digic6+ I am Porting another one, too. Eos R, RP also welcome to start with - though still Voting for 5d4

...The Mark IV went on sale in September 2016, over 3 years now. I think this needs to happen or the project and forum will just slowly disappear as the features of the older models really isn't up to the task anymore.

5D Mark IV dynamic range score....

It's not only about the dynamic range but lesson learned that 5d's provide fastest write speed and therefore highest Resolution with best Image quality. Pro's will use it and that again is where money will come from

@Everyone: Please make some noise on other forums, social media (twitter, facebook, instagram etc.). We need more attraction and supporters for this topic. C'mon it's about the future of this great community!

Thanks in advance.

[porting ML onto 5D Mark IV]

we need to get ML onto 5DMarkIV asap. I said it earlier, several times. Announce a code freeze for the existing cameras and focus solely on digic 6+ cams. There are enough devs for digic 5 cams available. That's whats going on already on the forums for months: Devs providing custom builds for the community.

I vote for trying to collect as much money as we can for a single purpose which should be porting ML onto 5D Mark IV. Then others can use that to port new cams, too. We need to buy at least one 5D Mark IV for you, a1ex. I vote for collecting 100% into your hands. 'Nuff said - don't think about the "other" devs. We are just awaiting that capable someone to do the job - who seems to be indeed only you. Once the first digic 6+ camera is suported others will folow. But for the sake of whatever or whomever just let's start to try to collect some money / donations and first see if we will get anything which will meet the requirements to do the job. If it's just hundreds of dollars: no, thanks! It's up to you. There's no must. No one expects a port for 5D Mark IV to appear in days / weeks. It could be years, who knows?

...will solve my difficulties for the current year, it will very likely postpone them into the next year. Which is why I'm looking for long-term support.

New cams will bring new users. Let's try and see what happens.

When one door closes, another door opens; but we so often look so long and regretfully upon the closed door, that we do not see the ones which open for us.

my previous posts:
1
2
3

Wonder what will be next: 100D?

No, Mark II, Mark III, Mark...VI

a1ex do you expect negative impact for us? Mentioning ML several times in the article hopefully won't harm future research on upcoming cameras but my gut feeling says that Canon hopefully won't change anything relevant on existing cameras.

Did anyone from CP contact you?

@Canon if you read this: How about sponsoring ML, please  .

[Eye Detection AF (Servo AF)]

You forgot to mention the most interesting feature (at least for me):

• Eye Detection AF (Servo AF)

Check YT videos.

'nuff time til June May 2020. I am sure there will be a way to either archive everything (read-only mode) or migrate almost everything.

I would just try to disable touch in canon menu until you find the root cause (stub / const). It's at least possible on 100d. Do you have a pull request available? It might help others to chime in

This is probably too hopeful, but I wonder if the main thing stopping me getting into ML menus is I haven't defined the button to trigger it?  I think this is supposed to be the delete / bin / trash button, but I don't know where to find it in consts / stubs / code.  What's the name used?  Or, more generallly, what's the path that leads to ML menus, so I can debug it?

Check platform dir and gui.h in it.
Might be a good idea to copy and use that from my 100d port. You can also grep source code for 100D

Nice one. Now you just may also use several lines of bmp_printf (e.g test1, test2, test3, test4...) to write some text onto the screen and use this approch to locate code which causes trouble. Afterwards it's easy to see which stubs / consts are used around / within that code. You then either uncomment that code and see where code execution reaches (next bmp_printf) or better fix the stubs / consts first. I used this approach a lot and even still do in vb6 when i get stuck in one of my private projects

Next, enable features one by one and use same approach...

... I'm sure some of my consts and stubs will be wrong.

...

Any ideas?  I have a lot of things I can try, I'm wondering if there is an obvious route for someone with experience.

Not really followed your post history but it sounds like you should focus on consts / stubs fixing first. Running the stubtest would be a good way but it shouldn't work atm. For me it was rather easy to do consts / stubs "matching" when porting Digic 5 by comparing ROM dumps with same generaton cameras. Drop me a PM if you don't already have some digic5 dumps to compare. I can't tell if it could help with digic 6+. Your situation is rather a difficult one as you got no fully working D6+ port available to do the stubs / consts matching.

congrats! Keep up your good work.

Didn't realize that you got your 70D alive gain @OlRivrRat. Nice!

As long as you got your lessons learned - which is - keep your initial ROM backups in a safe place - there might be a chance to reflash your camera once "he" returns. I won't even ask dumb questions like "did you try the portable rom dumper" etc.