Author Topic: Canon EOS M  (Read 847802 times)

jacquaviva

  • New to the forum
  • *
  • Posts: 17
Re: Canon EOS M
« Reply #2000 on: January 25, 2019, 10:38:12 AM »
Danne, do you mean framing is improved for crop mode mv1080 ? Thank you

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5906
Re: Canon EOS M
« Reply #2001 on: January 25, 2019, 10:52:22 AM »
Nope. Other issues.

ctfire

  • New to the forum
  • *
  • Posts: 37
Re: Canon EOS M
« Reply #2002 on: January 25, 2019, 11:17:24 AM »
New build. Only affects 'framing' setting. Hopefully solid preview now:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

No need for Clear Overlays 'HalfShutter' in framing mode hopefully.



Just tested that build, it's awesome improvement in preview. 1080mv in 2.35 : 1 now is more than usable. Thank you. Also tested 50fps option with sd uhs hack , and only downside is that in 14 bit loseless it's only rec 5 sec. But as i understand this is depends more from sd card than from magic lantern. Thank you againe Danne.

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5906
Re: Canon EOS M
« Reply #2003 on: January 25, 2019, 01:12:07 PM »
Cool. Yes, probably card. I can record more or less continuous when selecting 10bit.
Just pushed a build with slightly changed registers in 50fps modes. 45fps is still problematic.

AF-OFF

  • Freshman
  • **
  • Posts: 97
  • 50Dc EOSM
Re: Canon EOS M
« Reply #2004 on: January 25, 2019, 04:31:22 PM »
Did a quick 1x3 recording with the new (Jan25) build
10bit and 1:2.35, sd-uhd, didn't touch any of the regs
had to deaktivate sound, because it would record only few seconds

I was able to record continuously. first clip with the default 'Framing' - setting (Auto),
for 3 1/2 minutes. Then switched to Real-time and recorded 2 1/2 min.

With MLV App (drop frames disabled) both of them without any damage
Will test other modes later

Many thanks to Danne and other developers

 

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3736
Re: Canon EOS M
« Reply #2005 on: January 25, 2019, 05:25:05 PM »
...Notice that the only failing tests are the focus tests. This is with the EF-M 22mm f/2 prime lens but it is happening with all lenses in both movie and photo mode...

Figured it out. Those failing tests are supposed to run in photo mode outside of LiveView. In other words, the tests aren't valid on the EOSM/EOSM2.

Ok--now back to the cool stuff that Danne is doing.
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1359
Re: Canon EOS M
« Reply #2006 on: January 25, 2019, 06:48:30 PM »
Rendered 2 clips recorded with todays build @ 1x3 and another one @50p. No corrupted frame and just one single frame jump. So: nice progress!
I noticed in 1x3 a red line at the bottom. Is it possible to do something against? Or do we have to fix that in post (e.g. by copying blue and green channel from row n-1)?
5D2.212 | EOSM.202

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5906
Re: Canon EOS M
« Reply #2007 on: January 25, 2019, 06:52:31 PM »
Green line. I will take a look. Full 5k set up or 2.35:1?
What preset caused the frame jump by the way? With or without global draw enabled?

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1359
Re: Canon EOS M
« Reply #2008 on: January 25, 2019, 07:06:08 PM »
Setting was GlobalDraw On, 1504x1920, 10bit lossless, preview=framing.
Here the bottom line is red. You should it also have in the clip I sent you.
5D2.212 | EOSM.202

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5906
Re: Canon EOS M
« Reply #2009 on: January 25, 2019, 07:50:25 PM »
Thanks for noticing! Fixed:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

It could be fixed also by using the height reg in the sub menu reg_6804 set to + 1. Well sorry for this, new build posted.

Commit:
https://bitbucket.org/Dannephoto/magic-lantern/commits/133ba5a624c0b5d9bb7af809d8e792d16651ec39

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1359
Re: Canon EOS M
« Reply #2010 on: January 25, 2019, 08:38:18 PM »
Fantastic Danne! Works!
5D2.212 | EOSM.202

henricusmaria

  • Freshman
  • **
  • Posts: 70
Re: Canon EOS M
« Reply #2011 on: January 26, 2019, 06:35:15 AM »
Sounds good! Does it also work in other ratios like 16:9?

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5906
Re: Canon EOS M
« Reply #2012 on: January 26, 2019, 10:30:31 AM »
@henricusmaria
I pushed a fix also for the 5k 3x1 preset. Had a thin red line:

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

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...

henricusmaria

  • Freshman
  • **
  • Posts: 70
Re: Canon EOS M
« Reply #2013 on: January 26, 2019, 01:19:13 PM »
I will let you know, when I find the time. I am actually looking for a preset that gives me clean/corrupt free footage. I am shooting a film in China and I want to use the eos m in some areas where it’s a bit difficult (not allowed) to film. Right now I’m thinking of using the 2.5k preset since it’s the cleanest. The mv1080 gives too much aliasing and moire. But it would be great to be able to shoot with a wider angle. The 1x3 preset looks promising!

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5906
Re: Canon EOS M
« Reply #2014 on: January 26, 2019, 01:32:50 PM »
Cool. Yes 1x3 should be the best if it's reliable. If you could test it thoroughly we might work out a solid working 1x3 preset.

henricusmaria

  • Freshman
  • **
  • Posts: 70
Re: Canon EOS M
« Reply #2015 on: January 26, 2019, 02:03:29 PM »
Yes, will do. I have one more week of testing to go..

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5906
Re: Canon EOS M
« Reply #2016 on: January 26, 2019, 02:18:31 PM »
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

  • Contributor
  • Hero Member
  • *****
  • Posts: 1359
Re: Canon EOS M
« Reply #2017 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.
5D2.212 | EOSM.202

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5906
Re: Canon EOS M
« Reply #2018 on: January 26, 2019, 02:41:42 PM »
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

  • Freshman
  • **
  • Posts: 70
Re: Canon EOS M
« Reply #2019 on: January 26, 2019, 03:17:46 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

  • Contributor
  • Hero Member
  • *****
  • Posts: 5906
Re: Canon EOS M
« Reply #2020 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?

bergamote

  • New to the forum
  • *
  • Posts: 13
Re: Canon EOS M
« Reply #2021 on: January 26, 2019, 03:56:45 PM »
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

  • Freshman
  • **
  • Posts: 70
Re: Canon EOS M
« Reply #2022 on: January 26, 2019, 04:05:18 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

  • Contributor
  • Hero Member
  • *****
  • Posts: 5906
Re: Canon EOS M
« Reply #2023 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

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3736
Re: Canon EOS M
« Reply #2024 on: January 26, 2019, 09:07:14 PM »
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
Code: [Select]
// 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
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102