Messages

[Do not forget to set "Release shutter without card" to Disable again !!]

Download EOSCard version 1.4 from pel.hu/eoscard/
Connect a USB Cardreader to your PC or Laptop.
Insert the CF Card.
Start EOScard.
Click Refresh.
Make sure "EOS_DEVELOP" and "BOOTDISK" are both unchecked.
Click Save.

Your CF Card is no longer Bootable so ML cannot interfere anymore.
Put the CF card back in the camera and take a test shot.

Tell us your findings.

On your 7D:
Press Menu
Go to the first menu (red icon with camera and one dot)
Go to "Release shutter without card" and press Set
Make sure "Enable" is selected (blue)
Press Menu, and press Menu again (or half press the shutter)
Turn off the camera
Remove the CF Card
Move the mode dial to the GreenBox (most settings and Custom Functions are ignored in this mode)
Turn on the camera
Point to something far enough and take a picture (the LCD screen will display: "No card")

Tell us your findings.

Turn off the camera.
Open the battery compartiment.
Between the battery and the hinge you see a plastic strip with the text "CR1616   3V".
Remove the battery and slide up that strip.
Remove the small button shaped battery and replace it with a fresh one.
Insert both batteries and turn on the camera. (Set date and time)
While in GreenBox mode, take a picture.

Tell us your findings.

Do not forget to set "Release shutter without card" to Disable again !!

The latest Nightly build available at that time - magiclantern-Nightly.2016Jul09.7D203

I'll post my settings later when I get home.

I went to a concert the other day, where they played Beethoven and Schubert.
The "Full res silent picture" on the 7D saved my day !
No shutter release noise and no mirror slapping. Awesome feature!
Thank you very much ML team !!
I haven't played around with the various settings to get the most out of it, but I definitely will be digging into this.

Grabbed my Jobo SD/SDHC/SDxC CF Adapter (Art #SE9109) and my SanDisk Extreme SDHC card 32GB.
Fired up EOSCard and used a CF Cardreader and enabled ML and Bootflag on the SD Card, which was inserted in the CF Adapter.
EOScard copied the ML files, then I downloaded the latest build (magiclantern-Nightly.2015Aug18.50D109) and copied those files to SD, overwriting existing files.
Inserted the CF adapter with the SD in the 7D and switched on the 7D.
ML loads but on the first boot the red LED flashes for about 20 seconds.
Probably because a lot of things need to be written to SD and the throughput is not as fast as a CF card.
Eventualy I have ML running on an SD with a CF-card adapter in my 7D.

Now I have to keep track of the various memory cards with their ML versions.

https://code.google.com/p/400plus/
Used it and loved it. Gave my 400D a whole new life.

Hello
My coworker wants to 7D also installed Magic Lantern, but something we fail to install
I have a 550D and I have no problem with me
Of the instrument it is version 2.5 Firmware
Everything is done in the footsteps of the site
thank you
Sorry for the spelling I am not very good with English

A 7D with firmware 2.0.5 will not install ML.
Get the 7D back to firmware 2.0.3 and try again.

Correct.

I have always two CF cards with me.
One with bootflag and ML code, and one without bootflag and without ML code ("naked").
If I lend the camera to someone else, I switch cards and they have a 'normal' 7D in their hands.

which version is he using?
ML , TL , Nightly builds or Alpha?

At 11 seconds I see the Help menu and at the bottom I see;
Magic Lantern version : v2.3.NEXT.2014FEB19.7D203

I have Tragic Lantern running on my 7D and it has no Help menu.
Therefore I guess he is using an ML Nightly Build from Feb 19.

For what it is worth, I do not experiment with video therefore in *my* case there is no difference between ML and TL.
(why use TL instead of ML ? Well, just because I can. I switch back and forth between ML and TL for no logical reason)

I use a Meike MK-7D grip and have no problems at all using ML or TL.

Downloaded and installed it. It runs with no problems.
The changelog doesn't show anything.
Is there some specific feature you would like to be tested ?

I think I've found the bug.
Please try it and report if it is OK.
http://pel.hu/down/EOScard.exe

Yes! This version also works with my version of Windows 8 Enterprise 64-bit.
Thank you very much Pelican!

And to add to Pileot's suggestions:
When rightclicked the ML icon there is room for two buttons; [Clear cache] and [Download files]

For those who experienced crash with EOScard 1.36:

Please download the latest  http://pel.hu/down/EOScard.exe  try it and report if it's still crashing or not.
Thanks!

This version also crashes after a few seconds with the same Application Error.
Version 1.35 works perfectly.

EOScard 1.36 crashed on two computers (Win7 and XP) even if nothing is clicked.

EOSCard 1.36 crashes on my Windows 8 64-bit also.
After a few seconds an Application Error occurs.
"Exception EConvertError in module EOScard.exe at 00021E67."
"Invalid argument to date encode."

After a brief heart attack, got my camera starting up again.
I get to this point, everything goes perfectly and as explained. Then the EOS utility says to start the update press the set button on the camera. well on the camera it says "Firmware update program. Update file cannot be found. PLease check the memory card and reload the battery and try again"

Firmware.firm is in the root of the SD card, freshly formatted by the camera.

It seems the camera does not want to "update" to an older version, am I doing something wrong?


Additionally, I think the EOScard.exe did not download the files correctly, what files is it supposed to put on the CF card? It places no .fir files, which to me seems odd. How can I "reset" the EOScard application so it re-downloads all applicable files?

I Almost had the same situation you described.
Followed Britom's Step-by-step in post #756 and I could not get the 7D to autoboot.
It turned out I tried this on a CF card I already used for ML.
I formatted the CF in the camera and tried Britoms's steps again.
At the end I manualy copied the contents of Pelican's magiclantern-7D.203.Alpha2.zip onto the CF card.
See also Post #791 for the ZIP file.
Now my 7D autoboots.

I cannot recall the precise steps but these two postings helped me.

@Britom: "Right-click the ML icon" was the eye opener for me!  (RTFM?)

Ok, I see I have to follow a series of steps first!! Now I can't find anywhere the 1.2.3 firmware :/

Check out the signature of Pelican and click on the link.
In his folder you can find "eos7d123.exe".

Thanks for the feedback everyone, and sorry for the troubles caused to our two fellow testers 

I'll see if I can get a fix out ASAP (not today, probably during the weekend)

I'm already happy with the limited version of this pre-alpha release.
No issues on my side.
Take your time.

The mirrored text only appears when the screen is flipped to the max. A little turn in both directions and the screen is correct again.

ML is up and running.
Stability test runs perfect, but on screen I see some [fail] messages.
Touching the screen is the same as hitting the Q-button. That's nice.
Now checking out other functions.

Let's call it a test to see how many people are actually interested in helping out the project by donating a bit of time

Count me in.

I assume that his latest attempt to get the code to work in the alpha made the T4i explode in his face and he's died a horrible, plastic shrapnel death.

Maybe he was running his stability test on the "Don't click me!" function.

No, but I don't want that to happen to YOUR camera 

My 50D survived this function. I wouldn'd dare try it on my T4i.

There may be an alpha before Xmas after all.... what features would you like to be featured in the upcoming Alpha 1?

I use the Zebra's, Cropmarks and "Quick Zoom SinglePress -> 100%"when I shoot sports with my 50D.
When I feel the urge to experiment I use the extended ISO (25600).

Well, you can help porting if you have time and skills

By the way, the solid red light on shutdown (lockup) it's a known issue on the 650D

I am affraid that I don't have the time and very limited skills.

The red light means in normal conditions that a write action is active.
Just to be sure I waited for 15 minutes for the light to go out.
After 15 minutes I figured that the memory dump should be complete and switched off the camera and removed the battery.

(sold my 1100D and bought a 650D)

anyone who want to help can enable the bootflag and backup memory using this

Copied the files onto an 16GB SDHC card.
Started the 650D,
'updated' the firmware,
the camera reboots,
the camera comes back to life,
the screen displays
"font addr bad"
"Hello world!"
"EnableBootdisk"
"Oops!"

And a very happy feeling that ML is actualy possible.

Taking pictures works, the camera is in perfect working order.
When I switch off the camera the red led stays on.
Removing and reinserting the battery solves this.

The SDHC card now contains K301_101.DAT

What else can I do to help ?

[Note to myself]
- Read the whole thread instead of skipping to the last posting.
- Stop being a noob at testing new nightly builds
[/Note to myself]

Go to movie mode, set expo override ON, expose for the dark scene then pan from a  dark scene to a bright scene (e.g. the computer montor) and the bug should kick in.

When I set my 1100D in movie mode I can adjust the aperture by pressing the AV button and turn the wheel. I see the screen change in brightness
When I set Expo Override ON, the aperture goes to 5.6 and the screen is very dark.
When I press the AV button and turn the wheel the aperture says at 5.6 and the brightness doesn't change.
I tried several lenses on both sides of the zoom range and every lens I use shows this same effect.
Aparently I do not have the bug. At this time the Expo override ON is useless for me because the aperture stays at 5.6.
I use the latest nightly build (2012Oct21).
Used lenses:
Canon 70-200 F/4 L
Canon 18-135 IS (f/3.5-5.6)
Tokina AT-X 80-400 (f/4.5-5.6)
The 18-55 kitlens is sold so I cannot test that lens.

I need as many lenses tested as you can,

I have the following lensen:
canon kitlens 18-55, Canon 18-135 IS, sigma DC 18-200, sigma apo DG 70-300, Canon 70-200 f/4 USM and a Tokina AT-X 80-400.
Can you describe a step by step testplan so we all do the lens tests in a simmilar way ?

I had the same thing with the nightly build "2012Oct11".
Formatted the SD card in the camera and copied the nightly build 2012Oct13 and enabled the bootflag again.
Now the Exposure Fusion and Compare Images functions work correctly.

I have firmware 1.0.5 and a 16Gb SDHC class4 memory card.