Tragic Lantern for EOS M

Started by coutts, April 17, 2013, 01:43:28 AM

Previous topic - Next topic

0 Members and 3 Guests are viewing this topic.

gary2013

Quote from: RitterRunkel on March 27, 2014, 10:58:37 AM
Hi and thx for ML/TL! =)

I'm new to ML/TL and I'm just lost in the jungle. As a newbie I've not been able to find the latest and complete guide with all options to use ML/TL on an EOS M Mark I with 2.02 firmware. All the information seems to be splitted, distributed and sometimes outdated. I was expecting a first post in a sticky thread like this one clearifying all my questions as I'm used to on XDA-forums for smartphones.

So please let me ask some basic questions here:


  • There seem to be different options to install/use ML/TL, e.g. EOScard yes or no. Will I have to flash ML/TL over the Canon firmware or is it possible to use ML/TL only by booting from sd card?
  • I read about TL having more features and being developed far by 1% without backporting all of its features to ML. But am I correct with downloading the newest TL from https://bitbucket.org/OtherOnePercent/tragic-lantern? These files seem to be outdated while ML nightly for EOS M202 is from today!? Do they even work with latest 2.02 firmware?
  • Will I have to install/boot ML first and copy TL on top of it? My research says there is no stable, RC or beta of ML, right? So will I have to download and install ML nightly first and copy the (outdated?) TL files to my sd card?

In a nutshell I'm looking for the latest and most secure way to use ML/TL, preferably as boot option and especially for using raw crop video. It already would be a great help to know which files I will have to download at a minimum (EOScard, *.fir?).

Thank you so much!

Regards: Robin
Welcome to the forum, Robin. You can get the nightly builds for TL at http://tl.bot-fly.com/  Thanx to Jerry for maintaining this website for us to get the compiled files. I just installed Mar 26th build. I have used the nightly builds everyday since last July and I have never had any problems. You can get the ML nightly builds at http://builds.magiclantern.fm/#/  They do not have the fir file, that you will need. The TL version usually has more features available. I like having the Bit Rate options and the Video Hack options.

You can find a Guide for the M at http://www.magiclantern.fm/forum/index.php?topic=8825.msg82955#msg82955  Thanx to Max for this Guide. I am not sure if it is up to date, though. I have not seen Max around here since last December.

I do not use eoscard.exe. I format the new card in the computer using fat32. I then format the card in the camera using the Canon menu. After that formats, power down the camera and put the card back in the computer to copy the nightly files. There is the ML folder, the autoexec file and the fir file. After that completes, safely eject the card (always use safely) and put the card back into the camera, power up and set the camera mode with the dial on the top to the middle position for Picture Mode. Make sure the camera is then set to Manual. Next, go to the Canon menus and the second tab from the right has the firmware install at the bottom of that drop down list. Run the firmware update. It sees the TL fir file. Be patient and at the end a screen full of green text appears. Reboot the camera and turn the camera mode back to Video.

Tap the screen with two fingers and the TL files appear. You can get to submenus and back out with a single finger tap. The first tab is Audio. Turn off the headphone audio by highlighting it and then press Set to make it say Off. That feature is not working and it needs to be turned off. 
NOTE- Please ask 1% to turn on this feature. The last time I asked, a couple of weeks ago, he said he can do it, but there has been some confusion on here between ML and TL and 1% also has some other things he needs to do. So he has not gotten around to doing that for us yet. Many of us really want this headphone feature and we hope that he can do it for us soon.

Next, go to the modules menu and click on each module and press Set to have it load up after the next reboot. I do not install the arkanoid module. It seems to be some game to play. Do not install dot tune and crypt modules. They seem to cause problems for the M. Now, go over one more tab to Debug, go down to the second row and press Set to turn on the Load modules after a crash. Reboot and your good to go.

I always delete  the ML folder, the autoexec file and the fir file from the card before installing the new nightly build. We also have a shutterbug problem. You can read up on that. I now always just run a Canon format BUT make sure you KEEP the ML files on the card by not tapping that screen. Run the Format and reboot and the shutterbug is gone. But it also reverts back to Fat32 format if you used exfat in the beginning. I have no problem using fat32 for now. The other two methods are twisting the lens off a little and back on when powered up and the other way is a quick power off and then quickly back on before the LED flashes also work. But you have to do that each time you turn the camera on.

Some people don't care about the shutterbug because they do not take pics when shooting video. I always take pics when I shoot video. For example, when I have a shot where nothing is moving. Like an exterior shot of a building and the sign. I also do not need to set up a tripod for those shots. And, grabbing B roll cutaways can usually be a pic instead of video. This shutterbug has not been solved yet.

Have fun.

RitterRunkel

Wow Gary, thank you very much for this!

Extremly helpful to me. After spending hours this afternoon (from looking for files to unsuccessfully dealing with make-bootable-scripts and other stuff) I just did what you wrote (GParted@fat32, format in camera, copying the current TL, ...) and 2 min later the firmware was found immediately and I am able to use TL now. Great!

There's only one thing I'm not sure whether I get it:
Quote from: gary2013 on March 27, 2014, 04:06:10 PMI now always just run a Canon format BUT make sure you KEEP the ML files on the card by not tapping that screen. Run the Format and reboot and the shutterbug is gone.
I think the ML files (in the ML folder) will be deleted like all things on the sd card by formatting in camera !? How to keep them anyway? Or do you mean the ML files of the flashed firmware and that I just have to stay calm by never tapping the screen while formating?

Thx again, I hope I can contribute to the community myself in the future!

gary2013

Quote from: RitterRunkel on March 27, 2014, 07:38:16 PM
Wow Gary, thank you very much for this!

Extremly helpful to me. After spending hours this afternoon (from looking for files to unsuccessfully dealing with make-bootable-scripts and other stuff) I just did what you wrote (GParted@fat32, format in camera, copying the current TL, ...) and 2 min later the firmware was found immediately and I am able to use TL now. Great!

There's only one thing I'm not sure whether I get it:I think the ML files (in the ML folder) will be deleted like all things on the sd card by formatting in camera !? How to keep them anyway? Or do you mean the ML files of the flashed firmware and that I just have to stay calm by never tapping the screen while formating?

Thx again, I hope I can contribute to the community myself in the future!
u r welcome. It is confusing because we are using TL, but the Canon firmware menu says ML. Just don't tap the screen and it will keep whatever files (the TL files) on the card and it will reformat the system. Reboot when you are done. If you make a mistake and accidentally delete the files, just start over from the part where you copied the TL files to your card.

You will know if you have the shutterbug if you are in video mode, not recording, and try to take a picture and nothing happens. Then do my trick of Format in Canon menu  keeping the ML files. Reboot when that finishes. Make sure you are in video mode, not recording and you now should be able to take take pictures.

And, if you ever get in a jam with a camera freeze, you can't power off or the LED is blinking fast and will not stop, pull the battery out and then back in and reboot.