12 to 24 fps (FPS override Problem)

[dpjpandone]

Yes. Since we are happy with the timer_a_min values, leave them the way they are, but set timer_b_min back to:

 #define FPS_TIMER_B_MIN MIN(fps_timer_b_orig, 500)

and see how low you can push timer b before you have problems (remember to keep your shutter speed at 180 degrees, as this is how you would use the feature when shooting videos.  so if you are starting at 24fps, shutter at 1/50)

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)

here are the values from my own testing:

FULL FRAME: (we agree on this)

1080p30: 1965
1080p24: 1965
720p   : 1965
480p   : 1965

5X:
1080p30: 1195
1080p24: 1195
720p60 : 1195
480p   : 1195

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

BTW, you don't need to check recording vs. not recording because there is nothing in current fps implementation to support that, besides if timer B can go lower when recording vs. standby it's not going to do you any good because you would normally set it in standby, and if it goes lower in standby vs. recording the worst thing that happens is your recording stops.

so to sum things up, the goal is to choose values that give the maximum range of FPS, then pull them back a bit to some meaningful value on the safe side. i chose 650 since that allows me to overcrank up to 45fps (in my testing I can record 44fps reliably)

So I have mine set like:

Code: [Select]

#define FPS_TIMER_B_MIN (fps_timer_b_orig - (ZOOM ? 290 : MV720 ? 57 : MV1080CROP ? 650 : 57))
If we can agree that these values are safe, I will modify the pull request, if not, then I guess we'll have to go with the ones you reported initially.

[DeafEyeJedi]

We should be able to agree on this and the fact that it is safe to record up to 45fps in crop mode on the M according to my previous test results.

[Licaon_Kter]

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.

[dpjpandone]

3x crop mode is "Movie crop mode" in the ML menu?
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?
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.

Movie crop mode is limited to 1792 pixels wide, and works with raw or h.264. 5X allows higher resolutions, but the preview is not framed accurately. It can oly be used with raw. So that is why we want a timer_b_min value for 5x, in case someone wants to use fps override with 5x raw video.

So we agree on the values I posted? I will update the pull request and add you and deafeyejedi as reviewers. If you can look at the pull request and click "approve" that would be helpful

https://bitbucket.org/hudson/magic-lantern/pull-requests/649/fps_timer_a_min-and-fps_timer_b_min-fixed/diff

[DeafEyeJedi]

Approved via Bitbucket!

[Frank7D]

Movie crop mode is limited to 1792 pixels wide, and works with raw or h.264. 5X allows higher resolutions, but the preview is not framed accurately. It can oly be used with raw. So that is why we want a timer_b_min value for 5x, in case someone wants to use fps override with 5x raw video.

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.

[Licaon_Kter]

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.

[DeafEyeJedi]

Perhaps it works for both h264 & MLV/RAW? [emoji6]

[dpjpandone]

"movie crop mode" is a feature aavailable only on t3i and eosm. It works for both raw and h.264, the great thing about eosm is that movie crop mode is 1:1 pixels (no line skipping) just like other cams, but the preview is full color and framed correctly (unlike other cams that either frame in 5x, or greyscale)

[DeafEyeJedi]

[Licaon_Kter]

@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... ;(

[Licaon_Kter]

@dpjpandone: Using your build: https://bitbucket.org/hudson/magic-lantern/issues/2360/15-360-extra-pixels-of-noise-added-in-crop

[dfort]

So what are the steps to get 45fps crop mode video working? Both 1920x1080 H.264 and 960x480 raw?

Every time I go that high the screen flickers and so does the mov file. This is the first time I tried dpjpandone's build. Up until now I was just testing what was in the pull request. That one works fine but it will only get to about 31fps max.

I take it that "Video Hacks" (soon to be called "Compression Method"?) is not ready for a pull request yet?

[Licaon_Kter]

Well it's not perfect.


1080@30
fps override 45
low jello 180
crop on
raw 960x540
globaldraw off
info debug

also got the shutter to 180degrees

it yields >1000 frames since the card can't keep up
lowering the res a bit you can get it to work forever

[dfort]

Got it -- mlv or old school raw video?

I'm on location for a few days so I'll try it when I get home.

[Licaon_Kter]

MLV_REC


I for one did not bother with the old format, was there any imediate thing that old format did better though?

[dfort]

was there any imediate thing that old format did better though?

I think it used to be that raw_rec was more stable but MLV version 2.0 is definitely better.