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] 4 5 ... 27
Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
« on: March 15, 2014, 05:42:46 PM »
Gary, quick you run the .fir every time you change a nightly build?
no, if i did i would have to reformat every night to get rid of the shutterbug. I sometimes (not very often) try and do a full install from scratch.

Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
« on: March 15, 2014, 03:10:23 PM »
For example, it could have to do with the timing of reading TL from the card at load time. When you format the card in camera, it may copy the files in a linear fashion (whereas your computer may not unless you copy one file at a time) and thus you have a repeatable read time. Difference cards have different read speeds. The same card written to different ways has different effective read speed. I believe one user had the bug without even having TL on the card, but i had previously been on the card (the card had the flags set, which may cause the camera to change it's timing by searching for autoexec.bin). Timig caused bugs are a bitch, and the SD read speed is the only real variable we can effect here.

Which could easily be the timing of when the firmware lodes and when it first reads the lens.
Then why can I get rid of the bug just by performing another Canon format in camera keeping the ML files installed? Logic tells me the ML fir is doing something and the Canon reformat is fixing what was changed by ML. I don't think it is the read speed cus my Sandisk is above the average 37mb/s (some round it off at 40 mb/s write) the M camera can handle with read/write to any card. My card is 45 mb/s read and write, more than what the M can use.

Tragic Lantern / Re: EOS M Alpha shutter-bug discussion
« on: March 15, 2014, 02:57:06 PM »
I do not recall that poll ever being taken. Most of us just replied with what we have tried for cards. If someone can prove it is the cards, then I think it is important to have many different people reproduce this fix. I can reproduce the problem right now just by reinstalling the fir file. I have used a Komputerbay 128GB, I think it was a 60 mb/s write. That was my first card. Then I bought a Sandisk 32 GB, 45 mbs write. I also have a Micro Center 32 GB 15 mbs card. None of them got rid of the bug.  I did try the minimal autoexec that Alex asked me to try/test back when, I think, Malakai said he had no bug with that minimal version. I reported that the bug still showed up.

I hope someone does come up with a real fix that satisfies all lenses (and cards) on the M. And, as an afterthought, make sure you try using the USB cable with your M to your computer at least once with installing some picture styles or/and transferring files to the computer hard drive. I think someone said they had no shutterbug and they never used the USB. Max said he never used the USB but also had the bug. Go figure. 1% and I had many discussions about the USB also causing the camera to hang and require a battery pull and he said he thinks that the USB problem is maybe somehow also causing the shutterbug or they are tied to some common thing. Nothing was ever resolved on those problems or theories.

Camera-specific Development / Re: EOSM-Updated ML for 2.02 firmware
« on: March 15, 2014, 08:47:47 AM »
Not sure where to look (have a screenshot?)

Here it shows Built on: 2014-03-15 and the file is named Mar15.
Here is a current screen grab from
and the actual file has a name of Mar 15th.

EDIT-how do I directly put an image file to this post? I see the icon for add image, but then how do I get my actual PNG file in here between the [ ] ?

Camera-specific Development / Re: EOSM-Updated ML for 2.02 firmware
« on: March 15, 2014, 08:16:47 AM »
ML EOS-M Nightly builds are always now having different dates shown. For example, tonight's listing shows Mar 14th and after the download it shows the file as being named Mar 15th. This can be confusing at times where I think I don't need a download when I actually do need to get it. 

Camera-specific Development / Re: EOSM-Updated ML for 2.02 firmware
« on: March 12, 2014, 10:57:16 AM »
Have some screenshots?
MY bad. I think I just found it. I accidentally set the wrong thing in the Debug page. I usually set line 2 on to load all modules after a crash and I had line 1 turned on instead which is Disable all modules.  :(

Camera-specific Development / Re: EOSM-Updated ML for 2.02 firmware
« on: March 12, 2014, 10:47:43 AM »
I just tried the latest version, Mar 11 ML, for the M and I do not have the mlv/raw listings showing up in the menus even thought the modules are shown to be loaded correctly.

Camera-specific Development / Re: EOSM-Updated ML for 2.02 firmware
« on: March 11, 2014, 01:50:51 PM »
there are now two listings for the ML nightly build EOS-M. The  new one says Cleanup. Which one are we suppose to use? What does Cleanup mean? That it still needs too be cleaned or it is cleaned up and preferable?

Tragic Lantern / Re: Questions for those who have (had) the bug
« on: March 11, 2014, 02:45:42 AM »
My EOS-M arrives tomorrow, so I am getting ready. In preparation, I have have read through this and the entire 96 pages of the Tragic Lantern for EOS M thread. I am in no way a programmer, but I am a professional troubleshooter (i.e. computer consultant).

What jumps out at me from this thread is that there is no good data on the problem. There seems to be a trend that points to the biggest culprit being the SD card, with some other variables contributing (I love multiple trigger-point problems). What don't have is a statistically significant dataset.

I have two questions for those who have encountered the bug.

1) What brand and model cards have been tied to the bug?

2) Did you use EOScard or Macboot to set the flags?  (which would depend on Mac or PC or Virtual Machine) Are there other choices?

There are vast differences between brands of cards, plus the industry is awash with counterfeiting. There could be a significant difference in how cards behave and between read speeds.

EOScard or Macboot (or both) could have a bug or simply a difference in how they set the flags. I know from experience that there are places that can be written to on a drive that reformatting will not touch.

It would be helpful to narrow down or eliminate this variable (say, the problem goes away with Sandisk Extreme cards, for example)

I will be using a 16GB Sandisk Extreme 45MB/sec card (that came with my 6D). I'll report back

(edited for typos)
There is more than just one thread for EOS-M/TL. There is one just for the shutterbug and another one for the pink dot removal/PDR. Possibly more, but I don't remember at the moment. The shutterbug is not related to certain SDcards. It was random. That was the problem, it was all very random based and hard to nail down to a final fix. I have not seen any talk about the shutterbug for quite awhile. It is for sure related to the EFM STB lenses. As you probably read in all the posts, there are two ways to get rid of the shutterbug, but only for that session. When you reboot, it has reappeared and requires another lens twist or quick power off/on. My third way makes it go away all the time, but I lose the ability to use the EXFAT format. I do the internal Canon reformat/keep ML files and that formats it again back to FAT32. But it gets rid of the shutterbug for me. I have used Komputerbay 128GB card and I now use a Sandisk 32 GB/45 mb/s write card. I have seen on here other people using the Komputerbay cards. I have used eoscard and not used eoscard and it seems to not make a difference for me. I don't know for sure.

I think the shutterbug has something to do with ML/TL when it boots and how it talks to the lens since a lens twist off/on resets something and the bug goes away. Same for the quick power off/on. You do that before that LED flashes and the bug goes away. Something in ML/TL is happening at that time causing the bug. I am not sure why my way of using the Canon reformat gets rid of it. 

mouse cursor disappear after resize application window.

I also saw that happen here yesterday trying the latest 1.1.2 ver on my win 7.

Share Your Videos / Re: Underwater video with Magic Lantern
« on: March 10, 2014, 11:29:05 AM »
very nice footage. thank you for sharing.

i have the latest win 7 ver 1.1.2. Is it just me or is anyone else having trouble reading the new mov/dng icon? I have yo lean in closer to read it all the time.  :) Can you make the text whiter and a little larger? The other items are easy to see since the are bigger simple graphic symbols.

Camera-specific Development / Re: EOSM-Updated ML for 2.02 firmware
« on: March 10, 2014, 04:26:44 AM »
Should be in one of the next nightly, and the button to hold is INFO on the M
which nightly build? ML, TL or both?

General Chat / Re: What raw mode records sound?
« on: March 07, 2014, 05:11:34 AM »
Sorry.  I'm a DP and don't have the depth of knowledge to know how that works.  I googled it, and it just sent me here.
check out this thread for MLRawViewer. The first post has the app you can download that lets you view raw files as well as creating a ProRes 444 file from a raw file on a PC or Mac.

here is the download link for Windows version of MLRawViewer.
Download the zip from

Remember that to use this raw viewer app, you have to drag and drop a raw file you recorded on the camera on top of the exe file so it opens the viewer. trying to open the exe file does nothing.

EDIT- I forgot you are on a Mac. I am sure someone on here can help you with that. I am currently using a PC. There is a Mac version there to download as well.

Well gents I admit it.... I am just not smart enough to decode the specialized Language, find all the correct files, go through and understand the implications of the multi-stepped install on the E0S-M.
I have been through it all just like you and everyone else has had to do. Yes, seems very frustrating and all over the place. But, once you see and know, it all seems rather simple.

This is a good community and many of us are here to try and help each other. So always feel free to ask anything and do not feel like something might sound  stupid. we all ask stupid things now and then. Especially starting new here.

If you are going to use Tragic Lantern, which is what I always use, then use this thread for the EOS-M/TL.;topicseen

In case you do not know, you have to use two fingers and swipe on the camera LCD display to open up the ML menus. And inside ML/TL menus, there are submenus that you get to by tapping the screen with one finger over the item listed. Such as the menus for raw recording. You press the Set button (the center button on the back inside the dial) and it turns raw recording on. Now tap with one finger on that raw recording item and it opens up the submenus to adjust the settings for raw recording. Tapping again with one finger brings you back out of the submenus. Pressing the shutter button gets you out of ML/TL or wait 10 seconds and it always shuts off ML/TL menus.

Have fun. :-)

OK--I've got to confess that I skipped this step and it seems to work fine. I'm using a Lexar 64GB 600x speed card that the camera formats as exFAT, don't know if that makes a difference.

Finally, copy autoexec.bin and the ML folder to your SD card. You can delete EOSM_202.fir, it is no longer needed.

Now a couple of questions for the experts. I just checked the nightly build for today and it is still missing the EOSM_202.fir file that is essential for getting started. Should this be reported? Also, I didn't do anything to make my SD card bootable yet ML loads and as far as I can tell it works. I thought I read some instructions saying that running EOSM_202.fir in the firmware update step makes the card bootable. Is this true or false?

I did not use the eoscard.exe on my 32gb Sandisk 45mb/s write SD card and it works. I format the card on my computer with winnows 7, then again inside Canon. Then I add the nightly TL build on my computer to the SD card each day.

The fir is always in the TL builds and the ML builds do not have it. It is not needed to report this. I always keep the fir file on the SD card cus I test a lot and I sometimes need to use it again.


General Chat / Re: What raw mode records sound?
« on: March 07, 2014, 03:32:12 AM »
Just to confirm, the 14 Bit Raw mode is the only one that records MLV, right?  The older format was .RAW?
First we had .raw format. Then they developed a new format called .mlv that also records audio on some cameras. They both are 14 bit.

Take a look at this thread. The second post has a lot of information about these formats.;topicseen#msg105345

General Chat / Re: What raw mode records sound?
« on: March 07, 2014, 02:11:02 AM »
What raw modes record sound, if any?  Also, I heard that the original raw mode was 14bit and now there's a 14bit option.  What's the definitive word on that?

Howdy Slim,
I am surprised you survived in Dr. Strangelove.

MLV is recording raw on certain cameras. I am not sure about any option for bits.

Tragic Lantern / Re: Tragic Lantern for EOS M
« on: March 07, 2014, 02:04:06 AM »
It has to be coded but the big thing is that wav recording seems like it won't work. The camera hangs if you mess with the asif. So the best would be audio for H264 + headphones through the USB jack.
audio for H264 + headphones through the USB jack. i would be very happy to get that for now.  :)  Is it possible to also get the meters to work during setup before we record H.264? Maybe you or someone else can work out the wav recording for MLV later on.

Having the headphones for H.264 would be very helpful since I can then hear whether the mic battery starts to crap out or something else is sounding wrong during an interview. Like a person pops the mic or they accidentally knock the mic. I could then repeat the question to get another take. Also, listening to the sound on playback to double check. 

General Help Q&A / Re: Disable Magic Lantern's White Balance?
« on: March 06, 2014, 09:08:17 PM »
Does anyone know if there is a way to disable Magic Lantern's auto white balance feature? In our studio, every time a camera operator presses set from within the white balance menu, ML begins auto white balancing, with inconsistent and unsatisfying results. Some times it also screws with the G/M shift. Magic Lantern is fantastic, but this is one feature we need to disable... At the very least, we'd be satisfied with disabling its access to using the Set button, if that's the workaround.

Please advise! I've been Googling for hours and haven't found any answers about this...
what camera are you using and what build of ML or TL? Are you talking about pictures, or video using H.264 recording or raw/mlv? Are you setup to use all manual or some auto functions?

Tragic Lantern / Re: Tragic Lantern for EOS M
« on: March 06, 2014, 08:59:35 PM »

Lately I have I heard a lot of talk about audio with MLV. I just read your reply on the thread about the differences between Raw and MLV and I was thinking the same as you that the first thing I think of is Raw has no audio and MLV has audio. The M is still one of those ML/TL cameras with no audio features, such as audio meters for setup/recording, no headphones output and no MLV audio recording.

I have stayed off this topic since the last time I asked which caused a problem. I appreciate all your work for the M as well as all the other developers. I have been here everyday, testing every build since last July for the M. I try to help others with questions I know about, hoping it will help devs spend more time on what they are doing instead of having to answer questions.

Can you please tell me the status with audio for the M? Is it being worked on or has it been put on a shelf for later development? I feel it is the one big thing the M truly needs. Not only for MLV recording, but at least for H.264 recording and playback using headphones. It is really needed for doing things like interviews and checking playback. I do not want/need to use more external gear as a workaround when I can get the results from the camera by itself. I just can't listen to anything during recording and playback. The main reason I got the M was for it's very small size and high quality APS-C sensor. Perfect for run and gun and the ability to look like a tourist so as not to draw any attention. Adding more gear just for audio monitoring defeats the main reason I use this camera.

Best regards,

Yes, for the play icon this is the case. But it isn't for the other state icons like frame dropping & colour mapping. Those need to show the current state. The design decision I made was for all the icons to consistently show the current state.
So, the button with the arrow icon indicates the clip is playing, as well as we can see it is playing and the frames numbers are changing at the bottom. What icon do we now click on to make it stop since there is nothing that shows this? Anyone else who knows the answer cannot reply.  :) And, when the clip is paused and the well known symbol for pause is showing (a box usually means to stop), what icon do we click on to make it play the clip since there is nothing that shows indicating play?  :)

I am just trying to point out some logic and what is intuitive. Keep up the good work. Many people, and my self appreciate, what you are doing.

I understand, as I had to think for a while when designing this.

The model I went for is for all icons to consistently show the current app state rather than another state you can get to by clicking that icon. That means the play icon shows the arrow when playing, not when paused.  It also means the icons can have more than two states (like the colour mapping).

On windows you should set the file associations for .MLV, .RAW and .DNG to the mlrawviewer.exe so that you can just click on the files to be opened automatically in the the viewer.

Make one copy of the MlRawViewer_1_1_0 directory, for instance in "c:\Program Files\"

Then find an example MLV/RAW/DNG file, right click, select "Open with" then "Choose default programs..." from the sub menu. Click "browse" on the dialog that opens, then find and select the mlrawviewer.exe.

In case this doesn't work for you (I've had problems in Win7), find the mlrawviewer.exe, right click and "Pin to taskbar", and drag the MLV/RAW/DNG file to the taskbar icon to teach Windows about the association. After that, you should be able to set the defaults.

It's primarily a real time player for MLV/RAW/CDNG files, which does not require the files to be converted first.
It can also convert marked regions of the files to ProRes (click the red button or E key).

More features may come in later versions.
thanx for the reply. about the play/pause icons, it is obvious that the clip is playing by seeing it playing in the window and the frame numbers are changing as it plays to also confirm it is playing. So, do we also need to see the play arrow icon to know if a clip is playing? :-)

Tragic Lantern / Re: Tragic Lantern for EOS M
« on: March 04, 2014, 07:57:37 PM »
Hey sorry but i tried upgrading but when i plug in my eos m nothing on the menu is clickable on eos utility except monitor folder. How can i install Cinestyle?
Maybe you did not follow the steps or you do not have the camera in the Manual Picture Mode.

Here are the steps for anyone that needs to know. Make sure the camera is off and not plugged into the USB. Make sure the camera is set to Picture Mode set to Manual, not Video Mode. It is the dial on the top of the camera and it has three positions. You want the middle position. Now plug the USB cable into the computer and then the camera. Then turn the camera on and your computer will show it is connected.

Now go to the EOS Utility Main Page and select Camera Settings. Then select Register Picture Style File. From that point it is obvious. you have three tabs on top for the three slots of picture styles in the camera. You load each new picture style, one at a time, into User Def 1 or 2 or 3. Click the button to the right to navigate to where you have the Cinestyle file saved on your hard drive. WAIT until it is done loading. Then do User Def 2 and 3 if you want to load anymore styles. Remember to wait for each User Def to finish loading. When it is all done, turn the camera off and then unplug the USB cable. Now your picture styles will be  available on the camera.

Thanx for all your work on this app.

the play and pause icons seem backwards to me. i expect the pause icon to show while the clip is playing and the play icon to show when the  clip is paused. most app works like that.

when I click on the exe file, i expect the app to open up and nothing happens. i see that i can drop a file onto that exe and then it works. am i missing something on the way this works? i have mlv files in separate folders. do i have to copy and paste your exe to every mlv folder and then drag n drop on it? that seems to be a tedious way. isn't here a way to just open your app and then use an import function of some sort for single files? groups of files?

again, excuse my lack of understanding on this, but what else does the app do? It seems to only play back mlv raw files, some brightness control and color adjust. but then what? can i extract dng's? make prores proxies? i don't see any more menu items , drop downs or right click menus anywhere.

Pages: 1 2 [3] 4 5 ... 27