FCPX undo / auto save bugs + RAM Hog - Possible Fix?

Hi there FCPX users,
I have a 8-core 2010 Mac Pro with 16GB Ram and the stock GPU running Lion 10.7.2
I have been using FCPX since day dot, and have been overall very pleased with its super fast work flow and realtime capabilities.
I have completed over 100 3-4min edits with average project size of 50GB, and a bunch of wedding edits with approx 150-200GB project sizes. The issues I had with 10.0.0 - 10.0.1 were mainly FCPX quitting unexpectedly.
And now on 10.0.2 I have expereinced the well known auto save / greyed out undo bug. I have gone through all the steps via apple care which included:
Trashing the Prefs, repair permissions, check drive space / correct format, new user account and clean install of lion / Final Cut X.
I am still experiencing this issue. So yesterday I purchased another 16GB Ram totaling now to 32GB Ram, and I monitor the RAM usage via "Free Memory".
I Noticed that if my RAM is running low, I "free Memory" without quitting FCPX and continue to work as normal, and so far I have not yet experienced the issue again.
Dont know if this is a temporary fix, but it has worked for an hour long edit (approx 6-7 hrs without restaeting FCPX).
Also, I have noticed FCPX will eat up 16-20GB RAM quite easliy.
Not sure if this problem is related to RAM...
My 2 cents.

You have to really be conscious when you start a new project and how and where you manage your footage.
No one has complained more than I have about FCPX's quirky behaviors and it can be frustrating. I have worked with FCPX since day one, even tried to get a refund but couldn't. After using it for a while now, it is very easy to get used to how fast some elements are in editing and reviewing a lot a footage. But several things you have to make sure of that will keep the rendering speed up and less crashing happening.
First make sure that you can see how much space you have on your drives by right clicking in the main window of you screen and make the necessary clicks form the drop down menu. Make sure any drives you have been doing projects with lately are hooked up and do a secure empty trash. Its cool to see how much space you regain. 2) make sure that FCPX, Motion and Compressor (if you have those are installed on your boot drive).
3) Create a FCPX Projects folder on an external (FW800) with at least 75% of its drive space available if you do not have secondary drive installed in your computer. (Its very important to note that any drive you use for any aspect of editing should never be more 75% full, especially your boot drive.) This is where FCPX will log all of its operating files for all of your projects.
4) Either copy all of the other FCPX files from your main hard drive and paste then into the new folder you created. Then delete all of those files, as well as any Motion files too! (Do the same as you did for FCPX in the previous step)
5) If you need to move all of your music files to another drive as well. If its iTunes, you will have to tell iTunes where to look for the new files and it will populate accordingly. This will free up a tremendous amount of space. Make sure to delete them form the main drive.
6) Remove any junk programs form the boot drive (main) or move them to another drive if possible.
7) Now do another secure empty trash and watch your drive space return.
8) Now open up FCPX and make sure you only create projects on your new drive by clicking on that drive in the project window. Any older projects you can simply pull them to the other drive and you will be prompted on how to duplicate that project and all its files to that drive. Delete the other ones.
9) Only capture footage to you external drives. Save it there until you need it.
10) Create all new projects on the secondary drive and pull any footage you are working with on that drive as well. By keeping it all off the Boot drive FCPX will run much smoother and faster, especially if you have at least 16g of Ram, which I recommend.
So to re-cap:
1. Keep your boot drive lean. Delete anything you can move to another drive. Do not set up events and or projects to it...never!!!
2 Use you secondary drive for your project files and the video you are working with in your events.
3. Store raw footage on a FW800 drive ready to move to your secondary drive.
4. Use secure empty trash after all editing sessions when you are certain of your trash contents.
Doing these things have greatly increased much more consistently faster render times and much fewer crashes.
iMac 27 - 3.5gh - 16GB Ram - Quad i7 - 250SSD/1TBesata - External FW800 Drives
Good Luck

Similar Messages

FURIOUS! Warning: Undo Bug and Auto-Save Bug

So I'm pretty ticked off right now. I generally liked FCPX and its changes contrary to many others' opinions, but I just came across a bug that ultimately was worse than I thought.
During my editing process, at some point I was unable to undo changes. It was greyed out in the toolbar, and Command+Z wasn't working. It was annoying, but I didn't think much of it or bother to restart FCPX because I was in the zone and didn't want to stop. Eventually, I decided to restart FCPX to see if I could fix the bug with a lull in my edits. It closed out as normal.
When I re-opened FCPX, I found out that my project was at an EARLIER state. From what I can guess, when the undo bug happened. So, during that period of time, NOTHING was being saved. Since you CANNOT auto-save (I know you can duplicate a project, but Im not interested in that, I just want to save a copy manually), there is no way I can recover my edits. I lost about an hour or so worth of edits. Since FCPX doesn't support "versions" yet either, there is no way I can retrieve it.
I do not know if this is a bug due to 10.7, nor do I really care. I sent a bug report because this needs to get fixed. I consider you do the same but AT THE VERY LEAST, be mindful of this bug. If you suddenly can't start undoing, either STOP IMMEDIATELY or duplicate your project (maybe that would work). I'd hate to have someone else go through this problem too.
Sorry if this message is written poorly, like I said, I'm pretty ****** that this key function (Apple's ONLY way to save) failed.

Thanks guys for the tips. Unfortunately though stuck, I don't know if the finder trick will work. Remember, I never really had the file LOST, the changes were simply not writing to the actual .fcp file. So if I copied it in Finder, I think it would just copy the .fcp file which is currently not getting saved to anyway. Maybe duplicating the project in FCPX would work, but again I think that just takes the .fcp file and duplicates it. If it's not writing to it, then its a moot point. Oh well.
As with anything that frustrates anyone, I've cooled off haha, and doing the re-edits actually seemed to turn out easier and better then second time (you know, as theu naturally are I suppose haha). Obviously all sorts of problems happen with technology, its just a shame that its a bug that revolves around the ONLY save feature haha.
HOWEVER. I think I have replicated the problem, and MIGHT know the source of it. Or at least one. If someone wants to try this and confirm this? I'm running OSX 10.7 and FCPX 10.0 (obviously), however I encourage someone with 10.6 to try it too.
I noticed the "undo bug" (and thus the auto-save bug) happens when I took one of the "fader handles" (I don't know the actual name, but its the little marker-like icon found at the start and end of audio tracks, which when dragged, let you easily make a fade in or out. If you take a fader-handle, an drag it ALL the way BEYOND the length of the clip, it should get stuck. Youll notice you cant easily make a change to it again, and you can't undo it. I think this is what causes the problem, as I think this happened twice to me.
If this is it, I hope I can find a way to flag this for Apple so it can get fixed! At the very least we can be concious of it.

Smart object / Auto save bug

MacPro 1.1, OSX 10.6.8, PSCS6 Beta
Came across the following, which I think is a bug.
I have two ducuments: D_test_00042.psb and D_test_00052.psb.
Each were build using a few layers and a group "Retouch", and then converted to Smart Object. So both files contain a (different!) Smart Object called "Retouch".
If I open both files, and doubleclick the first SO, then go to the other and do the same, all works more or less as expected:
However, if I open one file, and doubleclick the SO, then close the original file (to save on system recources), thén open the second document and doubleclick the SO in it, I get a warning "The disk copy 'Retouch.psb' was altered since you last opened or saved it. Cancel / Update":
Cancel obviously won't open the second SO, Update updates the SO that's already opened (which belongs to the other document)
(History palette in the top center, shows "Update from file")
Message was edited by: Rene-) for exact workflow and screenshots

Follow up: PSCS4 (11.0.2) behaves the same, so it is probably something I never noticed before (which is surprising, since I didn't alter my workflow) and has nothing to do with Auto Save…
I'll make it a feature request then: Fix this. Use unique names 'internally' for SO's.
I want to be able to open a SO from an older document for instance to be able to copy paste from one SO to another.

Cannot Undo after Save -- Bug?

I've noticed that in Garageband once I save my project, I can't undo anything that happened before the save. I don't like that, and after the flexibility of apps such as Pages it seems unnatural, but I figured that was just the way things were.
However, I was talking with some programmer friends of mine and they were shocked when I mentioned data I'd lost that way, and they advised me to 'file it as a bug'.
Is it a bug, a setting I can change, or was it made that way for a particular reason?
Thanks!
~Iggy
Message was edited by: Ignolopi
Message was edited by: Ignolopi

GB does its housekeeping upon save, for instance a completely deleted region is deleted from the project file. this is just how it was designed.

Keynote 6.5 Couldn't auto-save document

Hi all,
I just pasted and copied pages of tables to keynote, it couldn't auto-save document. How do fix it ??
OS X Yosemite 10.10.1 , Keynote 6.5(2110)

I have the same problem just now. I've been working on a keynote for days, been saving it regularly and as of 10 mins ago it refuses to save all of the sudden. What the...
I've tried to move the document to another folder and then save (doesn't allow)
I've tried to duplicate the document and then save (doesn't allow)
I've tried to rename and then save (doesn't allow)
What did work?
Create a new keynote file
copy paste slides to new file
save it

HT5824 I've been using numbers for iPad and I accidentally deleted a column. And the auto-save feature saved that and now I can't undo it. Does iCloud storage have backups of saved files from like 10 minutes ago? I have number

I've been using numbers for iPad and I accidentally deleted a column. And the auto-save feature saved that and now I can't undo it. Does iCloud storage have backups of saved files from like 10 minutes ago? I have numbers synced to iCloud.
I tried to undo it but the app crashed.
I am hoping there's like a previously saved version of my file in iCloud somewhere.

No, iOS does not do short term incremental back ups to iCloud such as you get with Time Capsule.It backs up when you do soo manually, or if set properly, when the device is plugged in and connected to WiFi. It will not have saved your changes as of 10 minutes prior.

IPhoto auto-save possible?

changed to Mac 3 months ago and the only thing that's still bugging me is the way iPhoto works!
ok, let's say I have a managed library where all the imported photos are saved into the iPhoto folder.
when I make changes to the photos, can it not auto-save AT THE SAME POSITION instead of saving the edited photo in a different folder???
If I make a change I want the original photo to be deleted and only keep the edited one.
Because, if it keeps the originals and then in a year's time I want to say move to a PC or if I just want to backup in an external drive how will I do this without manually sorting out the edited photos from the originals that should have been deleted???
PS: if you're nice enough to respond, please do not respond with links to "tutorials" as they don't answer this question, thank you.

If I make a change I want the original photo to be deleted and only keep the edited one.
Then don't use iPhoto. It's not a photo editor, though it can edit pics. It's a Photo Organiser - that is, it manages your digital assets and always preserves your original file in the way a film photographer would mind his negative. This is built-in to iPhoto, it cannot be turned off. If you don't want the feature then iPhoto is not the app for you.
Because, if it keeps the originals and then in a year's time I want to say move to a PC or if I just want to backup in an external drive how will I do this without manually sorting out the edited photos from the originals that should have been deleted???
To back up: simply copy the iPhoto Library from your Pictures folder. That gets everything: your Originals, your edited versions, albums etc.
If you want to migrate then do it the really simple way: select the pics in the iPhoto Window and go File -> Export and set the Kind: to Current if you want your edited versions (or Originals if you want those).
Bluntly there is never a need for you to access the iPhoto Library via the Finder or with any other app.
Regards
TD

Universal Auto Save possible?

so I live in a part of the world where power/light, though exists, is infrequent and often comes with a low current or a very high current. As a result I've lost many a file and was wondering if there is a universal auto save program out there of if there is maybe some way to configure automator to do that (a program I know nothing about FYI).
I do have a UPS (battery backup), and regulator but when the current comes high, it blows out the regulator and UPS so I'm still with semi frequent shut down.
Any help GREATLY appreciated.

Believe me I am ALWAYS saving but my need is not just for myself but for other staff who aren't as quick with apple+S. In there defense the power situation here (West Africa) is abysmal at best and really causes serious problems. Not only that but the sockets here are far less reliable than what I've experienced in US or Europe - when you think something is plugged in, it's not always getting power and even when it is drawing power the likelihood of it switching off is high. Thanks tho for your reply.

FCPX Auto-Save: Error Sound When Hitting Command "S"

Final Cut Pro X should have an option to turn off auto-save. I HATE it! My question, is there any way to turn off the error sound when you hit command S? It is training me not to save and causing major problems for me when I use other software.

There is no meaning for "Save" in FCP X, since it is a database-driven application.
However, if you tend to hit Cmd-S pretty often, you may avoid the error sound by associating the keyboard combination Cmd-S to some innocuous command.

CS6 Auto-Save: 1 step forward, 1 step back

I have done a little testing with the auto-save, and there is some progress with CS6 - especially in the area where earlier versions would stop playback or scrubbing to fire off an auto-save.
It looks like the auto-save does not stop playback or scrubbing on the timeline anymore. It will stop you from other operations such as moving an audio slider or other non-critical mouse clicks. I tested with 1 minute intervals, and it appears that it won't auto-save during playback or scrubbing in the background, and will wait until the next interval after playback has stopped until it saves. (Instead of taking the very next possible moment after playback has stopped to makeup for the save) This seems like it could create the possibility that if you are playing back or scrubbing during multiple interval moments, you could have a long period where there are no auto-saves - especially if you set the interval to a high number. Like I said, I only tested with a 1 minute interval, so maybe this functions differently if you save every 10 or 20 minutes. Maybe then it will do an auto-save right after playback has stopped if it has been awhile.
The step back is that if you hide PPro, (I'm on a Mac, btw) instead of just bouncing the dock icon during an auto-save like previous versions, it will actually bring PPro to the front and block out/cancel anything else you are doing on your machine. How annoying! I can't figure out the reason to have it function like this. If it is simply hidden behind other windows, it does not do this, instead only brings to the front the small auto-save progress bar - It only happens if you hide the appplication. For example, if you are moving back and forth between PPro and AE, you could be working away on a comp in AE and suddenly PPro jumps to the foreground to let you know it did an auto-save. Since I have 2 monitors, I like to hide apps that I'm not working in to hide pallettes and other windows so I can have my desktop back. Seems like the solution for now is to not hide PPro ever and to do a proper save more often to avoid the issue of potential long periods of no auto-saves. (And submit a bug report?)
Anyways, long post for a potential trivial thing, but for those who care about this, it is a change. Anyone else experiencing this?

Jim,
Exactly, and that is what the "1 step forward" is with CS6. It drove me crazy when Auto-Save would interrupt playback. I was suggesting that it would be a better option that if you are playing back during an auto-save interval, it should take the very next opportunity to fire off a save, like maybe after hitting stop when there is a moment of downtime. However - in my testing - it looks like it skips that interval completely and waits for the next one. So, if you have it set to save every 10 minutes, but are playing back your timeline during each of those 10 minute intervals, it will never auto-save even if there are large stretches of time in between when you are doing nothing. It seems like it could be more intellegent about when it saves, and do it quieter in the background.

Feature Request: Auto-save in Background

Here's a feature request I've submitted. If you agree, please submit your request to:
http://www.adobe.com/go/wish/
*******Enhancement / FMR*********
Brief title for your desired feature:
Background Auto Save
How would you like the feature to work?
Auto-save would work just as it does today, except it would work as a background process, as it already does in Photoshop (without the Autosave popup getting in the way of the edit).
Why is this feature important to you?
The current autosave feature is terrifice and expected in any application today, but the current autosave popup dialog is useless. It only has a "Cancel" button. What's the point? I can't imagine when I would ever want to cancel an auto-save. And let's say I *did* want to cancel. The dialog is only on screen for a second or so. That's not enough time for user interaction, but it is just enough time for my work to be interupted, and for me to potentially hit the enter key as I go to Render something at precisely the same time.

Hi cscouper2013,
Thanks for taking the time to point out that my BSODs might be a problem with my RAM! Yes, I'll test it with the program you mention.
cscooper2013 wrote:
While I'm thinking of it, too. Sometimes Premiere will do an auto save only moments after I've done a hard save. That also seems like something to address in the next auto save feature update. If I have my autosave increment set to 5 minutes, then it seems to me there's no need to do an autosave for another 5 minutes after my last manual save.
I fully agree! That's something I requested during the CS5 beta program. I requested that every time a user does a manual save, the Autosave reset its counter. So for example, if the delay is 10 minutes between auto saves, and the user does a manual save two minutes before the next scheduled autosave, the autosave counter resets to 10 more minutes. But with the better solution of the current project constantly being saved after each edit, as Jim suggested, this feature wouldn't even be needed anymore.
MonkeyEatsMonkey wrote:If Premiere could "borrow" that functionality, while still retaining a "save as" option for versioning, I feel like we'd have the best of both worlds. It would even make dynamic linking more seamless, since changes wouldn't require saving. Any thoughts from the community on this?
That would be a perfect solution IMO! And yes, retaining the 'Save As' option would be very important!
I also like the idea of automatic versioning/backups (could be renamed to 'versions' since with a constantly saved project file, automatic 'backups' would no longer be necessary.
To resume, based on what has been discussed in this thread, I believe these would be the ideal saving options in Premiere:
Autosaving of every edit in the background without slowing down editing performance (as suggested by Jim).
Ability to create a user defined number of automatic backup versions, by setting maximum number of versions and time intervals (as is currently the case with Premiere).
In other words, the current project file would constantly be updated as the user edits. The automatic backups/versions would be created at user defined intervals.
Users would retain the ability to create a copy of the current project at any moment through the 'Save As' and 'Save a Copy' commands that already exist in Premiere.
Pop-up Auto-save dialogue boxes and the 'Save' command would be a thing of the past!
IMO, this would truly give us the best of both words as MonkeyEastMonkey suggests: constant saving as per FCPX, with the comprehensive versioning options Premiere currently offers.
Anything missing?

Auto-save a) crashes AE and b) will not turn off via preferences

I seem to be in an endless loop of AE starting, auto-saving, and crashing.
I reported a bug earlier of AE crashing if auto-save begins during a Warp Track. I thought I could defeat this behavior by turning off auto-save in preferences, but, even with that (the save box is unchecked), auto save starts within a minute of opening a project, and freezes AE (staying at 0% Completed indefinitely).
I've deleted AE preferences, verified that auto-save is off, and the problem continues.
Any suggestions of how to defeat this would be very welcome. Thanks!

Caught in the act. After restarting, fixing permissions, reverting to a early (pre-tracking) version of the project, and verifying that auto-save is still turned off, AE tried to auto-save during a track (this time the stabilize phase) and froze.
One possible new detail - it only attempts to auto-save when the tracking footage window is in the foreground. Is it possible that AE auto-save settings do not affect the tracker when it is in the foreground? I worked several minutes without interruption in another comp before returning to see the track, and apparently triggering the auto-save somehow.
Thanks for any help.

Auto save and very large files

Hi All,
I produce very high dim artworks, 6m x 2.7m(+) image at 200ppi, sometimes when I load the files Photoshop cc2014 would randomly will crash. This never happened with my CS5 version. I have auto save checked, could this be the issue?
I am running a high end computer with 32gb ram, 8 ssd's with two dedicated to PS scratch disk....the images, so far, load eventually but the heart beat stop moment when you think a file is corrupt really scares me, especially when $$$$$ are involved.
Any ideas?

Thanks JJMack
I will try it. It is possible it's not the auto-save feature, cs5 was rock solid and gave me confidence as it never crashed even with files over 5gb. The crash report states the faulting model is unknown for the last crash but I have seen ntdll.dll as the faulting module in previous crashes.

Auto save is making Premiere crash

Working off of CS6 on a Mac, with a project I've been working with on for nearly a year now off an external drive. Recently, as soon as an autosave (set for intervals of 20 minutes) begins, the project just stalls, no progress on the autosave bar, and the project will eventually crash, sometimes with the warning that there is low memory. The memory problem makes no sense, there should be plenty of RAM as well as storage on both the desktop as well as the external drive. Nothing has changed in the folder structure of my project, including the autosave folder which is in the same location as my project file. Seeing as how that folder was how it was set up so long ago, and it has only recently begun proving a problem for my project, I'm at a loss for what could possibly be causing this problem. If anyone could offer some ideas, it would be truly appreciated.

Might not be of assistance, but I know occasionally projects start taking up so much space they become an issue. So you might check your cache locations (displayed in the various preference dialogs) and also your auto-saves. If you've got more than the last few, I'd suggest going in and deleting a bunch of them. Carefully, might say take 2 of each group of 3 at first.
Also ... several folks have found that routinely clearing all cache files helps keep drives usable ... as they build up clutter, and they will ... you start getting to a point where there's slowdowns occurring simply because of stuff-bloat on the drives. Always keeping any drive in your video "chain" below 50% "occupancy" is wise.
Just ... something that might help.
Neil

Auto-save in Logic 8

Hey Guys
I've been trying to find an option for auto-save in Logic (and to set how often it does this)... but I can't find anything...
Does it just do auto-save in the background? Or is there no auto-save feature?
It's easy to forget to keep saving in a long session and would be nice to know Logic does it for you!!
Cheers
Mike

I'm sure that Logic will never need auto save.
the reason is: Logic have a .crash save function...
it works great... (if you don't use 3rd party plugs with false Audio Units validation Pass.
I'm a Logic user from the Notator version...
Auto save is dangerous...
the only usefull thing should a Fix with save before Crashing happen
Auto save is not "intelligent solution"
*Logic 9 should be comes with an intelligent way to save function that works ONLY WHEN AND IF NEEDED*
I'm sure that Logic 8.1 will solve the .crash issue with 3rf party plugs that are intentionally developed with only AU version bugs.
this is another of the "milion" fermusic ideas about sh*t auto save dangerous and *really obsolete* function
No Auto save... *vote for an intelligent way to automatic save function*
(vote for fermusic )
Thanks... expacially focused to Bee Jay and Erik

FCPX undo / auto save bugs + RAM Hog - Possible Fix?

Similar Messages

Maybe you are looking for