Messages

Thanks. Though I've worked with it, I don't use Resolve in my workflow at the moment.

The raw2Cdng frame here is the 16b flavour – but it [the moire, ca, artifacts] is also present in a 12b file, to the same degree.

Why should the raw2dng version allow ACR to process the moire artefact so much better?

Looks like moire artefacts to me.

Thanks. But if that were so, wouldn't it be present on *both* dngs? These are two types of dng from the *same* raw file – both processed through ACR!

It doesn't make sense to me...

**This shot was a test shot – deliberately overexposed by +1.5 stops. It pulls back fine in ACR.**

@a1ex Thanks. If I post them would you [or someone else] be able to have a look please? Bear in mind that they are two dngs created from one identical .raw file!

https://dl.dropboxusercontent.com/u/21590714/raw2dng.dng

https://dl.dropboxusercontent.com/u/21590714/raw2Cdng.dng

Here's hoping!

@g3gg0 Thanks for responding.

But if I've not misunderstood the whole process, the debayering is performed by software which produces a visual raster (in this case ACR). So why are these files [both in this example being processed identically by ACR] showing very different levels of debayering artifacts? Or is it instead down to the .raw > dng converter method, into which the debayering is already 'pre-baked' to the dng/Cdng?

I've confused myself!

Please look at the colour artefacts on the water ripples below.

https://dl.dropboxusercontent.com/u/21590714/raw2Cdng.jpg

https://dl.dropboxusercontent.com/u/21590714/raw2dng.jpg

Is it CA or is it something different? Does anyone know how to fix it?

I see it more heavily in C-dng, and Cineform-raw [through raw2gpcf] – but almost non-existently in 'normal' dng processed from .raw through ACR.

If anyone can help I'd really appreciate some [more] expert eyes on this!

Many thanks.

5DMkII - These shots 1880 x 1058 23.976, taken on a.d. build 4.10.13

The -lx and -dx switches set log-curve and debayer parameters respectively, but I'd rather direct you straight to the man (Dan Newman) who created the app offer his insight here:

http://www.magiclantern.fm/forum/index.php?topic=5479.msg40941#msg40941

@jonnyginese You may already know this: if you use the 'raw2gpcf' on the command line you can set up all your own custom switches for output to Cineform; say:

raw2gpcf D:\Source.raw E:\Output.mov -444 -l400 -d2 -q5

etc.

@chmee raw2cdng gui reports the dimensions as 1880 x 1058

@chmee Good news about the xmas version! Can it have chocolate, brandy and cream included?

So model ID/no model ID seemed to make no difference to the chromatic aberration issue. I did notice something odd though: Mac OSX finder window reports all my dngs from raw2cdng as being dimensions: 1864 x 1042, whilst all other tools (RawMagic, raw2dng, etc.) report them as 1876 x 1054 (I shot at 1880 x 1058 ad build 4.10.13)

Odd! Could this be a clue?

Thanks again.

rgds

@chmee Thank you for v1.4.8! I have much better results now in 'Partymode' and Gamma 1.0 getting rid of the pink going into PPro 7.1

Something else I have noticed is this chromatic aberration (?) in Cdng. I don't see it in straight dng. Two 100% crops from the same .raw file to illustrate here (You can see it clearly on the ripples):

https://dl.dropboxusercontent.com/u/21590714/raw2Cdng.jpg

https://dl.dropboxusercontent.com/u/21590714/raw2dng.jpg

Where is this coming from?

If this is old ground already covered / fixed, I do apologise!

rgds

PS Both the files here were debayered in ACR from the original .raws and then cropped.

**UPDATE**

Not sure that exporting the .look file from Speedgrade works as intended for some reason. :?

What does work for me (as a shortcut) is saving the entire ColourCorrection roundtrip as a 'Preset' file back in PPro.

Here's my preset if you want to try it.

https://dl.dropboxusercontent.com/u/21590714/MLraw_DePink-FirstCC.prfpset.zip

PS It even works if you add it as an Adjustment Layer over multiple clips on the PPro Timeline.

chmee's app has crashed before; but it's working for me now thanks to his latest fixes. I've had the best results with either 12b or 16b linear. Try turning the Unique ID checkbox off also (if you don't need it).

I guess there are so many variables between each person's image files it's hard to troubleshoot this, but if it helps:

– Mine were shot in standard ML.raw

– You can download my .look file I created in Speedgrade.

https://dl.dropboxusercontent.com/u/21590714/MLraw_PP-SG_PrimaryCC.zip

I hope it helps!

timbytheriver

While we await Adobe's own official patch for the pink-cast cdngs in PPro (and/or green-cast in Speedgrade) I'd like to share my own workaround.

I understand that PPro and Speedgrade are probably doing something funky together under the hood (shedding some bits somewhere?) but I think I can live with this for now, and the quality of the raw file seems to hold together to export.

You can see the before and after of my PPro > SGrade here:

https://dl.dropboxusercontent.com/u/21590714/Lum_off.jpg

https://dl.dropboxusercontent.com/u/21590714/Lum_on.jpg

The whole flow is this:

1) Export the MLraw Cdngs from either RawMagic (Mac) http://www.magiclantern.fm/forum/index.php?topic=6218.0
or chmee's newest Raw2Cdng (Win) http://www.phreekz.de/wordpress/2013/06/magiclantern-raw2cdng-cinema-dng/
2) Import files into PPro. They'll all look pink! (yuk)

** Here's where I stumbled on what eventually 'fixed the pink' for me**

3) Add a 'Lumetri' effect in PPro (Effects > Color Correction > Lumetri) It will prompt you to open a LUT/Look file. I experimented with a whole bunch until I came on one that ships with Speedgrade. It's called 'Canon 5D - SL - PROFILE.cube' *

4) Load this LUT onto a clip(s) and it will immediately flatten and de-pink the clip(s).
5) Now send the project directly to Speedgrade (DirectLink)
6) Project will open in Speedgrade with the LUT in place.
7) Add Primary correction layer(s) and correct for Lift, Gamma, Gain, Saturation etc.
Send the project back to PPro...
9) The clip should hold the correction in place.
10) Continue editing and going back and forth between PPro > SGrade
11) Do your final export / render from PPro.

NB If you want to toggle the correction on/off in PPro, simply select the clip on the timeline > Effects > toggle the Lumetri fx on or off.

For me the benefit of using the PPro/Speedgrade workflow is that even a modestly specced machine can playback Cdngs in realtime Full HD, unlike Resolve (sophisticated though it is), which needs an impressive Mac and a bunch of RAIDs to make it behave properly.

I'd be interested to hear whether anyone else has success with this workflow; or whether I've simply dreamt it all!

Good luck! And thanks Magic Lantern, RawMagic, @chmee, and err... Adobe!

timbytheriver

* On Mac this can be copied from Applications/SpeedgradeCC/Speedgrade.app [Show Package Contents] Contents/MacOS/Lumetri/LUTs/ to say Desktop for loading.

Canon 5DMk2
ML raw build 10.9.13

Sorry! Stoopid of me. Here it is:

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01:   raw2cdng.1.4.5.exe
  Problem Signature 02:   1.0.0.0
  Problem Signature 03:   52911779
  Problem Signature 04:   raw2cdng
  Problem Signature 05:   1.0.0.0
  Problem Signature 06:   52911779
  Problem Signature 07:   5c
  Problem Signature 08:   4ba
  Problem Signature 09:   System.NullReferenceException
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:   2057
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

@chmee Thanks for the link. The drag and drop fix mentioned there didn't work for me.

This time I ran the app I got a crash report. Does it say anything to you?

https://www.dropbox.com/s/sf70khxpv9qgb06/grab2.jpg

Thanks again.

Thanks for the reply!

Win XP is showing the 'Windows has encountered a problem and has to close' box

Win7 just fails to process the files (an empty folder is created, but no green progress bars) when I press the 'convert' button

Thanks chmee!

Unfortunately, v1.4.5 is still not processing any file and/or crashing for me Both on Win 7 and XP. If I try running as 'Admin' on Win7, the drag and drop does not work!

I'm running on Virtual Box on Mac OSX10.7.5 – but as I mentioned before all previous/early versions of your app have worked perfectly on it!

Any ideas please chmee / anyone?

Many thanks

Hi Chmee

Here's some of my debugging info if it's useful:

* Metadata for White Level (16383) I think is wrongly reported. Should be 15000 (?) All other is correct (frame rate, body etc.)
* I use ML build from 10.9.2013
* Not using mlv.
* I don't know what 'stripped' means! 

Screen grab of my Win 7 (It's running on Virtual Box on Mac OSX 10.7.5. All previous versions of your app have worked perfectly on this same setup!)

https://www.dropbox.com/s/96nu51crl0d3sbo/grab.jpg

Thanks again for your help.

My old Juicedlink CX231 preamp was a lovely little box – very quiet, but a little heavy and 'boxy'. 

However, I've had recent success using this as an alternative system: http://www.dslrfilmnoob.com/2012/11/25/irig-pre-hack-cheap-xlr-phantom-power-preamp-dslr/


With my AT875r mini shotgun mic (which has a slightly 'hot' output) the noise floor is indistinguishable from the Juicedlink. For a lightweight run-n-gun setup I've found this to be a great little setup.

UPDATE: I should add that I use this for recording directly into my 5dmk2 – not with a separate audio recorder; I don't see why it couldn't work that way though...

@Chmee

Thanks for answering. It does appear in the list. But then when I press the button, the list entry turns red but doesn't process. The dng folder is created – but no files inside.

Also I'm really not sure what to put in the 'Unique model' box! Do you have an example I should use for my 5dMk2 please?

Thanks again for your work!

[raw2cdng 1.4.0.Beta online]

raw2cdng 1.4.0.Beta online

http://www.phreekz.de/wordpress/2013/06/magiclantern-raw2cdng-cinema-dng/

Hi Chmee

Sorry to be a dunce, but I don't know what I should put in the 'Unique Model' field. Also, when I try to drag a Raw file in, the app does nothing (all paths are set etc.). All previous versions of your great app have worked perfectly for me! Do I need to uninstall them first maybe?

Any idea what I'm doing wrong?

Many thanks

Win 7
5DMk2
Speedgrade / Premiere Pro

Hi ShootingStars

I would investigate GoPro/Cineform as your intermediate 'codec'. You can edit [virtually] visually lossless files on your laptop without using much processor power. The codec itself is professionally highly regarded – but their software can be a bit flaky. :/

I'd recommend encoding MLraw (or even H264 will benefit) > Cineform. Then you can edit these files easily in something like Premiere (on Windows). If you choose a high enough quality of Cineform encode you can avoid round-tripping; Grade in your favourite application, and then edit out an 'online' edit straight out of the Cineform files to your chosen finished export flavour.

It can be a bit of a confusing workflow to start with, but I'd say it's well worth the time and effort learning it if you have limited hardware power.

Have a look here for a start: http://cineform.com/technology

timbytheriver

I'm confused by this. The lossless option seems to give me much smaller conversions than lossy, which is opposite to what I was expecting.
Eg for a file I've just converted:
RAW - 640mb
normal - 647m4
lossy - 389
lossless - 183mb

Is it possible the buttons in the batchelor UI are labelled backwards?

Thank you Fatpig for making this great tool available to us! I can also confirm the findings of Mei Lewis as above. I opened each file in RawDigger to find that the one output as 'lossless' was Full-Res, Lossy-JPEG, 8 8 8 bits whereas the one output as 'lossy' was Full-Res, JPEG, 16 bits.

Could it be the labels are indeed backwards?

Thanks again.

Tim

@fryderykp et al

Hi from a first poster,

I too have been keen to develop a reliable exposure strategy for ML-raw. It takes a lot to separate me from my manual spot-meter (Pentax) – but I'm learning to love the (raw) histogram in ML-raw

So, from my 'scratch' tests with 5DMKII on build 10/9 I have observed that shooting with ML-raw can probably capture about 11.9stops of scene dynamic range. It appears to be distributed approx -9 under, +3 over; with a standard grey card setting the 'correct' exposure.

I've observed a bright cloud-filled sky full of zebras; and the three rgb 'dots' of the histogram at about 1,3,1 – and still been able to pull back detail from the highlights in either ACR or Resolve.

For me (so far) I've established that if I want to use my spot-meter, I can meter a grey card in the key light and safely (I would say preferably) overexpose by up to +1 and 2/3stops. This seems to fit in with the old negative-film advice to 'expose for the shadows – and print for the highlights'.

I initially tried shooting at 100ISO in this way and the shadows were pretty noisy, so I've also found that the shadow noise was improved by using a higher ISO (400) when overexposing in this way, and for the scene I described.

These are merely what my eye tells me. I'm not a pixel-peeper or maths man; I'll leave that to the good people here who've made all this exciting magic happen. Thanks developers all!

Tim

5DMkII
build 10/9/13
Komputerbay 64gb 1000x
Stable continuous 1880 x 1058