![]() One final point about working with libraries is that you can have as many libraries open as you want, editing content freely between them. This is important if you are sharing media on a SAN with other editors! If you decide you need to change your storage locations for your library you can change the location in the Inspector then choose the consolidate option to bring all your media together.Īn important point regarding consolidation is that FCP X itself will never delete, move or otherwise alter a file outside the library (what FCP refers to as external media). These import options are applied whether you use the import window or simply drag and drop the file(s) from the Finder into your Event. If you don’t want FCP managing your media for you (by either copying it into your library or to the specified media location), choose the option to “Leave files in place” - that way FCP will handle media in the traditional way Premiere has, by referencing the original file directly. ![]() ![]() You can see these settings in the Inspector:īy default, these settings keep everything in the library bundle, but you can modify them to be kept anywhere on your system.įurthermore, checking your import preferences will tell you how FCP will be dealing with newly imported media. Your library has settings for how its media and other elements should managed. Ultimately, the library still keeps track of the media and how the media is being used via a database file that’s constantly updated as you edit. The library is a package containing lots of information used by FCP X. In Final Cut Pro X we deal with Libraries and Events. Nevertheless, in Premiere Pro project files and source media files tend to live and be managed separately. Up until fairly recently Premiere wouldn’t move or copy imported media, so you’d have to manually manage your source media files before import. The Scratch Disks specify where media, render files, and autosaves are stored, whereas the Ingest Settings instruct Premiere what to do with newly imported media. When you first create a project, you’re asked how that project should behave. These project files tell Premiere how it should operate, where the media is located and how it should construct that media into the edit. Premiere Pro works with project files, similar to those of FCP 7. Part of my job over the last few years has been to help demystify the different software to either find those common workflows or help people develop new ones, especially if a client is willing to pay you to edit, but are specifying a particular piece of software. they have a specific way of working that they’d like to replicate on the new system. In many cases the people switching often have specific questions about workflows - i.e. Over the last few years I’ve spent a lot of time helping “switchers” get to grips with changes and updates to video editing software - whether it’s been Avid or FCP 7 editors moving to Premiere Pro or Final Cut Pro X. We asked Chris Roberts (who’s both an Apple Certified Trainer and Adobe Certified Instructor) to help Premiere Pro editors draw parallels with FCP X. But, as FCP X becomes more widely used throughout the production industry, we thought we’d dedicate a little space to helping those familiar with other NLEs get to grips with our favourite editing platform. Here at FCP.co, we are all too familiar with the advantages of a Final Cut Pro X workflow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |