Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - gary2013

Pages: [1] 2 3 ... 27
And you just admitted the same warnings on ML. So, now what is the truthful way to make people not use T_? What about the guy I just mentioned who claims his loyal faith in whatever ML tells him? He based it on what ML said to scare him about being unsafe. You didn't comment on that.


Assertions are there for a reason and we don't mess with those as they could cause the camera to enter an invalid state and potentially brick.
ML warns people about using ML at their own risk and possibly bricking a camera. So what is the difference there? A double standard?

Then the EOSM thread is waiting for you.
Keep in mind that if said changes involve patching assertions in canon code they won't likely make into ML any time soon.
Assertions are there for a reason and we don't mess with those as they could cause the camera to enter an invalid state and potentially brick.
I have been to that eosm thread many times, as you know. I have supported and worked closely with anyone that has shown concern for the M. What happened to Jordan? He was suppose to fix all of this? what happened to that spreadsheet I volunteered to work on for the M and after I worked one day on it and then replied back to, what do I do now, nothing ever happened. I never got a follow up courtesy message saying thank you and why it is now dead. I forgot who it was now. Maybe nanomad.

Are you saying that 1% is now there in the eosm thread waiting to talk and work with us all? How come you guys gave headphone to the other cameras? we now have 1% willing to do it for the M. I am not the only one wanting this.


Tragic Lantern was a one way process.  The Magic Lantern developers were developing ML, and Tragic Lantern was taking these developments from ML, and developing features of it's own.
However, TL was not sharing these developments, back with ML.  Taking, taking, taking, and not giving anything back.

This is not how open source collaboration works.  ML is a development project first and foremost.  We, as users, are gifted these developments, by the developers.

During the discussion regarding these recent changes, suggestions where made, to have TL run on it's own website.  TL users are more then welcome to do as they see fit.
However, TL discussion cannot be supported on this forum.  If anyone bothers to read the OP, and consider the circumstances, beyond their own personal needs, the reasons why this decision has been made, should be abundantly clear.
I understood all of that. The big problem is constantly hearing one side say how terrible and unsafe T_ is and yet I keep saying I have used every new build everyday and I never had any problems. Yet no one from ML wants to discuss that openly and then maybe rethink their general public statements. We now have a poster (more than likely he is not an M, 6D or 7D user) claiming his loyal faith to ML and he will always believe anything ML tells him. That is sort of pathetic from my view. Maybe he missed my posts in the past about how it never hurt my camera in anyway. Probably no will will see any posts with all the T_ threads closed and hidden now. I am still wondering about this open source if old threads keep getting closed and then censored.

I am asking ML to show actual proof that T_ has caused anyone to have these unsafe things happen they claim. Because it sure has not happened here on my M camera withg every build since last July to date.

I am happy to see at least some people speaking out more on this and a little bit of discussion being made openly.

All I'm saying is that before you sign up for something, that you look at the specs and make sure that it fits your system.

For instance, I'm still running 10.8.4 on my main machine, so I have to carefully read to make sure that my specs fit the required minimums or I'm wasting my time. So that means no Red Giant Universe for me!
you're right. I was moving too fast to get the download started.

Come on about you read up what you're signing up for instead of blaming someone for posting about it?

Pomfort Cliphouse has been around for a long time, in my tests it's clunky and never played back more than a couple of frames at a time. The guys who make it never quite had a response as to why the issue is happening, and if I can't get a good sense of how well the app works from a demo, I'm not going to buy it.
Come on Mid, you can't expect everyone to know what you know. I never heard of it before and I research a lot. Probably more than most people ever do. You are probably a Mac guy, so of course you have heard of it. I bet you are more upset about something being said about Mac rather than just my request for a warning, which most people usually do. -_) Or you wouldn't have said anything. I am a PC and Mac person since the first PC and the first Mac. I am currently only PC. My post was not against Mac, just that I wasted time and handed out personal info for something that could have been avoided from a simple sentence of, BTW, it is only for Mac.

Tragic Lantern / Re: Tragic Lantern for EOS M
« on: March 27, 2014, 07:46:13 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.

If this guys had mlv instead of raw it would be great...
but i think it is a nice referent for mlrawViewer

the idea is being able to view a pool of the files on the sd  or cf card from the left, being able to view them on the right, convert the one that you see or batch convert all the files on the card to a destination folder.

color correction is not that important as i see when you digitize
Please indicate that this competing app for sale is only for Mac so Windows people do not waste time trying to get the demo and give out info with our email addresses for nothing.

I would think that the LE indicates it is the Light Edition so it would then not be 422 HQ. I personally, would want to use 444 since we are coming form a raw file that is 14 bit. One of the main reasons for shooting raw is to have better color grading with the larger amount of data it records. Seems silly to throw all the data away after shooting raw. Yes, the files from 444 are larger, but so what when we now can buy a 4 TB drive for $157 or a 2 TB drive for $80.
BUMP.  anybody?

also here,
when i used dual iso on 600d i used to have pink dots, mlviewer solved this issue...

Batch convert to cdng or prores will take this app great step forward.

PDR is solved? how is it being done?

I am not sure if this has been covered, but is there some way in your app to eliminate the pink dots we get on the M camera using raw or mlv files?

Tragic Lantern / Re: Tragic Lantern for EOS M
« on: March 27, 2014, 04:06:10 PM »
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 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  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  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  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.

Hello Gary,

My understanding is that CDNG files are white balance agnostic. What that means is that while the metadata might have information relating to what your preferred white balance setting is, it's not married to the actual image. I think that the white balance and tonal adjustments in MLRawViewer are only applied to the ProRes export.

Maybe Baldand could comment?
if i use ACR and make any adjustments to a frame in the dng seq and the sync it to all the frames, i can save it out  as new dng seq with all the changes i made on every frame. that is why i was wondering if it is possible in mlrawviewer.

Yup, if you don't need audio then .raw is IMHO superior performance-wise. On my 5D3 I can easily record continuous 1920X1288 on all of my CF cards in .raw. When I switch to .mlv, at times it seems like the camera can hardly keep up with 1920X1080 even with audio disabled.
that's a bummer on the 5d3. especially since it can record audio with mlv. maybe they will eventually work it out.

When i adjust the white balance for a MLV file in MLRawViewer, it doesn't seem to stay with the file. I load another MLV file and then adjust the white balance for that file and extract to a DNG sequence. Now when I load the first DNG seq, the white balance did not stay and it shows the white balance from the last file I adjusted. What am I missing about this?

The problem is not present in raw2dng, so try converting the MLV to legacy RAW first.
how do we do that?

You might want to read my somewhat rant-ish thread asking the same question.

I find .raw gives me better performance and has stronger existing conversion tools in the form of RAWMagic on the Mac, but if you need in-camera sound then you really don't have a choice.
I have an M and it does not do audio, which is the big reason to use MLV at the moment. So, I use raw and it is also easier to get  Pink Dot Removal from a few apps that only use Raw files and not MLV.


I opened one of the files in QuickTime.  It reads it as ProRes 422 HQ.
I opened it in VLC.  It reads it as ProRes 4:4:4 YUV 10-bit LE.  Based on comments from baldand, this is the most accurate answer.
I would think that the LE indicates it is the Light Edition so it would then not be 422 HQ. I personally, would want to use 444 since we are coming form a raw file that is 14 bit. One of the main reasons for shooting raw is to have better color grading with the larger amount of data it records. Seems silly to throw all the data away after shooting raw. Yes, the files from 444 are larger, but so what when we now can buy a 4 TB drive for $157 or a 2 TB drive for $80.

Edit: BTW, I endorse the earlier suggestion of making 'Mark In' and 'Mark Out' I and O respectively, as that is relatively standard for video prep and editing.  Again, if someone didn't read, that's what they would press on the keyboard.  Cheers!
It is also an industry standard to use the J K L keys where the K is for stop and play, J is Reverse and L is Forward. Tapping either J or L will increase speed in that direction. I think it is like 30% speed for each tap. I might be wrong, but there is a way for slow motion, fwd or rev. Maybe it is hold the K while tapping either J or L for slow motion increments in decreasing the speed.
Maybe these functions are not needed for this app. Take a vote from users if you are interested to add these functions.   

I was typing the same reply and didn't see your post. LOL
Still, read the post to see all the key commands.  :)

Tragic Lantern / Tragic Lantern for EOS M-GOP settings
« on: March 23, 2014, 07:49:04 PM »
1%, or anyone who might know, what is the difference between GOP 1 and GOP off? Are they both intraframe All i? I am using TL Mar 22.

Camera-specific Development / Re: EOSM-Updated ML for 2.02 firmware
« on: March 22, 2014, 11:57:27 PM »
Sorry this is a totally noob question, but where do I find the download that actually has the .fir file for the EOS M? I have the nightly build, but the 2.3 release doesn't have it. . . Thanks ahead for help.

1%, I sent you a PM. Please let me know when you get it.
Thank you, Gary2013.

1%, I have always been happy with what you have done. As I have said a few times now, I have never had any problems with your TL on my M using every daily build since last July. I know how you feel. I have "been there and done that" a few times in my life. Thank you very much for all your hard work.

Best regards,

Pages: [1] 2 3 ... 27