![]() I can and do work on videos that are fully animated, motion graphics, or even just have complex titles, such as callouts, highlighted keywords, lower thirds, and so on, video segments that I usually do in After Effects and can constantly be updated while keeping the same file name. I don't know about you, but when I start a production I try, as much as possible, to keep track of all the phases of the work and to have absolute control over all the media that will then flow into Final Cut Pro for the final edit.įor this reason, the fact that there may be assets that reside entirely within the libraries of Final Cut Pro scares me a bit: it's one thing if we're talking about footage, which is essentially static once it has been captured by the camera, but it's another thing altogether if we're talking about files that must comply with strict versioning rules. It can take a few seconds or even several minutes, depending on the complexity of the folder and the number of files it contains.Īt the end, FCP Diet 2 shows a message indicating how many gigabytes have been saved. Simple as that… Everything under control Immediately all the files will be scanned, even the hidden ones, and finally a screen will appear showing all the information about the libraries found, with even an indication of the space you'll save.Īt this point all you have to do is press the Diet button and wait for the processing to finish. But how does it work?įCP Diet 2 is really simple to use: you just have to drag the library or the folder of your project onto the main screen: Over the last few months, during our second Lockdown here in Italy, however, I felt that FCPX Diet 1 had some limitations, especially considering a very simple fact: Final Cut Pro library files are not actually the only part of a project I make, because every time I have to start a new production, I prepare a series of folders and subfolders that contain all the files that will be related to said production.Ĭonsider, for example, the footage shot, stock videos, music, sound effects, speaker, animations and motion graphics, After Effects files,…Įach production is of course different from every other, but generally it is made up of many assets that eventually go into the Final Cut project (and consequently into the library). So I started thinking about an evolution of FCPX Diet 1 that would take into account this fact: the Final Cut Pro library is a central element, but it is not the only one within an entire production project.įor this reason I started to develop FCP Diet 2 (without the "X", since Final Cut Pro X also became simply Final Cut Pro with the transition to version 10.5), so that it was not only a natural evolution of the first version of the program, but could add all those features that are convenient if not necessary when trying to manage a medium-large project.Īll of the software that I write essentially has one purpose: to automate the manual work that I personally do.įCP Diet 2 does the same, not only going to delete all redundant files, but trying to optimize the whole folder, the whole video production project, also performing consolidation and "general cleaning" functions. They always say "eat your own food", and in fact since that day I've been using FCPX Diet 1 practically every day, to manage my video projects. Two years ago, in just one afternoon, I made a very simple application, FCPX Diet (version 1), whose sole purpose was to automatically delete these files.įCPX Diet 1, although it was developed quickly and without too much effort, turns out to be one of the most successful applications I have ever made. I like to get my hands dirtyĪs a good programmer, I have always taken care of "opening" the Final Cut libraries and deleting by hand all the unnecessary and redundant files, an activity that I have always done especially before archiving the projects: the disk space, especially the backup one, has however a cost that must be managed wisely. ![]() Final Cut Pro's libraries are a very interesting object: they are not just a file format (but inside them there is actually a complex folder structure), but they are the beating heart of any project created with this video editing software.įinal Cut Pro X, from its origins, was designed to offer high performance at the expense of disk space occupation. This means that Final Cut's libraries are often very large, tens if not hundreds of gigabytes, because they contain the original files, transcoded files, optimized videos, and rendered files.įinal Cut Pro, in simple terms, " doesn't throw anything away": it means that every render file that is produced, for every single frame, is not deleted, and therefore as you work and work on a project its Final Cut library becomes larger and larger.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |