Activity › Forums › Apple Final Cut Pro Legacy › New MacBook Pro and Final Cut 2 (sucks?)
-
New MacBook Pro and Final Cut 2 (sucks?)
Steve Martin replied 17 years, 5 months ago 13 Members · 27 Replies
-
Andy Mees
October 29, 2008 at 12:32 amHey Peter
The general perception is certainly that FxPlugs render in hardware… but isn’t that actually dependent of the FxPlug’s coding? I believe they can be coded to render in either software (CPU) or hardware (GPU) and that where such a choice exists FCP will actually render on the CPU? ( I think that the preferred route is actually FCP specific )
Enquiring minds and all that.
Andy -
Zane Barker
October 29, 2008 at 4:10 amSome trouble shooting questions for you Justin.
[Justin Robots] “I just picked up the new (late 2008) MacBook Pro entry level option (2.4ghz). It’s replaced my entry level 1st Gen MBP (1.8ghz). “
How much ram in the old one and how much ram n the new one?
[Justin Robots] “After installing FCP right after opening the box”
Did you run ALL the updates?
[Justin Robots] “On my other machine it is taking about 5 hours to complete. So I really have no idea why this new machine is being such a dog.”
Have you set up a virtual cluster for allowing compressor to use ALL the cores in the processor? You easily could have done that on the old one and not have don’t it on the new one, that would make a IIG difference.
There are no “technical solutions” to your “artistic problems”.
Don’t let technology get in the way of your creativity! -
Rafael Amador
October 29, 2008 at 4:41 amHi Zane,
Is it worth to set a virtual cluster in a double processor computer?
Rafael -
Zane Barker
October 29, 2008 at 4:49 am[Rafael Amador] “Is it worth to set a virtual cluster in a double processor computer? “
Well I certainly notice a difference here. With out it compressor only sends things to one or the 2 cores.
There are no “technical solutions” to your “artistic problems”.
Don’t let technology get in the way of your creativity! -
Zane Barker
October 29, 2008 at 5:11 am[Rafael Amador] “Could I get even better performance with it? “
Do a test with it thats what I did.
There are no “technical solutions” to your “artistic problems”.
Don’t let technology get in the way of your creativity! -
Rafael Amador
October 29, 2008 at 5:15 amHi Zane,
I’m working with my MBP Core2 Duo 2.4 and I see in the Activity Monitor a 150-160% of CPU without setting the virtual cluster. Could I get even better performance with it?
Rafael -
Jeremy Garchow
October 29, 2008 at 5:28 amNot that I have seen. The general rule of thumb is to set the number of instances to half the number of cores. That would be setting the instances to one in a dual core. That’s what Compressor will use on the MBP anyway when submitting to Compressor. It doesn’t spilt it up. In my very informal tests, the cluster actually slowed it down a bump. Putting the instances on two slows it down even more.
I’d keep the cluster off on MBPs until they double the cores.
On MacPros, no doubt you should set up a cluster.
Jeremy
-
Justin Mcclusky
October 29, 2008 at 12:58 pm2gb of Ram in both machines, set up in parallel.
All updates have been installed as well.
I have tried to set up an actual cluster, as well as a virtual cluster. The virtual cluster AND the real cluster (between the old and new machine). Unfortunately the clustering does not play very nicely. Consistently it gives me errors of not being able to connect and ‘unexpectedly quit’ messages for various portions of the split up batch. Any ideas on that? I’ve heard mixed reports on that working at all.
I have a feeling that it may be how the new MacBook Pros handle the heavy lifting of Final Cut. Specifically, it’s crunching a semi high-def file in H264 and having major problems dealing with that. I don’t have QT pro on the new machine, although I’m skeptical that is the problem.
At this point I’m debating on returning this machine for a 2nd Gen MBP with equal or higher specs. It’s a real shame. However I’ll be reformatting and reporting on the fruits of that later.
Thanks again
-
Tom Brooks
October 29, 2008 at 1:13 pmThat would explain my informal findings in the heat of production last week that Compressor worked faster with QMaster sharing off. Quickcluster was set to two and it went nowhere. Turned it off and zoom.
-
Jeremy Garchow
October 29, 2008 at 1:36 pm[Tom Brooks] “That would explain my informal findings in the heat of production last week that Compressor worked faster with QMaster sharing off. Quickcluster was set to two and it went nowhere. Turned it off and zoom”
Do you have a MacBook Pro?
and by the way:
and the dance mix:
Have a good day,
Jeremy
Reply to this Discussion! Login or Sign Up