Re: DNG Metadata
Re: DNG Metadata
- Subject: Re: DNG Metadata
- From: Andrew Rodney <email@hidden>
- Date: Tue, 17 Jul 2007 14:28:17 -0600
- Thread-topic: DNG Metadata
On 7/17/07 2:14 PM, "Fleisher, Ken" wrote:
> If I change any of the settings then proceed to ³open² the file into
> Photoshop, it seems that the new settings are written to the DNG file that I
> just openedeffectively overwriting my embedded settings even though I never
> told it to save anything. The next time I open the DNG file, the changes are
> what appear in the RAW dialog, not my original settings.
The original instructions are over written yes. As for the embedded JPEG,
that depends (you actually have to force an update if that's what you're
asking about). There's a command to do this in CR, and now this can be
accomplished in LR 1.1 called Update Metadata and DNG Previews (not V1.0).
> Does this behavior make any sense to anyone? Is there a preference
> controlling this that I¹ve overlooked?
In LR you could go to Develop, History and go back in time, re-write a new
rendering to the DNG and update the preview if desired (or not).
Note that when you 'open' a raw in Photoshop, you're asking for rendered
pixel based data from the Raw and last set metadata instructions. The DNG
isn't affected. You can go back and alter the instructions and build a new
rendered pixel based document if you wish. This is accomplished using a
Virtual Copy or you could just go back in History and render out a new image
using those instructions. So open isn't really opening, its building a new,
pixel based document where none existed prior.
Where I'm not thrilled about CR and LR is handling of existing rendered
images using metadata. For example, its possible to build a set of
instructions to make a JPEG look Grayscale. Until you tell LR or CR to
'open' or build a new set of pixels, the original instructions are embedded
but should anyone open that JPEG in another application, they don't see the
edits you just made. That's really odd in my book. I also don't like the
behavior whereby if I 'edit' a JPEG in CR, it forever wants to open in that
module. In a way that kind of makes sense, you're asking for metadata edits.
Frankly, I think CR should have stuck with just raw processing and left
rendered images alone. In the old days, when you double click on a JPEG or
Tiff, it opens in Photoshop proper. Now it might open in Photoshop or CR
depending on your preferences or the how the rendered image was previously
handled. I find that confusing.
Andrew Rodney
http://www.digitaldog.net/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
| References: | |
| | >DNG Metadata (From: "Fleisher, Ken" <email@hidden>) |