Quantcast
Channel: Adobe Community : Popular Discussions - DNG SDK
Viewing all 4036 articles
Browse latest View live

Creating a DNG from scratch.

$
0
0

Hi,

I'm trying to save camera raws(16 Bit Bayer pattern) I grab directly from an industrial camera in the DNG format.

By looking at http://fossies.org/dox/digikam-2.5.0/dngwriter_8cpp_source.html#l00188 - the only example I could find online - I have been able to create a file which Photoshop & co are able to read. However I had to do some guesswork. Specifically I had to specify a profile with the following lines:

 

prof->SetColorMatrix1((dng_matrix) matrix);

prof->SetCalibrationIlluminant1(lsD65);

negative->AddProfile(prof);

dng_vector camNeutral(identify.rawColors);

for (int i = 0; i < identify.rawColors; ++i)

{

    camNeutral[i] = 1.0/identify.cameraMult[i];

}

negative->SetCameraNeutral(camNeutral);

 

I don't have this information. Just adding the identity matrix produces a strange tint.

 

What is the simplest way of saying "the camera sensor is linear" and "I know nothing about the color temperature"?

 

I'm thankful for any help!


Crash when creating a Lossless-jpeg compressed DNG

$
0
0

Hi all,

 

everything is in the title i guess. I work on a legacy system, using DNG SDK 1.1 (upgrading is not an option). The software was originally desgined under win, and is now ported to mac os X. When saving an image to a dng format, an exception is thrown during the lossless jpeg encoding. Do you have any idea of what it might be? What tests can I run?

 

thansk

S.

Get DNG Date Created from dng sdk

$
0
0

I have successfully compiled the dng sdk and the validate app and I wondered what is a simple way to just get the date created out?

The current DNG Profile Editor cannot interpret 7.1 raw settings

$
0
0

Hi,

 

I am frustrated that the DNG Profile Editor is not able to apply Lightroom's or Camera Raw's settings since the new Process 2012 has been in effect.

 

This SEVERLY limits the usefulness of the Profile Editor. And yes I know it is a beta.

 

However, are there no plans to release a compatible version?

 

 

Thanks,

Juan

DNG SDK cannot write files with floating point pixels?

$
0
0

I'm trying to create a DNG with 32 bit floating point pixels. The reason is to create a file which is not demosaiced but contains a large dynamic range. It goes well for the major part, but it fails in the linearization step (BuildStage2Image) when I'm generating a thumbnail. Looking into the code it seems like the floating point case is not handled, so it is easy to understand why it does not work.

 

Is this a bug in the SDK, or does not the DNG standard support floating point pixels?

 

(I'm using the latest release at time of writing, version 1.4)

 

Edit: I patched the SDK to support floating point pixels (like 4 lines of code), so it is quite simple to do. But not surprisingly it cannot be interpreted even by Lightroom.

DNG SDK thinks 0xFFFFFFFF is invalid white level for 32 bit integers

$
0
0

As discussed in another message the DNG SDK does not seem to be able to write floating point DNGs. Since I need higher dynamic range than a 16 bit sample I instead went for 32 bit integers.

 

This works, and I manage to create a file but when I run dng_validate on it it says the white level is invalid. The white level I have of course set to 0xFFFFFFFF to make use of the full 32 bit range. Looking into the code in dng_ifd.cpp where this test is made it seems like the default max white level is set to 65535.0 and the file's white level is compared against that, regardless if the sample type is 16 or 32 bit. This means that I can only make use of 16 bits of the 32 bit integer which seems kind of strange. Looking into the DNG spec I don't see anything there that forbids using the full 32 bit range of 32 bit samples. So this looks like a bug to me.

 

This is with version 1.4

 

the created file can be opened in Lightroom 4, so the only problem seems to be that dng_validate does not think its valid.

 

Message was edited by: torger76, removed clipping issue, that was a fault in my code.

How to write manipulated image back to negative?

$
0
0

Hi all,

I would like to do some simple dng raw image manipulation like black image subtraction.

 

Therfore I though I would get the stage2 image (because working on stage1 is not  correct right?) of both the main-image and the black-image and create an image "main minus black".

 

Now I want to have this image saved back as dng as if it was the main dng.

 

just setting the new image as stage2 does not work because writeDNG uses the stage1 image which is set as fRawImage in buildStage2Image.

 

Setting as stage1 does not work too because it is already a linearized image.

 

How can I reverse the linearization?

 

Or are there other way to do this correctly?

 

Thank you all and best regards

Andreas

converting RGB to DNG without affecting color profiles

$
0
0

Hi guys

 

I'm working with the DNG SDK in C++ for some time now.  I need to be able to take a raw RGB (not camera raw) and convert it into a dng file.  After playing arond with it for a few days, I realized creating the camera profile drastically affects the resulting dng image.

 

I can't seem to produce a dng file that was identical to the input source.  My picture appears very washed out and I end up using the adobe color profiler to try to bring the image back close to it's original color.

 

I'm trying to find a way to produce dng files without the need to affect the colors in any way, the resulting picture should be bit identical to that of the raw RGB input file.

 

I'm not even sure if I can do this considering the usage of the dng format.

 

 

UPDATE

I've realized that my program is loading the RGB buffer into the fData of the stage3 image object.  I have a feeling I need stages1 and 2 but i'm unsure if I need to and if so, then i will probaby need a source DNG to produce those stage1 and stage2 unless I can get stage1 or 2 from stage 3 (appears it works vice versa).

 

I'm able to do the reverse (DNG to RGB raw) by extracting the buffer from the stage3 render.  but in this case, all the metadata has been filled in by the input DNG. However, going from RGB to DNG, I don't have the metadata to fill into stage 1 and 2.


DNG/XMP AppendProperties/ApplyTemplate

$
0
0

I downloaded the latest DNG SDK (1.3) and XMP Toolkit SDK (CS6).  The DNG SDK expects "AppendProperties", while the XMP has replaced that with "ApplyTemplate".

 

I then tried an earlier version of the XMP Toolkit (4.4.2), but then multple Quicktime SDK linking problems arose.

 

Are there any DNG/XMP versions which are compatable, or method of converting the function?

 

Thanks.

Convert Raw to DNG

$
0
0

Dear all,

I'm seeking DNG SDK assistance, and I'm trying to convert our raw file(only contains metadata from the sensor) to DNG format so that we can use white balance, demosaic,vignetting and so on. But I don't know how to get start with it. Any help from the experts would be greatly appreciated.

 

Best,

 

Caigao

Installation failed: 'AppendProperties' : is not a member of 'TXMPUtils'

$
0
0

Dear all,

I’m trying to install DNG-SDK (1.3) but with no success, I have tried to compile with both XMP Toolkit SDK CC-2013.06 and XMP Toolkit SDK 5.1.2 but with the same error message:

 

error C2039: 'AppendProperties' : is not a member of 'TXMPUtils<tStringObj>'

 

Unfortunately I was not able to find XMP Toolkit SDK 4.4.2 that should solve the problem. The compiler is VS 2010 64bit.

 

Please can you give me some tips on how solve this issue?

 

Regards,

 

Hal

DNG SDK build project cannot find the xml sdk

$
0
0

On win7/x64.  Installed dng sdk and all dependencies per the readme files.  xml sdk built OK with vc10 express, as 64 bit static and dll.

But the vc solution for dng_validate has incorrect names for the xml sdk build projects, so it cannot find those components.  Specifically it looks for "..\..\..\xmp_sdk\build\vc\XMPCore.vcxproj".  the actual paths in the xmp sdk are different and longer, like "..\..\..\xmp_sdk\build\vc10\dynamic\windows_x64".  Moreover there is no XMPCore.vcxproj there.

I suppose the real problem may be that the dng sdk project is trying to build it as .net managed code, while the xml sdk was built as open code.  So I guess what I am looking for is a way to build the dng sdk open.

Compression artifacts in validate dng output - proof attached

$
0
0

I have uploaded a zip file - out.dng is the output of validate dng.

 

https://dl.dropboxusercontent.com/u/9906333/dngs.zip

 

Look at the edges of the white chair - you will see classic jpeg compression artifacts.

Note that this is the default lossless jpeg conversion only.

I used the program as

 

dng_validate -dng out.dng <input>

 

I confirmed this with a build in Visual Studio using qDNGUseLibjpg=0

 

I would appreciate the admins looking at the provided examples.

Output of stage 1 (pre linearisation) and clarification

$
0
0

hi,

 

Scratching my head on this one.

 

I have some DNG RAW files and i'm using dng_validate to explore in more detail.

 

I'm looking at all the stages of processing via outputting uncompressed tifs.

 

What i would really like to understand is the nature of the source data. When i open the file in After Effects i can see that in the 16 bit tiff file, there are only values shown from 0 to 2048. These files are supposed to be 12 bit so i would have expected up to 4096 (i have some clipping in the file to max the value).

 

After linearisation these files occupy the full 16 bit but they appear to be scaled with adjustments to the black and white point, that's fine. In other words if i take the pre linear file and use the levels i can pretty much get the same effect of linearisation.

 

What i would love to know is whether the dng_validate is outputting the exact data in the source files or whether the RAW DNGs could be floating point and the dng_validate when outputting the pre linearsation file is missing some data?

 

So how close am i to the actual data in the RAW files, are DNGs stored as integer data?

 

Really appreciate any help!

cheers

Paul

DNG SDK - What a Complete MESS !!!!!

$
0
0

Hi - and sorry for this to be HIGHLY infriendly message

 

 

I have downloaded and installed ALL latest greatest of anything pertaining to the DNG SDK -

Followed ANY read me, configure, make, make install files available there.

Installed CMAKE and everything else....

 

I am on OS X 10.9 and USE the xCODE version of Mavericks

 

I am developing MANY different things and NEVER have problems.

 

 

I have in my life NEVER exprienced something as cumbersome and clumsy as this. NEVER!!!!

 

 

I am trying to compile/build the inlcuded and generic dng_validate project. And this proves to be IMPOSSILBE.

 

Simply put. I cannot figure it out. And I cannot do more that to follow the instructions provided in the SDK.

 

 

This is incredible and I am missing the words to describe anger I am feeling.

 

 

I realize this sdk is something that adobe cares nothing about - hence all the problems adobe are having with their own apps, which arent even capable of reading DNGs correctly...

 

To whomever, maintaining this SDK ---- You are doing a really bad job at it !!!!

 

 

Regards

 

Morten


Catpture date.

$
0
0

I just want to read the capture date from a dng file. How do I do that?

Embed only mosaiced data

$
0
0

Hi,

 

I would like to embed only the mosaiced image into the DNG. Is this possible? I have tried to comment BuildStage2Image and BuildStage3Image, but with no success. So any clue will be appreciated.

 

Thank you.

I scanned a black & white negative. Can I turn it into a positive in PS?

$
0
0

I scanned a black & white negative. Can I turn it into a positive in PhotoShop?

How can i access cinemadng frame rate using the dng sdk?

$
0
0

I'm trying to figure out the right way to access the CinemaDNG frame rate using the DNG SDK --- preferably without having to hack up the DNG SDK, since that would have to be redone each time the DNG SDK changes. It looks like all the code has little loops for scanning tag directories, and when something unknown is found, it is dropped silently with no callback, so that there is no way to process out-of-scope tags such as those for CinemaDNG without replicating the original code.

 

On initial study it looks like the Cinema DNG tags, as produced by Blackmagic cameras, are DNG TIFF-like data, not as XMP-only data as the CinemaDNG 1.1 standard seems to suggest (Annex A). I suspect this is because the odds of a separate XMP file being carried around that matches the DNG images is low. Not apparent that they can be retrieved from either place.

 

So I'm wondering what the nominal Cinema DNG overlay onto the DNG SDK is. This is low-hanging fruit.

 

If the entire XMP library was to fall out of DNG and Cinema DNG, the world would be a much simpler place. Too many answers for too little problem. It's taken about a week to get the DNG SDK library to compile on Linux, with Windows still in progress and Mac to go. (cmake another non-helpful thing.... too much that does too little --- that doesn't match my build environment). KISS!

How to add bad pixels to a DNG made from a CFA sensor raw data ?

$
0
0

Hello all, I'm trying to build a proper DNG file from the raw CFA image acquired directly form an industrial camera.

As usually there are a number of bad pixels around and I would like to mark them in the DNG so they can be correctly interpolated when the image is processed.

In the latest DNG SDK (1.4) I've only found this rather thin references:

"Defective Pixels

There are two ways to deal with defective pixels in DNG.

The first is to map out (interpolate over) the defective pixels before storing the raw data in DNG.

The second is to include a bad pixel fixing opcode in the OpcodeList1 tag."

 

OK, as each program/customer/etc. seem to have its own ( best ) algorithm to interpolate the bad pixels then OpcodeList1 it is.

 

But then I've got this: FixBadPixelsConstant and I'm not clear about its usage, especially BayerPhase, is the same BayerPhase that is specified as a global property of the CFA or it is something separate and what ?

Also is there some "industry standard" value for the Constant that will make more likely the established programs to process correctly the image ?

And this Constant value is unique per DNG or can it be more ot them added, i.e. to somehow characterize the "badness" of the pixel, like reduced sensitivity, stuck at 0/max, etc ?

 

In the end if somebody can share an one-liner on how to add programatically this tag using the SDK I'll be very grateful.

 

Sorry for my newebie questions and many thanks for your help.

Viewing all 4036 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>