Known Participant

Question

Catalogue Management

Forum|Forum|8 years ago
February 9, 2018
4 replies
1477 views

So I now own a new pc, a small NUC Skull Canyon. I opted to go with a 250gb ssd and connect external HDD's up to it (or turn their switch on) when wanting to access the brunt of my data (12tb+). I didn't see the merit in having a 500gb or even 1tb ssd, as eventually the data/images/pics/files are going to have to be passed off onto cheaper HDD's (that I already own).

I'm now currently trying to figure out my workflow, from the moment the sd card is ejected from the dslr to importing and exporting images.

I can easily keep a nice 100gb 'buffer' reserve on this 250gb ssd C: for importing and editing (I'll imagine I'll have the fastest and smoothest experience doing this), but I'm a little shakey how the exporting is going to work. Do I export to the HDD's? I could do that, but I won't always have the HDD's switch on (they are in a vantec quad dock, self powered with a fan, sometimes a noisy thing which I don't want to have on all the time). Partially the decision to move to a NUC was the realisation that I seldom accessed the HDD's in my old noisy desktop machine, thus far I am enjoying the peace and quiet.

Initially I will copy files from the sd card to the main C: ssd. I will edit and export to this same drive I think, only when I near the 100gb threshold will I start moving the files off the C: and to somewhere else (should be a good month or two before needing to shift 100gb worth of RAW and Jpg Exports). That should give me the time I need if I ever need to go back to LR and edit a pic taken a few weeks past (which I've had to do on the odd occasion).

But what about long term... can LR's catalogue point to two locations? So in the event I want to retrieve and tweak a picture from 6 months passed (raw file and jpg no longer living on the internal SSD, therefore the Library won't be able to locate it 'missing file' etc), can it find the same file name if I point LR to check on another drive also (like the external hdd, switched on obviously)?

Failing that I might have to rethink about LR being used as a 'library catalogue' system and treat as a standalone editor.

If going down this route, can you;

a) Make LR work a little faster, turn off the Library Catalogue features?

b) When it comes to Export time, could I export a Jpg of the edit (which i normally do) as well as simultaneously exporting a RAW/DNG of the edit (so that if I import that same DNG export again, LR can see the adjustments I made? Or are they all reset?

Hmm... what do other people do in these circumstances?

TIA!

This topic has been closed for replies.

JP Hess

Inspiring

It is not possible to turn off the Lightroom "catalog feature" because the catalog is literally the only file that Lightroom opens. It is the center, the central file of the Lightroom system. Without a catalog, Lightroom cannot function. Everything you do using Lightroom is stored in that catalog. Your images are simply stored in folders on your computer. When you import images into Lightroom, essentially all you are doing is adding those images as records and the Lightroom catalog, which is a database. Lightroom does not make any changes directly to the images on your computer. All changes, adjustments, keywords, are simply information that is stored in the catalog. In order to have an image that includes all of the things you have done to it in Lightroom, it is necessary to export a copy.

dj_paige

Legend

But what about long term... can LR's catalogue point to two locations? So in the event I want to retrieve and tweak a picture from 6 months passed (raw file and jpg no longer living on the internal SSD, therefore the Library won't be able to locate it 'missing file' etc), can it find the same file name if I point LR to check on another drive also (like the external hdd, switched on obviously)?

Yes, Lightroom can point to photos on multiple drives.

The photos now on your SSD can be moved to another drive via Adobe Lightroom - Find moved or missing files and folders (see the section "Part 2 — Updating Folder Location").

As stated above by Just Shoot Me , don't put your photos on the SSD in the first place. Put them on the external drive straight out of the camera.

Failing that I might have to rethink about LR being used as a 'library catalogue' system and treat as a standalone editor.
If going down this route, can you;
a) Make LR work a little faster, turn off the Library Catalogue features?

You cannot make LR work faster by turning off the Library. It is not possible to turn off the Library. Library has no influence on the speed of other Lightroom modules, such as editing. The whole idea makes no sense. If you are having speed problems with Lightroom, you need to describe in detail exactly what actions are slow in Lightroom.

b) When it comes to Export time, could I export a Jpg of the edit (which i normally do) as well as simultaneously exporting a RAW/DNG of the edit (so that if I import that same DNG export again, LR can see the adjustments I made? Or are they all reset?

This is unnecessary extra work, and a horrible workflow. As stated above, put the photos on the external drive straight out of the camera, and then none of this is necessary.

dunker56Author

Known Participant

dj_paige wrote
But what about long term... can LR's catalogue point to two locations? So in the event I want to retrieve and tweak a picture from 6 months passed (raw file and jpg no longer living on the internal SSD, therefore the Library won't be able to locate it 'missing file' etc), can it find the same file name if I point LR to check on another drive also (like the external hdd, switched on obviously)?
Yes, Lightroom can point to photos on multiple drives.
The photos now on your SSD can be moved to another drive via Adobe Lightroom - Find moved or missing files and folders (see the section "Part 2 — Updating Folder Location").
As stated above by https://forums.adobe.com/people/Just+Shoot+Me , don't put your photos on the SSD in the first place. Put them on the external drive straight out of the camera.
Failing that I might have to rethink about LR being used as a 'library catalogue' system and treat as a standalone editor.
If going down this route, can you;
a) Make LR work a little faster, turn off the Library Catalogue features?
You cannot make LR work faster by turning off the Library. It is not possible to turn off the Library. Library has no influence on the speed of other Lightroom modules, such as editing. The whole idea makes no sense. If you are having speed problems with Lightroom, you need to describe in detail exactly what actions are slow in Lightroom.
b) When it comes to Export time, could I export a Jpg of the edit (which i normally do) as well as simultaneously exporting a RAW/DNG of the edit (so that if I import that same DNG export again, LR can see the adjustments I made? Or are they all reset?
This is unnecessary extra work, and a horrible workflow. As stated above, put the photos on the external drive straight out of the camera, and then none of this is necessary.

Thanks for that.

Ok so first off I won't be adding the files from the camera straight onto the external disks, for two reasons;

1) Speed. I'm no techy but I am imagining having the raw files on the internal ssd (960 evo NVMe 250gb M2) will be a faster and smoother editing process than through USB 3 to HDDs. I could of course be completely wrong, that in reality there is no efficiency by having the files on the same disk as LR, as I said I'm no techy, I'm basing this on perhaps 'old days' mentality and I am not wholly up to date with todays tech.

2) And now for the more important reason, noise and hassle. I photograph often, EOD sometimes, and the Quad Dock is similar in size and noise (from its fans) as a small desktop pc. I bought a small NUC Skull Canyon PC to try and move away from having a constant whirring away of a fan right next to me, to integrate and use the Quad dock on such frequent basis I think really defeats the purpose of the NUC SC. I of course understand the logic in suggesting it, it wouldn't be an issue to others and perhaps a younger version of me, but right now that's not what I want the Dock to be doing. I want the Dock to be in RAID and then once a week or fortnight it's turned on and stuff migrated off the internal SSD (to create space once again) and onto that.

Now as for my ludicrous idea of using LR without a catalog, that train of though stemmed from a 'slowed' down process in many regards to some other stand alone apps I have used, in various ways of which I'll try and explain briefly. My thinking was when it actually came to the Develop modue, that part was fluid, it's everything else that's kinda slowish, so was kinda wondering if there was a 'Develop only' mode to LR, but of course not and I see why now.

But perhaps someone can suggest ways to help make my workflow process quicker (from a LR only perspective);

1) First thing is the import, and then loupe mode and start the culling. I've watched a few youtube tutorials on this, what I'm finding is the process when marking/tagging a file (x or p) is slow and laggy unless I build previews. That 1:1 preview building takes quite a lot of time, I haven't yet tried building any other preview mode, but considering I am buidling previews only with the intention of culling (just so i can zoom in, see if the parts I meant to be are sharp and in focus etc or not), it feels like a slow process. Considering I could fire up something like Faststone and not have that lag and build preview time... so at this point in time I'm not sure if I abandon LR from the culling process entirely or not.

2) What i've noticed is the larger the catalog the longer times to load LR and performance in general. LR from my experience works better if restarted after an hour or so, and where possible deleting files from the library and keeping the library picture count down.

These two things made me ask about a 'lighter' version of LR, standalone editor etc, but I have the answer to that question. Use Bridge>Camera RAW>PS if going down that route.

Where I need help now (I think), is if I can get away with quicker preview build times (perhaps I don't really need 1:1 previews, especially considering the majority of these files will get culled) and then also once I have migrated the exported Jpgs and initial RAW files from their original location on the SSD (lets say it's 'C:\Users\xxxx\Pictures\Pentax In' for import and 'C:\Users\xxxx\Pictures\Pentax Out' for export), once these files have been moved from here to the external hdd, how do I tell LR to still 'see' them, so that if say in 2 months time I do need to go back and reedit (turn on the external hdd) LR can see the file (with the last adjustments made) and I can edit?

fwiw there shouldn't be an instance where the same file exists in two locations at once. I will be 'Moving' the file to the external hdd, not copying.

dunker56Author

Known Participant

Do you mean if you import to the external hard drive? But yes, as soon as you import to the external hard drive that folder on the external hard drive will be added to the library. I suppose it would add exports as well as long as you are adding them to your catalog. That's something I usually don't do.

JimHess wrote
Do you mean if you import to the external hard drive? But yes, as soon as you import to the external hard drive that folder on the external hard drive will be added to the library. I suppose it would add exports as well as long as you are adding them to your catalog. That's something I usually don't do.

Bit confused here, typically you import from not to?

I'm meaning I will only ever import from the internal ssd (ideally), I will also export to the same internal ssd. Yet when I have moved the files to another HDD, how can I get LR to keep track of that 'move' (without having to clear the library and re add manually all over again).

I think much of the confusion here stems from the part that LR does not automatically/watch and import files from a directory, you have to manually do it. You can't tell it to watch 'x' folder and if it fills up with files add them to the library. And if the current library has files missing, then remove them etc.
Lots of other software, file sharing/streaming software for example might ask for directories where they 'watch' and any content added ore remove from that is reflected in the programs library. I'm kinda hoping LR would be like this, it notices the files are no longer on C: but is keeping an eye on F: and can see the same filenames etc so they still are accessible (of course provided the external hdd is turned on).

The computer i have has a direct SD card reader, I would like to input the card from the camera into the SD Card on the NUC, set it to 'automatically import' when I do that, or copy the contents from the sd card over to the internal ssd, get LR to import the files from there, do the cull, do the edit, do the export (same drive), and have them sitting there for awhile before transferring (move not copy) the files off the ssd to an external. I want to do this as I edit and photograph often, but I do not want the whirr and noise and hassle of turning on additional computing equipment, if I wanted fan noise all day I would just stay with a desktop tower and have the hdd's housed inside.

I think I'm just going to have to do some testing with LR...

Just Shoot Me

Legend

Import directly to the external drive. Export to that same external drive.

Keep the catalog on the SSD. That will mean the Previews will also be on the SSD.

If I was doing this I would get a 500GB SSD. The more free space you have on a SSD the longer that SSD will last.

Conrad_C

Community Expert

dunker56 wrote
But what about long term... can LR's catalogue point to two locations? So in the event I want to retrieve and tweak a picture from 6 months passed (raw file and jpg no longer living on the internal SSD, therefore the Library won't be able to locate it 'missing file' etc), can it find the same file name if I point LR to check on another drive also (like the external hdd, switched on obviously)?

That shouldn't be problem. Lightroom can manage multiple volumes. I don't know if there's a limit, but my Lightroom catalog points to images on several internal drives on my tower computer, external hard drives, other computers on the network…and it's no problem to move images between those volumes, within Lightroom.

There may be a minor issue in Windows, where Lightroom might become confused when drive letters become associated with different volumes than they were previously. I think the solution is to permanently assign drive letters, but I'm not sure because I'm using Lightroom on a Mac where this issue doesn't come up because drive letters aren't used.

dunker56 wrote
Failing that I might have to rethink about LR being used as a 'library catalogue' system and treat as a standalone editor.
If going down this route, can you;
a) Make LR work a little faster, turn off the Library Catalogue features?

Since cataloging (that is, generating an image preview and adding its data to the database) is never optional and cannot be turned off, you won't save time on an image by image basis. The only time savings would come from cataloging a few images you want to edit, instead of hundreds you want to organize.

If you're only interested in the Develop module in Lightroom, and you're a Creative Cloud member, you can download Adobe Bridge, use it as a no-catalog file browser to browse your images, and open them into Adobe Camera Raw inside Bridge to do your raw editing. The raw editing options inside Adobe Camera Raw as basically the same as in the Lightroom develop module.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded