Messages

There's no such thing in 5Dc iirc; the workaround for opening the menu was different.

If the menu works, don't worry about it.

You can now check what settings you have modified (Config - Show modified settings).

Just look at exposure indicator - if it changes too much, take a picture. Keep shutter pressed halfway.

No, but it will be easier to port, if anyone is interested in doing that.

It should only compensate with shutter if iso is already at extreme values.

It already does that, but for regular file I/O calls, not for hacks.

On 5D3, you need to say A:/ or B:/. The FIO calls have a wrapper that autodetects the drive, but here you need to write it explicitely.

Read my post again (all of the words, not just half of them).

In playback you would have to decode the CR2 to show raw info. Not easy.

Would be even more fantastic if you could read the manual.

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

Yes, it's possible to implement the simplest type of motion detection outside LiveView. I'm not going to do it, but anyone else is free to give it a try.

ML only works on 1.1.3 for now, but you should be able to upgrade and downgrade.

If Canon likes us, we'll be able to update ML to work with the new firmware.

It's a bit smaller than 1920 (it's 1620).

http://magiclantern.wikia.com/wiki/HDMI_Output

All Canon cameras have 4:2:2 output right now.

Weekly builds probably make sense for those who don't like to be early adopters. Scenario: say we build the weekly on each Monday morning at 5 AM, early adopters can try it and post some feedback in the first half of the week, and if no major problems are found, the more conservative users can grab it for shooting in the weekend. But there isn't really any difference from just downloading only monday nightlies, so it's probably just a matter of taste.

We will need a separate zip for each new port, because these autoexec's are not cross-platform. We could squeeze everything inside, but the fat binary is getting a bit too big and may cause slow loading times.

Docs can be built automatically; they are only outdated. Here's some work in this direction: http://www.magiclantern.fm/forum/index.php?topic=3820

Maybe we can also revisit this:

http://www.magiclantern.fm/forum/index.php?topic=4318
http://nanomad.magiclantern.fm/feats.html

What about adding a thumbs up/down for each feature/camera pair in the feature table (each checkbox)? Example: a user clicks "thumbs up" for "zebra / 5D3", which means that feature works fine on his 5D3. Or, "thumbs down" on "bulb ramping / 50D", which means he had trouble with it. With this we can have some clue about what things are widely used, what things work well, what needs more attention and so on. For more detailed feedback, we can just add a link to the forum.

Download counters should be also helpful.

I also have some experiments which can analyze the code changes and identify which features were affected by code changes. E.g. if one edits the cropmarks code (inside #ifdef FEATURE_CROPMARKS), the "cropmarks" feature can be highlighted somehow in the automatic change log, so users can expect something different when using them.

It's easy to make it twice as fast, but I find it too fast.

I don't think it's worth the effort of adding an extra menu item for this, so you can just hack the source code yourself.

I guess Canon code triggers that property periodically in movie mode. That's just a hypothesis, you can check it (maybe by printing something from that prop handler).

Last time I've checked it was already updating almost as fast as it's reported by Canon firmware (delay 0.3 seconds or so). Don't have the kit lens right now to check.

PROP_LV_AFFRAME fires every second?! (in shoot.c). That's what clears the spotmeter.

Some of my plans (just what came to my mind right now):

- PicoC will be replaced with TCC. For now, it's still there because it does the job.

- RAW discovery. I don't feel like polishing the old hacks for a stable release (e.g. current bulb ramping method, or UniWB), now that we have the real thing.

- Backend stuff: we are pretty close to the limit of how much RAM we can use (how many things we can cram inside). Module system (under development) will improve this. This can be for 2.5 if you ask me, but g3gg0 would like it earlier.

- I'd like a boot process that supports all cameras with a single download (like the unified 2.3 zip). The current approach does not scale to the new models (it requires a huge fat binary containing the code for all cameras). I'd like a small platform-independent bootloader, the camera-specific modules (ML core), and user modules (functions that are only loaded on demand; usually platform-independent code).

So at this point I don't feel we are ready for a feature freeze.

I'm even thinking to switch to the rolling release model (just nightly), as it seems to fit better a hobby project maintained in our spare time.

P.S. This shouldn't stop you from running these tests. Good bug reports are always welcome, and in most cases, the bugs are fixed very quickly - once we know how to reproduce them.

Yep. Add files to first chunk, and when it's full, move to next chunk.

ML can't detect overexposure unless you are looking at the image review screen.

Also, the sensor saturation level for 5D Mark III seems to be 15200 (not 15488). This probably applies to dcraw too. I didn't notice any improvement by adjusting that, other than moving the histogram peak to the far right, where it should be.

On 5D3, the focus box gets hidden correctly when defishing is on. The spotmeter is fine. Maybe a video can help.

Yes, stop recording video.