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 ... 7
One thing I've never quite understood about the inner workings of the camera: How is it that we need these awful keypress simulations to get some things done? Isn't there some way to *directly* access whatever-that-key does, there has to be some entry point in the Canon fw we can simply call like for "metering and af start" - or am I getting this entirely wrong?

The current annoyance is that I'd like to engage *H (expo lock hold) with ML, but no button it is available has a gui event on the 6d - thus I cannot simulate it. Harrrrrrgnnn ...

... (background): this would be the solution to the braindead 6d af-pt-biased eval metering, the idea is to auto-expo-lock whenever engaging the af with halfshutter. The "dual button method" with simple hold on halfshutter and backbutton af is too slow and cumbersome for quick shooting.

General Development / fyi: gcc 4.9.3 breaks ml (sometimes)
« on: July 13, 2015, 09:26:58 PM »
Just to spare all you good people some trouble and b/c it might be the natural inclination of the hardware hacker to use bleeding edge software, too...

... the latest gcc 4.9.3 (from launchpad) breaks my 60d build, the led activates on boot and that's that. It's working just fine though with gcc 4.8.4, so some new optimizations don't like the ml source or there are some bugs in 4.9.

Strangely, compiling the very same source with 4.9.3 for *6d* works just fine. Go figure :-p

Yo, after managing to set my 6d to m-raw for some important shots (I didn't notice the warning, even though it was enabled) I'd like to add the option to *lock* the camera to raw mode, i.e. extent the feature in tweaks.c

Problem is: setting PROP_PIC_QUALITY seems like a premiere way to brick the camera, I guess thus the feature name "FEATURE_PICQ_DANGEROUS". I don't know if a "C" mode is a foolproof safeguard at least for testing:

The ML code contains the function to read the prop and figure out if raw is enabled, but how do I *set* raw - or is this not possible in a reliable way at all? Did anyone succeed at least on the current gen bodies (6d,5d3), how did you do it?

Feature Requests / Exif data (inc. gps) in silent dng
« on: May 28, 2014, 08:47:07 AM »
It would be nice if the (well, 6d for now) would add [edit: the usual suspect lens/camera exif data inc.] the current gps information to silent dng pictures so you can skip adding the geo tags from the tracklog later on. Currently, chdk-dng says: "Code stripped down a bit, since we don't care about GPS and advanced exif stuff (at least for now)"

Not a very pressing issue, but I'd like to add a feature request here as a reminder if someone works on gps or dng anyway.

General Development / How to deal with prop set lag?
« on: May 22, 2014, 05:45:28 PM »
I guess you know the issue as it affects various modules: How do you detect if a user changed a property when the ML code also changes it?

Example: In auto_iso, I want to disable the module when the user changes/overrides the iso value. But since there is a lag between setting a prop and it being actually changed I cannot really tell if it was the code or the user that changed it:
1. current iso: 400 -> code sets it to 200
2. next shoot_task cycle: code detects "still 400" -> is it not yet changed to 200 or has the user set it back to 400?

Question: I recently saw some time detection (I guess it was alex' code?), but I don't quite remember where. Is there some rtos-like max. delay when I can say that the prop should have been changed by then?

General Development / Brick camera with wrong C.Fn settings?
« on: May 22, 2014, 04:13:57 PM »
I'd like to add some c.fn toggling to my hotkey module (esp. switch to different af tracking "scenarios" on 6d by modifying the 3 relevant c.fn settings).

I'd currently hardcode this for my 6d, but I could also add a gui for "set c.fn (enter value).(enter value) to (enter value)." Alas, I certainly won't read all Canon manuals what c.fn settings are valid on what model, thus the question: Can users brick cameras by setting c.fn to out of bounds values - or does Canon code simply ignore wrong settings?

Feature Requests / Tie ML/Canon settings to lens id
« on: May 22, 2014, 04:10:09 PM »
Is there anything in the works concerning an abstraction layer to tie specific settings to the lens that is on the camera?

Currently, I'm (nearly :-)) about to hardcode my 3 lenses into my auto_iso module so I get lens-specific min. shutter settings in av mode - but I can imagine lots of other options (Canon and ML) that I always switch based on the lens I'm using as they indicate different "shooting scenarios".

If the core would provide some framework for this, other modules might also profit from this ... but alas, as always it probably needs some time-consuming gui work next to the backend.

Feature Requests / [INVALID] Focus stacking "burst bracketing" !?!
« on: May 13, 2014, 12:07:13 PM »
The latest versions of Helicon remote have a feature called "Burst Bracketing" - after pre-setting the max. fps of the attached camera it does this:

New feature - burst bracketing (combining continuous Stackshot movement with burst shooting to shoot focus stacks rapidly - in a matter of seconds)

Obviously, if this is possible this should go into ML asap :-) as it fixes the main shortcoming of focus stacking - the crawling speed which leaves you with broken stacks when the (natural) light changes.

Feature Requests / [DELEGATED] beep_custom() with volume
« on: April 29, 2014, 01:39:41 PM »
Could beep_custom() please be amended with an option to set the volume of the beep sound? Currently it's only global, but an added volume setting relative to that, i.e. producing quieter sounds (maybe in steps 1-10 or whatever) would be very welcome. Reason: I want to have quieter "notification" sounds and louder warnings.

I'd like to add a small function that resets the af point to center if I turn on the camera. Where do I hook this function w/o executing it all the time in shoot task as I usually do? Thanks!

I'm curious, but don't understand how ML interfaces with Canon and how much original memory management is in ML... gcc 4.9 now includes the address sanitizer for arm, is this useful for ML?

General Development / How to write a proper README.rst?
« on: March 31, 2014, 11:34:38 AM »
I cannot make my README.rst show the description text in camera - and I also don't see it from any other module *except* but that source code is unavailable atm :-\ ... where do I get a working README.rst sample? Thanks!

Feature Requests / Gamma preview instread of linear ev correction?
« on: March 06, 2014, 11:35:21 AM »
I'd like to preview ettr'ed or (deliberately of course :-)) underexposed shots with the built-in exposure preview in qr/play mode via the cursor keys or set+wheel.

Would it be feasible and probably a minor code addition to add an option for a non-linear preview, i.e. some gamma-ish curve that keeps the black and white point where it is - or even does a contrast optimization to fill the histogram? This would be a nice preview for later postprocessing and would help me to decide if the shot is ok or I need to modify something to save work later.

Feature Requests / [IMPOSSIBLE] Custom info overlay in play/qr
« on: March 02, 2014, 08:09:09 PM »
The Canon overlay in play/qr modes is cluttering the view - the font is larger than necessary, and they display information at least I don't care about. At the same time, switching the overlay off completely isn't an option since I require *some* pieces of information.

Would it be possible to print a customizable ML info line instead of Canon - or is some of the information Canon has (like Av/Tv) inaccessible to ML in play mode? Having this feature would also be useful when (and if) ML file tagging is added.

Edit: Marked this as impossible unless someone is willing to to the re alex described below.

General Development / Check for real/fake keypresses in module?
« on: March 02, 2014, 12:22:18 PM »
In the core, I can tell fake keypresses from real ones with an IS_FAKE(event) check & only then look at event->param keycode - but modules only get the button code. So how do I check for fake keypresses in a module? Thanks!

If anyone manages to figure out the gps props for the 6d, I'd like to include this in a module:

1. Adapt the satellite fix time according to the camera idle time, i.e. get new positions fast when the user is obviously doing something with the camera, but lengthen the intervals when the camera is doing nothing to reduce battery drain.

2. Auto-disable on shutdown, (re-)enable on startup to prevent battery drain when forgetting to switch gps off.

Any other ideas on what to do with gps are welcome.

Feature Requests / [DONE] Adjust ML aperture/shutter strings to Canon
« on: February 23, 2014, 09:46:59 PM »
Inspired by the discussion here:

I'd like to suggest two functions (via lookup tables if needed) that cast Canon's 8-step internal shutter/aperture values to the very same human readable "f/xyz" and "1/abcd s" that Canon uses for the given exposure level increments, no matter how accurate they are. Imho the discrepancy between ML menu and Canon menu/lcd/vf doesn't help usability, I stumble upon this all the time.

General Development / What keypress events are available on what model?
« on: February 18, 2014, 07:26:29 AM »
Is there a table somewhere stating which keypress (and unpress) event works where, in and outside live view?

This would be very useful when trying to code a module that works cross-platform, if it doesn't exist how about creating one - maybe with an automated tool that collects the required feedback from owners of these cameras?

Feature Requests / Sticky LCD exposure correction for ettr shots?
« on: February 17, 2014, 08:10:45 PM »
One problem with ettr shots is that they look horrible on the lcd and any newbie wouldn't suspect this is actually an excellent exposure if treated correctly in postprocessing. Personally, I often have a hard time figuring out if the shot is ok in other ways than the exposure so I use the exposure correction via set+wheel or left/right cursor keys.

My idea: Automatically determine what exposure correction is needed for ettr shots, and sticky this to the preview of this shot so apart from the histogram the shots looks "normal" like non-ettr. As a side effect, it's usually also easier to see where blown whites might be.

General Development / The big "keywords & tagging" frontend thread
« on: February 17, 2014, 07:39:03 PM »
I recently requested a backend for tagging to xmp files here, alex says it can be done:

So the question is: How do we implement it on the frontend side? To start the discussion, I'll write what *I* want to do with tagging and what approach would be sufficient for me. Feel free to write what you want to do with keywords & tagging so we can start coding.

I'd like to have more than one dimension than just 0-5 rating stars, at least *two* more tags (usually "dupe" and "todo", but let's call them "tag1" and tag2" so I can kickstart postprocessing when back at home.

I'd implement them using the current SET+Wheel code which I just modified to also work with cursor/joystick left-right. 1x Left would add "tag1", 2x Left "tag1+tag2", 1x Right "tag2", 2x Right also "tag1+tag" ... and the thing would wrap around with no tag1/tag2 at all when back.

In theory, tagging could be extended to whatnot, with unlimited custom tags entered in a text field and whatnot - I'd like to get a simple & realistic version that can be implemented by little devs like me, or somebody else also has to pick up coding the frontend.

Feature Requests / Mode switch in C modes?
« on: February 17, 2014, 07:15:50 PM »
I know mode switching is dangerous and alex bricked his 60d with this method... but I have to ask again: Is this also the case in C modes, as these don't save any settings permanently?

For wildlife/action switching modes by a button like on 1dx would be a god-send, anything else can be set by ml, just the mode itself (av/tv/m) switching is missing.

Feature Requests / Backend to add/remove keywords to sidecar files
« on: February 16, 2014, 02:21:21 AM »
We have already got the option to add post-deflicker and dual_iso tag information to xmp sidecar files.

What I'd like to have is the option to add or remove arbitrary keywords to this file, complete with the option to create the sidecar it if it doesn't already exist - like in CheckKeyword("tag"), AddKeyword("tag") and RemoveKeyword("tag").

The front-end (which buttons to press where in what mode with what feedback) isn't the problem - but have no clue about the file r/w stuff, so it'd be great if some other dev could help out with creating these backend functions :-o

Imho it's well worth the work, the 5d3 even got the (in)famous rate button because for pj work tagging in-camera is important - so I'm sure adding the ability for more than one dimension (rating) would be widely appreciated.

Using Bitbucket, when I try to sync my ML fork with the master I'm getting the error message "Unable to merge - conflicts during merge". Problem is: even after resolving all issues with files marked with "conflict" in the diff, it still fails w/o any file marked as a problem - unlike the promised "View the conflicts".

I have encountered this problem multiple times by now and the only solution I found is to completely reset, i.e. delete the repo, re-fork and re-patch in all my changes. Is there any way to find out what the problem is - probably by running hg directly w/o BitBucket? Thanks!

I know we cannot access the top lcd information directly - but maybe we can fool it into displaying what we want? My idea is to hack/modify the free card space information so we can get any number we want in the "remaining shots" display area.

This would be invaluable for photo mode when feedback is required or information could be given like set/remaining # of ml backets/focus stacks and whatnot. As my previous feature request about a back LCD notify box I think more feedback in photo mode would be a huge usability boost, just letting the camera beep sounds like C64 age again :-p

Feature Requests / Backend for custom back lcd visual feedback
« on: February 09, 2014, 06:34:38 PM »
Adding to my all-time favorite requests (submenus (nearly done) and array variables in modules) here's a new one:

For the auto_iso module and other features, I'd like to give non-audio feedback. The latter is limited to max. 2 beeps with varying frequencies and the audio on 6d is also very quit so it's often no good.

What I have in mind is about what Canon does on the newer Cameras with the subitems in the Q menu -  some large-print text and probably scale on the LCD w/o entering the ML or Canon menu.

One example would be to print the selected min. shutter/aperture from the auto_iso module, but I'm sure there are tons of other applications for visual back lcd feedback ... unfortunately, we cannot control the vf or top lcd, so that's the only option left.

Pages: [1] 2 3 ... 7