-
Fcpx is trying to load every file from 2 tb drive into import window
I wanted to import files into a new event in a new library. I made the mistake of trying to start the import with an SD card inserted in my mac which fcpx interpreted as a camera or archive. I made the worse mistake of ejecting the card while fcpx was trying to import from it. Now fcpx is trying to mount the entire 2 tb drive, a drive which it saw as fully mounted before. It loops like it will take days for it to find everything again. How can I stop this? I will try deleting the library from my computer. Please help asap
-
5 Replies
-
Lists the drive as a camera, not a device like the other external drive I have hooked up. This is after throwing away that new librwry. How do I get fcpx to treat the drive as a device rather than a camera? For now I can move the files I need to import into my other drive, but eventually I will need for fcpx to treat the hard drive normally.
-
Most likely you’ve somewhere along the line copied the contents of a camera card to the root level of your hard drive, causing FCPX to see the drive as a camera card.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Thanks for that insight. So, how can I check if they are there? By the way, I notice when I go to create a new library, fcpx does list the drive as a “device” where I could save the library. But the import window still considers it to be a camera.
-
Whatever is sitting on the desktop (root level) of that drive and reading as a Volume just needs to be placed in a folder and X will stop trying to mount it.
If you have decent desktop organization, it’s usually easy to find the culprit.
If your desktop is a mess, (something I see a lot in creative types!) try making 3 temp folders and temporarily stowaway 2/3rds of the desktop clutter inside their own folders in rotation while you reboot to narrow your focus until you identify which 1/3 group of files causes the problem.
That should help you identify the rogue file even if it’s buried beneath another covering file amidst any desktop chaos.
Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.
-
In most cases it’s a folder named “DCIM” on the root level of the drive.
– Andreas
Spherico
https://www.spherico.com/filmtools“He who fights with monsters should be careful lest he thereby
become a monster. And if thou gaze long into an abyss, the abyss will
also gaze into thee.” – Friedrich Nietzsche, Beyond Good and Evil
Reply to this Discussion! Login or Sign Up