Date format using Batch Process is not yyyy-mm-dd as required

(5 posts)
  • RobotDude
    Member

    I am using ACDSee Pro 8.1, having bought it weeks before Pro 2 was released (would have been nice for ACDSee to have warned me of the immediacy new version!), and find that the date format appears as dd-mm-yyyy when I use <Image:Date/time original> in the file name. However, using Batch Rename I get yyyy-mm-dd which is the format I require. Is this a 'feature' of Pro 8.1 and has it been addressed in Pro 2? If so, I suppose I will have to find the funds to upgrade (for the second time in 6 months) to Pro 2.
    The Option: General/Custom date/time output format has been changed to "yyyy/MM/dd" as suggested in previous posts.
    Hope someone can advise.

    Posted On February 1, 2008 - 03:10 AM (2 years ago) (Permalink to this post)
  • Marc Sabatella
    Moderator

    RobotDude said:

    I am using ACDSee Pro 8.1, having bought it weeks before Pro 2 was released (would have been nice for ACDSee to have warned me of the immediacy new version!)

    FWIW, there were pretty active public beta forums and offers to download the Pro 2 beta starting back in April. but I suppose they probably made those less prominent as Pro 2 got closer to release, since there was no point in signing up more people to be beta testers by then. They did make a series of offers to users of previous versions to entice them to upgrade, and if I recall correctly, the offer was pretty generous for people who had purchased 8.1 within the month previous to the release of Pro 2 - did you receive that?

    Anyhow:

    the date format appears as dd-mm-yyyy when I use <Image:Date/time original> in the file name. However, using Batch Rename I get yyyy-mm-dd which is the format I require. Is this a 'feature' of Pro 8.1 and has it been addressed in Pro 2? If so, I suppose I will have to find the funds to upgrade (for the second time in 6 months) to Pro 2.
    The Option: General/Custom date/time output format has been changed to "yyyy/MM/dd" as suggested in previous posts.

    I don't quite understand. If you have set the date/time output format to yyyy/MM/dd, then that is exactly what I'd expect to show up in the filename if you use date/time in your filenames through any dialog that provides that option. I've had no problems with this in either the original Pro (8.1) or in Pro 2. can you be more specific about what you are doing that causes the wrong format to show up? That is, you it works as you expect in Batch Rename; when *doesn't* it work? In the Get Photos wizard, perhaps?

    BTW, you say you have set the output option to yyyy/MM/dd", but that Batch Rename gives you yyyy-mm-dd. I assume one of those is a typo - it's either hyphens or slashes for both, right?

    Posted On February 1, 2008 - 06:31 PM (2 years ago) (Permalink to this post)
  • RobotDude
    Member

    Thanks Marc for your reply. I upgraded to Pro 8.1 on 3rd Aug 07 following an email received 25 Jul 07. I then received an on 12 Sep 07 regarding the release of Pro 2. So I suppose it is just a case of bad timing!

    To clarify the date format issue. The Custom Date/Time output format is set to "yyyy/MM/dd" which when a Batch Rename is used with Template <Image:Date/time original> #### produces correctly named files i.e. 2007-09-29 13-41-09 0023.jpg. However, when a Batch Process is used with the same Template, files are named dd-mm-yyyy hh-mm-ss ####i.e. 29-09-2007 13-41-09 0023.jpg which is not the format I require/expected. The Get Photos wizard produces file names in the correct format.

    Although the output format is set "yyyy/MM/dd", the file name is in the format "yyyy-mm-dd" as slashes cannot be used in file names. So this is correct.

    The only further thing to mention is that the Batch Process does not give an example of the resulting file name as the Batch Rename and the Get Photos wizard do, but displays <Image:Date/time original> 0001.jpg for the sample.

    As I suspect I may have the same problem with Pro 2, I will stick with Pro 8.1 and wait for the next major release.

    Posted On February 2, 2008 - 03:44 AM (2 years ago) (Permalink to this post)
  • Marc Sabatella
    Moderator

    RobotDude said:

    To clarify the date format issue. The Custom Date/Time output format is set to "yyyy/MM/dd" which when a Batch Rename is used with Template <Image:Date/time original> #### produces correctly named files i.e. 2007-09-29 13-41-09 0023.jpg. However, when a Batch Process is used with the same Template, files are named dd-mm-yyyy hh-mm-ss ####i.e. 29-09-2007 13-41-09 0023.jpg which is not the format I require/expected. The Get Photos wizard produces file names in the correct format.

    Understood, although I am still confused as to why you are using slashes in your output format. I suppose you like the slashes when using this for captions or filling metadata fields? I wanted to make sure you were aware this is not actually used for *display* of dates on screen - only for places where you use "insert metadata" to put the date into a filename or metadata field.

    Anyhow, I just tried using a rename template that incorporates the date in the Batch Processor for Pro 2, and got exactly the results I expected.

    You can of course install the trial version yourself to see if the problem has been resolved for you too, but I'm guessing you will find it is.

    The only further thing to mention is that the Batch Process does not give an example of the resulting file name as the Batch Rename and the Get Photos wizard do, but displays <Image:Date/time original> 0001.jpg for the sample.

    This also works correctly for me. the template itself reports the name of the field, of course, but the sample is correct.

    Posted On February 2, 2008 - 11:53 AM (2 years ago) (Permalink to this post)
  • RobotDude
    Member

    On checking, I find that I am able to set the Custom Date/Time output format to "yyyy-MM-dd" rather than just using the drop down options and this does indeed give me the format I require. Many thanks.

    Posted On February 4, 2008 - 04:58 AM (2 years ago) (Permalink to this post)

Subscribe to this topic via RSS

Reply

You must log in to post.