PS autosaving?

Is there an autosave feature that will save my work every so often while I'm editing it? Occasionally I'll get an error & PS will have to close & I lose unsaved work. I'm not sure why, but it happens very rarely. I think when I open a very large document is when it usually happens. & I am not in the habit of doing routine saves while I'm working on stuff, in case PS locks up.
Also, can moving a document from PS to AI lower the quality or mess it up in any way? When I'm done on something in PS I open it in AI to do some final things to it that are easier than doing in PS.
Thanks in advance for any help!

If you are convinced such a feature would truly add benefit you could lend your support to one of the Feature Requests (but don’t expect quick results), for example
                                  Auto-Save Option pleaseee                    

Similar Messages

  • Needs Ability to Configure AutoSave To Different Drive than Scratch

    If you edit a large document with limited memory, and are exercising the Photoshop scratch file, a coincidental auto-save can really slow things down because the drive then begins to thrash.
    It would be great if the AutoSave could be configured to go to a separate drive than that selected for the Scratch file.
    I mentioned this on a recent Connect session, and I'm putting it here as well.  I believe it's something Adobe needs to consider by CS6 release time.
    On a system with a sufficient number of separate drives at the point where scratch file activity picks up this could make a HUGE difference - between Photoshop usability and UNUSABILITY.
    Possible workaround:
    Because Adobe has had the good foresight to use a subfolder, it's possible that the auto-save folder could be redirected to another drive through a file system link.  I'll be checking into whether this helps the throughput, as I'm not sure how much the link itself being on the same drive as the scratch files could be a bottleneck.
    -Noel

    I have an SSD dedicated for use as a scratch drive. So far I haven't noticed a performance hit with background save active, but I've yet to get into really intensive processing with large images.
    Since there are so many different drive and drive bus limitations, it's hard to say that Photoshop would be less bogged down using different drives for scratch and auto save. You may find a dedicated  SSD is a real boon to performance as I have.

  • HT4753 Is there already a rant thread to restore save as button and disable autosave?

    I found some threads with users having problems with new autosave and duplicate feature, and none of them contained an answer, and I was asking myself if there is an "Apple give us the save as button" back thread somewhere already.
    First of all this autosave behaviour. I really don't want pages or numbers to save every nonsense I may write in a file, sometimes by simply mistyping cmd-v in a wrong window, without me telling it to do so. How dumb is that?
    Second, why is the save as button gone? And no, duplicate is not the same, because duplicate doesn't start in the same folder. If I write an invoice to the customer, I take the invoice from the last month, click save as, select new number and change some dates and sums. This means, I did before 10.7. Now I have to find this very invoice on disk, which is not everytime easy to click through, click c&p, create a new invoice, and than i can start working on it. Annoying. If I click duplicate in an open document, it starts with the default folder, which is wrong in 99.99% of the cases.
    Alas, the autolocking function on freshly created copies. This is just dumb. Really.
    So, what the deal with removing such a simple button as save as?
    I was being using iWork for business since 2007, and I have had hard time to convince everyone in the office to be on mac, and just as I achieved that, ... Well, now the people want to move to MsOffice again, isn't it silly? Thank you Apple.
    P.S. And yes I tried to live with it for 9 month, but I can't get used to it.
    P.P.S. I don't want to use ms-office....

    Terence Devlin wrote:
    Of course there's another way of looking at it.
    First of all this autosave behaviour. I really don't want pages or numbers to save every nonsense I may write in a file, sometimes by simply mistyping cmd-v in a wrong window, without me telling it to do so. How dumb is that?
    Not Dumb at all. Very intelligent actually. Why on earth should protecting your data require an extra step - saving? All that's happening here is that the app is defaulting to protect the data, instead of defaulting to having the data unprotected. It's common sense that it should take an extra step to trash data, not to save it. What's odd is that no computer up to now has defaulted to protecting the data.
    But in fact is acting the opposite way. Instead of protecting my data is trashes the data, by saving when I wanted it not to. Do I actually have to kill the pages from terminal with -9 to prevent it from saving my data?
    Maybe other people find it useful, great, then why not just make it optional and let those who do not need it switch it off?
    Terence Devlin wrote:
    If I write an invoice to the customer, I take the invoice from the last month, click save as, select new number and change some dates and sums.
    So, to be clear, you're using last month Invoice as a Template, right? So, why do that when you can just use an actual Template? Much more simple. That's what that whole 'Save as Template' command is about.
    This would mean that I have to save each and every document I write as template? I have several customers and always write the new invoice based on the previous one (change in adress, other people worked on it, etc). Saving it each time as template and creating a new one from template is not really an easy workaround to the save as thing. And, yes, TextMate, Eclipse and 1000 other programms do offer a save as button, and I never lost any data in it yet...

  • Premiere crashed, my project won't open because of an "unknown error," and my autosave apparently stopped working 6 hours ago... Any solution?

    I'm working in Premiere Pro CC 2014 on an early 2014 iMac.  I started to notice my session was getting kind of buggy - audio clips started missing from my timeline, effect controls on some of my video clips had set themselves to the defaults.   So I was trying to fix some of these things as I was editing.  I save compulsively (like after every couple of edits),  so I had not noticed that my session was no longer auto-saving. 
    Suddenly Premiere crashed. The recovery file will not open "due to an unknown error."  The original file that crashed will not open either (same message), and I notice the file size is about half of what it should be.  When I tried to open an auto-saved version, I discovered that the last auto-save was last night at about 10 p.m.  (I quit working last night at about 1 a.m., so it just spontaneously stopped autosaving midway through my edit session.) 
    I followed all the suggestions I could find in forums.  I trashed preferences, and I moved all my media into other folders.  But the session won't open even far enough that it starts asking for media.  When I create a new project and try to import my old edit sequence, dynamic link won't even get to the point where it asks me to select what sequences I want to import.  It just sits there forever trying to open the file and can't.
    Any  suggestions?

    Additional info - As I look further into the problem, it's even worse than I thought.  The autosave files that say they're from last night are actually referencing work from days ago.  So evidently, my auto-save is either putting incorrect time stamps on the files, or the project files are referencing old sequences.  Either way, I cannot seem to locate a project file that contains a reasonably recent version of my cut, even though the time/date stamps on the files indicate they shouldn't be that old. 

  • How can I stop apple mail from autosaving drafts?

    Hello all,
    I have finally got myself a new computer and been immersed in the "new" way- my old mac was a bit like a volkswagen beetle, old and cranky but very efficient.
    This new interlaced madness is proving to be very confusing on many levels but here I will state one problem I am seeking a solution to:
    Apple mail autosaves  a copy of my email reply drafts every 30 seconds in my apple mail draft folder. - This means many copies are saved!!!
    How do I stop this?
    The reason I ask this is for the following reasons:
    1- If I don't send my reply after 30 seconds I have to manually delete the drafts.- I didn't know this until I was doing a little organising and have realised that I have quite a few drafts of the same message lying around in my google on mac (imap) "all mail" folder and these end up taking alot of space.
    2- These then get transfered to my google mail "all mail" folder and end up taking up more space.
    3- Manually deleting things from my google on mac "all mail" account is a pain in the *** because I need to delete it into the googletrash on mac and not any other deleting area. (unless I do it directly from gmail) I didn't know this until I had a read through google- the "all mail" archive is another pain in the ***.
    I was deleting these messages from my mac "all mail" mailbox and they just magically reappeared into the same "all mail" mailbox, meaning they are downloaded from the server continually- I hate to think how much more that adds to data roaming.
    Possible solutions I have tried out:
    1- uncheck the "save draft on server" box in mail;preferences;mailbox behaviour (and saving it) - I did this and tried to write a message and there it appeared as each 30 seconds passed
    2- change the mac mailbox behaviour settings to gmail Imap settings for apple mail and save these- as above, I wrote a message and it still appeared in my drafts folder, new, message appearing every 30 seconds.
    3- uncheck the "use idle command if server suppors it"  box in mail;preferences; accounts;advanced (as someone mentions in another forum) and the message still autosaves.
    HELP!
    1. This seems to be common with most people
    2. I am using gmail and IMAP on mac book pro 2012 10.7.4, lion
    3. This never happened with my volkswagen which was also a mac but from 2006
    4. Some people say this is Imap related. I have only noticed it with this apple mail and have read it has been happening to people since 2008.
    5. Look forward to new solutions

    I'm having a similar but slightly different problem. My company just migrated to Gmail, and it's saving mail drafts every 30 seconds into my Trash folder.
    I unchecked the "Show in IMAP" preference in the Gmail settings, but my Drafts folder completely disappeared. I went back and checked it and the folder reappeared (with my drafts still in there).
    I like the idea if starting an email on my laptop and having the option of finishing it on my iPhone or iPad, so only saving Drafts locally would not be ideal.

  • Is there a way to limit the frequency of the "autosaving drafts" feature in Mac Mail on Lion?

    Using Mail Version 5.0 (1244.2/1244.3)
    On MacBook Pro with Lion 10.7.1
    Wondering if Is there a way to limit the frequency of the "autosaving drafts" feature in Mac Mail on Lion?
    Looked all thru preferences and googled the crap out of this and can't seem to find the answer I want.
    Basically, I have my mailbox behaviors set up exactly the way I want them. (ie deleted messages get saved to my "Trash" folder on the server) I do not think I should have to change them, but because of the autosave feature saving almost every 3 characters typed, I have an over abundance of versions saved in my Trash folder. This problem would be solved were there a preference somewhere I could select to save drafts "manually only" or "opened messages save when quitting" or something along those lines.
    Is this a preference setting already that I am missing?
    I would settle for a rule, just not sure what perameters should be set for this to work.
    Help

    Typically a server has a settable parameter to limit concurrent connections. Check the server's documentation.

  • Is there a way of getting my Air client to autosave?

    Hi,
    we have developed an Air application and want to add autosave functionality.
    Does anyone know how to do this? Is there a Cron function?

    Maybe use a timer. Here is a link to an article discussing timers and the enter_frame event:
    http://help.adobe.com/en_US/as3/mobile/WS4bebcd66a74275c36cfb8137124318eebc6-7ffb.html

  • Autosave & Versions. Is it a bug or well implemented feature?

    After reading hundreds of topics and google articles I'm still clueless regarding this autosave feature. Is it an early version of a future product with bugs in it, or it's the final product which is working just as good as Apple originally thought.
    It looks like I'm not the only one who has problems with this feature. Please stop advertising the workaround of duplicate and revert. It might be a solution for home users and rookies with no computer background, but not for heavy users.
    So the question is simple. Are we an early adopters of a technology which has its issues, and Apple will fix them accordingly ….. or ……..
    And my fear is this: This is how it should work and it's a great new feature.
    In the meantime how do you solve this two issues thanks to autosave:
    Quote from different users
    "Add to it that if you have Versions on text documents, it's practically impossible to figure out what you want to go back to and what you want to throw away for any kind of text file longer than one page or so. What are you going to do with the zillions of versions saved against your will, in case you really need to go back to a previous version of, say, a manuscript of 40 pages? Are you going to read all the 40 pages a zillion times? Because Versions does not show you the changes between versions, but the full **** thing!"
    "The recipe for self-destruct comes from the fact that, while this by itself is just annoying for business users, the fact that Lion does not support versioned files on network volumes (even an AFP share on a Lion Server) creates disaster. Currently, when you make changes to a file that resides on a server and close it, the original file is modified but no previous version is saved that you can revert to when you open it up next and realize your mistake. Want to test this out for yourself?
    Take a screenshot with Command-Shift-4 and move that beautiful image over to your file server.
    Open the image up in Preview.
    Select an area of the image and hit Command-K to crop it.
    Print the image (this step really doesn’t matter, but it’s here to give you an idea of why you would do this in the first place).
    Close the image.
    Open the image again and try to find a way to get your original image back. Buh-bye, no more pretty screen-shot.
    Cry.

    MacGuy From Hungary wrote:
    Take a screenshot with Command-Shift-4 and move that beautiful image over to your file server.
    Open the image up in Preview.
    Select an area of the image and hit Command-K to crop it.
    Print the image (this step really doesn’t matter, but it’s here to give you an idea of why you would do this in the first place).
    Close the image.
    Open the image again and try to find a way to get your original image back. Buh-bye, no more pretty screen-shot.
    Cry.
    Did you actually try those steps?
    That is a rhetorical question - of course you didn't. If you had, you would have noticed that as soon as you attempted Step # 5, Lion displays the following dialog:
    The remarkable thing about Versions and Autosave is how much research and thought Apple put into the feature. It is a new feature providing new capabilities that have never existed before. No good deed goes unpunished.

  • I need to turn off autosave for one Numbers document

    I have a Numbers document consisting of a single blank cell. I use it as follows: I have 10 small spreadsheets that I have to combine each week and save as .csv. I wrote an applescript do open each spreadsheet and paste it into the 1-cell document. I then save it as .csv and close it, throwing away all my changes. This way the 1-cell document is ready for next time.
    Unfortunately, sometimes Numbers autosaves in the midst of all this, ruining my 1-cell document that I never want changed. Can I set things up so that a particular document never autosaves? I tried locking it in the get info window, but then my Applescript can't paste in the other spreadsheets.

    Hi Edtpierce,
    Log onto ePrintCenter and select the print app that you wish to pause. Click on “setup,” then “Update settings,” then choose “Pause” for the desired amount of days. You can also select the print app from the printer panel and select “pause”.

  • Periodic autosave of XML file

    Hi guys, 
    I'm having quite simple task, but no idea how to achieve it. A have a While loop, inside it I have som form to fill in and the output of this form is saved into xml file (using older MSXML library) and OK button for running parser and writting data into right place in XML file. All I need to do is to save XML file after the Stop button is hit, or after e.g. five minutes of application run. Just simple autosave feature.
    For better ilustration, please see picture, or example.vi file. 
    I am running LV 2012
    Thank you for your answers.
    Attachments:
    Example.vi ‏9 KB

    You could put these functions in an event structure within the loop. Have a shift register on the loop, passing the value through the various states of the event stucture. Have the "save" button trigger an event to save your data, and at the same time (bad pun) put the current millisecond timer value onto the shift register. In the time out case of the event structure (with a time out value of, say, 100mS wired to it to cause the timeout case to trigger regularly), compare the value of the shift register with the current millisecond count and when enough time (x) has passed have it: 1) put the new time count on the shift register, 2) save the file. This should ensure that the file is saved every x within a 100mS window of time error.  
    Putnam
    Certified LabVIEW Developer
    Senior Test Engineer
    Currently using LV 6.1-LabVIEW 2012, RT8.5
    LabVIEW Champion

  • IMovie DOES NOT AUTOSAVE!!! Why the **** did Apple remove "Save" in the first place and how to fix this problem?!?!

    There's no good reason Apple removed the ability to manually save. I work in a project, I save it at a point and then make edits that I may or may not want. It could be 1000 changes I make before I see that I'm not satisfied with them and want to revert back to my last saved session. In iMovie not only can I not do that but the autosave doesn't work and has cost me tens of hours!
    iMovie just hit me with a bug saying I couldn't share becuase there wasn't enough memory so I have to quit iMovie, open it up again then try to share it. Well, there IS enough memory so I don't know why it was saying that anyway. But besides that, I was afraid to quit iMovie because the **** thing never saves.
    I google and find out I can duplicate a project and that should save it. I do that. Restart it. Bam. None of the changes I've spent the past 2 days on saved....
    Why has Apple broken their iMovie like this and is there ANYONE that has figured out a way to make projects save?
    This is absolutely the last time I'm using iMovie (or any Apple app that removed manual save) but I've done too much editing to start all over again in another video editor. I need to make these changes AGAIN then save them.
    How?!

    Here is all my battery information if that helps for troubleshooting:
    Battery Information:
      Model Information:
      Serial Number:    W01305XA8D3BA
      Manufacturer:    SMP
      Device Name:    bq20z451
      Pack Lot Code:    0
      PCB Lot Code:    0
      Firmware Version:    201
      Hardware Revision:    000a
      Cell Revision:    158
      Charge Information:
      Charge Remaining (mAh):    4767
      Fully Charged:    No
      Charging:    No
      Full Charge Capacity (mAh):    5539
      Health Information:
      Cycle Count:    112
      Condition:    Normal
      Battery Installed:    Yes
      Amperage (mA):    -2234
      Voltage (mV):    11819

  • The autosave feature does not work on Pages 5.2

    Since downloading the new version of Pages with Mavericks, the auto save fearure has never worked for me. After initally saving the document to iCloud, giving it a name and folder, every time I make a change I get the 'Edited' label next to the document name. I have to cmd-s of file save in order for the document to be saved, or am promted to save when I close to app. I have tried deleting and reinstalling Pages with no luck.
    Is there a way to turn the feature on, Please help ?!
    P.S- I am on Late 2013 Retina MBP 13", running latest software on both OS X and Pages.

    I don't think either of your "indicators" actually refers to whether a document has been autosaved; they both refer to the saving of a version.
    The prompt to save is a reflection of the setting in the General pane of System Preferences to ask when closing; if that is unchecked, the document will close without a dialog, but including the changes that you have made since the last version that you marked with ⌘ S.
    The "Edited" label indicates that there have been changes since the last marked version. The changes may have (eventually will have) been autosaved to disk, but if you browse back through the version history, the first step will jump over those most recent edits.

  • Photoshop CS6 is autosaving when it shouldn't be

    I turned off the autosave feature in CS6 but I'm finding that when I open an image in PS via Illustrator then go back to Illustrator, I get a dialog box saying the image has been updated. Usually all I'm doing is just opening the image and viewing it.

    Check the date on your Photoshop file, and let us know if the date has changed, or if this is a false positive from Illustrator.
    Also are your prefs in Photoshop set like this?

  • Does anyone have corrupt premiere projects and autosave files?

    A Premiere CC project that I have been working on for weeks now is corrupt and will not open.  I get a message "the project appears to be damagaed".  All of the associated autosave files are also now messed up (some are a month old). Everything else on the drive that contains the projects is fine. Even other older Premiere projects are fine.  I open the bad autosave projects in notepad and it is filled with jibberish compared to the other uneffected projects.  Is this a bug or have I been hacked by the recent Adobe securiy issue?  Here is a link to the project file http://adobe.ly/1awiNVO
    All of my autosave files look like this too.  How could all of my auto save files change to this jibberish too?  I could understand if a save to my current project goes to left field, but how do all of my autosaves get corrupted too?
    I have written out large portions of the project to finished movies, but still have a few I will need to start over from scratch if no one has a solution to my problem here.  I would really like to have a chance to go back and re-edit if I see anything I want to touch up in the exported movies I have.  Thank God I at least have what I do otherwise it would be a months worth of work down the tube.   Has anyone else had this issue, or better yet have a fix? 

    Thanks Jon, I was not aware of the new zip files for the project files in CC.  As Ann had confirmed, the project file was actually intact.  I moved all of my assets and the project to another machine and it opened just fine.  I still do not know why the project will not open on the other machine.  Premier will open and start a new project, but I get an error code if I try to open that project.  I did start the project in CS6 and convert it to CC when we upgraded, but a bug there still does not explain why the same project works on one computer but not the other.  I will do a better job of asset management next time I work on that computer just in case:)

  • Adobe 9 Pro crashing in Win7 x64 - and Autosave

    I've searched all through the internet and these forums (which do have good info), although I have not found a solution to my problem.
    We have a small office of 10 computers with Windows 7 Professional 64bit (on win2008 server domain) each with Adobe 9 professional (all updates and patches installed).
    For the most part everything runs smoothly and great, but every so often ( a few times per week) Adobe will crash while working on a large PDF (100 or more pages, with bookmarks, highlighting, etc.) and the user will lose the document they were working on unless it had been recently saved. The crashes are so intermittent and unusual, I'm not concerned with that at the moment... there appears to be no common denomenator in the crash happenings.
    What I am interested in is a better Auto-save feature or way to more fully restore Auto-save data files.I've changed autosave to happen every 10, 5, even 1 minutes, but although after the crash happens, Adobe recognizes the autosave and tries to open it, the document is corrupted and of no use, having lost a great deal of information in the original PDF. So, I'm telling my users to constantly click "Save" or Ctrl-S.
    Is there a better autosave functionality? A way to not save a backup only data file that can be recovered upon crash, but an automatic save to the current document? Any solutions, ideas or discussion is certainly welcomed here. Thank you for your time and I'm very interested to hear any ideas and/or thoughts!
    Dan

    Thank you again for the reply. I have been worried it's an x64 issue. Normally everything works so well though. I certainly understand that any program may have issues and crash from time to time.
    What would really be helpful is more info on the auto-save feature. I have not been able to find any way to modify its settings (other than on/off and how often). Does anyone know of a way to not merely auto-save a backup, but to have Adobe automatically save an open PDF on a specific interval, equal to ctrl-s to save? Thanks again for any help.

  • Word 2007 crashes during autosave and when saving as .DOC

    Hi,
    I have a problem with Microsoft Word 2007. It crashes every time during autosave. It also crashes when I try to save a file as .DOC (even an empty new file). When I save it as any other file type it's fine. 
    I have already tried repairing the office installation, reinstalling the whole suite (and then installing SP3 and all latest patches again), auto fix it from
    http://support.microsoft.com/kb/822005/en-us and
    http://support.microsoft.com/kb/921541/en-us, changing the autosave file location, using different windows account. None of these helped. I wouldn't like to work with autosave switched off.
    I am using Windows 7 Professional SP1 and Office 2007 Professional 12.0.6683.5002 with SP3 on HP EliteBook 8470w.
    -- Igor M.

    Hi,
    I tried to start Word in safe mode be it did not change anything. I also tried to start Windows 7 in clean boot but it did not help either (same issues).
    Two entries are added to the event log when Word crashes:
    First one:
    ID: 0, Application Name: Microsoft Office Word, Application Version: 12.0.6683.5002, Microsoft Office Version: 12.0.6612.1000. This session lasted 94 seconds with 0 seconds of active time.  This session ended with a crash.
    Second one (Google translation):
    Log Name : Application
    Source: Application Error
    Date: 2013-12-29 0:38:43
    Event ID : 1000
    Task Category : (100)
    Level: Errors
    Keywords: Classic
    User : Not applicable
    Computer: XXX
    Description:
    Name of the application causing the error: WINWORD.EXE , version : 12.0.6683.5002 , time stamp : 0x520bb457
    Name of the module causing the error : wwlib.dll , version : 12.0.6683.5002 , time stamp : 0x520bb54c
    Exception code : 0xc0000005
    Fault offset : 0x0006d564
    The process ID causing the error : 0xbb0
    Time to run the application causing the error: 0x01cf0425b9f67b73
    The application path causing the error: C : \ Program Files (x86 ) \ Microsoft Office \ Office12 \ WINWORD.EXE
    The path of the module causing the error : C : \ Program Files (x86 ) \ Microsoft Office \ Office12 \ wwlib.dll
    Report ID : 2fcdf5c7 - 7019 - 11e3 - 96f9 - 1c3e84fe29b2
    Event Xml :
      "><Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
        "><Provider Name="Application Error" />
        1000</EventID>"><EventID Qualifiers="0"> 1000 < / EventID >
        100</Task>"><Task> 100 < / Task >
        "><TimeCreated SystemTime="2013-12-28T23:38:43.000000000Z" />
        Application</Channel>"><channel> Application < / Channel >
        "><Security />
      "><EventData>
        12.0.6683.5002</Data>"><Data> 12.0.6683.5002 < / Data>
        wwlib.dll</Data>"><Data> Wwlib.dll < / date >
        520bb54c</Data>"><Data> 520bb54c < / date >
        0006d564</Data>"><Data> 0006d564 < / Data>
        01cf0425b9f67b73</Data>"><Data> 01cf0425b9f67b73 < / date >
        C:\Program
    Files (x86)\Microsoft Office\Office12\wwlib.dll</Data>"><Date> C : \ Program Files (x86 ) \ Microsoft Office \ Office12 \ wwlib.dll < / date >
      ">< / EventData >
    <span title="">< / Event >
    Kind regards,

Maybe you are looking for