PP CS6 Project freezing on Auto-Save and Save-As.

Hi,
I have a project that I've been using every month to solely to create titles and just yesterday a bug showed up....whenever it goes to auto-save the project, PP freezes and I have to force quit it. I tried moving the project to another location and had the same problem. I also tried  doing a save-as to create another coply of the project and that freezes PP as welll...I am however able to save the project, just not auto-save or save-as. Thoughts??

There is the problem with that sentiment. I don't like the loss of "save as" either. I think the new save/duplicate paradigm has more steps and is poorly implemented to boot. Yet, people complain far more about Versions and Autosave than they do about "save as"? Why on earth would anyone complain about Autosave? There is no user interface change involved with Autosave. It is entirely in the background. If you don't like Autosave, you are free to randomly delete files from your machine and from Time Machine if you want. I don't see what the point of that would be, but it would give you the same effect of not having Autosave. There is more a user impact to Versions, but it still a really cool feature. Why would you not want to have access to old versions of your document? It isn't going to eat much disk space. The last time someone complained about disk space usage by versions I calculated that it would take 38 years for them to run out of space due to Versions. If you don't want to use Versions, don't click on the Versions tools. Problem solved.
I don't want people lumping clear losers (like no more "save as") with clear winners like Autosave and Versions.

Similar Messages

  • What could be causing Illustrator CS6 to freeze when I save a particular .ai file?

    I tried saving it in a new location, changing the name, and saving it in a legacy format. Every time I ended up with the spinning beachball. No other file is having this issue. What could I look for in the file that might be causing this?
    Interesting note: once during this process I left the computer for 20 minutes, and it eventually unfroze. Still had the same issue when I tried to save it again.

    We have seen this issue with the latest Esko Data Exchange plug-in, version 12.0.147 and Illustrator CS6.
    If you are using Pantone Plus swatches, you may see a beach ball during a save. Either, remove the Esko folder from the Illustrator Plug-ins folder, or change your Pantone Plus swatch from an LAB value to a CMYK. Your file will now save correctly.
    UPDATE: I received a response from Esko, they said to turn off this option: In Illustrator CS6 go to: Illustrator/Preferences => Esko and turn off "update XMP on Document Save". Confirmed, it corrects this issue!

  • Adobe Premiere Cs6 Windows freezes with Tesla M2090 and Quadro FX 4800

    Premiere works firn with the Quadro FX 4800 in Windows. But I bought a Tesla M2090 and it loses all power. For example a video cannpy be displayed on the monitor screen and if you try to play it on the porgram window, it freezes the whole application. It has to be killed.
    I wonder if anybody ever tested this card. It passes all tests (the M2090) from the Cusa Toolkit.
    Maybe somebody knows a utility to test the Tesla and see if it really works as expected.
    I can open a technical support ticket if it makes sense.
    Update: I moved the Quadro FX and Tesla to a MAC, there is no advantages on speed when exporting a movie. Isn't Premiere supposed to work faster with a Tesla on Mac as well. That is what they told me in tech support. The M2090 does not work in Windows, and in a Mac is not taken into consideration, I guess since Nvidia did not write a Mac driver for this card and it still uses a generic CUDA driver
    I am despondent over this. Adobe support gave me wrong information.

    It is explicitly stated Tesla C2070/2075 and a Quadro card only to achieve a Maxumus configuration, not a very old FX card. Given the limited number of CUDA cores in the Tesla card and the limited bandwidth, the first Maximus results are far from appealing. A Quadro 6000 + Tesla  C2075 (€ 6000) is slower than a GTX 570 for a fraction of the price (€ 270). Talk about BFTB.
    From the documentation I have found about the M2090, for a whopping € 4800, it requires Windows Server 2008, is still based on the Fermi architecture and has the same number of cores as a 580, but less bandwidth.

  • No auto-save

    Hello...  Would anyone know why my auto-save function does not perform (CS6)?  I have it checked in preferences for every fifteen minutes, 6 versions.  No folder is created, and no auto-save window pops up while editing.... ever.  I've tried changing the interval times & no. of versions.  I've built several "dummy" projects, still no auto-save folders are being created.  It would be great not having to hit control-s after every edit.  Any ideas?  Thanks!

    IIRC, AutoSave is invoked, after the first time that the Project is Saved (File>Save, or Ctrl-S), and should then function, per your Preferences.
    I do seem to recall an older post, regarding AutoSaves not functioning, but thought that was for one of the updates to CS 4? Will see if I can locate that, in case there is something useful for you in it.
    Good luck,
    Hunt
    [Edit] OK, here it is, but there is not much in it, other than a link to a similar issue in CS6: http://forums.adobe.com/message/4708480#4708480

  • Auto save is not working

    There is some problem after upgrade to Lion, Auto save version is not working in Iwork and anyone can fix it please advised. T.T

    I have experienced projects not being auto save back-uped, and linked that to file structure problems (like I moved the project from the folder where it originally was created, or I changed the folders name where the Pr project was residing after starting it. I think that these things can lead the Auto-Save to get confused sometimes. This can also happen in Ae as well.
    I have gotten used to making a duplicate of the project every day or at junctures of major change in the finder. The Mac finder duplicates the project file with the added word "copy" so I know that it isn't the original project file. I then add the date and time to the end of the file name _yymmdd_hh and send a copy to another drive.
    It's too bad that there is no option in Pr to have it save the Auto-Saves to different drive than where the original is.
    I also use a droplet created with a Mac renaming utility called "Name Mangler". Here is the macro for the advanced area of the re-namer in case anyone is interested.
    [concatenate
              <name>,
              "_", [modified "%y%m%d_%H"],".", <extension>
    I just drop the project file onto the droplet and it gets appended with its modification date.

  • Premiere Pro CS6 Project Manager gives error & will not manage project - OS X Lion 10.7.5

    Premiere CS6 project manager reports  an error and will not manage my project. I have tried several times with both "Create New Trimmed Project" and " Collect Files and Copy to New Location". I have also tried to manage the project with options checked and unchecked (Include Preview Files, Include Audio Conform Files, Rename Media Files to Match Clip Names). Every time I try to manage the project, the process takes a few hours and then gives an error asking me to try again.
    The project is 90 minutes long and uses multiple footage formats:
    Sony FS100
    Sony NEX7
    Sony NEX-5n
    Canon C300
    Canon 5DmkII
    Panazonic HVX200
    My computer is:
    Processor  2 x 2.66 GHz 6-Core Intel Xeon
    Memory  12 GB 1333 MHz DDR3
    Graphics  ATI Radeon HD 5770 1024 MB
    Software  Mac OS X Lion 10.7.5 (11G63)
    Is this a bug, or are there specific things I can do to troubleshoot the problem? I have read of issues with AVCHD. I have confirmed all of my AVCHD folders are intact. Any other Ideas?
    THANKS!

    I have this same problem on a Mac with CS6. I was simple trying to archive a project using the "collect files" option. After five or six hours of troubleshooting (Thanks Adobe) I have narrowed it down to MXF clips that came over in a Final Cut EDL (Projects created in PP with MXF files seem to be fine).  In other words, as I was transitioning from FCP to Premiere Pro, I sent four or five projects out of FCP as an EDL, opened them in PP and continued to edit.  It seemed to work really well until I attempted to archive my media.  If there was a single raw MXF file in the timeline (Not the project panel for some reason) the Project Manager would give me the standard error:"An unknown error occurred during the Project Manager operation. Please save your project and retry the operation.".
    I have found two solutions that seem to work, both of which are a pain in the ax. 
    Option 1: Save the original project file only to an archive folder.  Then delete all the old timelines from the project, and save the project with a new name.  Create a new timeline and just drag all the raw video and audio into it. (Project Manager needs a timeline of some sort to archive) Then use the Project Manager to archive the modified project.  If I need the project in the future, I'll need to open the original PP project and relink all the media from the archived "media only" project folder. 
    Unbelievably, if you were to take this route and then re-edit the project in the future, it looks like you would run up against the same archiving issue AGAIN next time (At least using CS6). You'd have to go through all the steps above to archive it a second time. Depending on the size of your project, you may want to take option 2 and get the pain over with once-and-for-all.
    Option 2: If you only have a couple of MXF files in the timeline (in my case I had mostly renders from AE by the time I was done and THAT raw project had archived in AE just fine) you can export the raw MXF files to another format, then replace the media in your project panel.  Finally, use the Project Manager to archive the project like you should have been able to in the first place if Adobe had written the code well in the first place!

  • 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.

  • 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. 

  • How can I continuously auto-save and auto-name the JPEG files with a controlled time interval

    Hi,
    I am newly involved in some Labview projects that out of my knowledge. I am trying to save multiple JPEG images from a live imaging task to a folder in the computer hard disk every certain minutes. I'd like to name these files with the date and time (eg. Img_06012011_1635. jpg).Then, after hours long image capturing, I can have all the image files in a neat order.
    My goal is to have the jpg files auto saved and auto-named with the data and time at that moment. I also need to control this waiting time between each savings.
    Could you please show me some hints about this? See the vi attached, I know I need to do something on the "write path" part on the up right corner. Thanks!
    Solved!
    Go to Solution.
    Attachments:
    capture.vi ‏28 KB

    Thanks, Steve. When I built up a path with the date and time info and send them to the WriteJPEG File.vi like you mentioned, it stopped saving any files into the folder. Do you think this is the problem from my while loop?Could you show me if there is any other secret functions that restrains the file saving?
    I am planning to save the image files every 30 secs,for example, and then I can have a bunch of jpg files with their unique names after hours long image acquisition.
    I appreciate you kindly help!
    Attachments:
    capture(updated).vi ‏29 KB

  • 'Serious Error' and Auto-Save failure

    I have several times encountered the 'Serious Error' dialogue, mostly immediately after attempting to insert an audio transition (crossfade) between two simple audio clips.
    I have unsuccessfully attempted to research and fix the issue, so instead I have increased my auto-save frequency to every 5 minutes.
    I had been working on a project for two hours or so before a serious error popped up.  Auto-save dialogues popped up every few minutes.  I restarted the program and found that the project had reverted to a state several hours old.  Why is this?

    I can't explain the cause, but I can suggest a fix.
    http://forums.adobe.com/thread/1369232?tstart=0

  • CS6 Premiere freezes on save

    Working on a 2008 Mac Pro
    10.6.8
    2 x 2.8 GHz Quad-Core Intel
    18 GB of RAM
    Not quite sure how else to explain it. I'll be working on a project and everything is running fine. I go to save and the progress bar will get maybe a quarter of the way along and then it hangs. Very frustrated to lose all that work. I tried shortening the time of auto-save to help out. Now when the auto-save kicks in, same thing, little less than quarter of the progress bar and it hangs. Everything unresponsive. The problem is that sometimes it will save. I am not doing anything different when it is sucessful. Same screen layout, dame filters, same project.
    Help?
    John

    I am on Windows so have NO idea if any of these will help, but reading these saved links may point you in the right direction... especially the first 2 links about permission problems
    Mac and Root User http://forums.adobe.com/thread/879931
    -and http://forums.adobe.com/thread/940869?tstart=0
    Mac and Playback http://kb2.adobe.com/cps/842/cpsid_84287.html
    Mac and 2 Monitors http://forums.adobe.com/thread/876566
    Mac & nVidia Driver http://forums.adobe.com/thread/1075592

  • Want to upgrade to Mountain Lion, but CS6 questions about Auto-Save need answers...

    Hi,
    I'm on Mountain Lion for all my "non-critical" work, but I'm still running the latest Snow Leopard on my main desktop machine, running CS6 Design & Web Premium. I've avoided the switch primarily because of the auto-save feature that Apple placed into ML. I haven't found a satisfactory answer anywhere on the web to this basic question...is auto-save a problem, as Apple implements it, with CS6 and working on images?
    In particular: 1. I work on very larger files, 4GB+ in size regularly, and I don't wan't the peformance hits associated with constant saving, 2. I make changes to images, downsizing them, croping, color corrections, etc. so that I can make jpg proofs for clients or myself. These are more "intermediary" images and not intended to be saved. I don't want to downsample an image, flatten it to creat a jpg for proof and have it overwrite the original image layered, high res by mistake. Does this happen with photoshop, or does Adobe avoid the auto-save that Apple uses?
    I have all the latest iOS gadgets and it's becoming quite cumbersome managing multiple sets of iCloud info, etc. without being on ML. I'd like to make the switch, but at the cost of losing work, etc. Can someone with experience on ML & CS6 give me any input in the matter? And, does this also apply to all the other Adobe apps in CS6? I'm constantly making minor changes and edits that I usually "undo" out of and don't want saved.
    Thanks.
    Craig

    So, in other words, photoshops behavior works the same, using save as..., etc. as it did under Snow Leopard? I should expect the auto-save behavior that occurs in apps like iPhone, etc., where i can actually lose the original because of the constant backups, etc.?
    Thanks.

  • 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 Versions not working

    Auto Save and Versions are not working in pages or numbers.  I've worked on a project for over five minutes when I "Xed" out the drop down box opened up and asked if I wanted to save.  Any ideas why?  Also, how do you open up versions?

    There is the problem with that sentiment. I don't like the loss of "save as" either. I think the new save/duplicate paradigm has more steps and is poorly implemented to boot. Yet, people complain far more about Versions and Autosave than they do about "save as"? Why on earth would anyone complain about Autosave? There is no user interface change involved with Autosave. It is entirely in the background. If you don't like Autosave, you are free to randomly delete files from your machine and from Time Machine if you want. I don't see what the point of that would be, but it would give you the same effect of not having Autosave. There is more a user impact to Versions, but it still a really cool feature. Why would you not want to have access to old versions of your document? It isn't going to eat much disk space. The last time someone complained about disk space usage by versions I calculated that it would take 38 years for them to run out of space due to Versions. If you don't want to use Versions, don't click on the Versions tools. Problem solved.
    I don't want people lumping clear losers (like no more "save as") with clear winners like Autosave and Versions.

  • Auto-save and file-recovery

    Dear Adobe,
    It is the year 2015. Just lost several hours of work in Illustrator. Thanks for making your professional community the beta tester of your half-baked products. I have no interest using Illustrator if you release version after version with new "features" and leave out the most important thing: file recovery and auto save. Honestly, I am in severe disbelief that this is not built in. Don't release an update if you don't do this first. This has happened far too much for me to have any patience, or just to say, "it's ok, I will re-do it".
    I can't find words to express my severe disappointment in this software. I am not the first one to have said this. If no solution is in the works even, you really don't care.
    Sincerely disappointed and frustrated,
    A Creative Cloud User

    spybraek,
    Only an old native here.
    With regard to autosaving, you may consider these (I am aware that you may know (of) them):
    CS5/CS6/CC & Vista/7/8 or 10.7+
    http://www.astutegraphics.com/software/autosaviour/
    https://forums.adobe.com/message/6616027#6616027
    For Mac users with CS6 or CC, the app "Ai Auto Save" can be bought here:
    https://itunes.apple.com/us/app/ai-auto-save/id877602617?ls=1&mt=12
    With regard to file recovery, the following may apply (this may also be (too well) known to you):
    One thing often tried first is to create a new document and File>Place the (PDF contents, if any, of the) corrupted one to see how much may be rescued that way.
    Here are some websites where you can see whether it can rescue the actual file, and if it can, you may pay for a subscription to have it done,
    http://www.recoverytoolbox.com/buy_illustrator.html
    http://markzware.com/adobe-software/fix-illustrator-file-unknown-error-occurred-pdf2dtp-fi le-recovery/
    http://www.illustrator.fixtoolbox.com/
    As far as I remember, the first one is for Win and the second one is for Mac, while the third one should be for both.
    Here are a few pages about struggling with it yourself:
    http://daxxter.wordpress.com/2009/04/16/how-to-recover-a-corrupted-illustrator-ai-file/
    http://helpx.adobe.com/illustrator/kb/troubleshoot-damaged-illustrator-files.html
    http://kb2.adobe.com/cps/500/cpsid_50032.html
    http://kb2.adobe.com/cps/500/cpsid_50031.html
    http://helpx.adobe.com/illustrator/kb/enable-content-recovery-mode-illustrator.html

Maybe you are looking for