Messages

Hi Malakai.  What SD card are you using?  Once you install a new version of ML, what are your exact steps to get the bug.  Do you just power on the camera and the shutter doesn't fire?  Thanks.

I've tried several different cards. A stock mymemory 32gb class 10, Sandisc 16gb class 8, PNY 8gb class 6, 4gb generic card class 4 and a few other cards, 512 to 1gb. all having the same bug. I really dont think its the card that causes the bug. From the tests that I did with a1ex the bug isnt caused by using a different autoexec.bin because it was still happening even using the bare minimum autoexec.bin that only starts the canon FW. I dont think its the .fir because as a1ex explained the modified .fir only hooks into the stock FW to allow it to run the autoexec.bin on startup.

@a1ex or @1%
One thing I want to know is after running the eosm202.fir that allows ML/TL to run. And removing the bootflag. Does this leave anything behind? Does it revert the FW back to original FW or does it just disable the bootflag and leave some things behind?
If it leaves anything behind then this could be the reason the bug keeps coming back for me. If i run the orignal Canon Firmware update to 2.0.2 again, will this reset it back to original stock FW or have canon stopped this?

Clutching at straws now lol

"I strongly suspect this bug is no longer an issue.  I hope!"

Nope, I still get the bug. lol

Dont get me wrong, im not complaining or having a go or anything. Just seeking answers. 

so i've been doing this minimal bin for a week and i have no shutter-bug.
heres a crab:
http://www.bot-fly.com/crabbie_guy.jpg

I don't get this. Are the folks who claim they don't have the shutter bug with the 18-55mm EF-M actually bootloading and running ML/TL on the camera? The bug shouldn't be there if the bootflag has been removed as the camera is loading straight into the OFW. The custom FW just hooks in and allows autoexec.bin to run.

No, the point was to get rid of the shutter bug and restore the whole camera like it came from factory.

Anyway, made the memory card bootable once again, and only put that autoexec.bin in the root, still works like it should. But how can I tell if it really executed that file?

The point of this thread is to discuss and possibly find the cause of the shutter bug while ML/TL is installed and running. The bug comes with ML/TL and by removing it you remove the bug.

I get the shutter bug using both magic lantern and tragic lantern using all the autoexec.bin files you have been testing. Including the minimal one where all it does is start the canon FW. If i disable bootflag (remove ML/TL) the bug goes with it.

I had been working with a1ex testing a few custom autoexec.bins and magic lantern a few weeks ago, even down to one that all it does is start the stock firmware but still had the shutter bug with it. He then let you guys test it out to see what results came from it I guess. I asked for a video so I could follow your routine exactly and see if I can echo what you are getting.

@maxotics
Can you put a video up showing your process. From installation to showing the tragic lantern menu after powering camera on then taking shots without the bug please. I want to recreate your steps exactly as you have done them to copy you to see if i can eliminate the bug using your process.

Ta

Just tested the botfly 26th Sept release on two different SD cards and I still have shutter bug.

Thats ok, as long as the bug isnt happening just copy the ML, autoexec.bin and .fir file off, zip em up and post a link so i can test exactly what you have got on my camera.

Thanks

we do, can you post the files from your memory card gary so i can test them on my camera. Post them in the shutter bug thread please.
Ideally while the bug isnt happening lol

@wigglr which .fir are you using to bootload? can you share it please.

@EVVK

Did you uninstall tragic lantern before you used the memory card for something else? Watch my video in this post to see how to remove tragic lantern.
I need to check but im sure the bug stays even though you dont have the tragic lantern files on the card but still have the bootflag set on the camera.

Edit:

Ok, confirmed the camera wont even start without the tragic lantern files on the SD card. Just get flashing SD light.

I think you can assign half press to bring up a magnified view. Ideal for manual focus.

Yes, autofocus works, just no shutter activation.

No worries, only took ten minutes to throw together.
Gives folks a better idea on how to install ML/TL and how the bug is effecting it.

I uploaded a video covering the shutter bug that occurs when using either Magic or Tragic Lantern and an EF-M lens with electronic IS.

Mute the youtube music if you want. It was a silent movie

@1% + devs

I made a post here about the shutter bug. Do you think there could be anything in it?

Basically, could the shutter bug be due to the electronic IS starting before ML starts? Is there a way to make ML start before the IS or even restart the IS after it has started?
I only ask because if the power cycle or lens rotate trick are used it means the electronic IS is being restarted while ML is running thus allowing the camera to take photos.

edit: wrong topic lol

The shutter bug only occurs with ML. Not having ML on a card means the shutter bug wont happen as ML isnt running. ive tried it on everything from a 512mb card up to a 32gb card with the shutterbug occuring on every test that has ML running. That includes both the older non booting versions and the bootloading versions.

This leads me to believe the issue is happening when ML hooks into the OFW something to do with the electronic IS starting before ML as this bug doesnt happen with the 22mm ef-m. Only the two ef-m lenses with IS.
The bug is eliminated when the lens breaks contact with the camera. Either by the hard process of turning the lens or the soft process when the power cycle trick is used. by the look of things the power down routine from the camera is:

1. power button press
2. kill power to IS and close lens iris
3. run sensor clean
4. stop sensor clean
5. save final write to ML
6. full power off.

As we interupt the camera between stage 3 and 5, ML is still running on the camera and the camera has to re-establish a connection to the electronic IS and therefore allows the camera to shoot. The same thing occurs when you rotate the lens. The camera has to re-establish a connection to the IS while ML is running.

Perhaps there is a way to get the electronic IS to start after ML has started at power up?

Hope that made sense lol

@andyroo thats the power cycle fix, you can also get the same result by just rotating your lens on the body after you turned it on. Breaks the connection with the lens and body momentarily.

I outlined it here

@WiGgLr, which *.fir file are you using? Are you updating the firmware to install ML with a lens attached or not? I cant see how the card you use could cause the shutter bug.
@1% whats the purpose of the *.fir file? i appreciate its to allow fw update in the camera settings but what does it do? Does it hook into the canon FW to allow ML to run. If so what does it change in the canon FW that may be linked to the bug? Also. When powering off the camera. Whats the last write it does to the card?

Just had a quick skim of this topic, do you think you have the shutter bug sorted?

My recorded footage is between 80-100mbps on a MyMemory class 10 UHS 1 card with ML bitrate set to 2.1x... but thats not capturing RAW.
IMHO i think the read/write speed of the camera is classed at least UHS 1 because anything over 100mbps and I get buffer issues and recording stops. Canon probably limit the capture bitrate to 45mbps and use the buffer  to ensure there are less issues recording on slower cards. They should at least let you choose from a few pre-set bitrates. Just in case you have a faster card.

Am i right in saying that the EOS M only has a small (56mb) internal buffer. Perhaps this could be the bottleneck?

No.

I asked this on the feature request part and it's pretty much can't be done.

lol thanks

Heres a question. With ML on the EOS M. Would it be possible to have custom picture style files saved on the memory card and update the picture styles on the camera without having to do it via a computer?