mv1080 on EOSM

Started by dfort, February 06, 2016, 04:56:46 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

nlantz

Quotecrop_rec, Movie crop mode, zoom mode, 3x3, 3x1.6, yeah this is confusing. What's worse is that this discussion is about getting mv1080 working on the EOSM so pretty much nothing in your post is on topic.

Hey all, You nailed it on confusing! Im trying to figure out Movie Crop Mode on my EOSM. tried this, tried that but all leads me to 3x3. Couldnt find anything on 2.0.2 so upgraded to 2.0.3, put on the experimental from your repo DFort! and got Crop_Rec.mo

How and where do I find
QuoteMovie crop mode which is the only video mode that is actually working the way it is intended to work on the EOSM

I give up!, Also this mode still gives you 3x zoom ? that is my whole point in wanting it.

Danne

Movie crop mode is the only mode giving 3x zoom.
crop_rec is a smart way of binning mv720p footage so it gives same quality as mv1080p. Caveat. You get lesser height.

dfort

The confusion seems to be between 3x3 and 3x.

3x3 can mean that the sensor is combining 3 pixels in the horizontal and vertical axis. This is know as binning. Only the 5D mark III does this. All the other cameras, including the EOSM does what is called line skipping.

It is a little more complicated because of the bayer pattern on the sensor this but let's simplify it to illustrate what is going on.



Binning is making these nine pixels behave like one giant pixel while line skipping only uses the one pixel in the middle. Line skipping is much simpler but it does have aliasing issues. The net result from both of these methods is the same. Start with a sensor that has an active horizontal resolution of 5,760 pixels and a vertical resolution of 3,240 and you end up with a 1920x1080 image after doing 3x3 pixel binning or line skipping. Now the EOSM and most of the other Magic Lantern enabled cameras don't have that high of a resolution. The EOSM has a 5184 x 3456 (18 megapixels) sensor so the maximum resolution, assuming you want to keep the HD aspect ratio of 16:9 is 1728x972. How does it do 1920x1080 H.264 video? We're pretty sure it scales the image. How about 1280x720? It does a 3x5 pattern which means it skips (or in the 5D3 bins) 5 pixels vertically and again resizes in camera for H.264 but in raw you need to adjust the aspect ratio to un-squish it.

3x crop on the other hand uses all of the pixels, a.k.a. a 1x1 pattern. Since the pixels are closer together and there is no line skipping there is also less aliasing but a 1920x1080 image would use just a small area of the total sensor thus the "crop" in this video mode. You don't need a module to do this, it is either the "Movie crop mode" option or the digital zoom option. One thing I personally like about Movie crop mode when shooting H.264 is that it extends the effective focal length of your lens so that a 16mm prime lens can become a 48mm lens or adjusted to full frame if your brain thinks that way it would be like having about a 26mm and a 77mm lens in one. Sort of, not really, but good enough to make a point.

Uh oh, I mentioned zoom mode. This isn't as well known but if you tap the magnifying glass icon on the screen while in 1920x1080 mode in the Canon menu you can also get into a crop mode, confusing because it says 5x or 10x on the screen and you will get the same image no matter which setting you use. The big secret is that you can get an image up to 2496x1072 but it isn't all that practical to use.

The crop_rec module on the EOSM doesn't actually "crop" and it uses the 3x3 pattern. Thing is, it uses the raw buffer that is supposed to be used for mv720 mode which is normally a 3x5 pattern so as Danne pointed out it quickly runs out of vertical resolution, thus most shots you'll see from the crop_rec module on the EOSM are very wide screen aspect ratios.

Finally, to get back on topic, the EOSM can't use the full sensor in 3x3 mode which is known as mv1080 in the ML source code. We're trying but so far the only hack seems to be to record H.264 and raw simultaneously. You'll get lots of corrupt frames and a few beautiful ones that inspires us to keep trying to get this mode working on the EOSM.

So does this make everything about as clear as mud?

yskunto

Thanks for replays from you all. I understand now. The crop factor compared to full frame in crop mode is 3x1.6. Thanks

Teamsleepkid

these new builds have h.264 proxy so any developments on mv1080 with that? we need h.264 running to kick the eos m into mv1080 as i understand it..
EOS M

Danne

Yes, it goes into mv1080p mode while proxy is on. The proxy files are choppy and the mlv files are partly corrupted and a few ones looking good. Works better with 10bit.

Teamsleepkid

cool i tried it. looks good in between those pink frames. but you already knew that.. #catpic
EOS M

Danne

While filming proxy and raw and lowering fps to something around 10fps it actually records mostly corruptfree files and in correct order.

Danne

There is a way to film corrupt free mv1080p footage. It ain,t beautiful but it works.

For continouos do this:
1 - Bit Rate (CBR) 0.1x(H.264 files won,t be used anyway, maybe audio)
2 - FPS override 24
3 - Set proxy on and select 10-bit(mlv-lite.mo) Resolution 1488x692
4 - Set Preview  in RAW video menu to Hacked(will freeze liveview or make it choppy but images will be corruption free)

Hit record.

DeafEyeJedi

Finally managed to downgrade back to 202 from 203 with ease (not quite actually hadn't realized I was in CA mode and not in M mode until just recently and only god knows how long I was in that mode for ha!) as usually with the EOSM I can easily forget that the Modes are only accessible through the 'Q' menu as oppose to most DSLR's would have access to these outside within the body.

Anyway was this done with the latest experimental (ml-raw_video_10bit_12bit.2017Feb11.EOSM202) or the one before that @Danne? <--  Oops looks below!

Only asking because I notice this build was missing the option that enables H264 Proxy (as it did in previous build afaik) so could this have anything to do with commit #88b2139 (Merged raw-h264-proxy into raw_video_10bit_12bit)?

My wrong ... I realized that the H264 Proxy is only available under 'Advanced...' within the RAW module menu (mlv-lite.mo) and not MLV module. D'oh! After all I will get my hands dirty with this momentarily and report my findings asap.
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

DeafEyeJedi

Shot in 24p 1792x1008p in 10-bit RAW (build used: ml-raw_video_10bit_12bit.2017Feb11 from experimental page) w an Opekta 6.5mm @ ISO 800 while in 'Movie crop mode' during early afternoon from indoors.

https://vimeo.com/204071325

Card used: 32GB Sandisk Extreme Pro 95MB/s SDHC I Class 10 (old as hell and still running strong!)  8)

Post workflow: MLV > cr2hdr.app (spat out ProRes 422 Proxy files w Rec709 applied) while I got 4 seconds in each take and it's 99% close to perfection. Seriously no joke in here!
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

Teamsleepkid

so were getting there. i'm seeing a pink cast on my footage at lower resolutions(black level?). strange thing is it seems to work at higher resolutions. but i have c mounts so i can't film at higher resolutions without vignetting. also noticed just like when rbrun got 3x3 720 working the recording area isn't centered. still cool loving the progress:)
EOS M

DeafEyeJedi

Here's another shot in 24p 1792x1008p in 10-bit RAW w a 50L @ ISO 200 while in 'Movie Crop Mode' of Willoughby:

FYI the first clip is graded with Cinelog DCP 2017 (after applying Cinelog-C in ACR, in OCIO select Alexa Wide Gamut V3 Log-C EI800 as input with Cinelog Rec709 FM as output) + FilmConvert (FJ 8543 VD) applied and then the second clip is without FilmConvert...

https://vimeo.com/204135855

For those that are curious how I did this in post? Here's the screenflow:

https://vimeo.com/204218877

Finally some original 10-bit mlv-lite samples in 24p 1792x1008p for those that don't own an EOSM but want to play:

Few DNG's zipped (4.3 MB) -- https://bitbucket.org/DeafEyeJedi/magic-lantern/downloads/ml-experimental.2017Feb14EOSM 10-bit 1792 × 1008 DNG's.zip
Converted MLV zipped (171.7 MB) -- https://bitbucket.org/DeafEyeJedi/magic-lantern/downloads/M14-1405_1_2017-02-14_0001_C0000.zip
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

Danne

Are you getting 1792x1008? What build are you using?

DeafEyeJedi

ml-raw_video_10bit_12bit.2017Feb11 from experimental page
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

Danne

OKi you,re in movie crop mode, didn,t realize.

dmilligan

mv1080 ≠ "movie crop mode"

Teamsleepkid

https://youtu.be/vjUARErSL-w

mv1080 on eos m filmed with dannes settings with c mount 12.5mm lens. shows that the framing is not centered. also getting purple footage on some clips like the first then regular footage like the second clip. does work though.
EOS M

Teamsleepkid

Actually maybe it is centered..I'm probably wrong
EOS M

uncontrollable_CBR

Hi everyone

I was reading through the MV1080 on EOS-M forum and I was very interested by what Danne said here - https://www.magiclantern.fm/forum/index.php?topic=16608.150

I haven't yet tried his suggested settings, but what I don't understand is that you have said to use the 1488x692 resolution, but how could that be MV1080? Wouldn't MV1080 be 1792x1008?

Please let me know

I love all the work that's going into RAW, it's really amazing!

- Nathan

dfort

Breakthrough on this topic--1st sample of mv1080 on the EOSM without having to simultaneously record H.264:

https://www.magiclantern.fm/forum/index.php?topic=9741.msg203530#msg203530