TOPIC:

Well so far today, I got the lovely 'problems saving project, please shut down fcpx to save changes' message. And now a project I am exporting has stalled at 9% for the last half hour while importing/transcoding material for a different project. Nothing I don't do several times a week, every week, so it's really good to see that along with the smorgasbord of new features and updates - the bugs have been worked out too.

Yep, I STILL feel like an unpaid Beta tester!

When you get that message it often indicates that your system cannot handle the tasks you are wanting it to handle and FCP X has not enough memory available anymore to store or backup your work. So it would be good to have some more information on your system setup and the projects you are dealing with.

FYI: beta testers never get paid

- Ronny

Trust me Ronny, while I appreciate the reply - my system is definitely not wanting and there is no shortage of memory. I actually haven't had that error message in quite a while, and I'm pretty much editing 7 days a week (unless I'm filming!). So though that in itself wasn't too much of an irritant (the minute or so to restart), there is no excuse for the export to stall. Only FCPX, Safari and Mail are open - yet I could quite happily have iDVD burning off discs and XDCAM Transfer importing footage from SXS cards - ALL at the same time as working on FCPX, and nothing will skip a beat, so this is just another random episode which crops up every now and again to remind me that FCPX is still very far away from being the finished article.

Am I seriously the only one to have any of these errors?

ronny wrote:

When you get that message it often indicates that your system cannot handle the tasks you are wanting it to handle and FCP X has not enough memory available anymore to store or backup your work. So it would be good to have some more information on your system setup and the projects you are dealing with.

FYI: beta testers never get paid

- Ronny

Though I totally agree beta testers never get paid!! Hahaha!

No system is immune from occasional hiccups. If it's pervasive, that's different.

I cannot find much feedback about this particular issue but I know I have seen this before. All of a sudden CMD+Z stopped working and this was an indication that FCP X should be quit so it could store your changes. But that was many versions ago. Haven't seen this happening since. If you have this on a regular basis please submit a report to Apple. And no, you won't be getting paid for it

- Ronny

Arsecati wrote:

my system is definitely not wanting and there is no shortage of memory

Sounds to me like something is up with your system. I would try to repair permissions, run Disk Warrior if you have it.

ronny wrote:

I cannot find much feedback about this particular issue but I know I have seen this before. All of a sudden CMD+Z stopped working and this was an indication that FCP X should be quit so it could store your changes. But that was many versions ago. Haven't seen this happening since. If you have this on a regular basis please submit a report to Apple. And no, you won't be getting paid for it

- Ronny

Oh I was a victim of that too - just remembering that now has given me goosebumps: I lost hours and hours of work that day, but yes, that was quite a while ago now (maybe over a year now?), and was a specific issue acknowledged and rectified by Apple, so this is different. I never got a message or warning that time: as you said, it was only when realising CMD-Z no longer worked that I realised there was a problem. However, at the time, I just carried on manually fixing my 'undo's', having put it down to another glitch, and just simply not having the time to Google it, so it was only after I had shut down FCPX for some reason and re-opened later to a much older project, did I realise the problem was far greater. I'm shivering now: that was not a good time!

This is different though, and granted, doesn't come up too often (and as I said, at least gives a warning), so being so used to the myriad of bugs since FCPX came out, I just restart and carry on.

However, excellent idea tpayton, I actually knew there was something I hadn't done in ages!! I DO have Disk Warrior, but a good rub through with Onyx has usually cleared things up for me, but thank you so much for actually reminding me: there IS something else I should have done to keep everything up to scratch! How the hell did I forget about repairing permissions?? Haha! Going to give it a good lash now - should have been first thing to do once 10.1.2 was installed, give it a good clean out for the new update!

Right, hopefully that will put everything back in to shape again, and stop my whinging for another few weeks!

Recently we had a post here about a different issue that was solved by repairing permissions after updating the app. Although I agree that modern installers don't require doing this anymore I still think it is wise to manually repair permissions after every software install or update. So yes, that's a great idea.

- Ronny

I think it is only natural to blame the App we are using for problems, but computers are obvioulsy very complicated systems and there are many fail points. Case in point, I was humbled last week as I have been reporting slowdowns in the FCPX UI for 3 years. The last week I discovered the RAID I have been using on my main system has a horrible problem will small random writes and therefore has been a significant culprit of slowing down my FCPX UI.

Here is that post if you missed it:

www.fcp.co/forum/4-final-cut-pro-x-fcpx/...ith-different-drives

Count me among the happy campers. 10.1.2 seems faster and has finally resolved the host of bugs and dropped features issues I've been plagued with for a month or more. Details of those issues in this thread www.fcp.co/forum/4-final-cut-pro-x-fcpx/...enly-appearing#48923

Editing with FCPX is fun again without all the oddball workarounds.

I'm building a show in multi cam and when I receive final stereo and surround mixes from the sound department, I create a synchronized clip with the audio stems. I then drop the synced clip into my multi cam angle editor as an additional angle. On my main project timeline I just choose the new audio angle and voila my edit has replaced re-mixed audio in stereo and surround. This has been working great UNTIL THIS UPDATE. Previous multi cam builds still retain this pass-through sound setup with appropriate stereo and surround roles etc. But any new synchronized audio clips I build and drop into multi cam, now on my main project timeline don't playback properly. All my surround meters play back evenly as if its just referencing a mono audio track. Does any one have any suggestions?