Running multiple instances on the same PC

[DavePinMinn]

Windows 10 Pro 64-bit PC

I saw other topics on this, but it sounded like they all wanted to be in the SAME catalog...

I'd like to run two instances but have DIFFERENT catalogs open......  Right this moment I have the "short-term" (where the culling gets done so I don't end up with a huge number of garbage images in the "second copy" location) catalog building previews.  It's going to take a LONG while.  While that's happening I'd like to be in the FER-REAL "images" catalog doing other stuff rather than be at a dead stop for an hour or more while Lightroom is building 1:1 previews on new images.

Is there a simple way to do this?

[dj_paige]

You can have only one catalog open with Lightroom. You could install Lightroom twice for two different users, but I believe the license does not allow both of them to be open at the same time.

So... no dice. However:

Lightroom has a feature that allows fast culling without having to wait to build 1:1 previews. From what I have read (I don't really have the need to do it myself), it comes close to what Photomechanic provides. Why don't you try it? https://www.focusphotoschool.com/adobe-photoshop-lightroom-classic/module-2-importing-getting-photos...

[DavePinMinn]

I've used the embedded previews.  They're probably fine if you're not looking critically, but they're worthless for examining images at 1:1 for making final decisions about critical focus.  At the moment, the only way I've found to check critical focus on a dragonfly's eye shot from 10 feet with a 600mm lens is a fer-real 1:1 preview in Develop mode...

[dj_paige]

At the moment, the only way I've found to check critical focus on a dragonfly's eye shot from 10 feet with a 600mm lens is a fer-real 1:1 preview in Develop mode...

If you need that level of detail then the Develop module is the only way I know of. Too bad you didn't state this need in the first message of this thread, we could have saved some time.

[DavePinMinn]

Thus the running of more than one instance so the previews could be created in the "short term" catalog for culling, while I did other things in the "regular" catalog...

[Todd Shaner]

DavePinMinn  wrote

I've used the embedded previews.  They're probably fine if you're not looking critically, but they're worthless for examining images at 1:1 for making final decisions about critical focus.

What camera model. Canon and Nikon have full-size previews embedded in the raw file. For other camera models you can shoot JPEG + Raw with the below option checked in LR Preferences. When done culling simply delete all of the JPEG files.

[cmgap]

Do you have to build 1:1 previews upon import? Why not reduce import time and use Standard? Once you've culled and identified images you want to promote for editing you can build a smart preview? You'll also reduce the size of the previews database.

[DavePinMinn]

The cameras will be any (or all) of a Nikon D500, D7200 and/or D850.  Typically, situations where I end up with a lot of images it'll be the D500 and/or the D850.  Presuming they have the full-size previews in the raw file, is that what Lightroom is using for the embedded previews? 

As for previews, that's essentially what I currently do...  On import into the short-term catalog I build standard previews.  Throw out the stuff that's truly wretched - figure half the images are so bad it's clear they're garbage.  But if I've been out shooting birds or butterflies or an Air Show or something else that generates a lot of images, that will still leave me 4 - 500 images (or on occasion a couple thousand) for which I want 1:1 previews.

Which is a very slow process.  And I can't do anything else in Lightroom which they're getting created.

Since my fer-real image catalog is separate from where all that's going on, it would be really convenient if I could have an instance of Lightroom open that catalog so I could do stuff.  But, it sounds like Lightroom won't allow such a thing, even in a separate catalog.

It's generally not a big deal, just something that would make my workflow more productive.

[Todd Shaner]

DavePinMinn  wrote

The cameras will be any (or all) of a Nikon D500, D7200 and/or D850.  Typically, situations where I end up with a lot of images it'll be the D500 and/or the D850.  Presuming they have the full-size previews in the raw file, is that what Lightroom is using for the embedded previews?

Yes. All of those Nikon DSLR models you mention have full-size JPEG previews embedded in the NEF raw file. Using the below Import module 'Build Previews' setting allows you to view the NEF at 1:1 Zoom view in the Library module without having to build 1:1 Previews. Keep in mind if you switch to the Develop module and apply any edits BEFORE the culling process is completed LR will automatically build 1:1 previews when switching back to the Library module. This will slow down your culling process–DON'T DO THAT! Remain in the Library module until you have reviewed and culled your image files for editing.

[DavePinMinn]

Let me confirm this'll work with what I normally do.  Currently when I import I apply a copyright, and use an import preset to adjust baseline noise reduction, exposure and such, and set the profile.  That way when I do the initial examination I'm looking at images that are (hopefully) adjusted so they look reasonably "normal".  Is that going to work with the embedded previews or will the adjustments DURING import mess up the embedded previews?

[Todd Shaner]

DavePinMinn  wrote

Currently when I import I apply a copyright, and use an import preset to adjust baseline noise reduction, exposure and such, and set the profile.  That way when I do the initial examination I'm looking at images that are (hopefully) adjusted so they look reasonably "normal".

The Embedded & Sidecar Import workflow shows the camera's embedded JPEG preview in the Library module. So it will show the picture style, sharpening, and noise reduction settings you have applied in the camera. Set those so the JPEG preview appears similar to the raw file with your default Develop settings or what ever you use in your preset for initial import.

DavePinMinn  wrote

Is that going to work with the embedded previews or will the adjustments DURING import mess up the embedded previews?

That will work if you stay in the Library module and don't change any settings in the Develop module after import.