Brett Sherman
Forum Replies Created
-
It should work fine with Sparse Bundles. It looks to me like the only limitation is that you can’t use materials on another Sparse Bundle without FCP X copying it into the one where your project resides.
-
[Bret Williams] “all would function as it did before. Store all the one event libraries in a folder called final cut event libraries at the root level of your drive if you feel like it. You could also have a library that only has projects, no events. Or one project per library and store it at the root level in a folder called final cut project libraries. But now, you can put these things wherever you want, and mount and unmount at will. I think it really gives you more options.”
Actually on further thought, it wouldn’t work as it did before. If I create a Project in it’s own Library I think that means it will create new media every time I put a shot in from an Event that’s not in that Library. It’s going to lead to a lot of unnecessary file duplication, which not only will waste space, but will slow down performance while it’s copying. Basically, I see nothing here that I wasn’t already doing better and more flexibly with Sparse Bundles.
-
I don’t think there are enough feature updates to justify Apple charging for it. I think that’s the bottom-line rather than having free updates in perpetuity.
-
I hate to say it. But I agree with you. A bit of a disappointment in my book.
-
I’m probably going to stick with it the way I have it (using sparse bundles for individual events) for awhile until I can see a better way. It’ll be an extra step of creating a library each time I make a new event. And of course it’s going to be a good couple days of creating library files from my old events and projects with no benefit. But if it makes other people happy, I can deal with it.
-
I’m definitely getting the 6-core. The price difference to get a 25% processor increase (only in the best scenarios) is simply too great. Anything less than 512 GB for the drive would be problematic for me. The question is which is better – upgrading from 32 to 64 gb or going D500 to D700.
-
I’m always a proponent of getting things right rather than rushing to put out the latest, greatest. You’re right the update of the Mac Pro took way too long. That had little to do with the new imminent Mac Pro. But now we know its almost here. So waiting a few weeks I think is probably inconsequential in the long run. In a few months who will remember whether the release was December 1 or December 20.
-
Only the top of the line MBPro 15″ has Nvidia graphics. The rest use Intel Iris. I’m not currently up on what the Iris is capable of, but my guess is that the Nvidia is going to be much better. And GPU performance is becoming more important as indicated by the new Mac Pro with 2 GPUs.
-
Good to see another Marylander on here! My workflow is I export a ProRes Quicktime file and then I use Turbo.264 Software Encoder to make my MP4 from that. It’s well worth the $50. It’s fast and compresses much better at lower bit rates than Apple’s encoder. I have a setting that is 720P, 5000Kbps and I rarely see an artifact.
-
My sense is that unless you are releasing a feature film, high-end television production or something targeted to pixel peepers you’re safer sending out a DVD. For the kind of work I do, which is advocacy, we do not want anyone to not be able to play what we send out. So lowest-common denominator for us – DVD. But web more often than not. Blu-ray never reached the critical mass where if you sent out a disc, you know someone can play it. It never will either.