Messages

[Disclaimer:]

Maybe a dumb question, but I just installed the latest nightly build on my 5D3 and in the drop down options menu of the silent mode the "full res" option is missing.

Here is a build for 5D3 with firmware 1.1.3: http://we.tl/WTYtLFJv98
Info about the build here: http://www.magiclantern.fm/forum/index.php?topic=9741.msg142766#msg142766


If you are using firmware 1.2.3 you are out of luck for now, as it's has a separate branch and I'm not that brave to try and merge it with the FRSP one


/LE:


Disclaimer:
I don't have anything else besides a M1, but I can compile ML, so keep in mind the warning on top of this page: http://magiclantern.fm/downloads.html STILL applies if you choose to install one of these builds.

I recently started using ML on a 1100D for astrophotography.
I would like to use the silent mode.

You can't, it's not supported: http://builds.magiclantern.fm/#/features


Trying to compile it yields:

Code Select Expand


Will NOT load on:
    1100D (raw_lv_redirect_edmac, raw_lv_request, raw_lv_settings_still_valid, raw_lv_release)

And I have the same question that Silverburn, does anyone shoot in video mode with the M?

Apparently someone is shooting on M1.

here or build it from the repository

M1 here:

Got the M1 build compiled again:
What's changed:
*updated to the latest FRSP commit e6e9753
*bypassed the dual_iso module build error introduced in commit 9e99764 ( info here )
*bumped wait_lv_frames from 4 to 20 so one can use *-hold for AF ( just set C.FnIV to 1 or 3 ) when taking FRSP ( info in these posts )
*added the Depth of field display patch

Link: <removed>

/LE: links fixed


/LE: use the nightly, it's merged in main already

On my M1 I see it at Shoot -> Motion Detect

FPS is easy to check, open the FPS override submenu, but don't enable the feature (just read the default configuration).

29.9xx

The value is higher than expected; does this mean there is a noticeable delay between pressing the button and focusing?

Not that I see, given the 22mm is slow(ish).

Another hypothesis: what FPS do you have in LiveView in photo mode? IIRC it's 60 on the EOS-M, and 30 on most other cameras.

How do I see the FPS?

If you don't select a focus point, what happens? It stays on 1?

Yep, behaves like wait_lv_frames = 4 does for me.


On another thought, I can't repro the success with wait_lv_frames = 10 anymore.
I was testing in a dark room in the previous post, but now in daytime light it just does not focus. I bumped it to 15 and it's better but it still misses sometimes, might depend on whether the AF says it's got focus faster or something?
Also, after it starts, even if C.FnIV is on 1 or 3 it will not engage Focus unless I change the mode, say from 1 to 3 and back, after that it works.

[raw_rec]

You can print things with bmp_printf or NotifyBox, or simply printf.

Right, I saw that in your code, I'll try.

I think it's worth trying smaller values like 5 or 6.

I'll do this next, at first I though I go up to 10 but then I wanted it to be really long just to be sure my 22mm (non-USM, non-IS) that I test with has time to hum along, now what I do what to know is at 20 it should take I picture by itself eventually or did I read this wrong? If so, how long it should take?

About short presses, I'm not sure what I can do.

Actually it's better now, having a way to AF is more important. Although I would still like a way to select other button ( like REC/INFO/SET/whatever ) and leave * alone only for AF, as far as I can see this should be possible by replacing get_half_shutter_pressed() with a custom get_silent_button() or something.


And another thing, on this branch now raw_rec and dual_iso modules fail to build:

Code Select Expand

Building module raw_rec...
Updated HGVERSION
[ README   ]   module_strings.h
[ CC       ]   raw_rec.o
[ MODULE   ]   raw_rec.mo
[ STRIP    ]   raw_rec.mo
[ EXPORTS  ]   raw_rec.sym
00001960 raw_video_enabled
00001988 raw_movie_filename
[ DEPENDS  ]   raw_rec.dep
Will load on:
    EOSM
Not checked (compile ML for these cameras first):
    1100D, 500D, 50D, 550D, 5D2, 5D3, 600D, 60D, 650D, 6D, 700D, 7D
[ GCC      ]   raw2dng
../../src/chdk-dng.c: In function 'save_dng':
../../src/chdk-dng.c:763:9: warning: implicit declaration of function 'FIO_RemoveFile' [-Wimplicit-function-declaration]
         FIO_RemoveFile(filename);
         ^
[ GCC      ]   raw2dng
[ GCC      ]   raw2dng
chdk-dng.o: In function `save_dng':
chdk-dng.c:(.text+0x17f8): undefined reference to `FIO_RemoveFile'
collect2: error: ld returned 1 exit status
Makefile:13: recipe for target 'raw2dng' failed
make[4]: *** [raw2dng] Error 1
and

Code Select Expand

Building module dual_iso...
Updated HGVERSION
[ README   ]   module_strings.h
[ CC       ]   dual_iso.o
[ MODULE   ]   dual_iso.mo
[ STRIP    ]   dual_iso.mo
[ EXPORTS  ]   dual_iso.sym
0000136c dual_iso_calc_dr_improvement
000013c4 dual_iso_set_enabled
000013e4 dual_iso_is_enabled
000013f4 dual_iso_is_active
00001414 dual_iso_get_dr_improvement
00001594 dual_iso_get_recovery_iso
000015b4 dual_iso_set_recovery_iso
[ DEPENDS  ]   dual_iso.dep
Will load on:
    EOSM
Not checked (compile ML for these cameras first):
    1100D, 500D, 50D, 550D, 5D2, 5D3, 600D, 60D, 650D, 6D, 700D, 7D
[ gcc      ]   cr2hdr
../../src/chdk-dng.c: In function 'save_dng':
../../src/chdk-dng.c:763:9: warning: implicit declaration of function 'FIO_RemoveFile' [-Wimplicit-function-declaration]
         FIO_RemoveFile(filename);
         ^
/tmp/ccAsd4aT.o: In function `save_dng':
chdk-dng.c:(.text+0x17f8): undefined reference to `FIO_RemoveFile'
collect2: error: ld returned 1 exit status
Makefile.cr2hdr:16: recipe for target 'cr2hdr' failed
make[4]: *** [cr2hdr] Error 1
i guess you need to add some defines in chdk-dng.c to the save_dng function to separate in camera and desktop modes since this commit https://bitbucket.org/hudson/magic-lantern/commits/9e99764f432025872286f87d5b7e10014061277f?at=fullres-silent-pics ?
Now, I believe raw_rec can be ignored as is superseeded by mlv_rec anyway, right?

/LE:
Got to build it with multiple values:
To work C.FnIV must be set as 1 or 3.
"Hold on..." has lv_focus_status=1
"Half-shutter pressed..." has lv_focus_status=1
"Focusing..." has lv_focus_status=3 when the lens is focusing and lv_focus_status=1 when idle, it jumps between these values as you change focus point and hold * again.
wait_lv_frames = 4 or 6 never gets to "Focusing..."
wait_lv_frames = 8 gets "Focusing..." sometimes
wait_lv_frames > 10 gets "Focusing..." every timeYou need to select a focus point or else it does not work, it took me a while to get this, being used with the Canon software since it has some sort of default point anyway.

[silent.c]

Boo. Can you print the values of lv_focus_status when focusing and when idle?

How do I do that?

In the mean time, I messed around silent.c, in line 1343 I got wait_lv_frames(4); bumped to 20, which gives me:
1. on a * single press -> "Hold on..." -> snaps pic (unfocused!)
2. on a * hold -> "Hold on..." flashes quickly-> "Focusing..." and it just sits here forever with LV on BUT it does AF as it should -> a half-shutter press or a single * press snaps a pic (FOCUSED!)

compare that with your code now at 4:
1. on a * single press -> "Hold on..." -> snaps pic (unfocused!)
2. on a * hold -> "Hold on..." flashes quickly-> "Half-shutter pressed..." is written on a black screen and it just sits here forever WITH the AF light on, and rising my finger off the * will snap a pic (unfocused!)

Works pretty good, but AF is triggered a few ms later than the half-shutter press event. So, I had to wait 4 LiveView frames, that is, about 0.13 seconds of extra shutter lag if you use autofocus.

Not working on my M1, I get a "Hold on..." and a unfocus silent picture is taken, that is using the * and any C.FnIV option.

I saw that the last build has a shutter issue, is it still the case?

Apparently it is: https://bitbucket.org/hudson/magic-lantern/issue/1893/eos-m-shutter-bug
I don't have it myself but I might be a lone case.

Is there any kind of stable version?

Not really, always get the latest build: http://builds.magiclantern.fm/#/ -> EOSM.202 as it's better to report issues having the latest version anyway.

Did you activate DualISO?

[a1ex]

Its possible on my 60D

And it's not interpreted as halfshutter so it's usable for AF even for silentpics?
Then this is a M1 only issue? 4 posts above @a1ex said otherwise.

you start to run into camera specific problems, on my camera the rec button is also the LV button, so if you pressed it, you would exit LV, you could probably use SET though

Since there is a per platform modularisation in ML anyway, it's a given, I guess a selector would be nicer so that a user can choose the button of choice.


And another thing, the Wiki states, that for silent pictures: "from the LiveView image buffer when you press the shutter halfway. Make sure you don't have autofocus assigned to half-shutter press (put it on * or turn it off)" which a guess needs to be edited out as is not possible to use * for AF?

Possible, but requires some reverse engineering. Currently, all cameras interpret the * button as a half-shutter press.

Umm, ok, any reason it needs to be halfshutter? Say, since you are bypassing normal shooting anyway, can't it be made to take a picture when pressing other button that is not used like BGMT_REC 0x1E button (presuming that is the movie REC button and that it's accessible in non-movie mode that is). And this should apply to intervalometer too.

I was under the impression that if was merged in the main branch from which the nightlies are compiled?

I compiled it  ( this VM updated: http://www.magiclantern.fm/forum/index.php?topic=7579.0 w/ updated gcc-arm to 4.8.4 as the included one failed: https://launchpad.net/gcc-arm-embedded/4.8/4.8-2014-q3-update ) for myself yesterday ( commit 666c09b ): http://we.tl/p1e78AKUef

Do keep in mind there are some issues: http://www.magiclantern.fm/forum/index.php?topic=12523.msg142216#msg142216

Could anyone please tell me if the current fastest shutter speed for M1 w FRSP is still about 1/15th - correct?

On my M1 it doesn't record pictures faster than 239ms.

Regarding FRSP on the EOS M1, any chance to separate the * (STAR) button from half-shutter? As reported before ( http://www.magiclantern.fm/forum/index.php?topic=12523.msg137532;topicseen#msg137532 ) no matter what option I choose in the custom function IV menu, pressing * will take a picture and it will not AF.



Now, testing a bit, while using the intervalometer (w/ or w/o silent pics) the * button behaves the same, takes a picture, but if one sets a delay before starting the sequence you can see that the camera tries to autofocus in that time before it will start shooting.