Messages

First time picking up the EOS M in years. Really impressed with the Crop Mood build

[Sandisk Extreme Pro SDXC 95MB/s V30 UHS-I U3 256GB]

Sandisk Extreme Pro SDXC 95MB/s V30 UHS-I U3 256GB

Benchmarked in the 5.2K 1x3 preset with 2.35:1 aspect ratio. Red and orange at 14 bit and dropped to 10 bit for green.

1) Max Red Speed: 85.17 MB/s
2) Max Orange Speed: 82.73 MB/s
3) Max Green Speed ("Continuous"): 72.45 MB/s

Which means my new Lexar 1TB card is about 8.78 MB/s faster than this one.

A quick test trying to find the green data rate when testing the above card with 2.8k/14bits results in about 78.87 MB/s which seems to imply the 1TB version of this card is slightly slower than the 256GB version.

[Lexar Silver Plus mSDXC UHS-I 1TB]

I conducted the max data rate benchmark (green, orange, red) as suggested by gabriielangel.

Like gabriielangel I used a variable ND filter. However I chose to do the benchmarks in the 5.2K 1x3 preset with 2.35:1 aspect ratio. All tests were done in 14 bits.

I used the magiclantern-crop_mood.2024Feb19_Custom.EOSM202 by danne for my tests.

The results for the Lexar Silver Plus mSDXC UHS-I 1TB R205/W150 are as follows (using 240MHz / SDR50).

1) Max Red Speed: 93.49 MB/s
2) Max Orange Speed: 91.43 MB/s
3) Max Green Speed ("Continuous"): 81.75 MB/s

These results are a bit lower then the ones gabriielangel posted for the Lexar Silver Plus mSDXC UHS-I 256GB when testing 2.8k/14bits.

With these max speeds as baseline I tested a few settings to see if they impact the max data rate. I did not find these settings to impact recording times:

- Sound Recording (On/Off or lowering sampling rate)
- Shutter fine tuning (to achieve 180 degree shutter)
- Powersave in LiveView -> Dim display -> after 5sec

I was surprised regarding sound not having an impact... When disabling sound I was not able to improve on the previously established red/orange/green baseline. Disabling sound did not allow me to increase exposure and still meet the requirements to meet the red/orange/green benchmark.

My test with shutter fine tuning enabled (and compensating for the difference in exposure) would match the baseline. Same exposure value as measured by the histogram before and after enabling shutter fine tuning would satisfy the red/orange/green requirements.

[Speed Test: Lexar Silver Plus mSDXC UHS-I 1TB]

Speed Test: Lexar Silver Plus mSDXC UHS-I 1TB
R205/W150
096985-V30-01TBS A (written behind the card)
240MHz / SDR50 (Won't work with SDR104)

Code Select Expand

Preset: 5.2K
Aspect Ratio: 2.35:1
Framerate: 23.976 FPS
Bit-depth: 12bit
I also lowered the audio sampling rate to 11025 kHz.
Scene slightly overexposed.



Was able to get over 3.5 minutes of recording @ 89.63MB/s (green) until I manually stopped recording.



Recording initially went red.


Then orange.


Eventually green.


Still overexposed when I stopped recording (cam does warm up from all the testing though).


Highest data rate I've encountered is 104.06 MB/s (a 'burst' of 87 frames).

All in all I think this is a great card

[Speed Test: Lexar Silver Plus mSDXC UHS-I 1TB]

Speed Test: Lexar Silver Plus mSDXC UHS-I 1TB
R205/W150
096985-V30-01TBS A (written behind the card)
240MHz / SDR50 (Won't work with SDR104)

Tried the same settings as eosy:

Code Select Expand

Preset: 4.2K
Aspect Ratio: 16:9
Framerate: 23.976 FPS
Bit-depth: 14bit
I also lowered the audio sampling rate to 11025 kHz.

Was able to get 2 minutes of recording @ 91.71MB/s (orange) until it stopped recording.



On a second take (with a less complex scene?) I manually stopped recording after about 6 minutes @ 89.42 MB/s (orange).

Looking forward to try this on my MBP M2 Max!

Then, pressing the shutter halfway (Be careful not to push it too far!) will toggle x10 Zoom on off.
If you press it all the way in, it may take a photo, but sometimes it freezes the camera. So you need to pull the battery and restart it.

EDIT: I remember what I did to stop that annoyance:
Go to the Canon Menu
In the 5th tab
Set Video snapshot to: ENABLE
From now on, when in Video mode, the full Shutter Button won't work at all.
And it will work as usual in Photo Mode.
No Video Snapshot seems to be recorded on the card.
I haven't tested if it affects performance though. Let me know.

Does anyone know another workaround which prevents taking a picture when fully pressing the shutter button? Unfortunately the tip from gabriielangel didn't work for me.

Apart from that I'm super impressed with Crop mood! And I really like Dannes custom tweaks, especially the ISO adjustments with up/down keys and the INFO button for 10x zoom

Also, it is preferable not to use shutter fine-tuning.

Why is this preferable? Looks like since this update the shutter fine-tuning has been fixed and I don't see the shutter fine-tuning in the post you link to.

You can read about the Data Rate impact of certain settings in this post.

These are my current full settings:

Code Select Expand

- 1736x2214 23,976fps 1.61 crop (Full sensor width)
- Shutter range: Full range
- 180 degree shutter rule (1/47.96 via Shutter fine-tuning -0.35ms).
- 12-bit lossless raw video (can store up to 12 stops of dynamic range, camera is capable of 12.4 stops DR. Step up to 14-bit when required (but will lower recording times). Underexpose to get longer recording times. ["If you need to underexpose by 2 Stops or more to get a low enough Data Rate, it is preferable to select the next lower bit depth"](https://www.magiclantern.fm/forum/index.php?topic=27162.0)
- Aspect Ratio: 2.35:1
- Kill Global Draw: ON
- Small hacks: More
- Sound recording: 11kHz (as a sync track when recording sound externally or syncing to music) or 48kHz when recording sound internally (higher kHz will lower recording times). 8kHz seems to freeze the cam after recording for 7 seconds.
- Movie Tweaks -> Shutter Lock: ON
- LV DIGIC peaking: Slightly sharper
- Advanced settings: Kill Canon GUI -> Idle/Menus
- HDMI output: ON -> Output resolution: 1080i 60Hz
- Customize buttons -> Half-Shutter: Zoom x10
- SD Overclock: 240MHz (H)
- Zebras: OFF
- Spotmeter: OFF

 

Canon menu settings:

- Image Quality: RAW
- Grid display: Off
- Histogram display: Disable
- Image review: Off
- AF method: FlexiZoneAF()
- Focus mode: MF
- Image Stabilizer: Enable
- Exposure comp.: 0
- ISO speed: 100
- Auto Lighting Optimizer: Off
- Metering timer: 16 sec.
- [Picture Style](https://www.magiclantern.fm/forum/index.php?topic=27162.0): User Def. 1 (Neutral: Sharpness 7, Contrast 0, Saturation 0, Color tone 0)
- Movie rec. size: 1920x1080 24
- Sound recording: Auto
- Video snapshot: Disable
- Movie Servo AF: Disable
- AF w shutter button during recording: OFF
- Ctrl over HDMI: Disable
- File numbering: Continuous
- LCD auto off: 10 min.
- Camera auto off: 10 min.
- LCD brightness: max
- Video system: PAL
- Beep: Disable


I think I was able to confirm your findings.

I did my own experiment using DaVinci Resolve and indeed I see no difference when rendering a 5208x2214 timeline to 3840x1632 compared to rendering a 3006x1278 timeline to 3840x1632. And the result improves when rendering the 3006x1278 timeline to 3840x1632 with Super Scale 2x enabled with sharpening set to medium and noise reduction set to low. Using the 2x Enhanced Super Scale option seems to result in even more detail.

I've uploaded my samples on Dropbox.

Very informative! I'm ordering the 1TB Lexar Silver Plus Micro SD Card to see how it performs.

The result is equal or superior to going from the native resolution directly to 4k without AI. Why?
[...]
In order to keep the same amount of captured pixels and the same aspect ratio, the actual native size of the 5.2k preset should be 3008x1258 (3.78 megapixels).
[...]
I think it would be advisable to always work and distribute at, or below the native capture resolution and use a suitable upscaling program when needed.

I'm not sure I follow the conclusion here. I'm primarily interested in the 1x3 1736x2178 recording option. Are you saying you get better results when you desqueeze and downscale to 1920x803 (making the input resolution AI model friendly but throwing away actually recorded details in the process) and then upscale with AI to 3840x1606?

Would be interesting to see a comparison between directly scaling to 3840x1606 and downscaling to 1920x803 and then back up to 3840x1606 with DaVinci Resolve 2x Super Scale.

I tried to use this module on my EOS M with latest crop mood in the hope I'd be able to make the Accsoon SeeMo 4K accept the HDMI signal. Turns out the SeeMo 4K (basically an HDMI capture card for iOS devices) expects at least 1080p 60FPS so I wasn't able to make it work. I also tried the hdmi_out.mo included with the crop mood build. That one did work better, in the sense that I was able to get 1080 output over HDMI to a PC monitor. But it still didn't work with the SeeMo (probably because it can't handle the interlaced signal). Turns out I should have bought a dedicated field monitor instead of the SeeMo. Posting to prevent people from making the same mistake as I did.

Good news is that some zoom lenses have bigger circle of confusion than usual when zoomed in, i have one where wide angle 4mm covers 16mm frame and when you zoom in to 12mm then it almost covers micro 4/3.I suspect a lot of zoom lenses work like this but not all of them, i have also krasnogorsk 3 lens but it works totally different and its hard to get focus because it needs to be exactly distanced from sensor or it wont work.

Which lens is that? Covering a 16mm frame at 4mm foals length would still make it a very wide lens on the 2.8k mode

This is awesome!

Very much looking forward to properly try this out.

I did some crop factor calculations for different modes, to see how they compare relative to the width of a full frame sensor.

4.61x (1.6 * 2.88) in mv1080 x3crop 1800px wide
3.29x (1.6 * 2.06) in 2.5k @ 2.35:1
2.96x (1.6 * 1.85) in 2.8k @ 2.35:1

The 2.8k crop is a good match with lenses for Super16 sensors, since Super16 is 2.88x crop relative to full frame sensor width. This 2.8k mode comes really close to the Blackmagic Pocket Cinema Camera in terms of field of view.

EOS M sensor size: 22.3 x 14.9 mm
EOS M sensor width: 5184px

From my quick testing I conclude that the 2.8k mode has THE perfect crop factor for my Kiev 16U lenses! The Mir-11 12.5mm F2 (Kiev 16U lens) is used to it's max area without heavy vignetting, resulting in approximately a 43mm focal length relative to full frame.

SanDisk 64gb 170 MB/s Low Level Format @ 160mhz


SanDisk 64gb 170 MB/s Low Level Format @ 192mhz


SanDisk 64gb 170 MB/s Low Level Format @ 240mhz


SanDisk 64gb 170 MB/s Low Level Format @ Overclock Off


Interestingly the fastest speed I've seen was with 240mhz. Other than that, both of my cards (SanDisk 64gb 170 MB/s and SanDisk 256gb 95 MB/s) are responding the same to the overclock settings.

Awesome stuff! Did some benchmarks with my 95 MB/s card, but it works best with 192mhz. So 192mhz is not only for the 170MB/s cards.

SanDisk 256gb 95 MB/s Low Level Format @ 160mhz - Test 1


SanDisk 256gb 95 MB/s Low Level Format @ 160mhz - Test 2


SanDisk 256gb 95 MB/s Low Level Format @ 192mhz


SanDisk 256gb 95 MB/s Low Level Format @ 240mhz


SanDisk 256gb 95 MB/s Low Level Format @ Overclock Off


I've got a 64GB 170MB/s card too. Will report benchmarks from that one later.

Could be added. But iso will stay at 100 until aperture is all the way open. So basically when you want to shoot at iso 100 outdoor you'll only be changing aperture when using the existing iso + aperture hot keys.

[Presets]

Presets
These have already been introduced but I would suggest different (simple) names perhaps? Like:
- 1080 HD (16:9)
- 1080 HD 48fps...
- 1080 Wide (2:1)
- 2.5K ??
etc..

I think you have some good suggestions. One of the first things I did when working on the menu, is experiment with more universal preset names (what it does, instead of how it does it from a ML implementation perspective). I still think it could be nice, but after some talks with Danne I'm also fine with the names as they are right. At least now they're consistent across both preset sections.

And why is the "mv1080p MCM rewire" widescreen? Why does the "Mv1080 1736x976" have a ratio of 2.39:1? (though it doesn't show). Why are the start off presets different from the regular presets?..

The start off presets have their settings maximised while still allowing continuous recording. It's supposed to be an easy, no fuss way, of getting all the settings right (upper limit) for a specific recording mode (preset) without having to worry about which combinations of settings would still allow continuous recording. Therefore the "mv1080p MCM rewire" is widescreen and 14 bit. It can still record continuous at those settings. But in 2.5k or anamorphic 14 bit 16:9 won't get you much time at all, so it's defaults to lower bitrate and narrower ratio. Of course you can still drop the bitrate or make the ratio in "mv1080p MCM rewire" wider after applying the preset, but it's supposed to be a sensible default 'base'.

We're working on making the menu better, but I think we must embrace the fact that there'll always be questions, no matter how we make the menu. I don't think we should make different startup modes for Simple, Intermediate and Advanced usage. I think ML users are curious people. So if it defaults to a 'Simple' mode, people want to see what's possible in 'Intermediate' or 'Advanced' and will have questions. Also it will be a lot of work to make this, and I don't think it will result in more clarity and less questions.

What did help me a lot when just starting out with ML on EOS M are the video's from ZEEK! Even better than PDF documentation if you ask me

Veerle, you could if you like take a look at the Cine.lua script from Danne. It's actually very easy to make a couple of scripts with custom presets and naming like you suggest.

Thanks Danne and Jip-Hop!

That Gain/Aperture adjustment is sweet!

Edit: just tried the Gain/Aperture adustment, when I press down I come into the Canon iso menu. What am I doing wrong?
Also when enabling AF, autofocus doesn't work that great anymore in mcmrewire mode.

Can you check if you have set the down button to ISO setting in Canon menu? I think that setting is in the yellow menu somewhere.

I came across a black sun fix in DaVinci Resolve if I remember correctly. Maybe Google that?

I was using vintage M42 lenses on Viltrox speedbooster. Sorry can't be of much help for the next two weeks. Don't have my camera with me either starting today.

Tried latest build today. Can't do extensive testing from my vacation, also won't have access to computer for two weeks so only briefly played back some recordings in camera. Noticed some pink frames but not too many.

Noticed camera freezing quite a lot with 4k rewire preset and the 10x focus helper on half shutter press. Both standard and dark mode. Had to disable the feature. Seems to work much better in 2.5k mode.

Also had the camera get stuck on shutdown a few times. Would be stuck at sensor cleaning and only opening the battery door would actually shut it down.

That's how it works I think! Lower shutter speed, lower fps. Not auto iso for sure 

By the way how do you post process auto iso recordings? I read that the transition looks smooth on screen while recording but isn't smooth when playing back in DaVinci Resolve.

There's something else with eosm sharing trash can with pressing down. Not sure buttons are "longpress" sensitive.

I think you can find which keys are long press sensitive in the Lua api docs: https://builds.magiclantern.fm/lua_api/modules/constants.html#KEY

Keys that have the unpress state can be used for long press.

Hi garry23,

I'm using flags already and I'm aware I shouldn't return false always, but for this simple example I return false for all keys just to be clear that no keys should be handled as normal (they should all be blocked). Makes it all the more obvious when a key slips through.

From Lua api docs: "Event handlers will not run if there's already a script or another event handler actively executing at the same time."

This is a big problem for what I'm trying to do. If I double press the play key, I call a function to switch raw video preset and refresh live view. This apparently keeps the camera busy (it's actively executing a script). Therefore the key press event handler won't run the third time I press play, and the default action isn't prevented. Now the camera tries to go into play mode while still switching raw video presets and refreshing live view. This causes conflicts and partially locks up the camera.

So with a double press and a few seconds of patience it works fine, but if I accidentally triple press I lock up the camera and need to reboot or switch modes.

Conclusion: Until there's a reliable way to prevent the default action of a key I can't make this work.

Still curious if using task.create with a high priority would make a difference. But I still haven't figured out how to specify the priority...