Bret Williams
Forum Replies Created
-
Incorrect. Copying a file from one library to another doesn’t take up any more space on the same drive. Has nothing to do with networked storage. Is that what you’re suggesting? Ever since 10.1, people started noticing that when they upgraded their libraries, choosing to make a backup, that it was instantaneous. And they looked at their libraries expecting to see aliases, but lo and behold, 500gigs had been duplicated. Instantly.
So people started looking into it and discovered Apple was utilizing hard links. They explain it in the video pretty clearly. You can test it out for yourself. Take a huge library and copy all the files to a new library.
For example, take a 300gig project with all the media in the library package. Highlight ALL the media. Create a new library and copy it to the new library. Immediately take a look at the background tasks. All you’ll see is waveforms being created. You’ll instantly find all 300gigs in the new package. Not aliases, not symlinks. Actual media. But it doesn’t take up any additional space. That’s a hard link. Two actual files pointing to the same piece of data on the hard drive. That data won’t be deleted until all files referring to it have been deleted.
-
[Bill Davis] “if you want to use an asset currently in one Library in an event or project in another Library – you have to make a DUPLICATE of the asset and move it into the new Library. That consumes duplicate disk space.”
As long as it’s on the same hard drive, it actually consumes no more disk space. It creates hard links that aren’t aliases and appear in the finder as full media, but both libraries would point to the same media. You can even delete all the media from one project and the other media is fine. It’s rather genius and I wish the entire OS worked this way. Not sure why every operating system doesn’t.
Give it a try. Works the same way when you consolidate a project. Copying all the media is instantaneous and takes up no more drive space.
Here… go to 4:50 https://www.fcpworks.com/fcpx-hard-links-can-save-hard-drives/
-
Are you exporting 2pass? The i7 and its h264 acceleration is much faster than the Xeon when you’re using single pass h264 encoding which is just fine in most cases. It should export faster than real time.
-
I don’t see any roundness or anything at all similar to comic sans.
-
They’re extremely similar. And if I had to choose I suppose I’d choose the tighter helvetica neue. But there is nothing even remotely similar to comic sans in my eyes.
-
I don’t see any font change. Where do you see it. My email just looks like Helvetia, Arial, Verdana etc. Haven’t paid much attention to exactly what flavor. Certainly nothing bubbly or comical.
-
What is everyone talking about? I don’t see any change on my phone. You’re seeing some sort of handwritten comic sans type font?
-
FCP X can’t even run on that machine. It requires at least a 1 gig card. The fact that they called a 512card an upgrade is suspect. Id be amazed if Yosemite even ran with 4 gigs of RAM as well. Adobe or FCP 7 too. So right there the whole post is suspect. RAM for these machines is expensive. You also can’t transfer a license of FCP X. It’s tied to your Apple ID. CS5 is nearing useless on Yosemite. Problems are starting to show. And if that machine even runs El Capitan the Adobe stuff will likely have even more issues if it runs at all.
-
There is not. If you’re trying to send the project to someone then XML is probably the simplest. You can send the whole library or a project.
You could also move the media out of the library package to make the library smaller. Use the library inspector panel and set a new media location then consolidate the media and it will move your files out of the library and replace them with aliases. You could then delete render files to make it smaller too.
You could also try using a copy of an actual backup project from your backups folder (usually in movies folder).
I’m sure others will have other ideas. Just depends on if you’re sharing or actually backing up for safety. If the latter, then I’d probably use the actual backups folder files. But even just uploading an XML is a pretty good backup.
Edit: I forgot you can also just make a library with just the project in it. I think it’s under file>cooy project to new library or something like that. You should end up with a small library with aliases to just the media used in that project and just that project. The appropriate keyword collections will come along too. This is what I do when I finish a project, except I also consolidate the media INTO the library (I keep mine external during the edit) as an additional step and then put it on a mirrored USB 3 raid for long term backup.
-
Why press pause? Why not just undo an click in the timeline before the edit. No need to stop playing, undo, and all this JKL business. cmd z, click. Keep working.