While exploring the functionality, I created a few HDR files in darktable.
First I was surprised to find that the created DNG files could only be opened in darktable. All the other programs I tried showed a black surface with many differently colored dots. Is this a known phenomenon?
Everything else worked like with normal raw files, except the exporting to jpg (exporting to tiff works fine).
Sometimes, with some edits, darktable just drops out of memory with no message, except for an entry in the log file (Magick: caught exception 0xC0000005 “Access violation”…). To make things complicated, it happens only with some edits (i. e. xmp files).
Sometimes with one HDR-DNG file one edit exports fine, and the other causes dt to crash. This has never happened with regular raw or tiff files.
Has anybody experienced something similar - maybe there is a possible solution?
Such issues have come up a few times, with that "Magick: caught exception 0xC0000005 “Access violation”. And only under Windows, afaik. Tthe dt FAQ might help?
Thank you for your reply!
I checked various “Processing” settings (performance, Open CL) in various combinations. They have no influence on this behaviour, i. e. darktable crashes regardless of these settings.
Thank you for your reply!
At first I also thought the issue is in the other applications, but it is strange that all the applications I tried (see the list below) exhibited the same behaviour. It is difficult to assume, that all these applications are doing something not conforming to the DNG specifications.
here the list (some free/open source and some commercial):
I think the relevant part is about the openCL compatibility app, which seems to be automatically installed in certain cases. Some managed to get rid of the problem by removing that app.
I’m not sure what the effect of disabling openCL in darktable would be, but for mlost of the other settings I wouldn’t expect any influence on the behaviour in this respect.
One of the XMP files causes the crash, the other does not.
Btw. how do i associate a XMP to the particular image (raw, dng, tif, …) file in case of multiple instances?
two interpretations of the question… We’ll see what OP meant to ask
A bit more serious, if indeed you want to apply a sidecar to an image, that not all operations can be applied to non-raw files. I have no idea what happens when you apply a sidecar for a raw file to a jpg…
Can you try updating the WhiteLevel tag and try again in other software please? Something like exiftool -IFD0:WhiteLevel=1 Vrsic_181104_135633_0067_J_R00-hdr.dng? (Note that a backup .dng_original will be created.)
I believe there is a bit of a misunderstanding here. Perhaps my question regarding the xmp file identification has not been clear enough.
I have three files on the disk:
Vrsic_181104_135633_0067_J_R00-hdr.dng
Vrsic_181104_135633_0067_J_R00-hdr.dng.xmp
Vrsic_181104_135633_0067_J_R00-hdr_01.dng.xmp
When viewed in dt lighttable I have two images (duplicates) with different editing. Both images (in lighttable) have the same name. How do I identify which XMP file belongs to each of the images in lighttable?
The original file gets whatever.ext.xmp; subsequent duplicates are given increasing numberic suffixes, the first duplicate being 01, the 2nd 02 and so on. Even if you remove (delete) duplicates, the numbering carries on, so it’s possible that you end up with whatever_05.ext.xmp and whatever_10.ext.xmp on the disk, if you removed everything but the 5th and 10th duplicate.
two interpretations of the question… We’ll see what OP meant to ask 