Menu

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.

Show posts Menu

Topics - Marsu42

#101
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.
#102
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?
#103
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?
#104
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?
#105
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?
#106
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.
#107
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.
#108
The 7d2 is rumored to be able to capture video frames as stills, further specs unknown (see http://www.canonrumors.com/2013/03/eos-7d-mark-ii-test-camera-cr1) ... is it possible to implement something like this on older cameras, i.e. shoot jpeg "silent pictures" out of lv until the buffer overflows?
#109
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
#110
General Development / How to get/set properties?
March 18, 2013, 08:13:13 PM
Ok, simple /me is trying to add some saved/set properties to expo. presets (see http://www.magiclantern.fm/forum/index.php?topic=4861.0)... 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?


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);



#111
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"?
#112
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.
#113
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


#114
Feature Requests / [DONE] Auto-ISO: 1/4000 please...
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
#115
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.
#116
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.
#117
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.
#118
Feature Requests / 2nd ec for external flashes
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.
#119
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.
#120
I recently requested a feature http://www.magiclantern.fm/forum/index.php?topic=4612.0 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?
#121
Feature Requests / [DONE] Upper ISO Limit for Expo Lock
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.
#122
Feature Requests / [ALREADY DONE] Auto-Repeat Bracket
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.
#123
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]
#124
Feature Requests / AutoISO Limits
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.
#125
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.
#126
This is obvious and most probably left out because of time constraints - but it woudl be nice if there would be an option to re-order the items in the ml "My Menu" just like in the Canon one.

Otherwise great work, I'm very happy with this feature - now all we need is quick button access to features like scrax is developing, and it'll be a major usability improvement!
#127
Even if I'm potentially introducing a case for 3rd level menus (which I wouldn't like that much, see ui thread) :-p ...

... the current Handheld Shutter customization from 1/2...1/125 obviously is very static, it needs at least an option to set the upper limit. But the really interesting addtion would be to to add a dependency on the lens focal length (or zoom position), since that's what causes handheld shake. So I'd propose an additional "auto" option that enables handheld mlu when the shutter speeds drops say 1 stop under 1/focal length, which is the standard criteria for "hand holdable ". But of course some further intelligent behavior or customization would be nice since IS lenses can handle even slower speeds w/o mlu. What do you think?
#128
The recent Expo Lock is a great feature and might even draw pro shooters to ml because with it you can quickly set the dof while shooting full manual. The problem is that when shooting an event you don't have time to flip through the ml menu - to req #1: please add the option to toggle the feature through SET when outside ml. As a follow-up req #2 there would have to be a fool-proof confirmation if expo is locked or not (I'm fresh out of ideas here, can ml access the top lcd or the viewfinder bar?) - when in doubt a beep when locking (and maybe a double beep when unlocking) might also do.
#129
Feature Requests / Additional C modes
February 08, 2013, 12:54:54 AM
Like "ec on m" this falls into the category "potential ml killer features": Most cameras have a much too limited number of C settings on the dial (or no one, doh), for example 60d has 1x, 6d 2x, 5d 3x. It would be a very great, stunning and stellar (did I mention great?) feature if ml could read the Canon settings from a C position and restore them though the ml menu. Afaik the settings in the C modes aren't saved to the camera, so I assume restoring a C set through ml in C mode should be safe?
#130
The 6d & 60d are low on memory, it'd be nice if there'd be a compiler switch to turn off the audio and video (recording, not live view) features for people who never do video (i.e. me :-)) and want more ram. I'm posting this as a feature request since I guess a seasoned dev can identify the source code to wrap in a switch in no time, while it'd take me a long time to find it. I don't know how much memory would be saved tough & thus if it'd be worth the hassle.
#131
Feature Requests / EC on M
February 08, 2013, 12:45:48 AM
A feature in constant high demand though still absent from eos1 cameras is exposure compensation in full manual mode. The problem is that with the current behavior, when using auto-iso in m you're stuck with the camera's metering, even if you know the camera will get it slightly wrong or even constantly wrong to one side (for example the 6d is said to underexpose, so you're loosing dynamic resolution and you cannot ettr). Do not underestimate this, this is a big issue for pro event and esp. pro sports photogs who usually use full manual.

Request: new item "Expo -> EC on M" settable in 1/3 iso stops, only applies to full m mode and the ec is simply added/subtracted, the two dials keep functioning for setting aperture & shutter speed. If this is implemented it'd need some safety net though (like "Warning for bad settings") to prevent people setting the ec and then forgetting about it, potentially resulting in mis-exposed shots.
#132
Feature Requests / Add missing 3 phi cropmarks
October 06, 2012, 04:48:53 PM
The included phi cropmark for the se corner should be accompanied by the "missing" 3 others for sw, nw & ne - with just one it looks more like a tech demo, or am I missing something here and the bmp can be mirrored inside ml?
#133
I'd like to grab the current aperture value (Tv mode) or shutter value (Av mode) or iso (M with AutoISO), but while focus stack is running the camera doesn't measure these values until the next pic is actually taken. How do I get them - simulate half-shutter press, and with what command?

Background: I'll fill my own feature request again :-> and am adding an auto-cancel if lighting changes too much while running the stack.
#134
I know that ml cannot control focus w/o liveview (doh!), but is there a way to start liveview w/o the camera turning on the screen? That would at least simulate a quieter operation, I'd like to prevent focus stacking to constantly flicker between shots...
#135
If "Image Review" is set focus stacking is slowed considerably... I guess because there is this loop with get_out_of_play_mode() there is no direct way to set Canon variables, i.e. disable "Image Review" before starting the stack and re-enabling it afterwards?
#136
I think the "rack focus" and "stack focus" triggers in the focus menu should/could to be merged since they are mutually exclusive - rack is for video, stack/bracket is for still shots.

Before I do something that only works on my 60d (the only one I have or know) I wan to better make sure: Is there a dedicated video mode (60d: last setting on dial) on all supported eos, so ml can detect if a video or lv photo mode is selected? And if so, is there an existing variable I can check?
#137
EDIT: Please vote here, but discuss in the existing thread :-> http://www.magiclantern.fm/forum/index.php?topic=2812

Since it was discovered that the 1dc is "just" a more expensive 1dc with a firmware upgrade, people all over the place (like the CR forum) state that the Magic Lantern will hack the 1dx to save people spending money on the 1dc.

Apart from my personal opinion (see discussion thread) I'd like to get an impression of the general feeling, so here's the possibility to make your voice count (well, at least numerically).
#138
Forum and Website / What do the user classes mean?
September 26, 2012, 07:37:27 PM
I know supporter means you have paid some $$$ for ml ... but what does contributor (yellow bar) or developer (green bar) mean, and what does it take to be acknowledged as such?
#139
General Development / Suggestion: Focus menu improvment
September 26, 2012, 07:13:37 PM
Am I the only one who thinks "wtf?" all the time when looking at the focus menu? The rest of the menus is neatly organized, but in the focus menu rather informational lines (like "Focus End Point") mix with settings, and rack/stack/bracketing options are all over the place.

If no one violently opposes, I'd integrate the following change in a patch:
* Move "Focus StepSize & Focus StepDelay & Rack Delay" the menu that is @"Stack focus"
* Move "Focus End Point" down to the other informational lines
* Merge "Rack Focus" and "Step Focus" triggers because they are mutually exclusive anyway: You do Rack focus in video mode and stack/bracket focus in the photo modes, so ml should be smart enough to trigger the correct one itself.
* Maybe add a real "Reset distance" option because it's not intuitive that have to use SET on the distance like now

The change might break some existing stack/rack focus tutorials, but I don't think too severely, and you cannot make an omelet w/o breaking eggs :->
#140
When I added focus bracketing (see pull request) I wanted to add an "auto" setting that takes one shot behind and/or in front the current focus pane so that the start/end of the depth of field is where the original focus was. The intention to use the whole dof on the object and not unnecessaryly shoot some sharp air next to the object - it can be done with mf, focus peaking and dof preview but I'd like to automate it.

This would be *extremely* convenient for focus stacking, too - instead of manually guessing a stepsize for a given aperture ml could calculate it so that the dof-panes are exactly (or with a little overlap) behind each other with no missing parts out of focus!

Ml already reports the dof in meters - I didn't really look at the code yet, but can anyone tell me if there's a way to get a stepsize for the focus command from these dof values?
#141
Feature Requests / Powersave for focus peaking
September 23, 2012, 11:26:38 AM
I really like peaking when doing macro work, but it drains the battery even on the rather power-efficient 60d in no time. Setting the "turn off global draw" timer is nice, but not a real alternative because it disables the whole thing. As it is now, when I'm running low on battery I cannot use peaking anymore ... and yes, I could buy a bunch of spares, but I'd prefer a software option :-)

If possible it'd be nice to have a powersave option that either would use a tweaked more power-efficient algorithm or simply lower the update frequency from "as fast as possible" to "as slow as usable" - or wouldn't that make a difference battery-wise?
#142
This is a bit embarrassing, but I just cannot get Mercurial to update my repository. Even if there is a update "hg update" just shows "0 files updated, 0 files merged, 0 files removed, 0 files unresolved". If I try to force the newest revision via "hg update -r 00110a6f83aa" it says "abort: unknown revision '00110a6f83aa'!". This is what "hg summary" shows:

parent: 4756:04ef6f499dc2 tip
delete splash screen
branch: unified
commit: 1 modified
update: (current)

A fresh checkout via "hg clone https://bitbucket.org/hudson/magic-lantern/ -u unified" gets the new files, but of course kills all local changes. Argh - help please!
#143
I'm usually changing a line in menu.c to beta_warned=1 because I know I compiled it myself :-p

But maybe it'd be convenient to include a generic option that is switchable through Makefile.user. The other option would be to wrap all the beta code in a macro, reducing the build size a bit for release builds.. just an idea.

EDIT: Here's the patch, just add -DCONFIG_RELEASE_BUILD to CFLAG_USER ...

# HG changeset patch
# User Marsu42
# Date 1348137927 -7200
# Branch unified
# Node ID ae35f7a27e6e1358606a7e5afe49c909e707c7de
# Parent  00110a6f83aa7c05bb19f46c71c456f29ffedd13
Option to skip beta warning & some optimization CFLAGS (disabled by default)

diff -r 00110a6f83aa -r ae35f7a27e6e Makefile.user.default
--- a/Makefile.user.default Thu Sep 20 10:38:31 2012 +0300
+++ b/Makefile.user.default Thu Sep 20 12:45:27 2012 +0200
@@ -19,7 +19,7 @@
PYTHON=python2

# You can customize CFLAG here
-#CFLAG_USER = -mlong-calls \
+#CFLAG_USER = -march=armv5te -mcpu=arm946e-s -O2 -DCONFIG_RELEASE_BUILD \

# Naming convention for Magic Lantern builds:
# General rules:
diff -r 00110a6f83aa -r ae35f7a27e6e src/menu.c
--- a/src/menu.c Thu Sep 20 10:38:31 2012 +0300
+++ b/src/menu.c Thu Sep 20 12:45:27 2012 +0200
@@ -155,7 +155,12 @@
*/
}

+#ifdef CONFIG_RELEASE_BUILD
+int beta_warned = 1;
+#else
int beta_warned = 0;
+#endif
+
void
draw_beta_warning()
{
#144
General Development / Benchmarking & CFLAGS
September 08, 2012, 01:28:31 AM
1. cpu optimization:

I tried different optimization flags for the arm cpu and would advise you use "CFLAGS_USER= -march=armv5te -mcpu=arm946e-s" as it reduces the autoexec.bin size by -12% while the "CFLAGS_USER= -march=armv5te -mtune=arm946e-s" only cuts 6%, both result in no performance changes in the zebra benchmark.

2. gcc optimization:

On my 60d, a -O2 version is 20% faster in zebras than -Os. However, -O3 crashes the camera, so I cannot say how much faster that would be. The problems have to be one or some of the added flags over -O2, i.e. "-finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone" ... with try & error it would be possible to find the culprit and exclude it like for example "-O3 -fnoinline-functions" if anyone has time to spare.

3. gcc version:

The Linaro gcc 4.7 shows no fps improvement over vanilla fsf 4.6. That isn't really a surprise, many Linaro optimizations are for the latest arm cores, and it's only the zebra test that was tested. Still, as I wrote before Ubuntu & Linaro have switched to Linaro and it certainly doesn't hurt. I'll run this compile on my camera and see if any regressions occur, but since few things changed from gcc 4.6->4.7 I don't expect any.
#145
General Development / Compile ml w/ Linaro gcc?
September 05, 2012, 11:05:34 AM
I'm just setting up the arm toolchain and noticed that that the summon-arm script contains the outdated gcc 4.6.2 (current is 4.6.3).

Is there any reason to use this particular gcc release, and why doesn't it use the current linaro 4.6 or 4.7 gcc which is supposed to be the latest and greatest for building arm compiles? Is it just because of "never touch a running system" or does any more current gcc release make your cameras crash and burn? What gcc do you guys use?
#146
Feature Requests / Calibrate Audio RemoteShot Level
August 28, 2012, 08:39:46 PM
Setting the "Trigger level" for Audio RemoteShot is rather annoying because you have to exit the menu, try, change, retry, ... until finding the level that is louder than the background noise and still does the trigger w/o firing a gun next to the camera.

Suggestion: When opening the "Audio RemoteShot" submenu, add an audio meter or some much simpler binary indicator that shows if the threshold is reached. This way the the level could be changed in the submenu and it the result could be seen/tried *immediately*. Imho shouldn't be too difficult to implement because the metering code is of course already there and would simply have to be tied to some indicator in the submenu?
#147
Um, maybe I'm missing something obvious here, but on my 60d I cannot get the "Arrow/SET-shortcuts" to work (ml 2.3).

I tried "Audio Gain" and/or "ISO/Kelvin", but neither the SET button nor the arrow keys produce any result in or outside live view. The built-in help isn't helping... maybe I still have set something else that collides with this feature, but I tried to turn off everything else that uses the arrows or set keys.
#148
Feature Requests / Improvement for "Compare Images"
August 24, 2012, 11:17:54 PM
I just remembered why I almost never use the "Compare Images" feature (next to the thumb-breaking SET+Wheel :-)), maybe an improvement is possible?

1. When I use it, it's at 100% zoom to see which exposure is sharper. But since *handheld* exposures always have a shift, I never can compare the same element (like the eye of an animal where the focus is supposed to be). Is it possible to add the ability to shift one part of the split screen around to get the correct part on screen? As it is now, using the directional keys after initiating "Compare Images" quits the split screen immediately.

2. The diagonal split seems a bit awkward to me, an option to do a clear vertical split into left & right would make more sense to me personally.
#149
I just noticed that the SET-Button does nothing when reviewing pictures (I know SET is taken otherwise), at least with my config on 60d. Is this just me, or is this button really not used? If so, I guess I can come up with some great ideas on how to use it :-) because it is in convenient close range when flipping through pictures with the wheel and panning the picture with the direction buttons...
#150
... at least for verified members like supporters, devs etc. I'm perfectly capable of writing a meaningful post in less than 90 seconds, but with the limit now the text is gone beyond recovery if submitted too early which is rather tiresome.