So you see a DAM-based cultural heritage system can have very much to gain to use DNG instead of TIFF that most people might not be aware of. Then for example when someone would like a download of a big JPEG or the DNG the system can automatically pick the XMP-masterdata from the smaller files before the file is sent to the one asking for it. The last files might be as small as 1080 or 1024 just to archive max system performance when people are querying the system. In an automated workflow like the one I have experiences from building one RAW-based DNG could automatically generate one RAW-DNG (as is), a full size JPEG kan be automatically extracted fron the DNG and stored among all the other full size JPEG-files and a smaller preview that carries the master XMP-metadata can also be made automatically. It´s not just that the files are three times heavier than RAW-based DNG, I have also learned that TIFF-files has a more inefficient handling of metadata than DNG and JPEG that have special headers for XMP which TIFF is lacking, Updates are more inefficient of that reason.Ī DNG can both contain the RAW-data, a developed JPEG that is not just a small preview but a JPEG delivery file developed just the way the photographer intended and on top of that the XMP-metadata. No one that can avoid it will handle TIFF in a DAM-workflow. In enterprise DAM-systems you can do a lot of clever things in automated workflows that you can´t do with TIFF. My advice, just use TIF as you will not be able to use DeepPrime and you will not lose anything by not using DNG.ĭNG has other properties too that most people are not aware of.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |