Copy link to clipboard
Copied
Adding keywords to JPG files within Bridge now creates unwanted XMP files for some reason. I want the information to remain within the image file itself like it has in the past. I've reinstalled Bridge and tried on my laptop with same results. Anyone have a solution for this frustrating situation?
Copy link to clipboard
Copied
Which Operating System and which version of Bridge?
Copy link to clipboard
Copied
Sonoma 14.4.1 and Bridge 2024.
Copy link to clipboard
Copied
Sorry, not a MAC user but is there anything here which may help?https://community.adobe.com/t5/bridge-discussions/how-to-stop-creating-xml-files-for-regular-jpeg-im...
Copy link to clipboard
Copied
Thanks, Erik. Looks like this might be a bit too involved for me to get into at the moment. I'm a standin for a Photoshop Pro for the next few weeks while she's out of town, so I don't want to be fooling around with specs we've set up to maintain her protocol for consistency. I've downloaded that newer plugin, though, and plan to look into all this and install after she returns. Thanks for the link - Not sure how I didn't find that one myself! Have a great weekend.
Copy link to clipboard
Copied
The problem is still here since June. I discovered after many tests that Camera Raw is involved when using AI, everytime when you edit your files after export it will creat this xmp.
Copy link to clipboard
Copied
Hi @clevelanddesign , @DGGT,
Thank you for reporting the issue. We apologize for the inconvenience caused.
The additional XMP file you observe is created when changing or applying metadata to any JPG/JPEG file containing Content Credentials. This behavior change was recently introduced due to Content Credentials support in Camera Raw release (version 16.3).
We're actively working to investigate this issue and will keep you posted on updates around this.
Please refer to the article: https://helpx.adobe.com/bridge/kb/xmp-file-jpeg.html for more details and a workaround.
Thanks,
Bridge team
Copy link to clipboard
Copied
Hi,
The fix for the issue is available in the latest updates of Adobe Bridge 15.0 and ACR 17.0.
We would love for you to try it out and share your feedback.
For more details about the release, please refer to:
Regards,
Bridge Team