Date Management

(10 posts)

Tags:

  • What is according to you the best way to manage the pics date(s) in ACDSee as there are do many different dates that can be attached to a same pic ?

    What is the best way to keep the orginal date and time when the picture was taken ?

    The date created, if kept as it is now, being hte date when the file is first uploaded to the PC is partic ularly misleading. Would you advise to use a Set Time Stamp or Batch Set Information function to set the created date to the date the picture was taken ?

    Posted On December 22, 2008 - 07:00 PM (11 months ago) (Permalink to this post)
  • Marc Sabatella
    Moderator

    When the picture is taken (with a digital camera) or digitized (with a scanner), the camera/scanner automatically inserts the date into one or more of the EXIF fields (camera date/time, date/time original, date.time digitized).  I think most devices set all three to the same date, although I'm sure there are some that for whatever reason would only set one or one two, or would set them differently, so check you own images to see what your camera is doing.  I think Date/Time Original is the one most people rely on.  None of these dates would ever change unless you explicitly change them, and they definitely the most foolproof way to find the date an image was made.  Assuming, of course, you had set your camera to the right time in the first place.  If not, these are the fields you want to correct as soon as you discover the discrepancy.

    I have ACDSee set up under Tools->Options->Database to automatically set the Database Date to the EXIF date on import.  So actually, rather use the EXIF date directly, I actually use the Database Date for most operations (such as sorting by date, etc), to display in the status bar, etc).  No particular reason, except that if/when I ever do need to alter the dates of a bunch of files because of some problem with the camera's own clock (or my forgetting to set it correctly), it is fast and easy to change the database dates of a bunch of files, then batch copy that value to EXIF.

     

    Posted On December 22, 2008 - 07:25 PM (11 months ago) (Permalink to this post)
  • NA
    Inactive

    It seems to be the editing software that ultimately controls the EXIF Camera Date:

    Attached Image:

    Note the different "Camera Date" as compared to the other two dates, also the software identifier "ACD Systems..."

    "Camera" my foot; a snafu in the EXIF definition?

    Attached Files

    1. EXIF Dates.JPG
    Posted On December 22, 2008 - 10:12 PM (11 months ago) (Permalink to this post)
  • fharczuk
    Member

    Exactly, why is ACDSee changing the camera date?  Shouldn't only a camera do that?

    ACDSee needs works with the dates and calendaring.  If we do as you suggest by using the by using the exif date for the datebase date for the calendaring function in acdsee, then acidentally rotate the image in ACDSee it changes the exif date and database date, then the calendar function will be wrong.

    I need a date in the calendar that doesn't get changed by accident like the original date, or digitized date.  Why doesn't ACDSee have the ability to use these to dates for the database date?

    Posted On March 1, 2009 - 05:12 PM (8 months ago) (Permalink to this post)
  • murech
    Member

    fharczuk said:

    Exactly, why is ACDSee changing the camera date?  Shouldn't only a camera do that?

    Any software editing the image will do it and identify itself. Look at this one edited with Capture NX:

     

    Attached Image:

    What is misleading is that ACDsee shows some EXIF fields (tags) under a Camera heading. If you look at the same EXIF data with ExifToolGUI, this is what you get:

     

    Attached Image:

    As you can see there is no Camera heading here, and the date is clearly identified as ModifyDate. In both cases, the DateTimeOriginal is what identifies when the photo was taken.

    ACDSee needs works with the dates and calendaring.  If we do as you suggest by using the by using the exif date for the datebase date for the calendaring function in acdsee, then acidentally rotate the image in ACDSee it changes the exif date and database date, then the calendar function will be wrong.

    I need a date in the calendar that doesn't get changed by accident like the original date, or digitized date.  Why doesn't ACDSee have the ability to use these to dates for the database date?

    The date to be used for the Databese can be selected in Tools/Options/Database and for the Calendar in Tools/Options/Calendar. But also, once you are displaying the Calendar pane, you may click on the icon on the top-right corner of the pane and change the date to be used.

    HTH.

    Miguel

    Posted On March 1, 2009 - 07:08 PM (8 months ago) (Permalink to this post)
  • Marc Sabatella
    Moderator

    fharczuk said:

    Exactly, why is ACDSee changing the camera date?  Shouldn't only a camera do that?

    Any program that deals with EXIF should have the ability to change that, or won't be very useful. But it shouldn't change the date unless you ask it too, and ACDSee doesn't, so all should be fine.

    ACDSee needs works with the dates and calendaring.  If we do as you suggest by using the by using the exif date for the datebase date for the calendaring function in acdsee, then acidentally rotate the image in ACDSee it changes the exif date and database date, then the calendar function will be wrong.

    Rotating the image won't change the EXIF or database date - only the file modified date.

    I need a date in the calendar that doesn't get changed by accident like the original date, or digitized date.  Why doesn't ACDSee have the ability to use these to dates for the database date?

    It does.  You can set that in Tools->Options->Database.

     

    Posted On March 3, 2009 - 12:35 AM (8 months ago) (Permalink to this post)
  • Will Thackara
    Member

    An odd date quirk in 2.5: In Properties/File Info panel, the dates shown in Created and Modified are reversed; Accessed and EXIF dates are ok. Any solution?  Thanks.

    Posted On March 14, 2009 - 06:11 PM (8 months ago) (Permalink to this post)
  • jonathan7007
    Member

    Will,

    You have raised an important new question here (I think...) and I recommend posting it anew so everyone will see it.

    Posted On March 15, 2009 - 06:06 PM (8 months ago) (Permalink to this post)
  • Marc Sabatella
    Moderator

    Will Thackara said:

    An odd date quirk in 2.5: In Properties/File Info panel, the dates shown in Created and Modified are reversed; Accessed and EXIF dates are ok. Any solution?  Thanks.

    I'm not able to reproduce this.  I just took a file, run Batch Set Information on it with my standard tempate to update its IPTC info, and the File->Properties panel correctly reflected that the Created date didn't change, but Modified and Accessed did.  Is there a specific sequence of operations, or perhaps a specific file or file type, that is triggering the reversal for you?

    Posted On March 17, 2009 - 06:21 PM (8 months ago) (Permalink to this post)
  • murech
    Member

    Marc Sabatella said:

    Will Thackara said:

    An odd date quirk in 2.5: In Properties/File Info panel, the dates shown in Created and Modified are reversed; Accessed and EXIF dates are ok. Any solution?  Thanks.

    I'm not able to reproduce this.

    It is simple to reproduce and I don't think ACDSee can be blamed for it. Just get any file that has the dates "correct" and copy it to another folder. The created data/time will be that of the copy while the modified date will be the one in the original folder. Happens just the same if you use Windows Explorer to copy the file.

    Miguel

    Posted On March 17, 2009 - 07:58 PM (8 months ago) (Permalink to this post)

Subscribe to this topic via RSS

Reply

You must log in to post.