I have the same problem. Around 39.000 pictures in my catalogue, even newly imported folders with about 400 pictures in it do not work!!! Smaller folders are displayed correctly.
Windows 7 64 bit. Previous LR version: 3.4.
This is just unbelievable that this wasn't found during beta-testing. I will not play around with any workarounds but expect Adobe to provide an update asap. It is really annoying to pay for an update and then have to work with the older version.
I have the same problem with my catalog (25 628 photos)
Wow this is big.. How come so many people have the same problem. Does someone have a solution? Where Adobe?
Any help will be appreciated.
Adobe has finally contacted me and I must say that I am very disappointed. The communication was poor, it took a long time for them to get back to me and the resolution was not acceptable.
They told me what all of us with this issue ALREADY know. We must create a new catalog, import the old one and live with all of the publish services being lost.
I am really disappointed that after waiting this long the issue was not fixed by their engineers. I would expect this in a beta release but not a polished full release of a new version. It is very surprising that this was not caught during the beta.
PLease contact adobe if you are still having this issue and maybe the more people that call them the faster it will get fixed the right way instead of just a workaround.
I agree, no patches whatsoever and they appear not to care at all that you lose any publish information on keywords as long as you can export from one catalog and reimport it. Sad. The last time I contacted them, they had their response down to a routine. Still no patches or admission that there is a problem in the catalog conversion routine. They also keep replying to my open ticket trying to get it closed, but offering no solution except the workaround. You all need to open chat with Adobe or call them if you are having the issue.
I apologize for the fact that the customer service response has been unsatisfactory, and I understand that waiting for a patch is frustrating. This statement, however:
"Still no ... admission that there is a problem..."
is simply not true (please see my previous post, above). We are well aware that there is a problem, and are working on it actively. I know that yesterday would have been better than tomorrow, but this is one of our top priorities, and we will get a fix to you as soon as we can. Again, I will post back to this thread when I have something for you.
Appreciate the update Ben. Perhaps someone needs to share/discuss this perspective with the folks at Chat and that manage the tickets. Respectfully, while you had said there is a problem and that you would update this thread with more info 10 days ago, it's not clear to me where you are at in the chain with Adobe. So while you've said there is a problem and it is being worked on, you have a completely different story than we are getting in feedback from support. My experience is almost identical to Kevin's (zdybkela) above.
So, I'll retract my statement of "No admission, there is a problem..." Clearly, you agree there is a reproduceable issue, but I cannot find where Adobe has indicated they have a problem unless you are speaking for Adobe.
My statement was based on responses I have received in Chat in relation to my two tickets. Responses to open tickets that do not address the issue but that seek to close a ticket with a workaround is poor PR and leaves the impression that everything is just fine. When I asked to speak to a manager, my request was denied, my ticket closed. I'm not looking for a blow by blow, but a lot of Goodwill could be obtained if the folks at Chat and Support could at least indicate that the engineers are working on a solution and that there is currently no ETA. Even an update on the LR Support page would probably suffice for most.
The standard response that we need to create a new catalog and import the old one, even though we have repeatedly said this is not acceptable with no recourse and closing of the chat sessions is wrong. It does not help that Scott Kelby/Matt Kloskowski and other big proponents of LR continue to rave about the product and indicate that they've had "No issues". Seriously? If we're using LR and can reproduce the issues for you, we're not noobs at this.
A quick look at the "Hot Issues" reveals no mention of catalog conversion fail: http://blogs.adobe.com/lightroomjournal/2012/03/lightroom-4-hot-issues .html
even though it is discussed by consumer feedback recorded in the journal. Then, no more journals since the 12th. Not sure where we should get our info from, but it is difficult to find what is being done about the catalog conversion errors. Is there some place we can see what is being worked on and monitor for status, or are we supposed to keep hitting chat and our tickets?
To my knowledge you seem to be the only one that indicated you can reproduce the issue, but I have no idea who you are or what is being done about it other than what we get back through chat sessions, and it ain't pretty. I spent well over 60 hours of my own time trying to fix things and get my catalog working again. I'm finally up and using LR4 and now I'm dealing with how LR4 handles things much differently in the color reproduction and the conversion from ProPhoto to sRGB.
Respectfully, while you had said there is a problem and that you would update this thread with more info 10 days ago, it's not clear to me where you are at in the chain with Adobe.
Ben is up to his eyeballs in this stuff as a member of the LR team. You can bet the farm that what he says is as close to ground truth as it gets.
Your point (if I may paraphrase) that the left hand doesn't seem to know what the right hand is doing, is well taken. I have communicated with customer support, and asked them to please make it clear that we are working on a real fix for this.
Thank you Ben. I also just got pinged on my Chat ticket again and asked to join another chat. I'll go answer that. I've already imported my LR3 catalog to LR4 and rebuilt all my publish collection information by hand. So, at this point, I'm not looking to convert again, but would think this issue critical to get fixed. I am able to crash LR4 during the Sync process with SmugMug every ~100 photos during the presentation of potential conflicts. Not sure if this is related or not, but I worked my through 10k images 1 at a time until complete.
"I am able to crash LR4 during the Sync process with SmugMug every ~100 photos during the presentation of potential conflicts."
I would say not related. Please make sure that you are using the latest Smugmug Plugin:
I walked through it with Chat and they agree. What crashed was ntdll (NT Kernel). Tech pointed to my driver for Video card, but all drivers on my machine are current and I showed this. While I have no doubt this is windows kernel crashing, I suspect it has something to do with the conflict resolution panel displaying something the graphic card does not like. Perhaps it is in the rendering of the NEFs, I don't know. He also suggested I turn off all third party plugins. Which I can do, but we moved on. I agree, not related to the original catalog conversion problem. But I hit it while manually rebuilding my published collection data that got lost in the Export/Import workaround. I can hit it fairly reliably and I only hit with LR using the Sync portion of the plugin....
I also walked through crashing LR3 doing an export with previews on. Tech grabbed this info and escalated it. Again, would not be an issue if I had been able to convert the original catalog, so I don't think this is related either, but who knows.
Adding my voice from another thread on this topic. After ~12 hours trying to make this work, which included worthless help from Chat Support and an hour on hold then a worthless 1.5 hours of telephone support I got a refund for the product. When this gets resolved I'll consider trying again, but more likely give it some time to see what other bugs are being discovered by the Adobe test organization, aka the LR user community.
Same symptoms - collections, published services, previous import...all showed thousands of photo's - but nothing in the standard folder in the library module showed nothing. Selecting a photo in a collection and moving to the Develop module worked, as well.
Just saw this out on CNET:
It appears that they have a fix coming in Lightroom 4.1 release candidate
Check out link to see all the update goodness
Good evening everyone.....Looks like the wait is finally over!! Adobe Lightroom 4.1 RC (release candidate) has been released and this issue was corrected!! I just installed it and my folder previews AND publish services are all working as they did in LR3.
Here is the link.....http://labs.adobe.com/technologies/lightroom4-1/
Just a note that this is a "release candidate" and it will replace LR4 and not run "next" to it. I have had it installed for an hour and so far it looks good!!!
Overall I am very pleased with Adobe in their response to this issue.
I have the 'no photos in parent folders' issue and was glad to read it was resolved with LR 4.1RC - HOWEVER, I cannot find anywhere in the 4.1RC info that the release addresses this particular problem. Would you, Ben, or anyone else, please point me to something that assures me, before I jump in, that my problem will be fixed - or can anyone tell me that they have had success and can now see their parent photos after adding the release? I surely would appreciate it . . .
I just had this issue myself. I'm glad I came here first before doing anything drastic, like uninstall and reinstall. I'm in the process of downloading LR 4.1RC, and hope it fixes my problem. I hadn't noticed anything wrong untill this afternoon. None of my previews were displaying. Only thing that I can remember doing since the last time I ran LR4 was install the OnOne LR Presets. I'll report back later as to whether this fixes it.
Well...I installed the LR 4.1RC and it still doesn't display any previews. I even created a new catalog and re-imported all my photos, almost 14k worth, and it still won't display any previews. I'm now having it generate standard previews, and this is taking forever! If this doesn't work, I'll have to seriously think about upgrading the ram in my iMac and start using Apeture!
Anyone else still having problems after installing the update?
Message was edited by: BroPhotography