Dates modified/added are wrong metadata

Hey,
I have a late 2013 mb pro retina 13" which I got Dec 2014, and I have noticed the dates are wrong no matter if I sort by "modified" "created" "added". I've added a few screen shots.
So this is something I downloaded today 28/02/15 but it is displaying 6 Jul 2014. It's frustrating when I need to search for a particular file I downloaded on xyz date but can't find it...
Any solutions??
< same file, added 28/02/2015

Hi kdenson,
I see that you are experiencing an issue with your date and time in some files on your computer. I have an article for you that addresses this issue directly, and it can be found here:
If the wrong date or time is displayed in some apps on your Mac - Apple Support
https://support.apple.com/en-us/HT203413
Thanks for using the Apple Support Communities. Have a good one!
-Braden

Similar Messages

  • Date and time are wrong

    My date and time are wrong on boot up and won't adjust back to normal automatically.  I think the internet is telling me it's a problem with either my PRAM or CMOS or NVRAM battery, the little guy that holds info while the big guy is tapped.  I want to replace this. Is that possible?  What is the battery actually called?

    Hey MisterW,
    Thanks for the question. It sounds like you wish to reset your PRAM/NVRAM, the following article should assist you:
    About NVRAM and PRAM
    http://support.apple.com/kb/HT1379
    Thanks,
    Matt M.

  • How can I use "date modified" from metadata to date iphoto events?

    I am very frustrated trying to move photos from windows to iMac.  I have a number of photos, all of them have some metadata with date created and date modified.  This worked well in Picasa in Windows and kept everything in order.  Now it seems iphoto will not read date modified or assigns date created (if there is no date in the metadata) as the date everything was switched over.  I looked over some of the wrongly organized photos (there are thousands) and realized that under the old sustem, Picasa in windows must have used either date created or date modified, which ever came earlier or perhaps whichever was available.  In iphoto, it doesn't read "date modified" or does this crazy thing where even if the modification date is before the creation date, puts all photos in the order or when they were brought over from windows.  I have a lot of photos dated September 18 -- thousands.
    Is there any way to get either iphoto or some other program (I'm not terribly impressed by iphoto) that will properly organize the photos in an imac environment. In other words, I want a program to look at (1) creation date or (2) modification date (which-ever is earlier).
    Even Picasa is now confused (in the mac envirnoment). 
    Thanks,
    Mark

    No, as this is file metadata not photo metadata.
    You can adjust the date and time using the Photos -> Adjust Date and Time or even the Photos -> Batch Change command.
    Regards
    TD

  • No dates in Last Modified Date or Added Date

    Hello.
    Due to some issues with our servers i'm unable to make any SR's so i hope to recive some answers here instead while that issue gets resolved.
    When looking in the colums "Added Date" and "Last Modified Date" certain activites have no dates there. When attempting to filter all the activities with a filter "Added Date Equals 'Blank' " ie all aktivites who do not have a date in Added Date, the results are 0 activites. I interpret this as the fields are not empty but for some reason the information is not displayed.

    781070 wrote:
    Hello.
    Due to some issues with our servers i'm unable to make any SR's so i hope to recive some answers here instead while that issue gets resolved.
    When looking in the colums "Added Date" and "Last Modified Date" certain activites have no dates there. When attempting to filter all the activities with a filter "Added Date Equals 'Blank' " ie all aktivites who do not have a date in Added Date, the results are 0 activites. I interpret this as the fields are not empty but for some reason the information is not displayed.As far back as I can remember, filtering by either of those fields has never worked.
    There are a number of reasons why the last modified or added date could be blank.

  • Getting an error message: "if you are here, it is probably because your computer's clock is wrong."  Ergo, I can't get to the page I need.  My clock's date and time are right.  After re-booting, went to wrong time zone, which I changed-- still getting msg

    Getting an error message: "if you are here, it is probably because your computer's clock is wrong."  Ergo, I can't get to the page I need.  My clock's date and time are right, but time zone was wrong-- changed & saved it, but still getting error msg

    'Requires=network.target' wasn't in it so I added it but nothing's changed. I've left it in because openVPN does require network.
    As I said, I had this problem with a script so I don't think it's anything specific to openVPN. I had a weird occurrence this morning however. When I started the computer up this morning  openVPN worked just fine. However when the computer rebooted openVPN couldn't resolve the host address again.

  • When I open up "originals" in my iPhoto library, the dates are not there or are incorrect.  I see date created and date modified, not the original date the picture was taken.  How can I find the accurate original dates?

    I have had a lot of issues with my iPhoto program. After many trips to the Genius Bar and numerous hours with phone techs, I am now rebuilding my library, starting with a backup of it from before the corruption. When I "get info" of a picture, I notice the original date the picture was taken (most important for me), is not there or is wrong.  When I check package contents of my iPhoto library, the originals show up, but most (not all) of the dates are wrong.  Can anyone tell me how or where I might find the original dates?

    I did post to the iPhoto forum and am hoping for an answer soon. I don't want to continue rebuilding my iphoto library if I can do it using originals. My library has 45,000 pictures...a huge job!

  • How to change "Date Added" to "Date Modified"in Open a File dialoge

    Ever since updating IOS to the latest version the option to sort by "Date Modified" in the open a file dialog has been changed to "Date Added". How can I change this back to "Date Modified"?

    Hmm, in OpenSolaris and Solaris Express, the date format is a preference in the Nautilus Preferences dialog. But I don't see it back in JDS 3.
    One way (assuming you're using a bash shell) is:
    % gnome-session-remove nautilus
    % LANG=de_DE nautilus &
    which works, but also switches the rest of the nautilus UI into German.
    Setting LC_TIME rather than LANG in the second command should work better, because it changes only the dates/times into German. But it still uses the 12 hour clock, with "vorm." and "nachm." instead of "am" and "pm". I suppose that might be considered a bug...

  • Import from Excel to Project - blanks cells are having dates automatically added

    Hi. I'm very new to Project but have started setting up a Roadmap using it which is working fairly well so far, although have hit one snag.
    I have data in Excel: it is a list of projects with 4 columns containing the dates of various stages (planning, initiate, execute, close). I have created a reusable map so this can be imported into Project and the Gantt chart to show pre-defined markers
    on the timeline for each stage on each project row. All well and good so far.
    However, not all of the projects in Excel have all of their dates defined. E.g. a project might not yet have a close date. But when this is imported into Project a date gets applied for it. I have no idea why!
    How do i get the import into Project to allow any blank cells from Excel to remain as blank so that nothing is plotted on the Gantt chart for that particular section?

    Thanks for both of your replies. I have tried this and the same issue occurs. I have checked each row in the imported Project data and they are all showing as set to 'manually selected' yet at some point in the import Project is adding data to blank cells.
    I have retried using a simple test excel sheet and when this too is mapped into Project, any blank cells get populated with the date that appeared in the preceding row for some reason:
    I can then go through and manually delete this cell in Project (which then replaces it with an "NA") - but if i have to manually do this whenever importing from Excel into Project then it makes it very time consuming.
    Surely there must be a way for Project to not auto-populate blank cells? Or am i missing something fundamental?

  • Date modified/Date Created/Date Added(timestamp) - not showing the actual date?

    In finder, none of the date info seems to be accurate.
    By example, I just downloaded a new app from a website (onyx in this case), todays date is Nov 13th and when I install the new app (i.e. drag and drop into Apps folders) in finder the Date modified says Nov. 1st, Date created says October 31. Should one of these columns not reflect the true date that the app actually got onto my mac? I understand that one of these clumns probably relfects the info contained within the downloaded app, but surely one column can tell me that I installed this app on November 13! The "Last opened" columns is the only "accurate" date column I have. (as I write this however, i've noticed that the 'Date Added column does say "Today").
    I gues my question is what columne reflect what the file itself has imbedded in it, and what relfects the actions i've done (I.e. installed the app on Nov 13)
    Any help would be very much appreciated. Note sure if this is somehting more worrisome or not, but i've had it for a while with no major issues other than frsutration of not understanding this. i'm on 10.7.2

    The Date Modified column for the Applications folder itself will reflect the actual installation date. The others aren't supposed to.
    (61530)

  • Finder window date added date modified show date time always

    Is there a preference setting to have a finder window with Date Added and Date Modified columns enabled to always show the date and time? Currently, the column information is dynamic, like just providing a time where you infer Today, or one column does show the date and time but the other only shows the date, or it reads Today, 12:31pm.
    I want every window when displaying Date Added or Date Modified columns to always, consistently show the date and time, e.g. 3/15/14, 7:31AM.
    Aloha and Mahalo!

    I found half of the answer: View:Show View Options - Deselect Use Relative Dates.
    Now I just need a solution to always show the time and not only the date.
    Curiously, when you initially enable a column in a Finder window, it shows both the date and time; however when you return to the window after closing it, you lose the time of day on Date Added, but not on Date Modified. -- Bug or Feature?

  • Many original dates of photos are missing or wrong

    I have had a lot of issues with my iPhoto program. After many trips to the Genius Bar and numerous hours with phone techs, I am now rebuilding my library, starting with a backup of it from before the corruption. When I "get info" of a picture, I notice the original date the picture was taken (most important for me), is not there or is wrong.  When I check package contents of my iPhoto library, the originals show up, but most (not all) of the dates are wrong.  Can anyone tell me how or where I might find the original dates?

    Download and place this app in the Dock:   EXIF Viewer for Mac OS X. Then drag some of the problem photos original files from the iPhoto library package onto the app in the Dock.  You'll get this window where you can check the Image Generated date:
    If it's the same as what iPhoto is showing then the file is incorrect.  The date can be corrected in iPhoto with the Photos ➙ Adjust Date and Time menu option:
    OT

  • Retain Modified Date after adding a column

    I have a sharepoint list that has been in use for some time.  
    There are reports generated bases on "last modified"  
    As the site admin, I need to add a column to the list and then enter some values into the new columns. 
    But this changes all of the modified dates.  
    Any was to preserve this date? 

    If you are able to update the list items using PowerShell, you can use the SPListItem.SystemUpdate(false) method.
    This will update the list item without changing the modified date / modified by information, and without creating a new version.
    See: https://msdn.microsoft.com/en-us/library/office/Microsoft.SharePoint.SPListItem.SystemUpdate.aspx
    Regards, Matthew
    MCPD | MCITP
    My Blog
    View
    Matthew Yarlett's profile
    See my webpart on the TechNet Gallery that allows administrative users to upload, crop and format user profile photos. Check it out here:
    Upload and Crop User Profile Photos

  • Date modified always wrong

    Hi all,
    Recently I've noticed that document dates (modified) in Finder are all displaying incorrectly.
    As an example...a document I created Friday 30 May 2008 at 07:47, modified same date at 08:51, shows in Finder as being modified on 30 January 2008 08:51.
    When I do Apple+I the info is correct.
    The same as above example applies to all files...including about 250 photos I took last week whilst on holiday...only the ones copied/edited yesterday are correct (the show 'yesterday')...all the ones I copied to the MBP and edited earlier last week show January instead of May.
    Any else experiencing this...and can someone tell me what I can do to rectify it?
    Thanks,
    Nige

    I just created a new account, and guess what, dates/times look OK in Finder.
    So...what can it be in my account that's doing this? I did a full OS X and software re-install only 3-4 weeks ago, so I can't believe it's corrupted. Is there a config/plist/other file that I need to delete to reset something?
    Here's an off-topic winge (my own opinion)...
    As a new Mac user (4 months) I am wondering why I ever changed from Windows...the MBP cost about double what a good quality Windows laptop would have, I wouldn't have had to buy new software, and I wouldn't have had all the issues I've had...this machine has never worked properly , and I've never seen so many people having so many problems with hardware, software, updates as I've seen here...it seems that almost every Apple update breaks something...sometimes in a major way...what on earth is all the Apple hype about? Why do all the hundreds and thousands of Mac users put up with this? In 20+ years of using computers (yes...mostly variations of Windows), I can honestly say I have never, ever had the hardware and software issues I am seeing on my MBP. I know Windows is far from perfect, but for the most part, it does work OK. Amongst other things, I have had to re-install OS and software TWICE in 4 months...it's complete boll**ks.
    I hope someone can give me some good reasons to stick with a Mac, otherwise I might throw this in the bin...I'm loosing more money than the value of a new computer in the time I'm wasting that I can't bill to clients, trying to get this one working properly.
    /end of winge/
    vbrgds to all,
    Nige
    Message was edited by: nigelj

  • "Date Modified" for all files being changed if "Automatically write to XMP" is on

    Recently upgraded from LR3 (v3.4.1) from LR2 on OSX 10.6.8 and have always had Catalog Settings > Automatically write changes into XMP turned on.
    When browsing existing JPG files in my Library (no Develop changes, no keywording, no Presets, no Import), LR3 is writing to disk — i.e., when I look at files in Finder, almost every viewed file’s “Date Modified” is being set to today’s date and time. (It actually creates a .swp file, then changes it's name back to .jpg)
    This is really bad, as it's making it impossible for me to use Finder to figure out when I last worked with a file, it is triggering needless Time Machine and Backblaze backups, and unnecessarily churning my disk.
    If I turn off "Automatically write..." this behavior stops. Per David Marx at thelightroomlab.com, I tried turning off this preference, manually doing a "Save Metadata to File" for all files, letting that complete, then turning the preference back on. This does not solve the problem.
    Per a suggestion at photoshop.com, I used ExifTool to see what changes LR was writing to a sample file; from the diff below, you can see that LR is adding a bunch of new fields as well as moving other fields around. But my point is that LR3 should never overwrite a file on disk if all I am doing is browsing thru them.
    Is anyone else seeing this? Any ideas would be greatly appreciated!
    -- David
    diff Exif5609_original Exif5609_update
    2c2
    < FileName: DSC_5609_original.JPG
    > FileName: DSC_5609_update.JPG
    5,6c5,6
    < FileModifyDate: 2009:11:27 21:32:54-08:00
    < FilePermissions: rwxr-xr-x
    > FileModifyDate: 2011:08:07 22:06:47-07:00
    > FilePermissions: rw-r--r--
    27a28,29
    > ShutterSpeedValue: 1/200
    > ApertureValue: 7.1
    55d56
    < SerialNumber: 3209521
    75d75
    < Lens: 18-200mm f/3.5-5.6
    185,188d184
    < UserComment:
    < SubSecTime: 00
    < SubSecTimeOriginal: 00
    < SubSecTimeDigitized: 00
    211a208,299
    > XMPToolkit: Adobe XMP Core 5.2-c004 1.136881, 2010/06/10-18:11:35
    > CreatorTool: Ver.1.00
    > MetadataDate: 2011:08:07 22:06:47-07:00
    > SerialNumber: 3209521
    > LensInfo: 18-200mm f/3.5-5.6
    > Lens: 18.0-200.0 mm f/3.5-5.6
    > ImageNumber: 26634
    > RawFileName: DSC_5609.JPG
    > SavedSettingsName: Import
    > SavedSettingsType: Snapshot
    > SavedSettingsParametersVersion: 6.4.1
    > SavedSettingsParametersProcessVersion: 5.0
    > SavedSettingsParametersWhiteBalance: As Shot
    > SavedSettingsParametersIncrementalTemperature: 0
    > SavedSettingsParametersIncrementalTint: 0
    > SavedSettingsParametersExposure: 0.00
    > SavedSettingsParametersShadows: 0
    > SavedSettingsParametersBrightness: 0
    > SavedSettingsParametersContrast: 0
    > SavedSettingsParametersSaturation: 0
    > SavedSettingsParametersSharpness: 0
    > SavedSettingsParametersLuminanceSmoothing: 0
    > SavedSettingsParametersColorNoiseReduction: 0
    > SavedSettingsParametersChromaticAberrationR: 0
    > SavedSettingsParametersChromaticAberrationB: 0
    > SavedSettingsParametersVignetteAmount: 0
    > SavedSettingsParametersShadowTint: 0
    > SavedSettingsParametersRedHue: 0
    > SavedSettingsParametersRedSaturation: 0
    > SavedSettingsParametersGreenHue: 0
    > SavedSettingsParametersGreenSaturation: 0
    > SavedSettingsParametersBlueHue: 0
    > SavedSettingsParametersBlueSaturation: 0
    > SavedSettingsParametersFillLight: 0
    > SavedSettingsParametersVibrance: 0
    > SavedSettingsParametersHighlightRecovery: 0
    > SavedSettingsParametersClarity: 0
    > SavedSettingsParametersDefringe: 0
    > SavedSettingsParametersHueAdjustmentRed: 0
    > SavedSettingsParametersHueAdjustmentOrange: 0
    > SavedSettingsParametersHueAdjustmentYellow: 0
    > SavedSettingsParametersHueAdjustmentGreen: 0
    > SavedSettingsParametersHueAdjustmentAqua: 0
    > SavedSettingsParametersHueAdjustmentBlue: 0
    > SavedSettingsParametersHueAdjustmentPurple: 0
    > SavedSettingsParametersHueAdjustmentMagenta: 0
    > SavedSettingsParametersSaturationAdjustmentRed: 0
    > SavedSettingsParametersSaturationAdjustmentOrange: 0
    > SavedSettingsParametersSaturationAdjustmentYellow: 0
    > SavedSettingsParametersSaturationAdjustmentGreen: 0
    > SavedSettingsParametersSaturationAdjustmentAqua: 0
    > SavedSettingsParametersSaturationAdjustmentBlue: 0
    > SavedSettingsParametersSaturationAdjustmentPurple: 0
    > SavedSettingsParametersSaturationAdjustmentMagenta: 0
    > SavedSettingsParametersLuminanceAdjustmentRed: 0
    > SavedSettingsParametersLuminanceAdjustmentOrange: 0
    > SavedSettingsParametersLuminanceAdjustmentYellow: 0
    > SavedSettingsParametersLuminanceAdjustmentGreen: 0
    > SavedSettingsParametersLuminanceAdjustmentAqua: 0
    > SavedSettingsParametersLuminanceAdjustmentBlue: 0
    > SavedSettingsParametersLuminanceAdjustmentPurple: 0
    > SavedSettingsParametersLuminanceAdjustmentMagenta: 0
    > SavedSettingsParametersSplitToningShadowHue: 0
    > SavedSettingsParametersSplitToningShadowSaturation: 0
    > SavedSettingsParametersSplitToningHighlightHue: 0
    > SavedSettingsParametersSplitToningHighlightSaturation: 0
    > SavedSettingsParametersSplitToningBalance: 0
    > SavedSettingsParametersParametricShadows: 0
    > SavedSettingsParametersParametricDarks: 0
    > SavedSettingsParametersParametricLights: 0
    > SavedSettingsParametersParametricHighlights: 0
    > SavedSettingsParametersParametricShadowSplit: 25
    > SavedSettingsParametersParametricMidtoneSplit: 50
    > SavedSettingsParametersParametricHighlightSplit: 75
    > SavedSettingsParametersSharpenRadius: +1.0
    > SavedSettingsParametersSharpenDetail: 25
    > SavedSettingsParametersSharpenEdgeMasking: 0
    > SavedSettingsParametersPostCropVignetteAmount: 0
    > SavedSettingsParametersGrainAmount: 0
    > SavedSettingsParametersLensProfileEnable: 0
    > SavedSettingsParametersLensManualDistortionAmount: 0
    > SavedSettingsParametersPerspectiveVertical: 0
    > SavedSettingsParametersPerspectiveHorizontal: 0
    > SavedSettingsParametersPerspectiveRotate: 0.0
    > SavedSettingsParametersPerspectiveScale: 100
    > SavedSettingsParametersConvertToGrayscale: False
    > SavedSettingsParametersToneCurveName: Linear
    > SavedSettingsParametersCameraProfile: Embedded
    > SavedSettingsParametersCameraProfileDigest: D6AF5AEA62557FCE88BC099788BBD3CC
    > SavedSettingsParametersLensProfileSetup: LensDefaults
    > SavedSettingsParametersToneCurve: 0, 0, 255, 255
    > IPTCDigest: d41d8cd98f00b204e9800998ecf8427e
    228,230d315
    < SubSecCreateDate: 2009:11:27 21:32:54.00
    < SubSecDateTimeOriginal: 2009:11:27 21:32:54.00
    < SubSecModifyDate: 2009:11:27 21:32:54.00
    http://feedback.photoshop.com/photoshop_family/topics/lr3_date_modified_for_all_files_bein g_updated_when_browsing_photos_if_catalog_settings_automatically_write_changes_into_xmp_is /replies/6313647

    clvrmnky wrote:
    davidpope007 wrote:
    Then when LR3 loaded my old LR2 images into memory, it "dirtied" the in-memory copy of the file by adding in these new LR3 XMP fields. Then, because I had "Automatically write XMP" on, it said "I better write these changes to disk".
    Yuck. As a former software engineer, this is very bad software engineering.
    It should wait until the user dirties the file (via Develop, keywords, etc.) before presuming to add a bunch of metadata fields that are unique to the new version of LR3.
    Well, I'm a current software developer, and this is, really, a perfectly reasonable thing to do. It is a reasonable trade-off for a convenient feature required by a small subset of users.
    Yes, in most cases the in-memory copy should "never" be dirtied unless the user makes a gesture of some sort, but like I said earlier, this option (once set by the user) sets up the situation where this gesture becomes implicit. This is a clear trade-off for the sake of convenience. And if the XMP is out of date and needs to be updated en masse, so be it.
    The fact is, there is no easy way around this. Do we save up /every/ dirty buffer somehow until you make a gesture that /might/ require the XMP to be up-to-date before acting on that gesture? Now we have to worry about unflushed buffers if something goes wrong and the app exits. Do we save the buffers to the DB? Now we have to block some calls to make another blocking call to flush some or all of those to DB, and then write some or all of it out to one or more files. In what order? What if there is a gesture to have X files with up-to-date XMP and some or all of those are in unflushed buffers, unflushed DB writes or we have to wait for the DB.
    As you can see, this is a transactionality nightmare, and the easiest and safest thing to get what the user wants (i.e., up-to-date XMP for the purpose of talking to a third-party XMP aware app) is to simply update the sidecar or XMP block in an atomic manner using the correct file IO. The file will have to change at some point, so it may as well be now.
    [Thanks to both of you for your detailed replies. I am aware of the need for tradeoffs so when you say the approach taken is quite reasonable, I do believe you. I also apologize in advance for the length of the following and am extremely aware of the time it must have taken you to compose the above replies, but I'm going to add a bit more, if only for my own piece of mind and in hopes of coming up with a solution for my workflow.]
    From my naive point of view, I was expecting the answer to be simply "don't raise the XMPDirtyFlag upon reading in a file". Obviously if your architecture requires you to "upgrade to latest XMP format" upon read, and another part of the system auto-detects "out of date XMP", then it's going to write those changes to disk.
    But it didn't need to be designed that way. LR obviously has mechanisms to know when a user has made a change to XMP so it is able to write XMP changes to disk only when necessary.
    The promise (to me) of "Automatically Write XMP changes to disk" was to auto-save my changes, and not those made for any internal (i.e., XMP versioning related) changes.
    Perhaps the premise is that it is LR3's job to update an individual file's XMP to the latest version so that other XMP-aware apps can make use of it? I would argue that those third-party XMP-aware apps already have to know how to deal with all prior versions of XMP, so LR3 should just leave well enough alone.
    You asked if my problem with your approach was that it was "inelegant"; not at all, it is based on my own perception of what I need from my workflow, so let me describe that so maybe we can find a better way:
    * Part of the appeal of LR to me is that it preserves my original file as it came off the memory card, allowing me to move to a different workflow/toolset in 2025 if I choose to do so
    * However, with all of changes contained in a single database file, I'm concerned about rare (but possible) corruption, so to mitigate this risk, I let LR backup my database weekly and it's also backed up continuously in the cloud via Backblaze
    * Even with backups of the database, there is still a chance that I could lose changes made to individual files (e.g., LR corrupts the DB and I have to go back to last week's DB)
    * Thus the appeal of the "auto-write to XMP" flag -- that way critical changes (develop, crop, keywords) are saved on a per-file basis; I liked the "automatic" part of this (as opposed to a manual save) because then I don't have to teach others in my family how to manually save XMP changes
    * A nice side-effect of this setting is now when I use Finder to find a file and double-click on it to edit it in Photoshop, all my develop changes are right there; (in other words, I like the flexibility of not having to fire up LR in order to just invoke PS from within it); also when I use Bridge I see all the keywords there
    * So with LR2, I had gotten used to what I thought was the best of all worlds -- autosave of changes at the file level via XMP + raw negatives untouched (i.e., Date Modified == the date I took the picture); this allows me to use operating-system-level tools -- Finder -- to locate/search for files
    * Now I upgrade to LR3 and I'm finally now understanding that a concept "XMP versioning" is going to result in changes to many, but not all my files. (That's something else that's annoying about this issue -- I open up the Grid and browse a folder of files, and only seemingly random ones I've cursored over seem to get written to disk -- if it's so urgent that LR3 update the XMP, then it should do it for all the files in the catalog or at least in that directory)
    Here's a screenshot from Finder of what I see everytime I look at this folder:
    * So now I have to assume that each new version of XMP and/or LR is going to touch my files on disk. Sigh.
    * What I don't like about this is that it is ruining the promise of "untouched raw negative". Yes, the image data is untouched -- which I agree is most of the benefit; but the file has been touched.
    * Perhaps you might empathize a bit more if you imagined that someone went thru all your source code or Word files and randomly changed the date to "today" because you upgraded compilers or moved to Word 2011.
    I agree all of this would be solved by having an XMP sidecar file for JPGs, but you indicate that's not going to happen.
    You've also alluded to the solution of "resetting the Date Modifed" to it's original value -- which I believe is what Finder does when you move or copy a file -- but that that is fraught with issues as well. I believe you when you say there are issues, but again the naive part of me wonders why that soultion would be so bad...
    I just thought of another potential solution -- turning on Date Created in Finder -- but it turns out that's changed, too.
    I am really at a loss as to what to do and would welcome your suggestions.
    Thanks again and kind regards,
    -- David

  • How do I change or remove default apps for a given file extension (in Terminal?) without munging date modified on all my old files?

    When a program is installed, it seems to be able to do it (sometimes inappropriately if it hijacks file associations without asking) so why can't I?  This is for 10.4.
    Specifically:
    1. Since installing an HP wireless printer, HP not only tries to install a bunch of sales-ware on your machine that you have to carefully opt out of (annoying, but not a problem if forewarned), it changes the default file association for a number of basic file types, listing all sort of existing files as HP printer files. Using Get Info to change the default file type association globally causes it to mark ALL the files of that type as newly updated, munging the file metdata (which HP did NOT do). Most of the stuff on our computer is sorted by last modified, so if there is a way to fix this in Terminal (to simply fix or remove the HP default tag) without changing the date the file was modified, it would help. Note that uninstalling the program that created the default would do this, but I obviously can't do that (and reinstalling HP would have the same effect). So there has to be another way, right?
    2. Since updating iTunes to v.9 a while back, every mp3 is marked as an iTunes file even though iTunes has NO multiple library capability without a wonky reboot using the option key, meaning that if I click on an mp3 downloaded since last update of iTunes, it opens automatically in iTunes and gets added to the SOLE itunes library without asking. (There is no way to toggle between multiple libraries or archive media in separate folders; iPhoto has a similar problem. (Has this been fixed in the latest version of iTunes?) In comparison, Quicktime starts up immediately and does not attempt to create a playlist just because you opened a file and listened to it.
    (The iTunes playlists are simply subfolders of the single main library -- and you can't create a new library without doing a wonky procedure by clicking option during startup and telling iTunes to forget where its library is located (includin everything in it) and look up an entirely separate one by hand. So any mp3 file downloaded recently is uploaded to iTunes if you click on it. This wouldn't be problem if it didn't automatically add it to the sole iTunes library just because you clicked on it.)
    Besides, all my old mp3s are Quicktime files and they are all archived by date modified. To its credit, ITunes, unlike HP, does NOT hijack older files already on disk and remark them as iTunes files. It only marks newly downloaded files as such.  But if I try and change file association for FUTURE mp3 files using Get Info > "use this program for all files of this type", it munges the file metadata (date modified) for all existing files!
    Note that in HP case, it apparently does it at the file exchange preference level (or whatever it's called) since the OS then recognizes every file of those types as an HP file. In the iTunes case, it only does it if you download a new media file or open an existing file in iTunes, but again without changing the date it was last edited.
    Since these programs are able to change the default file association without changing the date the file was last edited, it should be reversible in Terminal, correct?  Why does it change "date modified" when you try and correct metadata using Get Info (or sometimes just by clicking an enclosing folder?) Date modified should be a record of when a file itself was edited, not when it was renamed, or other metadata. Otherwise stuff can't be sorted correctly.

    The unix commands you need are:
    GetFileInfo
    SetFileInfo
    and maybe find
    for cryptic details use the man command
    Macintosh-HD -> Applications -> Utilities -> Terminal
    man SetFileInfo
    You may use the SetFileInfo command to set the file type & the program which will open the file.
    # This little gem will do a get info on all files in a directory.
    mac $ ls  | xargs -I {} GetFileInfo "{}"
    file: "/Users/mac/playdoc/oddadocodd"
    type: ""
    creator: ""
    attributes: avbstclinmedz
    created: 05/01/2011 14:53:22
    modified: 05/01/2011 14:53:22
    file: "/Users/mac/playdoc/one.docx"
    type: ""
    creator: ""
    attributes: avbstclinmedz
    created: 05/01/2011 13:57:48
    modified: 05/01/2011 13:57:48
    file: "/Users/mac/playdoc/oneLineFile"
    type: "TEXT"
    creator: "!Rch"
    attributes: avbstclinmedz
    created: 05/07/2011 14:27:17
    modified: 05/07/2011 14:27:17
    file: "/Users/mac/playdoc/oneLineFile.txt"
    type: "TEXT"
    creator: "!Rch"
    attributes: avbstclinmedz
    created: 05/07/2011 14:27:49
    modified: 05/07/2011 14:27:49
    file: "/Users/mac/playdoc/three.docx"
    type: ""
    creator: ""
    attributes: avbstclinmedz
    created: 05/01/2011 13:58:03
    modified: 05/01/2011 13:58:03
    file: "/Users/mac/playdoc/two.docx"
    type: ""
    creator: ""
    attributes: avbstclinmedz
    created: 05/01/2011 13:57:56
    modified: 05/01/2011 13:57:56
    file: "/Users/mac/playdoc/weirder.doc.docx"
    type: ""
    creator: ""
    attributes: avbstclinmedz
    created: 05/01/2011 14:50:03
    modified: 05/01/2011 14:50:03
    # well, ! is a funnie character so we escape it.
    mac $ SetFile -t TEXT -c \!Rch two.docx
    mac $ GetFileInfo two.docx
    file: "/Users/mac/playdoc/two.docx"
    type: "TEXT"
    creator: "!Rch"
    attributes: avbstclinmedz
    created: 05/01/2011 13:57:56
    modified: 05/01/2011 13:57:56
    mac $
    mac $ date
    Sat May  7 14:40:56 EDT 2011
    mac $

Maybe you are looking for