Messages

When I press the trash button to use the menu of the ML it just stays in the menu only 5-7 secs and then it returns to the standby

That's a known bug... keep pressing buttons.

@dpjpandone: i know what crop mode is, but you speak of 3x and 5x and I did not understand what mode is that, where 3x/5x CANON ZOOM PHOTO MODE STANDBY (as in my table) is one thing and 3X/5X MAGICLANTERN RAW VIDEO RECORDING is a whole different thing.

Yes I will mixed them up if you don't specify what you mean... BTW should I wonder what you think the values in my table above mean? Here's a hint: it's never RAW

Also, the table above needed 2 full battery charges, a lot of time, a way to note results, and a whole lot of will, and now you're telling me that The Method was kinda faulty... ;(

Still using 1.3.3? What about 1.4.3? See bitbucket site -> Downloads

You're using this term "movie crop mode" to refer to regular video mode, but most people use "crop mode" to mean video shot with the 3x/5x zoom. This could be confusing.

exactly

After you mentioned RAW it clicked for me, THERE the crop(?)/zoom(?) factor 3x/5x etc is mentioned. I can use "Movie crop" and set a lower resolution in RAW, and that yields 3x/5x/7x and I can go to 45 fps ( only at 960x480 or so on my M, given the card speed, but hey it's freaking RAW )

So maybe rephrase the whole idea again maintioning RAW or H.264 please? Because I'm rather lost here.

[crop mode]

When you are testing the 3x crop mode, start with desired fps set to 45, and then start lowering timer b from there (it will save you lots of time and put timer a at a realistic value)

3x crop mode is "Movie crop mode" in the ML menu?

5X:
1080p30: 1195
....

3x:      (here's where our results are drastically different)
1080p30: 1195
...

You keep talking about this, is this "Zoom mode 3x/5x" for photos in standby? Why bother with it since I can't use it when switching to video anyway?

If you want to try to record 44fps in 1080p crop mode, you have to set the compression method to ALL-I under "video hacks", just don't forget to set it back to IPP before you turn video hacks back off

This is the first time that I see this advice, Why wasn't this specified before daammit!!?!?
Yes it works, 1080@30 can be pushed up to 46.056fps so yeah limiting it at 45fps is nice.

/LE:
Using your build ( I presume you set  #define FPS_TIMER_B_MIN MIN(fps_timer_b_orig, 500) in it, right? ), you say "see how low you can push timer b before you have problems", so I set 1080@24 in Canon menu, crop mode ON, video hacks ALL-I, turn fps override on, push it to 34, "low jello 180d", actual fps 33.528 and this yields timer A at 532 and timer B at 1794.

But, I can't lower them, they're stuck at 532/1794 and in goes to 1794 (FT-X) where X is a growing value, I can go to FT-400 but I'm not sure that is what it should do.

Would you be willing to do some more testing to see if any of the values in your table can go a little higher? I would recommend keeping your shutter angle as close to 180 degrees (or fps*2) when testing for timer B

Which values exactly do you mean to "go higher"? The difference?

1.raise "desired framerate" as high as it will go, (until "actual fps" stops changing) and check for artifacts

1080@30 max is 31.317fps
1080@24 max is 24.904fp

Kinda underwhelming...

2.lower "desired framerate" as low as it will go, (until "actual fps" stops changing) and check for artifacts

At least 1080@24/30 goes as low as 0.616fps.

Is this correct?

[readme2modulestrings.py]

Better comment out the mercurial check in readme2modulestrings.py maybe.

[zsh]

I was using the Windows Command Prompt. Which is your preferred bash shell for Windows? I didn't know the Cygwin shell was an option, it works in a jail/sandbox/chroot/whatever in the Cygwin environment.

It works meaning it finds apps, but it does not handle unix tricks, like the LC error, since you use Cygwin it's better to use bash/zsh/whatever unix shell.

As far as Cygwin goes I recommend https://babun.github.io ( zsh shell, pact install <cygwin package> and so on )

[Bash]

What shell do you use? Bash or something from Cygwin, right? Hope you're not using Windows provided cmd.

You've also installed mingw64-x86_64-headers right?

Stuck on Windows?
Yes, see this too: http://www.magiclantern.fm/forum/index.php?topic=15271.0
No, see this http://www.magiclantern.fm/forum/index.php?topic=13152.0

@toze3:
Latest cr2hdr from here: https://builds.magiclantern.fm/jenkins/view/Other%20tasks/job/cr2hdr-20bit/ right?



Do upload: Sample CR2 and Ouputed DNG.

I left it at 10 because I know it's a safe value, and your table did not have a value posted for zoom during recording, (which is probably lower than 50)

How do I zoom while recording?

test procedure is try a bunch of different fps settings in the various modes and tell me if you experience artifacts with any of those settings. Our goal is to have the widest range of fps without artifacts.

Yes but what exactly? Detail how you test: what Canon mode/fps? What ML fps override value? What fps mode ( jello, fix, other)? the whole procedure. I'm not that of a video shooter hence my lack of direction.

Actually I just tried to submit the pull request, but bitbucket keeps getting hung up on "creating pull request" - i'll try to do it through atlassian

Link of your repo? So I'll clone it and test directly ( since you have the early stuff with shutter fine tuning and the rest there too, right? )

[ZOOM ? 10]

Where did you got the value for ZOOM ? 10 ? Why not 50 ?

Yes, this needs an Euro check ( aka 25p, 50p ) too.

Can you paste a real diff or point us to your bitbucket repo so I can build it right? You will need one for the pull request maybe anyway?!

Also, do detail how the test procedure goes on, as I did not fully grasp what the problem was in the first place.


10x

Reformatted the table with the differences: https://mega.co.nz/#!9BBkEZZa!oqhQsDTgx4tK4eJ2vToYAvIU_wvafmFDoPKPJOKtPAY

You can't directly compare there.
Use a local diff:


1: https://i.imgur.com/Q9WAh3z.png


2: https://i.imgur.com/0AcMhrF.png

Oh, right, then I'm glad somebody is able and willing to advance EOS M development.
I'll gladly test.

Heh, my modes fix is also there

@Levton: copy CR2 in that folder, shift-right click on that folder -> Open Command Line here -> cr2hdr <yourfile>.CR2 and make a screenshot wih Snippingtool, post it here.

What camera/firmware? What ML build date?

Now "1 finger touch" is used in place of Q in the ML menus or you mean something else?

Regarding buttons, there is one exception where M feels cramped, the Autoexpo module: http://www.magiclantern.fm/forum/index.php?topic=7208.msg136296#msg136296 you can't change some values since we don't have that extra wheel.

Oh, cross-compile on Windows, you're brave, I'm doing it on real Linux and on Virtualbox with Linux.
Looks like a harmless thing regarding mercurial indexes.

I usually do a:

Code Select Expand


make clean -j4 && make -j4 && make all_modules -j4 && cd platform/EOSM.202 && make -j4 zip

Removing line fps-engio.c:237 makes the build go on I guess anyway?

The unified build supports EOS M as a main platform.

April brake is intentional, it can be fixed by hand ( edit fps-engio.c ) or by @a1ex once he gets a chance to tune the timers, see my values report in this thread: http://www.magiclantern.fm/forum/index.php?topic=14959.msg149308#msg149308

MLV Audio works fine, did you mean this bug: https://bitbucket.org/hudson/magic-lantern/issues/2255/mlv_sound-working-only-on-the-first-video ? Was fixed already: https://bitbucket.org/hudson/magic-lantern/pull-requests/646/added-sounddevshutdownin/diff

Want the latest unified build for EOS M to test? It's here: https://bitbucket.org/hudson/magic-lantern/issues/2255/mlv_sound-working-only-on-the-first-video#comment-19410615

I'm not sure what current means for you, current like the other unified cameras ( where there already afaik ) or current compared to what 1% was working on ?

Long standing issues for M now are the main shutter bug: https://bitbucket.org/hudson/magic-lantern/issues/1893/eos-m-shutter-bug and I guess those reported by me ( more or less): https://bitbucket.org/hudson/magic-lantern/issues?reported_by=~licaon_kter&status=open&status=new
Also this one is nasty too: https://bitbucket.org/hudson/magic-lantern/issues/1974/6d-m-700d-70d-in-live-view-mode-ml-menu

Crop mode is not line-skipped.
IIRC, it does not output clean HDMI, not even EOS M3 does.

@Tullen: Try the unified VC+ installer here: http://forums.guru3d.com/showthread.php?t=393405 ( remember to Run as Admin )