Messages

The latest as of writing, but with a slight modification to bypass the sig check as that wasn't working right.

EDIT: Funnily enough, Bitbucket is also down as of writing...

[no]

That's the source-code that you compile from, yes.

I'm not sure if I should do this, but I've attached my autoexec.bin and the .fir file for the 650D from the ftp space of the site.

I take no responsibility for what happens if you brick your camera, and I have no idea how to help in such event. I'm not even 100% sure this works.

You'll need to place both into the root of your card and then download the magic-lantern nightly and place the ML folder in the root. Then you'll need to download EOScard and check all threes boxes and click 'save'. Pop the card into your camera and then run the firmware updater and that should work, I have no idea as it's a different process to what I originally did.

Link removed by Nanomad: The bootfix does not enable the bootflag, it fixes it...and the FIR bypasses a crucial safety check
As always, the safest and officially recommended method is to wait until the official Alpha release.

Heh. Yep, it's as simple as pressing a button..... and then doing this, and then doing that, and then writing this here and that there.

Funnily enough, compiling Magic Lantern sort of is "next -> next -> finish" except Command Line style instead of GUI.

If you do want to compile Magic Lantern I 110% recommend getting the Virtual Machine made for it.

http://nanomad.magiclantern.fm/Development%20Box/VirtualBox/MagicLantern.zip

You'll need virtualbox for it. From then on you just need to make a make.user file and do 'make 650D' in the terminal and get your autoexec.bin off your VM.

Plants don't really grow that fast (I hope?), so I don't think he'd be taking a photo every 10 seconds. Maybe he could take 1 an hour and have 1 day = 1 second which would produce 14 seconds of time lapse footage at 24 fps.

I never got to try the old alpha. The version I was using before was a autoexec.bin I compiled myself on March 13th with the .fir from the 650D downloads section.

nanomad and I have been testing things on IRC and he thinks there might be a bug with his signature checking or that I was just using an old firmware or similar.

On the plus-side, here's an image of one of Magic Lantern's "features" [It's a joke btw, my camera is perfectly safe!]

https://imageshack.us/scaled/large/820/20130416215724.jpg

I tried to compile the latest version of autoexec.bin and I re-did the EOScard but when I booted up my LED flashes and camera doesn't boot, it's fine without the card though. Is it because I'm using an outdated nightly of Magiclantern or did I do something wrong.

I thought there already was a sound level indicator on the 650D?

I can't wait until you unlock the other ML features on the T4i. Live preview features and HDR-video and motion detection is great and all, but I'm excited for when focus stacking and advanced HDR (Picture) bracketing gets on the camera!

Great work all around nonetheless.

Good thinking t4ilover, I originally tested at 720@60. I'm currently testing 1080@30 at 3x bitrate and it's still recording at 1 minute 48 seconds.

EDIT: It goes for 6 minutes before cutting off.

You'll just end up with a load of empty/small threads.

@APXMusic, I tested then and I got up to 2.4x and any-more than that it stopped recording. This is with no HDR-video and with Global Draw in Live-view off. I did a benchmark test on my card and the camera said my card could do 40.9 MB/s (Or is it Mb/s? I forget). If you say that the standard is 50 megabits per second then I can film at 120 megabits per second.

What's the alternative method to using the .bin?

Also, how would I know if I do have Props disabled?

If it's alright with Nanomad, I'd be happy to upload/share my own compiled autoexec.bin and post a guide on how to install it. Although I'm not sure how perfect my compilation and install method was. (Are the help docs meant to be missing?)

I've compiled myself a magiclantern.bin and autoexec.bin but I'm not sure how to compile the .fir or whatever else I need.

EDIT: I've tried doing "make" in the install/650D folder and it's giving errors that I don't quite understand.  I'll post a link to a log as soon as I can get it out of the VM.

EDIT: Is it acceptable to use 650D-bootfix.fir with a compiled autoexec.bin and ML?

EDIT:
I took the plunge and it worked out-of-the-box when I inserted my card and turned on. (I think I had set my camera's bootflag on a previous experiment).

Seems to be fairly stable *nudge nudge*

I kid, a confident release is a happy release or something like that.

You made a test release for the test release?

Too exciting! I cannot wait! Thanks for your commitment to the project nano! and A1ex!

I actually can no longer find the link, but it was in the list of commits, the one like the commit that removed it but added it and clicking the 'view file' button downloaded it to my computer.

Ah, here it is, thanks to web history.

https://bitbucket.org/hudson/magic-lantern/commits/5859adcaa2442cfe5be93b025b44a8be64ce33b2

I noticed you can still get the original dumper from a certain repository, but I'm not crazy enough to use it.

Wish I could join in on the testing. Ah, well.

http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Feb02.650D.BOOTFIX.zip

I assumed the 'bootfix' meant that it was safe, but okay. I guess I should just wait for the next version.

Hello, I'm having a little bit of trouble testing the pre-alpha. I can dump the firmware successfully but when I put
'magiclantern-v2.3.NEXT.2013Feb02.650D.BOOTFIX.zip' onto my SD Card and try to make the card bootable EOScard just gives me "ZIP format." and my camera gives me the bootdisk error and a smiley face.