Auto-save didn't!!

After nearly 4 hours of editing in PE7, I got the Windows XP error message telling me that the program had encountered a problem and needed to shut down. Just before that, I had clicked on the button to make a DVD. My first reaction was that I wouldn't have lost much because auto-save was enabled, with saves every 20 minutes. However, virtually no edits had been saved. Looking at the PREL files in the autosave folder, I saw that there had been three saves from three hours previous, before I had done much work. For some reason PE7 had stopped autosaving. In preferences, auto-save is still enabled. I have both versions 3 and 7 installed on my PC, and this project was originally started in 3, so many files are saved in the version 3 folders including the PREL files, if that matters.
Any ideas what went wrong? I know that auto-save used to work reliably. Searching the forum and knowledgebase turns up nothing about this problem.
(my computer is a PC with an Intel 6700 Duo Core Pentium CPU and 2G of RAM running Windows XP Pro SP3)
Additional: I now see in the help file something I didn't notice before. It states "Note: Each time you open a project, you must save it at least once before the Auto Save option takes effect." I don't recall having manually saved it even once, yet it did auto-save three times, as mentioned above.

Thanks guys. I may set a timer to remind me to do my own saves next time. The autosave periods were the default 20 minutes, and I still don't understand why there were 3 saves early on, during a time when I was away from the computer. Only after I resumed working did that function stop. One more thing: the help file says that when restarting after a crash I should have seen a message asking if I wanted to resume from the last saved configuration, or something like that. There was no such message. Also, I see that the autosave PREL files are contained in the Autosave folder, but there is also a PREL, apparently the newest one, in the file path one level higher where all of the data files are contained.
This is a little bit away from the original question, but can I now delete version 3 since I'm (generally) satisfied with V7. I don't want to jeopardize the current project, which still has some more editing to be done, especially after losing the aforementioned edits.
One more thing: would increasing RAM from the current 2 gigs help prevent a crash like the one the occurred.

Similar Messages

Why did auto-save didn't save my entire project?

Hello,
I recently had some problems with auto-save. I was working on a project when my computer
stoped working and I had to force shutting down. However, my Premiere CC is set to auto-save
every 15 minutes. When I went to see the auto-save files I didn't find my entire work. I had several
sequences previsously the one I was left with. What had happen?
thank you,
Joao.

Some versions of Premiere Pro won't start autosave until you do a manual save. What version are you using?
Did you try searching your drives for project files in the event that it went to an unexpected place?

While composing email, keep getting "Unable to save as a draft" every 30 seconds. I've disable auto save and it didn't help.How can I stop this message?

While composing email, keep getting "Unable to save as a draft" every 30 seconds. I've disable auto save and it didn't help.How can I stop this message?

Mike,
Thank you for taking the time to look at my app. This is my last major stumbling block that I have to resolve for this and other forms in the app.
Actually, I did use the Form Wizard for Auto DML to originally create the form. It was great. It created most of the Buttons, Items and Validations automatically (basically most of the page). I just needed to create some Processes and Computations. Two of which were the Processes to update the 'create_dt' and 'created_by' fields and 'update_dt' and 'updated_by' fields. The Create process updates the fields just fine.
However, my problem seems to be that the Hidden 'create_dt' and 'created_by' fields aren't picking up the values from a record that is being editted. Then when I attempt to save the record those fields are NULL, causing the DB NOT NULL constraint to throw an exception for those fields. In the back of my mind I seem to remember seeing some post stating something to the effect that the information in fields with a Source Type of Database Column is just displayed and does not affect Session State items.
Even with that, I am still wondering just why the 'created_by' Page Item shows the value that is in the DB record being updated, but the 'create_dt" does not (as can be seen in my first posting). It is the 'create_dt' Page Item (:P205_CREATE_DT) not having the DB records 'create_dt' info in it that appears to be the problem.
Thanks,
Tom

The auto save function will not turn off.

While opening some files, I get- "This document was not closed properly, and some of your changes weren't saved. Do you want to recover these changes or discard them?
Niel helped me to figure out that this was happening because the save option and recent items option was checked in the appleworks preferences. I unchecked the "auto save" and "recent Items" options in appleworks preferences>General>files settings window and It seamed to work for awhile but now the problem is back.
I don't know why, but the "Auto Save" folder inside the appleworks User Data folder, which is inside the Documents folder is still saving data.
Can someone please help?
Marco

Greetings Peggy,
Nice write up link! I deleted "appleworks 6 preferences" in home file>library>Preferences>Appleworks folder (and the com.apple.appleworks.plist). Then turned appleworks back on and went to preferences>general settings and unchecked the "auto save" and "recent Items" options in appleworks preferences. I noticed the "make default" option button didn't light up. Do you think that is a problem?
The "document was not closed properly" problem happens about every two days or so. I haven't been able to duplicate what ever I'm doing. I'll wait and see, and let you know.
Thank you very much.
Marco

Pages has no auto save or document recovery? seriously?what century is this?

pages has no auto save or document recovery? seriously?

Are you reading carefully ?
LIon (OSX 10.7) embed an Autosave and a Versions feature at system level.
iWork components are using them.
The question and the given answer were dedicated to apps running under older systems.
alphaflight wrote:
Why should any user be expected to check for this? Most every Apple - heck most every modern product does it automatically.
It's perfectly odd to assume that an application deliver this or that feature.
It's perfectly wrong to write that "most every Apple - heck most every modern product does it automatically".
TextEdit did that but iLife apps didn't and I'm not sure that Apple's Pro apps were doing that before Lion.
More, some users are ranting in several threads against the Autosave and Versions features introduced by Lion.
Yvan KOENIG (VALLAURIS, France) vendredi 21 octobre 2011 09:54:04
iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0
My iDisk is : <http://public.me.com/koenigyvan>
Please : Search for questions similar to your own before submitting them to the community

Premiere CC - no auto save files since yesterday

Hi
I have been working all day in Premiere CC - then crash. That happens, but when I realize that there is no auto-save file from today I get quite frustrated to put it mildly (yes I know I should have saved manually). Does anyone have a clue what can cause such a fatal error? I have searched the system for newer auto-save files with no luck. This is going to be a terrible night!
Here is a screenshot of my auto-save folder:
I am working on a Retina Mac - OS X Version 10.9.4 2,7 Ghz 16GB ram. Premiere CC 2014.0.1

I just had the same problem and lost a project due to this. I was working on something for the past two hours and there have been zero auto saves since the other day. Sucks, it's setup to do this every 15 mins and it didn't even do it once during this most recent session.

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.

Auto Save folder not being created with new project

Just recently I've noticed that when I start a new project there is no auto save folder being created. I have all preferences the same (auto save every 10 min with a max of 50 and save next to project files). I have no idea why this started or what I can do to fix it.

So it seems to be working now. I went back through other projects that have been open for some time and the most recent auto save file I could find for any of them was from Oct. 8th. So auto save hasn't been working at all. What I did was go into preferences and change the interval a little and the frequency from where I had had it since intial set up. That seemed to have told it to turn it back on for some reason. It's really weird. I guess I'll just keep an eye on it, but people may want to check there folders just in case the same issue is happening. I didn't realize it until today and it's been happening for a couple of weeks apparently.

Auto-Save and Auto-Recovery

I hope the is a differnence between auto-save (as listed in you document properties) and Auto-Recovery (as set in Prefs). I would like some "protection" but I don't want flash saving over my file unless I tell it to save. I got burn last night while "experimenting" and and did a "revert" only to find that flash had saved over my file, what a pain. I went to find the "recovery" file only to not find one anywhere. My search on the net are conflicted with wheather or not these 2 features are the same. In my case both items where checked and both set to 10min (the default). soooo....
Please tell me that Auto-Recovery is different, is that it doesn't save over my file, ie it keeps a real back-up someplace, AND where i can find this "recovery" file. ?
This feature seems strange, why not do a std auto back-up to a user selected number of versions in a user selected location ?
Thanks
Joel

Thanks. After poking around for a while I kinda figured this out. I was just glad to find out I could get some kind of "back-up" function from Auto Recovery, because "Auto Save" is a nightmare. I can't understand where anyone would want to use this feature at all. Anything that saves over what your working on before your ask for the file to be saved is looking for trouble. I found it out the hard way. I had "auto Save" on and after messing around trying a few different things, none of which worked or I liked, I thought I would simply close and re-open the original file only to find "auto save" had saved over my original file. I can't see any place where this feature would be anything but a pitb. If they want a auto save feature it should be saving versions of the original (up to a user specified number of instances) in the seperate folder. Never under any curcumstances should the original file be saved over unless the users presses SAVE. Auto recovery would be more useful if it didn't erase everytime you restarted the app. Flash needs to look at the back-up and versioning systems that AE and PPro use.
It's one of those things that bother you about the whole "suite" concept. Adobe owns all these apps and while some of them do play well together to an extent, for the most part it is still a collection of indiviuals. While there have been some changes to get the "look" of the apps to be close, the actual functioning of the UI in the differnt apps isn't where it needs to be. There needs to be a Suite "czar" that makes all the apps do std UI things the same using the same keys etc. for example AE, PPro, Flash, Photoshop, fireworks, all use different keys to zoom in/out or of your image/stage/comp/viewer/monitor window ie main workspace or to enable the mouse "wheel" for zooming. PPro still refuses to use the spacebar to toggle the hand tool like every other "suite app". anyway. a std system for back-up and versioning is need across the suite.
thanks
Joel

Pages V5 COULDN'T AUTO-SAVE DOCUMENT error message

Why am I getting this error message when I attempt to save a document, duplicate a document, move a document--"Couldn't Auto-Save Document" I cannot save the document. I originally opened this document from the server computer to my laptop, made changes on the laptop at remote office and now I cannot save it, even to a new location on the laptop.

Hi.
I was just now suddenly afflicted by this problem.
Have new macbook pro retina - iOS X 10.9.2.
Everything is up to date.
Even Pages is up to date. checked it (of course), as soon as I started getting the error message every time I tried to save. Even tried saving or 'exporting' to Word, PDF...still same message.
Now...I recall that any time an app is 'acting up' (i.e. not responding the way it should)...it usually means that it either needs updating, or it has some sort of 'bug' to it.
If it needs updating...then simply update it. I checked that option...and got message that Pages is indeed up to date.
So...opted to simply 'force quit' pages (as well as quit many other still-open apps that I wasn't using at the moment...to try to cut down on excess memory being used...thinking that may be part of the problem.
Also...thought that maybe my hard disk was getting rather full...so opted also to move all my music, movies & pictures to an external hard disk to free up internal storage space (by eventually deleting all after first backing up to external hard disk)...and then of course finally freeing up all space by emptying the trash.
Then...after force quitting pages (and all other non-used apps at the time)...and still before completing the transfer of all those heavy files to an external hard disk...then I re-opened pages to test it...and 'WHOALA!"...it worked just fine!!!
So...it seems that this was the solution...at least for me at this moment...to simply force quit the renegade app, and then re-start it.
If that didn't work, I was going to simply shut down the computer...and do a complete re-start. That is another option that often times gives a new look to life for apps which are acting up.
OK...just thought to put in my two cents-worth here.
Hope this helps someone else.
Regards,
Balqees Mohammed.

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.

Auto-Save or Recovery?

In my excitement, I started a few sheets, then realized I should save them. Numbers quit unexpectedly when I was saving the first one. I reopened Numbers and there didn't seem to be any "recovered files" like MSOffice had - no trace of the documents.
1. Is there a place to "find" the sheets I had open when Numbers quit?
2. Does Numbers have auto-save? Or does it go by a different name?
Message was edited by: afs11

Are you reading carefully ?
LIon (OSX 10.7) embed an Autosave and a Versions feature at system level.
iWork components are using them.
The question and the given answer were dedicated to apps running under older systems.
alphaflight wrote:
Why should any user be expected to check for this? Most every Apple - heck most every modern product does it automatically.
It's perfectly odd to assume that an application deliver this or that feature.
It's perfectly wrong to write that "most every Apple - heck most every modern product does it automatically".
TextEdit did that but iLife apps didn't and I'm not sure that Apple's Pro apps were doing that before Lion.
More, some users are ranting in several threads against the Autosave and Versions features introduced by Lion.
Yvan KOENIG (VALLAURIS, France) vendredi 21 octobre 2011 09:54:04
iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0
My iDisk is : <http://public.me.com/koenigyvan>
Please : Search for questions similar to your own before submitting them to the community

Auto Save to Spread Sheet file every N samples

I am in the need for a way to automatically save data to a file for every N-samples that are acquired. I've written the attatched reentrant subVI, but there are some problems. Whenever I have it in my program loop it hogs the process (stalling data acquisition) and just writes the initial values a bunch of times (the file quickly goes into the 10's of megs). I don't know where I'm going wrong in my algorithm.
Here is the algorithm I'm trying to realize with this subvi.
Inputs:
1. 1 x M array
2. number of samples to record at a time (N)
3. path to folder to automatically save files
Algorithm:
Initial run:
1. Create file name based on current date/time and folder path input.
2. Initialize an array that is N x M (so the number of rows is the number of samples to record, by the number of columns coming from the input).
3. Place the first row of input data into the first column of the array.
Subsequent runs:
1. Place the input data into the next position of the N x M array
2. If and only if current_input_count % N == (N - 1) then save the data to the autosave file. (note: %=modulus operator)
My typical sample rate is around 2-5 samples per second. I need this because some of our tests are really long (like hours long), and if the DAQ computer fails to save the final data set then we pretty much lost the entire test.
Sorry my G code is so sloppy. Thank you for any input. I'm targetting LabVIEW 8.
-Nickerbocker
Attachments:
Auto Save N Points.vi ‏22 KB

For "automatically saving the data to a file for every N-samples that are acquired", you might have to use LabVIEW measurement file for storing your samples. Also, I have slightly modified your code. Double click on the LabVIEW Measurement file and then check different options available to store your samples. Hope this helps.
PS: Assuming that this is the only probelm you have, I didn't go through your algorithm.
Attachments:
Auto Save N Points.zip ‏51 KB

Will applications need to enable Lion's Auto Save feature?

After accidentally stepping on the power strip today and losing about a half hour of work (I know I know, save, save, save) I am chomping at the bit to get Lion with Auto Save. As a professional writer, if that was the only new feature it would be worth the upgrade for me. But at $30? Biggest no brainer ever. That is a truly revolutionary feature for me.
Does anybody know if applications will need to enable or program in the Auto Save functionality or if it will work with existing applications out of the box?

Apple's system wide, "you don't have to do anything but do your work" Auto Save is to Word's auto save like Ragu is to my grandpa's homemade gravy.
No, Apple didn't invent auto save (neither did Microsoft, BTW) just like they didn't invent a lot of other things they do. However, just like Time Machine did for incremental backups, Auto Save and Versions will take this concept to new levels of elegance and usability.
The fact that it's system wide and works seamlessly with Versions so that I can scroll back and easily grab previous versions of my document is what makes this revolutionary.
Linc: I don't doubt you at all (I'm sure you're right), I just hope you're wrong. Either way, it is a feature well worth even the previous $130 upgrade price, let alone the measly $30 price tag of Lion.

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

Auto-save didn't!!

Similar Messages

Maybe you are looking for