Danne's crop_rec_4k experiments for EOS M

[critix]

For firmware version 2.0.3:
https://bitbucket.org/ccritix/magic-lantern/downloads/magiclantern-Nightly.2020May17.EOSM203.zip
This is the latest version of Danne, but for 2.0.3:
https://bitbucket.org/ccritix/magic-lantern/branch/crop_rec_4k_mlv_snd_raw_only

[roogii]

Is it possible to shift the position of the 3x crop mode anywhere on the sensor? I have a schneider 6-66  super 8 lens that doesn't cover even the 4.6x crop, for some reason I'm not central in the image circle though.

[Danne]

Check post the recent two months. A user did just that.

[2blackbar]

That super 8 lens might cover 3x crop mode on 66mm range, maybe not in 1920x1080 , maybe in 720x*** mode , i did not tried any super8mm lenses because they obviously wont cover full area , you need cctv lens for 1/2'' sensor at least or 16mm film camera lenses.
I do have personalised ML build for canon M with centered mode for my cctv lens BUT, i have 2 adapters for CCTV mount(c mount) and one is slightly shifted , other is centered more ( or vice versa) so not all adapters are equal.With that being said you still can do micro adjustments to crop by moving i left/right with arrows onscreen in 2.5k mode which helps in some cases.

[tomcarrolls]

Hi guys! So my EOS M is doing great with 10 bit Raw, unless I record with an external monitor, then this happens (purple artifacting, screen tearing): https://drive.google.com/file/d/1ijDakNgj66t5jPWaaaI2wCg5DEqXyoaF/view?usp=sharing

I tried turning on VGA mode or whatever it's called, no luck. Will try turning off histogram and other overlays, see if that helps.

[tomcarrolls]

Okay the only way I could get it to work well was to switch my in camera FPS to 24. It was on 30 before this. I think that was the problem.

[roofusj]

Hi everyone. I have a problem using canon eosm and magic lantern latest BUILD "crop_rec_4k_mlv_snd_raw_only_2019Dec08.EOSM202"
I am using lexar 128gb 1667x sdxc memory cards.
When i am trying to shoot raw videos 2.5k or even 1920*1080 camera doesn't record a video it stops every time at the beginning because of the high bitrate > card seems to be isnt able to record a bitrate higher than 16 m/s. But after a several attempts to shoot at the speed 16-20 m/s card starts to record a higher bitrate about 45-50m/s but never at the beginning. Does anybody has this issue with eosm and lexar or other cards? Thanks for answers!

I'm using a Lexar 1667x 64 gb V60 card and i have similar behaviors from it. At first it won't record more than 3 or so seconds in 5k rewire mode. Then after 3 or 4 failed attempts it starts recording just fine and as long as i don't turn it off it will keep going like a champ almost getting to 60 MB/s with constant recording. It works fine in mcm rewire.

[Mythic Cinema]

https://www.youtube.com/watch?v=jdbsgCFvWo0

I really like the look of that lens flare on that lens.

[alexeym]

I'm using a Lexar 1667x 64 gb V60 card and i have similar behaviors from it. At first it won't record more than 3 or so seconds in 5k rewire mode. Then after 3 or 4 failed attempts it starts recording just fine and as long as i don't turn it off it will keep going like a champ almost getting to 60 MB/s with constant recording. It works fine in mcm rewire.

Just about a week ago I tried Lexar (I think it was 1800x or something very similar to yours) and experienced exactly the same behavior.
A bit of remedy was to use "Warm up card" option in menu. I think 256MB size worked for me.
It improved the issue a lot, but occasionally the card was still not able to start recording at higher speed. Also boot up time was much longer due to "Warm up" setting.
I also tried Samsung Evo with very similar issues.
Eventually I returned the card and ordered Sandisk Extreme Pro 128GB. Never had the issue since.

On a side note. It seems to me in 5K mode, 12 bit changes resolution. 14 or 10bits have different one. Is it a bug or I'm still missing something after reading this whole thread.

[Danne]

On a side note. It seems to me in 5K mode, 12 bit changes resolution. 14 or 10bits have different one. Is it a bug or I'm still missing something after reading this whole thread.

Changes to keep continuous recording.

[rh224]

Just about a week ago I tried Lexar (I think it was 1800x or something very similar to yours) and experienced exactly the same behavior.
A bit of remedy was to use "Warm up card" option in menu. I think 256MB size worked for me.
It improved the issue a lot, but occasionally the card was still not able to start recording at higher speed. Also boot up time was much longer due to "Warm up" setting.
I also tried Samsung Evo with very similar issues.
Eventually I returned the card and ordered Sandisk Extreme Pro 128GB. Never had the issue since.

I just experienced similar issues with one of my Samsung Evo cards and my M for the first time today. They've been rock steady for continuous recording in 14/12bit when used with both my M and my 6D (Use MCMRewire @ 1736 x 976 on the M). Today, it recorded two clips of about 2:30 on the M just fine and afterwards 5 out of about every 6 runs would give me a max record time of 4-5 seconds (even dropping to 1600 x 900 @ 10bit) and randomly I'd get rock solid continuous recording. Power off/on, pull battery, reset ML settings, reset camera settings, turn on Card Warm Up, no difference or pattern I could see.

It was a family outing and I hadn't planned to shoot much at and just happened to have the M and card with ML, so I couldn't do much testing. I plan to do some more troubleshooting when I have time  It's possible the card is going bad, but it's probably only the 4th or 5th time I've used it. I should probably just quit being stubborn and buy some Sandisk cards...

Also, I've got two Lexar 64GB 1000x cards that have never worked right in my M with the SD overclock.  They work very well when used with my 6D however. Never figured out why.

P.S. This is my first post here, though I'm no stranger to ML.  Long time listener, first time caller sort of deal... I can't post with out a shout out to the community here and the incredible knowledge, talent and accomplishments pushing the limits of what this amazing little camera can do. Thank You!

[Capsulepill]

i'm having some trouble with the latest version of dannes ML build for eos m (JAN-18-2020). i'm pretty new to using magic lantern.
but everytime i try and press the rec button to start a video recording, it doesn't do anything, the last build i used allowed me to use the trigger. but the newest build doesn't, or i'm not aware of the setting to put it on.

i don't know if i'm doing something wrong, but if anyone could help i would appreciate it!

[UPDATE] I figured it out guys haha. if your also having the same kind of trouble that i wrote down here
in order to fix it, you have to go to the canon functions menu, and In Custom function menu: C.Fn-7 Release shutter without lense: on

this allows you to use lenses not recognised by canon camera systems, like the vintage lenses im using.

[Bernie54]

How to use Manual mode and JPG on EOS M with magiclantern-Nightly.2018Jul03.EOSM202?
When using this build on EOS M with FW 2.0.2 JPG-shooting in M mode is disabled if modules are loaded but switched off.

Issue description:
When cam is set to M mode and shutter is pressed half, the display is cleared and the ML message "Set picture quality to RAW" appears. When shutter is pressed full no shoot is taken and cam returns to default display. If mode is set to RAW a silent full res picture is taken - even if this is set to OFF - and the cam hangs up and must be restarted. Only if ML is loaded without modules the cam works like expected.

Used ML settings:
Serveral modules like adv_int, file_man, mvl_lite, silent, ... are loaded but all ML functions are set to OFF, except some overlays .

Expected behavior:
Just shoot JPGs in manual mode when modules are loaded but the corresponding functions are set to OFF.

Any hint is appreciated.

[cmh]

It's probably the same shutter bug that I got my silver EOS M. Try turning it off and on two or three time real quick (while the led blink right before the display is on).

[Bernie54]

@cmh: Thank's for the reply.

Meanwhile I got rid of the issue with a fresh reinstall of magiclantern-Nightly.2018Jul03.EOSM202 to the SD card.
Because I had tested another very experimental build on the same SD card before, my assumption is that some config stuff was left over that conflicts with the nightly build. But I don't have a proof for that and the shutter bug thing might be a root cause too.

[ArchGalileu]

 Hello all

Great work Danne

In 5k anamorphic I can't see the overexposed zebras, any advice?

Best regards
ArchGalileu

[Danne]

Not really. Turned them on? I have zebras turned off upon first install of magic lantern.

[keel]

Can I get a quick breakdown on "rewire".

Specifically this 5k vs 5k rewire, or more info on rewire in general.

I assume both are strictly for anamorphic lenses.

[Danne]

Start readig from the download post. It is expected for newcomers.

[roogii]

context: my preferred mode is mv1080p MCM rewire x3 crop, 1736x1158 max resolution 3:2. The full aps sensor rainbow aliasing is too much, and I have perfect alias free 5D3 for big sensor stuff anyway. I like having proper real time preview of the real framing. I treat the MagicM as my 100£ ikonoskop, incredible.

Danne:
1. is it only your build that gets the increase in vertical resolution in mv1080p MCM rewire 1158px vs 1024px in the main website build?
2. in mv1080pMCMrewire x3crop, is it 1:1 pixel sensor readout without any skipping/ binning?
3. if i enter 2.5k mode and set 1736x1158, am i theoretically getting exactly the same output as mv1080p set at 1736x1158 x3crop?
4. what is the difference between 2.5k 1:1 centred mode and 2.5k 2520x1418 >> is it just extra vertical available pixels otherwise the same?
5. if mv1080pMCMrewire x3 crop is 1:1 sensor just like 2.5k mode, is there anything stopping increasing the resolution of the x3 crop within the mv1080 mode whilst retaining realtime full framing preview?
6. I also use your 5d3 build, i like using the same full 3:2 1080p mode, and if i setup clear overlays at halfshutter for example, the magic lantern bars disappear and I get full 3:2 realtime preview. On the M the magic lantern bars disappear leaving black bars in its place, with a 16:9 preview still. Am i right in thinking that the 5d3 actually uses a 3:2 preview through the buffer whereas the M is streaming a 16:9 native preview? or would it be possible to clear the overlays on the M to reveal a 3:2 liveview.

2blackbars >> is that you synthsundry? So you enjoy C lens too, did you play around with moving the framing in the standard mv1080pMCMreire x3 crop mode?

Oh...Danne, I have four of these M cameras and I assume there must be some kind of hardware variation, because using all same settings and build in mv1080MCMrewire, 2/4 of my bodies corrupt the image when changing into x3 crop, video >>>

[Danne]

I think your glitch is fps related. Either canon fps mode or fps override or set 25 fps is enabled causing the issue in x3 crop.

[keel]

Anyone ?

[Danne]

Anyone ?

Try back track a few pages. If you pay attention you´ll soon see that there´s a download post referred to on a regular basis. Find that page and start reading from that post and onwards. Most of your questions will be answered really fast.
You don´t mention any info about what build you are using or where you found it? Sources needed.

[roogii]

Ok that got it, so that's what set 25fps is for - matching the Canon menu.  The 2 other bodies are fine being mismatch set though.

Other questions too boring? I read the whole thread,    those questions didn't seem answered at least on my passing and in my head.

[Danne]

Ok that got it, so that's what set 25fps is for - matching the Canon menu.  The 2 other bodies are fine being mismatch set though.

Set 25fps is not to match canon menu.