Tricking Lightroom into working on a Network?

[joshmcculloch]

I've recently added a staff member, and wanted to make them be able to access my Lightroom Catalog across the network.  I realize that Lightroom does not allow you to store catalog files on a network/removable drive, so I've been looking for workarounds...  I recently employed this option (see below) for syncing my iCal and address Book across multiple Macs, so I was wondering if this might work...:

In Terminal (Mac, of course), using the ln (link file) command, I typed:

ln -s /Volumes/Working_Files/Image\ Related/Lightroom\ Catalogs/ /Users/joshmcculloch/Pictures/Lightroom

The ln -s command makes the linked file, the first directory (/Volumes/Working_Files/Image\ Related/Lightroom\ Catalogs/) directs where the linked file looks, the second part (/Users/joshmcculloch/Pictures/Lightroom) createds the linked folder.

Currently copying my catalog to the network volume, then will launch Lightroom and see what happens...

Well, scratch that.  Somehow, Lightroom knows it is really being stored on a network volume, as it still gives a warning stating that it cannot open the catalog as it is on a network volume.  Anyone know a way to make LR work across multiple computers sharing one catalog?

Cheers, Josh

[johnbeardy]

Josh,

Do you know why it doesn't work on a network? It's not because Adobe are being mean but because SQLite isn't a proper multi-user database with user level record locking like SQL Server or Oracle, and there's enough of a risk that multi-user access will introduce corruption of some sort. If you are going to do this, also spend a bit of time telling Adobe you'd like proper multi-user network access.

You might be better off looking at options such as Export as Catalog, and Import from Catalog, or at maintaining separate databases, storing the pictures on the network, and using Cmd S and Read Metadata.

John

[joshmcculloch]

Hey John,

Thanks for your quick response!

I had read a bit on the background of the issue before, but haven't yet told Adobe what I'd like, so I'll make sure to do that.  Thanks for the reminder and the refresher.

Thanks for the options on various ways to make this work.  What I use Lightroom for mainly is my Working files (ingested files), which I keep track of at their various stages of processing from import to DNG creation.  After DNG's are made, I use EM2 to catalog everything and go from there.  I physically move the files in Lightroom's "Folders" area as they progress through the various stages of processing, will the Cmd S and Read Metadata function also be able to keep track of where the files are located, or will I need to always be using the "Find Missing Files" function to re-link files to their proper folders?

It seems as though the Cmd S and Read Metadata would be much faster that using the Export to and Import From function, am I correct?

Cheers, Josh

[roberte]

Hi Josh,

It seems as though the Cmd S and Read Metadata would be much faster that using the Export to and Import From function, am I correct?

That's how I implement a shared Lightroom workflow. LR Catalogs live on each users machine and the images are on a server. Use folders to indicate what stage of the workflow each job is at like Peter outlines in the DAM Book. e.g.

1. Sort
2. Develop
3. Burn
4. Archive

Not only must you sync metadata but you need to reset paths if someone else move the job to a different folder. It takes a lot of disicipline for photographers to make sure they don't double up on the work and develop the same job twice. In the end it may be easier to use Bridge CS3 + Rapid Fixer because there is no need to reset paths or sync metadata.

-- Robert Edwards.

[joshmcculloch]

Hi Robert,

Thanks for the info, and the note about resetting paths for moved folders.  Lightroom had so much going for it, but this is a major setback!  I recently switched from Bridge CS3 to LR2, but may have to re-think that...  Errr!

Anyone used Bridge CS4?  I always had problems with High Quality previews in Bridge CS3 not rendering properly, or slowing Bridge down to the point of being unusable.  I eventually disabled this feature, but then I could not check image sharpness from Bridge, and had to open masses of images in ACR to double check sharpness...

Cheers, Josh

[johnbeardy]

If you have discrete jobs, the Export/Import approach lets you transfer the job with all its structure - any stacking, collections, virtual copies. It also includes history, if that's of any use. And the other thing is that you can choose to include the originals (the "negatives", prob not needed if they're on the network) and any previews which can save time as well as let you do draft prints. So this approach does more and is worth testing out.

There's also a preference for automatically writing out the metadata, so so Cmd S, but you'd still have to do a Read Metadata.

John

[peterkrogh]

Robert and John right on track as always.

As to Josh's question about CS4, yes, they've really done great work with it.  It can be very fast to work with, and the addition of forcing a 100% cache has really increased speed for quick edits.

Add RapidFixer and you've nearly got the shot-prep part of Lightroom all inside Bridge.

Peter