Author Topic: Canon EOS M  (Read 1169609 times)

IDA_ML

  • Hero Member
  • *****
  • Posts: 895
Re: Canon EOS M
« Reply #4100 on: May 06, 2020, 09:48:00 PM »
See that darn RGB moire crap in the trees? Is that normal?

Yes, this is normal in the 3x3 modes.  You can lessen moire and aliasing doing the following:

1) Try to avoid filming in high-contrast lit scenes.  Avoid high-contrast edges and straight lines in your scenes;

2) If possible, try not to use your sharpest lenses.  Vintage manual focus lenses do a great job in reducing moire and aliasing!

3) Try to film in the full sensor readout 5k anamorphic mode at 14 fps and then using the optical flow method in Resolve, interpolate your footage to 24 fps.  This works best for me.

4) Play with the chromatic aberation slider in MLVApp to suppress the color artefacts.

Danne

  • Developer
  • Hero Member
  • *****
  • Posts: 7031
Re: Canon EOS M
« Reply #4101 on: May 09, 2020, 09:16:51 AM »
New build:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

- refining higher frame rates
- custom modes


Been having issues with higher framerates for a long time. This is an attempt to fix frame corruption and increasing resolution for no ratio and 16:9 ratio. These modes needs testing so any help would be appreciated. There´s still a chance for frame corruption if you enable set_25fps. This will give you 48fps in 2.39:1 and 2.35:1 ratios. Otherwise 46fps.
Kill global draw enabled is mandatory for corruption freeness.

The other feature is about custom modes. Works like this. Upon installing magic lantern a folder tree is built but will not become active before a first reboot after install. Not the nicest way but better than having to go in manually and create these custom folders. Folders can be renamed to whatever you like. Folders are located in SETTINGS folder on your card.
How to use custom modes. Simply select a mode i.e CM1 and restart camera and then start customize any magic lantern setting. All will be saved into this folder. If you want more modes choose another i.e CM2 and restart camera and keep customize.
You can copy these folders into new magic lantern builds in the future if you like too. A small text with chosen custom mode will be showing in the right corner when checking menus to let you know where you are saving settings into.
More info from a1ex post here:
https://www.magiclantern.fm/forum/index.php?topic=24993.msg226872#msg226872

Higher fps refining


Before first reboot


After reboot


Thanks a1ex, Walter Schulz, IDA_ML


EDIT: reduced 16:9 to 38 fps for continuous recording reasons.

Walter Schulz

  • Contributor
  • Hero Member
  • *****
  • Posts: 7723
Re: Canon EOS M
« Reply #4102 on: May 09, 2020, 09:50:24 AM »
Little hint about renaming:
You should only use 12 characters if you rename your folders (because of 8.3 naming convention). Failing to do so will force cam to create a copy of your folder and name will be shortened to fit.

Example:
Folder name JustALongString will create a second folder named
JustALongStr

Both folders will show up in menu with just 12 characters visible. You can't tell them by name but the first one from top will be the one you created.
Try to avoid this.

This feature can handle up to 13 folders.

Your cam will order folders chronological according to folder creation or rename date!

ZEEK

  • Senior
  • ****
  • Posts: 305
Re: Canon EOS M
« Reply #4103 on: May 09, 2020, 03:25:35 PM »
New build:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959
Looks really good Danne, congrats! Saves me from switching SD Cards each time ;). I'll test it out tomorrow. Cheers! :)
EOS M - EOS M2 - 5D2

Danne

  • Developer
  • Hero Member
  • *****
  • Posts: 7031
Re: Canon EOS M
« Reply #4104 on: May 09, 2020, 07:35:59 PM »
Updated build again:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg208959#msg208959

No need for rebooting to get custom mode list enabled after vanilla install. Reboot still needed before customizing though. You need to be in one of the custom modes to be able and store configurations in the selected mode:
https://www.magiclantern.fm/forum/index.php?topic=24993.msg226973#msg226973

Thanks a1ex.

DeafEyeJedi

  • Hero Member
  • *****
  • Posts: 3401
  • 5D3 | M1 | 7D | 70D | SL1 | M2 | 50D
Re: Canon EOS M
« Reply #4105 on: May 10, 2020, 01:26:38 AM »
These modes needs testing so any help would be appreciated. There´s still a chance for frame corruption if you enable set_25fps. This will give you 48fps in 2.39:1 and 2.35:1 ratios. Otherwise 46fps.

This one just caught the corner of my eye. I've been hiding in the shadows as of late meanwhile watching Danne's bitbucket page which keeps on growing and yet still get updates periodically.  8)

That tells me that this community is still thriving (maybe not to the best of our ability) regardless of the unprecedented times we're all in. I'll definitely give this one a test run re: high FPS.
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

JRTRR

  • Just arrived
  • *
  • Posts: 1
Re: Canon EOS M
« Reply #4106 on: May 15, 2020, 01:49:08 PM »
Hi I'm James and I could really use some help.
I tried installing the most recent build of Magic Lantern for my Canon EOS M and it hasn't worked properly. I installed the build from the Dannephoto may 9th version and copied it onto my SD card. After putting in the SD card into my camera and clicking on the firmware update it said that it was incorrect and told me to remove my battery. I then went back in to my camera to find that the firmware had changed from 2.02 to 2.03 but Magic Lantern still hasn't installed. If anyone can give me any help on how to fix this it would be greatly appreciated as I am very unsure of what to do to fix this and add Magic Lantern another way.

Danne

  • Developer
  • Hero Member
  • *****
  • Posts: 7031
Re: Canon EOS M
« Reply #4107 on: May 15, 2020, 10:01:31 PM »
Unclear description. If you´re on firmware version version 2.0.3 downgrade to 2.0.2 and then it will work.

2blackbar

  • Senior
  • ****
  • Posts: 447
Re: Canon EOS M
« Reply #4108 on: May 16, 2020, 09:52:18 PM »
Danne did You changed structure cause croprec is not in modules in jiphop branch , i used hg clone https://bitbucket.org/Dannephoto/magic-lantern_jip-hop   like before
What should i clone and merge  ?
Quote
$ hg update crop_rec_4k_mlv_snd_raw_only
abort: unknown revision 'crop_rec_4k_mlv_snd_raw_only'!

Code: [Select]
hg clone https://bitbucket.org/Dannephoto/magic-lantern_jip-hop
cd magic-lantern_jip-hop
hg update crop_rec_4k_mlv_snd_raw_only
cd platform
cd eosm.202

ok solved it

Danne

  • Developer
  • Hero Member
  • *****
  • Posts: 7031
Re: Canon EOS M
« Reply #4109 on: May 16, 2020, 10:29:19 PM »
hehe, good. I was a bit surprised myself for a while but my brainfreeze just stopped here as well ;).

2blackbar

  • Senior
  • ****
  • Posts: 447
Re: Canon EOS M
« Reply #4110 on: May 16, 2020, 11:11:24 PM »
I noticed that anamorphic 1x3 mode does not work without ratio enabled, is it how its made, or a bug ? Cause normally i disable ratio and i change aspect ratio in tother submenu with resolutions and all cause it has a lot more options and ratios.
So when i turn off ratio and want to use anamorphic 5k 1x3 (second mode on the list under HD1080P) then half the image is pink and its single frame.
Not like its not working cause all you need to do is enable ratio menu.But i must admit i thought i changed some values in croprec by mistake and tried to figure it out,  cause i thought i broke that mode by tinkering.

Danne

  • Developer
  • Hero Member
  • *****
  • Posts: 7031
Re: Canon EOS M
« Reply #4111 on: May 16, 2020, 11:32:16 PM »
What happens when ratio is off it goes into flv full resolution live view and in 10 fps. That is you push menu button a couple of times to get the regs to settle.
When in this mode you can enable set_25fps and you'll get 2.35:1 full width 1736 in 18 fps.
Otherwise I hardcoded the selection in Movie tab menu.
Experimenting with other resolutions can be done from ratios off but it starts off in 10fps. Not likely that increasing fps with fps override will go more than 12 fps.

2blackbar

  • Senior
  • ****
  • Posts: 447
Re: Canon EOS M
« Reply #4112 on: May 16, 2020, 11:43:54 PM »
I see, would it be possible to get 4:3 ratio as well in ratio menu? It could be useful, what should i include to get new ratio, but now that i see it, requires shitload of regs  :o
Can i modify it from 16:9 ? And just use more skip pixels on left right

Danne

  • Developer
  • Hero Member
  • *****
  • Posts: 7031
Re: Canon EOS M
« Reply #4113 on: May 17, 2020, 12:09:11 AM »
Yes, go from 16:9 should work.

2blackbar

  • Senior
  • ****
  • Posts: 447
Re: Canon EOS M
« Reply #4114 on: May 17, 2020, 12:11:07 AM »
 but that won get max vertical res i suppose? or i should i simply not skip any pixels on bottom and top to get full vertical res ?

Danne

  • Developer
  • Hero Member
  • *****
  • Posts: 7031
Re: Canon EOS M
« Reply #4115 on: May 17, 2020, 12:22:42 AM »
I don´t use 4:3, I did not experiment with max resolutions with this ratio.

2blackbar

  • Senior
  • ****
  • Posts: 447
Re: Canon EOS M
« Reply #4116 on: May 17, 2020, 12:32:56 AM »
I skipped 0 from bottom in 4:3 but it gained only 20 pixels, where i can extend vertical resolution of anamorphic mode ?

Code: [Select]
   [CROP_PRESET_anamorphic_rewired_EOSM]  = { 1290, 1290, 1290,  960,  800 },
    [CROP_PRESET_anamorphic_EOSM]  = { 1290, 1290, 1290,  960,  800 },
This ?

Danne

  • Developer
  • Hero Member
  • *****
  • Posts: 7031
Re: Canon EOS M
« Reply #4117 on: May 17, 2020, 12:49:46 AM »
In this function register 0xC0F06804 alters resolution. Will probably break pixel maps. You can find height and width in the sub menu too. And you need to match 0xC0F0713c when modifying 6804:
Code: [Select]
static inline uint32_t reg_override_anamorphic_rewired_eosm(uint32_t reg, uint32_t old_val)
{
   
    /* gets rid of the black border to the right. Connected to mlv_lite which takes over these regs while recording  */
    if (!RECORDING)
    {
        EngDrvOutLV(0xc0f383d4, 0x4f0010 + reg_83d4);
        EngDrvOutLV(0xc0f383dc, 0x42401c6 + reg_83dc);
    }
   
    if ((ratios == 0x1 || ratios == 0x2) && presets != 0x8)
    {
        switch (reg)
        {
                /* 2.39:1 or 2.35:1 */
            case 0xC0F06804:
                return 0x78101e4 + reg_6804_width + (reg_6804_height << 16);
            case 0xC0F0713c:
                return 0x781 + reg_713c;
               
                // case 0xC0F06824: return OUTPUT_12BIT ? 0x5d4 + reg_6824: 0x69d + reg_6824;
                // case 0xC0F06828: return OUTPUT_12BIT ? 0x5d4 + reg_6824: 0x69d + reg_6824;
                // case 0xC0F0682C: return OUTPUT_12BIT ? 0x5d4 + reg_6824: 0x69d + reg_6824;
                // case 0xC0F06830: return OUTPUT_12BIT ? 0x5d4 + reg_6824: 0x69d + reg_6824;
               
            case 0xC0F06014: return set_25fps == 0x1 ? 0x89f + reg_6014: 0x89f + reg_6014;
            case 0xC0F0600c: return set_25fps == 0x1 ? 0x25b025b - 24 + reg_6008 + (reg_6008 << 16): 0x25b025b + reg_6008 + (reg_6008 << 16);
            case 0xC0F06008: return set_25fps == 0x1 ? 0x25b025b - 24 + reg_6008 + (reg_6008 << 16): 0x25b025b + reg_6008 + (reg_6008 << 16);
            case 0xC0F06010: return set_25fps == 0x1 ? 0x25b - 24 + reg_6008: 0x25b + reg_6008;
               
                /* dummy reg for height modes eosm in raw.c */
            case 0xC0f0b13c: return 0xd;
               
        }
       
    }
   
    if (ratios == 0x3 && presets != 0x8)
    {
        /* 16:9 */
        switch (reg)
        {
               
            case 0xC0F06804:
                return 0x78101e4 + reg_6804_width + (reg_6804_height << 16);
            case 0xC0F0713c:
                return 0x781 + reg_713c;
               
                //case 0xC0F06824: return OUTPUT_12BIT ? 0x638 + reg_6824: 0x69d + reg_6824;
                //case 0xC0F06828: return OUTPUT_12BIT ? 0x638 + reg_6824: 0x69d + reg_6824;
                //case 0xC0F0682C: return OUTPUT_12BIT ? 0x638 + reg_6824: 0x69d + reg_6824;
                //case 0xC0F06830: return OUTPUT_12BIT ? 0x638 + reg_6824: 0x69d + reg_6824;
               
            case 0xC0F06014: return set_25fps == 0x1 ? 0x89f + reg_6014: 0x89f + reg_6014;
            case 0xC0F0600c: return set_25fps == 0x1 ? 0x25b025b - 24 + reg_6008 + (reg_6008 << 16): 0x25b025b + reg_6008 + (reg_6008 << 16);
            case 0xC0F06008: return set_25fps == 0x1 ? 0x25b025b - 24 + reg_6008 + (reg_6008 << 16): 0x25b025b + reg_6008 + (reg_6008 << 16);
            case 0xC0F06010: return set_25fps == 0x1 ? 0x25b - 24 + reg_6008: 0x25b + reg_6008;
               
                /* dummy reg for height modes eosm in raw.c */
            case 0xC0f0b13c: return 0xd;
        }
    }
   
    if ((!ratios || presets == 0x6) && !set_25fps)
    {
        /* full readout */
        switch (reg)
        {
            case 0xC0F06804: return 0xcd701e4 + reg_6804_width + (reg_6804_height << 16);
               
            case 0xC0F06014: return 0x14E7 + reg_6014;
            case 0xC0F0600c: return 0x2550255 + reg_6008 + (reg_6008 << 16);
            case 0xC0F06008: return 0x2550255 + reg_6008 + (reg_6008 << 16);
            case 0xC0F06010: return 0x255 + reg_6008;
               
            case 0xC0F0713c: return 0xcd7 + reg_713c;
               
                /* dummy reg for height modes eosm in raw.c */
            case 0xC0f0b13c: return 0x11;
        }
    }
   
    //silent film mode
    if ((!ratios || presets == 0x6) && set_25fps)
    {
        /* full readout */
        switch (reg)
        {
            case 0xC0F06804: return 0x8a301e4 + reg_6804_width + (reg_6804_height << 16);
               
            case 0xC0F06014: return 0xbcf + reg_6014;
            case 0xC0F0600c: return 0x24b024b + reg_6008 + (reg_6008 << 16);
            case 0xC0F06008: return 0x24b024b + reg_6008 + (reg_6008 << 16);
            case 0xC0F06010: return 0x24b + reg_6008;
               
            case 0xC0F0713c: return 0x8a3 + reg_713c;
               
                /* dummy reg for height modes eosm in raw.c */
            case 0xC0f0b13c: return 0x11;
        }
    }
   
   
    return reg_override_bits(reg, old_val);
}

Danne

  • Developer
  • Hero Member
  • *****
  • Posts: 7031
Re: Canon EOS M
« Reply #4118 on: May 17, 2020, 01:10:33 AM »
Think you should go for 1280x2880.

2blackbar

  • Senior
  • ****
  • Posts: 447
Re: Canon EOS M
« Reply #4119 on: May 17, 2020, 09:59:52 AM »
I have no experience with altering these values, while changing framing was easy, this is not, when i try to change 6804 and 713c values in submenu then they wont affect anything.Its out of my skillset, i wanted to get 4:3 for anamorphic with true anamorphic lenses that require 4:3 to squeeze 2x image, also for 16mm film look and extend vertical res a bit.
But if it breaks pixel maps, maybe its not worth it.

Danne

  • Developer
  • Hero Member
  • *****
  • Posts: 7031
Re: Canon EOS M
« Reply #4120 on: May 17, 2020, 11:04:46 AM »
I tested some. You could start out with ratios off and then delimit height_6804 in sub menu. Delimit reg 713 with the same value. Decrease reg 6014 and reg 6008 to raise fps. If image breaks mess with cmos 7. Test set it to 341.
Problem is I think we need to go too low in height to achieve 24 fps. Personally not worth it but I could take a look building a preset to test.

critix

  • Contributor
  • Member
  • *****
  • Posts: 156
Re: Canon EOS M
« Reply #4121 on: May 17, 2020, 11:25:16 AM »
Danne's latest changes, but for 2.0.3:
https://www.magiclantern.fm/forum/index.php?topic=9741.msg224844#msg224844
Thanks, Danne
Canon 1300D, 500D, EOS M, EOS M2

cmh

  • Contributor
  • Member
  • *****
  • Posts: 137
Re: Canon EOS M
« Reply #4122 on: May 17, 2020, 05:04:52 PM »
I'll upgrade the firmware and test this out.
edit: so far so good, I'll keep it for at least a couple of weeks and report back if there's any problem.
edit 2: the preview seems stuck at real time, I can't get the framing mode (I checked the menu, tested various profiles, uninstalling/reinstalling).

2blackbar

  • Senior
  • ****
  • Posts: 447
Re: Canon EOS M
« Reply #4123 on: May 17, 2020, 07:58:53 PM »
Its complicated, without ratio and fps override i have max 14fps,but with override and ratio its normal 23.976 and normal shutter speeds .
I guess it will be easier to just modify 16:9 and crop on sides to get 4:3 instead of trying to make taller frame.

Danne

  • Developer
  • Hero Member
  • *****
  • Posts: 7031
Re: Canon EOS M
« Reply #4124 on: May 17, 2020, 09:29:08 PM »
Yes. Full resolution to the cost of fps but you could reverse it and find sweet spot of 4:3. If worth the hassle that is...

Edit: Speaking fps. There´s some lock in h.264 when recording with increased fps. Sure would be nice to find out what´s stopping the camera from recording here.