MlRawViewer 1.3.3 (CDNG/MLV/RAW Viewer & Encoder, Linux/Mac/Win)

[GooD]

Hmm... I was hoping this had been fixed in 1.1.6 as it now checks that the xport path is valid. But I guess the problem must be caused by something else.

Could you find the ".mlrawviewer" folder in your user home directory, send me a copy of the folder and all the files in it (it's small).

Then you can delete the folder, and that will probably work around the problem so that it doesn't fail on exports.

Here you are: https://drive.google.com/file/d/0B0eKXjSwHrNGNkpLcTdwZ3lEeHM/edit?usp=sharing

[poromaa]

I reported an issue about encoder stopping if display goes to sleep.

[davegravy]

Baldand, as requested I PMed you links to some sample RAW footage with pink dots from my 650D. Please let me know once you've dl/ed them so I can clear up some space on my Dropbox acct.

Thanks,

Dave

[Kuky]

Hi,

If you shoot crop mode (x5 zoom) with a 5D Mark III and use FPS override (for example 24 exact FPS) MlRawViewer will report 29,776 fps. Maybe it's a metadata mistake.

I verified shooting a timer watch in crop mode. It's actually using the override setting. Here is an actual file (2,2 Gb): https://drive.google.com/file/d/0B3ncQl4hSqlnR096bXNWbk1PYTQ/edit?usp=sharing

[baldand]

Hi,

If you shoot crop mode (x5 zoom) with a 5D Mark III and use FPS override (for example 24 exact FPS) MlRawViewer will report 29,776 fps. Maybe it's a metadata mistake.

I verified shooting a timer watch in crop mode. It's actually using the override setting. Here is an actual file (2,2 Gb): https://drive.google.com/file/d/0B3ncQl4hSqlnR096bXNWbk1PYTQ/edit?usp=sharing

The MLV header data reports 29776/1000. mlv_dump also gives the FPS as 29.776000. The problem looks to be in the file.

[Kuky]

Yeah, I wasn't sure, that's why I shot a timer 
But counting the frames it appears to respect FPS override

[mrsirio]

Hey Baldand,

It's all working well for me, except that I miss a way to choose the dimensions (and with that the exact aspect ratio) of the exported movie. Any chance to see this implemented?

thanks for writing the best software one can dream of!

[a13x]

Hi everybody.
Maybe someone tell me how disable log file create?

[ariaelf]

This converter is working great for me as far as exporting to DNGs, but I'm wondering is there a way to do batch conversions with it or something else? I was using M L RAW Video Converter 1.9.1 previously, but now it's spitting out errors and not working now...

[Frank7D]

This converter is working great for me as far as exporting to DNGs, but I'm wondering is there a way to do batch conversions with it or something else? I was using M L RAW Video Converter 1.9.1 previously, but now it's spitting out errors and not working now...

If you just need DNGs, there's MLV Mystic...
http://www.magiclantern.fm/forum/index.php?topic=10466.0

[ariaelf]

If you just need DNGs, there's MLV Mystic...
http://www.magiclantern.fm/forum/index.php?topic=10466.0

Thanks for the heads up Frank! I will definitely give Mystic a try right now. Fingers crossed!

*UPDATE* Mystic worked great! YAAAY! Thanks again Frank - you saved my workflow bacon!

[ugo247548]

Hello,
I'm having problems with Mac version 1.1.6.

Here's an example - shot to *.MLV (/w sound) using 4Jun2014 Nightly for 5DMK3
48fps Override, 1920x503

Some ugly gradients in the grass, overexposed leaves on the right and on the top of the shot (yes, I know not to expose that way - it was a test).
And also, there are some pink dots on the overblown hair.

MlRawViewer exports to ProRes4444 that way.

http://postimg.org/image/ejcr5eoq5/

The CDNGs themselves are okay - ACR in PSCS6 opens them properly.

http://postimg.org/image/g3e9zzvg7/

Any advice on how to deal with this artefacts?
I can upload the original MLV if needed.

[EDIT] Here's what Son of Batch MLV (Beta) exports:
 http://postimg.org/image/esjudkpl1/

Pity it's ProRes (HQ) Rec.709 with no control over Tint/Expo (and no sound).
What I like about MlRawViewer is that it exports ProRes4444 with LOG flat setting and decent WB/Tint/Expo Control prior the conversion (and with sound). Hope there will be a fix for the artefacts soon.

[EDIT2] Uploaded the MLV (420MB) http://yadi.sk/d/a3C99GZ7Sk3oA and a single .dng (2MB) http://yadi.sk/d/PphwlzA_Sk4Bf

Hope it helps and, baldand, thanks for already wonderful software which I hope is on it's way to become the best and only software anyone will ever need to work with ML RAW.

[baldand]

Hello,
I'm having problems with Mac version 1.1.6.
...
Some ugly gradients in the grass, overexposed leaves on the right and on the top of the shot (yes, I know not to expose that way - it was a test).
And also, there are some pink dots on the overblown hair.

Things always get tricky when you are trying to recover detail (by reducing the exposure level) from overexposed areas which have a clear colour that is different from that of the main lightsource (or sky).

Green objects are the worst because the green channel is the one the is clipped first, so the actual hue information has gone.

The current MlRawViewer highlight recovery tries to keep some hue by guessing the green level from the other channels, taking into account the current white balance. That works well for avoiding pink skies. But this is one of those overexposure cases where that approach can never work.

(The alternative would to throw away colour entirely as the luminance approaches the overexposed region, and just try to recover luminance detail, which is what ACR seems to do).

[Samario]

Hi All

Firstly, MLRAWVIEWER is pretty amazing (so thanks to the dev team!), because I can take my MLV files with sound, quickly balance/correct the exposure/temperature and then exported out to a very easily editable ProRes 444.  The conversion for me is very fast.

Quick question though.  I have noticed that you allow export of adobeRGB, Log, and Rec709.  What standards/libraries are you using to define your "Log", "Rec709", etc.  I need to know because after I edit these files in Premiere and I'm ready to colour grade (I use FilmConvert and Osiris), it's very important that I identify the source material correctly, for the LUTs to work properly.  I am using a 5dmark3.

Is your Log output exactly the same as the Canon C-Log? or equivalent to some other log like VisionLog. 
Is your Rec709 the same as any other Rec709?
Is the adobeRGB the same as the ML RAW Standard input for FilmConvert (i.e. untouched colours)

Your insight would be helpful as then I know the correct input starting point when I begin my colour grade process.
Thanks!

[baldand]

Quick question though.  I have noticed that you allow export of adobeRGB, Log, and Rec709.  What standards/libraries are you using to define your "Log", "Rec709", etc.  I need to know because after I edit these files in Premiere and I'm ready to colour grade (I use FilmConvert and Osiris), it's very important that I identify the source material correctly, for the LUTs to work properly.  I am using a 5dmark3.

Is your Log output exactly the same as the Canon C-Log? or equivalent to some other log like VisionLog. 
Is your Rec709 the same as any other Rec709?
Is the adobeRGB the same as the ML RAW Standard input for FilmConvert (i.e. untouched colours)

Your insight would be helpful as then I know the correct input starting point when I begin my colour grade process.

MlRawViewer is open source so it's easy to see (and change or extend) what it does and can do.
The code for all the relevant conversions is almost fully self contained in this (OpenGL shader) source file:

https://bitbucket.org/baldand/mlrawviewer/src/b9ea6b768d663e431df7378f1a3b5bd241f89d02/ShaderDemosaicCPU.py?at=master

In addition, the colour matrix calculations are here:

https://bitbucket.org/baldand/mlrawviewer/src/b9ea6b768d663e431df7378f1a3b5bd241f89d02/mlrawviewer.py?at=master#cl-1722
(these were based on the ones done by dcraw).

The initial colour balance multiplier comes from you either directly or by clicking on a reference grey.
The colour matrix to convert to XYZ colour space comes from Magic Lantern in the MLV file, and that is multiplied with a matrix to convert from XYZ to sRGB linear values. That combined matrix is used to convert the raw colour into linear sRGB (note, NOT AdobeRGB) colour.
The log function simply maps & cĺips the colour into the range 1-1024, and takes log2. That results in a value in the range 0.0-10.0, so it divides by 10.0 to make that 0.0-1.0 (shader colour output should always be in that range)
The sRGB and Rec709 functions apply the standard linear+power gamma functions for those two specifications.

I hope that helps you out a bit.

[rrrmusic]

Anyone experience that.
http://tinypic.com/r/xbcked/8

Workflow
MLV - 5Dmk3 april 20 nightly
mlrawviewer 1.1.6 to mov log curve
premiere cc Windows
m31 lut LOG

[Rewind]

Anyone experience that.
http://tinypic.com/r/xbcked/8

Strange. Banding artifacts are too harsh even for 8 bit workflow. Can you share this MLV file for testing or one of dng's made with mlv2dng?

[rrrmusic]

I think the problem is the mov convertion of mlrawviewer. Recently used raw2cdng and process in after effects. exported to mov prores and the problem is not present.

https://www.dropbox.com/s/yrdap681f7smiap/M02-1703_000001_DNG.rar

[baldand]

Anyone experience that.
http://tinypic.com/r/xbcked/8

Workflow
MLV - 5Dmk3 april 20 nightly
mlrawviewer 1.1.6 to mov log curve
premiere cc Windows
m31 lut LOG

What PC & GPU do you have?

[timbytheriver]

Hi @baldand et al

I'm a regular user of the Cineform codec. Would it be a massive complication to add this to the export options some time?

Many thanks for your continued great work.

[rrrmusic]

Windows 8.1 PC HP EliteBook 8760w GPU Nvidia Quadro 3000M

[rrrmusic]

Windows 8.1 PC HP EliteBook 8760w GPU Nvidia Quadro 3000M

[ToS_Maverick]

Hi baldand,

first of all, thank you for this great tool!

I have a few questions regarding the default exposure of the log curve.
I'm usually very careful about my exposures and just checked, with RawDigger, where 18 % grey falls in the linear space. It seems Canon places it in the area around 1024, which is at -4 stops.

The sRGB curve that you use for example, seems to use 2048 for it's grey value.

I've checked the code as you suggested, fired up good old Derive and plotted a chart, normalized to 10 bit output (0-1023).
This is what I got:


According to this, the 18 % grey, exposed with a light meter, should fall at 60 % or 614.
I tried checking the code for any default exposure correction value, but could not find it so far.

Could you maybe explain why the log curve is a bit darker?
Or did I overlook something?
Arri is putting grey at 40 % IRE for example, Sony with S-Log around 38 %:
http://blog.abelcine.com/wp-content/uploads/2009/12/SRW_ITG_S-Log_001_IO_EN.pdf

My goal is to expose correctly, set WB, switch to the log curve and batch convert to ProRes.
In my NLE I would then apply a log2r709 curve, with an S to avoid clipping.

Just my thoughts/2c,
BR,
Michael

[myneo]

Hi,
I am a beginner for using Magic Lantern. When I convert mlv file into mov. using MIRawViewer Im getting red spots in the dark areas of the footage.

Secondly, for making a music video the external sound got in sync with the mov. footage I got from  MIRawViewer. But the colour grading is not as good as the one done by after effects.

If, I convert the Mlv file to dng through MLVMysticand take it to AE the colour grading becomes best but the external sound doesn't sync with it in the Final Cut Pro X.

Please guide me wht to do. Im a  magic Lantern lover andI dont wanna quit using it because of lack of proper information.

[baldand]

Hi,
I am a beginner for using Magic Lantern. When I convert mlv file into mov. using MIRawViewer Im getting red spots in the dark areas of the footage.

Secondly, for making a music video the external sound got in sync with the mov. footage I got from  MIRawViewer. But the colour grading is not as good as the one done by after effects.

If, I convert the Mlv file to dng through MLVMysticand take it to AE the colour grading becomes best but the external sound doesn't sync with it in the Final Cut Pro X.

Please guide me wht to do. Im a  magic Lantern lover andI dont wanna quit using it because of lack of proper information.

The red (coloured) spots in dark areas is a known bug (seen mainly on Windows with Nvidia GPUs) which I have a fix for already. That will be included in the next release. (Link: https://bitbucket.org/baldand/mlrawviewer/issue/72/coloured-spots-in-mov-exports-with-114-115)

I would be interested to hear which kind of colour controls or features would make MlRawViewer good enough for you to use instead of a more heavyweight tool. You can suggest ideas or vote for existing ones on the issues list: https://bitbucket.org/baldand/mlrawviewer/issues?status=new&status=open