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.

Similar Messages

  • Grab auto-save file type locked by Acrobat Pro?

    I have tried using the posted command line in Terminal on both my iBook and G4 (both running 10.3.9) to get Grab to go back to saving screen shots as .jpg's, but it does not work. Ever since installing Adobe Acrobat Pro 6.0.0 both machines are saving screen shots only as .pdf's. In addition (and I have looked through all the AAPro preferences to see if there is something to 'turn off' - there isn't), AAPro has inserted toolboxes into all Office programs and I cannot get this to stop either. I've tried moving AAPro out of the applications folder, but this has had no impact. Any suggestions on a workaround?

    Aha! Thanks. "PDFMaker Lib" was the file inside the Office folder. If that does not fix it I will search deeper into the folders for the culprit.
    Still cannot switch Grab back to saving as .jpg vs. .pdf, using that command line in Terminal. Any suggestions on that issue? Do you suspect Acrobat Pro is involved due to the fact that this problem started about the same time?
    AAPro has inserted toolboxes into all Office
    programs and I cannot get this to stop either.
    I've
    tried moving AAPro out of the applications folder,
    but this has had no impact. Any suggestions on a
    workaround?
    Acrobat Pro puts a file in a folder in the Office
    directory that causes the Acrobat Pro tool boxes to
    appear. Moving this
    file will stop it from coming up. The folder is
    called Extensions, or Add-ons, or Plug-Ins or
    something like that. (I can't look up the actual
    path since I'm stuck in front of a windows machine at
    work at the moment.)

  • Errors converting Nikon D70s RAW files since yesterday

    Yesterday i've installed "Digital Camera RAW Compatibility Update 2.2" which seems to be the cause for some really nasty problems with Nikon D70's RAW files.
    Now (some of the) files will simply display a dark red image just displaying "Nicht unterstütztes Dateiformat" (means "unsupported file format").
    Will there be a fix like "Digital Camera RAW Compatibility Update 2.3" quite soon?
    Is there any chance to go back to 2.1 ?
    Please, provide me some hint on what to do next.

    I have this problem myself, and others have reported it too, and that was before the this new "Digital Camera RAW Compatibility Update 2.2" was released.
    It looks like a bug in Aperture.
    Just search for "Unsupported File Format Error" to see more reports.
    Try sending them feedback with the pulldowm menu item.

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

  • Plugin or action to Autosave or Auto-Recover files??

    I know Adobe hasn't seen fit to include an autosave function in any version of Photoshop. I consider that the height of arrogance and stupidity. Some will argue the time it takes to auto-save files doesn't justify it's inclusion. The time and effort in creating the work is equal justification for such a feature. Why should I have to remember to save every 10 minutes or so when I have no idea when the silly program will suddenly crash on me for no good or explained reason? Why should I be put through that kind of stress that will affect my creative workflow?
    As an alternative it would be helpful to find some third party software, plugin that would do the same thing. It would be good if it could be set to a timed response. An action might do it but it still require manual activation. Perhaps someone knows of a script that could be written? Any ideas or suggestions other than "tough it out" and "you can't do that, too bad" would be appreciated.

    Control-S is not a plug-in and not a script.
    Of course it is not. I was taking a bit of a license there. However, it is the answer to the problem, is it not? It's simple, fast, and you know that you will have an interruption, when you invoke it, so you can pause, and not get caught in the middle of an intricate Selection, or some other operation, where you might, in fact, loose all of the work/time that you have invested.
    That is why Adobe has chosen (for all these years) to not implement an AutoSave.
    As the program can never be sure when you are done working on something, or are just relaxing your hold on your stylus, it would never know when it was "safe" to AutoSave. Some of my Selections take hours to create. I'd hate to loose them, because I was not done yet, and the AutoSave kicked in during that Selection, only saving part of it.
    For tiny, simple images, it'd not likely be a problem. Some would likely benefit. I'd have it disabled most of the time.
    As I pointed out, there are major differences to what is being AutoSaved, between Premiere and Photoshop. Still, many editors turn AutoSave off, because the every 5 minute (default time) pause disrupts their workflow. Even on my very fast, robust workstation, a Save can take 30 sec. on some of the images.
    No, the manual use of Ctrl-s is the answer. Every NLE users learns this, even with AutoSave. Well-timed Save_As operations can be a blessing too. Nearly every PS user knows about Crtl-s and most incorporate it into their workflow.
    Sorry the the humor did not work. I will do better in the future.
    Hunt

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

  • Recovring auto save projects

    I recently sent my Adobe cc 2014 to auto save every 5 minutes because of a recent experience of losing quality editing time.  Premiere crashed on my PC again and I'm trying to locate my auto save files.  They are not in the folder I created my original project in?  I tried opening premiere and loading my last project worked on and my most recent edits are not on the timeline!?! I have a deadline coming up and I would appreciate any advice/solutions

    Check the Scratch Disk dialog box where Premiere puts its auto save.
    If it is set to 5 minutes you should have seen the save window pas by every 5 minutes. If not it did not save your project.
    Then you need to restart Premiere or even beter your pc.
    On a side note don't rely solely on auto save.
    Make a habit of making a Save A Copy to another drive every so often.

  • Is Auto-Save still next-to useless?

    In both CS-2 and 3, AutoSave(d) files are deleted if the program crashes (while working in a project)... Is 4 the same?

    I have learned the hard way to be sure and hit "save" every time the autosave flashes across the screen. On a half dozen occasions over the past two years, I forgot to do so and of course had a crash. I just learned my lesson again today in cs3. A crash is somewhat rare, but when it did, and I was not able to hit save, all the auto save files that were generated during that project session (since the last full save) were lost - I am sure of it. I'd like to say try it, but....

  • Can't auto save to a network drive

    I have two computers set up in gigabit network usinf premiere cs3 to edit with.  Premiere won't auto save to the network that I the project is stored to, I have to save as a new file.  Any thoughts?
    Seb

    You're not the first to have an issue with Premiere on a network.  Best recommendation is to simply not use one.

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

  • Where are the auto recovery files stored for Visio 2010?

    I have auto recovery set for every 5 minutes.  I have been working on a file that has been saved several times a day.  Today when just moving a shape Viso 2010 crashed after I had been working on the file for over 2 hours.  Auto recovery popped
    up every 5 minutes indicating it was saving the file.  After the crash the ony file I could find was the file as it was when I first opened it this AM.  None of the work done today was saved. 
    Did auto recovery completely fail?  Where can I look for the auto recovery file? 
    I have not done a reboot because I am afraid that if the file exits it will be gone for sure if I reboot.  Any suggestions are welcome.
    There must be a temp file or something that I can look for but not sure what the extension would be or the location.
    Hopefully someone here can help.
    thanks,
    greg
    Greg J Wilson

    How do I know? You state the the auto-save file extension is .vxd - that's the Visio document XML format.
    You can change this in File -> Options -> Save
    As for the crashes, are there any messages when a crash occurs?
    Check that the video drivers you have are the latest, try a different screen resolution to see if that changes anything and turn off or change any screen accelerators.
    -- Paul Herber, Sandrila Ltd. http://www.sandrila.co.uk/ Engineering and software shapes for Visio.
    My mistake - the file format is .vsd - standard visio format
    Here is the info from the event viewer for the specific crash that caused me temporary pain.
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider
    Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated
    SystemTime="2011-07-25T17:15:25.000000000Z" />
    <EventRecordID>83552</EventRecordID>
    <Channel>Application</Channel>
    <Computer>gw-Tosh_laptop</Computer>
    <Security
    />
    </System>
    <EventData>
    <Data>VISIO.EXE</Data>
    <Data>14.0.6022.1000</Data>
    <Data>4d6eacd6</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>8469f91f</Data>
    <Data>1668</Data>
    <Data>01cc4ae02611b81c</Data>
    <Data>C:\Program
    Files\Microsoft Office\Office14\VISIO.EXE</Data>
    <Data>unknown</Data>
    <Data>af70a4ff-b6e1-11e0-82fc-001e33913568</Data>
    </EventData>
    </Event>
    Greg J Wilson

  • Text Edit auto save

    Starting recently whenever I edit a text file with Text Edit a second file appears in the same folder of the main text file, with the +same name+ but with a tilde appended to the file name just before the .txt postfix.
    I understand this is the result of the Text Edit auto-save function, however, different from the previous behaviour (probably before the 10.5.5 MacOS update) these auto-save files are no longer automatically removed when the application is successfully closed.
    Does anybody have the same behavior ?
    Is this a correct behavior ?
    Thanks
    Piero

    They should close after saving or quitting the application. I have no idea where the tilde came from. Have you created a fresh account to test? If it works in TextEdit in the test account try this by logging back into your problem account...
    Quit TextEdit, go to Users/yourname/Library/Autosave Information/com.apple.TestEdit.plist and move it to your desktop then relaunch Test Edit? You may also need to move Users/yourname/Library/Preferences/com.apple.TestEdit.plist to your desktop also.
    -mj

  • Use Auto Save? If so, what settings?

    Bob Dix recommended disabling Auto Save in PP CS4 about a year ago on Creative Cow. He said issues had been report there.
    What should I do? I lost the assets somehow for the first half of a 30 minute project, went to the Auto Save file only to discover that PP's default is only 5 auto saves every 20 minutes. Fortunately, I was able to get the first half of project back by importing a backup I made the previous day and importing it into the affected project and copying assets (wondering if it's wise to put everything in a new project in case the project file is corrupted).
    Auto Save sounds like a good idea. If you agree, what settings for it would you recommend? I "Ctrl-S" after just about every change I make in the timeline. but I never know what might be happening at the beginning of the timeline if I'm working at the end--accidents like a mouse hanging up while I'm trying to drag and drop an asset on the timeline and unwittingly damage assets at the beginning of the timeline (Why do mice hang up, anyway? Is it perspiration on the hand? Memory getting stressed? Having Bridge, AE, and PP open at the same time? I've got 12GB, but it's so annoying.).
    Your expertise is greatly appreciated.
    Paul

    Paul,
    I wonder what prompted Bob to suggest not using AutoSave. I have not heard a bunch of negative reports, when it's configured correctly, and then used properly. I leave the default setting of 5 AutoSaves @ 5 min. intervals. However, I also use Save, Save_As and Save_As_a_Copy in many Projects. They are all similar, but there are differences. This ARTICLE will give you some background. When you know how each differs, you can then determine a workflow, that suits you and your needs.
    If I am doing a particularly difficult Project, I might also "archive" some of the AutoSave folders and files, with a Copy, just for safe keeping. However, with the right combo of the various Save options, one also will have those extra AutoSaves too.
    Now, it does seem that Adobe has changed the AutoSave functions, but I have not been able to confirm this. At one time, AutoSave was pretty smart. If one did not do any editing, AutoSave would not be invoked at the time interval, only with editing and changes. Somewhere along the way, it seems that AutoSave now works ONLY with the interval, so that if one leaves the machine for an hour, they end up with 5 duplicate AutoSave files in the folder. Personally, I liked the "old way" far, far better. Who needs 5 (or whatever is chosen) duplicate PRPROJ files? Maybe something in the code forced Adobe to "dumb down" AutoSave?
    As a side note, you talk about loosing some Assets. I have a policy - never use original Assets in my Projects - only Copies, with the originals on my NAS. Capture files from miniDV tape is an exception, as I do not reuse tapes, and could always re-Capture, if necessary. Also, remember that the PRPROJ file does not contain any media (Titles are a limited exception), and ONLY links to that media.
    Good luck,
    Hunt

  • Can't copy to file: /users/chris/creative cloud files/premiere pro/8.0/adobe premiere pro auto-save/[my project name].prproj. please check write permissions."

    Does anybody how to solve this problem. I truly appreciate.
    i can't save my Project.        can't copy to file: /users/chris/creative cloud files/premiere pro/8.0/adobe premiere pro auto-save/[my project name].prproj. please check write permissions."

    It seems Josh was unaware you are on a mac. Here was the solution I found.

  • Would a 347 MB file be slow? Auto save and auto type turn off?

    I am doing an art inventory and add jpegs of the art. I don't resize them they range from 750k to 3MB. I guess if it is slowing the program down i should? It currently is 267 rows by about 18 columns.
    Thanks in advance.
    Oh can I turn off auto save and auto type? That may help. How do I do that?

    Done.
    Enter Scrip Editor
    paste the posted script
    File > Save > as Script  on the Desktop
    Move the script to the folder :
    Macintosh HD:Library:Scripts:Folder Action Scripts:
    CAUTION, you will be asked to enter your pasword.
    Create a folder to do the job. I named mine Normalized. I created mine on the Desktop where it's easy to reach.
    Go to :
    Macintosh HD:Library:Scripts:Folder Actions:
    Double click the alias :  Configure Folder Actions
    Below the left column, click
    navigate to select your new folder
    Below the right column, click
    select the script image - normalize400.scpt
    After that, drag and drop a picture file onto your folder.
    The original will be move in the folder Originals (isn’t it original ?)
    and a reduced copy  400 x height will be stored in the folder Normalized images.
    And now, here is the script :
    --{code}
    Image - Normalize
    This Folder Action handler is triggered whenever items are added to the attached folder.
    The script rotates the image counter-clockwise (left).
    Copyright © 2002–2007 Apple Inc.
    You may incorporate this Apple sample code into your program(s) without
    restriction.  This Apple sample code has been provided "AS IS" and the
    responsibility for its operation is yours.  You are not permitted to
    redistribute this Apple sample code as "Apple sample code" after having
    made changes.  If you're going to redistribute the code, we require
    that you make it clear that the code was descended from Apple sample
    code, but that you've made changes.
    modified by Yvan KOENIG (VALLAURIS, France)
    2011/12/08
    This version normalize pictures so that
    (1) the greater dimension become the width one (rotate left if needed)
    (2) this greater dimension is ruled by the property maxWidth defined below.
    property maxWidth : 400
    -- set it to fit your needs
    property done_foldername : "Normalized Images"
    property originals_foldername : "Original Images"
    property newimage_extension : "jpg"
    -- the list of file types which will be processed
    -- eg: {"PICT", "JPEG", "TIFF", "GIFf"}
    property type_list : {"TIFF", "GIFf", "PNGf", "PICT", "JPEG"}
    -- since file types are optional in Mac OS X,
    -- check the name extension if there is no file type
    -- NOTE: do not use periods (.) with the items in the name extensions list
    -- eg: {"txt", "text", "jpg", "jpeg"}, NOT: {".txt", ".text", ".jpg", ".jpeg"}
    property extension_list : {"tif", "tiff", "gif", "png", "pict", "pct", "jpeg", "jpg"}
    on adding folder items to this_folder after receiving these_items
              tell application "Finder"
                        if not (exists folder done_foldername of this_folder) then
      make new folder at this_folder with properties {name:done_foldername}
                        end if
                        set the results_folder to (folder done_foldername of this_folder) as alias
                        if not (exists folder originals_foldername of this_folder) then
      make new folder at this_folder with properties {name:originals_foldername}
                                  set current view of container window of this_folder to list view
                        end if
                        set the originals_folder to folder originals_foldername of this_folder
              end tell
              try
                        repeat with i from 1 to number of items in these_items
                                  set this_item to item i of these_items
                                  set the item_info to the info for this_item
                                  if (alias of the item_info is false and the file type of the item_info is in the type_list) or (the name extension of the item_info is in the extension_list) then
                                            tell application "Finder"
      --set name of this_item to "YK#" & (text -4 thru -1 of ("0000" & i))
                                                      my resolve_conflicts(this_item, originals_folder, "")
                                                      set the new_name to my resolve_conflicts(this_item, results_folder, newimage_extension)
                                                      set the source_file to (move this_item to the originals_folder with replacing) as alias
                                            end tell
      process_item(source_file, new_name, results_folder)
                                  end if
                        end repeat
              on error error_message number error_number
                        if the error_number is not -128 then
                                  tell application "Finder"
      activate
      display dialog error_message buttons {"Cancel"} default button 1 giving up after 120
                                  end tell
                        end if
              end try
    end adding folder items to
    on resolve_conflicts(this_item, target_folder, new_extension)
              tell application "Finder"
                        set the file_name to the name of this_item
                        set file_extension to the name extension of this_item
                        if the file_extension is "" then
                                  set the trimmed_name to the file_name
                        else
                                  set the trimmed_name to text 1 thru -((length of file_extension) + 2) of the file_name
                        end if
                        if the new_extension is "" then
                                  set target_name to file_name
                                  set target_extension to file_extension
                        else
                                  set target_extension to new_extension
                                  set target_name to (the trimmed_name & "." & target_extension) as string
                        end if
                        if (exists document file target_name of target_folder) then
                                  set the name_increment to 1
                                  repeat
                                            set the new_name to (the trimmed_name & "." & (name_increment as string) & "." & target_extension) as string
                                            if not (exists document file new_name of the target_folder) then
      -- rename to conflicting file
                                                      set the name of document file target_name of the target_folder to the new_name
                                                      exit repeat
                                            else
                                                      set the name_increment to the name_increment + 1
                                            end if
                                  end repeat
                        end if
              end tell
              return the target_name
    end resolve_conflicts
    -- this sub-routine processes files
    on process_item(source_file, new_name, results_folder)
      -- NOTE that the variable this_item is a file reference in alias format
      -- FILE PROCESSING STATEMENTS GOES HERE
              try
      -- the target path is the destination folder and the new file name
                        set the target_path to ((results_folder as string) & new_name) as string
                        with timeout of 900 seconds
                                  tell application "Image Events"
      launch -- always use with Folder Actions
                                            set this_image to open file (source_file as string)
                                            set {oldW, oldH} to dimensions of this_image
                                            if oldH > oldW then
                                                      set {oldW, oldH} to {oldH, oldW}
      rotate this_image to angle 270.0
                                            end if
                                            set |échelle| to maxWidth / oldW
                                            if |échelle| < 1 then scale this_image by factor |échelle|
      save this_image as JPEG in file target_path with icon
      close this_image
                                  end tell
                        end timeout
              on error error_message
                        tell application "Finder"
      activate
      display dialog error_message buttons {"Cancel"} default button 1 giving up after 120
                        end tell
              end try
    end process_item
    --{code}
    Yvan KOENIG (VALLAURIS, France)  jeudi 8 décembre 2011 21:25:33
    iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
    My iDisk is : <http://public.me.com/koenigyvan>
    Please : Search for questions similar to your own before submitting them to the community

Maybe you are looking for