Messages

Well I bought a Sandisk extreme 45MB/s UHS-1 16GB on ebay for 19$, shipped. Seriously ebay is amazing for camera gear prices. It came new in sealed pack.

I have some good news. This is now working! Sweet. As far as I'm concerned the newer builds fixed the bug. Or maybe it was simply not using eoscard that did it.

Ok I will try again tonight. My card is a sandisk UHS1 45MB/s 16GB.

To be clear the install process is:
1- Put card in EOS M.
2- Put EF-M 18-55mm IS lens and manual mode
3- Do full format using the camera (its quick anyway).
4- Put card into computer
5- copy the unzipped files below unto the card:

http://ml.bot-fly.com/EOSM1202.FIR
http://ml.bot-fly.com/magiclantern-v2.3.NEXT.2013Sep17.EOSM202.zip

6- Put card in camera
7- Install firmware upgrade (to install ML)
8- Try to take a picture and see if able/shutter bug.

Hi. When I tried ML a few weeks ago I had th shutter bug. I used eoscard app and have a 16GB card.

My camera was originally with the v1 firmware, if that ever comes to make a difference

@manly:
sorry, no... i think everyone wishes that would be the "only real limitation".
it's not possible to record 5120x2880 because of the speed of the sd-controller. there are 2 raw streams to choose from. one is downscaled via row and lineskipping (which leads to really bad quality) and the other is a 100% sensor crop (1792x1028 cropped from the center).

I was talking specifically about how to code an algorithm that would not crop anything (beyond black bars to fit a 16:9 ratio (720p or 1080p) in a 3:2 ratio). The algorithm I described is not CPU intensive, easy to compute, and recreates your new RAW layer from the uncropped RAW data. I *do* assume the full resolution is available and you seem to suggest it's not. Are you saying the lineskip raw stream is directly provided by the canon code and 100% outside of our control? If that lineskip stream is ML code, I described a way to fix both issues...

Here is my understanding of the problem. Feel free to correct me.

The only real limitation we have is how to fit a 16:9 aspect ratio in a 3:2 sensor. In other words, 5184 pixels wide (or rather, a bayer-patterned mosaic of 5184 pixels wide) by 2916 pixels, cropping 540 pixels top+bottom combined.

Our cropped 5184x2916 (16:9) video is clearly above 1080p (and the write speed). We only need to resize those into either 720p (1280x720) or 1080p (1920x1080). If the digic5 processor is having a hard time doing this, then how about, in the case of 720p (where we need to cut to 24.69%), take 8x8 pixels (bayer-pattern) and reduce that to a 2x2 by averaging the bit-depths of the corresponding colors to the smaller matrix? You would get an exact 1280x720 pixel (720p) by cropping to 5120x2880, which would be fairly close to the full 5184x3456. This operation, under x86 cpus, would be both easy to code and quick to execute.

For 1080p it would be a bit trickier, since 1920/5184 = 37.03% doesn't rounds nicely. I'll let the knowledgeable people first see if my idea makes sense then I'll see if 1080p raw is even feasible (might not even be with write speed bottleneck).

[...]
Upgrade to 2.0.2. This fixes the slow AF problem. Don't expect DSLR AF speed, nothing on this planet beats OVF phase detection. Yet.
[...]
But I can tell you this anecdote: it's a lot more sensitive in low light than the 60D.

I might not have the experience of a professional photographer but I did also note that the 22mm pancake was amazing at taking good pictures even in really low lighting with no flash. One of the reasons I am fairly certain I will resell the speedlight flash that came with the kit (selling for half the price I paid the entire kit?!)

I did upgrade to 2.0.2. I was simply pointing out that it feels like it over/under focuses before coming back to the 'optimal' focus. If the in-focus detection settings were set more aggressively it could save valuable focus time. Additionally, such a setting could also help with the 'couldn't find anything to focus on' problem I seem to have every now and then. I'd be welcome to see/hear if you would agree with that.

Hi! I'm one of the many who bought an EOS M with last months 300$ deal and is just getting started in photography. I've been following this thread ever since. I understand ML is mostly geared towards recording enthousiasts moreso than people looking forward a more configurable firmware. I was wondering if by any luck ML can be used to fix the (forgive my french) god-awful EOS M AF speed (for pictures)?

I could be wrong but I do often have the impression from the stock 2.02 firmware that even in single-target focus mode it keeps on going too far to determine something is beginning to get out of focus and loses a lot of time there. As such, I assume the slow AF is in major part slowed down by the firmware. In any case, thanks again for any response from the more knowledgeable people.