I'm Confused

(5 posts)
  • garysibio
    Member

    I know if I edit an image, the original is copied to a folder named [Originals]. Now I make a change to the image. Does the image file actually change or is the alteration I made stored in a third file which gets reapplied to the image file every time I look at it?

     

    If it is the second option and there is no real change to the image file itself, why do we need a copy in the [Originals] folder? Why not just have an 'undo all changes' option? Also, what happens if I upload an image to SmugMug or Flickr or just email it to somebody? What are they going to get?

    Posted On October 11, 2009 - 05:21 PM (1 month ago) (Permalink to this post)
  • LV_Bill
    Member

    Garysibio said:  Does the image file actually change or is the alteration I made stored in a third file which gets reapplied to the image file every time I look at it?

    For Non-raw images (Jpegs, Pngs, etc.) processed in Develop mode, what you "see" does not get re-created on-the-fly.  It's an actual edited output image, not a "preview".  Your original image and the parameters of your changes (XMP file) are moved to the [Originals] folder.  A new edited version of your image is created in your initial folder - so you're always viewing the latest edited version of your image.

    Later changes update only the XMP file - your original NEVER changes.  With each later change with Develop, a brand new image reflecting your latest changes is created in the initial folder by re-processing the XMP file with your original image.  So, there is never any re-saving of Jpegs to worry about.  In fact, as long as you stay within Develop, the old need to switch Jpegs to a lossless image format is no longer necessary.

    Hope this helps, Bill

    p.s.  Many Forum members have requested the ability to "Turn off" the [Originals] folder - leave the XMP files in the initial folder - and, re-create the visible edited image on the fly.  You'll find this in many other threads referred to as "Treat Jpegs like Raw". 

    Posted On October 11, 2009 - 06:04 PM (1 month ago) (Permalink to this post)
  • garysibio
    Member

    So, if I make some changes to the original and save it, then come back to it the next day and make some more changes and upload the image file to Flickr, I will really only be sending the changes I made the first day since the second day's changes are only stored in the XMP. Is that correct? If so, how does that make any sense?

     

    If I take an image file and use 'Save as ...' to save it under a new name, does ver 3 see the new file in the same way it would a file that I had just imported from a memory card?

    Posted On October 12, 2009 - 06:15 AM (1 month ago) (Permalink to this post)
  • LV_Bill
    Member

    The changes are cummulative, of course.  And, each time you add more changes, the XMP file is updated and a new finished image is generated.  You can do this as many times as you want.

    Posted On October 12, 2009 - 06:29 AM (1 month ago) (Permalink to this post)
  • It's like Bill says.

    The big advantage if you only use Develop mode is that you can "process" a Jpeg image in stages over a number of sessions (adding further steps, or changing your mind about something you've already done), but the Developed image (the Jpeg in the main folder) is always just one stage away from the original (i.e. the image is completely re-processed, starting from the un-amended original, each time you click "Done").

    If you try to do this sort of thing in previous versions, or by using Edit mode in Pro v3, the only choices you have are to add further processing to an already processed image file (what I call "chain editing", which leads to degradation of quality, Jpeg artefacts, etc) or scrap your edits and start all over again from the original. With Pro v3, as long as you just use the features available in Develop mode, having to make such a decision should be a thing of the past.

    Posted On October 12, 2009 - 01:07 PM (1 month ago) (Permalink to this post)

Subscribe to this topic via RSS

Reply

You must log in to post.