MLV App 1.14 - All in one MLV Video Post Processing App [Windows, Mac and Linux]

[masc]

Do you guys happen to know if there is an option to rotate the image when recording 1080x1920?

Just 0° and 180° is available. Any other angle can be setup in your final NLE.

Second question, more general, what is your way of editing an .mlv file if you use Premiere Pro, as I do?
Is there a better / equally good method, like: edit in MLV App -> export finished file in ProRes 4444 as .mov -> work on timeline in Premiere Pro?
E.g. exporting in some format to Premiere Pro and colouring directly there?

You can use Adobe ACR in After Effects. For me still the benchmark color wise.

Most of the time I do my final editing on Davinci Resolve, exporting as DNG from MLV App. It is more convenient to do color correction and video cut on the same place, and also much faster to export.

Not always true. ProRes export currently is faster than DNG in MLVApp. And Resolve also needs much time to render...

MLV App is awesome on many aspects, but there are things like highlight recovery, noise reduction or local corrections that I miss from Resolve.

Highlight recovery and noise reduction is available also in MLVApp - good enough for most cases.

Hi! I'm getting flickering highlights when exporting a dual iso mlv as an Apple ProRes video.

If you use official release: probably the known problem and the reason why we discussed to remove dualiso completely. Upload a MLV for analysis. Or try the latest versions from @iaburn - he did a great work getting a better version of dualiso processing into the app. This one should be flicker free.

[iaburn]

If you use official release: probably the known problem and the reason why we discussed to remove dualiso completely. Upload a MLV for analysis. Or try the latest versions from @iaburn - he did a great work getting a better version of dualiso processing into the app. This one should be flicker free.

I couldn't fix the flicker, but cedricp implemented a workaround that prevents flickering by applying the same correction values across all frames:
https://www.magiclantern.fm/forum/index.php?topic=25781.3675

[Skinny]

So guys why don't you release 14.1 beta with these new dual iso corrections? It won't hurt anyone It's been a long time since the last release..

[masc]

So guys why don't you release 14.1 beta with these new dual iso corrections? It won't hurt anyone It's been a long time since the last release..

The new version is not in the main branch. And I think some testing appart from iaburns work could be useful too. Releasing several times with all the deployment needed to make it work on as much computers as possible, probably with fixes, might not hurt, but is a lot of work which makes not too much fun.

[bouncyball]

Hello guys! My old, good friends and newcomers.

I'm glad this great thread is still active and productive and newcomers providing great contributions!
 
I have missed you all

regards,
bb

[Danne]

So guys why don't you release 14.1 beta with these new dual iso corrections? It won't hurt anyone It's been a long time since the last release..

For Mac users I and also iaburn and probably a few others we could release a test build. For Windows users there must be someone out there...
Code is still worked upon so releasing official betas might.not be necessary.

[iaburn]

I've been also using the version compiled with the new Qt and dual ISO speed up on Windows and works fine.
I leave the decision of putting everything together and release a new version to Masc, as I think he is currently the main contributor to MLVApp.

It would also be cool to have a final version of cedricp's flickering fix, so we can put everything together when the time comes

[gabriielangel]

@iaburn, I tried the Windows version you posted and it really makes a difference on some clips.
So far, it works best when the whole scene is relatively well exposed without clipping and only the shadows needs lifting.
When there are a lot of highlights and mid exposures in a given area, we get the horizontal lines and resolution artifacts (Especially when not using a tripod).

I also saw that the "Transcode and import" option will not allow to import 10 second DNG sequences. On the official Mac version, it is possible to import around 260 frames before it gives an error.
This function is quite handy to match footage coming from motioncam, when the film emulation filter is used in MLV app.

Is this a Windows limitation?

[iaburn]

@iaburn, I tried the Windows version you posted and it really makes a difference on some clips.
So far, it works best when the whole scene is relatively well exposed without clipping and only the shadows needs lifting.
When there are a lot of highlights and mid exposures in a given area, we get the horizontal lines and resolution artifacts (Especially when not using a tripod).

Is this something specific on my fork or an issue in MLVApp in general? Could you please point out an example illustrating the issue?

[gabriielangel]

Your fork makes it less obvious, but this is an issue in general, as it also does it with the official build.
I will try to make a few examples in a controlled / repeatable manner over the weekend (I cleaned up my previous tests).

[masc]

I also saw that the "Transcode and import" option will not allow to import 10 second DNG sequences. On the official Mac version, it is possible to import around 260 frames before it gives an error.
This function is quite handy to match footage coming from motioncam, when the film emulation filter is used in MLV app.
Is this a Windows limitation?

Yes, Windows cmd line is limited. But only 260 frames on Mac? Currently I process GoPro RAW timelapse footage in MLV using DNG import and I also had 300+ frames... I've seen no error so far.

[masc]

I leave the decision of putting everything together and release a new version to Masc, as I think he is currently the main contributor to MLVApp.

It would also be cool to have a final version of cedricp's flickering fix, so we can put everything together when the time comes

I've seen there is a pull request ongoing. Nice to see all that contribution! For myself: I barely use dualiso, so I have to trust your input... also the reason why I was asking for more testing (also of other users)

[gabriielangel]

Yes, Windows cmd line is limited. But only 260 frames on Mac? Currently I process GoPro RAW timelapse footage in MLV using DNG import and I also had 300+ frames... I've seen no error so far.

Sorry, the Official Mac 1.14 version can transcode and import 420+ frames (Don't know the exact upper limit)
Official 1.14 PC Version: 305 frames Max (Gives an error at 306)
Iaburn's openmp version: Cannot transcode and import

[masc]

Official 1.14 PC Version: 305 frames Max (Gives an error at 306)
Iaburn's openmp version: Cannot transcode and import

If I remember right, Windows cmd is limited to 8196 characters. The number of frames possible to import, depends on the path name lengths.
You need raw2mlv executable in app image / path.

[iaburn]

I've seen there is a pull request ongoing. Nice to see all that contribution! For myself: I barely use dualiso, so I have to trust your input... also the reason why I was asking for more testing (also of other users)

We have merged cedricp's changes with mines on my fork. I will try to compile the app for Windows and MacOS ARM, but I think I was having problems with focus pixel maps downloading not working...
Another thing that I forgot is that sounds doesn't work, at least when I build it with my Qt versions
After that, I'll post it here and maybe put a link to the post also on the Facebook group, trying to get more people to test and getting it ready for a pull request

[gabriielangel]

Is this something specific on my fork or an issue in MLVApp in general? Could you please point out an example illustrating the issue?

Here are a few examples (2.5k and 5k frtp, with and without dual ISO 100/800): http://bit.ly/3K1Yfzx

In order to trigger artifacts in a clip easily, you must:

Move the camera vertically slowly;
Have areas where clipped and non-clipped detail-rich elements are next to one another (Like bare tree branches towards the sky);
Have horizontal elements moving through High and Low ISO scanlines;
Clip must be at least a few seconds long for you to see movement happening.

The exposure flickering is more visible in large, relatively flat areas (few details), where blending occurs.

If you use a tripod and avoid what is stated above, artifacts are sometimes imperceptible.

[iaburn]

Here are a few examples (2.5k and 5k frtp, with and without dual ISO 100/800): http://bit.ly/3K1Yfzx

In order to trigger artifacts in a clip easily, you must:

Move the camera vertically slowly;
Have areas where clipped and non-clipped detail-rich elements are next to one another (Like bare tree branches towards the sky);
Have horizontal elements moving through High and Low ISO scanlines;
Clip must be at least a few seconds long for you to see movement happening.

The exposure flickering is more visible in large, relatively flat areas (few details), where blending occurs.

If you use a tripod and avoid what is stated above, artifacts are sometimes imperceptible.

Thanks for the samples (nice images btw, lots of snow still!).

I see now what you mean, thin horizontal shapes with highlights are one of the worst cases for dual ISO. I tried to minimize the artifacts by adjusting settings but cannot get rid of them completely.
In one of the videos is very obvious on the tree branches and the railing next to the building. On this edge cases, I'm afraid there is not much you can do 

[RhythmicEye]

I don't think there is currently a way to rotate the image on MLV App, but if you are editing on Premier it's just a small inconvenience while preparing for export.

Most of the time I do my final editing on Davinci Resolve, exporting as DNG from MLV App. It is more convenient to do color correction and video cut on the same place, and also much faster to export.
MLV App is awesome on many aspects, but there are things like highlight recovery, noise reduction or local corrections that I miss from Resolve.

When importing footage / DNG images into Davinci Resolve what input color space settings are you using for images captured using ML? I know Zeek used to suggest using Arri Alexa but I'm wondering what the native color space is for ML. I would have assumed a Canon variety color space would have been optimal but I'm left wondering

Thanks RE.

[vastunghia]

When importing footage / DNG images into Davinci Resolve what input color space settings are you using for images captured using ML?

As long as you work with Raw DNG only, unless you are a professional colorist, my advice is to just trust DVR. Go for DaVinci YRGB Color Managed with Automatic color management. Then I suggest choosing HDR as Color processing mode, regardless of your Output color space (SDR should be the norm here). Also, in the Camera Raw settings, under CinemaDNG, I suggest you do *not* enable Apply Pre Tone Curve, leave Color Science = Camera Metadata, and pick Color Space = Blackmagic Design.

At least that's what I do after trying out more complex settings.

[ML700D]

I use cineon log in mlv app (color space use wide gamut like: adobe rgb, alexa wg, sony or davinci gamut) when edit using DR with default setting,  I think.. it gives better gamma and easier to grading when work in rec.709 environment.

[ML700D]

.

[RhythmicEye]

As long as you work with Raw DNG only, unless you are a professional colorist, my advice is to just trust DVR. Go for DaVinci YRGB Color Managed with Automatic color management. Then I suggest choosing HDR as Color processing mode, regardless of your Output color space (SDR should be the norm here). Also, in the Camera Raw settings, under CinemaDNG, I suggest you do *not* enable Apply Pre Tone Curve, leave Color Science = Camera Metadata, and pick Color Space = Blackmagic Design.

At least that's what I do after trying out more complex settings.

@vastunghia thank you for your excellent reply.

Yes all of the information you stated is correct but the most important information to make it all work correctly within DR is knowing your input color space first or the color space your camera records hard baked into your data. If you don't know this or get this right none of the other settings that you apply will be accurate because they relate to output color space / display color space. You must know the input color space first before you can get accurate results within DR for output to your monitor. Example: Canon C-Log (input CS) to REC 709 / Gamma 2.4 (output CS)

Even with color managed Davinci Wide Gamut Intermediate you still need to know your camera's or input (graphics etc) CS. If you don't know this info it's very difficult or even impossible to get accurate results when color grading. Especially if you are using footage from multiple, different camera manufacturers within the same project.

I'm assuming ML must use some form of Canon Log for the color space data.

Thanks again RE

[names_are_hard]

Are you talking about raw images here?  Those don't really have a colour space.

[RhythmicEye]

Ahhh yes RAW. My bad I meant some form of Canon RAW not log.

In DR there is an option for DNG Raw or Canon Raw. I'm assuming the Canon color science / algorithmic data from the sensor must remain in the DNG files.

Maybe not but that seems strange as all the sensors are Canon. I know this must seem pedantic but I think it's important to clarify.

[names_are_hard]

Raw files are straight from the sensor, no colour science has occured.  They don't have a colour space.  You can convert the raw data into any colour space you want.  I would guess DR has an option for Canon Raw because CR2 / CR3 is a different file format to DNG.