Lightroom 5.3 issue

I'm still having issues with Lightroom 5.3 with the Noise Reduction and sharpening. When I'm in the developement mode and correct my pictures then go back to the Library it does not keep my changes. I never had this problem. I thought this was supposed to be fixed with the 5.3 version? Thank you

I'm still having issues with Lightroom 5.3 with the Noise Reduction and sharpening. When I'm in the developement mode and correct my pictures then go back to the Library it does not keep my changes. I never had this problem. I thought this was supposed to be fixed with the 5.3 version? Thank you

Similar Messages

  • Lightroom 5 download issue!

    I Have a mac computer and im trying to download the free trial but when i click on the file in the downloads i keep getting this: "Couldn't open "Adobe Photoshop Lightroom 5.pkg". and it stating it can not be completed. Is it not compatable with my mac book pro?
    Or is it because i have lightroom 2 on my computer not and its causing an issue?
    Should i delet light room two and try to reinstal it aging?
    Im normaly a pretty computter savy person but this just seem to be not working!

    Adobe does not sell it.  You may be able to find one for sale on Amazon, but be careful you are buying from Amazon not somewhere that is just selling pirated software.
    Is there a reason you can’t run Mavericks, which I think it a free upgrade?

  • Photoshop CS5/Lightroom 3 integration issue - "Edit Copy with Lightroom Adjustments" does not work

    When clicking "Edit Copy with Lightoomroom Adjustments" from Lightroom, I get an error in Lightroom 3 complaining that the Camera Raw plug-in is not up to date; full message below.
    "This version of Lightroom may require the Photoshop Camera Raw plug-in version 6.1 for full compatibility.
    Camera Raw version 4.6 is the latest version available for Photoshop CS3. If raw file support for your camera was introduced after Camera Raw 4.6, the Photoshop integration features in Lightroom require Photoshop CS4 and the latest Camera Raw version 5 plug-in.
    The version of Camera Raw plug-in currently installed is 0.0."
    After I click "Open Anyways", Photoshop CS5 is initiated but it seems to have lost context of why it is opened and asks me what file I want to open (i.e. the Open As dialog).
    "Edit Copy" and "Edit Original" from Lightroom 3 works as expected and opens images fine in Photoshop, CS5 however.
    My installation is on Windows 7. I currently also have Lightroom 1.4 and Photoshop CS3 installed. Everything worked fine with the old configuration. I also tried the same workflow in Lightroom 1.4 again just now, which is now linked to CS5 instead of CS3. The "Edit Copy with Lightroom Adjustments" also work just fine.
    Things that I have tried but do not worked:
    I did an Update via the Help -> Update menu, and also manually downloaded the Camera Raw 6.1 plug-in.
    Blew away the Photoshop preferences file
    Made sure that Lightroom 3 points to Photoshop for editor
    I'm thinking that I'll try uninstall CS3 next. Anyone else encountered this issue?

    [CS5.1 (12.1) ACR 6.5RC / LR 3.5RC; MacbookPro 4gb Leopard 10.5.8 ] As a Lightroom instructor, up until now this has been a vexxing problem to explain to my students. Even if ACR in Photoshop is up to date (I just downloaded 6.5RC and installed the PS Plugin), I still get the error when attempting to edit from Lightroom 3.5RC. I deleted the PS prefs file to no avail. I was not willing to re-install Photoshop as a solution (per some blog's suggestion), although that might be the ultimate answer. But what an ordeal if so!
    For a solution, I went back to a resolution I devised when I had a CS3 compatibility problem with LR3. I went into the Preferences of Lightroom and manually chose the Photoshop app as the "custom" image editor. I went back to edit the file in PS from Lightroom and the ACR error disappeared. Try it. Yes, this means you need to use the Custom editor as your image editor, but it seems to have resolved the issue.

  • Lightroom 4 performance issues

    Hello,
    Months ago I switched from Aperture 3 to Lightroom 3 and quickly fell in love with the program.
    I switched due to constant freezing and crashes in Aperture 3. I invested time and money to learn Lightroom 3. Performance in Lightroom 3 was superb. Anything I would do with regards to any type of adjustment gave instant results on the screen. Program never crashed or froze onec. Quite frankly, I was shocked in a very positive way.
    This was on Macbook Pro i5, 8GB RAM, Hi Res Antiglare screen with Snow Leopard.
    I purchased Lightroom 4. I did a clean install of OSX Lion and, clean install of LR4. New catalogs, no importing of anything. LR 4 is sooo slow. It works just like Aperture 3 worked, the  precise reason that made me dump it.
    The longer LR4 is opened, the slower it becomes. The more adjustments are applied, the slower it becomes. I will use brush and I have to wait to see results. I can't use brush. It takes me 15-30 min to brush small part of the image. I will slide adjustments and wait. I will click on crop tool and wait, wait, wait. I really love this program but I just can't work like that.
    Would anyone share some light or advice on what could be done, on what is going on?
    Thank you.

    Rob,
    I am working with NEF files and have done so in LR3. I understand from some reading that one of the benefits from converting files to DNG is that they are faster to work with. So I just copied one of my NEF as DNG and I have been working on it for about 15 minutes applying brush after brush and other adjustments to see if LR4 will slow down. Thus far it has been incredibly faster. I will continue to work on this one image and maybe convert few more to DNG to test but do you think that there might be some issue with NEF format? Another bizzare thing I just noticed is that when I open NEF image, my memory quickly goes up to over 3GB and that's not even during applying adjustments. Working now with DNG, memory is just around 1.3 GB. WHAT IS GOING ON HERE???
    I wonder what type of files are other LR4 users that are reporing performance issues working with.
    Please share your thoughts.
    Thank you.

  • Lightroom/CS3 color issues on Mac

    Hello,
    I've seen a few posts about color issues, and I've tried following the advice posted, and I'm still having a problem. My photos appear fine in PS and in Lightroom (as well in in Mac's previewer) but when I upload them to the web or view the saved file on another computer, they appear severely desaturated with a blue tone.
    I'm using running Mac OX X on a new MacBook Pro. I have Lightroom and CS3 installed and fully patched.
    I am shooting in RAW with my Nikon, and importing the photos to Lightroom. In Lightroom, I choose "edit in CS3" and then the file opens in CS3. My settings for that are to open it as a 16 bit PDF ProPhoto RGB. My color settings in CS3 are set to ProPhoto RGB working space, preserve embedded profiles, ask when opening and pasting.
    The files still look great when I open them in PS, and then I save them and when I look at them again in Lightroom they also look good (the same). However, if I export them as .jpgs from Lightroom, or save them directly from CS3, they lose their color quality.
    I've found that if I change my proof setup to "monitor RGB" then I can see the photos the same way they appear when saved (the bad, desaturated version).
    I would really appreciate any help anyone could provide. I am generally happy with my Lightroom/CS3 workflow, but I'm totally baffled with this color issue.
    Emily

    Well, I think what you need to do is get a better grasp on the fundimentals of color management-which is a bit beyond the scope of what the forums can offer you.
    The bottom line is that Lightroom & Photoshop CSx (meaning past CS or actually even back to 7) can and does make use of display profiles (you can't turn it off even if Photoshop has a setting that makes you think you can). An image in Lightroom and Photoshop is always color managed...outside of an app that is color management, all bets are off.
    Save, assigning and converting to profiles are all very different. Photoshop CS3's color settings are absolutely critical because that's how you deal with managed and unmanaged color.
    Until you learn different, I would suggest that you set your CS3 color settings to North American PrePress 2....if you want images for the web, Convert To sRGB or use the new Save For Web (which can now do the sRGB conversion-finally).
    For other uses and purposes, I would suggest that you seriously consider using Adobe RGB-until such time that you understand the implications of using Pro Photo RGB.

  • Lightroom 6 update issue

    I have Lightroom 5 on my iMac and have just purchased the update to LR6.
    The email that confirms my purchase informs me that I've purchased Adobe Photoshop Lightroom 6 (Mac/Win,English) and gives me a serial number.
    However, when I follow the download link I'm offered three versions of Lightroom, Mac/Win English, Windows Multiple Languages and Mac Multiple Languages.
    The Mac/Win English download has my serial number against it the the next column states that the download is "not applicable".
    The other two show no serial number and offer a download link. In desperation I tried the Mac Multiple Languages link and this downloaded, but it will not install, stating that I don't have an applicable product on my Mac to upgrade from.
    I'm stuck.
    How do I download and install the product that Adobe tell me I've purchased?
    Brian

    I finally found the solution to the problem I was having.  I don't know if this will help anyone, but I'll put it out there anyway.  As I said in my previous comment, in previous upgrades I was having problems with Lightroom not launching if I performed the upgrade from within the CC App Manager and Adobe had provided an alternate link to download the upgraded version separatly.  The result was (because I didn't clean up after these upgrades) was that I had multiple versions of Lightroom on my system (Windows 7):  Ver 5.4 and 5.7.  In the start menu, these displayed as separate lanuch icons including the version in the txt.
    Yesterday, when I decided to take the chance and upgraded Lightroom from within the CC App Manager, it performed the upgrade, said it was up to date, but I did not notice that it created another version of Lightroom WITHOUT any of the version numbers in the title.  This version was buried down in the "All Programs" folder of the Windows 7 start menu.
    TODAY, still a little frustrated, I opened the CC App Manager, It still said up to date.  I launched Lightroom (from the old 5.7 icon, or rather a shortcut to one of my existing lcats which was tied to this old version)  I went to the "Check for Updates" and it said new software was available and showed the new features available in ver 6.  I'm not sure why it didn't show this info yesterday but there it was.  I clicked the Download button which took me to the lightroom page on Adobe.  There was a download button near the top right.  It was there yesterday, but all it did was download a CC App Manager install file.   So, I went ahead and did the install again, but it just went directly to opening the App Manager.  I signed out of the App Manager, and signed back in....still no apparent change.
    THEN, AND HERE'S HOW I FOUND OUT THE UPGRADE HAD ACTUALLY BEEN INSTALLED:  I ACCIDENTALLY clicked on the Lightroom Icon itself in the CC App Manager.  To my surprise, it launched the window showing a list of my catalogs asking me which one I wanted to open.  I didn't even realize I had clicked the icon.   I chose one of my older, less valued catalogs to be opened...viola!  It said I needed to upgrade the catalog.  Wow!  I cancelled out because I didn't want to upgrade without understanding what was going on.  I tried to launch that catalog as I would usually do and it opened right away in version 5.7.....what the hell?!?!  Then I had the thought that maybe I had accidentally clicked that icon, so I manually made a backup copy of that catalog and it's previews folder in Explorer.  I clicked directly on the Lightroom icon in the CC App Manager.  It opened the "choose catalog" window again.  I choose the catalog, upgraded it and it opened the upgraded catalog  IN VERSION 6.  Wow!!
    So, being Windows, not Mac, I had to associate the lrcat file type with the NEW Lightroom.exe file, I've upgraded the remaining catalogs and I'm good to go.  So, apparently, my previous frustration comment about Adobe maybe fixing the upgrade issue is no longer a valid comment....they have fixed that problem, for my situation at least.
    Like I said I don't know if this helps anyone else, but I thought I'd put it out there.
    Bill

  • Aperture to Lightroom plugin storage issue

    The plugin doesn't seem to refresh the available storage space number when changed to an external drive that has plenty of space. As my aperture libraries are both 250GB and I'm on a macbook with about 70gb remaining, it causes a bit of an issue.
    Any thoughts?

    Very sorry about the late reply.  Was having issues posting to the forum and forgot to come back.
    What I'd do is relocate all your managed images to "referenced" on the same 4tb drive.  In doing so, make sure you choose a folder/file convention that will match the physical structure you'd like to see in Lightroom.  This choice is not mandatory, but is helpful.  Note: If you convert managed images, they'd just wind up in one locatino.
    I should have asked what size your Aperture library is.  If you have space for all your images a second time over, then yes, you should not be seeing this error.  But if you're using the plugin on a library with many managed images, the plug-in needs to copy those images, even if it's on the same drive, to a location outside your Aperture library.  That's why it's helpful to relocate them as "referenced" images before the conversion.

  • Bizarre Lightroom image quality issue

    I have a weird image quality issue with Lightroom, when opening RAW files (haven't tried it with any other file format, admittedly).
    Here's an example of how the image appears in Lightroom.  As an experiment, I exported the image as a TIFF and opened it in Gimp to see if it was just down to a display issue, but the exported TIFF showed the same quality issues as Lightroom. Aside from exporting as a TIFF (and then saving as a Jpeg), this image is SOOC:
    <a href="http://www.flickr.com/photos/swisstony10/4912360565/" title="IMG_4134 by swisstony10, on Flickr"><img src="http://farm5.static.flickr.com/4093/4912360565_5891c0160f.jpg" width="333" height="500" alt="IMG_4134" /></a>
    If I open the same image in Canon's own DPP software, this image quality issue does not occur, so I know that it's not an issue with the memory card, the camera, or my laptop's monitor.  The SOOC image from DPP (exported as a Jpeg) looks like this:
    <a href="http://www.flickr.com/photos/swisstony10/4912362053/" title="IMG_4134b by swisstony10, on Flickr"><img src="http://farm5.static.flickr.com/4116/4912362053_1ca92078c9.jpg" width="333" height="500" alt="IMG_4134b" /></a>
    Has anybody else experienced this, and if so, is there a fix?  (there had better be - I'm not going to be overly chuffed if my expensive Adobe software is being outperformed by the free stuff..  )
    Russ.

    This is proving to be an extremely helpful forum!
    Thanks for the advice on embedding my calibrated colour space - I don't very often send files anywhere other than my own home network (where all the monitors are calibrated), and when I do upload any to Flickr, it's never caused a problem in the past (and if I get anything printed by a lab, I use their ICC profile).  I'll definitely keep that all in mind though..
    Here's the original RAW file of the image I used as the example  https://www.yousendit.com/download/aHlUa3ZONmNFd2Z2Wmc9PQ   - I hope that helps someone to shed some light on what's going wrong.  From what you've said though, it does look as if this is just an extreme example of something that Lightroom isn't very good at doing.
    As I said in my original post, it'll be a bit disappointing if that's the case though, because a fair amount of the pictures I take tend to be of bands playing in what are, let's face it, diabolical conditions for photography.  (At the festival I was attending at the weekend for example, all of the photographers - even the seasoned pros - were moaning about how awful the lighting was in the Big Top, and how much it sucked to try and get a decent picture there, as opposed to the main stage where everybody wasn't completely backlit by either red or purple lights.  I appreciate that Lightroom is a much more powerful tool than Canon's DPP - the noise reduction controls on their own completely rock - but I must admit I'm a bit surprised that it can't handle highlights terribly well...

  • Lightroom 3 exporting issue: exported JPGs come out with much more noise than original edited files

    Hi all,
    My first post here so nice to meet everyone. I've been having some issues with exporting in Lightroom recently. It appeared to happen quite out of the blue. Sometimes when I export my edited .cr2 files as jpgs (in srgb), at a good quality (no less than 85), some of resulting jpgs seem to have exposure higher and/or a horribly large increase in the amount of visable noise. It seems many of the photos which this occurs in have pretty high settings for fill light, but even still, the noise is not visable in lightroom while editing the metadata linked .cr2.
    I thought it might be the problem that I'm viewing the final exported jpgs in preview, but I also tried adding them back into the catalog and they look just as off. I just upgraded to 3.3, but it seems to be having the same issue. If anyone can please help, it would be greatly appreciated!
    Thanks

    No sharpening at all during my export, Ian. Sometimes I sharpen for screen at a standard strength, but I turned it off when I started seeing the extra artifacts but the results of the exports remains basically the same with or without sharpening.
    However when I import it seems my photos already have some sharpening on them in the develop module. The settings there are sharpening = 25, radius = 1, Detail = 25, masking = 0. I honestly rarely mess with the sharpening, so I guess I skipped over those settings during the countless hours I have worked with LR! But I assume those are normal post import numbers, correct? I never apply development settings during import, that's why I say that. Thanks for keeping up the conversation and brainstorming Ian! Anyone else also free to chime in.

  • Export of the book from Lightroom to blurb, issue with Backgrounds ' opacitty = overexposed

    Hello, 
    I have Mac book Pro last generation.
    While preparing the book with Lightroom, I used new proposed tool that I found very useful , to place photos as background with different type of opacity. After upload to Blurb some of these backgrounds have disappeared at all and some have very bright color (overexposed) , so I am afraid to launch the print . After export into Pdf, everything works correctly.
    Please find enclosed  two obvious examples, two print screens of pfd file and 2 prinscreent from the ecvivalent of  the book Hylem & Mourad wedding at elyseephoto blurb page page 28, 42, 43(i add print screen also).
    Please help me to solve the issue, maybe there are some installation to correct for the graphic backgrounds? Are there minimum opacity level?
    Thank you in advance for your quick answer.
    Kind regards,
    Anna Akoun

    In the top right hand corner of the Book Module under <Book > change from <PDF> to Blurb.
    With Blurb selected you will get lo-res warnings when the resolution is too low. Later on you can change back to <PDF>.
    See screen shot:
    You would not get a lo-res warning if you used original images from your camera. But if you either use small JPGs, or you crop an image severely and then use it for a full page image, the image will be too small to be used.

  • Lightroom 5 GPS issue with Nikon D3

    I can not see the GPS coordinates in Lightroom 5. I am using a Nikon D3 with the GP-1 GPS unit.

    Thanks, this solved my issue! Don't know why, it was the printer color profile who had been selected on my monitor profile!!!

  • Lightroom 4 Download issue

    I am having an issue downloading Lightroom 4 onto my MacBook Pro. Please help!

    Could you please ellaborate the issue as to what happens when you try to download Lr 4. Do you get any error message? Which operating system do you have?

  • Photoshop Lightroom Camera Raw Issues

    I just purchased Lightroom 5 (not the CC version, I bought mine through Amazon).  I was editing a photo in Lightroom and wanted to open it in Photoshop.  A message said that Camera Raw 8.2 was required and when the photo opened in PS some of the LR editing wasn't there.  So I tried to install the most current Camera Raw (8.7) and my Mac says it's installed, but Photoshop still indicates that the older plugin is there and my issues with Lightroom Photoshop compatibility continue.  I use PS 5.  How can I solve this problem??  I've closed and reopened everything. 

    "Photoshop 5 doesn't even have ACR."
    Well that's odd because the Camera plugin I have says Adobe Photoshop Camera Raw 6.7.  Regardless, I suspected it was because of my PS 5.  Is there no way I can upgrade to PS 6 without going to CC?  Because I think it's pretty ****** to stop selling the software and make Adobe customers pay an ongoing fee. 

  • Tethered to Lightroom auto-rotation issue

    Hi, I'm using a canon EOS 1D Mark III tethered to Lightroom via EOS utility. When I shoot, at the time of capture/import lighroom doesn't display my vertically shot images as verticals, rather horizontals. I've tried to toggle with the auto-rotate setting in camera (trying all 3 settings) and nothing has changed. What am I doing wrong?

    Yes there is...actually after posting this problem, I realized that my issue was that "rotate image" under the "remote shooting" menu in prefs of EOS util was ticked on. It should be ticked off.

  • Lightroom 5 Slideshow Issues

    I don't like that you have to wait for the previews to build in Lightroom 5.  Lightroom 4 had a way around this which really helps when you have large libraries.
    I also liked how you could use the keyboard arrows during the slideshow in LR 4 to go back to a previous image / set of images shown in the slideshow. 
    It would be great if these issues could be addressed in the next update.  Thank you very much!

    Yes, what happened to the option to render previews before playing (great if you have lots of time ) and the previous default to render as the slideshow is playing (great for almost every time I need a slideshow).
    Even the Preview button has to render all the slides before showing!!!
    Any chance this option is going to be put back?

Maybe you are looking for

  • OSS Note #838429

    Hi all, Is there anybody who have already read OSS #838429 ? in the solution, they mentioned about do not load infosource 2LIS_02_ITM and 2LIS_02_HDR. But I use them for my cube 0PUR_C01. Maybe there is anybody know whether there is any problem on th

  • Roxio Media Manager - It keeps trying to install itself

    Hi Everyone, Roxio Media Manager continuosly tries to install itself and it won't go away.  I tried to uninstall it but a window pops up that states Windows Installer is running.  I tried to force quit the installer and/or Roxio, but I don't see anyt

  • Allow schema HR to select from fnd_profile_option_values

    Hi I try to create alert on table that already on HR schema, the problem is when i create the alert it will create invalid trigger on database because HR schema not allow to select from fnd_profile_option_values table, i try to give permission from A

  • OS X Mavericks with Server 3.0 doesn't show all databases

    Hi. I upgraded to Mavericks and to the new Server.app I wanted to create a backup script for Profile Manager and Wiki. I had it running perfectly on Mountain Lion and Server 2.2, The problem that I'm facing right now is that I cannot find the databas

  • Input Validator : FocusLost event handling

    I am new to working with FocusListener and I am trying to use it validate the input of a textfield to be an integer. This seems like a seemingly simple thing to do, but I am getting errors. Here is a portion of the code where I make the textfield and