![]() ![]() Certainly, it would be much better if Black Magic cooperated to help develop an open source. ![]() If you get past any encryption, it will take months to disassemble the firmware, trace what commands and process will do what, and then fit all of the new stuff into the resources available on the camera. Third, you are not talkings about a few days. Potential is that you end up with a brick. Second, a few intrepid users are going to have to risk their cameras in early testing. I think the problem is there isn't that much demand as before because now we have the BMPCC and such.As one of two or three initial testers of Magic Lantern, I give you heads up on what you can expect.įirst, the developer is going to have to have a camera to test with. They already found ways to upload code to new camera's (M50, 80D, 5D4, etc) and are waiting for other developers to port existing code to them. The biggest problem is there are only a few active developers with not enough time. Filmmakers like Rubidium (Crimson Engine) still often use the 5Diii ML as their C200 B-cam and that's of course bad business for Canon, who'd rather that professionals settle for an EOS R or buy a second Cinema camera. No doubt Canon has already taken steps to make ML builds more difficult to port to their newer cameras. ![]() In essence, the modern DIGIC processors or sensors are much more complex and the brilliant team of developers at ML are only able to develop the software in their spare time. It's a wonderful utility that has allowed us to shoot RAW video on a budget, but we haven't seen a RAW module come to any Canon camera that was released after 2013. Magic Lantern has perhaps already reached a terminus of sorts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |