Doh, well spotted, teach me to skim through the manual lol
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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.
Show posts MenuQuote from: Walter Schulz on May 16, 2016, 06:53:09 PM
Source? Link, please. It's nonsense because 80D will force UHS-III cards into UHS-I mode and some cards (Sandisk ...) will be outperformed by fast UHS-I cards. See www.cameramemoryspeed.com
Quote from: santeri on January 04, 2014, 09:49:09 PM
Any news regarding the issue? Since there's been no replies for a good while I assume not, but as an EOS M owner myself too, I'd of course like to see this get solved. I would love to have focus peaking!
It seems weird that the bug appears also when TL is not loaded but the loader is used to fire up canon's code. The thing that with the 11-22mm objective fully extended always manifests the problem and fully retracted (storage position) doesn't, tells it very likely has something to do with the lens initialization and it might be very sensitive to timing at the first power on of the camera. I assume with the 11-22mm it's almost the same there was no lens installed if it's retracted.
How much does the configuration with minimal autoexec.bin add to the startup time? How long does it take from the power-on to the jump to canon code with TL versus without TL?
Could it be just that Canon's code works with pure chance, the code is just magically waiting at the correct location / done some required initializations if only clean Canon firmware is used? When TL adds a bit of code to the startup, the lens has done it's own stuff before Canon's code reaches some point it should've been at a few milliseconds before and thus won't work.
I might possibly find the answer to the next question by searching a bit, but I'm just going to ask.. Is the power to the objective hardwired or can it be controlled from the software? Could the objective power on command (or some other thing that tells the lens it is attached) be removed from the startup of Canon firmware and make TL command it after everything else has loaded properly?
Edit: Just an idea, if the above would be true, it could mean that with clean firmware, no TL, the bug could be reproduced by having the lens a bit loose, powering on, and very quickly (almost simultaneously) turning the lens so it gets contact. Could be almost impossible to get the timing right of course..
QuoteWith its existing firmware the EOS M can't recognise when the lens is in its retracted position, and will allow the shutter to release. Canon recommends updating the firmware to the co-announced Version 2.0.0 for full compatibility, which as a bonus promises faster autofocus with all lenses.
Quote from: gary2013 on November 03, 2013, 10:19:06 PM
Malakai, I am just curious if you still have the shutter bug? I have not had it now for almost two weeks.
Quote from: gary2013 on October 16, 2013, 03:08:49 PM
Alex and 1%,
You asked for ways to replicate the bug and I think I have found a way. I also figured out how to get rid of the bug. I mentioned here the other day I did not have the bug again. I added the modules one by one and I eventually had all the modules loaded and I still did not have the bug. Even after typical use of the camera recording raw and taking pics using the EFM 18-55mm lens.
I got the bug again last night when I used the USB cable to transfer files and load picture styles. When I unplug the USB, the camera would not shut off as I have mentioned here before. I have replicated that using the USB will always add the bug.
I got rid of the bug by using Canon Clear All Settings and then Canon format, but, keep the ML files on the card option and do not use the low level format. After the format, reboot the camera and then the bug goes away. All the ML stuff was still loaded and working. I have replicated this procedure as well.
I am using the latest Oct 15th version. The bad thing is I then lose the exfat format I had on the card. The Canon format always returns it to Fat32.
Gary
Quote from: nanomad on October 12, 2013, 02:57:33 PM
Can you guys to a little test for me?
- Note down the "release shutter without lens" setting (under custom functions)
- Try to take a picture. If it fails change the setting to a different value
Repeat a couple of times. The question is wheter that setting does somehow re-initialize the lens communication or not
Quote from: maxotics on October 09, 2013, 06:57:58 PM
Hi Malakai, since one can't shoot decent RAW with any of those cards it's hard (for me at least) to get worried about a bug I can't seem to replicate. You need to get a recent UHS 1 40MBS or greater card (like Sandisk). Maybe borrow one? Maybe it's complete wrong, but the two people with outstanding shutter bug problems are not using what I would consider the rights SD cards. Shouldn't we factor that out?
Page created in 0.111 seconds with 13 queries.