Messages

I also think you should set your project to a standard resolution, like 5k or 6k, because I think you might risk degrading the quality of your uploaded videos, as the host will most likely resize 4800x2040 either down or up to a standard, which can have adverse effects on quality, but ymmw.

Great advice, thank you!

[IrfanView]

To all the IrfanView users out there: make absolutely sure that you disable this function in Settings > Plugins. Otherwise IrfanView will report half the real size of your DNG's.








____

It turned out that my image viewer (IrfanView) was reading the resolution of the CinemaDNG's incorrectly.
It erroneously reported them as being 1020 pixels in height.

I opened the DNG's in PhotoShop and they were 2040 pixels in height. So it's all starting to get clear now.

?
In 4.8k 2:35 your resolution is 1600x2040 which must be expanded to 4800x2040.
I have troubles to understand where your 1020 pixel setting happens.

That's the big question.
My DNG's are 1020 pixels tall.
Maybe I have set wrong export settings in my MLV app.

2. Is unneccessary because Bilal listed all modes and their resolutions. You are re-inventing the wheel.

Sure, but I wanted to get the de-squeezed numbers. Once I had them written down on file, I no longer go through this step.

[4800x2040]

Here is my workflow. You guys tell me if I am doing anything wrong (most probably I am).

1. I use a Canon EOS-M camera with Magic Lantern Crop Mood installed and shoot a clip in 4.8K, 2.35:1 anamorphic.

2. I then use the MLV app to export the .MLV file to AppleProRes LT for the sole purpose of finding out what the final de-squeezed size should be. It turns out that the final size must be 4800x2040 pixels. I write this down.

3. I then use the MLV app again to export the same .MLV clip to CinemaDNG Lossless.

4. I create a new project in DaVinci Resolve.

5. I change the project settings (File > Project setings) to Custom and then enter 4800x2040 pixels

6. Then I import the CinemaDNG sequence in the Media Pool of DaVinci Resolve

7. In the Cut page I drag the CinemaDNG sequence down to the editor tab, and this automatically creates a new Timeline

8. I right click on the new Timeline and do Timeline Settings > uncheck Use Project Settings > Mismateched Resolution = Stretch frame to all corners

Tada! I now have a perfectly de-squeezed footage.


Now. I see one huge problem with this workflow.
The original CinemaDNG's are 1020 pixels tall, which means that when I stretch them to the final height of 2040 pixels, I lose quality.
If I leave them at 1020 pixels of height, then I no longer have 4.8K footage. It is a Catch 22 situation.
What should I change in this workflow?
How do you guys manage to upscale the 1020 pixel DNGs to a larger size without loss of quality?



____________

Yes, at first I thought that my card was fake. But since it scores above 90 mb/sec, it should do the job.


PS
Copying the Settings folder from one card to another saves time.

Thanks a lot, man. It worked.
I am now able to access ML while in Photo Mode.

I ran the benchmark test once again (in Photo Mode and on a freshly formatted SD card) and got the results shown below.
I think they are decent.

You access ML the same way, by holding the trash button a few seconds.
Try formatting your card in camera. Use the "Keep ML Files" option, restart.

I did all of that. Still, I cannot access the ML settings menu in Photo Mode.
Pressing and holding down the trash can button in Photo Mode does nothing in my case. It also causes the camera to make weird noises.

I just benchmark tested my new SD card. It is a Sandisk Extreme PRO that is advertised to reach 200R / 140W speeds.

I noticed something strange.

When the card was completely empty, it scored 71 MB/sec write speed and showed some error for the read speed in Video Mode.
Then, I recorded a short video and ran another benchmark test again in Video Mode. This time around the card scored 92 MB/sec write speed and 83 MB/sec read speed.
Don't know what is causing this difference in benchmark results.

PS:
I haven't tested the card in Photo Mode because I don't know how to access the Crop Mood settings in that mode.

I think you definitely need to activate the overclock on the 2nd card after the first boot.

Thanks. Will do that.

Every card needs a first installation to make the card bootable.
Why don't you test the rest and draw you own conclusions?

Thanks. The SD card that I bought will arrive tomorrow and I will do some tests.

Bit about oc doesn't make sense. If you are not using oc you are limited to cam specs and this means 50 MByte/s theoretical bandwidth.

Sorry, I didn't phrase my question correctly.
My question was: If I copy all ML files from an overclocked SD card to another non-overclocked card, does this automatically make the second card overclocked too?

I bought a new SD card for use with ML Crop Mood.

Kind of a stupid question, but do I have to go through the entire ML installation process for this new card, or is it going to be enough to just copy all the essential ML folders and files from my older card on which I already have ML installed?

In case that copying the files from one card to another is going to be enough, do I have to still overclock the new card?

Thanks!

[Sandisk Extreme PRO]

I use an older model Sandisk Extreme PRO microSD card with an adapter. My microSD is overclocked to 240MHz.
It does the same results on the benchmarks as the regular size SD cards that I have seen other people use.
In my personal experience, Magic Lantern Crop Mood works great with microSD, as long as it is a Sandisk Extreme PRO.

It worked.
Best watched in 4K.

the other important thing is that a set up ML to "open gate" mode, it means, almost 4:3 aspect ratio (1736x1160), and so this can increase that separation of background from subject a bit more

Very interesting, thanks!
I wasn't aware of the "open gate" mode. Will look in the ML settings and try to find it and experiment with it.

Looks awesome! Amazing separation between subject and background.

A quick question: How did you get such a blurry background from a f/3.5 kit lens?
Did you keep the lens zoomed all the way to 55 millimeters all the time?

[1920 x 816]

My first (successful?) try at using Magic Lantern.
EOS M and 15-45mm kit lens.

24 frames per second
1/50 shutter speed.
ISO was kept at 100 at all times.
Originally shot using the 4.8K preset in Crop Mood and then exported using the MLV App to 1080p (1920 x 816 to be more precise).
This was done in order to save editing time in Adobe Premiere.

No color grading or color correction was applied.
Also no noise reduction.

Everything was shot hand-held and then stabilized in Adobe Premiere.
The stabilization process cropped the video and this took away from the sharpness of the original material (which was a bit soft to begin with).

______________________________

Could you try this version?
https://www.magiclantern.fm/forum/index.php?topic=27084.0

Hi Danne, I confirm that your version works.




I am now able to control the ISO with the Up and Down buttons, which is awesome.
Is there a way to assign the Left and Right buttons to the Aperture?
What is your workflow for quickly changing exposure settings when filming?

Also, I remember watching a tutorial on the original Crop Mood and there was a way to lock the shutter speed at 1/50.
Does your version have that option too?


I will continue to experiment with some of Bilal's original builds of Crop Mood too.
I suspect that the older ones would work better than the newer ones.
Will keep you guys posted.

Could you try this version?
https://www.magiclantern.fm/forum/index.php?topic=27084.0

At least one combo you show will not work on eos m.

Hi! Thanks.
I will try it tomorrow and will post back.

Show button/key associations.

[EOS-M]

I got myself a Canon EOS-M.
Downgraded its fimware from 2.0.3 down to 2.0.2
Then downloaded the latest Crop Mood build: magiclantern-crop_mood.2023Aug19.EOSM202.zip and installed it.
Set the video settings to 4.8K, 12 bit, ~24 fps.

I can't make the programmed buttons work and therefore I can't change the ISO and Aperture. The buttons do not respond while in Crop Mood.
The dial is as good as dead and does nothing as well.
What could be causing these issues?

?
MLVFS should be able to handle focus pixel maps thus no need to deal with focus pixels in any following workflow steps.

Awesome. Thanks.

When using the MLVFS will I be bale to somehow remove the focus pixels form within Adobe Premiere?