Author Topic: Canon EOS M  (Read 1090322 times)

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6920
Re: Canon EOS M
« Reply #2050 on: January 29, 2019, 07:41:38 PM »
The 50fps preset right? Might settle for the 48fps soon then.

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1677
Re: Canon EOS M
« Reply #2051 on: January 29, 2019, 07:52:16 PM »
Right... edited.
5D3.113 | EOSM.202

henricusmaria

  • Freshman
  • **
  • Posts: 70
Re: Canon EOS M
« Reply #2052 on: January 30, 2019, 04:53:58 AM »
Managed to get 1x3 footage in 16:9 without corrupted frames. Only there is too much aliasing going on to my liking. Anything I can change in my ml settings or mlvapp that can help?

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6920
Re: Canon EOS M
« Reply #2053 on: January 30, 2019, 05:57:44 AM »
Could you upload an example with aliasing? Maybe a shortened mlv?

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1677
Re: Canon EOS M
« Reply #2054 on: January 30, 2019, 07:57:21 AM »
Managed to get 1x3 footage in 16:9 without corrupted frames. Only there is too much aliasing going on to my liking. Anything I can change in my ml settings or mlvapp that can help?
I think I know what you mean, because I also was not satisfied in the beginning. I think you are speeking about artifacts on detailed structures like trees?! Are you able to compile MLVApp? The latest revisions can debayer such MLVs much better. You could compile MLVApp yourself or wait for next release. Using Resolve you should be fine...
5D3.113 | EOSM.202

henricusmaria

  • Freshman
  • **
  • Posts: 70
Re: Canon EOS M
« Reply #2055 on: January 30, 2019, 08:47:11 AM »
@masc I think you know what I mean ;)
How do you compile mlvapp?

@Danne I’ve already deleted the mlv files

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1677
Re: Canon EOS M
« Reply #2056 on: January 30, 2019, 09:00:42 AM »
How do you compile mlvapp?
See compiling information on this site: https://github.com/ilia3101/MLV-App
On the other side, v1.5 is not far away...  8)
5D3.113 | EOSM.202

henricusmaria

  • Freshman
  • **
  • Posts: 70
Re: Canon EOS M
« Reply #2057 on: January 30, 2019, 09:25:07 AM »
Thanks! I will have a look.
V1.5 might not be far away, but I need to find out this week if the 1x3 mode is reliable enough to shoot with.

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6920
Re: Canon EOS M
« Reply #2058 on: January 30, 2019, 11:58:14 AM »
New upload:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

Focused on corruption free recordings on all presets. Let´s see where and if it breaks:


 

AF-OFF

  • Member
  • ***
  • Posts: 109
  • 50Dc EOSM
Re: Canon EOS M
« Reply #2059 on: January 30, 2019, 03:54:47 PM »
Downloaded new build from Danne and did some little tests.
build Jan30, sd-uhs hack, 10bit, 16:9 global draw off, sound module not loaded, MLV App 1.4 (Playback>Drop Frame Mode off)
first just did a benchmark with the bench.mo from the ML experimental Lua build copied over inside the Modules directory of Danne's build. The performance dropped about 5MB/s but fortunately now the benchmark runs the read-tests too, which it did not in previous builds. So with max of 54MB/s Write and 56MB/s Read I did following quick tests. 
mv720p 1736x694 50fps
recording stopped after 23 seconds. had to stretch the image 1,67x in MLV App, reported Frame rate was 49.959 fps. after 650 frames first corrupted frame, seven in total.
same mode but reduced Frame rate to 47 fps. recording continuous, did a 00:01:36 recording, reported speed 47.009 fps. Have done the same height stretch of 1,67x as before. Somewhere at 00:01:20 mark there was one bad frame.
next I did a mv1080p 1736x976 46/48 fps recording. from start on I lowered the Frame rate to 44 fps. But as MLV App reports, it has the res of 1496x842 pixels which is 16:9 ratio. no stretch needed in MLV App. did a continuos recording of 5896 frames (00:02:13) at frame rate of 44.013 fps.
There were 27 bad frames in the first 40 seconds of the video, so I did another recording but this time did not lower the frame rate.
reported frame rate is 45.983 fps. one minute recording, 2 bad frames .

So this looks very good, many thanks to Danne and others
Will do further testing

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6920
Re: Canon EOS M
« Reply #2060 on: January 30, 2019, 04:51:41 PM »
Thanks AF-OFF. Still much to work on :P. If you lower fps try do it from reg_6014 register in the submenu. Push it forward for decrease.
One goal is to have the 2.35:1 setting working with all presets without issues. THe rest is more or less extras. If you want to test the presets with the 2.35:1 ratios set I wouldn´t mind hearing about the results  8)

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1677
Re: Canon EOS M
« Reply #2061 on: January 30, 2019, 08:07:13 PM »
This test release changes a lot, Danne! mv1080 48fps @1648x702, okay, some pixels are missing now (a little smaller), but I get continous recording @10bit lossless now and after 45sec (>2000 frames) I have no single corrupted frame! WOW! Important: Global Draw has to be OFF. If I leave it ON, the maximum I can get is 800 frames, but with may 1 corrupted frame in 20 frames.
5D3.113 | EOSM.202

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6920
Re: Canon EOS M
« Reply #2062 on: January 30, 2019, 08:45:26 PM »
That is good news. I really want the 2.35:1 presets to be solid and to have a 48fps 3x3 binning is very nice indeed.

Jonit

  • New to the forum
  • *
  • Posts: 39
  • EOS M | 700D
Re: Canon EOS M
« Reply #2063 on: January 30, 2019, 09:42:06 PM »
Awesome work Danne!!!

I did some tests yesterday with yesterday build and I was getting some pink frames in 50fps mode and also 5k anamorphic - dualISO.
I'm going to shoot a wedding in three days so I guess it will be a serious test for this stuff  ;). There will be also a second cameraman on that wedding, otherwise I wouldn't risk the shots with such a bleeding edge stuff. Actualy, that was my requisition, that I would only film if they allow me to film in ML RAW  8), I explained the risks... All this development in RAW video is so exciting, that I didn't touch the normal video mode in a quite long time and I'm shooting almost exclusively in RAW.

Anyway... the most important modes for me are 48fps and DualISO. Today I tested your current build (30.1.) and I was blown away by how much it improved over yesterdays build.
I got some pink frames, but very few in a long recordings, and now I realized that it was probably due to the fact that I didn't turn off the global draw. Need to test it again with GD off.

Here are my results (with GD on, framing LV, 1:2.35, 10bit)(all recordings stopped manualy):
5K-A-DualISO-sound: 20 seconds - 0 corrupted frames
5K-A-DualISO-NOsound: 14 seconds - 0 corrupted frames
1080_3x3-1648x702-48fps-sound: 25 seconds - 5 corrupted frames, evenly happening in the first half of the clip
1080_3x3-1648x702-48fps-NOsound: 40 seconds - 2 corrupted frames (one after another) in the middle of the clip


SIDE QUESTION: I'm getting 700D tomorrow and I'm wondering in what state of development it currently is regarding to 1x3 mode and 48fps mode? I was trying to find something on the forum, especialy about the 48/50fps mode and I didn't find much :(. If any of you guys know, my question is, if there is a working build for 700D with reliable 48fps recording?

Thanks!

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6920
Re: Canon EOS M
« Reply #2064 on: January 30, 2019, 10:44:43 PM »
I would do all recordings with 10bit 2.35:1 sd_uhs on.
48fps with global draw off.
If the anamorphic mode isn't continuous you can reduce offsets manually by using the skip_left, skip_reight etc to reduce ratio straight in the sub menu. This maybe works straight in Raw video resolution menu, not sure.
Anyway. Tell me what presets you aim to use and we can focus on them for a while.
700D has some very intelligent crop_rec code from a1ex. Also ask theBilalfarouk for some useful info.

AF-OFF

  • Member
  • ***
  • Posts: 109
  • 50Dc EOSM
Re: Canon EOS M
« Reply #2065 on: January 31, 2019, 12:02:57 AM »
If you want to test the presets with the 2.35:1 ratios set I wouldn´t mind hearing about the results  8)
sure ...
Just downloaded the fresh Jan30 build and did some testing - all recordings 2.35:1 , 10bit, sd-uhs , no GD and no sound. did stop all recordings manualy after 1min.
mv720p, 1736x694 50fps, no bad frames. MLV App reports 1736x442 pixels , 49,959fps. needs a height stretch 1.67x.
mv1080p, 1736x976 46/48 fps, no bad frames, actual size is 1648x702 & 47,991 fps.
mv1080p, 1736x1158, two bad frames, actual size 1736x738 & 24.002 fps.
& finally also 2.5k 2520x1418, no bad frames, actual size 2520x1072 & 23,976 fps.

it gets better and better. Many Thanks Danne and others



   

Jonit

  • New to the forum
  • *
  • Posts: 39
  • EOS M | 700D
Re: Canon EOS M
« Reply #2066 on: January 31, 2019, 08:45:43 AM »
I would do all recordings with 10bit 2.35:1 sd_uhs on.
48fps with global draw off.
If the anamorphic mode isn't continuous you can reduce offsets manually by using the skip_left, skip_reight etc to reduce ratio straight in the sub menu. This maybe works straight in Raw video resolution menu, not sure.
Anyway. Tell me what presets you aim to use and we can focus on them for a while.

Yeah, I did all recordings with 10bit 2.35:1 sd_uhs on, only difference was that I had GD on. Didn't have time yesterday to test it with GD off. But anamorphic seemed to do OK even with GD on and recording times were also great (possibly continuous). The only "problem" was with 48fps, where it had a couple of pink frames.
Do you think Danne, that there will be a possibility someday to run corruption-free 48fps with GD on? So to have a proper framing... because I find it quite difficult to properly frame a subject without "framing LV" mode.

Thanks a lot.

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6920
Re: Canon EOS M
« Reply #2067 on: January 31, 2019, 09:07:05 AM »
You could test the 2.35:1 48fps setting with preview Real-time or Auto. Could give a corrupted file, especially in the beginning.

ctfire

  • New to the forum
  • *
  • Posts: 45
Re: Canon EOS M
« Reply #2068 on: January 31, 2019, 01:24:23 PM »
Just film some footage and also get color dots in blown out areas , for converting mlv i as always use MLVapp


masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1677
Re: Canon EOS M
« Reply #2069 on: January 31, 2019, 01:29:07 PM »
Just film some footage and also get color dots in blown out areas , for converting mlv i as always use MLVapp


What was your setting (camera and MLVApp)? Would be nice to get some frames of this clip for testing! These dots look different than mine. Have you tried MLVApp version from today? v1.5 is out!
Danne solved one of my dot problems: don't use ISO6400! (I would never do that for serious recording. I only did that for testing... and so the dots came...)
5D3.113 | EOSM.202

gravitatemediagroup

  • Member
  • ***
  • Posts: 242
Re: Canon EOS M
« Reply #2070 on: January 31, 2019, 03:28:29 PM »
What setting would be causing all highlights to be pink?  I've tried several variations of settings adjustments but pink is all I get, so I figured I'd stop and ask for directions. lmao

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6920
Re: Canon EOS M
« Reply #2071 on: January 31, 2019, 03:50:06 PM »
More info please. Settings etc. Maybe also a mlv file.

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1677
Re: Canon EOS M
« Reply #2072 on: January 31, 2019, 05:02:24 PM »
What setting would be causing all highlights to be pink?  I've tried several variations of settings adjustments but pink is all I get, so I figured I'd stop and ask for directions. lmao
There is no setting causing pink highlights. It is the standard of each file where highlights are overexposed (green channel clipped makes pink color). You can repair this: bring down exposure of highlights, check Highlight Reconstruction, setup "the right" RAW White Level. For my EOS M @10bit lossless this is around 2800+-100.
@Danne: sometimes this is a little higher, sometimes a little lower. Do you have an idea why? Normally the value were a channel clips should always be the same.
5D3.113 | EOSM.202

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6920
Re: Canon EOS M
« Reply #2073 on: January 31, 2019, 05:10:43 PM »
Not really sure. Maybe lossless works with variable bitrates in highlight. Maybe I am talking out of my ass  :P.
Anyway. I set 10bit by reducing gain valuse in crop_rec.c:
Code: [Select]
    if (bitrate == 0x3)
    {
/* 10bit roundtrip only not applied here with following set ups */
adtg_new[13] = (struct adtg_new) {6, 0x8882, 60 + reg_analog_gain};
                adtg_new[14] = (struct adtg_new) {6, 0x8884, 60 + reg_analog_gain};
                adtg_new[15] = (struct adtg_new) {6, 0x8886, 60 + reg_analog_gain};
                adtg_new[16] = (struct adtg_new) {6, 0x8888, 60 + reg_analog_gain};
}

In raw.c I hard code White level to 3000. Maybe it should be set to 2800?:
Code: [Select]
        if (shamem_read(0xC0F42744) == 0x4040404)
        {
    /* 10bit by checking pushed liveview gain register set in crop_rec.c */
            int default_white = WHITE_LEVEL;
            return (default_white = 3000);   
        }

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 12457
Re: Canon EOS M
« Reply #2074 on: January 31, 2019, 05:11:01 PM »
Pink highlights: see this commit and follow the links.

The workaround for 700D/100D might also work out of the box on EOS M/M2 and 650D, possibly other models, or it might not. Running the tests linked in the above commit is the only way to find out.

If analog gains are tweaked, it might be a different story. Still, the value printed by raw_diag should be a good starting point.