FCP 10.1 Horrible Performance - HELP!

One other thing. Option E now longer shortcuts to export a master file. It still works thru the File Menu, but just get the error sound otherwise.

I'll be updating Apple on the issues today after I try to get caught up on the work I didn't get done this weekend.

Regarding performance issues with an existing user account, read this fix by Oliver Peters:

www.fcp.co/forum/4-final-cut-pro-x-fcpx/...ys-locked-open#38243

- Ronny

I had a crash today, and lost one of my projects- thankfully I still had the 10.0.9 version in the "old" folder, so I copied it out and put it into the old "Final Cut Projects" folder and reimported it into 10.1. Came in fine, and more noticeably, the sequence suffered from none of the UI slowdowns I've been experiencing.

Then I exported an XML of that Project and imported it into the new Library. Once I did this; same project, UI problems back. Very weird.

I think there's something very specific about the structure of the Event or Projects (or both) for this job that has resulted in my problems. I'll have to try importing a couple other simple jobs I'll be having to revisit this month.

I don't know if anyone else is having this problem but I'm still experiencing extreme project bloat. This problem was sporadic in 10.08, and frequent in 10.0.9 and still exists in 10.1. Specifically working in multi cam. I'm working on a 2 hour show with 2 video angles and audio angle. Starting out the fcpx is quick and snappy but when I get into about 20-30 minutes a simple angle cut takes about 30 seconds. Playback gets choppy and if I keep going I get the spinning beach ball which can last over 60 seconds. I've noticed that the project file size balloons up to about 200mb and will grow substantially every time I switch angels. At this point it's basically useless and time consuming to work with. The library and event files seem to stay fairly small and I can still work in other areas of the library and events. It's just the projects.

So in 10.1, I created a work around. Once the project starts getting bogged down which is about a 1/4 of the way through the show, I export the project xml then re-import it back into the library. I still have the original 200mb project to reference but now the new project is under 10mb and very snappy (fast) to work with after cutting the next 90 minutes, the new project doesn't seem to bloat as large or as fast as the original project.

I'm hoping Apple can fix this problem in 10.1.1.

Man that sounds horrible. I have done lengthy multicam projects but I haven't had any of those issues in any version.

How many cuts or angle changes are you having? (Look in timeline index)

What is your multicam clip like. How many angles? Are you adding effects once your multicam clip is in the timeline? Are you adding audio keyframes? How about transitions? Any compound clips anywhere? What else is on your timeline?

What are the specs of your machine? What codec are the clips? And the audio?

All of my problems above are related to multi cam projects. I think something is going on in the conversion with certain projects that 10.1 doesn't like.

Disproportionate Pictures wrote: One other thing. Option E now longer shortcuts to export a master file. It still works thru the File Menu, but just get the error sound otherwise.

I'll be updating Apple on the issues today after I try to get caught up on the work I didn't get done this weekend.

Make sure the Master File is set as default in the preferences under destinations, and also check your keyboard shortcuts in the command editor.

Thanks- Master file wasn't set as default. That must have happened when I deleted my preferences. Now if I can just figure out why my Blackmagic I/O video isn't working. Audio is going thru, and FCP7 outputs fine, so its definiltey something related to FCPX

What Blackmagic do you have, and which driver version? Make sure you have "Window-->A/V Output" checked, it's easy to overlook. Also make sure your output settings in the Blackmagic system preferences match what you're trying to output. When you change this, you will have to reboot FCPX (in FCP7 you didn't have to reboot to change output settings).

Holy crap, two for two. Thank you. It was indeed the Window A/V output, and again was probably related to me trashing my plist or preferences when I was trying to figure out why this project was running so slowly. I'd never had to check the A/V output before (since it's probably been turned on by default since I installed the Blackmagic Desktop Video software- I did not even know it was in that menu.

Sucky that we still have to exit FCPX to change resolution or frame-rate- I wonder why this hasn't been solved yet.

My issue isn't pervasive- if I create a new library or project I have no responsiveness issues, but mouse-driven UI is patently awful in this 42 video, 3-camera multi-cam job. If you read my posts above you'll see how I've been trying to problem solve this without having to rebuild whole videos.