Crop mood - WYSIWYG Edition (650D / 700D / EOS M / EOS M2 / 100D)

[Danne]

Probably need some refining same as with regular eos m.

[eosy]

On my EOS M2, SD card seems to write about 70MB/s.

small hack disabled: approx. 70MB/s
small hack enabled: approx. 74MB/s

I used these two SD cards and the benchmark results were very similar.
Let me know if you need more detailed information.

[SanDisk Extreme PRO (2022)]
256GB
SDSDXXD-256G-GHJIN

[Samsung EVO Plus (2021)]
512GB
MB-MC512KA/EC

[Walter Schulz]

If you check card's root you will find files named BENCHx.PPM. Number will get increased with each benchmark run. You can convert it to PNG/JPEG, upload it somewhere and link it here.
I think you haven't pressed PLAY button after benchmark which will force card into "PLAY-UNK" (-PH, MV) mode. Restart cam in photo mode and redo benchmark run. Samsung will show 90+ write rate.

[eosy]

Thanks. I guess I didn't read the description of the benchmark module. Moreover,
I thought "malloc error" would always appear.

After starting the benchmark, I pressed the Play button and was able to confirm that both "Sandisk Extreme Pro", "Samsung Evo Plus" exceeded 90MB/s.

-----
However, I have one question. The description of the benchmark module says "Movie mode or in Play mode".

I first ran the benchmark with EOS M2 in Movie mode and got a result of 74 MB/s. (Global Draw is disabled.)

Then, as per your instructions, Restart cam in photo mode and redo benchmark run, I get over 90MB/s.

In other words, it is fast in photo mode but slow in movie mode. In fact, when I shoot RAW video with Crop mood enabled, the indicator turns orange or red at 70MB/s and stops frequently.

Is there any information or setting I am missing?

(This image was taken in Photo mode when 94 MB/s was measured by pressing the Play button after starting.)
https://x.com/hassyX/status/1811631272852357513

[Walter Schulz]

Take it with a grain of salt...

In builds without Bilal's enhancements to SD_UHS.mo the following rule of thumb applies:
Benchmark in photo mode tells about physical restrictions. More or less answers the question what cam's hardware can do with a given card type.
Benchmark in video mode is close to actual write performance for real life recording.

In builds with Bilal's enhancements benchmark in video mode is kind of obsolete (IMO).
You can take benchmark numbers from photo mode and decrease them by 11-13 MByte/s overhead to get real life limits.
(This may apply to M, 650D, 700D only. Haven't tested 100D, M2 thoroughly yet. They are slighty different.)

This change in behaviour has not been documented yet.

EDIT: Did some short tests with M2. Got 4:01 with 76.8 MByte/s before cam stopped itself. This is 4-6 MByte/s slower than 650D. Not that bad.

[theBilalFakhouri]

By the way, I noticed that when I shoot RAW video with the following settings, the bottom scan line turns white.
I am attaching the image.
..
[Crop mood 2.5K 1:1 crop]
Preset: 2.5K
..
[RAW video]
Resolution: 2520x1082

Thanks for reporting, will fix in next release, resolution should be 2520x1080 in this preset not 2520x1082.

[Walter Schulz]

Well, thread in discord was auto-deleted. So I put it here, too:

Crop M2ood build issues:

1.) Taking RAW pics in photo mode is accompanied by "Raw error. Falling back to YUV overlays"
2.) Silent.mo: Full res silent pic (FRSP) buggy. Standard trigger method "Half-shutter" may work or not. Most of the time half-trigger will force cam to do a non-silent pic. Even very short half-shutter presses may do so.
Tested half-shutter. Not a hardware issue with this cam.
3.) Selftest.mo: Cam takes a few shots (2-3, I think) and stays in recording mode doing nothing else.

[names_are_hard]

This thread? https://discord.com/channels/671072748985909258/1258303113069199360

I think they get deleted after some long time with no activity but to start with it just hides them (you can find them with search).

[doktorkrek]

Thank you @theBilalFakhouri for the great work on the M2 build, works well on my device!

How should one create the focus pixel maps on M2? Should one just inspect the footage and locate them there, or do we know something about their positions? Bilal says M2 "shares the same sensor as in 100D", can 100D pixel maps be used, after accounting for the crop?

I have found only this mirror of a repo with code that generates focus pixel maps for different models based on the discovered focus pixel patterns, but it's unclear if it works for the newer crop_mood presets:
https://github.com/bouncyball-git/mlv-tools

[DylanAWRoberts]

I seem to be having an issue on my 700d once I've made a raw recording and then go to film again it just cuts out and won't allow me to record again untill I cycle between photo and video mode any clues anyone?

[itx]

Hello, i have a trouble loading crop mood in M2.

appears text like this in a box:

Locking cache
Lens moving (22,0)
Error loading `ML/MODULES/EOSM2_103.sym` : File does not exist
updating Movie Tweaks -> Movie Logging
updating Movie Tweaks -> Time Indicator

any solution?

[Walter Schulz]

Hello, i have a trouble loading crop mood in M2.

appears text like this in a box:

Locking cache
Lens moving (22,0)
Error loading `ML/MODULES/EOSM2_103.sym` : File does not exist

Make sure to have extracted zip and copied *all* files and directories/folders to card. Esp. check \ML\Modules\EOSM2_103.sym
If file exists it is likely your card is not compatible with selected overclocking mode and cam lost connection to card completely.
In this case delete contents in ML\SETTINGS and try to work without overclocking first. Then try lowest overclocking setting (160 MHz) and run benchmark:
1) Access Modules tab and activate bench.mo
2) Restart cam
3) Access Debug tab -> Benchmarks -> Card benchmarks -> Quick R/W benchmark (1 min) 
4) Start benchmark and press PLAY button after benchmark screen appears.
Results: If numbers are around 20 MByte/s your cam dropped transfer speed to failsafe mode. Means: Incompatible with selected mode.
Work your way up to higher frequencies. Most likely it will fail and at least fail for 240 MHz.

Also check list of "known-good" cards: https://wiki.magiclantern.fm/cards_240mhz

[Walter Schulz]

I uninstalled it and tried to install of the crop mood builds off the download link on the first page but file cannot be found.

https://bitbucket.org/bilal_fakhouri/crop-mood-builds/downloads/magiclantern-crop_mood.2023Aug19.650D104.zip

[anto]

Hi guys, for the first time I have a problem with the M. when I turn on the camera the led star to flash with green light and nothing happen.

I tried different batteries, sd card (also without), change lenses.. works normally till some days ago

[Walter Schulz]

Remove battery, remove card.
Insert battery.
Try to startup using Power button.
Results?

Remove battery.
Insert battery.
Try to startup pressing PLAY button.
Results?

[anto]

tried both, nothing

[Walter Schulz]

Join our Discord server invite and open a thread in "Magic Lantern Community" -> #unbricking-and-diagnosis.

[anto]

I think the problem was the sd card (lexar silver plus)
I tried another sd card where ML version for eos M is already installed, and the camera starts normally.

I use the lexar some days ago to backup PS4 files, then erase on mac (exfat) and put ml files. Tried many times to erase but maybe needs some other passage.

[Walter Schulz]

Format card in PC.
Insert card into cam and format again.
Insert card into PC and copy extracted build content to card.
Insert card into cam and run firmware update (=ML installation) again.

[anto]

Format card in PC.
Insert card into cam and format again.
Insert card into PC and copy extracted build content to card.
Insert card into cam and run firmware update (=ML installation) again.

card fomatted in PC, but when put it in the card the problema is the same

its just the card... two days ago I just needed to backup some files from PS4, and to use it I had to format the card with ps4. then the problem arrived

[Walter Schulz]

Try this formatter: https://www.sdcard.org/downloads/formatter/

There is another trick to test if this fails.

[anto]

Solved, thank you

wait... I formatted again with my MAC and now doesn't work again. I'll try again with PC a longer formatting

[names_are_hard]

Solved, thank you

wait... I formatted again with my MAC and now doesn't work again. I'll try again with PC a longer formatting

This is probably a known bug with MacOS.  It creates invalid exfat disks.
https://www.magiclantern.fm/forum/index.php?topic=25656.0

[anto]

This is probably a known bug with MacOS.  It creates invalid exfat disks.
https://www.magiclantern.fm/forum/index.php?topic=25656.0

ok... so I've to use W di format this card.
the first time I've test the card I reached 90 MB/s in recording with the camera green and orange. Now max recording its 82 Mb. In bech the results was the same 102 writing and 86 reading.

[Walter Schulz]

ok... so I've to use W di format this card.

I suppose "W di" means Windows and you don't have to use Windows only. The problem is with directories/folders created by macOS if file system is ExFAT.

SDXC cards formated in cam will get ExFAT.

If you are using macOS you have to follow this procedure:
- Format card in PC but apply FAT32 file system.
- Then copy ML files to card.
- Run firmware update to install ML. This will make card bootable and this is a requirement to run ML.
- After installation format card in cam with default option "Keep ML".
-> Cam will format card with ExFAT option and directories/folders are recreated with correct properties.

Again: The problem are directories/folder created by macOS with card having ExFAT.

the first time I've test the card I reached 90 MB/s in recording with the camera green and orange. Now max recording its 82 Mb. In bech the results was the same 102 writing and 86 reading.

It would help to tell the card you are using.
82 MByte/s is a proper write rate for SanDisk Extreme Pro and Samsung EVO Plus.
90 MByte/s continuous data rate may be possible with some Lexar.

But format card in cam first and retry.