Skip navigation

Photoshop Lightroom 4 (READ ONLY)

This discussion is locked

chris honeysett Calculating status...

Currently Being Moderated

LR4 Beta won't let me import my LR3 Catalog.

Jan 10, 2012 10:45 AM

Tags: #lightroom #catalog #import #3 #4 #bets

Why can't I import my current LR3 catalog if I am going to Beta test this new version?

1957 Views 23 Replies Latest reply: Tom Hogarty, Jan 19, 2012 10:53 AM

Replies

Currently Being Moderated

1. kamilek303,

Jan 10, 2012 10:49 AM in reply to chris honeysett

Report

I think, it´s not the best idea at all. Duplicate folder with your pictures and import them into LR4 - this way avoid to some critical mistake on your original files. Sorry for my english, but i hope you will understand what i mean.

|
Mark as:
Currently Being Moderated

2. Richard Critz,

Jan 10, 2012 10:52 AM in reply to chris honeysett

Report

Tom has made it very clear on his webinars today that this is intentional. Lr4, while in beta, will not read previous versions' catalogs.

|
Mark as:
Currently Being Moderated

3. chris honeysett,

Jan 10, 2012 10:52 AM in reply to kamilek303

Report

Good idea, though I can always delete the catalog from LR4. The original RAW files live happily in one location and wouldn't be moved either way.
But thank you for the response.

|
Mark as:
Currently Being Moderated

4. kamilek303,

Jan 10, 2012 10:55 AM in reply to chris honeysett

Report

you are welcome

|
Mark as:
Currently Being Moderated

5. chris honeysett,

Jan 10, 2012 10:58 AM in reply to Richard Critz

Report

Didn't know that, so I appreciate the information.

|
Mark as:
Currently Being Moderated

6. ssprengel,

Jan 10, 2012 11:01 AM in reply to chris honeysett

Report

To avoid corrupting existing photos and sidecars, make a copy and import that copy. The toning settings in Process 2012 are different so it might make sense to start from scratch, although you could Write Metadata to Files on your photos before importing them, and then change the Process Version to 2012 to see a comparison using Before/After.

I have used import-as-a-copy for some of my existing photos into a new folder tree specific to LR4.

|
Mark as:
Currently Being Moderated

7. Richard Ettinger,

Jan 17, 2012 5:11 PM in reply to Richard Critz

Report

Such a policy is totally boneheaded. If i'm to evaluate LR4 properly, explore it's new and wonderous features, why must I have to redo the work I've already completed in LR3. Come on Adobe, you had me with the book module.

|
Mark as:
Currently Being Moderated

8. Lee Jay,

Jan 17, 2012 5:37 PM in reply to Richard Ettinger

Report

Richard Ettinger wrote:

Such a policy is totally boneheaded.

No, it's quite reasonable. The upgrader might have bugs, the application might have data-loss bugs, and either one could kill someone's catalog, and there's no guarantee they'd have either a backup or the knowledge of how to undo the damage.

You can properly test the trial after release.

|
Mark as:
Currently Being Moderated

9. Jeff Schewe,

Jan 17, 2012 6:09 PM in reply to Richard Ettinger

Report

Richard Ettinger wrote:

If i'm to evaluate LR4 properly, explore it's new and wonderous features, why must I have to redo the work I've already completed in LR3.

I guess you don't beta test software much do ya? This ain't a demo bud...it's beta grade software. Not the final, not even a release candidate but beta. There's no tech support (other than this forum) and there are known bugs that will not be in the final release. It would be really, really foolish to update your LR3 catalog into LR4 beta then continue working while your previous catalog is ignored.

You aren't supposed to use the beta for real work, just testing the features and functions. If you can't do that on a subset of your current catalog, I'm not sure you are a good person to be testing. As Lee Jay says, once LR4 ships, there will be a 30 day demo you can try. For now, restrict your testing to a few example images–a couple thousand at most. I suggest taking a few folders save out the .xmp processing data and import those into LR4. That way you'll have the processing instructions already. Course, you'll prolly want to update those to the new processing engine anyway.

|
Mark as:
Currently Being Moderated

10. Rob Cole,

Jan 17, 2012 6:53 PM in reply to chris honeysett

Report

LrFourB may be of interest to you.

|
Mark as:
Currently Being Moderated

11. Jeff Schewe,

Jan 17, 2012 7:32 PM in reply to Rob Cole

Report

Rob Cole wrote:

LrFourB may be of interest to you.

Which I think is a real, real bad idea...to do anything to encourage users to move to a beta version of software is, I think, an injustice to the user.

There's a really good reason why Adobe doesn't not allow the conversion of LR3 catalogs, it's a really bad idea. To do anything to circumvent that is wrong…

"*** WARNING: This plugin is a tad rough, but it worked for me ;-}"
Really, you think that's a quality disclaimer?
Only a fool would try to update a LR3 catalog to use in LR4 beta. I seriously suggest users avoid this like the plague.
Really bud, why did you publish this? You wonder why you are on the short list?
There's a reason why Adobe doesn't want users trying to update LR3 catalogs...

|
Mark as:
Currently Being Moderated

12. Rob Cole,

Jan 17, 2012 8:43 PM in reply to chris honeysett

Report

chris honeysett wrote:

Why can't I import my current LR3 catalog if I am going to Beta test this new version?

Because Adobe is a conservative company, and they aren't finished with Lr4 yet, and they don't want to have to deal with headaches that may result from bugs or changes that occur before final release.

|
Mark as:
Currently Being Moderated

13. Rob Cole,

Jan 17, 2012 8:47 PM in reply to Richard Ettinger

Report

Richard Ettinger wrote:

Such a policy is totally boneheaded. If i'm to evaluate LR4 properly, explore it's new and wonderous features, why must I have to redo the work I've already completed in LR3. Come on Adobe, you had me with the book module.

The safety section in my toaster manual says: "do not take into bathtub with you" - the toaster company's lawyer made them put that clause in there, for their protection.

|
Mark as:
Currently Being Moderated

14. Rob Cole,

Jan 17, 2012 8:52 PM in reply to Jeff Schewe

Report

y'all can do what ya want.

Me? I'm using Lr4b for real work, right now.

I'll be careful, I promise...

|
Mark as:
Currently Being Moderated

15. John Hollenberg,

Jan 17, 2012 9:26 PM in reply to Rob Cole

Report

> The safety section in my toaster manual says: "do not take into bathtub with you" - the toaster company's lawyer made them put that clause in there, for their protection.

Good analogy. Trying to convert your LR3 catalog using that plugin and using it to do "real work" is about as risky as taking your toaster into the bathtub... but if you want to get the hot water running, make some toast and jump into the tub, go ahead. Just don't say we didn't warn you.

|
Mark as:
Currently Being Moderated

16. Rob Cole,

Jan 17, 2012 10:09 PM in reply to John Hollenberg

Report

I have a better understanding of what that plugin does than anybody, and it's not so risky as you seem to think...

If anybody wants to discuss these issues outside the forum, feel free to PM me.

Rob

|
Mark as:
Currently Being Moderated

17. Jeff Schewe,

Jan 17, 2012 10:30 PM in reply to Rob Cole

Report

Rob Cole wrote:

I have a better understanding of what that plugin does than anybody, and it's not so risky as you seem to think...

Uh huh...but the odds are the vast majority of users should NOT attempt ANY method of updating LR3 catalogs to LR4. Right?

Are you suggesting that this is a safe and useful effort or a blatant attempt at self promotion? Come on, come clean...are you trying to circumvent Adobe's wish to keep users from working in LR4 beta with LR3 catalogs or not?

You are doing a disservice to the community...tell the truth for a change.

|
Mark as:
Currently Being Moderated

18. Rob Cole,

Jan 17, 2012 11:19 PM in reply to Jeff Schewe

Report

Not sure why you get your feathers so ruffled. Its not about me - its about what to do, or not, if you want to move a little faster than Adobe...

I'm not recommending anything to anyone.

|
Mark as:
Currently Being Moderated

19. Jeff Schewe,

Jan 17, 2012 11:36 PM in reply to Rob Cole

Report

Rob Cole wrote:

Not sure why you get your feathers so ruffled. Its not about me - its about what to do, or not, if you want to move a little faster than Adobe...

So...do you understand the Adobe point of view regarding updating LR 3 catalogs or not?

If you do, then why would you tempt users to do so?

You ARE recommending a less than optimal approach when you post ANYTHING regarding a user being prompted to updating LR4 catalog to LR4. Right?

Or are you suggesting users circumvent Adobe's attempts at limiting LR3>LR4 catalogs?

Still smacks as self promo to me...be REALY careful who you listen to is my advise...

|
Mark as:
Currently Being Moderated

20. toondewit,

Jan 18, 2012 2:21 AM in reply to chris honeysett

Report

That's is for you own safety. Adobe advice: don't use your originals in this Bèta!!
So may be this opsion is even blocked.

|
Mark as:
4,793 posts
Apr 1, 2008

Currently Being Moderated

21. Victoria Bampton,

Jan 18, 2012 3:31 AM in reply to Rob Cole

Report

Rob Cole wrote:

Because Adobe is a conservative company, and they aren't finished with Lr4 yet, and they don't want to have to deal with headaches that may result from bugs or changes that occur before final release.

So will you be dealing with the fallout yourself Rob, or are you planning on lighting the touch paper and running away? What risks you take with your own catalogs is your business, but the moment you make that publicly available, you become responsible for the consequences, however many disclaimers you put up.

What happens when someone uses your plug-in to upgrade their catalog and starts reporting bugs which only occur because of a problem with that upgrade? So Adobe are expected to spend hours chasing down problems that you've caused, when they could be fixing real bugs, are they? And what if the user continues using the upgraded catalog, and it has problems a year or two down the line as a result?

There are really good reasons why catalog upgrade is disabled for the beta, and it's not just laziness. Anyone reading this, please don't do it, even if it doesn't 'appear' to have any problems. LR4 is not ready for final release.

|
Mark as:
Currently Being Moderated

22. Hal P Anderson,

Jan 18, 2012 3:52 AM in reply to Rob Cole

Report

Rob,

You said, "I have a better understanding of what that plugin does than anybody, and it's not so risky as you seem to think..."

Are you serious? Can't you see how insanely irrelevant that is? Your plugin could be absolutely perfect and still users would be exposing themselves to a huge risk. Suppose the converted catalogue works fine, and a user uses it to process 40,000 images over the next three months only to find at the end that the Adobe conversion from the Beta won't work on his catalogue. Are you going to reimburse him for his time?

The Beta isn't perfect, and using it as if it were a standard release is going to have costs associated with it that many people may not see in advance and will regret having to pay. And you will have a large part of the responsibility for that. Do yourself a favour and remove the plugin from your site.

"Here's a stick of dynamite. Go play with it in the back yard. And be careful."

Sheesh!

Hal

|
Mark as:
Currently Being Moderated

23. Tom Hogarty,

Jan 19, 2012 10:53 AM in reply to Hal P Anderson

Report

Everyone, I have to strongly, strongly recommend not using workarounds or plug-ins to migrate a Lightroom 3 catalog into the public beta.

Regards,
Tom Hogarty
Lightroom Product Manager

|
Mark as:

Forum guidelines

Answers + Points = Status

10 points awarded for Correct Answers
5 points awarded for Helpful Answers
10,000+ points
1,001-10,000 points
501-1,000 points
5-500 points