Messages

[CONFIG_INT]

PR already here: https://bitbucket.org/hudson/magic-lantern/pull-requests/779/add-switch-to-reset-exposure-compensation/diff

A fix for https://bitbucket.org/hudson/magic-lantern/issues/2448/exposure-compensation-display-is-slow somewhat, as at least on (my) EOS M, I find the wheel a pain to use to get EC right (also this does not help https://bitbucket.org/hudson/magic-lantern/issues/2257/selected-wheel-setting-marked ), so having it reset to zero on restart helps me and my shooting style.

Hope it's useful for others too.

Some points that might be up to debate:
* it's ok as CONFIG_INT( hey, it does not error out on compile like this ) instead of static CONFIG_INT?
* is the position in the menu at Prefs/Misc key ok?
* is this working as I think on all cameras?

Thanks

DO read post #1716

Wasn't this (crop mode) something that had an issue on EOS M? It got reset on restart or something.

See my post above.

This is old and unfortunately unmaintained.

Did you try MLVFS already? It's on active development: http://www.magiclantern.fm/forum/index.php?topic=13152.0

You are not shooting RAW where styles don't apply?

@biggles: Do not use that 2.3 version, it's years behind. Get the Nightly.

Compile issue?

Code Select Expand

Building module raw_rec...
Updated HGVERSION
[ README   ]   module_strings.h
[ CC       ]   raw_rec.o
[ HGDIFF   ]   hgdiff.tmp
[ MODULE   ]   raw_rec.mo
[ STRIP    ]   raw_rec.mo
[ OBJCOPY  ]   raw_rec.mo
[ EXPORTS  ]   raw_rec.sym
00001984 raw_video_enabled
000019ac raw_movie_filename
[ DEPENDS  ]   raw_rec.dep
Will load on:
    6D.116
Will NOT load on:
    6D.113 (powersave_prohibit, powersave_permit)
Not checked (compile ML for these cameras first):
    1100D, 500D, 50D, 550D, 5D2, 5D3, 600D, 60D, 650D, 700D, 7D, EOSM
[ GCC      ]   raw2dng
[ GCC      ]   raw2dng
../lv_rec/raw2dng.c: In function 'find_and_fix_cold_pixels':
../lv_rec/raw2dng.c:1213:9: error: 'for' loop initial declarations are only allowed in C99 mode
../lv_rec/raw2dng.c:1213:9: note: use option -std=c99 or -std=gnu99 to compile your code
../lv_rec/raw2dng.c:1215:13: error: 'for' loop initial declarations are only allowed in C99 mode
../lv_rec/raw2dng.c:1233:5: error: 'for' loop initial declarations are only allowed in C99 mode
../lv_rec/raw2dng.c:1243:9: error: 'for' loop initial declarations are only allowed in C99 mode
../lv_rec/raw2dng.c:1245:13: error: 'for' loop initial declarations are only allowed in C99 mode
make[4]: *** [raw2dng] Error 1

Magic Zoom is not something that I use, not sure if because it does not work as well or anything else, although I do like do play with my OM Zuiko glass, I just use the zebras.

I'll take a look asap.

I asked this somewhere else and no, you can't.
Post #701 and #702 here: http://www.magiclantern.fm/forum/index.php?topic=12523.msg145189#msg145189

[4]

Do get 1.4.3 from Bitbucket and retry

Any new idea regarding the "broken" lenses that don't actually trigger the correct apperture in FRSP?

What interval?
Works fine here for both normal and silent pics, with 10s and Canon picture review of 2sec.

If you read some pages behind you'll see tha some lenses don't actually close the aperture and only shoot at max aperture ( say if it can do f/2 and you setup f8, when it takes the picture it will be at f/2), hence overexposure.

Do test by looking at the lens to see if it actually closes as it should, say test with f/22.

So 750D, 760D, 80D, EOS M3, 7D Mark II, 5DS and 5DS R ? 

There is no stable any more, not in the last 3 or 4 years.

It's a rolling version, always use the latest nightly, always submit bugs (reproducing) using the latest nightly.

Not to mention, you get all the fun toys _now_

Umm, it's not working like this here, but:
* 1 -> lock only focus on * (star) press (or left button how you've said), it will meter and take the picture on button press.
* 3 -> lock both focus and metering on star press, it will just take the picture (unchanged) on button press.

Both 0 and 2 don't do anything on * (star) press, at least on my EOS M.

In Canon menu -> Key with four squares -> Custom functions (Fn.p) -> Fn.pIV AE lock -> did you use option 1 or 3? Test them both.

Thanks for the PR on EOS M. Looks good so far.

Yes, I can confirm too. Strange.

@Licaon_Kter: are you able to get correct behavior on your EOS M?

Not sure what the problem is though.
S/he make a screenshot of ML or what?

Reset ML settings to default.
Reset Canon settings to default.
Retry.

 What ML build date?

Good idea, although on import/download you could just (bulk)rename MLV/RAW files.

Maybe @hjfilmspeed thinks you can just upload ML there in memory, but that's volatile IIRC, right?