It’s been almost 4 years since the last update of FCP 7. The last officially supported OS was 10.6.8. It’s time to move on people.
Beauty Box Video 4.0 (due out in a month) will be our first product that does not officially support FCP 7.
It’s a great video editor but Apple make it very hard to support older software. Especially if you’re trying to run it on newer systems. If FCP 7 is a mission critical app for you, you’re taking a pretty big risk by trying to keep it grinding along. We started seeing a lot of weird behaviors with it and 10.9. I realize people are running it successfully on the new systems but we feel there are a lot of cracks beneath the surface. Those are only going to get more pronounced with newer OSes.
I know people love their software, hell there are still people using Media 100, but Premiere Pro, Avid, and even FCP X are all solid alternatives at this point. Those of us that develop software and hardware can’t support stuff that Apple threw under the bus 3 and a half years ago.
We will continue to support people using Beauty Box 3.0 with FCP 7 on older systems (10.8 and below) but we can’t continue to support it when most likely the problems we’ll be fixing are not caused by our software but by old FCP code breaking on new systems.
What causes Final Cut Pro X to re-render? If you’ve ever wondered why sometimes the orange ‘unrendered’ bar shows up when you make a change and sometimes it doesn’t… I explain it all here. This is something that will be valuable to any FCP user but can be of the utmost importance if you’re rendering Beauty Box, our plugin for doing skin retouching and beauty work on HD/4K video. (Actually we’re hard at work making Beauty Box a LOT faster, so look for an announcement soon!)
Currently, if you’ve applied Beauty Box to a long clip, say 60 minutes, you can be looking at serious render times (this can happen for any non-realtime effect), possibly twelve hours or so on slower computers and video cards. (It can also be a few hours, just depends on how fast everything is)
Recently we had a user with that situation. They had a logo in .png format that was on top of the entire video being used as a bug. So they rendered everything out to deliver it, but, of course, the client wanted the bug moved slightly. This caused Final Cut Pro to want to re-render EVERYTHING, meaning the really long Beauty Box render needed to happen as well. Unfortunately, this is just the way Final Cut Pro works.
Why does it work that way and what can be done about it?
Continue reading How Final Cut Pro X Caches Render Files (and how to prevent Beauty Box from re-rendering)
In the process of putting together a number of tutorials on time lapse (particularly stabilizing it), I discovered that FCP X does not import image sequences. If you import 1500 images that have a name with sequential numbers, it imports them as 1500 images. This is a pretty huge fail on the part of FCP. Since it is a video application, I would expect it to do what every other video application does and recognize the image sequence as VIDEO. Even PHOTOSHOP is smart enough to let you import a series of images as an image sequence and treat it as a video file. (and, no, you should not be using the caveman like video tools in Photoshop for much of anything, but I’m just sayin’ it imports it correctly)
There are ways to get around this. Mainly use some other app or Quicktime to turn the image sequence into a video file. I recommend shooting RAW when shooting time lapse, so this means you have to pull the RAW sequence into one of the Adobe apps anyways (Lightroom, After Effects, Premiere) for color correction. It would be much nicer if FCP just handled it correctly without having to jump through the Adobe apps. Once you’re in the Adobe system, you might as well stay there, IMO.
No, I’m not a FCP X hater. I just like my apps to work the way they should… just as I tore into Premiere and praised FCP for their .f4v (Flash video) support in this blog post.
What’s wrong with this picture?