- Posts: 57
- Thank you received: 2
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
can't Undo after shutting down FCPx
- randychesbro
-
Topic Author
- Offline
- Senior Member
-
Less
More
10 Aug 2014 21:46 #51152
by randychesbro
can't Undo after shutting down FCPx was created by randychesbro
Maybe I don't know enough here but is there a way to do an undo after coming back from shutting down the computer. I would think theres away to keep the undo cache so you can continue editing when you come back. any ideas?
thanks, randyc
thanks, randyc
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
10 Aug 2014 23:17 #51155
by Tom Wolsky
Replied by Tom Wolsky on topic can't Undo after shutting down FCPx
The undo cache list is dumped when the application is closed.
Please Log in to join the conversation.
11 Aug 2014 02:18 #51158
by BenB
Replied by BenB on topic can't Undo after shutting down FCPx
Normal behavior for most apps. Very few retain any undo data once you quit them.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
Less
More
- Posts: 4455
- Thank you received: 962
11 Aug 2014 05:40 #51162
by ronny courtens
Replied by ronny courtens on topic can't Undo after shutting down FCPx
What Tom and Ben said, plus I will add: it's absolutely a good thing that the Undo cache gets flushed whenever you shut down the app. The Undo cache is stored in your RAM, so after working for many hours your RAM will get filled with Undo actions and - depending on the amount of RAM you have - your system may slow down. I have asked Apple numerous times to
1. Have an option to put a limit on the total amount of RAM FCP X can use (an option we do have in Motion)
2. Have an option to put a limit on the amount of Undo actions you can store
3. Have an option to flush the Undo cache inside the app
This would especially be helpful for people who work on systems with less than 16 GB RAM.
You don't really need to store that many Undo actions anyway.
- You can make regular Snapshots of your edit. Snapshots allow you to instantly get your edit back to the state in which it was when you made the Snapshot. Making regular Snapshots has become a standard procedure in our workflow and I wish we could manually flush the Undo cache whenever we have made a Snapshot.
- If you have shut down your app or your computer and you would like to go back to a previous state of your edit but you have made no Snapshots, and of course you cannot use Undo anymore, you can always try to restore your edit from the latest Backup. This will bring your edit back to the point where your last automatic Backup has been made. Backups usually get created every 15 minutes.
- Ronny
1. Have an option to put a limit on the total amount of RAM FCP X can use (an option we do have in Motion)
2. Have an option to put a limit on the amount of Undo actions you can store
3. Have an option to flush the Undo cache inside the app
This would especially be helpful for people who work on systems with less than 16 GB RAM.
You don't really need to store that many Undo actions anyway.
- You can make regular Snapshots of your edit. Snapshots allow you to instantly get your edit back to the state in which it was when you made the Snapshot. Making regular Snapshots has become a standard procedure in our workflow and I wish we could manually flush the Undo cache whenever we have made a Snapshot.
- If you have shut down your app or your computer and you would like to go back to a previous state of your edit but you have made no Snapshots, and of course you cannot use Undo anymore, you can always try to restore your edit from the latest Backup. This will bring your edit back to the point where your last automatic Backup has been made. Backups usually get created every 15 minutes.
- Ronny
Please Log in to join the conversation.

