gen_

Q: Logic X search by extended attributes

Okay, so this is what happened.

 

Mid-12 hour session, my HDD maxes out on space. Knowing that my backup is a much larger drive (I use CCC instead of Time Machine), I foolishly dragged the Logic X file from it's location to that drive. Bear in mind I do backups at the end of each day, so there is no evidence of the file there yet. I hit play to see if Logic would auto-locate these files then continued when it did.

 

A few GBs in recordings later when I manually hit save, I realise that it has saved to the original drive, so Save As then direct it to the new one. Bad move. It seems Logic deleted the package then realised that none of the file pathways worked, so simply saved the new recordings in an empty project (all regions from before the copy are now blank containers).  

 

Now I think I've recovered the files using Disk Drill, but they are all named sequentially. (file0001.wav etc etc) Is they any way in which I can have Logic check the hex or hash of the files to find which is which or do I have to manually slog through 300-ish recordings.

Logic Pro, OS X Yosemite (10.10)

Posted on Sep 3, 2016 5:45 AM

Close

Q: Logic X search by extended attributes

  • All replies
  • Helpful answers

  • by BenB,

    BenB BenB Sep 3, 2016 6:08 AM in response to gen_
    Level 6 (9,816 points)
    Video
    Sep 3, 2016 6:08 AM in response to gen_

    CCC backup drive is a BAD idea to use for work.  When it kicks in to do a backup, you'll have stuff missing, if it wasn't on your original drive.  And no, you'll have to manually relink all those files.  When you move a project for any Apple pro app, it is best to do it on the Finder level manually, and verify you've got everything in tact.  Otherwise, they use hard and soft links in various situations to save drive space.  Which can mess you up doing things like this, on backup drives, that alter contents when the backup software kicks in.