![]() Just consider the heat budget before you try using the camera innards as a supercomputer. But if you have the programming chops and the latest camera supported by ML, with enough RAM and power, you could script a lot of the stuff to make post-processing easier afterward. Sure, it can be awkward to manage because it is not a part of the original package, so you would need to adapt your capturing and post-processing to ML. The ETTR + Dual ISO module combo, in tandem with other features ( edit e.g., enfuse stacking), make ML very compelling for DR. It is painstaking work even if you have the best and brightest and then you would have to connect to code that also needs to be imagined and developed. We are not responsible for any damages to your camera. There are lots of reverse engineering involved and investigation of hardware registers. Warning Magic Lantern is not approved nor endorsed by Canon in any way, and using it will probably void your warranty. Moreover, each hardware and firmware difference between cameras has to be considered. Perhaps there could be a pot that goes to the individual (s) who crack a specific camera’s OS. It has a nightly base with all of the possible features but not all cameras support them. Especially, is there a way to support people working on specific cameras or lines of cameras For example, the M50 or early RF mount cameras would definitely have a lot of supporters if there was a safe way to donate. Not sure if this answers your collective questions: ML is constantly being updated. Why bump such an old thread? Do you have questions yourself? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |