Jon Cairns
Forum Replies Created
-
If I follow you correctly, you are booting from the new SSD drive so your user folder is on that drive.
Assuming that the “Movies” folder that you listed on your HDD is the movies folder from your previous install then the Final Cut Events folder and Final Cut Projects folder reside within. You would need to move those two folders to the root of that HDD in order for FCPX (prior to the latest version) to see the events and projects.
jon
-
To some extent this is true. There are libraries in both Aperture and X, but Events don’t exist in Aperture.
From a Apple support on using Aperture with iPhoto:
Projects in Aperture are called Events in iPhoto. Likewise, Events in iPhoto are called Projects in Aperture.
It would, for me, make it easier to understand but if Apple was consistent but, hey, I always referred to the “viewer” and “canvas” as program and preview windows.
Jon
-
[Craig Alan] “The advantage for me is that the sparse bundle contains all media connected to that particular film – original media and edited media. I can copy and move the entire contents easier. But I see the advantage of having the origin media on a different physical drive. The media drive would be less full. If the media drive goes down, you still have original files.”
It sounds like we work the same way, only I don’t use the sparse bundle approach. I use a master folder for each project. When I said working drive earlier I meant that that drive had the raw footage and all other media related to that project. So, like you, I can move or copy all of the project contents in one go. Sorry I wasn’t more clear about that.
jon
-
[Craig Alan] “Is this finder folder of camera card folders drag > finder’s folder of the Event or
finder folder of camera card folders drag > the event window in FC?”Drag the finder’s folder onto the proper Event in the Event window.
[Craig Alan] “Also what is your practice to back up original content? I used to save my original tapes labeled with project name, date, A or B cam. Could always reimport using FC legacy’s project file if the media drive died or got corrupted. With cards that get reformatted in the camera what do you do to back up original media?
“In my workflow, I offload all media to two different drives. One will be a working drive and the other is a backup drive. Once a project is complete then all the media gets put onto an archive drive which has a cloned backup drive. I virtually never import media from a camera card into FCPX. I’m not saying not to do that, just that this is the system that I use.
jon
-
[Bret Williams] “Never has my Canon footage been copied to the event using the drag method. I never tried to use the import command. I only use that command for media that requires it.”
Bret,
I believe that we’re saying the same thing. If the import command is used FCP will copy that footage to the Event folder. If the folder is dragged into the Event then the original files will be referenced. The behavior of the Import command changed at some point (10.0.8 or 10.0.9?) to always copy, regardless of the preference setting.
Jon
-
If your Canon footage is in folders which duplicate the camera card structure then FCP X will duplicate the files on import, regardless of whether or not you’ve got “Copy files to Final Cut Events” deselected. The workaround for this, while keeping the folder name as a keyword collection, is to drag that folder into the event from the Finder.
Jon
-
[Oliver Peters] “The timeline window simply won’t hold them all and clears them out at what appears to be somewhat random order. In addition, the layout of this open folder in the project library window is pretty unwieldy once you have a lot of projects in there.”
I like the idea of having this “space” to hold projects but I agree that it’s not very ergonomic. It would be nice to have some viewing options, like changing heights or switching to list view or icon view. Maybe even be able to focus into folders.
Moving from timeline to timeline feels similarly clumsy to me. It would be nice to go directly from one open project to another without either going out to the project library and then back in or “moving through” open projects.
jon
-
Bill,
But it isn’t a finder copy. It’s all done within FCP 7. You stated earlier that you couldn’t have more than one project open in Legacy which meant that you had to reimport footage so you wound up with multiple copies in a scratch folder. What I am saying is that you can have multiple projects open and move elements from one project to another, all of which will reference the original file.
Yes X saves the step of having to open an earlier project to access the element compared to Legacy. Of course if you’ve moved the Event that media is in out of the Events folder then you need to go an put it back online…
Not arguing that the old way is better, just reacting to the impression that you give that you couldn’t move media (references since it’s just the pointer in FCP) before FCPX.
FWIW
Jon
-
[Bill Davis] “And I could only open one project at a time! Perish the idea that I was working in one project and realized an asset that I’d used in another one could help my edit in this one. Walled garden firmly in place. If it’s outside the project, all I can do is go find it an re-import another reference and make sure I remember that I now inefficiently had it in TWO capture scratches.”
However, you can/could have more than a single project open. And drag sequences or bins from one project to another. So reusing assets in a project was doable and you don’t need to copy the files, it simply points to the same files in the same location. But maybe I’m misunderstanding what you mean by reimport it and having it in two capture scratches?
I don’t say this to be combative just to point out that that isn’t new. I’ve implemented X into our workflow so this isn’t a “Legacy is better and X is flawed” argument.
Jon
-
Alternatively, you could just buy a portable firewire drive. Install leopard onto that drive and then just boot from that drive when you need to transfer P2. It’s an extra drive to carry along which is a consideration but it works.
Jon