Messages

Doubt.
Hic Rhodus, hic salta!

Hehe. Would love to. Give me a working 5D4 ML and you might see a video or two, why not a whole playlist with ML videos from me

A little step for the devs, a huge step for 5D4 humanity! )

Good news - 40D boots the GUI in QEMU, just like most other EOS models!
...
Also compiled ML from the rufustfirefly repository and got a half-working Space Invaders clone (menu appears when pressing delete, navigation keys are working, fonts don't seem to work):
.....
Happy hacking!

Lovely! MORRAL KOMBAT is next! )

Joke aside! This is a great news! After all these years it would be lovely to have a working 40D with advanced functions available. Even though my 40 D got so broken to the point its repair cost is the same as buying a second hand 40D. But I've got a friend who's hobby is photography and he got the same body.

I hope for the best!

No, that's your interpretation. I'm suggesting if there is no ML for his cam he should act like there will be no ML for this cam ever.

OK. And are there any newer cameras reverse engineered then?

[dying]

So don't hold your breath and read my advice: If there is no ML for your cam act like there will be no ML for this cam ever.

So are you suggesting that the ML is slowly but surely dying?

Video is always better than text these days indeed. :-)

Even after all this time.... Here things are as stuck as they are on the 5D4. Why do I pick the wrong for ML camera :/

Leider "noch" nicht :/

And Digic 6 is around us since 2014, November (7D2) and a generous offer (750D for free) for anyone willing to port a 750D is still open. Only lately we saw substantial progress: Bootflags for Digic 6 cams. 
So: What do you expect? If you have any ideas we all will listen ...

So if I understand you correctly - the issue is that the Digic 6 (5D4 is 6+, which I hope wouldn't be that different, or?) is still not reversed? Even after 3 years? :-( How unfortunate! This is really unpleasant. And canon's firmware is so not nice as yours.... :/

Sorry, unable to decode your request. Rephrase, please.

We are beyond 1st year of 5D4.

5D3 is still the hot topic around and I find that for normal. The majority of people still are happy with 5D3 and see ni reason to update. In the context of Nikon D850 however ML will begin to seem outdated

Dev's time is neither cheap nor in abundance. Ergo new serious recruits would be a fresh and good idea.


Sent from my iPhone using Tapatalk

I think whoever takes and explains something to the community is adorable. 

However Inalso believe that even though he took of his time tomerite his explanations down you devs have also made that software. I think it would be OK if he shares 10% of the profit with ti help to cover at least the forum hosting server expenses and domain fees.


Sent from my iPhone using Tapatalk

A1ex, as I remember you somewhere shared that from the core developers nobody has it - ergo no development...

Perhaps a little more asking from your side around in your own forum  would speed it up.

1 year after its release - nobody even has began it according to my understanding. I would love to help, but I am a noob compared to you Gods of firmware code.


Sent from my iPhone using Tapatalk

Canon Announces Clog for Mark IV!

https://www.usa.canon.com/internet/portal/us/home/explore/see-legendary/canon-log

And no wifi GUI improvements :/

I hope ML will manage to hack it sooner than 5D3.


Sent from my iPhone using Tapatalk

Well there you go!  You already have it with 5D4


Sent from my iPhone using Tapatalk

I think I know it. But I mean an own ML app (again open source).


Sent from my iPhone using Tapatalk

Are there any plans to write an ML app (ios, android, win) for remote control via wi-fi and regular tethering?

The current app Canon connect 2.0 is clumsy for 5D4.


Sent from my iPhone using Tapatalk

Nobody knows.... as it seems. A dead end :/

So is it working? :-) Sorry not quite clear for me 

True. :-) But why would be there such huge fallback in all firmwares? I mean since ML does it, then it's possible to view histogram and zebra highlights based on RAW and not on JPG.

Why with firmwares it's always JPG analysis and representation? Battery drain, image processor (most probably not)? Why do they keep using the embedded JPG?

There's another thread for the processor being hacked. It's about the same ML.


Sent from my iPhone using Tapatalk

Thank you guys for the answer.

I hope other n00bs will also find this topic and the corresponding link to the branch in question. :-)

Hi everyone.

The best article/post on the subject so far. Thank you very much for taking the time posting it. :-)

Question: I understand that the analyzed data e.g. DR, histogram, ETTR goal, etc. are displayed based on RAW. However the image itself when shot - is its jpg preview as in the regular firmware or it's the RAW file?

I am asking because as bad as the camera display could be, still one could better judge the results if it's (trying to represent at its best) the raw actual image and NOT the discrete contrast and compressed jpg version. The feedback would be great.

So is ML displaying the RAW image or (its closest representation) or it's also dealing with bad jpg version of the image?

Thank you in advance for your answer and excuse my limited knowledge on the subject.

Haha... Did I wrote that with the betas....   Damn! :-) I got pawned by a developer of course...

What is the usual way of initializing re-porting when new body comes out? I have you, guys started? What is the the implementation process for LM?

:-)

Hi everyone.

When can we expect first betas of 5D4 port? :-)