Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Marsu42

Pages: 1 ... 3 4 [5] 6 7
In property.h there are 3 values that have something to do with LOCK ... I want to detect if the camera is in button lock mode or not (6d: just a button, 6d: switch, ...): Can anybody give me a hint if this has been figured out yet? It would be most helpful for shortcut keys.

On 60d, I cannot install a handler for the BGMT_*PRESS_ZOOM*_MAYBE events - it shows an event in live view, but outside lv it doesn't seem to work since my 60d ignores the handler.

Is there any other possibility to intercept and use this this button (zoom in, on the top right on the back of the camera) on the 60d outside lv? Can I probably bend the Canon functions that are triggered by this key to some custom ml code?

General Development / Hide features in menu or disable on compilation?
« on: April 06, 2013, 02:43:11 PM »
Now that the new 60d memory code is there (thanks!) the feature-complete ml fits into my 60d again. I used to #undef features I didn't need...

... and now I'm asking myself: Is there still any advantage of having a smaller binary w/o features I will really, really never need or is it basically the same concerning performance, stability, memory fragmentation and so on to have it all and then hide the menu items?

Feature Requests / [DONE] Beep on ml loaded & initialized
« on: April 05, 2013, 11:09:39 PM »
I always find myself pressing the ml menu key to test if ml has been properly loaded (I could wait and see if the led blinks, but that takes more time). So I'd like the camera to beep once if ml has started, I could add this myself but the question is: where is the end of the "main" subroutine that is kicked off by the hacked Canon fw?

General Development / New/Minimal proposal for non-lv shortcuts
« on: April 05, 2013, 09:27:55 PM »
Today I had a go at ml again, implementing several smallish things I wanted the camera to do - and I discovered that after the first source code shock it's not that hard to implement some basic features. So while you guys are working at cameras I don't own, video or lv I don't use I'd like to add something for us still shooters.

I'd like to request or even add myself a simple, minimal-invasive shortcut system for things I'd like to switch w/o taking my eye away from the vf. I remember vaguely reading something similar some time ago, but nothing has been merged yet so here's my proposal - sorry if I'm repeating things, but I'd really like to see this actually happen.

* Menu: Prefs->Key Preferences with the following items:
- selectable meta key: [none, INFO, Q, LV]
- several key [UP, DOWN, LEFT,  RIGHT, SET] to function mappings

The idea: Add a key handler for the selected meta key, and if one of the shortcut keys is pressed during a certain time span (like 3sec?) perform this action, other wise time out. If the same meta key is pressed twice perform the function the button was originally designed to do. If beep is enabled sound different(!) signals for all keys and actions (on/off) so you don't need to look or guess if the result was correct. If the meta key is none, just map the functions to the keys (if lock is not enabled, can we check for this?).

I desperately want to be able at least to change/toggle these functions:
- switch single point af <-> all af points
- switch one shot <-> servo af
- switch eval metering <-> spot

Plus in a 2nd step, but maybe there are better "mini c-mode" proposals:
- toggle two full expo presets (all t/f/iso/wb/drive/metering) - already in ml
- map a certain expo preset to a key (select what to save of t/f/iso/wb/drive/metering)
- reset to one of the expo presets

Anything else? Sounds reasonable? Did someone already do this?

Feature Requests / Flash: auto-switch from hss to 2nd curtain sync
« on: April 04, 2013, 06:42:44 AM »
This is a major annoyance on Canon flashes, but it could be fixed by software. There is a Canon "sync" menu option and an equivalent button on the flash that cycles though 3 settings: a) 1st curtain sync, b) high speed sync, c) 2nd curtain sync.

The problem: If you enable hss it's only about shutter speed faster than x-sync (5d & Rebels: 1/200s, 7d/60d: 1/250s, 6d: 1/180s). For x-sync speeds the camera auto-switches to 1st curtain sync when hss is enabled, meaning that auto-switching to the very useful 2nd curtain sync is not possible because it is limited to x-sync and everything brighter will be overexposed.

Request: An option "auto-switch hss & 2nd cs", the camera should use 2nd cs when <x-sync and hss when >x-sync. Implementation: Ml would have to check if flash is enabled, and set one or the other in the Canon props.

Feature Requests / [ALREADY IN CAMERA] Prevent 6d wifi sleep mode
« on: March 31, 2013, 10:00:44 PM »
Multiple reports indicate a problem with the 6d sleep mode when remote controlling the camera with iOS or Android: After some time of inactivity the camera disappears off the grid and you cannot activate it remotely again. This is esp. tedious for wildlife shooting or when the camera is positioned in awkward places for special shots.

Request: Add an option to the 6d to disable wifi sleep mode, probably by automating the current workaround ("ping" = do something now and then).

Edit: Doh, the user on CR that reported the problem didn't know about the "power off" setting in the camera, so forget about this.

The 7d2 is rumored to be able to capture video frames as stills, further specs unknown (see ... is it possible to implement something like this on older cameras, i.e. shoot jpeg "silent pictures" out of lv until the buffer overflows?

Feature Requests / [DONE] Switch to high speed on Canon bracketing
« on: March 20, 2013, 06:55:41 PM »
I only use Canon bracketing for handheld because it's faster than ml. All the time this involves two steps - setting the bracketing distance and then switching to high speed continuous, and I sometimes forget the latter (doh).

Request: Shooting Preferences -> Fast Canon bracketing (check on half-shutter, then switch).

I could try do this myself, but I don't know how to check if Canon bracketing is set or not (ist it PROP_DEFAULT_BRACKET?) :-o

General Development / How to get/set properties?
« on: March 18, 2013, 08:13:13 PM »
Ok, simple /me is trying to add some saved/set properties to expo. presets (see but in the meantime from when I last looked at the code I forgot again :-\ how the property thing works. Is there a tutorial somewhere on how to do it - via handlers or directly?

The three things I like to set are like this, but how do I get them in the first place - _get_prop(int prop) doesn't seem to be reliable?

Code: [Select]
prop_request_change(AF_MODE, &c_af, 4);
prop_request_change(PROP_DRIVE, &c_drive, 4);
prop_request_change(PROP_METERING_MODE, &c_meter, 4);

General Development / What keys generate event codes?
« on: March 17, 2013, 09:35:59 AM »
Sorry if there is an obvious list elsewhere and this is a dupe, but what camera keys generate event codes that can be intercepted by ml in shooting mode? Does it include "dof preview" and "popup flash"?

Feature Requests / Expo Presets: also save af, drive, metering modes
« on: March 16, 2013, 09:13:06 PM »
I used the expo preset feature lately, but it doesn't save enough data for the most prominent usage case I can think of: One preset for shooting static objects (low iso, slow shutter, one shot, slow drive, eval metering), and then another for moving objects (high iso, fast shutter, servo af, fast drive, center metering) - both are usually found in quick succession when shooting people or animals.

Request: Please add 1) af, 2) drive, 3) metering modes to the vars saved - currently only f, t and iso.

Feature Requests / [IMPOSSIBLE] Auto-ISO: smaller steps than +-1ev
« on: March 14, 2013, 07:35:46 PM »
First, there is a bug in the current help description for Auto-ISO: It says the t/f values are +-0.5ev, but in fact they are +-1ev

However, the help text describes how it imho should be (and maybe was planned?): Full stop steps are quite large, it'd be nice to really have +-0.5ev or +-1/3ev - whatever is selected in the Canon menu C.Fn I: Exposure level increments

Feature Requests / [DONE] Auto-ISO: 1/4000 please...
« on: March 14, 2013, 07:18:46 PM »
When doing high speed action shots Auto-ISO only reaching 1/2000 is a bit limiting - imho it'd be nice to add 1/4000 to the list for cameras that have 1/8000 shutter (afaik everything except Rebels & 6d).

EDIT: I just added it myself and will post a pull request - though my solution is static (different #define for different cameras in features.h) rather than dynamic though FASTEST_SHUTTER_SPEED_RAW

Feature Requests / [DONE] Tilt direction for level indicator
« on: March 04, 2013, 08:27:52 PM »
I really like the "always on" level indicator in the lv, but unlike the Canon original via INFO the ml version is rather small and I personally always find it hard to see to which *direction* the camera is tilted - if the tilt is very little you have to watch for the two small steps in the white line which is very awkward when not sitting in the comfort of your home...

Suggestion: Add a way to immediately see to which side the camera is tilted, I can imagine these possibilities:
* add a dot to the end of the line that points downwards or if that's too hard to code
* colorize the line differently for left/right tilt.

I was out the last couple of days shooting focus stacks and was very surprised (and yes, sad) to see focus bracketing gone. It's not only the fact that I added the code myself as my contribution to ml, but there actually was some reason for doing so - please let me elaborate:

* Focus bracketing is important when doing shots with large aperture and small dof: On the dslr lv screen (even less in the vf) you cannot see *exactly* what is in focus, focus peaking also just gives a hint. To make sure to hit the correct spot, the possibility to shoot a little behind and in front of the current focus is essential.

* Focus bracketing is important to save time: When doing available light stacks outside, the current/old approach (manually focus, then step through follow focus & focus peaking) is very slow, thus costing valuable time that might break the shot and eating a lot of battery power. It is much more feasible to quickly & roughly set the starting point, then let ml shoot a little in the "wrong" distance for safety, then shoot a pre-set number of frames - and if overshooting a lot or reaching max. focusing distance stop the stack (i.e. ml stops or I turn the camera off). This is my experience from real life shooting during the last years.

* Focus bracketing is convenient: With cameras w/o a swivel screen you might have to cower in awkward positions to see the lv screen, while focus braceting allows you just to pre-set the values. When doing outside stacks in the snow or dirt you will recognize this is an advantage.

Suggestion for (re-)implemenation:

1. Add two menu items "frames in front" and "frames behind" (values 0-99) and, if set, let ml shoot with these when starting the stack. If a "traditional" follow focus distance is set use this over the manually set values until it's reset.

2. The caveat when I coded it was that different lenses move need pos. or neg. focusing values to move "closer", so I had to add a "direction" normal/reverse menu item since I couldn't figure out a way to tell plus I had to name "in front" and "behind" as neutral "A" and "B".

3. Add a way to stop the currently running focus stack other than turning the camera off (I didn't add this then, but it'd be nice to have).

... if there is a way to script this through picoc with setting the appropriate values (bracket a, b, direction) and read the values currently set in the focusing options and/or set them in a picoc option it'd be an alternative, though I wouldn't know how to do it in picoc atm and picoc still has bugs on my 60d.

Feature Requests / [DONE] Focus stacking: honor 10/2 sec delay
« on: March 04, 2013, 08:52:38 AM »
When starting a focus stack via the menu it starts instantly, but it'd be important that there is a 2/10 sec timer delay because when putting the camera on a not-so-sturdy tripod or something else improvised (no choice at ground level) it needs some swing-in time - otherwise the first couple of shots are broken.

* Suggestion: Simply add a 2/10s delay if the self-timer was set before starting the stack.

Feature Requests / 2nd ec for external flashes
« on: February 22, 2013, 12:21:44 PM »
Ml only implements ec for the first flash in the ui and scripting, but I usually shoot with multiple flashes in a:b-c mode where a a:b ratio or more often a 2nd ec for the c group is set. I'm pretty sure a lot of people use this to a low power fill flash from modeling flashes, so having it in the ml ui would be nice and appear less "Rebel"-like.

Feature Requests / GPS tracker in 6d and other upcoming cameras
« on: February 19, 2013, 07:36:35 PM »
Imho this would get Magic Lantern a very large popularity boost because people wouldn't have to buy a dedicated tracker next to a 6d, so using ml would actually save money:

The 6d (and other upcoming cameras that most likely also will feature gps) can only display the current position and write a log. The functionality missing to use the 6d as a gps tracker substitute is:

1. Quickly set the current position or a list of positions as a reference ("car finder mode")
2. Allow the user to enter a list of custom coordinates either on the camera or with a pc on the ml card ("geocaching mode").
3. Calculate distance (and probably direction, see 4.) to another set of coordinates
4. Show the compass direction the camera is moving to by comparing two gps samples

Imho at least the very basic "car finder mode" should be rather simple to implement, if the calculation of distance and direction should prove to be to complicated in the first step even a simple coordinate difference would suffice ("your target is xyz coordinates away"). The next step would be the "geocaching mode" list of coordinates, even if this would be achieved 2/3 of the functionality of a €100 gps tracker would be done by ml.

Scripting Q&A / Beep after bracket/intervalometer with picoc?
« on: February 18, 2013, 11:41:43 PM »
I recently requested a feature and wonder if this is possible to script instead with the current api (I know it has beep()) ...

* trigger shooting with the currently set bracketing values, then beep
* trigger the intervalometer to shoot multiple consecutive brackets, then beep

And is it possible to set the bracket or intervalometer option values (like ev spacing or # of repeats) with picoc?

Feature Requests / [DONE] Upper ISO Limit for Expo Lock
« on: February 17, 2013, 10:44:00 PM »
When setting Expo. Lock to modify ISO before Av/Tv it goes up all the way to H (12800) on my 60d which is next to unusable, making this feature basically useless in this setting. It's absolutely vital to add a "Expo -> Expo. Lock"-> Max. ISO" setting to prevent drowning in iso noise.

Feature Requests / [ALREADY DONE] Auto-Repeat Bracket
« on: February 17, 2013, 10:22:29 PM »
When doing long time exposures with a nd filter to eliminate moving people or other objects from the scenery it's pure luck if it works or if a person or car decides to remain stationary for a while so the shot is ruined. Because of that, I always repeat these brackets a number of times so I don't experience bad surprises when doing postprocessing. Currently I wait for the bracket to end and start it again manually, which doesn't seem quite appropriate with something as useful as ml.

Suggestion: Add a menu item "Shoot -> Advanced Bracket -> Repeat bracket" so I can sit somewhere in the general vicinity and let the camera shoot for 15 Minutes.

Note: This is not the same as repeating each individual frame (2*-1ev, 2*0ev, 2*+1ev) because repeating the whole bracket (-1ev, 0ev, 1ev, -1ev, 0ev, 1ev) makes it more likely that a "good" frame is captured when the disturbing object is gone.

Feature Requests / [DONE] Beep after bracket/intervalometer
« on: February 17, 2013, 09:54:22 PM »
I just acquired this new 10 stop nd filter and am doing nighttime brackets for hdr/exposure fusion. Each bracket takes up to 5 minutes, even longer if doing consecutive brackets with intervalometer. Instead of staring on the camera display to show the last shot it would be mighty useful to let the camera beep after the procedure is done so I could leisurely stand next to the camera and look at the scenery. I wanted to implement this simple feature for ages but never came around to it, so I'm posting a feature request (for now). 

Menu suggestion: Shoot -> Shoot Preferences -> Beep when done [after bracket, intervalometer or intervalometer+bracket]

Feature Requests / AutoISO Limits
« on: February 17, 2013, 09:49:17 PM »
The shiny new cameras like 6d & 5d2 have an advanced auto-iso function that lets you set lower and upper limits. It'd be mighty useful to backport this feature to older and lesser camera bodies, for example on my good ol' 60d it's only possible to set some crude upper iso limits. Esp. a lower iso limit is important to prevent the camera going down to iso100 and setting too slow shutter or too large aperture.

Yes, this can be somehow circumvented by using the fixed "ML Auto ISO" settings, but it works only in Av/Tv mode, but a more flexible solution would be very useful. The alternative solution to a 5d3/6d backport would be to improve "ML Auto ISO" to use *minimal* shutter/aperture values which would also prevent the camera using unnecessary low iso values.

I only discovered this yesterday when doing night-time shots - when doing a bracket 0+-+- or 0++ when the slower frames are more than 30s, the camera automatically opens up the aperture to still reach 30s which the bad effect on sharpness and ability to merge frames because of different dof.

Ml can do bulb timing, so it'd be great if the slower brackets could still be shot with a smaller aperture, but more than 30s shutter speed? That would also be a distinct advantage over Canon bracketing.

Pages: 1 ... 3 4 [5] 6 7