Messages

I don't see what the problem with HDR video is? It's meant to change ISO levels in the display to let you preview the two light levels you'll work with.

If you mean on playback it changes ISO, that's how it's supposed to be. Look at the documentation I linked you to before (http://wiki.magiclantern.fm/userguide#hdr_video).

If it's something beyond those two, then I guess you have found a unique bug, but you'll probably need to describe it better.

Anything happening yet guys? I'm a bit anxious to use the 'test' version as the T4i ain't exactly the cheapest camera out there. But are we looking at a release date soon?

http://wiki.magiclantern.fm/faq#when_will_you_release_the_next_version

Gradual Expo - On -  Ramping Speed 1EV/16 Frame
HDR Video - ISO 200/800v 2EVO

Recorded Video also Flicker

RTFM - http://wiki.magiclantern.fm/userguide#hdr_video

It's suppose to flicker, that's how the HDR Video feature works.

http://wiki.magiclantern.fm/faq#troll_questions

"When it's done"

how is HDR video working in the pre-alpha 2? Any better than pre-alpha 1?

I haven't tried it out on Alpha 2, but I have no reason to believe that it's any different to when I attempted to try it out as I don't remember seeing any code change commits relating to HDR video.

Hows HDR video working?

I uploaded a video a while ago showing HDR video on the 650D. It's certainly not the best video showing HDR as it was hand-held and had moving subjects and it was my first go at it. [Not sure if it has a lot of dislikes for that reason [and if so, I say those reasons in the description anyway] or because people think it's fake?]

http://www.youtube.com/watch?v=s05gZqJ8gS0

Can't you just get Python for Mac?

I don't think anyone is intentionally giving incorrect information. Also, the admins/developers have repeatedly said that this is a pre-alpha and even the officially released pre-alpha was intended for those apart of the first pre-alpha. So it kind of goes without saying that everything else is unofficial and not officially supported.

As I saw it, the idea of the pre-alpha 2 was for people already testing the pre-alpha to continue testing. If people are going to suck up all the helping posts, they'll do that regardless. and if there weren't any helping posts, they'd ask for some, as they have.

If you were passively meaning me, I try to give as accurate advice as I can and most of my advice is helpful [Like that 'bypass-the-45-minute-VM-download' it seems]. The only time I think I gave potentially dangerous information was when I gave out my autoexec.bin and a link to the bootfix.fir [See my post on my confusion over the two .firs], though I did explicitly say I wasn't responsible in that post, and the links were then edited out when nanomad saw what I had done wrong and no-one's cameras were damaged/bricked.

Oh, right. I'm always getting confused between the bootfix.fir and the safe-dumper.fir.

To temporarily revert back to "pure-Canon" turn the camera off. Hold down the 'SET' button then switch to On. You should see "Magic Off" printed to the screen.

To permanently revert to Canon stock firmware I think you can do that by formatting the card in-camera and there should be an option to disable 'Keep ML'.

@StreetShotz I think running the bootfix firmware updater allows you to remove the bootflag, which would also permanently disable ML as well.

Movie > Image Finetuning > ML Digital ISO

Perhaps, except it takes 5 seconds to download the .fir and on my connection about 45 minutes for the VM image Luckily I used my School's fibre and it only took 5 minutes.

EDIT: Oh right, you were talking about the first part of my original post for your reply.  Oops.

But wouldn't the link be the updated version while the one that's included in the VM out-of-date?

Unless you're suggesting that doing 'make 650D' also makes a .fir?

Is there any difference in the files you released and the custom-compile with the source-code?

@Newsense Why bother downloading the VM when you can get the .fir here? https://bitbucket.org/hudson/magic-lantern/src/99bd629f7c5712346369840e64c04fd2d4576520/platform/650D.101/devkit/650D-safe-dumper.fir?at=unified

I set mine to enabled chromatic aberration correction and I can still burst shoot at ~5 frames. My SD card is 45mbytes/s though.

News is found either by a developer posting here or on the source code repository: https://bitbucket.org/hudson/magic-lantern/commits/all.

[ML does not modify the firmware right?Does ML flash any firmware onto the camera?When ML installs what exactly does it install?]

I just want to get some things straight

ML does not modify the firmware right?

Does ML flash any firmware onto the camera?

When ML installs what exactly does it install?

1. It does modify the firmware, part of why it is currently un-safe.

2. Well, it doesn't flash a firmware but it does modify part of the on-camera memory, which is why it is potentially un-safe and why the 650D Magic Lantern port has not been released for testing.

3. It changes the 'boot-flag' on the camera's memory (IE. Not on the SD card but the camera itself) that IIRC tells the camera to look on the SD-card for a debug firmware (Which is there for when Canon is doing testing/etc I imagine).

I posted the link to the VB image a couple pages back, I'll edit it in shortly.

Here it is: http://nanomad.magiclantern.fm/Development%20Box/VirtualBox/MagicLantern.zip
But it doesn't come with the latest source, so you'll need to grab the latest from bitbucket.

And because someone mentioned it on this page, no, it is not currently safe.

You've already got Magic Lantern with the buggy parts disabled, as I think what nanomad was trying to say was that they haven't got the installing/loading of Magic Lantern completely done/safe.

Or plaster this everywhere

http://wiki.magiclantern.fm/faq?&#troll_questions

Or better yet, make it pop-up in a lightbox kind of embedded pop-up thing for non-registered users.

Mine works without the card in, and I can boot up without ML running by holding down SET as I turn it on.

Well there we go. I guess it is best to wait until the official alpha, though I still don't get how I managed to get it working on my camera.

All I know is I kept getting that until I somehow got the right setup and got ML working.

Ah, that's right. I also adapted my method of getting it working on my camera from the method from installing the pre-alpha that's no-longer available (http://www.magiclantern.fm/forum/index.php?topic=3697.msg24949#msg24949). Obviously you can't do the dumper part (and I didn't need to). If you (or anyone) wants to continue, you'll have to interpret that and think about what steps to do. I'd be more descriptive, but I'm off to bed now.

Yes, I was getting that when I was originally trying to get it to work, but I forget what I did. Maybe you need to do the EOScard step when you put the http://nanomad.magiclantern.fm/650D/magiclantern-v2.3.NEXT.2013Feb02.650D.BOOTFIX.zip on in that first step as well as after you replace the files?

after you do the firmware update:

Download the nightly: http://nanomad.magiclantern.fm/nightly/ (The .zip)

Copy the 'ML' folder in that nightly package into your card (And overwrite when it says if you want to)

Then download the autoexec.bin I originally posted in my first post (The Google drive thing). Put that onto the root of the card and overwrite the old one.

Then run EOScard and check all three boxes and click 'save' (I press it a couple of times because someone suggested that 10's of pages ago and because OCD). Then put the card into the camera and turn it on (You probably shouldn't have to do another firmware update).

[removed]

Ah, okay. Try this instead:

Wipe the root of your card (Except the DCIM folder if you have anything stored there).

Then extract removed onto it.
Edit by nanomad: Nope, the bootfix won't work..it's a fix, not a proper bootflag enabler
Do the firmware update.

Replace the ML folder and autoexec.bin with the nightly and file I linked to, respectively. Do the EOScard step.

and it should just boot up into ML [Press trashcan on the normal operation display to bring up the ML menu].