-
Brand new £10k Mac Pro 12 core – Final Cut Pro crashing relentlessly!! :-(
I bought a new Mac Pro last week. Here are the specs
2 x 2.93 6 core (12 cores)
16Gb Ram
512Gb SSD
1TB Sata
2 x Radeon HD 5770
2 x 27″ cinema displays
FCS3 with FCP 7.03
OSX 10.6.6
All software fully updated.Magic Bullet Looks installed
Noise Industries FX Factory installed
Calibrated Software MXF Import OSXI have recently been doing a lot of shooting in Brazil, LA & Vegas. I used a Canon XF305 1080i 50mbs.
The calibrated plug-in was installed so I could drop the MXF files into FCP. I’ve only been using the machine for 4 days, so it’s clean apart from what’s listed above. When I was cutting footage with no filters or effects or cropping/distortion, anything.. Just clean cuts, it seemed fine. As soon as I started doing spilt screen, adding bad tv effect and MBL looks filters, I get symptoms such as Juddering footage, constant crashes, out of memory error message, bad codec message. Wouldn’t render properly in compressor. It was only an hour of footage cut into 2 mins…
Here’s the final result > https://www.youtube.com/watch?v=p1EJzJXRhpQ
The only reason I got a finished product was I had to keep re-booting all the time, and it took about three times as long to do it.
WHAT’S UP WITH IT??
I just paid almost £10k for a new mac system and it doesn’t work!! I’ve also bought an EX3 but not edited any footage yet. Although, the last Mac I had (Quad-core) 2 years old worked fine with EX3 footage using MP4 plug-in from calibrated software. No problems at all….
I spoke to Apple care and they informed me I didn’t need two cards (which I thought I did, why didn’t the reseller tell me!?), so I plugged both monitors into one card. It seemed like it did the trick, but as soon as I added filters, MBL looks, the same problem occurred. I’ve got loads of deadlines and this is driving me crazy! Can someone please help!!!!
Nick
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
12 Replies
-
The crash logs should help to track down what is causing constant crashes. Two graphics cards are certainly not needed and could be a problem.
-
[Nicholas Treharne] “WHAT’S UP WITH IT??”
In my experience, the only problem may be that your system is a MESS.
A fresh installed system/application is far from being optimized to work.
I would start by repairing permissions; then rebuilding directories with Diskwarrior or TechTools.
rafael -
[Michael Gissing] ” Two graphics cards are certainly not needed and could be a problem.
“
Good point.
Don’t use both. Connect both monitors to the same GPU.
rafael -
Final Cut Pro has never supported multiple graphics cards – it’s a well documented issue and anyone who has spent any time installing FCP systems should know this.
I’d agree that after a fresh install a computer’s drives can be a bit scattered but in no way should this cause constant crashing.
I’ve never used the Canon XF305 but the Canon recommended workflow is to use their plugin to convert the footage to ProRes. This might take a bit of extra time but it will be a lot more stable and probably nicer to work with as a whole (All long GOP video is a pain in my opinion and to be avoided at all costs)
————————
FCP and Avid Technical Support
Air Post Production
Shoreditch – London -
Dual Graphics cards. Get rid of one of them.
Walter Biscardi, Jr.
Editor, Colorist, Director, Writer, Consultant, Author, Chef.
HD Post and Production
Biscardi Creative MediaRegister now for our Open House March 5
-
[Gary Askham] “I’ve never used the Canon XF305 but the Canon recommended workflow is to use their plugin to convert the footage to ProRes. …… (All long GOP video is a pain in my opinion and to be avoided at all costs)”
That was years ago.
The Canon works with XDCAM-HD 422, optimized to work natively on FC.
I work with NANO-Flash files XDCAM-HD 422 (some times at 280Mbps . Canon is just 50Mbps) and I never transcode. No problems.
rafael -
Thanks for your input guys…
This is how I’ve proceeded…
I had 2 x Radeon HD 5770 cards in slots 1 & 2. I removed 1 card from slot 2 and rebooted. Even before opening final cut the left monitor display was juddering and displaying random dots. I removed that card from slot 1 and placed the card I removed previously in slot 1. Displays seem stable. I have opened Final Cut and scrubbed through my project with no side effects as yet, although I haven’t performed any new renders/filters/etc… I’m going to edit as normal this afternoon and add filters etc. I pray that it stays stable and that’s the end of it.
-
Ok. So clean editing has been ok so far and using Soundtrack Pro. However, I just installed Magic Bullet Denoiser and it crash FCP immediately. I had already informed Red Giant yesterday about MB looks crashing system and they sent instructions to change permissions, which I have just done. I’m not going to install denoiser until red giant advise. I have sent them the full crash report. This is the top of the crash report. What do you think? Also do you think I should run my system as 32 bit and not 64 bit as someone else has suggested? Thanks.
Process: Final Cut Pro [530]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCutPro
Version: 7.0.3 (7.0.3)
Build Info: FCPApp-1008261348~8
Code Type: X86 (Native)
Parent Process: launchd [105]PlugIn Path: /Library/Plug-Ins/FxPlug/Denoiser.fxplug/Contents/Resources/libGPPIPAPI_IPP.dylib
PlugIn Identifier: libGPPIPAPI_IPP.dylib
PlugIn Version: ??? (???)Date/Time: 2011-03-05 15:52:52.086 +0000
OS Version: Mac OS X 10.6.6 (10J567)
Report Version: 6Interval Since Last Report: 163264 sec
Crashes Since Last Report: 34
Per-App Interval Since Last Report: 113568 sec
Per-App Crashes Since Last Report: 26
Anonymous UUID: 037FC068-CB9E-482E-80AE-FA95997F7133Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000e7676003
Crashed Thread: 0 Dispatch queue: com.apple.main-threadThread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libGPPIPAPI_IPP.dylib 0x4535892f p8_ippiCopy_8u_C4CR + 191 -
FCP is a 32 bit app so you should be running 32 bit OS
-
Hello
I am editing with a prores LT sequence. There is only one working gfx card in the machine. I have switched to 32 bit. It still judders and crashes…
Any help?
Reply to this Discussion! Login or Sign Up