1/8/2024 0 Comments Magic lantern t3i![]() ![]() ML is under ALL circumstances an "experimental" Hack, use at your own risk.ī. Its not something a narrative film maker is overly concerned with, because with Magic Lantern, you know when something is going haywire, immediately, and you just do another take.īut as to event work, I would be damned sure I had thoroughly tested the version, and knew the pitfalls before I used it.Ī. I have had plenty of problems with many versions, but I have never come close, in my mind to bricking a camera. Ultimately, you h ave to decide whether the risk of some undiscovered bug that will brick your camera is worth it. But I have one favorite in the new versions, and that is the inclusion of a false colors mode to help you set usable exposures with a minimum of hassle. The other features are extra and most of the time I disable those. But when you can't do that, and you need decent sound, in camera, Magic Lantern is the thing you will probably have to learn to use at this point. In many situation I work my way around sound problems using double system sound and Plural Eyes. To me, the necessity for something like Magic Lantern was the sound issue. He has been doing it mostly on his own, and dealing with school too. In the meantime, on the 5D side, Antony Newman was developing a new 5D version that has some very nice stuff on board. Add to that the fact that Alex over there seemed to turn out a new version twice a week, the versions never had a chance for extensive testing before the next version was out. As a result, the potential for conflict in the systems increased. The developers of ML for the T2i took off from there with a fast moving campaign which added more and more bells and whistles. At that time, the product was very basic, and only did a few things, and as a result, was eventually stabilizied. I was one of the original testers of Magic Lantern in the 5D when Trammel Hudson was first developing it. I don't care who runs what, I just don't have a "dog in this hunt", but the "true believers" ought to be trying to find this guy a REAL solution that addresses his full problem. He was stuck with the last "trial" modification and cannot even go back to original firmware version. When Tram Hudson hit that "limit" his 7D stopped accepting further updates. They stopped ML development for the 7D cold by incorporating a firmware update counter along with a counter limit in a firmware update. But they didn't and they do not like having their code in the firmware altered or "reverse engineered". In addition they may refuse to do any repairs even on a paid basis.Ĭanon should have included the features ML adds. And chances are if he sends his camera in to Canon for warranty service, they will find the ML changes in the firmware (the "bootflag" that makes the camera look to the media for the ML files) and they will likely declare his warranty null and void FOREVER. This is irrelevant to the guy who is experiencing a problem. ![]() They are quick to point out "I have run this without any problems at all". ![]() Every time we see a report indicating some malfunction, failure, or instability under ML we have the "true believers" posting something like this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |