Trivial example: I could not find one of the stubs (GUI_Control), so I wrote a function that did the same thing, from scratch. I mean, porting ML is no longer going to be "just" pattern matching there will be parts of the code requiring wrappers or other "creative" solutions, not required on other models. It has some bits from PowerShot firmware, which makes it a bit different from all other EOS models. Again, a1ex observes, further down thread: the dSLR code the ML developers are familiar with whole sections of code they're used to being able to rely on aren't there. Keep in mind, this will be a far more difficult port than with the dSLRs, because the M50's code is based in part on the Powershot code vs. Stick to whatever's posted in the main builds, and if there isn't anything for your specific camera body, then wait-or contribute-until there is. If you cannot actually follow the developer discussion from where you grabbed the file, do not load it, it is not for you. Just grabbing whatever files you can find on the MagicLantern site's discussion board threads and loading them is A Very Bad Idea if you're not a firmware coder with the appropriate knowledge and tools to unbrick your camera. There is no official ML build for the M50, yet. If the autoexec.bin doesn't exist, nothing happens.
Magic Lantern uses a boot flag to tell the camera whether or not to load the autoexec.bin from the Magic Lantern build after loading the regular firmware. Please find the FIR file for enabling the boot flag on the EOS/PowerShot M50. This is very clear when a1ex wrote just above the file link: IT IS NOT A MAGIC LANTERN BUILD it is a developers' tool that allows a coder to change the boot flag so their camera can load their code for testing. What you downloaded and put on your camera was simply a piece of firmware that allows you to change the boot flag of the camera.
0 kommentar(er)
