TOPIC:

OK...so I know better now...but is there a way to recover from what I've done? I have a very fast external hard drive (1 TB) where my library exists. (In retrospect I realize now that this drive *probably* needs to be bigger!) All of my media is organized into folders under a single top folder for each project that I do (located on the external drive). So...that means that I have "double files" on my drive...along with all of the render working files (I've learned how to get rid of those to give me some breathing room.) I know that better speed can be had by having the media and library on separate drives is better...but I'm happy with the speed I have...for now, anyway.

Am I stuck with the way this particular library was created? Is there any way to "revert" from having those imported files exist in the library? (Even if I have to jump through some hoops to accomplish this goal?)

OK...I think I've answered my own question. I found an article about consolidation. I think I've resolved my original question but I now have a secondary question.

I originally had "folder 1" containing all of my original media. As I imported, it was going into the library. I have since consolidated into "folder 2"....all being on my external drive. Am I correct in understanding that "folder 1" was dead as soon as it was originally imported (into the library)? Can I safely delete "folder 1"?

You could open both folders in the Finder and manually compare the names, dates, and sizes, in order to verify everything is in the new folder that was in the old folder.

Or, you could use Terminal ("diff" command) to compare both folders. If you don't mind acquiring a new application, Beyond Compare  is an excellent application.

I remember somewhere in a video or tutorial from Ripple... if you look into the package at the media when files are left in place, you'll see the same media names, but as aliases to the originals. So, and this is the magical part as I remember, if you accidentally imported into the library, you can simply select all the files in the event browser, and use relink to relink them to the originals outside of the library. Check back into the package and all the files are replaced with aliases. Boom done. I'm not sure where the files went, maybe the trash, so maybe you have to empty the trash or something. But this is a one step method to fix the issue.

Bretwilliams wrote:

...if you accidentally imported into the library, you cly select all the files in the event brower, and use relink to relink them to the originals outside of the library. Check back into the pack,age and all the files are replaced with aliases. Boom done...

Bret, thanks for mentioning this important point. It's easy to unintentionally import media with "copy to library", do some work, then realize you wanted "leave files in place" external media.

Using the consolidate method to move media out of the library works. However upon the original import within the library, FCP uses a different folder structure. If any on-disk files had duplicate names (even though in separate folders) FCP adds the suffix (fcp1), (fcp2), etc. to avoid a filename conflict. This is especially likely with Sony filenames like C0001.mp4.

The consolidate method of moving media out of the library works but (1) It required another physical move and (2) Some users rely on folder structure and filenames for recordkeeping.

I recollect that in past versions the procedure you mentioned would not work or might have been unreliable. However, I just tested it several times on Intel & Apple Silicon versions from 10.5.2 to 10.6.5 and it now works very well -- provided all filenames are unique. If the filenames are not unique, then relink will not work because the imported filenames were given (fcp1) suffixes and the original files have different names. This is another example of why all media filenames should be globally unique, not just in the current library but across all libraries and all archival storage.

There were significant relink changes in 10.4.9 for proxies, so maybe the above relink behavior changed for the original media files then. I can't remember.

You are correct, after the relink the internal files are no longer there.

Unfortunately moving the files out of the Library via consolidate doesn’t fix the space saving issue as you’re moving, not deleting. And at some point in the future, you may not have the media any longer, and need to relink to originals, which are somewhere on card backups, with potential duplicate file names, and now, due to FCPs meddling in names and folder structure, a huge PIA to figure out which to relink.

These duplicate file name issues are yet another reason to avoid importing to the library. If you leave in place, with the original card structure, relinking duplicate file names is never a problem as FCP will tell you specific file path the file used to be in- eg Brads Cam>Day 1 > (card structure). The ability for FCP to tell you the card and file path or the original file off the camera/cam backup is priceless. Letting FCP manage media in any way mangles that relationship. For 11 years I’ve always left in place wherever possible and duplicate file names aren’t an issue because of it. Of course there’s a million other ways to skin a cat. Just my method. YMMV.

Many thanks for all of the great info! All of this is good to know for my future endeavors, but I'm still looking for a definitive answer specific to my "folder 1" issue in the OP. Once I have done a consolidate into "folder 2" (from the wrongfully imported library) I see that it appears to have resolved my issue as far as library file size reduction...but is "folder 1" now "dead" at this point with all media now residing in "folder 2"? Can I delete "folder 1"?

Technically yes. If all the media is now linked to folder 2. But only you know for sure. If you had just relinked to Folder 1 instead of consolidating, you'd be done now. Same result, but you'd keep the original folder 1 structure. I'm assuming folder 1 is a copy of your card(s)? I'd still relink to that and ditch folder 2 personally. Definitely keep the Library on the external, usually in the same "job" folder as all your media and other resources. You CAN keep it anywhere you want, but all your renders and other transcodes and caches will be in your Library. If it's on the high speed external with your media, then it's playing back from the cache in the library, on a fast drive. If it were on your internal, you'd risk the internal filling up with cache and grinding your system to a halt. Again, a million different ways to do this stuff. Just my .02