Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
A few more wins for the BM is it's awesome color science, BRAW, and it's beautiful highlight roll-off. You can get the roll-off there with ML, but BM renders that transition SO much better than Canon, even on their cinema lineI like the rolloff of my 5D III RAW better then my ursa mini pro, let alone my pocket 4K. I also like the color science of canon more. But thats just personal taste offcourse.
BTW, after playing a bit with M and M50, I started to wonder what's the purpose of all other Rebel cameras on the market. Do they have better battery life, or...?True the only camera's from canon that matter atm are the 5D IV and canon eos r. Hope ML will run on either soon
Hi there,Awesome news! Having big hopes on you robotron!
this is my first post here, but I've been following both the 80D and the 5D IV threads for a little while now, since I just upgraded from an 80D to a 5D IV.
I'm a computer science student and am willing to spend some time on this, and think I could help a little bit. My 5D IV runs v1.1.2, so I'll start by updating the codebase to the new version.
However, I've got finals coming up in a few weeks and won't be able to work on this until late February.
Hope I'll be able to help!
If you click the quoted link, you'll see some details about this process, including how to try and review it in QEMU. To try it on the camera, I need to prepare a custom FIR; this being a somewhat risky process, I'm not going to make it available for everyone without testing.
This step will let you compile current ML code from source and run it as "autoexec.bin", rather than FIR. Expect outcomes similar to previous FIRs, i.e. the proof of concept code (e.g. logging, saving the raw data necessary for DNG frames in LiveView, possibly taking still pictures and so on).
One thing I forgot to mention: I'm only prepared to run this test on firmware 1.0.4. For latest version, the following task is still open:
Maybe some of you can find some time to look into it during the holidays, as I've got plenty of other stuff to catch up with.
This particular test (enabling the boot flag) is a little more risky than all the others, because it will modify the ROM. So far all other models were OK (including 5DS, 7D2, 80D, 750D, 760D and also a 200D tested privately), but obviously that's not a guarantee. Of course, if anything goes wrong, I'll do my best to recover it, but that's not a guarantee either.Ok greats lets get this going. How can I perform this test? Exactly? What dump should I download? Install it on a CF/SD card, plug it in a 5D IV, boot it? And thats it? Or are there some extra steps?
Isn't it more interesting to invest in developing ML for EOS R? It is mostly the same as 5d4, but with more interesting photo and video features, like: eye tracking, rotated screen, separate video and photo settings, new processor, focus peaking, etc. And due to a new RF mount (fully backward compatible with EF) - more future proof modern camera..No, the dynamic range of the 5D IV is better. Which is for me the most important aspect to upgrade my 5D III (and 60FPS full hd RAW would be great as well). Most users of magic lantern, dont use autofocus anyway. They use it for more filmic stituations like commercials or shortfilms, where you have time to create your shots and not your everyday event shooting type gigs.
