LR 1.4 with LR 2?

  • Thread starter Thread starter cadmanmeg
  • Start date Start date
Status
Not open for further replies.
C

cadmanmeg

Guest
So am I correct in what I am reading here and other places is that I can
install LR 2.1 alongside with my LR 1.4 and the 2.1 will not affect my 1.4
at all? Then, once I get comfortable with 2.1 I could go solely on it. I
think I understand that I can also port over some items like setting,
rendered previews, and whatnot? Is this all correct? Any suggestions along
the way with this? Thanks much for the input!
 
You are correct. You can install 2.1 alongside 1.4 quite happily, although I found once on 2 I never used 1.4 apart from doing some speed tests.
 
Not quite so simple, LR2.xx upgrades the catalogs from 1.4 and they cannot be opened by 1.4, However with the upgrade of catalogs the original ones are left in place.
I suggest that you d/load and install 2.1 and create new catalogs until you want to upgrade the old ones.

By the way welcome aboard, fill in your signature please as there are more tios but they are OS dependant.
 
So when it installs, does it also copy over any web templates. prefs, etc...? If not, what is the easiest way to get these over there if I am going to run 1.4 and 2.1 concurrently here? Will all web templates and the like work properly in 2.1 or I sohuld say, should they? Thanks much.
 
So when it installs, does it also copy over any web templates. prefs, etc...? If not, what is the easiest way to get these over there if I am going to run 1.4 and 2.1 concurrently here? Will all web templates and the like work properly in 2.1 or I sohuld say, should they? Thanks much.

They should work concurrently although 3d party and some templates may not. You may have noticed there are threads about new/updated templates for 2 here.
And I do know tat seems double dutch !! LOL
 
I do not recommend doing that. In my case( LR1.3 and 2.'), I had both programs working. Initially, everything looked normal. But, when I went over to develop in LR2, file was not found. Then, I backtracked to the grid. All the thumbnails had question marks. (meaning the links were broken)

So, I followed the procedure to re-establish the links in LR2. When I did that, I broke the links in LR1.3.( question marks appeared) So, I came to the conclusion that both programs are incompatible if you are trying to access the same files. If you have totally different images in LR2, I think you should not have any problems.

Good luck,
Bob
 
Well, yes, Bob is correct, Rule #1 for running both versions.

Don't use the same catalogs and image files with both versions. If that wasn't pointed out above, it certainly should have been.

If you have segregated version 1.x catalogs and image files, from version 2.x catalog and image files, everything will be fine.
 
Okay, so I think I understand now what and how I should go about this. Guess once I get comfortable with 2.1, I can just remove 1.4. So then would there be a particular process of which to port of the catalogs once I reach that level? I think what I will do is remove the link for some folders from 1.4 and then set them folders up for 2.1. These folders are all subdirectories under a master folder I have, but I am thinking that there shouldn't be any problems, right? I mean, how did you all approach this? Am I being overly cautious? See, I never, ever had any issues with any releases of 1.x and don't want to start with issues in 2.x. Any other suggestions on this? Thanks for all of the help thus far!
 
You sound very cautious and that can be a good thing. I suggest that you start off with a new catalog and import some of your folders into that - the ones that you have isolated.
First though, write out the metadata in your LR 1.x catalog with Select All/ Cmd-S.
The difficulty with the cautious approach is that while you can play with the files you won't have carried across flags, collections etc that are catalog specific.
Personally I just upgraded all my catalogs and went for it with only a few issues.
 
Well I got delayed in setting this up and trying it out. Did as recommended above with a whole new pic area and whatnot with seperate catalog, etc... but upon trying to even import from HDD about 25' pics, it crashed not once, but twice. Before it crashed the second time, it did complete the import. I even used the minimal redering option to boot. So for me, I am not sure this is a good idea right now. Am I overlooking something here? I mean, I have had LR1.4 crash on import for me, but not twice in a row and whatnot. Any other suggestions here? Thanks for all the help thus far!
 
to clarify - working backwards V2.1 to V1.4 won't work?

Not quite so simple, LR2.xx upgrades the catalogs from 1.4 and they cannot be opened by 1.4, However with the upgrade of catalogs the original ones are left in place.
I suggest that you d/load and install 2.1 and create new catalogs until you want to upgrade the old ones.

My colleague and I work on a team project - I take the photographs (DNG's) and tweak them in Lightroom to my satisfaction and then export a catalog of those images and give those to her. She does further tweaks to her satisfaction and then uploads them as jpgs to our website. Using this approach - she can work on or change my edits.

Up until recently we have both been using v1.4. I have recently upgraded to v2.1 but she doesn't want to spend the money for the upgrade so still has v1.4. Am I right in thinking that she won't be able to read V2 catalog files and my edits? I guess it has to be that way, since there are new tools e.g. local corrections that are not in v1.4.

Is there a workaround for this, or should I simply burn my changes into the images and export them as tiffs for her to work on?

Alastair
 
I just went through this same process and would agree that there is little reason to keep LR 1.4 once you start using LR 2.1. Upgrading the catalogs is far easier and does preserve all the non-metadata goodies; it saves a lot of time vs recreating everything in LR 2.1.

The most dangerous thing is to save metadata to the same file using both LR 1.4 and 2.1. As mentioned before, if you must keep LR 1.4, you should create separate master files.
 
My problem anymore isn't with what version to use and whatnot, but the fact that I have crashes right from the start isn't a good way to move someone into a new version. Maybe I just need to tweak it some more?
 
It depends on what changes you're making. Most of the data can be saved to the XMP header in the DNG file, which would then appear in her 1.4 catalog when she imported them. Flags, collections, virtual copies and a few other minor bits aren't included in XMP, and 1.4 would just ignore the new tools data that it doesn't recognize.

Peter, what makes you so concerned about saving metadata to files from 2 different versions? I'm interested, as I've had no problems to date, and I use XMP constantly.

cadmanmeg, try the troubleshooting steps here if you haven't already. There were a few reports of preferences not upgrading cleanly from 1.4.1 to 2.x, so your crashes could be something as simple as that. You could also try temporarily uninstalling 1.x as I have heard a few reports of that solving some crashing problems, even though they shouldn't in theory interact.
 
Last edited:
It depends on what changes you're making. Most of the data can be saved to the XMP header in the DNG file, which would then appear in her 1.4 catalog when she imported them. Flags, collections, virtual copies and a few other minor bits aren't included in XMP, and 1.4 would just ignore the new tools data that it doesn't recognize.

I checked to confirm that 1.4.1 won't read 2.1 catalogs, and when we imported the DNGs directly it didn't bring in keywords, image adjustments, or crops, though the keywords are embedded in the IPTC and can be read by other applications. Do I need to "save metadata to file" in 2.1 before importing the files into 1.4.1. and then "read metadata from file" in 1.4.1?

Alastair
 
Yes to saving the metadata. I don't think you should have to read metadata once you import into 1.4.1, although definitely try it if it's not working as expected.
 
Status
Not open for further replies.
Back
Top