-
Final Cut Pro 7 after Mac OS X Lion 10.7 upgrade
-
I hear you, Paul. People are out of their minds about the latest upgrade and all you get is Bile at the moment.
That said, in general, I don’t recommend ANY major OS upgrades, Mac or Windows until they’ve had one or two .0X updates under their belt. There are ALWAYS problems and you want to be careful with primary production systems.
As far as your test systems go, that’s what it’s there for. Create a back up and go to town. I’ll be doing the same with one of the machines in a lab I teach in. We’ll be checking program compatibility as well as Final Cut Server compatibility, which they’ve completely dropped much to my chagrin.
Hell, I’ve even got an FCPX install I’m playing with to see how it can fit into future workflows.
Apple has to get its act together and communicate better. It also wouldn’t hurt to at least sell some FCP 7 licenses for a while since the new release is such a radical break.
-
Did some testing to see about FCP 7 under Lion. All was okay – Matrox MXO2 mini delivered the same good video to my monitor, projects saving fine, also reopening in Snow Leopard– until I couldn’t get the VO tool to work in the Lion partition. Anybody found a similar problem and solution?
Coruway
Quad 2.8, eSATA RAID, 16 gig RAM, Matrox Mini Max -
only problem i found was when i wanted to render in color and had to keep setting the render directory for every project. previously it would default to a selected for all projects but now every new project has to have the directory set or nothing will go into the render queue…..
-
Just did a clean install of Lion (from scratch) and FCP7 on my MacBook Pro i7. After just one project, the experience is not all that great.
-Lots of “out of memory” errors when rendering, which never happened before, even though I have upgraded to 8GB of RAM with the update. Rebooting FCP seems to fix the problem for a while.
-I have an external monitor plugged though the DVI port, which I use for preview. Picture freezes after 10/20 minutes of use. Refreshing A/V devices doesn’t seem to affect, and the only way to get the picture back is by rebooting FCP.
-Exporting with quicktime conversion is buggy. Some of my final quicktimes (H264) had frozen frames and glitchy audio. Deleting renders and re-exporting didn’t help. Had to export uncompressed and use Compressor. Sending straight from the timeline to compressor was giving “out of memory” errors.
It has just been one project, but my settings have been the same that I have used regularly in this same system for a number of years (ProRes HQ), and never came across any of the above.
I will reinstall Final Cut Studio before the next project, and see what happens…
-
It’s slower overall, on a MBP 2.2 (2007). Which is to be expected with an older machine. However, a fresh Snow Leopard install is more serviceable. You can edit with Lion on this machine, but the video drops too often for fine cuts.
Sincerely,
Daniel Loyd
Editor, Producer
https://DanielLoyd.com -
Bumped up to Lion from 10.6.8 and FCP 7 performance was a disaster. I couldn’t navigate along the timeline without “preparing video for display” popping up every time I moved the playhead, and the general response time was exceedingly slow. When I tried to play a sequence, there were drop frames galore, even on clips without filters. I did a fresh install of FCP on top of Lion, and there was no change.
Currently I’m cutting a film shot on the Arri Alexa, using ProRes 4444 files (not proxy) with Nick Shaw’s LUT applied to all, and prior to Lion I could play down unrendered clips without dropping a single frame – so I know it’s not my system.
I wound up backing everything up to an external drive, reformatting my hard drive, reinstalling Snow Leopard and all updates, then reinstalling FCP . A time consuming pain in the ass, but I’ve noticed a small speed boost and most important, Final Cut is humming along.
Bottom line: FCP seems to run flawlessly for some on Lion, while others are experiencing serious issues. I would resist the urge to upgrade, and stay with 10.6.8 if you want to ensure FCP runs as it should.
-
Updated to 10.7.1 hoping that this would fix the issues with the external monitor (since it addresses a similar problem for iMacs) but everything remains the same. I have also changed the energy saving settings so the computer doesn’t switch between GPUs, but that didn’t do it either.
Another thing I have noticed. No matter what drive I set as my scratch disk, Final Cut will always create a second set of folders inside the user’s documents folder.
Anybody else seeing this?
[Vicente Perez] “Just did a clean install of Lion (from scratch) and FCP7 on my MacBook Pro i7. After just one project, the experience is not all that great.”
-
There are huge problems with certain plugins in FCp and Lion. Red Giant has posted a couple of issues with some of their plugins and Neat Video Denoiser is also having issues. Basically after updating to lion FCP no longer saves information from plugins. So after you add the plugin and then quit FCP you have to reinitialize the plugin on whatever clips you used it on
-
FWIW, I upgraded to Lion when it first came out on my home computer. I don’t do much work with FCP at home, but I do a little bit for personal projects here and there. Recently, I was doing a slideshow for a friends wedding a home on my Lion/FCS3 machine, and everything booted/works fine except a few plugins. Specifically, I was using the Photo Montage plugin from Noise Industries. I could build the project fine and everything worked and rendered, however once I would close the file and reopen it, half the settings I changed on the plugin in the timeline were reverted back to the default. After a lot of frustration, I emailed Noise Industries Support and here is what they said:
I’m sorry for the inconvenience. The problem you’re having is a known issue that appeared with OS X Lion. When Final Cut Pro 6 or 7 are running on Lion, they “forget” to save certain parameter configurations.
We’ve notified Apple of this problem, and we are hoping they will fix the issue in the near future. In the meantime, you have two possible workarounds:
– Use Motion to set up the same animation, using the Photo Montage generators. Motion supports the same effects as Final Cut Pro, and it is immune from the issue.
– Switch to a system that is still running Mac OS X 10.6.8.I took that file to my work computer running 10.6.8/FCS3, reapplied the changes, and it saved with no issues. Outside of the plugin though, I have had no other issues in the limited work I have done on my home machine.
-
Why can I not find my plugins folder? I “unhid” my library (something that Lion does…which is weird), but that doesn’t seem to be the correct library. How do I access my hard drives library?
Reply to this Discussion! Login or Sign Up