Messages

A ugly hack would be to stop down the aperture (for example, f22 is 7 stops darker than f2.0).

http://a1ex.bitbucket.io/ML/states/600D-alt/sm70.htm - sbsDarkRelease might be related.

Zoom should be a bit better now. It's tricky because it actually uses a small flood of zoom events, combined with changing Canon variables in RAM (zoom level and position), and the exact behavior can vary slightly between cameras.

With 85c2b1eca3ec it feels very smooth on 5D2 and 60D, didn't try on 550D.

Scrax: the trap focus shortcut looks at the value of CURRENT_DIALOG_MAYBE (correct naming for that is GUI_MODE). With that you can identify what dialog is currently on screen, but it's camera specific. Another method is to check the address of dialog handler code, with get_current_dialog_handler() - this is very robust, but also the address of the handler is camera specific.

Or, you can trap the buttons themselves (with handle_* functions). For trap focus I chose the dialog since the buttons for triggering it are different among cameras (and not all of them can be caught by button handler).

This feature was discontinued; next update will have a LiveView contrast adjustment for the entire screen.

If things go well, next week we'll have a release candidate (RC1) for public testing.

Hehe, good remark about the GNOME way. Fortunately, the new menu fine tuning does a very good balance between feature packing and usability. By default you get everything there, with obscure things in submenus. You want a minimalist menu - no problem, just hide everything you don't use and you have a minimalist menu.

Offtopic: zooming on AF point works very well

The only way to get it back is to show me a way to call it safely. For this you need reverse engineering skills.

Testing does not help at this stage. The probability of things going wrong because of this feature is small, but nonzero.

The 5Dc renders ML menus at 720x240, so you can inspire from there. All the changes required for this can be in bmp.c / bmp.h / vram.c IMO.

Yes, right there.

User configurable menu is possible, try out changeset eddae7f63dc5.

Audio.c and http://magiclantern.wikia.com/wiki/600D/Audio

You can play with them; scrax reported that registers were changed (new value could be read) but the audio meters stayed the same.

Great feedback, thanks to everybody.

Here's my proposal for the menu (60D - changeset ad4ed848db04 ) - heavily based on Scrax's one:


About features, I think I'll remove only what's buggy. I'll reconsider movie remap for future updates, if there will be a way to call it without side effects. Also I'm thinking to drop the simple menu mode (since it caused many confusions - why feature X is not on my camera?)

ISO+LV is technically the same as movie mode remap. The problem went as far as doing persistent damage to movie mode in 60D (it stopped working, even without ML, and all I did to cause this was flipping mode dial back and forth a few times - with remapped C mode and movie resolution set to 640 crop). So, there's no way I will enable this in a stable release.

So far I've only removed things that were causing problems.

I like the idea, here's a very rough patch that rearranges menus a bit on these lines: http://a1ex.magiclantern.fm/bleeding-edge/submenus.patch

Small note: the focus settings (step size, delay and wait flag) are also used for rack focus, focus ramping, stack focus... so maybe a second submenu with 3 settings would be better? but then you will have to press more buttons to change focus speed.

Also, people will have to get used to new menus etc, maybe more clicks for old tasks, but probably it's worth it. What do you think?

Both (especially decluttering the menu). Code size is no longer a problem.

Edit: disabled auto ISO limits too (because I've set it at 100-400, and manual ISO stopped working somehow - started working again after setting it to 100-6400).

The user-configurability part is a bit difficult (especially how it will interact with future menu changes). But we can choose a very good set of defaults for the simple menu mode.

That's good to know. There is huge potential in matrix mode (on 60D it is technically possible to move the focus box around at full speed - 30fps). There are still many details to sort out (the biggest one being memory - allocating large blocks of RAM is possible (up to 160 MB), BUT interferes with normal shooting).

It's on the todo list for 2.4.

Instead of silent pics, I highly recommend FPS override for timelapse.

For picture style controls it's true, not all cameras let you preview adjustments in realtime. 5D2 and 60D do, so those users may find picture style controls redundant.

The plugin interface and Lua scripting are in very early stages of development and will not be included.

My quick list of candidates:

- Auto ISO limits in movie mode
- Picture style controls (same controls as with Canon menu)
- 60D level indicator (Canon has one too)
- Defishing (very rough in LiveView, although good in playback mode)
- Image effects (MOVIE menu) - they don't do any harm (they are simply DIGIC controls), but I don't think anyone will use them for normal shooting.
- Flash / NoFlash (I've used it on compact cameras and missed it on dslr, but now I no longer use it)
- Silent pics - advanced modes (I intend to keep only simple, burst and maybe matrix modes)
- Mirror lockup sync'ed with self timer (anyone using it?)
- Follow focus with LCD sensor (I don't remember anyone saying he used this)
- From Display menu: image position, orientation, upside-down mode (although they can be useful when you need them)
- Sticky DOF preview / HalfShutter (I never used those, except sticky halfshutter when running through DIGIC register). Trap focus no longer needs this.
- Some things from Debug menu (like tasks, CPU usage...) - but keep indicators with free memory and so on.

From that list, only silent pics is known not to work in matrix mode on some cameras, and I'll just disable that feature where it doesn't work. All the other things are working fine, but aren't that useful IMO.

You can come up with other suggestions too.

Removed:
- auto ISO limits (unstable, interferes with manual ISOs)
- movie remap (sorry for that, I know it was very handy, but causes stability problems)
- record with SET button (100% useless)
- ML auto ISO algorithm (was present in december version, but was too slow for real use)
- zoom in face detection mode (found to be unreliable, and couldn't find any use for it)

The problem here is that only changing PROP_SHOOTING_MODE (with no other ML code running on the camera) still causes problems (same behavior as will full ML loaded). So, at least for now, I have no idea what I can do to fix it. Probably there is a higher-level wrapper function that I should call for changing the mode, but this should be found by reverse engineering.

Anyway, decision was taken. You can suggest even more useless things to remove.

I mean the screenshot function in ML.

After playing a while with movie mode remap (going back and forth to C) I've managed to break movie mode completely on 60D (black screen). So this feature will go away right now. Sorry.

Movie mode works again after clearing settings.

Sounds good. After you use the camera for a while (take a few pics, record a few clips), can you take a screenshot for Debug menu? (on 60D I can't).

The BUSY thing from changing ISO NR was also on 60D (before ERR70). But it's gone with latest changeset.

I also can no longer duplicate the error after cleaning the settings, but I can notice differences between movie remapped to C and normal movie.

The problem with the recent memory tricks is ERR70 when you change ISO NR (at least on 60D). This is a clear sign that it's interferring with normal shooting. I've narrowed it down to the shoot_malloc call.

1%: how does ML feel with 5908947bf583 stability-wise? and how much free memory do you have with it?

Technically, both are movie mode remaps (they work in the same way internally - by changing PROP_SHOOTING_MODE). But the remapped movie mode certainly borrows some things from the mode you were before (and this is camera-specific).