The script simply searches your iMovie library (which is really a folder that the Finder treats specially) for movie clips, and finds matching files in a second folder that you specify (the original source of those clips).
It’s available on GitHub, and you can just drop it into some location on your PATH.
To work around these problems, I wrote a very simple Ruby script called dedup-imovie-library. I suppose Apple intends for you to only keep the copy in your iMovie library, but like I said, I prefer to have my files exposed on the filesystem so I can edit them or organize them individually. I have a 512GB SSD on my MacBook, so I don’t have the space to leave duplicate files everywhere. The other problem with the library concept is that iMovie copies videos into its library, meaning you now have two copies on your disk. I prefer to use the filesystem to organize my files, and to be able to use multiple tools in my workflow. iPhoto works in a similar way, wher all your photos get placed inside a library and are no longer accessible to other tools like Pixelmator. This means that you can’t use other editing tools on your video – for example, I prefer use the free GoPro Studio app to do color correction for my GoPro videos, but I can’t open the copies inside the iMovie library. Any videos that you import into iMovie get copied into this monolithic library, and the individual files cannot be accessed from any other application. One thing about the new iMovie that I strongly dislike is that it now consolidates all your files into an opaque “library” which can only be used by a single application. This is a huge win even for the small, simple videos that I put together of scuba diving or flying my quadcopter. The best part about this is that many operations that used to block and make you wait in older iMovies are now done asynchronously, allowing you to keep working while clips import, movies render, or stabilization is analyzed. In fact, it’s pretty clear that the new iMovie is just a reskinned, limited version of Final Cut Pro X. While it initially appears to be oversimplified, it actually still has most of the editing and organizational features that were available in older versions of iMovie, and it moves to a Final Cut Pro X based backend that is much faster and more powerful. Hard linking videos to save space in your iMovie libraryĪfter an initial adjustment period, I’ve come to quite enjoy the new iMovie (2013).
0 kommentar(er)
