Messages

@masc Completely offtopic!? You guys were talking about MLV App otherwise I wouldn't have asked the question. Anyway thanks for your answer 

A couple of general MLV App questions.

Do Profile Presets and "Allow Creative Adjustments" make any changes to the RAW data file when exporting to any of the CDNG formats in MLV App?

When "Allow Creative Adjustments" is deselected are we looking at a clean RAW image (+RAW Corrections) or is something else happening to the image we see in MLV App video window?

I just want to understand if I'm bringing clean RAW data into DaVinci Resolve and that what I'm seeing in MLV App closely matches what I'm seeing in DVR.

OK got it!

Now that I've had a chance to do a bit more testing, I'm starting to understand where and why you've made the compromises/choices you have. Been swapping SD cards between Danne's Jan 19 2024 build and Bilal's Aug 19 2023 build to see the performance and functionality differences.

I really like the compromises you've made to give us something with the best of both builds and a bit more ML magic sprinkled on top.

Once again kudos and thank you Danne and Bilal!

Making preview 14bit allows for more precise exposure monitoring, as false colors and Histogram are more representative. Those were always slightly off when recording below 14 bits before, so you had a greater chance of clipping footage. The pink clouds you see in iaburn's example are the result of the highlights being clipped. It's not always possible to get rid of those after.

Interesting, I didn't know that.

I've been experimenting with a variable ND filter and using the RED, AMBER, GREEN recording icon as a kind of exposure metre. I ride the exposure with ND filter based on the icon. Similar to focus pulling, it's not perfect but it gives quite a good result. Definitely takes some practice though

Is what we see on screen during recording under 14 bit not a representation of what is recorded to SD card? Including the new build...

New upload:

- Reworked Movie tab menu, added access to all important stuff
- Fixed screenshot bug
- Added fixed intervalometer and rec delay lua scrip(autoenabled, bottom in movie tab), fixed a console bug

Sharing my extended Config Presets folder for - Crop Mood Danne custom tweaks 16th Jan 2024

Make sure to read the Presets_READ_ME before installation and follow the specific instructions

Please feel free to share link https://drive.google.com/file/d/1OWKJGSERLr9bbWm9wjSy6AiPJSLju2ux/view?usp=sharing

NOTE: all resolutions are intentionally set to 23.976 @ 1/48 shutter

Enjoy!

If you set your camera to Manual Focus (MF), in the canon menu, or on the lens if you are using an ef-s lens on an adapter.

You can go to the customize buttons menu and set it as:

Half-Shutter: Zoom x10
SET Button: Aperture +
INFO Button: Aperture -

@gabrielangel

Thanks for the suggestion man but you've probably already seen Danne has added a sticky half shutter fix to the code. Woohoo!

Allows for the best of all button presets.

Hard to believe the EOS M just keeps getting better in 2024.

RE

Danne!!! This is awesome man, thank you.

Yet another level up on functionality. Great job and thanks again.

RE

I was using SET for x10 Zoom but now using for Aperture + so was hoping for an alternative for x10 Zoom that toggles on/off

Thanks Danne.

I just came back to post an update to my previous post to say I retested the new build on a different SD card and it solved the issues I was having with CR2.

All seems to be working fine now

@Danne

Testing - magiclantern-crop_mood.2024Jan11_Custom.EOSM202

Adding custom mode presets folders removes the ability to capture CR2 in camera mode, works when custom mode presets is set to off and the camera restarted.

Works in various resolutions if CM is set to off and camera restarted.

Will sticky half shutter toggle be able to be fixed in Crop Mood? Would be nice to be able to have x10 Zoom stick on half shutter and the ability to toggle on and off, it currently freezes LV when activated. I know this is an old issue but thought it worth revisiting.

Otherwise working like a dream so far. Even on older slower cards.

Thanks for checking in.
I want a workflow which excludes the scroll wheel. As you say, it works bad as it needs multiple functions to work. With expo shortcuts we can skip the scrolling fiunally.
Installing this build automates modules and enables the build. Having an option to turn off the "invisible" modules will complicate things and I like to keep this simple. There´s the main crop mood build to do tests with. My version is more my personal preference and built around simplicity and usability.
Added false colors to tap display and fixed a few bugs.

Danne's on fire in 2024. This is awesome!

I'd just completed configuring my presets folders when I saw your update from yesterday. Combined with my presets this takes the little EOS M to a whole new level of functional.

Presets folder jpeg
https://drive.google.com/file/d/1Ew3EqcYAQOHQGj9SSY8Em6UznV11I7in/view?usp=share_link

One has to be careful not to push the shutter button too far. If done while recording, the camera hangs on a "Busy" message and needs to be restarted (Battery Pull).

It's a pity this broke in crop_mood... previously it just captured a still. Would be great to be able to take production stills while shooting. Not a deal breaker but it sure was a handy reference tool that saved us having to dig through CDNG files

Posted another build. Better Focus aid, closer to subject. Still needs better centering but works pretty well while filming with 1x3 and 1x1 presets.
https://bitbucket.org/Dannephoto/magiclantern_hg_02/commits/752c78080de8505f2943deb9dd9f7d2ca83dfc26

These registries zooms much like x10 zoom while filming.

Code Select Expand

        EngDrvOutLV(0xc0f11B8C, 0x0);
        EngDrvOutLV(0xc0f11BCC, 0x0);
        EngDrvOutLV(0xc0f11BC8, 0x0);
        EngDrvOutLV(0xc0f11A88, 0x1);


Download:
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/

Firstly a huge thank you once again to Danne and Bilal for all your extraordinary work!

Secondly a very safe, productive and prosperous 2024 to all the ML community.

All the best for the year ahead.
RE

Really love the crop mood and the work everyone in the magic lantern team has done to make it possible, thanks to everyone involved for that! I have used it alot and have started wondering if another mode could be added:

Anyhow I mostly use the 1x1 2.5k crop because of reasonable rolling shutter and little aliasing, the crop is acceptable when considering the colors and overall image quality from the magic lantern eos m. For me, the rolling shutter of about 24ms still requires a stabilised lens for handheld use, to look good (every mode works well on a tripod, of course). The 2.8k mode has as much rolling shutter as the 4.4k 1x3 mode (about 29ms according to ml menu), so the 4.4k seems a better overall choice because of less noise and less crop. Now I have started to wonder if there has been any experiments with smaller crops using the 1x3 mode? Would it be possible to make a 4k or smaller crop of 1x3 to get the rolling shutter closer to 20ms? A super-16mm crop (3x) in 1x3 mode could also be interesting, if possible, with even less rolling shutter. I guess the picture would be softer, and there would be some aliasing compared to the 1:1, but maybe it would be a good compromise considering the problems of the different modes, or are there other downsides?

100% agree, I can't thank the ML devs enough for all their excellent work. It's truly remarkable what is now possible with Crop Mood...even with the limitations etc

Here's a link to an excellent article on alternate ways for dealing with and minimising rolling shutter. I know it doesn't answer your questions but may be helpful for others new to the issue of rolling shutter

https://shotkit.com/rolling-shutter/

[both]

Thanks @RhythmicEye!

This an old issue which is related to susepdning aewb task i.e when setting Small hacks to "More" also when using shutter fine-tuning.

What about having both without a compromise :
I was able to find a workaround and fix the issue three days ago, this commit (no one noticed the commit? ). The fix will be available in next release, you can also compile from the source if you want.

Bilal, Bilal, Bilal!!! Crop Mood is becoming the uber beast of beast ML builds.

Awesome work.
RE

Thanks! I appreciate it, currently I don't have a personal funding account, also I am not sure if I want to create one.
Well, you can probably still be able to support ML project by donating to ML bitcoin address (if you are familiar with Bitcoin).

Yes I'm very familiar with Bitcoin. However it's been tanking recently and I'd prefer my donation didn't devalue once donated 

Try setting your shutter to 1/42 (or the closest value, depending on the resolution you are using). That way, you don't need to use shutter fine tuning, and there is no appreciable difference. The image remains sharp down to 1/30 (unless you are filming fast cars, etc.). This allows you to use all the hacks and record 3K 12 bit for at least 30 seconds on a freshly formatted card. The gain in clarity / fov trumps the motion blur difference (if any) in my opinion.

By the way, to get the exact same motion blur I am used to at 1/48 on a Sony cam, I need to set my eos m to 1/44 - 1/46.

Thanks Gabriielangel!!!

Good advise right here. I just needed a little kick to get past my pedantic nature to see the light. This little tip gave me the clue to get a fully functional set of modes from 1080p through to 5K. I had to make some tweaks in some of the more data intensive modes but more or less totally functional across the park. 3K is the most unstable and the only one where continuous recording is sketchy although it is possible in some conditions.

I'll do some day light testing in the coming days and report back with a detailed list for each mode.

Thanks again
RE

[ON]

ADDIT: Further testing in 5.2K mode with Sound ON, same settings as above with the following tweak

Resolution: 1696 x 2164 (5088 x 2164 in MLV App)
Sound: ON

Works very nice in controlled lighting so far. Icon mostly orange and green with a little red occasionally in bright highlights but continuous recording is possible.

[ON]

Issue fixed when turned off? If so your settings have no effect on recordings and might as well be turned off. Even more so if you say you like your results.
Probably one of the hacks in raw video menu causing it. Learn those functions properly and what works or not.

You're 100% correct Danne. I switched "small hacks" to ON instead of more and the issue is gone but so are the RAW performance gains. Recording stops after 40 seconds or so in 5.2K @ 12bit.

As suspected I'll have to compromise somewhere, which is fine, I just need to work out which is more important to me; 180º shutter angle or RAW performance 

Thanks again
RE

EDIT: The compromise solution I came up with to give me total control of the image capture process in "5.2K" RAW (no longer 5.2K but close enough) is below

Resolution: 1712x2184 (slightly reduced from 5.2K to 5136 x 2184 in MLV App)
Aspect Ratio: 2.35:1
Data format: 11bit
Small Hacks: ON
Shutter fine-tuning: +0.63ms
Shutter lock: ON
Shutter: 1/48
FPS: 23.976
Shutter angle: 180º
Sound: Off
SD Overclock: 240Mhz
Data rate: 72MB/s approx

SD Card: Sandisk Extreme Pro 170MB/s
Build: magiclantern-crop_mood.2023May09.700D115_Shutter

These settings are giving me pretty robust RAW performance even when over exposed significantly in controlled lighting. Have not tested in daylight conditions as yet and have not checked properly for image artefacts. Seems to be artefact free atm though

P.S I use aperture, ISO and ND filters to control exposure triangle

OK will take a look and do some tests and report. That makes a lot of sense though, I just haven't had time to dig much deeper than getting all the basics working more or less flawlessly in each mode. Absolutely loving Crop Mood regardless...

And a huge credit to you for all your work over the years as well Danne.

Much appreciated!
RE

[1/48th @23.976FPS (+0.65ms @1080p up through to +0.72ms @5.2K)]

Check if shutter fine-tuning is enabled.

Shutter fine-tuning is on and shutter set to 1/48th @23.976FPS (+0.65ms @1080p up through to +0.72ms @5.2K) and shutter lock is set to ON in "Movie Tweaks". I use this workflow in all modes to give me the 180º shutter angle I prefer to use in my shooting method.


This setting is a typical one I've always used with ML and never had this issue before. Maybe something has changed in Crop Mood that now makes this workflow redundant.

If that is the case I will just add a 1-2 stop or variable ND filter to my working method which I've been doing with Crop Mood anyway. I really like how it looks using this workflow, so maybe this will be my long term workaround if it's changed permanently.

Thanks for your reply
RE

[May.09.2023]

New Crop mood builds are out:
May.09.2023

3K 3072x1308 got semi full real-time preview

[gifv]https://i.imgur.com/Djp0aMQ.mp4[/gifv]


Added 30 FPS to 1280p 1:1 preset




Changes:

• Added 30 FPS for 1280p 1:1 preset.
• Now autofocus in normal preview at lower bit-depths like 10-bit is as accurate as in 14-bit (when using crop mood and lossless).
• AF method will be switched to FlexiZone Multi automagically when using manual focus, preview works better with this in 3x3 presets.
• Implemented semi full real-time preview for 3K 1:1 preset, only 2868 from the middle are being showing in preview from 3072 horizontal pixels.
• Hidded 1080p 3x3 preset from crop mood for 650D / 700D / 100D (you can use 1080p mode from Canon, crop mood isn't needed in this case).
• Implemented a simple workaround for ISOless errors for 650D / 700D (works on 700D, 650D needs testing).
• Fixed horizontal blurry line artifact which appears in some 1x3 presets which affect RAW data.

Crop mood builds - Downloads

Thanks once again for all your excellent work Bilal. Just a spectacular leap in functionality with Crop Mood and with each iteration it gets better.

I have one issue to report on my 700D which is happening in both April release and in the May release as well.

The issue I'm having is that I get a jump in exposure setting after hitting record. Exposure ramp is turned off and I've checked all my settings in both Canon and ML settings and there's nothing obvious to suggest user error.

Exposure jumps one to two stops to the right and it is absolutely consistent across all ML files for about 1 second so it's not too hard to compensate for. It can be seen clearly on the scopes in MLV App as well.

I've also been told by one other person via YT comments that this is also happening on his EOS M. Makes it hard to have confidence that I'm exposing correctly but it does seem to be exactly the same jump in exposure in all lighting conditions. Could be why some users are struggling with over exposing in the highlights when out doors.

My compensation technique is to under expose by one to two stops from what I see on the monitor and scopes when setting my exposure.

Have you or anyone else experienced this issue or know someone who has?

Build: magiclantern-crop_mood.2023May09.700D115_Shutter

So far that's the only real issue I'm having but I'm doing more real world testing today, I'll report any further findings in the coming days.

Thanks again
RE

P.S Do you have a "Buy Me A Coffee" account? :-}

If you want to know how to color correct mlv raw files to match other cameras, you may look at what photoshop does with it's camera profiles..
For example, if you convert mlv to dng and open it in photoshop, it will look almost the same (or the same) as usual cr2 file from the camera.

So it is obviously the same raw data. I don't know what adobe software does with color, but they have profiles for all cameras somewhere in folders, you can find there your canon camera profile. Maybe this profile can be converted to some LUT or something somehow...

Good suggestion but for Davinci Resolve I just needed to confirm the flavour is Canon RAW sensor data. That's what I assumed but was never 100% due the .MLV to DNG file conversion.

Now for some lighting and color chart testing to see just how accurate the color reproduction is for each of the various RAW flavours within DR.

Cheers RE

That's wrong. MLV and DNG are different formats, which hold the same RAW image data, but in a very different internal structure.
For color calibration MLVApp uses the camera matrices. No idea what DR does here.

Thanks for the explanation. MLVFS converts so quickly it seems to be more like a wrapper removal than a transcode.

Always happy to be wrong in the process of learning.

CinemaDNG isn't used at any point by ML, or by Canon, as far as I know.  Where are you seeing this?

ML takes the sensor data from camera memory and copies it unchanged into MLV files.  I would expect CR2 files to use the sensor data in the same way; by not changing it.  The file format of CR2 differs, the sensor data should be the same.

Again my bad, I meant DNG not CinemaDNG. An .MLV file is just a container for a sequence of DNG files. I use MLVFS to unpack them real time so I can grab still frames and short DNG image sequences easily. MLV App is a much better workflow though.

https://www.magiclantern.fm/forum/index.php?topic=13152.0

Anyhow you just answered my question which gives me the information I was looking for.

Thanks for your patience.