Messages

Okay, so here it goes:

Magic Lantern Security Bulletin: using movie mode remap may cause explosions, data loss, and other kind of permanent damage. See the FAQ: http://wiki.magiclantern.fm/faq#is_it_safe

I knew who you are from your first post. There are no paid subscriptions implemented yet, but probably there will be something like this (where supporters will get betas earlier).

I'm researching how these settings can be restored if anything wrong happens - a disposable camera (like a very cheap second-hand 500D, even not fully functional) would help greatly. What I'm sure is that the bootloader is always loaded, so even if something bad happens, I will be at least able to dump the ROM and do some troubleshooting. But I'm not comfortable trying altering the ROM by hand on a good camera.

For now, there's this page: http://magiclantern.wikia.com/wiki/Unbricking

http://wiki.magiclantern.fm/userguide#iso

That's why you have spotmeter.

The interface looks like a dos program or something old school like that

http://www.videocopilot.net/forum/viewtopic.php?f=20&t=74499#p271250

I'd just record a movie and average all the frames, like this:



A single frame from the movie:

I had some experiments with custom configs (each beginner mode loading a different config file), but caused major stability problems.

Here's an old patch, if you want to play with it: http://a1ex.magiclantern.fm/bleeding-edge/multiconfig.patch

Probably loading the config in a separate task (not directly from prop handler) is enough to fix most problems. Also, a few things may require restart (but most settings take effect just by changing the variables).

Canon settings are not affected by this - only ML settings.

You have histogram, waveform, zebras, vectorscope... much better than any automatic metering.

No.

Down and closed.

http://photography-on-the.net/forum/showthread.php?p=14654077

OK, I'll add that.

You can fine-tune the exact FPS directly from the timers, so if for some reason you need exactly 23.456 fps, you can get that. See the user guide.

It's also used with red eye reduction.

http://twitter.com/snapsort/status/220264367210508289

What's uploaded by EOS utility is not the same as what's in the pf2 file. If the pf2 is encrypted, and what's uploaded into ROM is decrypted, and I post the decrypted version of some Canon (or other company's) picture style, that would break the copyright law IMO.

And technical: the picture style data need to be flashed to ROM. This means way more risk than ML carries now, when running from the card.

So... my answer is no.

Icon meanings:
- green/dark gray: on/off
- play-like icon: action (like.. take a screenshot)
- volume-like icon: numeric quantity (like ISO)
- dice icon: a finite set of choices (something that can't be disabled, you just choose from a list)
- red X: actively disable something that it's normally in Canon firmware (e.g. 5x zoom)
- rectangle around the icon: that item has submenu
- variable-size green dot: some quantity that suggests size (like magic zoom size)
- red dot: warning message (you need to enable something else to use this)
- a few less-used others like RGB/Luma, named colors...

Yes, some users mentioned they can do this without ML on google groups. Not sure how.

Risky to try (may cause permanent damage), but I think I know where to start. However, picture style data is encrypted - so even if it can be done, it will be very clumsy to use and distribute (and there may be legal issues too, but I'm not a lawyer - I just smell trouble).

Great summary - I'm sure this will end up with a very nice design - both attractive and practical.

Aside from design, there's a very difficult problem: what's the best way to organize the menus? Some good ideas were suggested here: http://www.magiclantern.fm/forum/index.php?topic=1130.msg1796#msg1796

And another remark is about icons - they appeared for the purpose of showing quickly what's enabled and what not, from a glance. Now there are probably more icons than there should be, there also submenus... so there's a lot of room for improvement in this area.

Works for me too (just compiled, did not run). RAM usage for 5D2 binary: 341k (prebuilt GCC) vs 339k (32-bit arm toolchain).

I can split the topic and move the second half to Development. Can you suggest a title and a splitting point? (from the post with first screenshots maybe?)

You can still use it at your own risk - nobody is stopping you from compiling a custom version with it enabled.

But please don't ask me to release something that has the potential of causing permanent camera damage. I'm 100% sure it can - it happened on my own 60D, but I was lucky that I still had access to Canon menus to clear the settings and bring the movie mode back.

Have a nice reading: http://groups.google.com/group/ml-devel/browse_thread/thread/802d76120a9f5472

If you enable continuous mode... doesn't work?

I like the light blue and green ones. Red could be reserved for debug menu

Technically possible, no problems about that.

What colors do you suggest?

Simply installing ML for the first time should save a ROM0.BIN - that's what you need.