Lightroom 4.4 Malfunction

I just upgraded to Lightroom 4.4 and now the Adjustment Brush doesn't work.  When I try to adjust the brush size, the brush morphs into the Zoom tool.  I also had this happen occasionally in LR4.3, but was able to clear it by restarting the Adjustment Brush.  In LR4.4, it persists as the Zoom tool.  I had no problem at all with the Adjustment Brush in LR4.2 and am considering a reinstall of 4.2.  Better would be to fix the problem.  I haven't tried deleting the Preferences file because I hate the thought of having to completely redo all of my personal preference settings.  Can this be fixed without rebuilding a new Preferences file?

I would suggest you replace the preference file. It's not that difficult and takes 10 min max.
This file can go "funny" and is then responsible for all kinds of strange behavior of Lr. The remedy is replacing the Preference File. 
BTW: Re-installing Lr does not replace the Pref. File since it is designed to "survive" upgrades.
See here for where to find the Preference file for your OS: http://helpx.adobe.com/lightroom/kb/preference-file-locations-lightroo m-4
See here for how to go about Replacing the Preference File: http://lightroomers.com/replacing-the-lightroom-preference-file/745/
PS: Since you report this behavior in two different versions of Lr, I am pretty sure that the Pref. file is the culprit.
Message was edited by: web-weaver PS Added

Similar Messages

  • Size control error in LightRoom

    I discovered a malfunction in the Mac version of Lightroom 3. When I set any number as maximum file size all the EXIF data is wiped from the exported JPG.
    During my work I need to send photos resized to a given resolution and within a specified filesize. All exporting is fine but whenever I activate the maximum filesize option all EXIF data is wiped. Even if I set 30MB for a less then 20MB RAW, the output JPG is created without any EXIF in it.
    Does anyone see this error either on Windows or preferably on Mac? Is there any solution to this or will be there any repair by Adobe?

    I can hardly accept a bug being called a feature without any reasoning. Please explain what purpose such an unwanted data removal would serve in favor of any photographer. By the way if this is in deed a feature the Mac version has than the Windows version of Lightroom has the malfunction not having this - still ununderstandable feature. (Shall I send a feature request to remove it from the Mac version or should I rather advice it if it has any purpose then please make it optional?)
    The EXIF is the smallest part of the image file so removing it cannot be a practical approach to make the image file reasonably smaller. Especially not when LR has a totally separate option to minimize (maybe remove?) metadata. It definietly has a sense to have this OPTION to clear EXIF but only as an option and not a hidden and constrained feature.
    I expect a setting to do what it is meant (rather called?) to do and nothing else that is not related to the given option. Especially not removing some information from image files without any warning or notice of the user.
    Thank you for our advice to experiment with quality settings but I choose LR because I mistakenly belived it is a professional photographer tool that does what its settings imply to do.

  • Since installing LTR 5.4, which I've now upgraded to 5.6, I've encountered repeated slowness and malfunctions in operations, especially when using the Compare View function and the Tab key to open and close the right and left side panels.  Such problems n

    Since installing LTR 5.4, which I've now upgraded to 5.6, I've encountered repeated slowness and malfunctions in operations, especially when using the Compare View function and the Tab key to open and close the right and left side panels.  Such problems never arose during two years of using LTR-4 and nothing else has changed on my computer.  I have a pretty simple system with only a few plug-ins, which are usually not in operation.  I have 12GB of RAM in my Windows 7 PC.  I could illustrate these problems with screen shots if you would tell me how to submit screen shots.  Otherwise I will try to describe the problems in words.
    The problem is clearly cumulative, growing worse as usage time passes.  Compare View feature gradually slows down and eventually seems to choke as my work session proceeds. If I Exit LTR and re-enter and start all over, things will work normally for maybe 30 minutes, but then the Compare View feature begins to become very slow to respond.   In a recent example with my screen full of thumbnails in Library mode I highlighted two images to compare. LTR started to open the Compare View screen by first having the top row of thumbnails disappear to be replaced by the "SELECT" and "CANDIDATE" words in their spaces  (but no images), but Compare View never succeeded in gaining control of the screen. After some seconds the top row of thumbnails reasserted its position and the Compare View windows disappeared. But LTR kept trying to bring them back. Again the top row of thumbnails would go away, Select and candidate would reappear, try again, and give up. This went on for at least 2-3 minutes before I tried to choose File and Exit, but even that did not initially want to respond. It doesn't like to accept other commands when it's trying to open Compare View. Finally it allowed me to exit.
    To experiment I created a new catalog of 1100 images.  After 30-40 minutes, the Compare View function began to operate very slowly. With left and right side panels visible and two thumbnails highlighted, hitting Compare View can take half a minute before the two mid-size  images open in their respective SELECT and CANDIDATE windows. When the side panels are open and two images are in the Select/Candidate spaces, hitting the Tab button to close the side panels produces a very delayed response--25-30 seconds to close them, a few more seconds to enlarge the two images to full size. To reverse the process (i.e., to recall the two side panels), hitting Tab would make the two sides of the screen go black for up to a minute, with no words visible. Eventually the info fields in the panels would open up.
    I also created a new user account and imported a folder of 160 images. After half an hour Compare View began mis-placing data.  (I have a screen shot to show this.)  CANDIDATE appears on the left side of SELECT, whereas it should be on the right. The accompanying camera exposure data appears almost entirely to the left of the mid-screen dividing line. Although the Candidate and Select headings were transposed, the image exposure data was not, but the data for the image on the right was almost entirely to the left of the line dividing the screen in two.
    Gurus in The Lightroom Forum have examined Task Manager data showing Processes running and Performance indicators and they see nothing wrong.  I could also send screen shots of this data.
    At this point, the only way I can process my images is to work 30-40 minutes and then shut down everything, exit, and re-start LTR.  This is not normal.  I hope you can find the cause, and then the solution.  If you would like to see my screen shots, tell me how to submit them.
    Ollie
    [email protected]

    Since installing LTR 5.4, which I've now upgraded to 5.6, I've encountered repeated slowness and malfunctions in operations, especially when using the Compare View function and the Tab key to open and close the right and left side panels.  Such problems never arose during two years of using LTR-4 and nothing else has changed on my computer.  I have a pretty simple system with only a few plug-ins, which are usually not in operation.  I have 12GB of RAM in my Windows 7 PC.  I could illustrate these problems with screen shots if you would tell me how to submit screen shots.  Otherwise I will try to describe the problems in words.
    The problem is clearly cumulative, growing worse as usage time passes.  Compare View feature gradually slows down and eventually seems to choke as my work session proceeds. If I Exit LTR and re-enter and start all over, things will work normally for maybe 30 minutes, but then the Compare View feature begins to become very slow to respond.   In a recent example with my screen full of thumbnails in Library mode I highlighted two images to compare. LTR started to open the Compare View screen by first having the top row of thumbnails disappear to be replaced by the "SELECT" and "CANDIDATE" words in their spaces  (but no images), but Compare View never succeeded in gaining control of the screen. After some seconds the top row of thumbnails reasserted its position and the Compare View windows disappeared. But LTR kept trying to bring them back. Again the top row of thumbnails would go away, Select and candidate would reappear, try again, and give up. This went on for at least 2-3 minutes before I tried to choose File and Exit, but even that did not initially want to respond. It doesn't like to accept other commands when it's trying to open Compare View. Finally it allowed me to exit.
    To experiment I created a new catalog of 1100 images.  After 30-40 minutes, the Compare View function began to operate very slowly. With left and right side panels visible and two thumbnails highlighted, hitting Compare View can take half a minute before the two mid-size  images open in their respective SELECT and CANDIDATE windows. When the side panels are open and two images are in the Select/Candidate spaces, hitting the Tab button to close the side panels produces a very delayed response--25-30 seconds to close them, a few more seconds to enlarge the two images to full size. To reverse the process (i.e., to recall the two side panels), hitting Tab would make the two sides of the screen go black for up to a minute, with no words visible. Eventually the info fields in the panels would open up.
    I also created a new user account and imported a folder of 160 images. After half an hour Compare View began mis-placing data.  (I have a screen shot to show this.)  CANDIDATE appears on the left side of SELECT, whereas it should be on the right. The accompanying camera exposure data appears almost entirely to the left of the mid-screen dividing line. Although the Candidate and Select headings were transposed, the image exposure data was not, but the data for the image on the right was almost entirely to the left of the line dividing the screen in two.
    Gurus in The Lightroom Forum have examined Task Manager data showing Processes running and Performance indicators and they see nothing wrong.  I could also send screen shots of this data.
    At this point, the only way I can process my images is to work 30-40 minutes and then shut down everything, exit, and re-start LTR.  This is not normal.  I hope you can find the cause, and then the solution.  If you would like to see my screen shots, tell me how to submit them.
    Ollie
    [email protected]

  • Lightroom opens right after I turn on my computer.  If I close out of it I can't open it back up

    I have lightroom 5.5 64 bit which I purchased.  I also have Photo cs6 and cs6 64 bit.  My program manager also says that I have adobe bridge cs6,  and adobe bridge cs6 64 bit. I can't tell the difference between the photoshop programs and I don't want them on my computer because I'm not using them.   Also and adobe extension manager I use Widows 7. 
    My biggest problem is, Once I open lightroom I have a difficult time importing photos which takes forever when it works, and once I close the window, It will never open again. the whole process has been cumbersome and extremely aggravating.  I was going to purchase lightroom for my son and his wife, but I'm really hating it.  I spent a bundle on lightroom 5.5 as well as adobe photoshop, and I'd like to throw them both out the window unless someone can help me very quickly.

    Your Lightroom probably opens when you start your computer because somehow, you included Lightroom to be among the startup programs (in the Startup folder under "All Programs")
    If you shut it down improperly, that could cause you being unable to open it again
    Slow imports are probably due to a malfunctioning card reader
    All of this is speculation, as I am not sitting at your computer

  • Using Lightroom 5.7, Raw files become from my Nikon D810 become corrupted when I select them to view or edit.

    .Updated to Lightroom 5.7 to accommodate the Nikon D810. Upon importing RAW files to the files become corrupted when they are selected to be viewed or edited.
    I am using Windows 7, 64 bit, with 8 GB Ram.
    Any help would be appreciated.

    There are several likely sources of corruption, and video card would be far down on my list of possible suspects.
    The transfer from camera card to hard disk is the most likely place for problem, either the card reader or USB cable can go bad. Another likely source of problems is the computer's hard disk is starting to fail. The camera card itself may be bad. And lastly, the memory in the computer may be malfunctioning.

  • Can photoshop CC open raw files from Lightroom 5?

    Trying to open raw files from Lightroom 5 in Photoshop CC 2014, with no luck.
    Anyone?

    Problems are as follows— all versions are current.
    1. When in Lightroom, trying to open a photo in Photoshop,-- choosing Photo>Edit in Photoshop CC 2014— Photoshop opens but no photo appears. The only time a photo opens is if it is a JPEG… CR2 does not open, dng does not open
    2. When trying to open a JPEG in Photoshop, dialog box opens offering choice between "Edit Original", "Edit a copy", or "Edit with Lightroom adjustments", Only choosing “Edit Original” allows photo to open.
    3. When in Photoshop choosing “Browse in Bridge” does not open Bridge… opens CC app and prompts me to install another version of Bridge, or keep version I have.  (See attached screenshot) Either way it’s a malfunction… as I said earlier all versions are leanest.
    PLEASE HELP!!
    Steve

  • Different colours shown in Lightroom.

    Hi everyone,
    Have been struggling with lightroom colours since i downloaded the trial version.
    Technical Info:
    All images used are Jpeg and nothing to do with RAW
    Monitor: DELL 2209WA
    Original profile: SRGB
    Calibrated profile named Spyder pro 3
    Calibrated by: Spyder pro 3
    Lightroom version 3
    Photoshop cs 5
    SRGB in camera settings
    Have been researching online for weeks since i have the colour problem and tried all sort of methods mentioned in forum and several website.
    The jpeg colour straight out of camera shown on the monitor using firefox, photoshop and picasa photo viewer seem different from the version in Lightroom.
    The jpeg imported in lightroom shown is more yellowish in colour, extra effort have been taken to make sure nothing has been changed during the importing process, all presets unchecked etc.
    To ensure the colour in lightroom is a permanent colour view and not a temporary view. Exported it using SRGB and Calibrated profile.
    If exported using SRGB, the colours will go back to the original colours shown in monitor. If exported using calibrated profile (Spyderpro 3) The colours of the jpeg (yellowish) in lightroom stays. (Viewed in firefox and picasa viewer)
    However if viewed in photoshop, choosing embedded profile or convert to working space shows lightroom colours and if discard embedded profile is choose, the default colours shown in monitor is shown.
    The colour profile used in photoshop is Spyper pro 3, and embedded profile in photo is SRGB
    Calibration is done by adjusting brightness and RGB sliders to adjust white balance and kelvin as close to 6500k and luminance of 120.
    After calibration, i will change the
    device profiles in advanced to spyder pro 3
    and viewing conditions profile to WCS profile for SRGB conditions
    Default ICC profile is Spyder pro 3 afer calibration.
    Conclusion, the initial colours shown in different program, esp lightroom vs the rest make me hesitant on which colours to trust and which to do editing on. I have no issues with the exported Jpeg, which i can get them to the colours i want.
    Resetting all profiles to default(SRGB) solved this inconsistent colours issue between lightroom, photoshop and other programs, but now they are all consistently incorrect.
    One problem solved in lightroom colours creates another problem, and this is already the third biggest problem i have.
    I was having the export problem with colours, and after researching, found out that a matrix profile over LUT profile will solved the exported colours issues, but now with the matrix profile, i am getting inconsistency with the initial colours.
    Many thanks in Advanced
    YH

    Do you have screenshots illustrating this?
    Also, you have to be more specific about what you're comparing Lightroom with. Browsers are all over the map with regards to color management - IE, for instance, will not use the monitor profile, but substitute sRGB. XnView I know nothing about, but again, many applications claim to have color management when in reality they miss at least half of it.
    And since you say you have the "same problem" as the previous posters, there are a lot of confused ideas there about what color management means - one of them even embeds the monitor profile in the exported file, which defeats the whole purpose and actually turns all resemblance of color management off.
    So just to have it established: A fully color managed application, like Lightroom, converts from the source/document color profile to the monitor profile, on the fly, and that's what goes to the display. Of the web browsers, only Firefox and Safari will do that, and even then it requires that the document profile is embedded and doesn't get stripped somewhere (which can happen).
    All that said, it is of course possible that the Spyder is making bad profiles. It could be that the sensor is malfunctioning. First of all I would check for software updates from Datacolor.
    Another thing - what is your monitor model?
    EDIT: Windows Picture Viewer (not to be confused with Windows Explorer) is fully color managed and should display identically to Lightroom. How does it look there?

  • Any new fixes for corrupt images in Lightroom 4.4?

    I have seen many threads on this and tried a lot of the tings people say to try. But I do get corrupt images in Lightroom. I currently have an AMD FX-8150, 32GB ram, 2 SSD Raid0 + USB3.0 drives as backup.
    Drive and Memory:
    Note, I only keep up to the last 3 shoots on my SSD, the rest are stored on my USB3 drives. Any time I import files to the USB drive I get no corruption. Now that would imply that I have bad drives, I have run diskcheck and contacted Muskin and they had me run some disk checks, speed tests, +other things and identified that the drives are running fine with no issues and this has to be a software issue.
    I have run memtest86+ with no errors, also ran memtest86+ with my memory in another machine with no errors.
    To rule out the card reader:
    When I just copy files from my CF Card to a folder using explorer all images import fine and you can even open every image in photoshop with no issues. As soon as you add those files already copied to the HD to lightroom, they start to corrupt. I just recently used the windows explorer method and added ~400 images to lightroom, all images imported fine, when I later accessed lightroom(Today), about 10% of those images are not corrupt.
    Does anyone have any suggestions? Could it be because I use Raid0? Or even SSD drives?
    This is quite annoying and I would like to get things fixed.

    jproductions111 wrote:
    Usually when Lr renames the photos as you saw kianjillwedding-19, Lr changed the name from IMG_1968. Thats may have something to do with the corruption.
    I don't see how. Renaming shouldn't change anything on disk except, well, the name - and of course update a bunch of things in the catalog.
    jproductions111 wrote:
    I will get back to you if the problem continues but everything still seems to be fine in Lr5, even after letting Lr rename all the photos with my current(today's) import of 700 images.
    OK - thanks.
    jproductions111 wrote:
    I know you don't believe its software
    ~impossible it's Lr4 software. Theoretically possible, but highly unlikely. As I said, Lr4 should never be rewriting those files, and therefore essentially can not corrupt them. I mean, its possible that it got it's brains scrambled, and went ahead and rewrote them, for god-knows why or just for the he|| of it - because some bits seemed to be set wrong..., thus invalidating the assumption that it's not rewriting them. It's just that this scenario is the least likely. I mean, Jeff Schewe has given me spankings more than once before, for even bringing it up, since it's so unlikely...
    jproductions111 wrote:
    maybe Lr 4 was causing some sort of bug to make the hardware malfunction
    Although theoretically possible, I'd still venture to guess that's not what happened.
    jproductions111 wrote:
    this is not happening to my in Lr5.
    Didn't you also change your disk drive situation around just before you started using Lr5?
    jproductions111 wrote:
    But I am keeping my fingers crossed.
    Me too - please keep us posted...
    R

  • [お知らせ]Lightroom 5.7.Camera Raw 8.7 をリリースしました

    Photoshopユーザーの皆様、こんにちは！
    Lightroom 5.7とCamera Raw 8.7のアップデートが提供開始となりましたのでお知らせします。
    Lightroom 5.7は、Lightroom 5ユーザー向けに無償アップデートとして提供されます。Camera Raw 8.7は、Photoshop CCおよびPhotoshop CS6のユーザーに無償アップデートとして提供されます。CS6向けのCamera Raw 8.6については、Camera Rawのポリシー変更に基づき、カメラおよびレンズプロファイルのサポートのみのアップデートとなりますのでご留意ください。
    今回追加されたRAWデータのサポート対応機種は以下のとおりです。
    サポートカメラ機種
    – キヤノン EOS 7D Mark II
    – キヤノンPowerShot G7 X
    – キヤノンPowerShot SX60 HS
    – カシオEX-100PRO
    – 富士フイルム X30
    – 富士フイルム X100T
    – 富士フイルム X-T1 Graphite Silver
    – リーフ Credo 50
    – ライカ D-Lux (Typ 109)
    – ライカ M-P
    – ライカ V-Lux (Typ 114)
    – ライカ X (Typ 113)
    – ニコン D750
    – オリンパス PEN E-PL7
    – オリンパス STYLUS 1s
    – パナソニック DMC-CM1
    – パナソニック DMC-GM1S
    – パナソニック DMC-GM5
    – パナソニック DMC-LX100
    – ペンタックス K-S1
    – ペンタックス QS-1
    – Samsung NX1
    – Sony ILCE-5100
    – Sony ILCE-QX1
    テザー撮影がサポートされた機種
    – Nikon D4S
    – Nikon D810
    追加されたレンズプロファイル一覧
    Mount
    Name
    Apple
    iPhone 6
    Apple
    iphone 6 Plus
    Canon EF
    SIGMA 18-300mm F3.5-6.3 DC MACRO OS HSM C014
    Canon EF
    SIGMA 150-600mm F5-6.3 DG OS HSM S014
    Canon EF
    Tokina AT-X 116 PRO DX-II 11-16mm f/2.8
    Canon EF
    Zeiss Otus 1.4/85 ZE
    Fujifilm X
    Fujifilm X100T
    Fujifilm X
    HandeVision IBELUX 40mm F0.85
    GoPro
    Hero
    GoPro
    Hero4 Black Edition
    GoPro
    Hero4 Silver Edition
    Leica M
    Leica SUMMARIT-M 35 mm f/2.4 ASPH
    Leica M
    Leica SUMMARIT-M 50 mm f/2.4
    Leica M
    Leica SUMMARIT-M 75 mm f/2.4
    Leica M
    Leica SUMMARIT-M 90 mm f/2.4
    Leica M
    SLR Magic 50mm T0.95 Hyperprime Cine Lens
    Leica M
    Voigtlander VM 12mm F5.6 Ultra Wide Heliar ASPH.
    Leica M
    Voigtlander VM 15mm F4.5 Super Wide Heliar II ASPH.
    Leica M
    Voigtlander VM 21mm F1.8 Ultron ASPH.
    Leica M
    Voigtlander VM 21mm F4 Color Skopar
    Leica M
    Voigtlander VM 25mm F4 Color Skopar
    Leica M
    Voigtlander VM 28mm F2 Ultron
    Leica M
    Voigtlander VM 35mm F1.2 Nokton II ASPH.
    Leica M
    Voigtlander VM 35mm F1.4 Nokton Classic
    Leica M
    Voigtlander VM 35mm F2.5 Color Skopar
    Leica M
    Voigtlander VM 40mm F1.4 Nokton Classic
    Leica M
    Voigtlander VM 50mm F1.1 Nokton
    Leica M
    Voigtlander VM 50mm F1.5 Nokton
    Leica M
    Voigtlander VM 75mm F1.8 Heliar
    Leica S
    Leica SUMMICRON-S 100 mm f/2 ASPH.
    Nikon F
    Nikon AF-S NIKKOR 20mm f/1.8G ED
    Nikon F
    Nikon AF-S NIKKOR 400mm f2.8E FL ED VR
    Nikon F
    SIGMA 18-300mm F3.5-6.3 DC MACRO OS HSM C014
    Nikon F
    SIGMA 150-600mm F5-6.3 DG OS HSM S014
    Nikon F
    Tokina AT-X 116 PRO DX-II 11-16mm f/2.8
    Nikon F
    Voigtlander SL 40mm F2 Ultron ASPHERICAL
    Nikon F
    Voigtlander SL 40mm F2 Ultron ASPHERICAL Close-up Lens
    Nikon F
    Zeiss Otus 1.4/85 ZF.2
    Pentax
    HD PENTAX-DA 645 28-45mm F4.5 ED AW SR
    Pentax
    HD PENTAX-DA 16-85mm F3.5-5.6 ED DC WR
    Pentax
    HD PENTAX-DA 20-40mm F2.8-4 Limited
    Sigma
    SIGMA 18-300mm F3.5-6.3 DC MACRO OS HSM C014
    Sigma
    SIGMA 150-600mm F5-6.3 DG OS HSM S014
    Sony Alpha
    SIGMA 18-300mm F3.5-6.3 DC MACRO OS HSM C014
    Sony Alpha
    SIGMA 24-105mm F4 DG OS HSM A013
    Sony Alpha
    Sony DT 18-55mm F3.5-5.6 SAM
    Sony Alpha
    Sony DT 18-70mm F3.5-5.6
    Sony Alpha
    Sony DT 55-200mm F4-5.6
    Sony Alpha
    Sony 75-300mm F4.5-5.6
    Sony Alpha
    Sony 300mm F2.8 G SSM
    Sony Alpha
    Sony 500mm F4 G SSM
    Sony E
    HandeVision IBELUX 40mm F0.85
    Sony E
    SLR Magic 50mm F0.95 Hyperprime Lens
    Sony E
    Sony FE 16-35mm F4 ZA OSS
    Sony E
    Sony FE PZ 28-135mm F4 G OSS
    Sony E
    Zeiss Loxia Biogon T* 2/35
    Sony E
    Zeiss Loxia Planar T* 2/50
    アップデートの入手方法
    このアップデートは、Adobe.comとPhotoshop CCおよびPhotoshop CS6のアップデートを通して入手できます。
    製品からのアップデート方法
    Creative Cloud ヘルプ | アプリケーションのインストール、アップデートまたはアンインストール
    Adobe.comからのダウンロード方法
    以下のページのおすすめのアップデートから該当するものを選んでください。
    アドビ製品のアップデート
    2 閲覧
    カテゴリ: レンズプロファイル、カメラプロファイル
    タグ (編集):
    メッセージ編集者: TETSUMA SHIMIZU

    Blue screen/Computer shuts down is almost always a hardware malfunction or a driver problem.
    Make sure your video driver is up to date.
    If it is, then the next suspect, in my mind, is overheating, make sure all of the fans in your CPU case are working properly.

  • Import Corruption in Lightroom CC?

    Can anyone suggest what is going on with this import corruption in Lightroom CC?  Reinstall LRCC?  First photo imported with LRCC; second imported with Nikon Transfer.  Both imported in NEF and these are SOOC jpg conversions.  Thanks.
    LR CC
    Nikon Transfer
    Maybe reinstall LRCC?  Thanks for any help.
    Clay Johnson

    This is always a hardware malfunction. It could be anywhere from the camera to the card to the card reader/USB port or USB Cable, computer hard disk or computer memory. Re-installing LR won't fix this problem.

  • Saving metadata from Lightroom erases custom XMP data in DNG...

    Hello,
       There seems to be an issue with the way Lightroom applies changes in from the LR catalog to the assets metadata.  The setup is LR 2.5 and there is an orginal set of images that have custom XMP data applied to them via Bridge.  There is one LR catalog that points to these images and the LR catalog ratings and labels match those that are in these images.  A second LR catalog copy (not export) was made where additional changes were made only to ratings and labels.  This catalog also points to the original assets.  When using the Save Metadata to files function in LR for this catalog (and selecting ALL files), LR erases all the original custom XMP data contained in the DNG images and writes only the ratings and label information.
        It doesn't seem that LR should be overwriting the entire XMP packet when only ratings and labels have changed and are saved back to the assets.  Is that the way this is designed or is this a malfunction?
    Thanks for any help on this!
    David

    I may have answered my own question as we have run into this issue before.  Lightroom is really not designed for any type of simultaneous workflow on the same files.  Most content management applications utilize the check-in/check-out mechanism to avoid having to perform any type of merging or implement a logical business rule to determine which content updates "win"  It is no different with Bridge and LR.  You work in one application at a time doing specific things to the same files and then read from each other when those actions are complete.  Working in this manner you never run into the merge issue or lose data from either side.
    Our simple answer to this question is adjust our workflow timing for things to accommodate this behavior.  The one thing that I will say is that LR does really need to provide some type of catalog history functionality that can be queried.  I believe that LR does interact with the catalog database in this manner when you use the Save functionality from the context menu and have not imagery selected.  It scans the database looking for any changes and then only updates those files it finds changes for.  If we could only see this type of functionality added in a way that would show us history for changes to the catalog at large and not have to dig into individual assets to look for these changes that would be great.
    We are going to look at a way to query the LR database itself to see if there isn't some time stamp information and file ID/filename data that can't be accessed as it would be invaluable to be able to look across large catalogs (well over 1000 images) and find the files that had been most recently updated (in updated I mean only simple updates to rating and label) and then separate these out to work with in their own group (collection).
    I could also look at this as yet another opportunity to refine a workflow that doesn't create changes to identical data each time changes are incurred.  I will look at that option much more closely as it is really the only thing we can easily control.
    Cheers!
    ~David

  • Hi to all, I use Windows 7, 64Bit and Lightroom 5.7, Camera Raw 8.7, when I develop or export files (mostly Raw Fils from Nikon D810) after 10 to 20 pictures my computer shuts down or I get a bluescreen. Please tell me why.

    Hi to all, I use Windows 7, 64Bit and Lightroom 5.7, Camera Raw 8.7, when I develop or export files (mostly Raw Fils from Nikon D810) after 10 to 20 pictures my computer shuts down or I get a bluescreen. Please tell me why.

    Blue screen/Computer shuts down is almost always a hardware malfunction or a driver problem.
    Make sure your video driver is up to date.
    If it is, then the next suspect, in my mind, is overheating, make sure all of the fans in your CPU case are working properly.

  • I lost CS2 when I upgraded to OSX Yosemite.  I want to install Lightroom. Can I transfer the Lightroom 5 software to an SD card and then download from that to my computer?

    I have a 2009 21.5 iMac with malfunctioning internal disk drive. I lost CS2 when I upgraded to OSX Yosemite.  I want to install Lightroom. Can I transfer the Lightroom 5 software to an SD card and then download from that to my computer?

    you need the installation files, not copies of installed programs.
    Downloads available:
    Suites and Programs:  CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4 | CS3
    Acrobat:  XI, X | 9,8 | 9 standard
    Premiere Elements:  13 | 12 | 11, 10 | 9, 8, 7 win | 8 mac | 7 mac
    Photoshop Elements:  13 |12 | 11, 10 | 9,8,7 win | 8 mac | 7 mac
    Lightroom:  5.6| 5 | 4 | 3
    Captivate:  8 | 7 | 6 | 5
    Contribute:  CS5 | CS4, CS3
    Download and installation help for Adobe links
    Download and installation help for Prodesigntools links are listed on most linked pages.  They are critical; especially steps 1, 2 and 3.  If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

  • Lightroom 5 won't import all photos on card

    Hello,
    I've been using Lightroom 5 successfully for half a year (Mac OS X 10.7.5--my camera is a Canon Mark III--and I shoot raw), and never had a problem with importing photos. Suddenly yesterday, when I clicked on import, and then my card, the thumbnails on the card came up, but most were greyed-out, and the program only wanted to import a few select photos. I did the update for Lightroom 5, but still couldn't get the photos to import. The same thing happened again today with a second card, and I cannot uncheck/or check all of the photos, or find any other way to get the greyed-out photos to become un-grey or to import. I hope someone can help me soon, because I am running out of cards.
    Thanks.

    Thanks Catherine.
    Normally these issues are due to some sort of hardware malfunction.
    The cards themselves could be a problem (less likely because you have used multiple cards).
    The card reader could have an issue.
    The USB cable connecting the card reader to the computer may also be faulty (you could try a different cable and see what happens).
    Sometime the USB port and controller might be corrupted.
    Something to try while going through all the options is to copy the images from the card onto your system and then try to import them from the hard drive into Lightroom and see if the problem persists.
    This process is a somewhat trial-by-error thing.
    Tony Jay

  • Lightroom 4.3 corrupts my RAW images stored on local SSD harddisk

    Using Lightroom 4.3 with Camera RAW 7.3 on latest MacBook Pro with 256 GB SSD harddisk, 8 GB internal memory bought 2 months ago. Hardware shows no other problems or malfunctioning, no issues with RAM or otherwise.
    Started Lightroom 4.3 did an import from perfect images (viewed before using various other software packages) stored on the harddisk. Used option ADD to add to the catalog. Almost immediately certain images were showing missing areas or areas with pink/white stripes, etc.
    I didn't even touch the images to view or edit them. The images were corrupted on disk as previewing them with other software packages showed.

    bruijnesteijn wrote:
    I appreciate all the help
    You're welcome, for my part .
    bruijnesteijn wrote:
    I am getting the feeling that a Lightroom user is expected to be know a lot of possible hardware and software stuff thn can be expected from the average photographer.
    Only if they're having problems .
    bruijnesteijn wrote:
    MacBook extended checks. No issues, unless we are going to question the Apple software used for checking their own hardware...
    I have no clue...
    bruijnesteijn wrote:
    I copy my images to my harddisk using Adobe Bridge Photo Downloader = check, images are OK in Camera RAW & Photoshop.
    If we're talking about the raw rendering, and not just the jpeg, then this means transfer hardware is OK.
    bruijnesteijn wrote:
    After this no other hardware is involved
    That is not so true. Hard disk, ram, cpu, ..., - all play a continuing role.
    bruijnesteijn wrote:
    No proprietary RAW format e.g. I use standard Canon 550D settings. Not sure how proprietary you call that and what I can do about that and why Lightroom would have a problem with it. If that would be an issue I would expect a lot more issues from other users.
    A proprietary raw file is any raw file that is not DNG. The distinction is important because:
    * Proprietary raws can not be corrupted by Lightroom (that statement has 99.999999999999% probability of being true, in the context discussed so far).
    * DNGs on the other hand, are, in some circumstances, completely re-written, and can, therefore, be corrupted on Lr's watch (due to hardware failure). Granted, if such failure does occur, Lr is able to give a fairly clear & unambiguous message, since it keeps check codes for raw data integrity assurance. Note: such protection assumes the image was good when initially converted to DNG, and went bad after-ward - which is not necessarily the case: thus a good reason to visually inspect all images after conversion to DNG.
    bruijnesteijn wrote:
    Software:
    No other software
    *iff* it is certain that raw image (raw-rendering, as distinguished from jpeg preview), was OK, before accessing via Lightroom, the other software is a non-factor.
    bruijnesteijn wrote:
    Calibration display:
    XRITE i1 display pro
    I am a bit confused why a calibration file would get off-balance after some time? You need to recalibrate the display once in while, but that's because the display is changing.
    I can understand Lightroom has problems with a corrupted profile, but how can it get corrupted as I would assume it is only read (not written) and why is Photoshop not having these issues?
    My focus is now on recalibration of display to rule out that item
    Not my area of expertise. However, in general, if you're having uncaught disk or hardware problems, or even software bugs, files can become corrupted - not just image files.
    PS - Did the Mac/HW test include the drive where photos are stored?
    Cheers,
    Rob

Maybe you are looking for