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 ... 4 5 [6] 7
Feature Requests / [WONTFIX] Reodering or other order of items in "My Menu"
« on: February 09, 2013, 02:05:01 PM »
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!

Feature Requests / Customization & Lens dependency for Handheld Shutter
« on: February 08, 2013, 01:07:42 AM »
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?

Feature Requests / Fast access to and foolproof confirmation for settings
« on: February 08, 2013, 12:59:21 AM »
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.

Feature Requests / Additional C modes
« on: 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?

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.

Feature Requests / EC on M
« on: 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.

Feature Requests / Add missing 3 phi cropmarks
« on: 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?

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.

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...

General Development / Can ml set Canon variables like "Image Review"?
« on: September 29, 2012, 02:30:31 AM »
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?

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?

General Development / POLL: Should ml attempt to hack the 1dx into a 1dc?
« on: September 26, 2012, 08:39:49 PM »
EDIT: Please vote here, but discuss in the existing thread :->

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

Forum and Website / What do the user classes mean?
« on: 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?

General Development / Suggestion: Focus menu improvment
« on: 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 :->

General Development / How to get number of focus steps for dof range?
« on: September 23, 2012, 02:00:04 PM »
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?

Feature Requests / Powersave for focus peaking
« on: 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?

General Development / How to update local reposititoy to latest rev?
« on: September 20, 2012, 10:32:37 AM »
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 -u unified" gets the new files, but of course kills all local changes. Argh - help please!

General Development / Change hardcoded beta warning to macro?
« on: September 20, 2012, 10:20:47 AM »
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 ...

Code: [Select]
# 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 @@
 # 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 @@
+int beta_warned = 1;
 int beta_warned = 0;

General Development / Benchmarking & CFLAGS
« on: 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.

General Development / Compile ml w/ Linaro gcc?
« on: 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?

Feature Requests / Calibrate Audio RemoteShot Level
« on: 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?

General Help Q&A / How to make the shortcut keys work (60d ml 2.3)
« on: August 28, 2012, 01:31:20 PM »
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.

Feature Requests / Improvement for "Compare Images"
« on: 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.

Feature Requests / SET button at picture review - not taken?
« on: August 24, 2012, 08:27:25 PM »
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...

Forum and Website / Plz remove 90sec delay limit between posts...
« on: August 23, 2012, 01:15:06 AM »
... 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.

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