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 2 [3] 4 5 ... 7
General Development / [DONE] Clean up repo branches?
« on: September 26, 2013, 12:04:14 PM »
Currently there are 32 branches in the main ml repo - how about deleting the outdated branches?

They are dragged around with every fork which doesn't seem very clean & might create confusion as unified seems to be the only one being worked on... since there are so many ml working forks probably doing in-repo branches except for quick experiments isn't such a good idea at all, but create a full fork even if the person has write access to the main repo?

Feature Requests / Silent pics: Save all, mark best
« on: September 25, 2013, 10:15:20 PM »
Currently with silent pics burst, I can decide if to save all or only the "best" (= in-focus shots, if I understand it correctly(?)).

My suggestion is to also mark the "best" if saving all, or add another option for this alternative, since then I could first looking among the "best shots" and if this fails to find the one I look for sort through the rest as a fallback option.

Possible ideas to mark the "best" when saving all would be a file name appendix or a keyword marker in the dng file.

Feature Requests / [DONE] 6D: Tie SET to setting center af point
« on: September 25, 2013, 09:32:37 PM »
Focus pattern unfortunately don't work on the 6D, the whole ml section has been removed. There is one regression though, which has a large practical impact for action shooting:

Problem: With my 60D & ml, I could quickly set the af to the center point by pressing SET (= *one* click = fast), with the 6D I need to press af select and then SET (= *two* clicks = slow). Yes, this might make the difference between getting the shot you want or not.

Suggestion: Simply re-enable the part of af patterns that ties SET to quickly setting the center af point... shouldn't be too problematic if the 6D af prop is already reverse engineered or the same as 5d2?

Disclaimer: This might sound a bit outlandish to people not using flash(es), but let me ensure you this is one of the worst regressions from 5d2->6d and one of the main complaints about the 6d from portrait/wedding photogs. If this gets solved then it'd be one big brownie point for ml.

Problem: The 6D max. x-sync is only 1/180s, but it's not mainly the mediocre speed that's the problem, but the fact that you're not able to set it if "C.Fn I-1: Exposure level increments" is set to 1/3ev. The alternative 1/2ev is not practical, the interval is simply too large, esp. since the flash exposure compensation is also tied to this.

Suggestion 1 (optimal solution): Squeeze in 1/180s between 1/160s and 1/200s by intercepting the dial and force-set it in M/Tv on 1/160s->dial up & 1/200s->dial down

Suggestion 2 (a bit more usability hassle): Tie force-setting 1/180s in M/Tv to some button like SET or another less often used button ml can intercept.

Feature Requests / User base config in addition to ML defaults
« on: September 23, 2013, 01:50:00 PM »
This was buried in soem menu thread, I'm sure alex has noted it and it's not here to build pressure, but simply to move the request where it belongs:

Issue: The hard-coded defaults of ML sometimes are pretty arbitrary, plus they clutter the recent "Modified" menu. If some mis-configuration is done, resetting to ml defaults isn't a good option because a lot of carefully chosen settings are reset just to catch one problem. The current solution is to file-copy the config files on the card, but that cannot be done from the camera (quckly).

Suggestion: In addition to the ML base config, add an option to save a USER base config and base the Modified menu on this. Add a "Reset to USER defaults" option next to "Reset to ML defaults". This additional safety net would invite more feature tryouts over reboots and enable the users to fall back to their own working config in a panic situation.

Forum and Website / Split general & modules discussions
« on: September 19, 2013, 01:38:44 PM »
Suggestion: With now 10 sticky threads the "general discussion" is getting rather cluttered, I suggest adding a "module support & discussion" subforum where - next to module-related threads - each module could have a sticky'ed support thread that's mentioned in the modules' readme files.

Feature Requests / Inter-modules framework or code samples?
« on: September 19, 2013, 12:42:10 PM »
As more features get moved into modules, inter-module connections imho becomes more important as for example ettr using dual_iso's calls with "extern WEAK_FUNC(ret_0) ...". But what if I want to do these things w/o touching the other module:

1. detect if a module is loaded at all?

2. get or set other module's config vars?

Are there existing code samples anywhere? If not, it'd be great if there would be a core framework for these, for example module_check_enabled("ettr") and module_set/get_config("ettr", "auto_ettr", "0").

Feature Requests / "On Demand" option for overlays in Quick Review
« on: September 17, 2013, 10:43:10 AM »
I like the option to look at focus peaking, Zebras, ... in play mode after pressing the appropriate button when setting "Global Draw" to "Quick Review" or "ON, all modes".

Problem: the overlays are *always* enabled _without_ button press in Quick Review right after taking a shot which draws too much battery power if I just want to have a quick look at the framing and not the exposure.

Request: Add an option "Quick Review GD -> Always on / On demand" for example in Display -> Advanced Settings" to let the user choose if the overlay is applied right away or if a button press is also required in quick review mode after taking the shot just like it is in play mode now.

Feature Requests / dual_iso: Option to embed original cr2 in converted dng
« on: September 16, 2013, 09:28:21 PM »
The dng spec has the option to embed a raw file like cr2 in the converted dng for safekeeping if it should be required later on, for whatever reason. The embedded can be extracted or deleted later on.

Since the cr2hdr process is lossy and a newer version might have better results, I'm currently keeping all old DUAL cr2 around, resulting in quite a messy archival and tagging situation. It would be great if cr2hdr would have the option to embed the original cr2 in the dng so both are kept in the same place, though of course at the cost of a larger file - but if the original file is to be kept anyway this doesn't matter.

Feature Requests / Raw histogram (at least) for picture viewer
« on: September 15, 2013, 01:19:31 PM »
I couldn't find a request for this, so here it goes (again?):

It would be really helpful to have a raw histogram not only for the last shot taken, but added as an option to the ml picture viewer or to the Canon picture player. It doesn't have to be fancy at all, actually *any* hint, even a text message, if there were blown highlights in the cr2 would be really helpful to decide if to re-take a shot or not.

General Development / [DONE] Bitbucket comment forbidden?
« on: September 15, 2013, 12:15:48 AM »
I cannot comment on bitbucket commits anymore, is this a bug or a feature, i.e. did the devs decide not to allow normal users to comment there but prefer this forum?

Feature Requests / Array variables for modules (CONFIG_ARRAY_ELEMENT)
« on: September 08, 2013, 11:24:16 AM »
This was buried in some dev thread, but I'd like to add an "official" feature request for this:

Modules currently don't support multiplexing variables as arrays, which is unfortunate since it's an extremely useful function and it cannot be worked around easily. As soon as an author module wants to have different config or variable sets, this is the way to go - take for example different exposure curves in the autoexpo module. I also wanted to use this in a module of mine to tie variables to dial settings until I found out that copy/pasting my code that was working in the core was broken as a module :-\

In modules, the user can add entirely new menu points with menu_add - but imho sometimes a small enhancement would be better placed under an existing menu point from the ml core. I suggest to add this to the function, so you could write something like this:

Code: [Select]
menu_add_children("Prefs", "Misc key settings", my_menu_children, COUNT(my_menu_children));

The file_man module and one of mine show the OldAPI warning with the latest trunk and won't work, strangely the other bundled modules work, even yet another one of mine.

I read that "just recompiling" should bring up the modules up to the new version (, but obviously this isn't it - am I missing something here?

EDIT: I solved it myself, though "make clean" wasn't enough but I had to clean up some leftover files from the module directories manually.

Though older cameras like my 60d only have a *max.* autoiso range setting in the canon fw, I just discovered that the min part doesn't contain junk or zero, but actually the setting that is used - iso 100. Could it be that Canon uses this value in their fw, but just didn't provide an ui frontend for it? If so, exposing it would make a great addition for the ml expo menu!

Did anyone try to *set* this value yet (I'm a little hesitant to do something like this, even in C mode, since I cannot afford to brick my camera)? This is how it's read, the same as on 5d3/6d:

Code: [Select]
int canon_min_iso = auto_iso_range >> 8;

General Development / Nested/2nd level submenus?
« on: August 26, 2013, 02:36:05 PM »
Is it possible to nest submenus, or is this a planned feature?

Some menus I have in mind with a lot of choices, for example for choosing hotkey functions, simply don't seem appropriately placed in the main menu hierarchy, and having submenu-submenus would allow splitting up large item lists into more logical pieces.

I would like to make some ml settings lens-dependent, i.e. auto-switch them when changing lenses. Question is: How to I tell one lens from the other the easiest way, ideally w/o comparing strings like name (do have all lenses this field?) and multiple properties like min/max aperture?

If there is no easy way atm, I'd like to request a lens_id field for the lens_info struct where all unique lens properties are distilled into one easy, unique hash or number you that can be quickly compared and saved in a config value. Rather than doing this in a module imho this should be so useful it'd be better done in the ml core and added to lens.h

Feature Requests / ISO bracketing with same exposure
« on: August 25, 2013, 03:01:23 PM »
The purpose is different from the existing bracketing, but it could be integrated nevertheless:

When taking long-time exposures at night often some things move and are blurred, an example would be a flag. If you want to prevent this you have to take another shot at high iso and blend both exposures.

I'd like ml to automate the shooting sequence, i.e. with a new option "same exposure" use the "0 + ++" pattern to take a bracketing sequence with the given EV spacing by raising the ISO value and modifying the shutter accordingly.

I could just do this in a module, usually 2 shots (one iso100, one high iso) are enough, but if it would be a real bracketing sequence with multiple shots it would allow the shot with the best blur/noise tradeoff to be isolated much easier.

General Development / String localization?
« on: August 23, 2013, 05:10:56 PM »
Are there any ideas, plans or schedules for localized ml menus/strings other than patching the whole source code and (this is the bad part) adjusting this patch for every changeset?

To people accustomed to the Internet and participating in English forums this might be probably surprising, but at least in Germany there is a good part of the population in the east who did not learn English in school (and forgot their Russian :-)) and any non-localized user interface is a objective or at least subjective barrier that is not to be underestimated.

To some, modifying their camera with a "hack" sounds obscure enough, but it's worse when the hack speaks a language you barely understand :-p ... so imho the potential ml userbase is narrower than it could be.

Can we set the shooting_mode by software, i.e. w/o turning the dial and assign switching modes to a button like on the 1dx? Thanks!

General Development / [ANSWERED] Is MODULE_KEY_UNPRESS_SET working?
« on: July 31, 2013, 01:25:30 PM »
Um, I'm trying to catch the MODULE_KEY_UNPRESS_SET event, but it doesn't work on my 60d (_PRESS_ works fine though). Is this supposed to work on every model? Are there any hidden catches when this event is called that I'm not aware of? Thanks!

Feature Requests / Purge xmp files for file browser module?
« on: July 31, 2013, 09:49:02 AM »
Do you think it makes sense to add a function to the file browser that deletes all xmp files from ml deflicker that don't have a corresponding cr2/jpg anymore, i.e. these shots have been deleted by the user? Having tons of abandoned xmp files over the place is neither clean nor tidy when browsing the folder on the pc, but then again maybe I'm the only one with that impression.

I have to admit I'm a bit confused by the state of the discussion about the flash prop (;all) ...

... but apart from setting/detecting specific flash functions, is it currently possible to detect if the pop-up / an external flash is enabled/attached _at_all_?

* Shutter: I know the raw shutter value doubles every 8, so for example 120 = 1/250s and 160 = 1/8000 ... but what the intermediary values, i.e. what is 1/180s and 1/200s?

* Aperture: What are the raw aperture values & what are the steps?

* As I read in the source code you cannot set any value but have to stick to 1/3 or 1/2 steps, but this is covered by the functions in lens.c, correct?


Afaik it's advised to just add PROP_HANDLERS in modules when needed - but can I predict in which order they are executed, for example the core PROP_HANDLERS before the modules?

In my current case I'd like to add a PROP_HANDLER(PROP_ROLLING_PITCHING_LEVEL) to auto-switch the af points from portrait to landscape and vice versa by reading the "struct rolling_pitching level_data" that is initialized in the core PROP_HANDLER.

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