Best strategy transitioning from LR to CO
Pretty sure this topic has been beat to death, but all I can find is "how to do it this way" info, not really much in the way of "why should I do it this way" advice.
I'm transitioning from LR to CO as my "master" processing app. I am not eliminating LR, and like its DAM and printing approaches, and also that I can edit using outside apps from within LR. But I would like CO to be the primary intake and PP app. If all I had to do to transition was to switch ingesting strategies, I would probably use CO's sessions concept as it works for me. But what about my 30,000 photo catalog?
I have all my masters stored on a (well backed up) SSD, and that's where I put things when I bring them into LR. Then I have a LR catalog on the same drive, which is what LR accesses when it opens. All of my edits to old photos are in my LR catalog, so I don't want to have to redo all of that work. But I also don't want to create a duplicate db of master photos.
I'd like to have a solid CO database and folder, so I don't want to just use it as an external editor, accessing from LR.
1.Should I create one massive CO catalog and reference the masters? If I do that, then I won't have the LR edits.
2.Or should I use "sessions" and bring events into CO gradually? But then how do my old LR edits get incorporated?
3.And if I use "sessions," how do I get my new photos going forward into there LR db?
4.Is there a way to use the "referencing" concept from Aperture to get CO to recognize LR edits while still leaving the master in the main master folder?
I'm certain that I'm over thinking it, and that there is a very simple answer right under my nose.
Tks
I'm transitioning from LR to CO as my "master" processing app. I am not eliminating LR, and like its DAM and printing approaches, and also that I can edit using outside apps from within LR. But I would like CO to be the primary intake and PP app. If all I had to do to transition was to switch ingesting strategies, I would probably use CO's sessions concept as it works for me. But what about my 30,000 photo catalog?
I have all my masters stored on a (well backed up) SSD, and that's where I put things when I bring them into LR. Then I have a LR catalog on the same drive, which is what LR accesses when it opens. All of my edits to old photos are in my LR catalog, so I don't want to have to redo all of that work. But I also don't want to create a duplicate db of master photos.
I'd like to have a solid CO database and folder, so I don't want to just use it as an external editor, accessing from LR.
1.Should I create one massive CO catalog and reference the masters? If I do that, then I won't have the LR edits.
2.Or should I use "sessions" and bring events into CO gradually? But then how do my old LR edits get incorporated?
3.And if I use "sessions," how do I get my new photos going forward into there LR db?
4.Is there a way to use the "referencing" concept from Aperture to get CO to recognize LR edits while still leaving the master in the main master folder?
I'm certain that I'm over thinking it, and that there is a very simple answer right under my nose.
Tks
0
-
I don't know that there is a simple answer. If you want to use both LR & CO you'll have to make some compromises to your workflow. The only way to view your LR edits in CO is to export them out of LR as TIFF, JPG, etc. And same goes for viewing CO edits in LR.
You could make an "output directory" where you export TIFF's to from both programs then which ever program you reference the TIFF's with you'll see the other programs edits and can make further adjustments. You'll loose the ability to be working directly on the RAW file but this is essentially what is done when you're exporting to photoshop (unless your using smart objects).
I use both programs myself. I've been using LR for many years and have a giant catalog with no plans to transfer it to CO. CO is my tethered capture tool of choice and I work in sessions. Sometimes I'll keep the shoot in the CO session for processing and other times I'll import the session into LR and do the post work there. It just depends on which program is better equipped/more convenient for the particular job I'm working on.0
Post ist für Kommentare geschlossen.
Kommentare
1 Kommentar