Messages

When all else fails, read the manual

See my previous post. There was no progress since then.

Wrong NVRAM values depend only on how they are interpreted by Canon code, so emulating only ML code won't help. If you get permanent ERR70 after changing some setting, that's a clear sign that you have set an invalid value; there's no other way to tell this. Maybe full emulation could help here, but that's very difficult (of course, I won't be surprised if g3gg0 succeeds). Detecting memory leaks may be possible (maybe run ML under valgrind?)

I want to emulate ML so I can check how the menus look on each camera, without having to buy every single model. Also, it may be helpful when writing user scripts, or when working with graphics code, fonts etc.

Yes, feel free to add them.

Yes, only for emulation. I don't need to emulate the entire Canon firmware, just ML code.

Does this happen in both movie and photo mode?

You should try to read the first post from the front page

http://www.magiclantern.fm/whats-new/78-news/145-happy-holidays-updates-inside

http://chdk.wikia.com/wiki/G1X

Set bulb timer to some huge value and should work.

2. This needs reverse engineering, we don't know how to do that.

3. should be easy, I'll add it.

4. sounds interesting, but I'm not sure where it would be useful; can you describe some use case for this?

5. should be easy. You can already use custom spotmeters, see img.c.

Also, we are considering to upgrade the engine to TCC (it's much faster, roughly 1000x, since TCC is a compiler, not an interpreter). Technical discussion: http://www.magiclantern.fm/forum/index.php?topic=4877 . The existing GUI is already working with TCC (just compile with CONFIG_TCC=y instead of CONFIG_PICOC if you want to try it).

The main issues that need to be solved:
- memory usage is a bit higher now (so 60D won't boot with it), but TCC only needs to be loaded when compiling the scripts, and then unloaded.
- compatibility with existing scripts (TCC is more strict, it requires a main function)
- how to stop the scripts? (we could just kill the task, but it's ugly)

The existing API should be easy to port, I don't foresee any difficulties here.

Its common for astrophotographers to remove one of the IR filters on DSLRs to improve the red sensitivity of cameras...

... and you are probably the only one of them who uses ML, so it's likely that only you can implement it.

Or, you can just shoot RAW, so you no longer care about in-camera WB.

http://www.dvxuser.com/V6/archive/index.php/t-247001.html
https://groups.google.com/forum/?fromgroups=#!topic/ml-devel/8cnLT_FjgIw

This is a Canon bug, present on all cameras that I've tried. ML has a fix for it, just enable exposure override ( http://wiki.magiclantern.fm/userguide#expoverride ).

The big problem is that both buttons report "shutter half-pressed", so... if AF-ON is kept pressed, you just don't know when your finger is no longer on the shutter. I don't know how to solve this without side effects.

Probably waiting for focus confirmation with some timeout (2-3 seconds) would work best.

I can't notice any slowdown on my 5D2 with 50/1.8 (my only AF lens).

Try tweaking the delays.

If it's trivial, just grab the source code and implement it.

60D and most newer cameras (also 550D) support display filters. The 50D/7D can do this only in playback mode (not Liveview), because we don't know how to change the display buffer address.

It's possible, in the same way as defishing or anamorphic preview (with display filters), but not on 7D. You need a camera with CONFIG_DISPLAY_FILTERS enabled in internals.h.

I'm going to let somebody else implement it though.

Did this thing for years, no problems...

That's difficult, since Canon code also expects a catalog of files (not just what's on the filesystem). If you rename the files from the camera, you'll get ERR70.

How to reproduce? I just turn it off and the battery doesn't discharge.

The 6% is when the camera is on, with display off.

It's quite easy to implement, even for someone who doesn't know C. There are no "due" dates, as ML is just a hobby project.

Not yet, but there's an unofficial build in the 5D3 thread, you can try that.

You can automate pretty much everything with PicoC scripts: http://www.magiclantern.fm/forum/index.php?topic=4362

The autostart feature is not yet done, but it's planned (maybe a script named AUTORUN.C could be executed at startup automatically).

You can try the nightly, hopefully the procedure is a bit easier.

Thread: www.magiclantern.fm/forum/index.php?topic=4747

Here's a sample of the noise lines:

At 2-3 fps it works fine, you can already try it, there are some experimental binaries in the 5D3 thread.

Can it print the error in some log file if it fails? I did a fresh clone and compiles fine here...