What happens when you try to render the proprietary data in the embedded file and a converter is not available? It seems like you are adding a layer of obfuscation for the sake of 'future proofing'.
It would seem that converting to the actual open standard would be safer if you were really concerned about file compatibility in the future. On Thu, Jul 12, 2012 at 3:07 PM, George Sinos <[email protected]> wrote: > The ASMP has had this website up for quite some time. They seem to > keep it up to date. It's a good reference when you're trying to come > up with a good workflow. > There is a lot of information here. > > <http://dpbestflow.org/> > > Here's an interesting entry on DNG files. > > "The DNG format preserves the original raw sensor data just the same > as the proprietary raw files. Nothing is left out. DNG is a safer > archival container for several important reasons. The first is that it > is a documented format. Its specification is openly published and how > DNG files are constructed is openly shared with other software > vendors. > > The second reason is that, unlike any other raw format, DNG contains a > file verification tool known as a "hash" that can tell if the raw > image data remains unchanged and uncorrupted. This hash only > references the raw image data, so a DNG file can be processed an > infinite number of times and the XMP instruction set(s) and embedded > JPEG preview(s) can be redone an infinite number of times, but the > underlying raw data does not change, so it can continue to be verified > forever. > > One disadvantage of DNG has nothing to do with the format itself but > has to do with the number of software vendors that choose to support > DNG. Since not all do, DNG files cannot be processed in every possible > raw file processor out there, especially the camera manufacturer's > software. > > DNG can, however, contain even the proprietary raw file within the DNG > container, so if this is a concern, you can choose to save your DNG > files with the proprietary raw files embedded. The file verification > hash will then also protect the proprietary raw data as well as the > DNG raw image data. > > This, in fact, is currently the only way to verify proprietary raw > files. DNG files can sometimes be smaller than proprietary raw since > DNG uses a very efficient lossless compression scheme on the raw image > data. DNG files can be the same size or slightly larger than > proprietary raw if they contain full size JPEG previews. DNG files can > be twice the size of proprietary raw if the proprietary raw file is > optionally embedded." > > gs > > George Sinos > -------------------- > [email protected] > www.georgesphotos.net > plus.georgesinos.com > > > On Thu, Jul 12, 2012 at 1:55 PM, Godfrey DiGiorgi <[email protected]> wrote: >> On Thu, Jul 12, 2012 at 11:12 AM, steve harley <[email protected]> wrote: >>> on 2012-07-12 11:29 Godfrey DiGiorgi wrote >>>> It's up to the user to manage their original files. >> >> "Original files" means the masters used in the editing system, not >> what's on the camera storage card. What's on the camera storage card >> is irrelevant in the context of the editing system except as a source >> for importing. >> >> The sensible way to manage your original files for use with Lightroom, >> Aperture or any other image processing system is: >> >> - Create an image repository rooted in a single directory on a >> per-volume basis. >> >> - Inside that repository, create subfolders structured by whatever >> mnemonic is most sensible to you ... dates, categories, jobs, clients >> ... whatever works. >> >> - Define a system of subfolders in the image repository germain to >> your editing tools through which to migrate your work. For a >> Photoshop/Bridge workflow, this is often a series of subfolders based >> on a project or job such as "picks", "work in progress", "editing >> completed", "output for use A", "output for use B", etc. For >> applications like Aperture and Lightroom that include image management >> functionality, you normally do not do this in the file system >> directly, you use tools internal to the app for this, that is, a >> defined progression using "collections", "albums", labeling, rating >> stars, etc. >> >> - Backup and archive the original files by replicating the entire >> image repository to an another storage location, preferably twice >> (good data security policy is one working copy and two backup copies). >> Keep it up to date, do it regularly ... automated >> backup/synchronization tools are best for this. For apps like Aperture >> and Lightroom, also include in the backup schema the .aplibrary file >> (Aperture) and .LRDAT file (Lightroom). This preserves all the editing >> and annotation work, and the history and state of all your files. >> >> It's the same four points to managing your original files, no matter >> what image processing system and tools are used to do the work. >> Whether a particular tool has automated part of the tasks for you or >> not is a convenience. >> >> The underlying need is to learn the tools you want to use well, design >> a configuration and a set of policies to achieve what you want, and >> then use them consistently. >> >> Godfrey - godfreydigiorgi.posterous.com >> >> Announcing "Ways Together" .. my new photo book! >> See it on Blurb at http://www.blurb.com/user/GDGPhoto >> >> Come to the reception and book-signing: >> ModernBook Gallery >> 49 Geary Ave, San Francisco, CA >> August 2nd, 5:30-7:30 pm >> >> -- >> PDML Pentax-Discuss Mail List >> [email protected] >> http://pdml.net/mailman/listinfo/pdml_pdml.net >> to UNSUBSCRIBE from the PDML, please visit the link directly above and >> follow the directions. > > -- > PDML Pentax-Discuss Mail List > [email protected] > http://pdml.net/mailman/listinfo/pdml_pdml.net > to UNSUBSCRIBE from the PDML, please visit the link directly above and follow > the directions. -- David Parsons Photography http://www.davidparsonsphoto.com Aloha Photographer Photoblog http://alohaphotog.blogspot.com/ -- PDML Pentax-Discuss Mail List [email protected] http://pdml.net/mailman/listinfo/pdml_pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
