From: "SavagePhoto HOLY CRAP Wacom released drivers on the 14 . I just installed those and the problem apears to be GONE!!!! So it was a Wacom driver problem, not a LR problem? Bob Frost ... View more

From: "Bach 59 With a catalogue of 4-5 hundred images open all at once this is the slowest, most unproductive program out there. Culling and tagging are LIGHTING fast in Photo Mechanic! I have 65,000 images in my catalog without any problems currently. The only lag is going into Develop for the first time the program is used. Culling and tagging in Library is fast. Some other people have 500,000 to 800,000 images in their catalog. They may have 'optimized' their systems, but still haven't found what is causing the problem. The 'restart' mentioned by someone, is simply part of LR's curing an improper shutdown. If LR is cut off before it has closed down properly, by a OS or other program crash, then some temp files may still be present which have to be removed by a restart. Bob Frost ... View more

From: "Keith_Reeder" Personally I'm about at the point of giving up, and going back to my fast, stable, reliable Lr 4 install and getting some more work done... ?? Do you mean LR3? Bob Frost. ... View more

From: "freemind42" The fact that the point curve adjustment bug made it into a release version lets me doubt that... Simply means most people don't use curves these days. I haven't used curves since I started using LR about 6 yrs ago. As soon as it was reported in the public beta, it was cured by Adobe. That's what public betas are for - to discover the less common problems that didn't show up in prerelease testing. Bob Frost ... View more

From: "glugglug >On restarting LR4 the performance issue had gone. Since I had changed >nothing on the computer during the seconds between LR shutting down and >restarting it, simple logic says the problem was within the LR realm. >Examining my computer would therefore be pointless. So you know what was wrong on your computer - your catalog was corrupt! LR can cure some catalog problems on its own, but not all. In your case it did cure it! No need for further investigation. Bob Frost ... View more

Hi Steve, A lot of people (not employees), using very different computers, do pre-release testing for Adobe, and if any of the serious problems had showed up on their computers, Adobe would have fixed it before release. Some of these testers, most, are professional photographers who also know what's what. So most people probably don't have problems - you don't rush to a forum to post saying 'I don't have a problem' - you just get on with your work. So forums are largely populated with people who DO have problems - that is what they are for - to try and help people sort them out. Adobe can't possibly test all combinations of hardware and software that exist - there are millions of different combinations. I've used LR since version 1, and I've had problems with it in the past, mainly when upgrading from 2-3, and 3-4, but I solved those by cleaning up the catalog and creating all new previews and cache files. I've also had problems with nVidia drivers not coping with LR. Updating the drivers, uninstalling all the extra stuff that gets installed along with the driver, and recently switching to a Radeon card, solved those. I've had LR crashing and corrupting the catalog and previews - due to a faulty power supply. LR still has problems; lens corrections, noise removal, and clarity , for example, are very cpu-intensive, and are best left until late in editing - not put in a preset at the beginning. Hopefully these problems will be overcome eventually, but they do not cause any serious problems on my computer. So what is different about your setup and mine? Well yours is a Mac and mine is Win7x64, and we have different graphics drivers and other software. It's obviously not just a Mac problem, because the prerelease testers using Macs didn't have your problems, so it probably comes down to different other software on your computer (or different hardware, but less likely than with Win machines that are all different. I hope you find what your problem is, or Adobe comes up with a cure, but without a computer that has your problems, Adobe has to guess. As several people have suggested, what we need to to collect up some of these computers with problems and take them to Adobe's labs! Bob Frost ... View more

Bach 59 wrote: I could not agree more!  I just finished processing a wedding and it was like running in water. What was instantaneous in LR 3 now gives the spinning wheel of death! Screen redraws take for ever...... Simple adjustments are a constant waiting game. All this on a Mac Pro 3.33 hex core with 24 gigs of ram AND an SSD!!!!!!!!! Yet my 'Frost Special' with a hex core processor, 16GB ram, and SSDs runs LR4.1 just fine!!! Very speedy. So whatever the problem is, it only affects some computers. Have you tried running 4.1 on a clean OSX installation? Bob Frost ... View more

Interesting! I don't use hyperthreading at all, because it sometime slows things down, and some software doesn't use it, and it produces more heat in the cpu, without much if any benefit. Try just using your main cores, and turn hyperthreading off in your bios. Bob Frost ... View more

From: "Butch_M Then why do you care enough to post in this thread? Just trying to help. I've used Nikon's Camera Control Pro in the past for tethering. Don't use it very often. As my Nikon dealer has been telling me for the past 2 months, you just have to be patient! Bob Frost ... View more

From: "Butch_M It's fine if you want to belive that "most" people don't shoot or need tethered functionality, I'm sure many don't and I may be in a small minority ... but I also bought and paid for an app to offer me thethered functionality .... along with all the other bells and whistles ... I don't recall anyone warning me that features would be withheld after I put up my hard-earned cash ... the tethering feature is not "new stuff" either ... if the feature is going to be included and is on the bullet list for the marketing department to hype the feature set that Lr offers ... "most" people who bought Lr because it did claim to have a functioning feature ... would expect to be able to use said feature ... as it stands, tehtered shooting in Lr is like playing darts blindfolded ... only good fortune and happenstance seem to apply ... Most people can't use tethered shooting - only about 30 cameras are supported. And I have to search to find any mention of it in Adobe's advertising. It was only introduced for a few cameras in LR3. Bob Frost ... View more

From: "Butch_M In my mind, what good is all the RAW processing capabilities of an imaging app, if you have to jump through hoops just to import images if you need to shoot tethered? OK, but you have to remember that most people don't shoot tethered; you're in a small minority. Most people would prefer that Adobe get the bugs out of LR4 before adding any more new stuff! Bob Frost ... View more

dacdidac007 wrote: Thank you for your reply. Yes Tethering, do you know why its not supported and the D700 is? Will it be an update or something? If so, how long does that sort of thing take to make it work? I did manage to tether the pics across into lightroom through this third party (freeware)  http://www.mountainstorm.co.uk but I really did want to just keep it simple and just use Lightroom 4 The D700 is supported because that camera is now about 4years old; the D800 is only about 2 months old, so Adobe has only had 2 months to work out how to control it. Then the revised LR will have to be thoroughly tested before release in a future update - probably 4.2 is my guess in a few months time. Nikon releases its own camera tethering software before it lets others do so. Nikon's Camera Control Pro is more advanced than LR tethering, but it is not free. Bob Frost ... View more

From: "PrestonPage Jeff, I'm frankly baffled by your position and tone.  I can only assume that you are new to reviewing camera SDKs and that you didn't apply to download the Nikon SDKs to investigate further the file revision history. The column header above the dates reads "Update" and means the date that the SDK files were last updated.  For the D4 and D800, that date is 12/4/2010.  I'm registerd to be notified of SDK revisions, so I know the SDK was available on 12/4/2010. As I explained in a previous post, the date given by Nikon in that column is 12/4/10. It does NOT say 2010, and the first number - 12 - is the year (obvious when you look down the list and see the dates on the older cameras start with 11, 10, 09, 08), and the last number 10 is the day of the month because some of those numbers are 22, and 30! So the date is reversed - 12/4/10 means 10th April 2012. Different countries have different date orders. This one is called Gregorian Big-endian date/time format and is commonly used in Asian countries and is the ISO international standard. Bob Frost ... View more

From: "jules_1973 >I'm cancelling my D800 order if I do not have lens profiles and Lightoom >support. I'm sure that will make some other person waiting for a D800 very happy. Bob Frost ... View more

The date of release of the D4 and D800 SDKs is given on the Nikon SDK website as 12/4/10, which reversed gives the 10th of April 2012. Just look down the list of dates and you will see that the first number is the year of release. https://sdk.nikonimaging.com/apply/ Bob Frost ... View more

Did you happen to check to see what your actual usage was before reducing the size? Mine is running well now so I don't want to mess with anything, but I do see that I have about 6,5 Gigs in the cache. Mine is set at 35 Gb, probably way more than I need with a 16 Mb camera. I could imagine a correlation if you had a huge amount in the cache just as there might be if there was not enough room allocated. You can easily work out how much space you need in your ACR cache as each of the new xxx.dat files is about 500KB in size on average (my 55K  of .dat files take up 30GB of space in the cache. All 1:1 previews rendered). If you make it smaller than it needs to hold all the xxx.dat files it simply works on deleting the oldest .dat file to make space for a new one. These .dat files only  get changed when you delete and image or render a new image. Bob Frost ... View more

To those who are still having problems with LR4, I would only say again, that the solutions I found are still working - LR4 lon my computer does NOT have the problems that some of you are so irate about. So what did I do? I upgraded my catalog from LR3 to LR4 and had all sorts of strange problems, so I deleted my previews folder (all the previews plus the previews.db and rootpixels.db - this is on Windows. Macs have a different folder/file for previews). I also cleared the acr cache to that was empty. Then I went in to Library/previews and with All Photographs selected at the top of the LH panel, I told it to Build All Standard previews. When that was done I told it to Build All 1:1 previews. Building all those previews also populates the acr cache with new xxx.dat files. That solved most of the problems, and it has worked for others on this list. But there were still one or two strange things happening, so I repeated this again after Exporting my upgraded catalog to a new catalog (without previews). That clears out any rubbish left over from the LR3 catalog that might be upsetting LR4. After creating all the new previews again with the new exported catalog, and recreating the acr cache again, everything was fine, no problems at all. So please try it. If it doesn't work for you, then let me know, but don't keep on complaining if you haven't tried it. To complete the clearout of old stuff, you might also trash your prefs file. Make sure you trash any old LR3 prefes files as well, since LR4 may try and use your old prefs file if it can't find your current one. So make it produce a completely new one and reset your prefs in the new one. Why is this necessary, some may ask? Well, as I said above, some LR3 stuff left over in the catalog can upset LR4. And if you have had any crashes with LR, the previews, previews database, andr cache can get corrupted and be out of sync with the catalog, thus slowing down the whole process of getting the right previews when scrolling through them. So, 1   Trash your prefs 2   Clear your acr cache. Make sure it is big enough to hold 1:1 data files for all your raw files. 50K of raw images needs about 30GB of ACR cache. 3   Export your upgraded catalog to a new one. 4   Delete your previews folder and create all new standard and 1:1 previews. 5   Use the latest version of LR4 - 4.1RC2 or 4.1 when released (soon I expect). Bob Frost ... View more

There is a lot of rubbish being talked about LRs 'cache memory' that you can move/resize in preferences. So let's get the facts straight. The ACR cache that you can move or resize in Prefs, is a cache of partly-processed raw image files. Every time you render a new raw image, the image goes through a long rendering process. Every time you want a 1:1 view of an image, it has to repeat this rendering. So to speed this up, the ACR cache stores a part-rendered xxxx.dat file, that can be finished off more quickly when you need a 1:1 in future. So if you look at this ACR cache it consists of a xxx.dat file for each raw image you have rendered. I have about 67K of images in my catalog (55K of them are raw files), and 55K of xxx.dat files in my ACR cache (plus an index to them). When you delete a file, the corresponding xxx.dat file is deleted, and when you import a new raw image, a new xxx.dat file is added to the cache. Originally the xxx.dat files were quite large, and one couldn't have them for all raw images (unless one had a very big HDD to spare). In any case there is a limit on the size of the cache, which has been increased recently. But now with LR3.6 and LR4, the size of these xxx.dat files in the ACR cache has been reduced drastically by compression, so my 55K of xxx.dat files only take up 30 GB (prior to this they would have taken up hundreds of GB. If you can't afford this amount of space for the xxx.dat files, you can limit the size of the ACR cache, and it only keeps the more recent ones up to the limit you specify. When the cache becomes full, the files are replaced on a one in/one out basis. So the ACR cache has nothing to do with being a scratch file as in Photoshop. There is another temporary 'scratch' file that LR uses, but that is not under your control, and in Windows it is in the usual temporary files folder, and it is deleted on closure of LR. Bob Frost ... View more

From: "MarceloTrad How would we make Adobe read all this posts? This is a User-to-User forum where we are supposed to help each other. If you want help from Adobe staff, you should post on their forum - http://feedback.photoshop.com/photoshop_family/products/photoshop_family_photoshop_lightroom Bob Frost ... View more

From: "joema3 I just installed LR4 and am appalled at how slow the Library module is when sequentially stepping through photos. Have you created your previews? If you are allowing LR to create the previews as you step through the library, it will be slow. But if you created your standard previews on import, or just did it by selecting build previews from the library menu, it should be much faster. Bob Frost ... View more

From: "andreas603 Aside from rebuilding my entire library, is there a way I can see if I have a preview already of a certain RAW file? If you select the file(s) in library grid, and then go to the menu bar - Library/Previews/RenderStandardPreviews and select 'build one' in the popup dialog, it will scan for a preview and make one if none is present. If there is one already, it will just do nothing. If you select 'build all' in the dialog, it will scan the whole folder and make any that are missing. Bob Frost ... View more

From: "Marko_Ch Edit - Catalog settings - File handlings - Preview Quality - Low That is something I haven't tried - using low quality previews. I must do a comparison of processing power/time needed for high or low quality. That might well affect not just initial preview rendering, but also preview updating while moving sliders. Bob Frost ... View more