Author Topic: Canon EOS M  (Read 1095331 times)

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6933
Re: Canon EOS M
« Reply #2325 on: February 24, 2019, 09:20:11 PM »
I should recommend run the cinema lua script as starting point. It sets to 1:2 in RAW menu and you also end up in anamorphic mode. Then I would leave RAW video alone and only use settings in Crop mode sub menu and start build from there. It´s part of the round trip journey.
Quote
- somehow it seems the standard is x3 zoom mode. So it was always hard to come out there to get normal mode...
Can´t really follow you. But yes, rewire MC mode is a totally different beast from the other crop_rec presets. Getting back to the other presets is a bit harder than usual.
If I knew more c-code I would put it in either as a menu option in Movie crop mode or have it as default when starting up my eosm and selecting RAW video.

Jonit

  • New to the forum
  • *
  • Posts: 39
  • EOS M | 700D
Re: Canon EOS M
« Reply #2326 on: February 24, 2019, 09:53:39 PM »
@masc just to check, when you're exporting the video (or png file) from MLVapp, are you disabling "Fix focus dots"? If you leave that setting on, as it is by default, I find that additional focus pixels which are really difficult to see show up, and they're not there if turned the setting is turned off.

Thanks for pointing that out. Yes, you're right. It was "Fix focus dots" which was causing those pixels.

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3751
Re: Canon EOS M
« Reply #2327 on: February 25, 2019, 01:03:45 AM »
Maybe this will clear up some of the confusion over what is happening with the focus pixels on these new resolutions:

https://www.magiclantern.fm/forum/index.php?topic=16054.msg212529#msg212529

Then again maybe it just adds to the confusion.
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1691
Re: Canon EOS M
« Reply #2328 on: February 25, 2019, 10:11:52 AM »
Great work @dfort! That works so good also in MLVApp. Now MCM rewire looks really nice for me (and hopefully many others).
5D3.113 | EOSM.202

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6933
Re: Canon EOS M
« Reply #2329 on: February 25, 2019, 10:18:58 AM »
Cool. So Mlv app updated for mcm mode now?

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1691
Re: Canon EOS M
« Reply #2330 on: February 25, 2019, 10:29:43 AM »
Not directly. Download 80000331_1872x1190.fpm from dfort's repos and copy it next to executable (.exe on Win, on OSX executable inside app package). MLVApp will recognize this file and use it.
5D3.113 | EOSM.202

Jonit

  • New to the forum
  • *
  • Posts: 39
  • EOS M | 700D
Re: Canon EOS M
« Reply #2331 on: February 25, 2019, 10:38:36 AM »
Outstanding work dfort! I have such a deep appreciation for this community. You guys are doing great job here.

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6933
Re: Canon EOS M
« Reply #2332 on: February 25, 2019, 11:10:44 AM »
Nice masc. I wonder if we can add one pixel map for both x3zoom and mcm rewired in the same context that would work with both setups.

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1691
Re: Canon EOS M
« Reply #2333 on: February 25, 2019, 12:51:16 PM »
I don't know why, but the focus pixel map from dfort only works for full (uncropped) MCM rewire clips. So 3:2 works, but e.g. 16:9 doesn't. It looks like there is an wrong offset somewhere (when pixel peeping). Until now I thought, if you have the map for maximal resolution of a preset, it works also for cropped clips. (not zoomed)
5D3.113 | EOSM.202

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6933
Re: Canon EOS M
« Reply #2334 on: February 25, 2019, 01:22:34 PM »

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6933
Re: Canon EOS M
« Reply #2335 on: February 25, 2019, 02:15:00 PM »
Just tested my change and it worked when changing reg 6804 to the same as for the 3:2 preset:
0x4a601e4
So if we now the 0x4a601e4 is working then we can work from this one aand calculate any new offset from that when following the rest of the presets? There are also this for x3zoom in my crop_rec.c:
0x45601e4

For 16:9 and 2.35:1 I have this:
0x42401e4 but will change to working 0x4a601e4

0x4a601e4 = 1736x1190
0x45601e4 = 1736x1110


Maybe should have a talk with the "dotman" dfort...

Edit: 0x45601e4 seems to work with x3zoom...

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1691
Re: Canon EOS M
« Reply #2336 on: February 25, 2019, 08:46:05 PM »
Did a quick test without any crop submenu setting and with 16:9. Both was working with the focus pixel map. Yay. :)

Edit: 2.35:1 at 3x3 working too. At x3 zoom, it is working for 1800x1012 (in two of three clips, must test where the difference is, maybe just forgot the menu buttons), for 1800x766 too, but not for 1624x1080.
5D3.113 | EOSM.202

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6933
Re: Canon EOS M
« Reply #2337 on: February 25, 2019, 09:55:16 PM »
...but not for 1624x1080.

I do some trickery to differ this mode to get around some of a1ex black level autodetection code in raw.c. I knew it would bite me sooner or later. I´ll see if I can do something else here(c-noob):
Code: [Select]
          case 0xC0F06804: return 0x45601e5);

    /* needed for autodetecting black level in mlv_lite.c */
        case 0xc0f06800: return 0x10011;


EDIT:
Ok, let´s try this one. Should work better:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Feb25.EOSM202.zip

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1691
Re: Canon EOS M
« Reply #2338 on: February 25, 2019, 10:11:24 PM »
Ok, let´s try this one. Should work better:
https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Feb25.EOSM202.zip
Hmm... really? This build is able to toggle my LED. Camera not booting.  :P
5D3.113 | EOSM.202

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6933
Re: Canon EOS M
« Reply #2339 on: February 25, 2019, 10:14:08 PM »
Happens to me sometimes. Check an extra round if you extracted all ml files onto your card. Or do a battery pull  :P

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1691
Re: Canon EOS M
« Reply #2340 on: February 25, 2019, 10:14:57 PM »
All done. Downloaded, installed, battery pulled... all 2x.  :-[
5D3.113 | EOSM.202

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6933
Re: Canon EOS M
« Reply #2341 on: February 25, 2019, 10:17:57 PM »
Strange. I just downloaded and ran it on my camera. Hm, older build working? Cam starting without ML on it?

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1691
Re: Canon EOS M
« Reply #2342 on: February 25, 2019, 10:22:15 PM »
Reverted to an older build. Worked. Installed again. Working now. WTF.

Tested all 6 MCM rewire combinations between AR and x3 zoom: all working with dfort's focus pixel file. GREAT!

Positive side effect with MCM rewire: AUTO-ISO is working really good here. ;)
5D3.113 | EOSM.202

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6933
Re: Canon EOS M
« Reply #2343 on: February 25, 2019, 10:25:00 PM »
Great! Mcm touching prop regs. Seems stable enough though. One really have to abuse some code watch guards to soft brick. Believe me, been there. A1ex fixed it in half an hour though  :P.
Autoiso. Gotta test. Never used it.

MADagain

  • New to the forum
  • *
  • Posts: 2
Re: Canon EOS M
« Reply #2344 on: February 26, 2019, 02:42:35 AM »
Is there a stable build for the EOS M?

DeafEyeJedi

  • Hero Member
  • *****
  • Posts: 3397
  • 5D3 | M1 | 7D | 70D | SL1 | M2 | 50D
Re: Canon EOS M
« Reply #2345 on: February 26, 2019, 04:22:55 AM »
Great! Mcm touching prop regs. Seems stable enough though.

Agreed. Been playing with this all afternoon and so far I've been impressed. Still trying to push it's limits.

Autoiso. Gotta test. Never used it.

Same here. Just tried and I can see what @masc is referring to... especially when utilizing the EF-M 18-55 STM. That lens is a fun toy to play with. So light!

Is there a stable build for the EOS M?

Why don't you just give a try at least with today's build from @Danne's bitbucket page?  :P
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3751
Re: Canon EOS M
« Reply #2346 on: February 26, 2019, 06:26:47 AM »
Maybe should have a talk with the "dotman" dfort...

I just finished going through all the sample files I could find for the EOSM and it looks like there's "only" a half-dozen of these new crop_rec settings that aren't quite working 100% yet with the new map files. I've been pushing to the repository so if you want to give it a try (in MLVFS) please do so.

Off topic: The 100D tests are 100% at this point.
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 6933
Re: Canon EOS M
« Reply #2347 on: February 26, 2019, 07:08:40 AM »
Great!
By the way. Is it possible to do the same kind of testing but from Mlv App instead?

dfort

  • Developer
  • Hero Member
  • *****
  • Posts: 3751
Re: Canon EOS M
« Reply #2348 on: February 26, 2019, 07:45:00 AM »
Not sure. Look in in MLV-App-master/src/mlv/llrawproc/pixelproc.c around line 318 and you'll see there's code there to use ".fpm" files but I'm not sure how it works. The plan is to re-write the code to create the map files as needed for these new crop_rec settings.
5D3.* 7D.206 700D.115 EOSM.203 EOSM2.103 M50.102

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1691
Re: Canon EOS M
« Reply #2349 on: February 26, 2019, 08:05:15 AM »
Is it possible to do the same kind of testing but from Mlv App instead?
This is what I do.

Not sure. Look in in MLV-App-master/src/mlv/llrawproc/pixelproc.c around line 318 and you'll see there's code there to use ".fpm" files but I'm not sure how it works.
MLVApp searchs for fpm files first. If it doesn't find one, it uses internal code. If it finds a fpm file, it uses the file. So just copy your fpm next to the executable (.exe on Win, executable inside App package on OSX) and have fun. This will override internal code for this setting.
5D3.113 | EOSM.202