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

[nick.p]

Do you mean thumbnails in the individual DNG files, or something else?

Yeah, essentially the option found in the adobe dng converter.

[arrinkiiii]

Good work Baldand =))

[ItsMeLenny]

Yeah, essentially the option found in the adobe dng converter.

People don't know what that means, you have to provide examples.

[RenStarFilm]

I love the fact that it now has thumbnails so i cant see what DNG file I'm working with!!!!!!!!!!!!

[DavidSh]

Good work man!

Great tool.
You really take post and on set preview to other level.

noticed:
mouse cursor disappear after resize application window.

Mac OS Mavrickis.

[swinxx]

Anamorphic desqueeze would be a very great addon

https://bitbucket.org/baldand/mlrawviewer/issue/38/desqueeze-anamorphic-material-with-ratio

[jose_ugs]

@swinxx... which is a good reminder to add this:
https://bitbucket.org/baldand/mlrawviewer/issue/39/50-60fps-squashed-mode

[Midphase]

2. *EXPERIMENTAL* DNG export as alternative to MOV.

This is really fantastic, thank you so much!

However, as you move forward on refining this, could I lobby you to consider CDNG instead of regular DNG? The reason why is that Adobe is likely about to fully support CDNG in Premiere Pro, and thanks to Blackmagic it's quickly becoming the de-facto standard for raw video files. My understanding is that the difference between DNG and CDNG is just in the header information which includes specific information as it relates to video.

Right now, on the Mac, there is a need for some sort of .mlv to CDNG solution since none of the current apps can do it. It would be a fantastic option to have MLRawViewer do it.

[baldand]

However, as you move forward on refining this, could I lobby you to consider CDNG instead of regular DNG? The reason why is that Adobe is likely about to fully support CDNG in Premiere Pro, and thanks to Blackmagic it's quickly becoming the de-facto standard for raw video files. My understanding is that the difference between DNG and CDNG is just in the header information which includes specific information as it relates to video.

Of course. I don't see any reason not to aim for making CDNG-compatible DNG sequences. I already set the FrameRate tag from the CDNG spec, and IIRC there are only 3 other (optional) tags there that might be needed.

(DNGs embedded in MXF files  - the alternate format of CDNG - is a totally different story I won't be doing that.)
 
@midphase could I ask you (or somebody else) to try out the DNG sequences being produced currently in Premiere Pro (which I don't have access to) and tell me what doesn't work or what needs adding? I've already tested in Resolve 10 and After Effects and they seem to import the sequences ok.

[aace]

Is there a change log I can reference somewhere? I'm trying to keep track of the progress of this app. Which is awesome by the way.

[DavidSh]

 

@midphase could I ask you (or somebody else) to try out the DNG sequences being produced currently in Premiere Pro (which I don't have access to) and tell me what doesn't work or what needs adding? I've already tested in Resolve 10 and After Effects and they seem to import the sequences ok.

You get an error message after importing, saying:
The file appears to have no media data.

Premiere do not know how to handle DNG, only CDNG

Hope it helps...

Best

[andy kh]

yeah premiere doesnt support dng files

[chmee]

@baldand
the mystery behind cdng for premiere are not really the cdng-tags, but debiasing and maximizing values. possibly the delinearizationtable from bmcc-files can help. AND: of course the dng-files should be converted to 16, 12 or 10bit, because 14bit is no typical video-bitdepth, only supported by resolve (and acr as a photo->converter)

https://infogr.am/bmcc-delinearization-curve?src=web
and
http://www.magiclantern.fm/forum/index.php?topic=7122.msg105445#msg105445

regards chmee

[ItsMeLenny]

Is there a change log I can reference somewhere? I'm trying to keep track of the progress of this app. Which is awesome by the way.

All changes https://bitbucket.org/baldand/mlrawviewer/commits/all

[gary2013]

noticed:
mouse cursor disappear after resize application window.

I also saw that happen here yesterday trying the latest 1.1.2 ver on my win 7.

[baldand]

@baldand
the mystery behind cdng for premiere are not really the cdng-tags, but debiasing and maximizing values. possibly the delinearizationtable from bmcc-files can help. AND: of course the dng-files should be converted to 16, 12 or 10bit, because 14bit is no typical video-bitdepth, only supported by resolve (and acr as a photo->converter)

https://infogr.am/bmcc-delinearization-curve?src=web
and
http://www.magiclantern.fm/forum/index.php?topic=7122.msg105445#msg105445

regards chmee

Thanks chmee. That should be enough info for me to work out what's needed for Premiere. I expect it's the 14bit data. I can easily make an option to pad to 16bit (though that will waste disk space)

[KMA_WWC]

Baldand, this is quickly turning into an ultimate tool for ML users. Just want to say huge thanks for both making this awesome software and supporting it. Many people started, but many never finished and left their creations raw and unusable (I'm talking about some converters on this forum). Besides fixing bugs you add new features. Incredible! I really appreciate your, devs and simple user contribution work on this forum.

Keep up the great work and can't wait for CDNG 16bit format option.

[arrinkiiii]

Yes indeed. Some app that do the conversion  from MLV to CDNG and import directly to Premiere will be the ultimate tool !!!

[MA Visuals]

When I use the "A" key to desqueeze my 1920 x 672 (60p) footage, the 1.4x de-squeeze is not enough to reach a vertical height of 1080.  I believe you would need a 1.61 (1.6072 to be more precise) vertical stretch in order to bring the vertical height from 672 to 1080.  Would it be possible for you to add 1.61 as another vertical stretch factor when toggling using the "A" key?

[ATP]

Wow, what an amazing update Baldand  !

[ItsMeLenny]

When I use the "A" key to desqueeze my 1920 x 672 (60p) footage, the 1.4x de-squeeze is not enough to reach a vertical height of 1080.  I believe you would need a 1.61 (1.6072 to be more precise) vertical stretch in order to bring the vertical height from 672 to 1080.  Would it be possible for you to add 1.61 as another vertical stretch factor when toggling using the "A" key?

The problem here is it would change between cameras. (Replying as I was the one who put it in, and I based it off the squeeze that the camera claimed).
Let's work it out

Camera	Max 1080	Max 720	Squeeze
5d3	1920x1280	1920x672	1.9x
6D	1808x1216	1792x568	?wat
650D	1728x1150	1728x694	1.657x
7,60,600,550D	1728x1156	1728x694	1.66x

well in that case, it probably should be 1.6x. No idea who suggested 1.4x (maybe it said it in camera), i was just doing what the people wanted!!!!

[Midphase]

Thanks chmee. That should be enough info for me to work out what's needed for Premiere. I expect it's the 14bit data. I can easily make an option to pad to 16bit (though that will waste disk space)

That's the way RAWMagic handles it, but despite all the CDNG files being 16bit, Premiere still reads the files wrongly (they will import and playback, but there is a nasty pink overcast on all the footage which makes it kinda unusable).

Something is going on with the way Premiere is reading files generated by the Blackmagic Cameras vs. the files generated by ML CDNG.

PM me if you want me to give you some Blackmagic CDNG files to study.

[andy kh]

That's the way RAWMagic handles it, but despite all the CDNG files being 16bit, Premiere still reads the files wrongly (they will import and playback, but there is a nasty pink overcast on all the footage which makes it kinda unusable).

Something is going on with the way Premiere is reading files generated by the Blackmagic Cameras vs. the files generated by ML CDNG.

PM me if you want me to give you some Blackmagic CDNG files to study.

problem solved with raw2cdng

[a1ex]

5d3

1920x1280

1920x672

1.9x

Wrong. LiveView coverage at 1080p is not identical to 720p, and the exact behavior is camera-specific.

Some better approximations are here, but I can't bet on them: http://www.magiclantern.fm/forum/index.php?topic=6215

[baldand]

That's the way RAWMagic handles it, but despite all the CDNG files being 16bit, Premiere still reads the files wrongly (they will import and playback, but there is a nasty pink overcast on all the footage which makes it kinda unusable).

Something is going on with the way Premiere is reading files generated by the Blackmagic Cameras vs. the files generated by ML CDNG.

PM me if you want me to give you some Blackmagic CDNG files to study.

I got hold of PremierePro for testing and I have the basics working now thanks to chmee's tips. All that was needed was 16bit DNG, a non-default LinearizationTable (PP seems to need this even though it *should* be optional - surely Adobe's bug) and BlackLevel/WhiteLevel tags to be Short instead of Long (another Adobe bug - both Long and Short are allowed in the DNG spec).