-
1. Re: Bridge CS5 doesn't see changes made by LR3
Ian Lyons Sep 12, 2010 2:15 PM (in response to deedeecz)By default the adjustments are only saved to the Lr catalog. To be seen by Bridge you must save the settings back to the original file (keystrokes Cmd/Ctrl+S).
-
2. Re: Bridge CS5 doesn't see changes made by LR3
deedeecz Sep 12, 2010 2:45 PM (in response to Ian Lyons)Hey, thanks for a prompt answer. It seems that I have a bigger problem on my hands now. Somehow, I applied "auto tone" in the Develop module in LR to a bunch of images in different folders(which significantly overexposed the images). I don't even know how I did it!!! Is there a way to track down what I did and reverse the process?
-
3. Re: Bridge CS5 doesn't see changes made by LR3
Ian Lyons Sep 12, 2010 3:02 PM (in response to deedeecz)You haven't mentioned whether the image had previous adjustments or not. If they didn't then Reset should fix the problem. However, if the images already had settings which you don't want to lose you've and you've already closed the application and lost the ability to use Undo then it's likely that the fix is a tad labour intensive. In Develop module, select an image from filmstrip then go back one step (more if needed) in History list (left side panel). You'll need to do this for each image that had Auto Tone wrongly applied.
-
4. Re: Bridge CS5 doesn't see changes made by LR3
deedeecz Sep 12, 2010 3:16 PM (in response to Ian Lyons)UPDATE: Nevermind, I think I accidentaly clicked "Auto Tone" in the Quick Develop pane in the LIBRARY module and that messed up a looooooot of images. I went to the top folder for all my images, selected all images and clicked "tone" in the Develop mdule with "auto sync" on ans that fixed it Coming back to the original thread though, If I hook up my hard drive with images to another computer with LR3 installed, it won't see the changes I've made on my computer until I copy the catalog folder onto the new machine - is this correct?
-
5. Re: Bridge CS5 doesn't see changes made by LR3
deedeecz Sep 13, 2010 8:16 AM (in response to Ian Lyons)May I ask what is your routine in regards to this matter? Do you usually save the settings back to the original file or just leave it in the LR catalog?
-
6. Re: Bridge CS5 doesn't see changes made by LR3
Ian Lyons Sep 13, 2010 9:19 AM (in response to deedeecz)deedeecz wrote:
May I ask what is your routine in regards to this matter? Do you usually save the settings back to the original file or just leave it in the LR catalog?
Your original question was:
When I make changes to the NEF files in LR3 in the DEVELOP module, Bridge doesn't see it. Must I develop NEFs to other format first for bridge to pick up the changes?
The answer to that question hasn't changed - save the settings back to the original file - Bridge cannot read the catalog. If I want Bridge to see the adjustments or metadata applied in Lightroom I have no other choice but to save the settings back...
-
7. Re: Bridge CS5 doesn't see changes made by LR3
deedeecz Sep 13, 2010 1:02 PM (in response to Ian Lyons)I did what you suggested ctrl + s in LR but the image hasn't chnged in Bridge Instead, 2 small, round grey icons appeared in the upper right corner of the image in bridge(one for cropping and one dor levels). The image itself hasn't chnaged.
-
8. Re: Bridge CS5 doesn't see changes made by LR3
Ian Lyons Sep 13, 2010 1:20 PM (in response to deedeecz)The two badges tell you that what you did in Lightroom has been written to the raw file. However, if Bridge is not reflecting these changes it will very probably be because the default view in Bridge is use the embedded preview. This is used for speed but means that it doesn't actually show how the image really looks within Adobe applications. Fortunately, this is easily fixed - switch the Bridge previews to High Quality as shown in below screen shot. The downside of using High Quality is that Bridge will be slower (much slower) at rendering previews for your thumbnails
-
9. Re: Bridge CS5 doesn't see changes made by LR3
deedeecz Sep 13, 2010 1:26 PM (in response to Ian Lyons)Excellent! Thank you very much.



