-
slow renders on fcp+nehalem
hello there,
i switched to a new computer the other day. the nehalem with the fastest ATI-card and 16 gig ram and whatnot.
but its renders slow ( at least 50% slower than my previous 3-year old macpro). Color renders slow too..(with the latest ATI radeon)
i always edit with the activity-monitor-cpu-usage-window on my sidescreen.
Normally (with other computers and previous versions of fcp) the cpu’s show half-too-threequarter renderpower in the activitymonitor with a heavy rendertask within fcp.
But now, with my new above combination, the cpu-usage-windows just lays flat, with some of the 16 pictured cores just bumping to 5 or 10% of their max renderpower…
is there someting i’m missing here, ’cause i can’t find other people on the internet having this problem.
cheers,
joppo -
8 Replies
-
Color is pretty much all GPU based, especially for renders, so you’ll not see anything on the cores monitor. Try https://www.atpurpose.com/atMonitor/ to get a good read of the GPU.
I’ve just purchased a new Mac Pro on the basis that the 8-cores are for use with compressor, I’m also getting a Matrox MAX card with it, and the GPU being for Color.
I’ve predicted huge improvements over my current MacBook Pro/MXO2 based setup.
-
hi jack,
thnx for the reply
i know the processors won’t do much in color, but my greatest concern is fcp7 in this case. the cpu is almost laying flat during rendering wich causes unnessesary long rendertimes.. -
I have a similar setup. Final cut just renders slow. Until we get to a 64bit version of OS and Final Cut that is bulit to be multicore aware we are going to be taking render breaks!
James
-
[James Sullivan] “Until we get to a 64bit version of OS and Final Cut that is bulit to be multicore aware we are going to be taking render breaks!”
Mac OS X Snow Leopard is a fully 64-bit OS. Final Cut Studio is not yet 64-bit, because Quicktime is not yet fully 64-bit. Once Quicktime has full 64-bit functionality, Final Cut Studio will follow.
Details here:
https://forums.creativecow.net/readpost/8/1053457
-
okay, i know fcp should be faster, but my problem is now that my nehalem-cpu renders like 5x slower than my 2006 macpro…
update: fcp on the nehalem does a full realtime playback in HD with multiple layers/effects. so it IS fast, but when it comes to actually rendering, it slows down like crazy.
i did a diskspeed test on my internal raid (wich used to work just fine) the readspeeds is about 270MB/SEC and the writespeed is about 6 (!) MB/SEC.
okay, so the disk is propably ****ed. so i connected a HUGE-raid-system through fiberoptic 4Gb/sec on my nehalem; ran the speedtest, and read AND write are now above 280Mb/SEC. but then i started working in fcp again and still the actual renders drops down really slow. so maybe not a disk-error? -
okay, i know fcp should be faster, but my problem is now that my nehalem-cpu renders like 5x slower than my 2006 macpro…
update: fcp on the nehalem does a full realtime playback in HD with multiple layers/effects. so it IS fast, but when it comes to actually rendering, it slows down like crazy.
i did a diskspeed test on my internal raid (wich used to work just fine) the readspeeds is about 270MB/SEC and the writespeed is about 6 (!) MB/SEC.
okay, so the disk is propably broken. so i connected a HUGE-raid-system through fiberoptic 4Gb/sec on my nehalem; ran the speedtest, and read AND write are now above 280Mb/SEC. but then i started working in fcp again and still the actual renders drops down really slow. so maybe not a disk-error? -
[joppo te veldhuis] “i know the processors won’t do much in color, but my greatest concern is fcp7 in this case”
So why start the thread here and not in the Final Cut Pro forum where it belongs. This forum is not a dumping ground for all things Studio.
Walter Biscardi, Jr.
Editor, Colorist, Director, Writer, Consultant, Author.
HD Post and Production
Biscardi Creative Media“Foul Water, Fiery Serpent” now in Post.
Creative Cow Forum Host:
Apple Final Cut Pro, Apple Motion, Apple Color, AJA Kona, Business & Marketing, Maxx Digital. -
I had the exact issue with internal raid -2 month old disk failed – do a permissions on the main drive and send the renders to main drive to see if faster – it might also be a permissions issue with the render folder – worse case dump preferences ….
MINTedit
London, EnglandMac Pro – 8gig ram – FCS 3 – CS4 – Cinema 4D
Film, Edit and Deliver
Reply to this Discussion! Login or Sign Up