![]() ![]() * leave auto-save-xmp disabled (Lr preference), then save xmp manually after each round of "milestone" photo edits (those you'd hate to have to do over) - call that a "session" I guess. Since processing usually requires several sessions in Lightroom, should I back up after each session or wait until I have finished? Even Lr's preview system I think of as a "last ditch" backup of sorts. I also have hi-quality jpegs (exported with xmp embedded) as a form of backup (in case edits go south or originals are inadvertently deleted). * It won't include xmp sidecars or changed originals.Īnyway, my point is that it's good to have more than one form of backup - archived backups that are never touched may be good, and photo files will be included in complete system backups too, assuming you do those. import date is no longer a very meaningful organization. * It includes all the rejects which should be disposed of. * It's never touched after it's created, so you know those are true originals.īut it's not good as a long term or only backup, because: * It *is* organized by date imported, so you know where to go for files recently imported. * It has all files (even those you deleted on accident, or on purpose but regretfully.). I mean Lr's 2nd copy (note Adobe's avoidance of the term "backup") is an excellent *import* "backup" because: Yeah - "backup" is kindofa nebulous term. I have no connection to Backblaze other than being a very pleased customer. Once that backup completes, I can confidently delete the files from my memory cards. As soon as the new image files appear on my D: drive, Backblaze sees them and starts backing them up to the cloud. Then I do a SyncToy backup (per my drives as described above). After doing an import, I do a quick edit to find the rejects and delete them. Backblaze even saves old versions of files for a month.Īs for having LR make a backup of image files upon import, I agree with Dick that I reject and delete many original RAW files, so there is no need to keep a backup of those. I've used it to retrieve a file or two for clients while I am traveling with no access to my office computer. In addition, I backup the LR catalog and all image files to an external HD, but I only do that from time to time (since Backblaze has a copy of everything).īackblaze is available on the web and also has an iPhone app. Backblaze is set to backup C: and D:, but not E. I use Microsoft SyncToy to backup my LR catalog and all image files to E: (also internal). LR catalog backups, which I do each time LR exits, are also on D. I have my LR catalog on my C: drive (SSD). The initial backup takes several days, but Backblaze works in the background and is completely "invisible" to the user while you work. Again, do not rely on you having the time and remembering to do so.įor the past year or so, I've been using a cloud backup service called Backblaze - It costs fifty bucks a year, about 14c/day, for unlimited storage. ![]() You can use third party software (some of which are free) to accomplish this. You also need to make automatic backups of the photos. I can't really tell you what frequency is best for you I only know what is best for me. In Lightroom, you can set the time period for making backups of the catalog to whatever you feel is appropriate, but I wouldn't go more than a week, and if you do a lot of photography, you might want to back up the catalog every night, or every time Lightroom closes. You need an automated back up methodology, that doesn't depend on you having the time and energy and remembering to make backups. In my opinion, this is not an acceptable way to go. I do not consider exporting or publishing to be backups. Once again, you can load any of these presets into your own photo using the Preset Ripper plugin, either by opening the original XMP files, or by downloading any of these JPEG files below (right click, save as) and opening it in the Preset Ripper plugin.You need to back up BOTH the images and the catalog file, and you need to make sure that the backups are on a different physical disk than the originals. Looks like “Bright” and “Cinematic” are very similar to each other. Following is the list of Lightroom 5 renditions of those presets. There were about 20 interesting presets in addition to Revel presets and non-Lightroom stuff. Loading develop settings from XMP isn’t supported by Lightroom, but Preset Ripper plugin gets the job done. Most of the settings are compatible with Lightroom, and the presets are still stored as XMP files inside their application bundle. Since then, Adobe has revamped their mobile Photoshop Express application, it is now based on the same photo processing pipeline as Revel is. Few months back, I posted how to load Adobe Revel presets into Lightroom. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |