For weeks I've been trying to get FCP to export via firewire on my iMac DV SE. I finally figured out my problem. It was an extention confict. I went to the extentions manager control panel and rebooted with just the "9.0.4. base" extentions and to my
surprise Final Cut Pro finally exports via firewire. Actually, I feel kind of stupid that I didn't try this earlier, but ...........I still don't know what was conflicting with FCP but at this point I
don't care. I made a custom extention set for FCP so whenever I want to run it I just reboot with the custom set. One more thing: Using the base extentions I notice that the video in FCP plays back more smoothly and I didn't get one "general error" message.

[bizzare]

Could of it been a RAM problem as well?

Originally posted by bizzare:
Could of it been a RAM problem as well?

I doubt it. I have 256 meg. I'm pretty sure FCP saw an extention it didn't like. Of course I'm not an expert. It runs like a dream now.


cabana

[brock76]

I found that 256M is pushing it on my machine. At www.2-pop.com you'll find that you should set FCP to 128-150megs to avoid dropping frames. OUCH!! This forced me to go out and purchase another 128 to give me 256 altogether. I still find that Im running out at times. Oh well. Time to go buy some more.

brock

[Feathers]

Glad things worked out Cabana, it's probably stating the obvious at this stage but frequently people have problems with audio-visual software and they don't pursue the route they would with say (ugh)MSOffice (apart from deleting it!). I actually get a bit incensed by people having problems and dissing the software when it's actually a poorly maintained system folder that's to blame. Moral: Conflict Catcher