Author Topic: Canon EOS M  (Read 850627 times)

henricusmaria

  • Freshman
  • **
  • Posts: 70
Re: Canon EOS M
« Reply #3500 on: September 27, 2019, 01:36:59 PM »

turnlemons2lemonade

  • New to the forum
  • *
  • Posts: 16
Re: Canon EOS M
« Reply #3501 on: September 27, 2019, 02:27:35 PM »
Hey guys, I just registered to congratulate Danne & Zeek (and others) for pushing this little beast.

I'm also starting my channel which will be mostly using the EOS M for everything video.

I have a few questions and I think it would be great to have answers on this:
1. What is the most stable and lower file size preset we can use right now? I've been currently using MCM Rewire preset but I'm getting some dropframes here and there when using a Feelworld MA5 monitor (probably because I can't switch the feed to 480p) - so for that I think when recording it's just better to turn off the monitor, right? At least for the moment.
2. Is there a faster way to convert ML RAW to ProRes 422 LT? MLVApp seems to be taking around 10 minutes for 30 seconds of video. I'm shooting long format 5-10 minutes videos for my YouTube channel and converting 10 minutes of RAW to ProRes is taking 2 days.
3. I noticed that it's a very big difference in file size between ProRes 422 & 422 LT with not that much disadvantages. Also it seems that MLVApp doesn't care if you export 4K or 1080p, the export time for a 30 second clip is usually the same. Also MLVApp seems to freeze sometimes, a few times I exported 3 minute RAW clip and it just froze after 1.5 hours.
4. The preamps in this camera doesn't seem to be that great neither, so probably would be better off recording externally. Any suggestions on that?

Overall I am blown away at the difference between H264 and ML RAW and definitely will continue using it, I'm just trying to find a workflow that's worth it so that I'm not waiting 5-8 hours to export videos.


743v04

  • Just arrived
  • *
  • Posts: 1
Re: Canon EOS M
« Reply #3502 on: September 27, 2019, 07:17:13 PM »
First just want to thank everyone (especially Danne!) for all of the hard work put into this amazing project. Does anyone have experience using the EOS-M with a Zhiyun Crane 2 by any chance? I recently picked one up to use with my 5D II, and it works perfect with that running the experimental 10-12 bit firmware.

However, trying it with my EOS-M running the most recent firmware release when I try to use it the same way it gives me a computer connection symbol on the screen. It seems like it has something to do with the fact that the M is mirrorless so doesn't have a non live view to switch out of like the DSLR 5D does, but I just figured it was worth checking in to see if anyone has any insight!

I do not have any video of this behavior to show currently, however I can get some over the weekend to show what I mean if it is something anyone is willing to look into, thanks!

guerchi

  • New to the forum
  • *
  • Posts: 13
Re: Canon EOS M
« Reply #3503 on: September 27, 2019, 07:40:45 PM »
1280x1900, what ratio is that?
I also recommend using the 5k anamorphic rewired mode. A little less height but more stable.
With 1280x1900 resolution, the aspect ratio would be 2:1. To get this resolution, I set the ratio at 2:35:1 and the aspect ratio at 2:1.
In 14 bits it is not stable, but in 12 bits it is. And, after testing, I think I prefer to work in 12 bits rather than sacrifice some height.

lightspeed

  • New to the forum
  • *
  • Posts: 32
Re: Canon EOS M
« Reply #3504 on: September 27, 2019, 09:58:45 PM »
Not sure I understand the point of anamorphic mode. The resolution does not appear to be any better than 2.5k and in fact seems to look worse.

mix_vfx

  • New to the forum
  • *
  • Posts: 19
Re: Canon EOS M
« Reply #3505 on: September 28, 2019, 11:28:07 AM »
Not sure I understand the point of anamorphic mode. The resolution does not appear to be any better than 2.5k and in fact seems to look worse.

You get less crop. Almost full sensor width readout, and stellar resolutions when desqueezed.

henricusmaria

  • Freshman
  • **
  • Posts: 70
Re: Canon EOS M
« Reply #3506 on: September 28, 2019, 12:39:16 PM »
You get less crop. Almost full sensor width readout, and stellar resolutions when desqueezed.

Maybe he means it is less sharp..

masc

  • Contributor
  • Hero Member
  • *****
  • Posts: 1372
Re: Canon EOS M
« Reply #3507 on: September 28, 2019, 06:38:14 PM »
That is all off-topic here, but I'll answer anyway. Better asking such questions in the MLVApp thread!
2. Is there a faster way to convert ML RAW to ProRes 422 LT? MLVApp seems to be taking around 10 minutes for 30 seconds of video.
No. The rendering has to be done no matter which codec is selected. So the time will be the same. Fastest is when not changing an "Edit" area setting.

3. I noticed that it's a very big difference in file size between ProRes 422 & 422 LT with not that much disadvantages.
"Not that much", but there is a difference.

Also it seems that MLVApp doesn't care if you export 4K or 1080p, the export time for a 30 second clip is usually the same.
The rendering has to be done no matter which resolution is selected (original resolution is fastest). So the time will be similar.

Also MLVApp seems to freeze sometimes, a few times I exported 3 minute RAW clip and it just froze after 1.5 hours.
Please post into MLVApp thread, what you've done exactly to get MLVApp frozen. Best, if it is reproduceable.
5D2.212 | EOSM.202

turnlemons2lemonade

  • New to the forum
  • *
  • Posts: 16
Re: Canon EOS M
« Reply #3508 on: September 28, 2019, 06:47:57 PM »
Thanks for the clarifications masc, so pretty much this is the workflow at the moment. Appreciate it!

2blackbar

  • Member
  • ***
  • Posts: 225
Re: Canon EOS M
« Reply #3509 on: September 30, 2019, 05:23:23 PM »
My camera is crashing basically everytime i restart after filming is stoped, getting error 70.
crashlogs:
Code: [Select]
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_READOUTDONE_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:479, **INT-D9h**:1116c
lv:0 mode:3

CtrlSrv stack: 27bfb0 [1d9db8-1d5db8]
0x0009E558 @ 9e864:27bfb0

Magic Lantern version : Nightly.2019Sep24.EOSM202
Mercurial changeset   : 803005845230 (crop_rec_4k_mlv_snd_raw_only) tip
Built on 2019-09-24 12:27:24 UTC by daniel@Daniels-MacBook-Pro.local.
Free Memory  : 230K + 2583K
Code: [Select]
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_SETPARAM_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:462, **INT-E0h**:1112c
lv:1 mode:3

debug_task stack: 27bfb0 [1ebdf0-1e9df0]
0x0009E558 @ 9e864:27bfb0

Magic Lantern version : Nightly.2019Sep24.EOSM202
Mercurial changeset   : 803005845230 (crop_rec_4k_mlv_snd_raw_only) tip
Built on 2019-09-24 12:27:24 UTC by daniel@Daniels-MacBook-Pro.local.
Free Memory  : 229K + 2564K
Code: [Select]
ASSERT: !IS_ERROR( TryPostEvent( this->hTaskClass, this, EV_SETPARAM_INTERRUPT_EVF, NULL, 0 ) )
at ./Evf/EvfState.c:462, **INT-E0h**:1112c
lv:1 mode:3

debug_task stack: 27bfb0 [1ebdf0-1e9df0]
0x0009E558 @ 9e864:27bfb0

Magic Lantern version : Nightly.2019Sep24.EOSM202
Mercurial changeset   : 803005845230 (crop_rec_4k_mlv_snd_raw_only) tip
Built on 2019-09-24 12:27:24 UTC by daniel@Daniels-MacBook-Pro.local.
Free Memory  : 229K + 2565K

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5919
Re: Canon EOS M
« Reply #3510 on: September 30, 2019, 05:30:11 PM »
I need much more info if you want help. Preset used etc. Also try to reinstall. Maybe helps.
Are you using fps override?

mesebar2

  • New to the forum
  • *
  • Posts: 31
Re: Canon EOS M
« Reply #3511 on: September 30, 2019, 07:12:10 PM »
First of all, I'd like to thank you Danne for the amazing work you're doing.

I finally had the chance to try the new builds you created for the EOS M. They are so much fun, and the quality is absolutely incredible, and the 5K anamorphic rewired is brilliant.
I have used the September 24th build during the earth strike day, just to try it out quickly. And wow, the image quality I got using the MLVApp is just too good. And the focus pixels using your presets are just not there.
Thank you again for the work you and all the ML developers are doing!

I have a question and am wondering if any of you could help me.

Yesterday I had to literally run to quickly record something, and while doing so I disable the presets. Long story short, I manage to record the footage but instead of using:
5k anamorphic rewired, 1088x1632 10 bit lossless
I recorded anamorphic  1120x1680 14 bits lossless

As a result, I did manage to shoot what I needed but I'm not able to remove the focus pixels in MLVApp. Is there any way for me to get rid of them?
I searched in the forums but I don't think I found (or maybe understood) how to do it either in MLVApp or through mlv_dump.

If it can help, I uploaded the preset and non-preset samples below
https://we.tl/t-jgtbxyn9NJ

Thanks to anyone who has the patience to help me or point me in the right direction.

And thank you again, Danne, for the amazing work you're doing!


2blackbar

  • Member
  • ***
  • Posts: 225
Re: Canon EOS M
« Reply #3512 on: September 30, 2019, 07:29:54 PM »
yes im always using fps override to 23.976
I went back to build from last august.Too much trouble with new one.I might be the only one if people dont post anything about issues but i had to pull battery so many times and got error 70 over 10 times in a row. i pick mcm rewire from that new menu , then change to 12 bits , fps override , 16:9, not much else, digic sharpening on , white balance 5000, shutter 41, histogram on.Yeah it doesnt say anything i know.I also noticed that my recording times are much weaker now, i get 20 seconds max and it stops, but i could record for longer than that it started to happen since that new menu was introduced, but i like it so im on august 30.

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5919
Re: Canon EOS M
« Reply #3513 on: September 30, 2019, 08:56:16 PM »
It could be anything but I bet it's related to fps override in your case. If it's related to the build is hard to say but you are free to use whatever build you want so.

ZEEK

  • Member
  • ***
  • Posts: 148
Re: Canon EOS M
« Reply #3514 on: October 01, 2019, 12:54:08 AM »
As a result, I did manage to shoot what I needed but I'm not able to remove the focus pixels in MLVApp. Is there any way for me to get rid of them?
I searched in the forums but I don't think I found (or maybe understood) how to do it either in MLVApp or through mlv_dump.

You just download the focus pixel maps from the link below, unzip them and drag them onto the black screen on MLV App. If it's still there, 3x3 chroma smooth shouldn't hurt ;)
MASC Focus Pixel Tutorial Video found on this page towards the bottom:
https://www.magiclantern.fm/forum/index.php?topic=16054.675
Focus Pixel Maps Download:
https://www.youtube.com/redirect?q=https%3A%2F%2Fbitbucket.org%2Fdaniel_fort%2Fml-focus-pixels%2Fdownloads%2F&redir_token=XAGCeaNtGohw2MmJkXwYfOzsvPN8MTU2OTk3MDE3NEAxNTY5ODgzNzc0&v=zbOEAD9RfJ0&event=video_description
EOS M - EOS M2

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5919
Re: Canon EOS M
« Reply #3515 on: October 01, 2019, 06:06:19 AM »

mesebar2

  • New to the forum
  • *
  • Posts: 31
Re: Canon EOS M
« Reply #3516 on: October 01, 2019, 07:15:00 AM »
You just download the focus pixel maps from the link below, unzip them and drag them onto the black screen on MLV App. If it's still there, 3x3 chroma smooth shouldn't hurt ;)
MASC Focus Pixel Tutorial Video found on this page towards the bottom:
https://www.magiclantern.fm/forum/index.php?topic=16054.675
Focus Pixel Maps Download:
https://www.youtube.com/redirect?q=https%3A%2F%2Fbitbucket.org%2Fdaniel_fort%2Fml-focus-pixels%2Fdownloads%2F&redir_token=XAGCeaNtGohw2MmJkXwYfOzsvPN8MTU2OTk3MDE3NEAxNTY5ODgzNzc0&v=zbOEAD9RfJ0&event=video_description

Thank you so much, ZEEK!
I'll try and let you know if it worked as soon as I'll be back home.
Thank you again!

EDIT: Thanks ZEEK, it worked perfectly!!!

ngemu

  • New to the forum
  • *
  • Posts: 48
Re: Canon EOS M
« Reply #3517 on: October 01, 2019, 08:38:43 AM »
Absolutely loving the new aperture up and down custom buttons. Sometimes, clicking the buttons too fast or soon causes a glitch where the aperture shoots all the way up or down.

When it gets dark, i switch back to the iso custom buttons.

Makes shooting so much more enjoyable :)

Johnny Yul

  • New to the forum
  • *
  • Posts: 3
Re: Canon EOS M
« Reply #3518 on: October 01, 2019, 03:41:36 PM »
10bit raw is a great solution, but there is a problem, 10bit is linear right? so it does not contain enough data for mid tone and shadow area, worse than 10bit log (not raw file), i think it should be recorded in log profile, not in post-production in MLVApp (data has already lost at that time), it should be done within the progress something like cmos data to 10 bit.
i think 10bit log profiled raw is the perfect solution, it can replace 14bit linear raw in most cases, 10bit linear raw has a obvious gap to 14bit linear, especially when grading mid tone an dark area, mid tone is so important!

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5919
Re: Canon EOS M
« Reply #3519 on: October 01, 2019, 03:56:02 PM »
10bit raw is a great solution, but there is a problem, 10bit is linear right? so it does not contain enough data for mid tone and shadow area, worse than 10bit log (not raw file), i think it should be recorded in log profile, not in post-production in MLVApp (data has already lost at that time), it should be done within the progress something like cmos data to 10 bit.
i think 10bit log profiled raw is the perfect solution, it can replace 14bit linear raw in most cases, 10bit linear raw has a obvious gap to 14bit linear, especially when grading mid tone an dark area, mid tone is so important!
What is you point? 10bit is a compromise to get continuous recordings. If 12bit or 14bit works use that but we are talking eos m here. Not the most obvious cpu powerhorse  :-*

Johnny Yul

  • New to the forum
  • *
  • Posts: 3
Re: Canon EOS M
« Reply #3520 on: October 01, 2019, 04:07:00 PM »
What is you point? 10bit is a compromise to get continuous recordings. If 12bit or 14bit works use that but we are talking eos m here. Not the most obvious cpu powerhorse  :-*
thank you for your great job, first! i am using your build.
i mean current 10bit raw is linear, right? if it is log profied, it will be almost perfect, just within the progress down sampling to 10bit, i don't know whether the cpu can afford it (i use eosm too) , just a suggestion :)

Luther

  • Member
  • ***
  • Posts: 176
Re: Canon EOS M
« Reply #3521 on: October 01, 2019, 04:13:01 PM »
10bit raw is a great solution, but there is a problem, 10bit is linear right? so it does not contain enough data for mid tone and shadow area, worse than 10bit log (not raw file), i think it should be recorded in log profile, not in post-production in MLVApp (data has already lost at that time), it should be done within the progress something like cmos data to 10 bit.
i think 10bit log profiled raw is the perfect solution, it can replace 14bit linear raw in most cases, 10bit linear raw has a obvious gap to 14bit linear, especially when grading mid tone an dark area, mid tone is so important!
Raw data is raw data. There's no "log" in raw. I think you have a reading to do. As Danne said, you can use 12-14bit if you need more dynamic range.

Johnny Yul

  • New to the forum
  • *
  • Posts: 3
Re: Canon EOS M
« Reply #3522 on: October 01, 2019, 05:38:22 PM »
Raw data is raw data. There's no "log" in raw. I think you have a reading to do. As Danne said, you can use 12-14bit if you need more dynamic range.
raw data is also numbers array in memory (a kind of voltage value? ), number can of course be remapped by a non-linear function curve (such as log), just value modification, nothing else.
A log profiled data does not need special data or treatment, only the remapped value taking place of the original one, same size and structure as the original, the only thing need to do is to let the cpu remap the value when down sampling to 10 bit, it is a kind of tiny calculation, i wish cpu can afford it, although, it can already do the down sampling calculation, right?
Anyway, thanks to all the contributors :)

Danne

  • Contributor
  • Hero Member
  • *****
  • Posts: 5919
Re: Canon EOS M
« Reply #3523 on: October 01, 2019, 05:44:02 PM »
My bitdepth implementation is a crude, simple one. Lowering analog gain registers from around 400(14bit) and then to 12/10bit values. If there are other values to tweak I donĀ“t know how to do that. This modification was realized from an idea from Levas. Code in crop_rec.c:
Code: [Select]
            if (bitdepth == 0x3)
            {
                /* 10bit roundtrip only not applied here with following set ups */
                adtg_new[13] = (struct adtg_new) {6, 0x8882, 60 + reg_gain};
                adtg_new[14] = (struct adtg_new) {6, 0x8884, 60 + reg_gain};
                adtg_new[15] = (struct adtg_new) {6, 0x8886, 60 + reg_gain};
                adtg_new[16] = (struct adtg_new) {6, 0x8888, 60 + reg_gain};
            }
           
            if (bitdepth == 0x4)
            {
                /* 12bit roundtrip only not applied here with following set ups */
                adtg_new[13] = (struct adtg_new) {6, 0x8882, 250 + reg_gain};
                adtg_new[14] = (struct adtg_new) {6, 0x8884, 250 + reg_gain};
                adtg_new[15] = (struct adtg_new) {6, 0x8886, 250 + reg_gain};
                adtg_new[16] = (struct adtg_new) {6, 0x8888, 250 + reg_gain};
            }

Luther

  • Member
  • ***
  • Posts: 176
Re: Canon EOS M
« Reply #3524 on: October 01, 2019, 05:52:03 PM »
Not sure if I'm following you guys. Isn't ML just reducing the amount of possible tones per channel from 16.384 (14-bit) to 1024 (10-bit)? How could you apply "log" into this if it's an absolute value?