Does moving to LR CC/Classic mean losing my standalone version?

[luxborealis]

I have LR 6.6 stand-alone. I’m reticent to drink the Adobe Kool-Aid, but am also looking to the future. Since I teach workshops and do presentations, I want to stay current. So, despite my initial “Adobe can kiss my ...” comment, and the fact that I abhore the subs model, it looks like I don’t really have a choice.

So, will LR CC over-write my standalone version of CC (just in case I have a change of heart six months or a year down the line)? I’ve scoured the ‘net for an answer, but, given the confusion over what was LR CC and what LR CC is now, searches are coming up blank.

[Leszek Piotrowski]

Terry,.. I'm with you,... but I do not have a business to support,.. but I do care a lot about my LR SQL database that records my precious images.  So,.. If you can find out how the SQL LR Database is maintained going forward thru all these "LR upgrades/new/???  ",... It would be much appreciated.. I'm on LR 6.12,... so far all is good,.... for how long ,... time will tell.

[pearlstreet]

Why not change the lame of your current Lightroom.exe (or whatever it's called) to something else when you install the new stuff? Wouldn't that prevent an overwrite?

[john beardsworth]

I have LR 6.6 stand-alone. I’m reticent to drink the Adobe Kool-Aid, but am also looking to the future. Since I teach workshops and do presentations, I want to stay current. So, despite my initial “Adobe can kiss my ...” comment, and the fact that I abhore the subs model, it looks like I don’t really have a choice.

So, will LR CC over-write my standalone version of CC (just in case I have a change of heart six months or a year down the line)? I’ve scoured the ‘net for an answer, but, given the confusion over what was LR CC and what LR CC is now, searches are coming up blank.

The answer is no. However, it's never so simple, partly because Adobe make it difficult to know exactly what you are asking.

LRCC is generally being used for the brand new PC/Mac application Lightroom CC. But what you have been using before is now called Lightroom "Classic" or LR7.

Let's assume you mean to stay "Classic". When you install "Classic", the installation via Adobe's CC app defaults to removing previous versions. The Advanced Options let you keep them. When you open a LR6.6 catalogue, "Classic" makes a copy of it and upgrades the copy, which is good. It also appropriates its previews folder. If you want the LR6.6 catalogue to keep its previews folder, temporarily rename it before upgrading. This forces LR7 to build its own previews folder, which is what I prefer (preview generation is much faster in LR7).

But if we assume you do mean LRCC, the new desktop app, it installs separately and does not take over any existing content. It will populate collections / albums from smart previews that you may have synced to Adobe's cloud. There is a File > Migrate Catalog command which allows you to import a LR6/7 catalogue. You would use this if you wanted that catalogue's contents in LRCC, which will sync originals to the cloud. Because LRCC is now managing your originals and syncing them, Migrate Catalog also disables the LR6/7 catalogue's ability to sync. Personally, I won't do Migrate Catalog - I don't want my originals in the cloud, and am happy using LRCC as "Lightroom Mobile on my laptop".

A lot of detail there - hope it answers your questions.

John

[Alan Goldhammer]

Let's assume you mean to stay "Classic". When you install "Classic", the installation via Adobe's CC app defaults to removing previous versions. The Advanced Options let you keep them. When you open a LR6.6 catalogue, "Classic" makes a copy of it and upgrades the copy, which is good. It also appropriates its previews folder. If you want the LR6.6 catalogue to keep its previews folder, temporarily rename it before upgrading. This forces LR7 to build its own previews folder, which is what I prefer (preview generation is much faster in LR7).

John, I think this is what we are all wrestling with.  I'm also in the same boat and I would not want to have my LR6 removed or my existing catalog that LR6 uses compromised 'if' I update to the new LR Classic.  Is there way to clearly present this installation from removing the 'old' LR6?  The catalogue issue should be easy to deal with by simply renaming it to a new catalogue that LR7 won't import.

[john beardsworth]

John, I think this is what we are all wrestling with.  I'm also in the same boat and I would not want to have my LR6 removed or my existing catalog that LR6 uses compromised 'if' I update to the new LR Classic.  Is there way to clearly present this installation from removing the 'old' LR6?  The catalogue issue should be easy to deal with by simply renaming it to a new catalogue that LR7 won't import.

Yes, Alan, it's all about remembering "by default" and it's not difficult... if you remember. When you press Upgrade in Adobe's CC app, the panel contains a link Advanced Options (Here is the dialog box). One of the options is Remove Old Versions - just uncheck it.

Your existing LR6 catalogue is always safe. LR7 copies it, adding a -2 to the filename, and then converts that new file.

[jrsforums]

Yes, Alan, it's all about remembering "by default" and it's not difficult... if you remember. When you press Upgrade in Adobe's CC app, the panel contains a link Advanced Options (Here is the dialog box). One of the options is Remove Old Versions - just uncheck it.

Your existing LR6 catalogue is always safe. LR7 copies it, adding a -2 to the filename, and then converts that new file.

One additional consideration.  I expect that if you are updating the ‘XMP’ files, you should make sure that, at most, only one catalog does this.

[john beardsworth]

One additional consideration.  I expect that if you are updating the ‘XMP’ files, you should make sure that, at most, only one catalog does this.

Sorry, I don't think XMP files are relevant here.

[jrsforums]

Sorry, I don't think XMP files are relevant here.

Ok, so no worry if both LR6 and Classic are updating the xmp of the same images on the physical database?

[luxborealis]

The answer is no. However, it's never so simple, partly because Adobe make it difficult to know exactly what you are asking.
...
A lot of detail there - hope it answers your questions.

John

Many thanks, John, for clearing that up. This makes sense.

[Hoggy]

There's one area that still remains unclear to me..  If both versions are kept, don't they still use the same appdata folder?  When I upgraded and removed previous versions (mistakenly, in retrospect), it's still showing the use of the same appdata folder.

What would be the ramifications of that?  Or if both versions are kept, does it duplicate the appdata folder for Classic?

[john beardsworth]

They do, but it's no problem. Their preferences files are different, and presets are identical format.