- May 1, 2009 at 7:32 pm
Final Cut has been crashing during timeline playback (in different places.) No spinny pinwheel, no error message, it just suddenly freezes and sends screeching digital audio noise to your headphones. Nice. Can’t force quit, just have to hold the power button down.
We’ve just upgraded to 24″ iMacs and FCP 6 after years of cutting DV offlines on FCP 5 with ancient G4’s. Our projects are straight ‘cuts and dissolves’ story segments with maybe ten tracks of audio, so I wouldn’t think we’re pushing any limits of our hardware. (if a dual 500 MHz G4 could do it….)
We did recently upgrade the RAM from 2 to 4 GB (Micron brand.) Apple hardware test disk says it’s good, but since this is the only thing that has changed recently (other than the project getting progressively more complex), is the RAM the first suspect? Any troubleshooting help would be greatly appreciated.
Here are the details:
24″ iMac 8,1
2.8 GHz Intel Core2Duo
6 MB L2 cache
ATI Radeon HD2600Pro with 256 MB VRAM (driving a second display)
4 GB 800 MHz DDR2 SDRAM
video is coming from a G-RAID via FW800
(captured to DV files from an AJA IO in our online room)
- May 1, 2009 at 7:54 pm
You are running iMacs with an external Hard Drive for your media and render files? If so make sure all media and renders are on that external. If the noise sounds like the shreeek of someone taking a hatchet to your speakers at full volume, I have had luck deleting my audio renders and re-rendering it.
- May 1, 2009 at 8:44 pm
Thanks for the idea. Yeah, all media and render files are kept on external FW800 drive. I’ve trashed the render files (there weren’t very many) and trashed my preferences, so we’ll see if that helps….
It’s definitely a full-volume shriek that it makes…a hatchet (or maybe a circular saw?) cutting through the audio cicuitry is about right!
- May 4, 2009 at 7:03 pm
Still crashing. This last time I was just playing a source clip in the viewer–then the freeze with screaming digital white noise in my eardrums. Any thoughts anyone? I’ll put back the old RAM and see if that helps.
- May 7, 2009 at 4:40 pm
I seem to be just talking to myself here, but if anyone’s curious, our problem appears to have been bad RAM. It’s been working like a champ since I put the old sticks back in….
Log in to reply.