DxO v8 vs. Lr4

Just tried DxO v8 (first time since v6)
Results:
* v8 seems a little better than v6 (I didn't do a rigorous comparison, to say the least), but overall I still much prefer Lr4.
Still, DxO's lens vignette correction is close to perfect, whereas Lightroom's: not so much.
Rob

I have LR 4 RC1 and LR 3.6 on my computer.
I find that the 4 RC1 is still draining memory to the point of making the computer useless...and 1980's slow!!!
TO keep both version of LR on my computer I made External hard drive second copy of my LR 3 catalog with metadata and presets and a full set of photos for protection.
Also I'm not sure if this was important but instead of doing an upgrade...I installed a complete LR 4.
I did not import the copies files into LR 4 but the 4.9 info are the original copy ONE in LR 3.6....then I imported the external drive's set of 3.6 infor back into the 3.6 catalog to make sure nothing was touched by 4.0
I'm sure it's overkill some would say...the UPGRADE was supposed to keep both...but didn't. Once imported into 4RC you can't see changes prior to that.
I'm happy to track to advances in 4 RC1...but feel safe that I can go back into 3.6 to do modification.

Similar Messages

Testing of LR4 Beta

I tested LR4 for a while and have following comments : - the new developpement tool is very attractive and the results are well above LR3, I would say much more nuanced in the approach. What is still not present is a set of HDR tools or an attempt of a preset HDR ; - the workflow, both import and export, appears to be faster than the previous version ; - using the Diaporama tool very often, I see no improvements versus LR3, very few possibilities regarding the transitions, the matching with a sound record still doesn't work and the export facility is too limited in formats, this is a pitty; - regarding the new facility of setting up a book, which can than be printed thru " Blurb", seems to be very promising ; I only tested the set up without any problems; - the printing facility, although not that much different fro LR3, woks very efficienty. I'm not using the web facility and have not tested it. The integration of a mapping tool looks interesting but I'm not having presntly Photo material that earmarks the sites, so no test as such. Plugs-in with DxO, Photoshop and Silver Efex are working very smoothly.
If a issue, besides the one raised for the diaporama, would be comming up when further testing, I will come back.
Regards

Intersting.
The screen shot I posted only occurs when leaving the Develop module. .
When I leave the Book module, it leaves a smaller gray box on the screen, too.
I just found out that whenever it leaves a gray box on the screen, I cannot restart Lightroom 4 Beta until I have done something to interrupt that gray box, like clicking on it or doing anything else that takes over the screen.
No problem leaving any of the other modules.

How many times can I install my CD LR4 ?

Hi
I have LR4 in CD but the past few months, I have the Creative Cloud. I installed the LR5 from my CC, but I want to uninstall the LR4. Could I possibly reinstall?
Thank you

Thank you very much! I want to keep this version ok LR, because, If I choose to not renew my license Creative Cloud, at least I will still have the CD version, with my key!
Thanks again and have a nice day

LR4 Problem: The file could not be edited because Adobe Photoshop CS6 could not be launched.

Is there a fix for this? When I try to edit an image in Photoshop from Lightroom 4 (CTRL+E), Photoshop CS6 launches immediately but with no image. In Lightroom 4, after about two minutes, the message box appears saying "The file could not be edited because Adobe Photoshop CS6 could not be launched." When I click OK, the image promptly opens in Photoshop CS6 like normal. This wan an itermittent issue for me after the LR4.1 release. I was hoping that LR4.2 would help, but now I get the error every time.
System
Lightroom 4.2 x64
Photoshop CS6 v13.0.1 x64
Bridge 5.0.1.23 x64
Windows 7 Pro x64
AMD Six Core / 3.9 Ghz
16 GB Memory
NVidia Quadro 1 Gb Video
Scratch space on three drives

This may be a cooincidence, I starting having problems after I started using a Nikon D800, which has 36MP files. LR4 released at the same time as the D800. LR4 shows signs of struggling with the larger files, which are typically 280MB TIFFs for the D800, like freezing for several seconds when using an adjustment brush or going into a spasm with the crop tool. Because Photoshop does not have similar large file issues, I'm doing more basic work in Photoshop, like cropping, dodge and burn, exposure adjustment, etc.
Because Photoshop otherwise runs fine, and appears to read all the prefernes properly mid-issue, to get a better idea of what's going on, I turned on Process Monitor from Technet. For what it's worth, LR4 appears to touch the Photoshop preferences before it launches Photoshop. LR4 must have a memory leak in that corrupts the Photoshop preferences file in a way that makes no difference to Photoshop.
My weekend project is to try Capture One to see if I can spend more time on photography and less troubleshooting Adobe problems. As it stands, LR4 is not usable for me.

Why does LR4 show brightness changes after external processing in CS4?

I am an experienced user of Lightroom and get excellent results. But an anomaly is puzzling me. I capture images in DNG format and download to a PC Windows 7 using a calibrated Eizo graphics monitor. Before exporting and delivering a processed image I ensure that there is no unacceptable clipping showing on the histogram. I export 16 bit files which are only converted to 8 bits immediately prior to delivery. Recently I have adopted the procedure of importing a copy of the final delivery image back into LR4.3 for better library management. (There are often keyword changes or other refinements in the delivered image) Occasionally I notice that some pictures are noticeably brighter than the existing LR processed masters which formed the basis of the above operation. So I did some tests.
I selected an image with wide tonal range, adjusted it in Develop module to meet my 'no unacceptable clipping' rule and exported it as described above into CS4. My working colour space is Adobe RGB 1998 and Color Management is set to 'RGB Preserve Embedded Profiles'. In CS4 I only changed the mode from 16 to 8 bits and then saved the file using a modified name. That was the only processing done in CS4. Both files (8 bit and 16 bit) were then re-imported back into LR4 and the histograms compared with the original modified master file. In both cases they showed highlight clipping indicating that the image is brighter than when starting the final processing in CS4. In most cases the extra brightness is not a big problem; but in some instances it is quite unaccepable and I could not use that version without further processing in LR4. Mode change does not seem to be the culprit.
Can anyone help me to understand what I might be doing wrong to bring about these unwanted involuntary changes to normally processed files? Thank you.

What colorspace do you have configured in LR for your TIF Edit-In export to PS? Since PS is out-of-date with respect to LR, presumably you are using the Edit with LR Adjustments option not the Open Anyway option.
What happens if you don’t change to 8-bits in PS?
What happens if you merely export the TIF from LR and re-import it? With variations being: if the Export bit depth is 8 bits vs 16 bits and if the Export colorspace is ProPhotoRGB vs AdobeRGB?
Do you somehow have lens-profile corrections set as the default for TIF Imports or any non-zero Toning being applied on Import? The LR defaults for TIFs can be set independently from the defaults for raws.
What happens if you use ProPhotoRGB in your Edit-In export settings and as your working space in PS?
What happens to the histogram if you soft-proof to Adobe RGB in LR?
Is your monitor calibrated with a hardware calibrator? If so is the profile ICC V2 or ICC V4?

I have lost Lightroom 5.6 due to a hard drive crash. The old hard drive has been replaced. How can I get LR5 back? I don't have a disc. I still have my LR4 disc and key. I have another adobe key, but don't know if it relates to LR5.

I have lost Lightroom 5 due to a crashed hard drive. I don't have a back up disc, and I dont think I have a key. I have a an adobe key recorded but don't know if it relates to LR5. I have an LR4 disc and key. LR5 is still intact and running on my laptop, but I need to use LR% on my desktop PC. I need an address to try a download so that I can try the key which might fit it. Any ideas how I can transfer the program (with key) from my laptop? Any other ideas?
John Carden <[email protected]>

Just download and install.
you can find by internet search for "download Lightroom", or click here:
https://creative.adobe.com/products/download/lightroom
Note: trial software is same as licensed software, once you license it.. (I hope you still have the license key).

I have Lightroom 5 from an online update to LR4. My computer is ill and needs a system wiope and re-installation of programs. Can I reinstall LR5 through Adobe after the wipe

As stated I operate LR5 as an update from LR4. LR 5 was installed as an downloaded update from Adobe ( via an amazon purchase )
My laptop is ill having nearly filled my HDD. I need to wipoe my HDD and begin again to gain some storage. Is there any way I can re-install LR5 from ADOBE as part of the original purchase agreement ?
Many thanks
Brian Mordew

You can download thru the following page and use your serial number to activate it...
Lightroom - all versions
Windows
http://www.adobe.com/support/downloads/product.jsp?product=113&platform=Windows
Mac
http://www.adobe.com/support/downloads/product.jsp?product=113&platform=Macintosh

Files Renamed when importing to LR4 and now can't find them in LR3

Help! What should I do???
Yesterday I installed LR 4 Beta. I had a folder with 300 images in it on LR 3, obviously all files had names. I imported these photos into LR4 to work with LR4 and they were renamed in the process. Now in my LR3 folder, all the files still have there old names and the "missing photo ?" and I assume that's because the name has been changed and LR3 can't find them. Any thoughts on an easy fix?
Thanks,
Matthew Kraus

Thanks so much for helping me with this.
I must admit, I didn't pay too much attention when importing this "test"
group of photos to LR4, therein lies my problem. Now that I look at the
import settings that were used:
1. Files were not added or copied, they were "moved" to a new location and
also renamed.
2. Files were renamed starting with "264" using my regular import template.
Listed below are the first 10 photos with their original LR3 and he
changed LR4 names.
1201_001 changed to 1201_264-2
1201_002 changed to 1201_265-2
1201_003 changed to 1201_266-2
1201_004 changed to 1201_267-2
1201_005-Edit-Edit changed to 1201_268-2
1201_005-Edit changed to 1201_269-2
1201_005-Edit changed to 1201_270-2
1201_005-Edit-Edit-2 changed to 1201_271-2
I have a back up of my images on an EHD from several days ago which has the
original file names, but this backup only has 203 of the 268 images I
imported yesterday and are renamed.
Thanks again,
Matthew Kraus
2012/1/11 Dorin Nicolaescu-Musteață <[email protected]>
Re: Files Renamed when importing to LR4 and now can't find them in LR3 created by Dorin
Nicolaescu-Musteață <http://forums.adobe.com/people/dorin_nicolaescu> in *Photoshop
Lightroom* - View the full discussion<http://forums.adobe.com/message/4132062#4132062>

Trying to combine folders within LR4 from two separate drives without creating duplicates--sometimes it won't let me transfer to destination folder because it says files are there when they are not; other times, allows duplicates to transfer

Trying to consolidate 261K+ of images within LR4 between two drives. Someone who was "helping" me with my Library in LR4 for some reason took some but not all of the file folders from my main backup drive (M) and duplicated them onto a partitioned hard drive (E) directly on the computer. The duplication is huge, so I am trying to condense them all back onto the original backup drive M, particularly since I believe there are also folders on the partitioned backup drive E that do not appear on the main one M, and there are many more file folders on M that are not on E, so that is the destination drive.
CONSOLIDATION: When I try to drag either the file folders or the individual files from the duplicate drive E to the original drive M to combine the two drives since the folders in many cases for some reason are not identical, sometimes LR4 says the files already exist when they clearly don't. Other times it allows me to drag and drop all files, even if the exact duplicates are already on the destination drive, thereby doubling the number of files per image and creating more duplicates. Right now I am opening each file folder on the duplicate drive E, looking at what extensions and file names are there, scrolling to the original drive, making sure they appear to be identical, then going back to the duplicate drive E, deleting the images in the folder, removing the folder, and moving to the next folder on the duplicate drive E. *There has got to be a simpler way.*
CONSOLIDATION APPROACH: I did start to create file folders names A, B, C and group file folders under them to reduce clutter, since those header folders can be closed down when not in use, but now I am wondering if I should have done that alphabetization to the main backup drive rather than to the partitioned backup drive.
My goal is to consolidate the two drives down to one, delete as many images along the way that I know I will never miss, then backup the catalog and export it to an external drive and then copy that to yet another drive for offside storage. Does this sound like the proper plan? Last time it took almost 24 hours and over a terabyte to export the catalog.
DUPLICATION: I also have many file folders that have the exact same image in them. One portfolio image may actually be in eight different folders, with the exact file, file name, file size, and date, even though I always have checked "no duplicates on import," How can this be? What is the best way to sort through duplicates? Why are the files in some of the duplicate folders not in numerical order? If I do a search and call up a file # and find 15 duplicates, the only way I can find where those duplicates reside is to take each duplicate, right click to Locate Folder in Library, then once I find it, I have to go back to All Photographs>Text.search for file #, go to the second duplicate, right click to Locate Folder in Library, then once I find it, I have to do it all again. Is there a simpler way to see all the occurrences in their respective folder locations at once?
SEARCH BY FILE FOLDER NAME ONLY: I also find I can't search for a file using a folder name (for example, "John_Doe"). I can only search by file #, keywords, or camera/lens/date, etc. Why will it not work to use All Photographs>Text>search for Doe? In other words, if I didn't keyword the individual files as John Doe, I can't search for them by that moniker.
BACKUP: It also appears that the only way I can back up the catalog is to shut down LR. Really?!
FOLDER LIST PRINTOUT: Is there a way to print out the Folder list (other than a screen shot)? I have so many file folders on each drive since I sort not by Year/Month/Date but by subject. It makes trying to compare duplicate folders quite unwieldy.
SLOW RESPONSE: And finally, as though that weren't enough, why does LR4 continually blink to a white screen after each keystroke? Takes forever just to be able to click through images, view info after hovering, etc. All other programs are closed down and the operating system shows very little memory being used.

A brief and probably non-helpful answer: I know of no way to eliminate your large amount of duplicates other than by repetitive, tedious manual effort.
*There has got to be a simpler way.*
I hope you're right, but I don't think there is a simpler way.
BACKUP: It also appears that the only way I can back up the catalog is to shut down LR. Really?!
Yes, really

Suddenly i am unable to import RAW to Lr4.4. I was able to import just prior to leaving US, but now i receive an error message (if i could update the screenshot, i would)

i have been using Lr for years. No recent changes to my preferences on Lr4.4 or my MacBookPro. When i tried to import RAW while traveling in Vietnam, i receive this error message
"some import operations were not performed"
then there is a list of my import files with the comment "the following files were not imported because they could not be read"
yet i have been importing RAW files from this camera (Canon D5II) for several years.
Thanks in advance for your help

"Could not be read" means that the destination directory, where the photos are supposed to be copied into, does not have WRITE permission.
Change your permissions on that folder.

Why do I get Colored bands on some images in LR4 and LR5, but not in Aperture?

On some images -- both RAW and JPG -- when opened in LR4 or LR5, there will be one or two "curved" color abberation lines across the entire image. This doesn't occur when I open the images in Aperture. Any idea why? Thanks

>Is it possible that Aperture is showing you the camera-embedded JPG by default? What happens if you actually produce a JPG from the raw file in Aperture?
Aperture works the same way as Lightroom in this respect. It will first show you the embedded jpeg and will render a new conversion from the raw data as soon as it can. So it is possible the OP saw the embedded jpeg, but that should not last long and certainly by now should have been replaced with a newly rendered preview. Either Aperture is more forgiving of a small defect in the raw file or Lightroom import is somehow getting corrupt files of the sd card and Aperture not (would be weird). Another option is that the camera raw cache is corrupt. This can be checked by emptying the cache (Preferences->File Handling->Purge Cache). Lastly, this might be a corrupt preview in Lightroom. Check this by zooming 1:1 on an offending area in the Develop module and seeing if it goes away.
>I suspect that the curvature is in fact due to lens corrections, and that these lens corrections are always on
I believe you are right. I remember vaguely that there is some default lens correction with some cameras like this that is independent of the lens correction module. No clue whether the LX7 is one.

Republish to Flickr from LR4 posts as new photos instead of updates them (only one set, not all)

I have a single set on Flickr that I cannot republish updates to from LR4 - republishing a modified photo posts it as a new photo. All other sets seem to work fine. I use the "built-in" Flickr plugin and LR4.3 with a Flickr Pro account. This issue started with LR4.2 when I got my Nikon D800. I've tried just about everything I can think of and have been searching for any similar problems for months and decided to finally ask for help myself.
Back in October I created a set of an event, and published the photos to Flickr without issue. A week later I wanted to republish a few photos and noticed that they instead published to the set as new. If I mark to republish, yet another copy is posted as new. After some testing, this is only for images in this one particular set - any other images in any other set update their existing version as expected.
After a while I began to wonder if the machine tag I added was causing it (active:event=) so I removed the tag from the image on both sides and tried to republish again with the same results.
Naturally I delete the new copy of the image from Flickr which then dissassociates the LR photo with anything on Flickr. I found another (cludgy) plugin which can associate photos in LR with photos on Flickr and that fixes the link between the two. But again, republish from LR and a new copy shows up.
Any ideas? This has been driving me nuts. I haven't found any special permissions or settings on the Flickr set or within LR which would explain why this one set is affected and no others. I don't want to delete the set on Flickr and lose the history. I'm trying to avoid having to manually update the images on Flickr where I would also have to manually update the titles, etc.

This has happened for LR4.2, 4.3, 4.4, and now LR5. The seemingly random nature of this bug is irratating. Last week while still on LR4.4 I published a photo, changed it, and was able to republish it without issue. Today on LR5 I published a set and went to republish a handful of photos only for them to be added as new photos to the set. LR5 indicated that they were photos to republish and not new ones to the set.

LR4 error when reading from its preview cache, needs to quit

I'm getting the above message. Lightroom says it will attempt to fix this problem the next time it launches,
requiring me to click OK and the program closes. When I relaunch it, I see the same message.
I'm on a PC w/ Win7; I updated LR4 with the 4.1 download recently to enable it to read the 5DMarkIII raw files.

From: "Steve from Maryland
I am having this problem regularly now on my laptop (SSD HDD and 64 bit
Win7Pro). I have erased the cache multiple times (BTW- you have to stop
textextractor.exe to be able to do this- more on this below as well). The
corruption keeps happening and I don't know why. Anyone????
Not sure what cache you are talking about. LR only refers to two 'caches' -
the acr cache which stores part-rendered images to speed up rendering in
Develop, and a video cache which does something when you use videos. The
catalog and previews are stored in another folder, along with a previews.db
and a rootpixels. db which store info on the previews.
If you are having trouble as you describe, you need to delete the previews
folder (including the two .db files) just leaving the catalog. Then you need
to clear the acr cache (under Edit/preferences/File handling/camera raw
cache). Then regenerate all your previews in LR (select your main parent
folder, and tell it to build all previews). If you have a lot of images,
best to do this overnight.
Then all the various caches, databases, previews, and catalog should now be
in sync again, and you shouldn't see that error.
Not sure what textextractor is but if it interferes with LR, I'd get rid of
it.
Bob frost

Internal error: assertion failed - still won't work in LR4

When I try to export an image from LR4 I get the "internal error: assertion failed" error. I'm running Lion 10.7.3 on a MacBook.
I started by reading the thread at:
Re: "internal error: assertion failed" when exporting via LR4
tinaTS offered what she thought was the correct fix but her suggestion didn't apply to my situation. She suggested moving user presets but I don't have any to move.
I also tried the basic “repair permissions” and Lion restart with no luck.
Kirk Marcus suggested removing the com.adobe.Lightroom4.plist from my library. This didn't help, still getting the error.
Then I removed these files as well:
com.adobe.Lightroom3.plist
com.adobe.Lightroom2.plist
com.adobe.Lightroom3.LSSharedFileList.plist
com.adobe.Lightroom3.plist.lockfile
None of that helped.
I tried removing all files that began with com.adobe.Lightroom and then creating a new library and just importing one picture but I still get the same "internal error" VERY FRUSTRATING.
Obviously, the program is worthless to me if I can't export images.
Additional suggestions would be appreciated. I see that lots of people on the internet are having this problem but none of the suggestions I've found so far have been of any help.

Thanks for the suggestions. I tried removing the com.adobe.Lightroom4.plist. This didn't help, still getting the error.
Then I removed these files as well:
com.adobe.Lightroom3.plist
com.adobe.Lightroom2.plist
com.adobe.Lightroom3.LSSharedFileList.plist
com.adobe.Lightroom3.plist.lockfile
None of that helped.
I tried creating a new library and just importing one picture but I still get the same "internal error" VERY FRUSTRATING.

Can I delete LR2 after upgrading to LR4?

I just upgraded from LR2.7 to LR4.2. LR2.7 is still on my computer.... The upgrade transferred my old presets OK. So, can I delete LR2.7 without any problems?
Ed in Florida

Yes, you can uninstall older versions of LR. The LR upgrades (and updates) are complete programs - they don't need the older versions to run.
P.S. Even if you want to fall back to the old process version of LR 2.x, LR 4.x still does support them (menu settings -> process ->... or at "camera calibration" pane).

DxO v8 vs. Lr4

Similar Messages

Maybe you are looking for