Messages

Speaking of prores. I wonder how they managed to put that in the BMPCC when the canons don't have enough computing power to convert raw to prores... Dedicated prores chip?

Either implemented in hardware, or more likely using some GPU Compute resources to do some of the work (the latest Tegra based design comes to mind) or a dedicated DSP plus a multi-core ARM chip probably makes it doable without being too expensive either from a cost or power design. It'd be interesting to know what they've done actually. Although, I don't actually know that ProRes is really a heavily compressed for mat. Probably doesn't take much more computing resources over h.264, just a higher write bandwidth is required. Maybe more CPU if there's no hardware dedicated to it.

Awesome Drizzt321!  I was just rereading through the thread and about to try to answer my own question, so you've saved me some time. Now onto the tests.

You're welcome  

[EOS_Develop]

I didn't see a zip file in the bitbucket. Am I missing somthing?

There are 3 files to download from this thread (plus the EOSCard app).

[EOSM202] (need to rename to have .zip extension): https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip
UpDaterM.fir: http://www.qfpost.com/file/d?g=NzBmhwaBK
magiclantern-EOSM.106.Alpha1.zip: http://bit.ly/UP7Avg

So, here are the steps that I took, a slight modification along with correct links on Canon eos m instructions.

1. First soft format your SD card on your computer.
2. Then format the card on your EOS M. This will create the 'DCIM' and 'MISC' folders on the SD card.
3. Next download files from the bitbucket.org link (https://bitbucket.org/OtherOnePercent/tragic-lantern-6d/downloads/%5BEOSM202%5D%20FirstVersion-NoInstaller.zip) provided by 1% above on to your harddisk. Unzip the files and copy directly to your SD card.
4. Next copy the updaterM202.fir (link on page 33 of this thread) UpDaterM.fir (http://www.qfpost.com/file/d?g=NzBmhwaBK) on your SD card.
5. Open the EOSCard link from the installation section of the 5DMarkIII home page.
6. With the SD card in the card reader open the EOSCard utility.
7. Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
8. Then copy the ML directory from the Alpha 1 (http://bit.ly/UP7Avg) version (you can find this on the EOS M home page). Unzip and copy the 'ML' folder on the SD card. Then transfer the 'Modules' files that you got from the bitbucket.
9. Make sure not to use the autoexe.bin file from Alpha 1 but autoexe.bin file you got the bitbucket.org link. (step 3)

I finally managed to get ML running on my EOS M 2.0.2.

Took me a few tries but figured it out. Still has issues but is very useable.

Workflow:


First soft format your SD card on your computer.
Then format the card on your EOS M. This will create the 'DCIM' and 'MISC' folders on the SD card.
Next download files from the bitbucket.org link provided by 1% above on to your harddisk. Unzip the files and copy directly to your SD card.
Next copy the updaterM202.fir (link on page 33 of this thread) on your SD card.
Open the EOSCard link from the installation section of the 5DMarkIII home page.
With the SD card in the card reader open the EOSCard utility.
Once in the EOSCard interface checkmark the 'EOS_Develop' and Bootdisk and press the big 'ML' icon and then press the 'save' icon on the top left of the EOSCard interface.
Then copy the ML directory from the Alpha 1 version (you can find this on the EOS M home page). Unzip and copy the 'ML' folder on the SD card. Then transfer the 'Modules' files that you got from the bitbucket.org link (above) and copy it into the ML folder that you got from Alpha 1. Make sure not to use the autoexe.bin file from Alpha 1 but autoexe.bin file you got the bitbucket.org link. 

Place the card in the EOS M and it should be ready to rock.

I followed this, used the UpDaterM.fir instead of updaterM202.fir which I couldn't find. Got it to install and run fine, although like others it isn't booting right into ML after turning it off/on. Other than that, don't have more time to play with it tonight, but great job 1%!!

Yea, its not going to take 1 day. I just reorganised stubs and found adtg shutter, it cleans up FPS sprinkles/lines but timings are too loose, have to set manually. So one bug down, can get some time lapse out of this thing finally.

Next up porting. Fingers crossed for display filters/mz.

Ah well. A person can hope, right? Anyway, awesome, keep up the great work and do what you gotta do!

+1 I just got in on the EOS-M deal and using it mostly for fooling with alt MF lenses. Hoping to get the zoom box back that I am so used to on the 60D

Yea, I actually have 2 adapters coming for tomorrow, an MD mount (no corrective optics FTW!) and m42 mount adapters so that I can use some of my old lenses. I've got a nice 28mm f/2.8 MD lens that'll probably look pretty sweet, and a 55mm f/2.8 Macro in m42, and a 135 f/3.5 in m42 along with my bellows and I could have a pretty sweet Macro setup that's relatively light and puts a lot of pixels right on target

Below MZ working well again.

If you've got a prototype build for 2.0.2 I'll be happy to test for you. I've got 48 hour film festival this weekend, and it'd be cool to add EOS-M to my 5d2/5d3 for shooting, and ML would really help with that. I'm willing to risk bricking it.

I can second that. It's a great card, but it's not close to the 150 Mbps write that they claim.

Was this the 16GB or 32/64GB card?

Looking at the 16GB card image, it shows W of 95 MB/s, while the 32GB shows 150MB/s. Not saying you're wrong, just curious which you got because the larger capacity 32/64GB likely has more NAND dies which means more dies for parallel writes which generally means higher peak write speeds.

Just got my EOS-M, and wouldn't you know it, it's firmware v2.0.2    Hopefully 1% can get the alpha loading up on it soon. I need to start learning the timelapse/intervalometer on this camera so I can use it at the end of August.

Currently it is available only as a closed beta to those who have donated. If you donate(even a very small amount) you will receive a download link with the firmware for the 5d2.

I don't know exactly when the first full public release will be but hopefully very soon.

I donated back in early April, but did not receive any email from ML (got it from Paypal on the transaction) giving me a link to the Unified 5d2 beta.