@j_szczygiel since you are a newcomer I'd advise you to read through this discussion and search the forum for other EOSM related posts. I too got this camera as an introduction to Magic Lantern and while the cost/size/performance ratio is impressive, it has some severe limitations though it has gotten significantly better since the camera was first ported.
Video shooters wanting raw will be disappointed that it will not shoot mv1080 like the other cameras--at least not yet
Still photographers who want to use compact EF-M zoom lenses will swear at the still unresolved shutter-bug
However, it is a fun little camera that is inexpensive enough to risk bricking for the experience of learning how to use Magic Lantern. In fact it already looks like a small brick.Anyone feeling adventurous?
@garry23 -- You asked for it! I put all the latest experimental stuff you could possibly want to play with into one build.
This started out with someone who just signed up on bitbucket and the first pull request was a complete firmware update from 2.0.2 to 2.0.3. I don't know who this person is but he/she did an excellent job. It works so well that as far as I can tell everything works as well as the current 2.0.2. In order to encourage EOSM users to give it a test drive I pimped it with all sorts of goodies and posted it on my bitbucket download area:https://bitbucket.org/daniel_fort/magic-lantern/downloads
If you prefer rolling your own, the branch is in my repository:https://bitbucket.org/daniel_fort/magic-lantern/branch/update-to-EOSM.203_experimental_branch
Some things are working great like crop_rec and 10bit/12bit. Other things are highly experimental like simultaneously recording H.264 and MLV. I got it working once with raw_rec (MLV Lite) but not with mlv_rec. I also defined RAW_DEBUG_TYPE which lets you select the raw type (for PREFERRED_RAW_TYPE) from the Debug menu if you want to experiment with that while testing out mv1080 video. In order to run the manual lens lua script the latest lua fix is included. Oh yeah and that bulb_nd module is something that keeps coming up in the forum. It is in the code base but not activated so let's activate it and try it out.
The download package has the ML folders inside of the zip package, sort of like a TurDunkin. That's because I also included the Canon firmware 202 and 203 files so you can go back and forth easily. You can actually copy both firmware updates to the same card--but don't mix it up with the ML-SETUP.FIR file because that won't work.
If you just want to take a peak of coming attractions, that's fine too. Going back to the previous firmware is easy. Just make sure you always do a firmware upgrade/downgrade with a freshly charged battery.
This is all experimental stuff so the chances of having something going terribly wrong is greater than with a nightly build. Though I've got 4 EOSM's and have done some crazy things to these cameras without incident.
If something starts going weird and you feel you discovered a bug do everyone a favor, reset your Canon settings and delete the ML configuration file and try to reproduce the issue before making a bug report. Learned that lesson the hard way with these experimental features!
A special note about the way crop_rec works on the EOSM. You'll need to use software that can handle the focus pixels for this format. The one that is currently working properly is Danne's cr2hdr.app
which already has a special focus pixel map file for this format. If you want to use MLVFS
you'll need to install the EOSM_crop_rec_mv720_combo_map_file
in the MLVFS application. I'm not sure if MLVProducer
has the new map file but the developer, AWPStar, is usually quick to respond to user's requests.