Universal Auto Save possible?

so I live in a part of the world where power/light, though exists, is infrequent and often comes with a low current or a very high current. As a result I've lost many a file and was wondering if there is a universal auto save program out there of if there is maybe some way to configure automator to do that (a program I know nothing about FYI).
I do have a UPS (battery backup), and regulator but when the current comes high, it blows out the regulator and UPS so I'm still with semi frequent shut down.
Any help GREATLY appreciated.

Believe me I am ALWAYS saving but my need is not just for myself but for other staff who aren't as quick with apple+S. In there defense the power situation here (West Africa) is abysmal at best and really causes serious problems. Not only that but the sockets here are far less reliable than what I've experienced in US or Europe - when you think something is plugged in, it's not always getting power and even when it is drawing power the likelihood of it switching off is high. Thanks tho for your reply.

Similar Messages

  • IPhoto auto-save possible?

    changed to Mac 3 months ago and the only thing that's still bugging me is the way iPhoto works!
    ok, let's say I have a managed library where all the imported photos are saved into the iPhoto folder.
    when I make changes to the photos, can it not auto-save AT THE SAME POSITION instead of saving the edited photo in a different folder???
    If I make a change I want the original photo to be deleted and only keep the edited one.
    Because, if it keeps the originals and then in a year's time I want to say move to a PC or if I just want to backup in an external drive how will I do this without manually sorting out the edited photos from the originals that should have been deleted???
    PS: if you're nice enough to respond, please do not respond with links to "tutorials" as they don't answer this question, thank you.

    If I make a change I want the original photo to be deleted and only keep the edited one.
    Then don't use iPhoto. It's not a photo editor, though it can edit pics. It's a Photo Organiser - that is, it manages your digital assets and always preserves your original file in the way a film photographer would mind his negative. This is built-in to iPhoto, it cannot be turned off. If you don't want the feature then iPhoto is not the app for you.
    Because, if it keeps the originals and then in a year's time I want to say move to a PC or if I just want to backup in an external drive how will I do this without manually sorting out the edited photos from the originals that should have been deleted???
    To back up: simply copy the iPhoto Library from your Pictures folder. That gets everything: your Originals, your edited versions, albums etc.
    If you want to migrate then do it the really simple way: select the pics in the iPhoto Window and go File -> Export and set the Kind: to Current if you want your edited versions (or Originals if you want those).
    Bluntly there is never a need for you to access the iPhoto Library via the Finder or with any other app.
    Regards
    TD

  • FCPX undo / auto save bugs + RAM Hog - Possible Fix?

    Hi there FCPX users,
    I have a 8-core 2010 Mac Pro with 16GB Ram and the stock GPU running Lion 10.7.2
    I have been using FCPX since day dot, and have been overall very pleased with its super fast work flow and realtime capabilities.
    I have completed over 100 3-4min edits with average project size of 50GB, and a bunch of wedding edits with approx 150-200GB project sizes. The issues I had with 10.0.0 - 10.0.1  were mainly FCPX quitting unexpectedly.
    And now on 10.0.2 I have expereinced the well known auto save / greyed out undo bug. I have gone through all the steps via apple care which included:
    Trashing the Prefs, repair permissions, check drive space / correct format, new user account and clean install of lion / Final Cut X.
    I am still experiencing this issue. So yesterday I purchased another 16GB Ram totaling now to 32GB Ram, and I monitor the RAM usage via "Free Memory".
    I Noticed that if my RAM is running low, I "free Memory" without quitting FCPX and continue to work as normal, and so far I have not yet experienced the issue again.
    Dont know if this is a temporary fix, but it has worked for an hour long edit (approx 6-7 hrs without restaeting FCPX).
    Also, I have noticed FCPX will eat up 16-20GB RAM quite easliy.
    Not sure if this problem is related to RAM...
    My 2 cents.

    You have to really be conscious when you start a new project and how and where you manage your footage.
    No one has complained more than I have about FCPX's quirky behaviors and it can be frustrating. I have worked with FCPX since day one, even tried to get a refund but couldn't. After using it for a while now, it is very easy to get used to how fast some elements are in editing and reviewing a lot a footage. But several things you have to make sure of that will keep the rendering speed up and less crashing happening.
    First make sure that you can see how much space you have on your drives by right clicking in the main window of you screen and make the necessary clicks form the drop down menu. Make sure any drives you have been doing projects with lately are hooked up and do a secure empty trash. Its cool to see how much space you regain. 2) make sure that FCPX, Motion and Compressor (if you have those are installed on your boot drive).
    3) Create a FCPX Projects folder on an external (FW800) with at least 75% of its drive space available if you do not have secondary drive installed in your computer. (Its very important to note that any drive you use for any aspect of editing should never be more 75% full, especially your boot drive.) This is where FCPX will log all of its operating files for all of your projects.
    4) Either copy  all of the other FCPX files from your main hard drive and paste then into the new folder you created. Then delete all of those files, as well as any Motion files too! (Do the same as you did for FCPX in the previous step)
    5) If you need to move all of your music files to another drive as well. If its iTunes, you will have to tell iTunes where to look for the new files and it will populate accordingly. This will free up a tremendous amount of space. Make sure to delete them form the main drive.
    6) Remove any junk programs form the boot drive (main) or move them to another drive if possible.
    7) Now do another secure empty trash and watch your drive space return.
    8) Now open up FCPX and make sure you only create projects on your new drive by clicking on that drive in the project window. Any older projects you can simply pull them to the other drive and you will be prompted on how to duplicate that project and all its files to that drive. Delete the other ones.
    9) Only capture footage to you external drives. Save it there until you need it.
    10) Create all new projects on the secondary drive and pull any footage you are working with on that drive as well. By keeping it all off the Boot drive FCPX will run much smoother and faster, especially if you have at least 16g of Ram, which I recommend.
    So to re-cap:
    1. Keep your boot drive lean. Delete anything you can move to another drive. Do not set up events and or projects to it...never!!!
    2 Use you secondary drive for your project files and the video you are working with in your events.
    3. Store raw footage on a FW800 drive ready to move to your secondary drive.
    4. Use secure empty trash after all editing sessions when you are certain of your trash contents.
    Doing these things have greatly increased much more consistently faster render times and much fewer crashes.
    iMac 27  -  3.5gh  - 16GB Ram  -  Quad i7  -  250SSD/1TBesata  -  External FW800 Drives
    Good Luck

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

  • Texture Artists: Auto Save As Type

    I have used photoshop for years now. Mostly I do texture's for virtual enviornments. I was wondering if it would be possible to add a feature that allowed the users to automate saving as different file types from a PSD. Let me give you an example:
    Current Versions:
    I am working on a texture for a chair. I have one PSD named Chair.psd that has tons of information in it. Once I finish the texture, I have to goto save as --> targa (it auto renames to chair copy.tga) ---> rename it to Chair_DIF.tga --> save --> select 24 bit --> save. Finally I have it saved. Now I have to change a few layers I have set, or hide some and then save it as Chair_SPEC.tga and sometimes Chair_EMS.tga, Chair_NRM.tga. Once I am done with all that I can test it on the model in 3d... if a change needs to be made, I have to make it and then go through that whole process again. It is very repatative and pointless. Many times I have to do it 20+ times...
    New Feature:
    Allow the user to enable a special mode through the main PS preferences designed for texture artists. It adds a new drop down menu next to help labeled 'Auto Save As' or something. When you select it to drop down, it only has one option, 'new'. You hit 'new' and it brings up a dialog of what you want to call the new profile, what filetype, where the file should be saved, and and options the file type selected would normally have. For the filename, you should be able to choose if you want a whole new name, or just add a suffix or prefex to the PSD name. Once youe done, you hit create and it saves that profile to the PSD your working with. This is important, the options should save to the PSD. That way, any time you open up a file, it is automatically set to the save options and locations you want for that texture. From then on, any time you drop down that list, a texture artist could just click Diffuse Map, and it would auto save it to the proper location, filetype, and name. You could create one for anything you want: Specular, Normal, Emmisives, Balding, and so on.
    I beg you, please add this option in the next version of PS!

    So much love. However, it adds the layer comps index number to the file names on save. I suppose this would be good if you had comps the same name. However, I don't, so I changed the script manually and commented out that code.
    If anyone comes across this thread and wants to know how to remove the indexing of the file names, you can open up the Layer Compes to File script in notepad or any text editor and comment out the line:
         fileNameBody += "_" + zeroSuppress(compsIndex, 4);
    Simply add // in front of it. So it should look like:
         //fileNameBody += "_" + zeroSuppress(compsIndex, 4);
    However, I must warn you, if you do have comps the same name it won't work. It will save over the previous comps that have the same name...
    Thanks again J.

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

  • Auto save and very large files

    Hi  All,
    I produce very high dim artworks, 6m x 2.7m(+) image at 200ppi, sometimes when I load the files Photoshop cc2014 would randomly will crash. This never happened with my CS5 version. I have auto save checked, could this be the issue?
    I am running a high end computer with 32gb ram, 8 ssd's with two dedicated to PS scratch disk....the images, so far, load eventually but the heart beat stop moment when you think a file is corrupt really scares me, especially when $$$$$ are involved.
    Any ideas?

    Thanks JJMack
    I will try it. It is possible it's not the auto-save feature, cs5 was rock solid and gave me confidence as it never crashed even with files over 5gb. The crash report states the faulting model is unknown for the last crash but I have seen ntdll.dll as the faulting module in previous crashes.

  • A question about Auto Save, Versions and Preview.

    I haven't upgraded to Lion (yet?). I'm trying to understand what impact Lion will have on my workflow.
    Do I understand right that it is not possible to turn off Lion's Auto Save?
    And that the autosavings are stored in a hidden sqlLite data base?
    I use Preview for... err... previewing files (PDFs and image files). Nothing I open (preview) in Preview I save.
    Is Lion's Auto Save going to save every file I take a look at in Preview?

    Thebestplacehere wrote:
    I think is more a pro than a con to upgrade ..
    The idea of Versions looks good to me, it certainly is not a 'con to upgrade'. The amount of disk space it uses and where (on which disk) is a bit of a concern to me. But by the time the applications I work with implement this feature that probably will be sorted out.
    there's more to upgrading though.
    Not so much on topic:
    I do want to upgrade. Eventually. Although I do worry about the direction Apple are heading in, I don't want to get stuck in the past.
    I'm disappointed AirDrop is not for my computers. And the treatment Spaces and Exposé got really withholds me of upgrading any time soon. Maybe a third party developer dives into this matter. Working with an external display connected to notebooks has changed in Lion and is not particularly handy for everyone. (While using the external display only, opening the lid of the notebook in Lion turns on the display of the notebook. This was not the case before Lion.)

  • Auto-Save &Auto-Close after inactivity

    I'm new to JavaScript, so please be patient. I am using Acrobat XI
    I have a document that I am trying to have auto-save and auto-close after 10 minutes of inactivity. I've found where I would enter the JavaScript under the document actions, and I see the "Will Save" and "Will Close" functions, but I guess I don't understand what JavaScript I need to put in these fields to get them to do what I want.
    I can get the document to run JavaScript that will close the document after being open for 10 minutes, but I need it to save and close after 10 minutes of inactivity. Is this possible, and if so how do I go about this?
    Thanks SO MUCH in advance.

    The "Will Save" and "Will Close" events are only triggered after an action to save the PDF or close the PDF has started.

  • AD connector Auto Save creating issue

    Hi everyone,
    i have integrated my AD with OIM 9.1 on jboss. All is working fine. I am able to provision and reconcile the user. But As soon as i enable the autosave option under process definition and then assign the AD resource to any user , create user task getting rejected with exception "java.lang.classCastException. Java.lang.String cannot cast to Java.lang.boolean thrown by adapter "ADCS Create User". While if i unchecked the "Auto Save" option under process definition same is working fine. After unchecking the auto save option i am not putting any value. All the values are pre-populated automatically using pre-pop adapters so any possibility of submitted data (to ADCS Create User) mismatch is not the reason. I have tried it 2 instances and both are showing the same behaviour :(

    You need to provide default values for your checkboxes with a 0 or a 1.
    -Kevin

  • Auto save when scheduling shut down?

    Is there a script or application that would allow me to have every program save and close before the system automatically shuts down when scheduled in energy saver?
    I work for at a video production studio and we often have to leave the computers on over night to transcode, render or export.
    Is it possible for running programs such as final cut pro, compressor, and dvd studio pro to auto save when closing during scheduled automatic shut down?

    Sounds to me like scheduled shut down in your environment is not ideal. Why not just let the machines remain on? They'll go to sleep normally (unless you've disabled that) once all activity is done, and sleep mode uses very little power.

  • Auto Save & OS X Server Group Folders

    I just discovered that auto save enabled applications like Text Edit cannot save to /Groups directories on OS X Server. 
    I have two local users David and Celia that are members of the local group davidendcelia. This group has the group directory /Groups/davidandceilia. All members of the group are able to save and edit files in the group folder regardless of who created the file. This is just what is wanted. It is not possible to save a file with Text Edit into the group directory. When you try to navigate to the group directory it is not accessible.
    The /Users/Shared file will work with Text Edit, but it does not allow one user to edit a file created by another user.
    Is there a way to make the group folders work with auto save enabled applications?
    These are the permissions on the file.
    imac10:Users Jeff$ pwd
    /Users
    imac10:Users Jeff$ ls -l
    total 0
    drwxr-xr-x+ 29 Jeff   staff     986 Jan 31 15:43 Jeff
    drwxrwxrwt   8 root   wheel     272 Feb  5 19:40 Shared
    drwxr-xr-x+ 13 celia  _amavisd  442 Feb  2 19:58 celia
    drwxr-xr-x+ 20 david  staff     680 Feb  2 19:45 david
    imac10:Groups Jeff$ pwd
    /Groups
    imac10:Groups Jeff$ ls -l
    total 0
    drwxrwx---@ 9 root  admin  306 Feb  5 19:30 davidandcelia
    drwxrwx---+ 2 root  admin   68 Jan 31 21:01 workgroup
    imac10:Groups Jeff$ ls -l

    Every search page also has an RSS feed, so doing a search for "" will get you a list of all pages sorted by last modified date (change the sort order if you like). That search page will contain your preferred RSS feed.

  • Auto save is making Premiere crash

    Working off of CS6 on a Mac, with a project I've been working with on for nearly a year now off an external drive. Recently, as soon as  an autosave (set for intervals of 20 minutes) begins, the project just stalls, no progress on the autosave bar, and the project will eventually crash, sometimes with the warning that there is low memory. The memory problem makes no sense, there should be plenty of RAM as well as storage on both the desktop as well as the external drive. Nothing has changed in the folder structure of my project, including the autosave folder which is in the same location as my project file. Seeing as how that folder was how it was set up so long ago, and it has only recently begun proving a problem for my project, I'm at a loss for what could possibly be causing this problem. If anyone could offer some ideas, it would be truly appreciated.

    Might not be of assistance, but I know occasionally projects start taking up so much space they become an issue. So you might check your cache locations (displayed in the various preference dialogs) and also your auto-saves. If you've got more than the last few, I'd suggest going in and deleting a bunch of them. Carefully, might say take 2 of each group of 3 at first.
    Also ... several folks have found that routinely clearing all cache files helps keep drives usable ... as they build up clutter, and they will ... you start getting to a point where there's slowdowns occurring simply because of stuff-bloat on the drives. Always keeping any drive in your video "chain" below 50% "occupancy" is wise.
    Just ... something that might help.
    Neil

  • OS X Lion-specific features (Versions, Auto-Save, Fullscreen)

    Why have these not been implemented? Okay, there is Adobe's own version of Auto-Save, and fullscreen is there too (but not in Apple's way where you can use the app as a space).
    Versions is the most wanted feature. Is it possible for Adobe to integrate these OS X specific features in the new Photoshop?

    I thought I'd take a moment to outline OS X's fullscreen mode in relation to Photoshop's Full Screen Modes and explain why we stuck with our Full Screen Mode in the near term:
    Here's the short story:
    If we replace Photoshop's Full Screen mode with the native 10.7 full screen mode, then our users will loose the following functionality:
    The ability to use multiple displays while in fullscreen mode
    The ability to switch between different document windows while in fullscreen mode
    This in not something our long time users have said they want to give up.
    That said, we're pretty excited about full screen mode in Lion like you guys are, and it's possible that Apple may change the full screen mode in OS X in the future to include this functionality in the future – and we'll continue to evaluate if it meets all our users needs.
    Here's the longer story with more details:
    Photoshop's full screen model is a per display mode. This means that in multi-displays configurations, some displays may be in Full Screen Mode while others are not. Photoshop's full screen display can can also contain one or more document windows. When a display is in Full Screen Mode, then all document-windows on that display will be full screen when they are brought forward. Photoshop's model has two full screen modes: Full Screen with UI (including the OSX menu bar) and Full Screen without UI (in this mode the OSX menu bar is hidden).
    The native full screen implementation in OS X 10.7 is a single display mode. When you enter fullscreen mode on a given display, then all other displays become dark (and windows are hidden on dark displays). Dark displays can contain UI for the active application (but not documents).
    When you enter the OSX fullscreen mode, then a new (temporary) Space is created for the fullscreen window. Only a single document window lives in this new Space. This means that you cannot switch between different document windows while in fullscreen mode (command-tilde does nothing).
    Here's the definitive/first post on Full Screen mode: http://forums.adobe.com/message/4282217#4282217

  • Composing: turn auto save drafts off?

    the title says it all: is it possible to turn auto save of Drafts off during composing? I often end up with multiple copies that have to be deleted manually later, and most of the time, I don't even need Drafts to be saved.
    I just want a draft to be made/saved whenever I hit the button. NOT every 20 seconds.

    I have the same problem, did you find a solution?

Maybe you are looking for