Author Topic: Canon EOS M  (Read 864732 times)

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3739
Re: Canon EOS M
« Reply #1750 on: November 28, 2018, 04:23:48 PM »
Does this build break any of the other platforms?

It would be great if we can get all the great work being done being done recently on the EOSM, 100D and 700D into merged into the experimental branches of the main repository. Then maybe see if some new resolutions can be found for the 6D and 650D as well.
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

optical-work

  • New to the forum
  • *
  • Posts: 17
Re: Canon EOS M
« Reply #1751 on: November 29, 2018, 07:33:57 PM »
is there any way to get the "framing" liveview work on an external display? whatever i choose for preview, it's showing "realtime" for hdmi external. by the way, i searched but i couldn't really get 1x3 crop mode, it shows at liveview and records very wide. i can provide footage does it need to be dng or are compressed formats okay? (i'm using mlv app on windows and i'm really grateful to both firmware and software developers.)

norek

  • New to the forum
  • *
  • Posts: 8
Re: Canon EOS M
« Reply #1752 on: November 30, 2018, 08:02:12 AM »
Hell yeah @dfort.
No footage yet but hopefully some of the downloaders could provide. There's a focus pixel map for the mv1080p setting already? Only one needed for 1x3 right?

Danne,

First, thank you again your hard work!!!

And can you explain what you need to the focus pixel map for new fw?


Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6010
Re: Canon EOS M
« Reply #1753 on: November 30, 2018, 08:29:43 AM »
One file recorded with 1x3 setting showing focus  pixels. Might be hard to find them. You can load the file in Mlv App and uncheck all focus pixel fixing function and look.

norek

  • New to the forum
  • *
  • Posts: 8
Re: Canon EOS M
« Reply #1754 on: November 30, 2018, 10:23:17 AM »
One file recorded with 1x3 setting showing focus  pixels. Might be hard to find them. You can load the file in Mlv App and uncheck all focus pixel fixing function and look.

Danne,

here is the file:
https://we.tl/t-t1OpChmFaN

norek

  • New to the forum
  • *
  • Posts: 8
Re: Canon EOS M
« Reply #1755 on: November 30, 2018, 10:42:01 AM »
something I do not understand, the file is what i upload is 696px height and the focus pixels showing. on/off the eos m changed the height to 1120px and the focus pixels not showing... hmmm which setting is wrong?

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3739
Re: Canon EOS M
« Reply #1756 on: November 30, 2018, 07:48:52 PM »
Interesting, MLV App is changing the height with the focus pixel fixing on/off?

I tried it with the current version of MLV App and didn't experience that. Here is your file with the focus pixels removed:



And without fixing the focus pixels:



I obviously stretched the colors to make the focus pixels more obvious.

I've seen height changes because of the "Default Scale" tag in the exported DNG file. The Default Scale tag is useful when shooting mv720 (5x3 sampling) though not all graphics applications honor that tag. Your sample file exported as DNG in MLV App and mlv_dump show different Default Scale values:

Code: [Select]
Software                        : MLV_DUMP CDNG
Default Scale                   : 1 1.666666667
Reel Name                       : M30-0960_.MLV
Image Size                      : 1736x696

Code: [Select]
Software                        : MLV App
Default Scale                   : 1 1
Reel Name                       : M30-0960_
Image Size                      : 1736x696

This means that the DNG files with the 1 1.666666667 Default Scale tag will be stretched vertically, depending on the app used.

Interesting that mlv_dump keeps the filename extension in the "Reel Name" tag while MLV App drops it. (Used exiftool to look at the tags.)

Your file appears to be shot with the crop_rec module using 3x3 sampling so the correct Default Scale should be "1 1":

mlv_dump -v
Code: [Select]
    raw_capture_info:
      sensor res      5184x3456
      sensor crop     1.62 (APS-C)
      sampling        3x3 (read 1 line, skip 2, bin 3 columns)

I'm not sure if mlv_dump needs a "fix" for this or if the problem is in the MLV file because the crop_rec module is using the mv720 raw buffer but modifying it with 3x3 sampling in place of the default 5x3 sampling. It should probably be fixed though it is easy enough to rescale the height in post for now.

The the new crop_rec module resolutions are a relatively new development and mlv_dump (crop_rec_4k version, a.k.a. mlv_dump on steroids) doesn't handle these focus pixels yet:



Just for fun, here's the same frame using MLV App with the correct aspect ratio and focus pixel fix turned off:



In this case the DNG files were converted with Adobe Camera Raw and manipulated to get the focus pixels to show up clearly.
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

norek

  • New to the forum
  • *
  • Posts: 8
Re: Canon EOS M
« Reply #1757 on: December 01, 2018, 07:55:36 AM »
No, the MLV App is working ok, not change the height. I thing upload wrong file yesterday (non-crop).

https://we.tl/t-lzgOVocvSr crop mode is: 1x3_1736x1120, but I don't see the focus pixels...

Teamsleepkid

  • Member
  • ***
  • Posts: 229
Re: Canon EOS M
« Reply #1758 on: December 01, 2018, 09:12:39 AM »
my mlv app is showing the video correct and then outputting it squashed too tall not wide. i had to stretch it out in final cut. like it was anamorphic footage. looks great lots of detail. very good quality this 1x3 footage. I'm doing 1120x1120 which looks like 2:66:1 aspect ratio very nice. i use chroma smoothing 2x2 to get rid of focus pixels
EOS M

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6010
Re: Canon EOS M
« Reply #1759 on: December 01, 2018, 09:29:02 AM »
1x3 mode is supposed to be used in regular mv1080p mode, not in x3 zoom which already can do 1:1.

critix

  • Contributor
  • Member
  • *****
  • Posts: 113
Canon 1300D, 500D, EOS M, EOS M2

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3739
Re: Canon EOS M
« Reply #1761 on: December 01, 2018, 04:57:46 PM »
No focus pixels -- Yay! Got a similar sample from the 100D and it does show focus pixels so maybe you just got "lucky" and shot a lighting situation that doesn't show the focus pixels. This is actually happens quite a bit and makes hunting down all of the possible focus pixels a challenge.

Found some interesting stuff with these 1x3 sample. I'm a little lost as far as figuring out which app is doing the "correct" thing because there is nothing to guide us in this image. I guess you can say that there's no image in this image.

mlv_dump -v
Code: [Select]
    Res:  1736x1120
...
    raw_capture_info:
      sensor res      5184x3456
      sensor crop     1.62 (APS-C)
      sampling        1x3 (read every line, bin 3 columns)

Note that the sensor resolution is 5184 pixels wide but the sampling bins every 3 columns so the maximum width should logically be 5184/3 = 1728. Well, there's an area that normally gets cropped so the sensor resolution is actually a bit more -- 5208.

Another thing to watch out for is that while resolution is written as width by height, the sampling is written as height by width. We had a conversation about this on another topic:

I was used to Octave notation (line/column) when writing the binning notation (5x3 etc), but relating these to resolution seems more logical; too late to swap them?
Probably not necessary. Besides, it makes the "desqueezing factor" super easy to figure out -- 5/3 = 1.67x

So, for 1x3 sampling the "desqueezing factor" should be 1/3 = 0.3333...

Let's see what some of the MLV apps are doing with 1x3 footage when exporting to DNG.

mlv_dump

Code: [Select]
Software                        : MLV_DUMP CDNG
Default Scale                   : 1 1
Reel Name                       : M01-0745.MLV
Image Size                      : 1736x1120

dcraw -T (1736 × 1120)


Adobe Camera Raw (1736 × 1120)


Not that exciting yet. There's a difference between the way ACR and dcraw rendered the DNG file but that's expected.

MLVFS

I recently updated my Mac to Mojave and it wasn't working when I was checking out that previous file. After updating osxfuse to 3.8.2 it is working again.

Code: [Select]
Software                        : MLVFS
Default Scale                   : 1 1
Reel Name                       : /M01-0745.MLV
Image Size                      : 1736x1120

dcraw -T (1736 × 1120)


Adobe Camera Raw (1736 × 1120)


No surprises there.

MLV App

Code: [Select]
Software                        : MLV App
Default Scale                   : 1 0.3333333333
Reel Name                       : M01-0745
Image Size                      : 1736x1120

It makes sense that MLV App shows the correct Default Scale because some of the developers working on this app are also experimenting with the new crop_rec resolutions. This app also allows you to save to various types of image files so you don't have to create DNG files to work with. Let's export a tiff file from MLV App

MLV App (1736 × 373)


Let's take a DNG file exported from MLV App and run it through dcraw and ACR.

dcraw -T (5208 × 1120)


What's up with that file size? Instead of reducing the height dcraw increased the width to get the correct aspect ratio.

Adobe Camera Raw (1736 × 373)
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6010
Re: Canon EOS M
« Reply #1762 on: December 01, 2018, 05:55:07 PM »
Cool findings dfort

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3739
Re: Canon EOS M
« Reply #1763 on: December 02, 2018, 09:07:12 PM »
What are everyone's thoughts on updating the EOSM to 2.0.3? The original pull request has been up for nearly two years. Recently @critix and I have been running tests on it and it is as stable as 2.0.2. I can do it on some of the experimental builds to get started--provided @a1ex approves.
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

DeafEyeJedi

  • Hero Member
  • *****
  • Posts: 3348
  • 5D3 | M1 | 7D | 70D | SL1 | M2 | 50D
Re: Canon EOS M
« Reply #1764 on: December 02, 2018, 11:50:17 PM »
Cool findings dfort

Indeed cool findings! :)

What are everyone's thoughts on updating the EOSM to 2.0.3? The original pull request has been up for nearly two years. Recently @critix and I have been running tests on it and it is as stable as 2.0.2. I can do it on some of the experimental builds to get started--provided @a1ex approves.

Sounds good. I’m all for this plan. In fact, I’ve wanting to get my hands dirty again w you guys sooner rather than later.
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6010
Re: Canon EOS M
« Reply #1765 on: December 03, 2018, 06:10:17 PM »
New version:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec_4k_mlv_snd_raw_only_2019Dec08.EOSM202.zip

branch:
https://bitbucket.org/Dannephoto/magic-lantern_jip-hop/branch/crop_rec_4k_mlv_snd_raw_only

Been working hard with Jip-Hop to refine presets and all around movie handling approaching the eosm more like a movie cam. Some of the things done recently:

- reworked Movie tab menu(Jip-Hop)
- fast preset access by simply tapping display
- corruption free 4k anamorphic modes(slightly reduced height in raw.c)
- shutter coherency. Same shutter across all presets(fixed a bug introduced by myself)
- Movie Restart for raw recordings(Jip-Hop)
- autoenabling modules(refined by Jip-Hop)
- gain buttons up for higher iso. push down for lower iso, also working while recording
- aperture + ISO(up/down buttons will open or close aperture when max/min iso is reached)(Jip-Hop)
- h264 mov preset, working with x3 digital gain(SET button) and gain buttons(up/down)
- toggling between photo and movie mode working better

Upon install buttons will be reassigned as follows:
SET x3 crop and back to x1.6 mode
Up/Down gain increasing/decreasing(iso)
Tap display startoff preset list
Halfshutter press x10 zoom aid(release for normal view)

For newcomers and for people who just wants to get down to recording do following:
1 - Install above build onto your eosm and start film. Camera will be set to mv1080p 2.39:1 24 fps
Or...
2 - Set your camera into manual focus mode and tap your display to get into the fast access preset list:

Select a preset after tapping your display. Done!:


Reworked Movie tab menu(thanks Jip-Hop):


Movie Restart feature(thanks Jip-Hop)


customize buttons:


h264 mov. Select it from tap display options:


Missing 3K, 4K? Still there. Reach them by tapping "presets" from Movie tab section:


cine 2.39:1 script still there(refined by Jip-Hop)
















OLDER STUFF BELOW. NOT SUPPORTED ANY LONGER


branch:
https://bitbucket.org/Dannephoto/magic-lantern/branch/crop_rec_4k_mlv_snd_isogain_1x3_presets

I focused on getting rid of corrupted images in 5K anamorphic mode. And also to complete a set up that will record all the presets continuously when a certain set up is performed. To enable continuous recordings do following:
sd_uhs hack on
bitrate to 10bit
ratios set to 2.35:1
(will scale down or reduce bitrate depending on preset chosen)

For instance. 5K anamorphic 1736x2150 will be set to 1504x1920 when ratios 2.35:1 is set. Still a stellar file since upsampled in Mlv App you will export a file that´s 4512x1920 in size.
3k will run with reduced fps and so will 5k setting. Most other presets will still keep original frame rate. All presets will record with 2.35:1.
If you want full manual control just skip the 2.35:1 ratios setting and do whatever tweaks in other menus instead.

Enjoy and don´t forget to post what´s working or not…










From here:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg211572#msg211572

- Cleaned out scripts, kept two. One is new. "eosm cinema 2:35.1". The script will through lua add all necessary parameters to get into anamorphic 4.5K preset. Once the script has finished you can use any of the crop rec presets and they will all run in 2:35.1 and continuous. A fast sd card will be needed. The script also enables the sd_uhs script "sd overclock engine" and sets it to auto. The script is good as starting point instead of fiddling around for 10 minutes before getting into filming.
Why 2:35.1? Easy. Eosm has it´s limitations and restriction and this ratio seems like sweet spot for most presets on this cam.



- The other feature(also added though "eosm cinema 2:35.1" script) is "Crop rec preview" in mlv_lite menu. Once this is set to auto mode The crop rec presets will work either with framing or real time preview depending on what works better. Reason for this is that it takes a little too long to switch both preset and preview mode for every preset changed. Watch out. This auto mode setting overrides any Preview mode setting aready set from before. Disable auto mode when not in use.
All modes and settings can of course be set manually without the scripts.



Additional stuff:
3xcrop toggle



All of this is of course experimental, bleeding edge and out here for tests and feedback. As always thanks to a1ex, g3gg0, dmilligan for code and lua api.

A lot of tutorials from this guy and eos m enthusiast:
https://www.youtube.com/channel/UCCn0RQHYheA41EudwmLnYKA

Also check this thread:
https://www.eoshd.com/comments/topic/28526-5k-raw-24p-video-for-150-magic-lantern-making-great-strides-on-canon-eos-m/#comments


Also check in my work on the 5DIII here:
https://www.magiclantern.fm/forum/index.php?topic=23041.msg216899#msg216899

alpicat

  • Freshman
  • **
  • Posts: 56
Re: Canon EOS M
« Reply #1766 on: December 06, 2018, 03:20:53 AM »
@Danne, this build works nicely shooting 2520x1308 in 9 or 10 bit lossless. I can't seem to get rid of the focus pixels using mlvapp, but other than that the image quality is perfect. Liveview looks a bit funny colourwise but it's not particularly distracting and still very usable.

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6010
Re: Canon EOS M
« Reply #1767 on: December 06, 2018, 07:48:59 AM »
That is dfort area. Could you share a file in the focus pixel thread or in Mlv app thread so it could be fixed?

ctfire

  • New to the forum
  • *
  • Posts: 38
Re: Canon EOS M
« Reply #1768 on: December 06, 2018, 12:08:05 PM »
Hey , is there any working ML for eos m with correct mv1080 without crop ?

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6010
Re: Canon EOS M
« Reply #1769 on: December 06, 2018, 12:35:26 PM »
There's no crop with the mv1080p preset.

ctfire

  • New to the forum
  • *
  • Posts: 38
Re: Canon EOS M
« Reply #1770 on: December 06, 2018, 04:10:19 PM »
There's no crop with the mv1080p preset.

And what about live view when recording in this mode?

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6010
Re: Canon EOS M
« Reply #1771 on: December 06, 2018, 04:29:57 PM »
It is what it is. THanks to A1ex we at least have full preview but a bit slow...

Teamsleepkid

  • Member
  • ***
  • Posts: 229
Re: Canon EOS M
« Reply #1772 on: December 07, 2018, 02:42:12 AM »
alex is the coolest
EOS M

alpicat

  • Freshman
  • **
  • Posts: 56
Re: Canon EOS M
« Reply #1773 on: December 08, 2018, 01:13:44 AM »
That is dfort area. Could you share a file in the focus pixel thread or in Mlv app thread so it could be fixed?

Will do, I've been trying to get a screengrab that shows all the focus pixels clearly but no success so far, hard to tell the focus pixels apart from the background. I guess if I shoot against a clear sky that might work best.

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3739
Re: Canon EOS M
« Reply #1774 on: December 08, 2018, 04:57:37 PM »
Try shooting simple silent stills with the movie settings at the resolution you want to test. This will save a DNG of the full raw buffer. Shoot light subjects, dark subjects, flat walls, scenes with lots of contrasty details--sometimes focus pixels pop right out and other times they are hard to find. Then again if you can't find them that's the best news of all!
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102