Hi, @PORTRET, the problem I'm having with your problem is my awareness that Bridge doesn't "DO" anything with an image. That is, it looks at the image and presents it to the viewer. The one thing above the same action that, say, an email does is that it also views any metadata the image may have. By that, I mean if you open a JPG in Adobe Camera Raw and make some changes, and then send that image in an email, the recipient will see the image as it originally was because email applications do not have the ability to see the changes. [If you want others who do not have Adobe image products to see the changes, you need to resave the changed JPG into a new JPG from within ACR, Photoshop, or Lightroom and then send it to others.]
So, when you say that Bridge is causing this, it's like saying that when you store your images in a drawer upstairs and Fred pulls them out, there are scratches, but when Mary pulls the images out in a downstairs cabinet, there are no scratches; it's obviously Fred's fault. My question is, how are the photos stored? I suspect that it's how your images are stored that may be contributing to this.
Keep in mind that Bridge was not designed to work on NAS drives, only directly connected drives. It's possible that your Intel Arc 750 GPU computer is not as good a match to work with NAS drives as the other system. And, like the drawer upstairs that you've been blaming Fred for damaging the photos, it's the drawer that's causing the damage.
To sum up, obviously, there is damage, but I think you need to do more investigation. Bridge can only show what it is given to show and does not interact with the photos
1
Reply
AdChoices
