Digital Light & Color

I'm trialing a new work flow that involves using a dng file. When I open a file (produced in other software) in PWP (v7.01.17a) after the raw dialog process I get a striped image (see attached). Any clues?

You probably need to describe the workflow that leads from the Canon raw file to the DNG in order for someone to suggest what happened.

I just checked our DNG test files. They are working correctly. How did you generate the DNG file you were trying to open.

Kiril

Thanks for the replies Charles and Kiril, I appreciate the time you've given me.

Depending on what I want to achieve with the image I also use DxO Optics Pro and newly Capture One (C1). I usually finish the process in PWP. Normally I can work with Tiffs but the Tiff files generated from the Canon 5Ds raw files are about 300 MB! whereas the DNG's are less than half this. I can see my 5 terabytes of disk space being eaten up!

I've done some more testing (the DNG's were generated from raw files without any adjustments on my part):

These are the results from various workflow permutations:

DxO--->C1 = OK

C1--->PWP = OK

DxO--->PWP = stripe problem

C1--->DxO--->PWP = stripe problem

DxO--->C1--->PWP= won't process at all

It would appear that the problem lies with the way DxO generates the DNG files. (The DxO DNG process is out-only so I think that they are happy to be the first in line but not a receiver.)

I haven't (and won't) try this with Light Room or Photoshop.

Oh well disk space is relatively cheap and I just need to be prudent with the space I have.

Thanks again.

Here's a long shot you might try. Save the huge TIFF file and open it in PWP. Put it through an inconsequential transformation or two, for example, resize by taking one pixel off a dimension, or add a border and in a second step crop it off. Save the result and see whether it is smaller.

Thanks Charles.

I've tried that and a couple of other with no success.

It seems as though I'm stuck with tiffs.

Thanks, we have a DNG file that does not open correctly (pretty much any DNG that DXO generates apparently) -- it turns out the problem is within dcraw and we have relayed the problem to Dave Coffin who maintains it.

Thanks Jonathan.