Events and Projects Librarys Missing in FCPX (but folders and videos in finder exist)

[Mitch Ives]

[Bill Davis] “If I read all the threads correctly, it seems this isn’t actually a Final Cut Pro issue so much as an underliing Unix file tree issue.

Perhaps, but I don’t think so. The only issues with UNIX involve the use of punctuation in the filename. All of these words can be used in file names and work fine under FCS, AE, Motion etc. It’s FCPX that seems to be having some kind of issue with some aspect of this.

[Bill Davis] It starts with the poor practice of doing FINDER copies of card data that creates essentially false directory tree branches that X “thinks” leads to cards – but don’t.

How can the program tell whether a particular DCIM file is a proper camera clip or a finder tag for an asset collection? My brain can supply context based on where amongst the thousands of possibilities I put it – but I don’t think the computer’s directory is going to parse that.

So those of use who have been using card based cameras longer than you and doing finder copies without any issues are suddenly wrong. Okay…

[Bill Davis] Bottom line. Archives and/or Disk Images are your friend, since it appears that FCP-X never gets confused no matter how many of them are on a hard drive and how many you open to re-populate your projects. They just work and simultaneously keep all the directory structure info in precisely the same state it was when the card came out of the camera.”

So once again, we need to change the way that we do things because Apple has decided “theirs” is a better way. There’s a reoccurring theme here. Funny how we didn’t need to do that with ANY other program.

BTW, if I read that thread correctly, Steve Martin has confirmed that making disc images under Lion doesn’t work like it did under SL. In fact, I believe he said it doesn’t work. The Command File-New-Blank Disk Image has indeed been removed in Lion. Are you making Disk Images? If so are you using Lion? If so, I’d like to know how you you are doing it?

Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com
http://www.insightproductions.com

“Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.” – Winston Churchill

[Eugeny Korkhin]

Let’s put it another way. This problem can be easily recreated. I have just tested that. Creating a new folder named DCIM in the root of the hard drive makes all the projects and events on that volume disappear for FCPX. Once you delete that folder, they are all back. So, make sure you don’t have DCIM in the root. And who knows what other names of folders or places they are located in can cause that trouble.

[Bill Davis]

I just use the same workflow I’ve been using for the past two years and it’s still working perfectly. (Including under Lion – which I’ve used for the past six months without a single problem in my editing workflow.)

Mount your camera card via the finder. (I happen to use a USB card reader, but direct connecting the camera via USB works the same.) Then launch the Apple free “Disk Utility” software and choose “new disk image” from the menu bar. Select and image the card.

Done.

If you want to take the time to re-name the disk in the finder prior to imaging it, feel free – or don’t – it really doesn’t matter in the long run and freshly formatted cards that are UNTITLED won’t cause fatal problems later – but you might like having ID tags on your desktop for your mounted cards later – your call.

Even if you launch a dozen archives so that you end up with a dozen “Untitled” cards on your desktop – X keeps it’s act together, likely referencing the underlying “virtual disk ID” data rather than just the finder names.

The bottom line is that there are workflows and habits that lead to success in all complicated processes – and usually small “gotchas” in all sorts of specific workflows. Thus it has ever been – thus it will ever be.

I honestly don’t think it’s on Apple to protect us from ALL possible workflow snafu’s, since there are just WAY too many possible combinations of ways to do things.

It’s on us to do what this thread is all about – share “best practices” so that people can learn about what avoids the problems.

If we wait for our software to be “perfected” before we use it – we’ll likely be waiting forever.

FWIW.

“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor

[Jeremy Garchow]

I think we are talking about two different disk images here.

BIll, you are talking about a disk image that essentially makes an image of the selected “disk”.

Andy, You’re talking about sparse disk images for media storage.

Spare disk images for media storage (while clever), in my opinion are not a good idea. Just my opinion.

Since they aren’t working in Lion as they did in Snow Leopard, that’s a pretty good reason to stay away from them and manage Events/Project via Apple’s recommendations in the FCPX manual, or use a rather excellent front end of the Finder in Event Manager X. Worth every penny of just under 5 bucks.

Jeremy

[Eugeny Korkhin]

Jeremy, you are absolutely right – They are speaking different languages, for sure. But what is even more surprising, is why would they still discuss the way they work with images in this exact thread? Who cares? You may be putting whatever you want in images, even your .doc files, but let’s get back to earth – John is still missing his events and projects and I think he wouldn’t mind some real advice, rather than read your arguing.

[Jeremy Garchow]

[Eugeny Korkhin] “Jeremy, you are absolutely right – They are speaking different languages, for sure. But what is even more surprising, is why would they still discuss the way they work with images in this exact thread? Who cares? You may be putting whatever you want in images, even your .doc files, but let’s get back to earth – John is still missing his events and projects and I think he wouldn’t mind some real advice, rather than read your arguing.”

Wow, sorry to offend. I thought the points were valid especially to a new user. There’s something to be said for techniques that arent working, no matter how the thread started. I’m curious if the OP has tried moving the media to a different drive.

No answer.

[John Smith]

I have no folders called DCIM on my system.
I am not using Lion I am using Snow Leopard 10.6.8
I am not making disc images.

I cant see how moving the media to a different drive is going to do anything seeing as it FCPX cant see it when its directly on the main internal hard drive itself (That everything else is on too)

Thanks Eugeny Korkhin for trying to get this back a little more on topic

Any more suggestions on how to sort this problem please?
I feel that there needs to be some kind of way to tell FCPX which folder to find events and projects in.

Thanks

[Jeremy Garchow]

[John Smith] “I cant see how moving the media to a different drive is going to do anything seeing as it FCPX cant see it when its directly on the main internal hard drive itself (That everything else is on too)”

Just to see if FCPX can see another drive, and therefore get you back up and running.

Or do you not want any help?

It will also tell you if there’s something wrong with the actual event/project or not.

And as always, trash your prefs.

[Mont Sherar]

I can truly understand and FEEL your frustration John.

I too have had the same issue. Even when making dupes from within FCPX to another drive (selecting copy ALL references etc), sometimes certain clips including audio is simply missing. It is there perfectly on the drive. Its a pure copy from one drive to the other. And yes, I’ve tried several different drives. Reinstalling. Trashing prefs. Even buying an expensive utility just for fixing FCPX from Digital Rebellion – to NO AVAIL.

Not to sound cynical but it is amazing how some simply “insist” it must be no fault of the app (FCPX) because THEY have never had the same experience. Then, the same advice over and over. Trash prefs etc.

This is clearly a BUG. Period. As mentioned, it is not even consistent in its behaviour even though THE HARDWARE, SOFTWARE, AND ACTIONS selected are identical to recreate the problem! (FCPX sometimes seeing clips/audio – and sometimes NOT when making backups and then reloading from that dupe.)

Someone wrote here that perfection is not to be expected. Sure of course that is true. Patronizing to suggest that anyone wouldnt think that! BUT, to expect a video-editing program to perform proper connections of media is something that should be a GIVEN prior to releasing it! Otherwise, dont release it until first base is reached – that is just OBVIOUS! Why do some feel the absolute urge to defend these complete BASICS of expectations? Oh wait, it must be because THEY dont have the problem – therefore it isnt something that THEY worry about…..lol…

I understand you completely John, and unfortunately it appears we need to wait until a future (hopefully the next one) release before something as basic as this can be realized.

[Mont Sherar]

Here is some possible useful info re. media suddenly “unconnected”.

Begin from time 124:40
https://www.youtube.com/watch?v=UmHMzm2oQlU

It shows a common problem – that is, the user has the playback setting selected that are not valid for the media (proxy media is showing up as “offline” because proxy is not selected in playback) etc.

HOWEVER, note after this is discussed, they also CONFIRM their own experiences for “media not connecting for “unexplained” reasons ….. and these are not dumb, inexperienced users like me ;-)))

“trash preferences” lol…

The best way to get something done is to
++++++++++B E G I N +++++++++++

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.