Will this hybrid workflow work? -- LrCC and Lr Classic
I'm a long time (amateur) user of Lr Classic, but keeping my eye on Adobe's direction with cloud based LrCC. From what I've read, LrCC is aimed at casual photographers. I think Adobe will continue to grow LrCC towards that demographic rather than professionals or serious amateurs. So I'm doubtful that LrCC will move toward providing the in-depth capabilities of Lr Classic, but I can be hopeful meanwhile.
But lately I'm spending quite some time looking into LrCC. I understand the repeated warnings to not try to go forward syncing between LrCC and Lr Classic. It looks possible, but lots of knowledgeable people warn against it. OK, I'll try to not go there for now.
My drivers for looking at LrCC are:
- for use while traveling -- to review, cull and perhaps make initial edits. I currently don't/won't travel with a laptop PC. I will often take an iPad.
- increase the ease of creating albums for my wife to have on her iPhone/iPad -- e.g. grandkids or vacations. LrCC still seems barely OK for exporting for this purpose, but I can learn to make it work.
My drivers for staying connected with Lr Classic are:
- ease & familiarity with editing photos while sitting at my desktop PC
- strong path to preparing and exporting photos for printing and for LCD screen frames
- probably several things I don't yet realize I like in Lr Classic but can't do in LrCC.
That said, I'm thinking of the following workflow approach -
- Migrate Lr Classic catalog to LrCC, just so "it's all there" and to open possible learning with known photos I already have.
- Do only minor editing in LrCC. Use my desktop PC for this mostly because its easier than trying to use a touch screen iPad to edit
- When I'm ready for in-depth editing of a set of photos, export the full size RAW files to my PC, import them into Lr Classic and proceed -- (not trying to use syncing).
- Use Lr Classic for exporting with in-depth control of export dimensions, jpg quality, dpi control and destination folder or online print service -- (all almost unavailable in LrCC)
Does this sound reasonable? Any pitfalls I'm not seeing yet?