Moving Presets to your Lightroom Catalog

There is this nice little feature in Lightroom that changes where your presets are stored to the location where your LR Catalog is stored.  This will work out much better for how I work, since I have yet to forget to backup my catalog when I setout to rebuild my machine.  My catalog is stored under my documents directory, specifically at: C:\Users\USERNAME\Documents\LR.  Which is a pretty easy location to find and backup.

Changing the default location

1) Open Lightroom
2) From the Menu select Edit > Preferences
3) Select the Presets Tab
4) Within the Location area, select “Store presets with catalog”
5) Select OK to exit the Preferences dialog

If you check the folders where you catalog is stored, you will now have a new folder called Lightroom Settings.

Move Existing Presets

There are a couple of additional steps if you already have Presets configured within Lightroom.  Since it seems that selecting “Store presents with catalog” does not move your existing presets to the new location.  So the quickest way I found to move my existing presets is to open the old present location (remember the nasty AppData path) and copy the contents of the Lightroom folder to your new Lightroom Settings location. 

From this point on you can easily add new presets to Lightroom using your catalog location.  ]]> http://markgroves.us/blog/2008/11/30/storing-lightroom-presets-with-your-catalog/feed/ 0 http://markgroves.us/blog/2008/10/05/photo-backup-my-process/ http://markgroves.us/blog/2008/10/05/photo-backup-my-process/#comments Sun, 05 Oct 2008 08:10:00 +0000 mgroves /post/2008/10/05/Photo-Backup-82113b-My-process.aspx Brian Auer of Epic Edits has a series of articles on this blog discussing the options for ensuring that you don’t lose your photographs due to the various things that can go wrong with a computer hard drive. I thought I would post how I handle this since, as Brian outlines, there are several approaches.

First off, I’m a PC guy, always have been, and don’t see a reason to change now. For catalog management I use Adobe Lightroom 2.0. I have been a big fan of Lightroom and have been using it since the 1.0 betas. Another critical part of my photo backup process is my Windows Home Server. I have a HP MediaSmart Server filled with hard drives.

I do not store any of my photographs on my desktop, all photographs go directly on the Home Server as soon as I transfer them from the Compact Flash cards. Since I don’t have any redundant hard drives on my desktop, its safer in my mind to store everything on the server. Within the Home Server I have a file share called Photos, this share is set to be duplicated within the Home Server so I don’t have to worry about a drive failing and wiping out those files. To make it simple, and to ensure that I don’t accidentally store photographs on my desktop, I map the default pictures user directory in Vista to the photo share on the home server.

To do this find your user directory, within Vista it is usually C:\Users\USER\Pictures. Right click on the folder, select properties. From the properties dialog, select location, type in the location of your network share, \\MACHINENAME\Photos, then hit the move button. This will now set the default picture folder within Vista to the server share, the server does not need to be a Windows Home Server, it just is in my case. Now every program that wants to store or retrieve pictures will by default look in this directory.

Currently I have Lightroom configured to copy into date based folders within the Photos share. This seems to work best for me, since I frequently take shots of various subjects, and trying to come up with folders based on the subject of the photograph was just to difficult, plus that is what keywords are for anyways.

I currently have all four drive bays filled within the HP MediaSmart Server, 2 500GB drives, and 2 750GB drives. I also have a 500GB external USB drive integrated into the storage configuration. One of the nice features of WHS, is the ability to have various drive sizes within the case, and still enable redundancy between drives. I at one point had a server setup with a RAID-5 configuration, it was good for redundancy, but all the drives needed to be the same size, and with hard drive prices dropping all the time I like the ability to upgrade my 500GB for a 1 TB drive when the price drops.

The configuration I outlined above works great for making sure I don’t lose any files within my home network. The one risk is that if something happens at my home, fire, theft, etc. That is why the next point of protection is offsite storage. I currently use KeepValue as my backup provider. KeepVault has a add-in for WHS that automatically backs up any new or changed files to their servers. The KeepVault interface is very simple, you just pick which shares on your home server you would like to be backed up, and it takes care of the rest. KeepVault for WHS is $100 per year for unlimited 100GB of storage. I could not find a better deal, since I backup all my photos, my extensive music collection (re-ripping all those CD’s does not sound fun), and my family videos.

Well I hope this help anyone that are looking for ways to protect their photography. As photographers we like to get the coolest and latest gear, but don’t forget to invest in the backend of your process, and poor backup strategy will be costly.

It is pretty easy to figure out if your sensor need a good cleaning, just take a shot of something like a piece of white paper at f/22, if you have a bunch of dust all over the photograph you may need to clean your sensor. Double check that it is not your lens that needs cleaned, but if you take a few shots with different lens and the spots on the pictures are in the same location you most likely need to clean your lens.

Here is an example of a photo taken with a dirty sensor looks like:

Now these spots can be cleaned up in Photoshop using the healing tool, after awhile it is just best to clean your camera.

I won't bother going through all the steps, since there are great sites out there already going into way more detail then I could, such as CleaningDigitalCameras.com. I do recommend pickup up the correct cleaning supplies at your local camera store, or as I did and purchased a kit from Micro-Tools.

Here is the after shot (I still have a couple spots but much better than the first shot):

Here is an interesting article from CNET on color spaces, I have to admit I did not fully understand the differences between all of the choices within Lightroom. I have been using Lightroom for several months now and really love this application, it is not cheap but then you do get what you pay for.

Adobe Lightroom and color spaces | The Pervasive Datacenter – CNET Blogs

That was my problem. I was exporting to JPEGs with an Adobe RGB color space. Lightroom (like Photoshop and other higher-end imaging programs) understand how to properly display images using that color space on an sRGB monitor. However, neither Firefox nor IrfanView do.

Moral of the story? Although Apple's Safari and the Firefox 3 beta can display non-sRGB color spaces correctly, Microsoft's Internet Explorer and Firefox 2.x don't. Nor do most basic file viewers. Therefore, for most purposes–and certainly for Web display–it's best to use JPEGs with an sRGB color space or the results probably won't be what you expect.

On an additional Lightroom note, with version 1.3 and the new SDK, and thanks to Jeffrey Friedl you can now export directly to SmugMug. Jeffrey is still working through some bugs, but recent versions are starting to work pretty well. Thanks Jeffrey!