Danne's crop_rec_4k experiments for EOS M

Started by Danne, December 03, 2018, 06:10:17 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

henricusmaria

Yes, will do. I have one more week of testing to go..

Danne

What I'm thinking is to reduce the 2.35:1 preset to reach 4k and that might be what it takes to create a more robust set up. I could create a version with both 2.35:1 presets available for tests. Let me know what you think.
There's already a 16:9 3.5k 1x3 binning in there. Not sure how that works...

masc

I am not sure if it is neccessairy to reduce the resolution. I tried recording clips with many different settings today. The most safe one was the 4.5K 2.35:1 1x3 10bit preset. Selecting 16:9 there (-> smaller resolution) brought more corrupted frames - no idea why. But when speeking of "more corrupted frames" - this were 2 corrupted frames in 20 seconds, where the 2.35:1 preset had one or none.
5D3.113 | EOSM.202

Danne

4.5k more robust. Good to know.
I am keeping the height since reducing it will kill real time preview. Keeping it is probably one reason for difficulties.
Other than timing registers I don't really know what registers to tweak. Maybe eosm also has some memory routines that works different from each recording so one could look into this as well.

Timer regs are in the sub menu so anyone can try and optimize.

henricusmaria

Quote from: masc on January 26, 2019, 02:23:29 PM
I am not sure if it is neccessairy to reduce the resolution. I tried recording clips with many different settings today. The most safe one was the 4.5K 2.35:1 1x3 10bit preset. Selecting 16:9 there (-> smaller resolution) brought more corrupted frames - no idea why. But when speeking of "more corrupted frames" - this were 2 corrupted frames in 20 seconds, where the 2.35:1 preset had one or none.

Thanks. Will try that present tomorrow. I also had more corrupted frames when choosing 16:9. Although I'd rather film in 16:9 since my other footage is in that aspect ratio.

Danne

What happens if you create a 16:9 preset from regular raw video sub menu instead of using my ratios preset?

bergamote

Quote from: Danne on January 26, 2019, 10:30:31 AM
If you or someone else could check all presets for bottom red lines it would be good. With and without ratios from crop rec sub menu set. Lack of time here. Open up the files in Mlv App and simply zoom into the file, scroll to bottom...

I just quickly went though the presets, without the crop rec ratio then with it at 2.35 then at 16:9
Only found a line of noise at the bottom of the 2.5k preset with ratio 2.35.
But then again, I think I fudged up something. The sizes selected don't match the clips I got. I only had crop_rec and mlv_lite loaded, do the presets rely on lua scripts or sd hack?

Also, there's always a black line at the bottom of the 1x3 preset but is that because of the resize in MLVApp?

henricusmaria

Quote from: Danne on January 26, 2019, 03:24:22 PM
What happens if you create a 16:9 preset from regular raw video sub menu instead of using my ratios preset?

I haven't tried it with the latest built but I got a lot of corrupted frames before. I will try again tomorrow and report back.

Danne

Pushed some fixes to 16:9 ratios setting when used with 1x3 binning. Couldn,t get any corruption but see if anyone else can:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

dfort

While checking log files for the EOSM2 and comparing them to the EOSM and 700D I found this should probably be changed:

platform/EOSM.203/consts.h
// http://magiclantern.wikia.com/wiki/ASM_Zedbra
-#define YUV422_HD_BUFFER_1 0x44000080
+#define YUV422_HD_BUFFER_1 0x463cc080
#define YUV422_HD_BUFFER_2 0x46000080


Where is this used? Found a feature called FEATURE_PLAY_EXPOSURE_FUSION that uses this. I'm unfamiliar with this feature but it apparently works on the 700D and with a few tweaks it can be activated on the EOSM.



It also turns on a load of other features. Hum--interesting.



Here's what I did to turn this on:

https://bitbucket.org/daniel_fort/magic-lantern/commits/79d180e53752ed4d9b54fc097ed949e7cac1721e

Walter Schulz

You will find a description in outdated
https://wiki.magiclantern.fm/userguide#image_review_settings
422 options are gone, though.

Have to link some example pics in camera_help, WIP.

dfort

Thanks Walter. There are so many features that I haven't even touched yet!

Walter Schulz

Quote from: dfort on January 26, 2019, 09:41:43 PM
Thanks Walter. There are so many features that I haven't even touched yet!

... there are spiderwebs and dust bunnies. Lots of.
Some options and features haven't been used for years. See bug reports 2920-2923.

henricusmaria

Quote from: Danne on January 26, 2019, 05:11:42 PM
Pushed some fixes to 16:9 ratios setting when used with 1x3 binning. Couldn,t get any corruption but see if anyone else can:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

Thanks Danne! Will do some tests today. Do you think changing the bit depth to 12 or 14 bit lossless and lowering the resolution will improve the image quality? Or is it better to film in 10 bit lossless with the highest resolution?

Hmm

Hi everyone! I've encountered an interesting issue. My Samsung EVO 128gb microSD ocassionally starts to work at very low speeds (about 21 MB/s) and keep working like that until I format it. I have sd_uhs hack loading at startup. Things I tried: removing battery, different croprec modes, older ML builds, recording RAW video without croprec, loading sd_uhs manually, loading sd_uhs in photo mode and etc.
And the most interesting thing is, after I formated the card on my PC write speeds returned to normal. BUT, after some tests with ML (I tried using silentpic.mo with 4k croprec preset on 1/4000 shutter speed) my camera froze (so I had to remove the battery), and after 3-4 more crashes like that I decided to check if I am still getting nice write speeds. And guess what, my microSD card starts to underperform once again. This time I decided to format it in camera and it helped.

Any thoughts about what exactly casing it? Is there any way I can fix it without formating my card?

And, I would be very grateful if somebody makes a working silentpic.mo as 4fps burst speed is too low for my needs.

Danne

New build:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

Renamed 1x3 binning to simply 5K anamorphic.
Faster routine for sd_uhs module(experimental, use at own risk)
Better centering for the 5K anamorphic presets(2.35:1, 16:9)

ctfire




Just tested the latest build (_2019Jan27) there is a lot of corrupted frames at start of the footage , in crop rec mv1080p 45 fps preset (2.35:1 10bit)

ctfire

Quote from: Danne on January 28, 2019, 12:28:26 PM
New build:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

Renamed 1x3 binning to simply 5K anamorphic.
Faster routine for sd_uhs module(experimental, use at own risk)
Better centering for the 5K anamorphic presets(2.35:1, 16:9)

Just downloaded this new build, and also get corrupted frames in  in crop rec mv1080p 45 fps preset (2.35:1 10bit) (at start of the footage)   and in crop rec mv1080p 50 fps preset (2.35:1 10bit)  somewhere afrer the 300-400 frames get 1 or 2 corrupted frames

Danne

Yes, 45fps and 50fps modes are corrupted.

ctfire

Quote from: Danne on January 28, 2019, 01:05:25 PM
Yes, 45fps and 50fps modes are corrupted.

Maybe its possible to make a little lower resolution but make them without corrupted frames ?

Danne

You can reduce fps by pushing reg_6014 forward in the sub menu. Also works with reg_6008. Modifying reg_713c and reg_7150 also affects output.
Even reducing fps straight in FPS override should do.
If you get solid results please share your settings.

ctfire

Quote from: Danne on January 28, 2019, 01:12:00 PM
You can reduce fps by pushing reg_6014 forward in the sub menu. Also works with reg_6008. Modifying reg_713c and reg_7150 also affects output.
Even reducing fps straight in FPS override should do.
If you get solid results please share your settings.

In crop mode mv 1080p  1736x738 50fps (2.35:1 10 bit) changed reg_6014 to +20 and reg_6008 also +20 . And get more than a minute footage without corrupted frame. FPS override shows that the framerate with this settings is 47.3fps and on 24fps timeline you can do 2x slowmo. Danne if you can make a presset with this values, i will be very thankful.
In mv1080p 1736х976 tryed different values but in all efforts get corrupted frames (

Danne

Thanks for testing. For 1736x738 50fps I´d prefer if we can have it working with 50fps. When I test it over here it works uncorrupted when global draw is set to off. If you set fps override to 48fps it should run ok?
If nothing works we should really try to find sweet spot for a 48fps preset.

What needs more digging is the 45 fps setting. Seems harder to nail.

EDIT:
By the way. Could you test the 45 fps with following  starting point:
Global draw off
10bit
full 1736x976 ratio
reg_713c -8
reg_7150 -8
reg_6014 +2

ctfire

Quote from: Danne on January 28, 2019, 02:32:50 PM
Thanks for testing. For 1736x738 50fps I´d prefer if we can have it working with 50fps. When I test it over here it works uncorrupted when global draw is set to off. If you set fps override to 48fps it should run ok?
If nothing works we should really try to find sweet spot for a 48fps preset.

What needs more digging is the 45 fps setting. Seems harder to nail.

EDIT:
By the way. Could you test the 45 fps with following  starting point:
Global draw off
10bit
full 1736x976 ratio
reg_713c -8
reg_7150 -8
reg_6014 +2


Try your settings and still get video with corrupted frames, and get this on screen


Danne

Yeah, thanks, so needs more tweaking and maybe it should be run in 44fps in the end.