All files in double

When I adding my D:\mp3 directory, i see all my song 2 times.
When do a check 2 of them, I see it s exactly the same file except the path that are:
d:\mp3\mygr~1\music.mp3
and
d:\mp3\my group\music.mp3
Seems that itunes doesn't differentiate the old dos path and the windows long path.
I tried to delete all files and add them again, doesn't change anything

I never had problem before and it appears with the latest itunes release a few days ago...
"DEEPDI~1" and "Deep Dish" directories are the same directory. It's just a DOS compatibility feature made by Windows to encode long filename. There's no hidden files, no system file or whatever. It happens to all long directories in my mp3 directory and not in the short directories.
http://www.telegraph.co.uk/connected/main.jhtml?xml=/connected/2002/12/30/boot11 4.xml
"You may have noticed that file and folder names in DOS are only 8 characters long, DOS shortens the longer file names used in Windows to the first six characters followed by a tilde (~) and a number (normally 1, unless there's another file with the same first six letters). When naming files you should use the DOS convention, i.e. as it appears on the screen."
Can it be a new windows bug with the latest itunes version?

Similar Messages

  • We have developed a desktop application using Flash software and published the same for MAC environment. When we double click on the index.app file, the application is working perfectly in Mac 10.6.7 at our office. But if the same index.app file is double

    We have developed a desktop application using Flash software and published the same for MAC environment. When we double click on the index.app file, the application is working perfectly in Mac 10.6.7 at our office. But if the same index.app file is double clicked in Mac 10.6.7 at out clients location, its not opening. For your information the client is able to open this same application by double clicking on index.swf file. The main problem is that client is not able to open the application using index.app file at their office whereas we are able to do so at our office. Can anyone give some suggestions to sort this problem?

    The most common reason is different versions of Flash, or different versions of web browsers used.  Some users may elect to not have Flash installed at all because of the processor overhead of Flash.  If you are going to make an application for a client, check what operating system and browser versions they are using first.  Then determine if a stand alone application is required, or if they have the necessary plugins to run specific browser enhanced code.
    P.S. MAC is an acronym for Media Access Control.  Mac is the shorthand for Macintosh, the operating system and computers made by Apple Inc.

  • New Album from Smart Album makes NEW VERSIONS of all files? Bug?

    Got what I think is an oddball bug here, but see if any of you have experienced it.
    Making a new album of the contents of a Smart Album with about 600 images resulted in the SBOD, a lot of time and disk activity and the creation of NEW VERSIONS of all the files populating the new album. This, of course, also doubled the number of files in the original Smart Album, since the keywords used are a match. First thinking it might be something I had not read in the manual, I grabbed the book and could not find this behavior listed…..so….my expected result is a new album with the identical contents of the Smart Album selected as the source.
    I am creating a presentation for a client whose work is in multiple projects in a ~150GB library. All images are heavily keyworded, so making Smart Albums of specific elements of the work was easy. My intended workflow to get through this mountain of pix was to make Smart Albums of specific elements, then make New Albums from each, manually edit and reorg these albums individually, then combine my edits into a single book file.
    Now the structure leading to this problem is as follows:
    1) I created a single “main” folder to store all projects and other elements and hierarchy for this client. Clicking on this folder returns some 8500 images spanning multiple projects…all as expected.
    2) At the top level of this “main” folder, I made about 20 Smart Albums to presort the main elements I wanted to include. I made the first Smart Album by clicking the icon in the top bar. The rest of the smart albums I made by duplicating the previous Smart Album, then changing keyword selection. I would select the new keywords I wanted, then de-select the ones that were from the album I had duplicated. The reason I did it that was for speed, there is little delay in displaying the items that were already searched for, and a significant delay in going from new. Anyway, somewhere in this process, I decided to organize my workflow further, so I created a new folder (calling it Smart Album Selects) at the same level as the Smart Albums, and then dragged the Smart Albums into the new Smart Album Selects folder. Still, no problem.
    3) Later in my session, I went to create another new Smart Album, and this time I did so already in the Smart Album Selects folder. When I opened the HUD to select the keywords, the Keyword area and check box were greyed out!!! Weird, I though….so I simply duplicated an existing Smart Album from my Smart Album Selects folder, opened the HUD, and sure enough, all my keywords were there. I changed the keyword selection, and went on with work. During the day I did this same operation 3 more times, making 4 Smart Albums created the same way.
    4) OK…here is the strange behavior. To make my new custom album from the Smart Album selects, I selected one of the Smart Albums, and clicked on the New Album icon. Got the expected dialog, make with 1 image or all images, selected all images, and instead of a new album popping up moments later, I got the SBOD, and the Activity Monitor said Aperture and my hard disk was cranking away. About 4-5 minutes later, Aperture became responsive again, and had created a new album. However, upon inspection, the album contained NEW VERSIONS of all the images that were in the Smart Album, about 600 files.
    5) I went back and clicked on a different Smart Album in the same spot in the hierarchy…but it was one of the first ones I had created (meaning I built this BEFORE reorganizing into the Smart Album Selects folder). Tried making a new album again, with 1 image, worked fine, popped up instantly. Tried selecting 4 images, same thing, worked fine. Selected All, made album, worked fine.
    6) Went back to the Smart Album I had the problem with, this time selected 4 images, make New Album, and sure enough the New Album had NEW VERSIONS of the pix again…OK, I went back to the top of my folder hierarchy, my “main” folder and made a brand new Smart Album by clicking the icon, and selecting keywords. Made a new album from that, no problem, popped up instantly, no new versions.
    7) I then re-made all my Smart Albums at the top of the folder hierarchy, and they all work fine creating new albums. I got back to the task at hand…hopefully there is enough data here to let the Aperture engineers find this problem…Assuming, that is it is not just me misunderstanding some element in the program.
    Sorry for the length, but has anyone else run into this??
    PowerBook G4 1.67 2GB RAM 128MB ATI Video, External FW Drives for library   Mac OS X (10.4.7)  

    Nope, all the images at this point in my workflow have been unstacked, with the non-picked members of the original stacks discarded.
    Now that it seems I am not the only one who has witnessed this behavior, what I am really trying to find out, is what is the definitive proper operation of this according to the Aperture group at Apple.
    Assuming I have opened a Smart Album with images displayed, and no images are selected.
    Is the correct behavior:
    1) Selecting New Album makes a new Untitled Album (very quickly) with the identical contents of the Smart Album....OR...
    2) Selecting New Album makes a new Untitled Album (slowly) with NEW VERSIONS of the contents of the Smart Album. (Also, depending upon the number of images, typically brings up SBOD and makes Aperture unresponsive until it is complete.)
    Now what I expected to happen was #1, as it is what happens when I select New Album when a project is selected. Given Apple's human interface creedo for intuitive operation, I think this is the most intuitive choice, because I can't think of a good reason I would want to double the number of versions of all files in an album, unless I expressly told the app to do this.
    Could an Apple guy provide the definitive answer, please...
    Thanks in advance for your help.
    PowerBook G4 1.67 2GB RAM 128MB ATI Video, External FW Drives for library   Mac OS X (10.4.7)  

  • I need to back up my imac running Tiger (no time machine) so that we can upgrade OS. It is set up for multiple accounts.  How do I capture all files in each account using newly purchased USB external hard drive?

    I need to back up my imac running Tiger (no time machine) so that we can upgrade OS. It is set up for multiple accounts.  How do I capture all files in each account using newly purchased USB external hard drive?  Thanks!

    Backup Software Recommendations
    Carbon Copy Cloner
    Data Backup
    Deja Vu
    SuperDuper!
    Synk Pro
    Tri-Backup
    Others may be found at VersionTracker or MacUpdate.
    Visit The XLab FAQs and read the FAQ on backup and restore.  Also read How to Back Up and Restore Your Files.
    Or you can simply use the Restore option of Disk Utility to clone the drive to the backup:
    Clone using Restore Option of Disk Utility
    Open Disk Utility from the Utilities folder.
    Select the destination volume from the left side list.
    Click on the Restore tab in the DU main window.
    Check the box labeled Erase destination.
    Select the destination volume from the left side list and drag it to the Destination entry field.
    Select the source volume from the left side list and drag it to the Source entry field.
    Double-check you got it right, then click on the Restore button.
    Destination means the external backup drive. Source means the internal startup drive.

  • I bought a mac air retina to replace a mac pro. How can I get all files of the back up and copy them to the new mac?

    I bought a mac air retina to replace a mac pro. How can I get all files of the back up and copy them to the new mac?

    Mail window may be in the Full Screen mode.
    Move the mouse pointer to the top right corner of the Mail window and hold it there.
    Menu bar should drop down and click the blue double arrow icon.
    Full Screen toggle shortcut:  control + command + F

  • .java files appear double spaced in Jdeveloper IDE.

    After checking for updates and not finding what I was looking for, all .java files appear double spaced in the Code Editor. I can't find project property that seems to control this. The files appear fine when opened with other editors.

    How does the file show up in notepad or vi? How does it show up in firefox?
    You might want to evaluate the file with an ASCII reader to see if there are any extra line breaks in the code.
    Also are some of the developers on linux/unix and some on windows?

  • XML DB: As XML file size doubles validate time more than doubles

    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    We have default XMLDB install. I am using schemavalidate() to successfullly validate xml files against a registered xsd. For some reason as the files size doubles the time to validate the file grows at a faster rate than double? We wanted to generate approx 18MB files since they hold 5000 records. But as you can see it appears I would be better off generating six 3MB files instead. What init.ora or xdbconfig.xml parameter might I change to help out with behavior? Any other ideas of why this happening? Is this an example of "doesn't scale"?
    1.5MB 3 Seconds
    3MB 15 Seconds
    6MB 1 Minute
    12MB 6 Minutes
    18MB 16 Minutes
    Code is simple..
    procedure validate_xml_file (p_dir in varchar2, p_file in varchar2) is
    v_xmldoc xmltype;
    begin
    select XMLTYPE(bfilename(p_dir, p_file),NLS_CHARSET_ID('AL32UTF8'))
    into v_xmldoc
    from dual;
    v_xmldoc.schemaValidate();
    end validate_xml_file;

    If I take the clause off the end of the cview table this procedure does not work at all.. It fails at the schemavalidate call...
    Error report:
    ORA-19030: Method invalid for non-schema based XML Documents.
    ORA-06512: at "SYS.XMLTYPE", line 345
    ORA-06512: at line 26
    19030. 00000 - "Method invalid for non-schema based XML Documents."
    *Cause:    The method can be invoked on only schema based xmltype objects.
    *Action:   Don't invoke the method for non schema based xmltype objects.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • All files in the external HDD are not able to open

    HI guys,
    I have an external hard drive for backup. All files in it can no longer be read properly.
    I can still see all the folders and files as usual, but when I double click to open them, they are not readable any more, docx, jpg, pdf etc...
    I tried to verify disk and repair disk, but not able to do it since the hard drive has been converted to NTFS format for some unknown reason.
    It contais a lot of precious pictures and documents. Any solutions would be appreciated.

    It looks like something went wrong with your HDD, it might be either physical (hardware) or logical (software) issue. The worst thing you can do in that case is try to "repair" the HDD with different utilities and eventually corrupt it even further. The best option is to find a Data Recovery company (like http://www.denverdatarecovery.net/ for instance) and send them your disk for free diagnostics so they could tell you if data is recoverable and how complex it might be.

  • Newbie question -  How to read all files for a backup

    Hello all,
    I have two users on my iMac. I am an administrator and the other user is a Standard user.
    From my account, I wish to run backup software that will backup the entire "User" directory. The problem I am having is that when I run the backup software (fyi: iBackup),
    it complains that it cannot read the files in the other user's account.
    I notice that when I browse to the other user's account, all the directories in their home folder are locked.
    How can I run my backup software so that it can read all files in the User directory?
    Thank you kindly!
    Jeff
    17" iMac Core Duo   Mac OS X (10.4.6)  

    Hi kneecarrot !
    I don't know if this will suit your needs, but one easy way of backing up other user's stuff is via the terminal . If you have an admin accountm just use:
    sudo ditto -rsrcFork /Users /Volumes/"nameof_anotherharddrive"/Users
    This will perform an identical clone of all your users home direcories for backup purposes. To restore the bkd'up files, just reverse the lines:
    sudo ditto -rsrcFork /Volumes/"nameof_anotherharddrive"/Users /Users
    ATTENTION: Be aware that it will restore the files to the exact structure and contents it was when backed up, erasing all new and modified files!! You may however copy just the files/folders you want to recover, e.g.:
    sudo ditto -rsrcFork /Volumes/"nameof_another_harddrive"/Users/"usera"/Documents /Users/"user_a"/Documents
    IMPORTANT: As with all terminal commands... be careful, think twice and double-check the syntax. You may want to test with non-critical stuff or demo user accounts first.
    Good luck,
    Michael
    MacBook Pro   Mac OS X (10.4.6)   2 Gig RAM

  • How to bundle all files and directories in a package?

    how to bundle all files and directories in a package?
    i plan to put all image files, .class files and some other files together.and then double click the package to execute the program.
    should i use jar?is there a link for tutorial or example?
    thanks in advance

    http://java.sun.com/docs/books/tutorial/jar/

  • Can't Open Files with Double Click??

    HI
    I am on 10.8.3 Mountain Lion and when using the trackpad or my wireless bluetooth mouse, I cannot open files by double clicking all of a sudden.  This is a serious problem as I cannot view my video files in Final Cut Pro.   There is no click speed preference in System Preferences and I have no idea what to do.  I don't want to have to right click to open any file on my Mac.  Does anybody have a solution for this?  Thanks

    I solved the problem.  If you go to System Preferences > Accessibility > Mouse and Trackpad -  You can set the speed of the double click to be much slower.   Hope this helps someone else with a similar problem.

  • My files is double in itunes.

    How can I remove all the double files in Itunes? In some strange way, all my files is double, and it is double on my hardrive in Itunes folder. The songs are stored like this in the folder: fame.m4a and fame1.m4a. It is too much work to delete them one by one.

    Using Windows, do an Advanced Search for the Name 1 in the folder where you have stored your iTunes Library. The results will give you a list of the duplicate files which you can then delete in one go. You may then have to rebuild your iTunes library by deleting all current content (making sure you choose not to remove the files from your computer) and then add the iTunes folder again.

  • Excel 365 still won't open files by double clicking!

    I know this issue has been posted before but, unlike many, I've started with a clean slate - a brand new machine running Windows 7 Professional SP1. The only Office product I've installed is 365. Like most others, I can open Word and PowerPoint files by
    double clicking but Excel refuses point blank to play ball. I get the "Problem sending data to the program" error.
    I've tried the multitude of "fixes" spread around the forum and the net - to the extent that I can't remember which I've already done when I come across them - and nothing changes.
    Surely (?) someone at Microsoft must have picked up that there is a real problem here, affecting a multitude of users. So why isn't there a unified fix available? Let me put that another way, does anyone know of a unified fix that's available all in one
    place?

    Hi,
    I have definitely heard your frustration, we can try these methods to check if it works.
    Is that error message “There was a problem sending the command to the program”? If so, we can
    turn off the “Ignore other applications that use Dynamic Data Exchange (DDE)” setting. Run “Fix it for Windows 7”.
    http://support.microsoft.com/kb/211494/en-au
    On the other hand, maybe this problem is not in Excel, it is in Windows.  We need to associate the file type with
    corresponding program:
    Right-click the Office       file that you want to open.
    Select Open with,       then click Choose default program.
    Select the appropriate       program to associate with the file, click to select the
    Always use the       selected program to open this kind of file check box, and then click
    OK.
    Next, if the issue still exists, we can choose Run and enter Excel.exe /regserver .This will cause Excel to start up, re-register all of its registry keys, then quit. Now, try opening your Excel files.
    Feel free to post back.

  • "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

  • Photos that have been deleted to aperture trash cannot be viewed. Any assistance is welcome in fixing this bug. The showing all files option is selected in the filter. System is 10.8.4, aperture version 3.4.5

    Photos that have been deleted to aperture trash cannot be viewed. Any assistance is welcome in fixing this bug. The showing all files option is selected in the filter. System is 10.8.4. Aperture version 3.4.5. Used to be able to view the files then all of a sudden they have stop appearing. Once the aperture trash is emptied the files can be viewed in the system trash. Becomes quite annoying if you want to review the aperture trash files before deletion.

    Photos that have been deleted to aperture trash cannot be viewed  ...
    The showing all files option is selected in the filter.
    Cookiemonster, previously Frank Caggiano's magic helped in this situation - have you tried the double, double Caggiano as described here?
        Images not appearing in browser, search filter is cleared
    https://discussions.apple.com/docs/DOC-3062
    In the most recent version I cannot get this trick to work, however. But try it anyway, maybe it is just my macthat has an issue.
    Did this happen directly after the update? Where is your library located, on an external or an internal drive? Are your originals managed or referenced?
    I'd try next to check, if this is caused by the library, by creating a small test library and trying to trash pictures there. If it works well in a new library try to repair the database and the permissions on your regular library.  See:
    http://documentation.apple.com/en/aperture/usermanual/index.html#chapter=27%26se ction=10%26tasks=true
    Regards
    Léonie

Maybe you are looking for