Intermittent, unpredictable inability to add or apply edits to metadata fields such as IPTC Core using Adobe Bridge 12.0.2 and preceding 12.0.1.246 release. This is particularly unacceptable when editing metadata of multiple selected images. Worse yet, there is no error message generated! You must check file by file, metadata field by field, to see if the edit was applied. This seems to persist in certain image files but not others.

When only one file has metadata added or edited metadata, clicking the lower right corner “Apply” icon results in either:
1. the added or edited metadata disappear from the field after a few seconds and the metadata is not changed, or
2. the added or edited metadata remains visible and the metadata is actually changed.

Reverting back to Bridge 11.1.3.200 seems to eliminate the problem. Added or edited metadata are applied to the XMP sidecar file(s).

Is this a bug in how Bridge caches writes to the XMP files?

Windows File Explorer file shows all the XMP file attributes are either N or A. None of the XMP files are Read Only. All the XMP files seem readable and intact in Notepad. All the image files tried are Sony ARW files, both compressed and uncompressed.

Windows information for the machine: Windows 10 Pro version 21H2 OS Build 19044.1766 with Windows Feature Experience Pack 120.2212.4180.0

Adobe Bridge CC 2021 11.0.0.83
macOS 11.01 (also macOS 10.14 and 10.15)

Reporting this as I cannot find any documentation that indicates this should not work.

If I add a custom Metadata Extension view.xml that contains any of the following three Dublin Core properties I am unable to edit and save a metadata template.

name="dc:title"
name="dc:description"
name="dc:creator"

if data is already present in any of these when editing the template from the Tools menu an error dialog pops up reporting "The operation could not be completed" for the following actions:

1. Editing the existing data and coming out of the property field (tab or clicking)
2. Adding/editing data to any other property fields and clicking Save

This error is reproducible using the Sample Extension provided as part of the Adobe XMP SDK.

It seems to be View related as I can clear down any addtional schema definitions from the SDK example and leave only the custom View code containing these properties in the View.xml file.

Conversely I can leave custom schema properties in the View.xml, removing the problematic ones and everything works as expected.

Given the exampe provided by Adobe has one of these fields specifically shown as a custom view example I feel this should work as documented.

Thanks

There is an error in METADATA panel, DATE CREATED line that appears for all my video files rendered in Premiere Pro and After Effects. No matter what codec or container they are rendered to - the date created is set to five days in advance. For example - I have created a file today (2020-07-28), but Bridge is trying to convince me I have rendered it on August 2nd, which will be next Saturday.
I am a Windows user, and all my other software, including Windows File Properties tab show correct creation date, only the bridge fails to recognize it.
Even when I import those files into AE or Premiere Pro, the correct date is displayed in Project tabs.
I have found exif file property - Encoded time which is set to 08-02, so maybe the problem isn't in Bridge, but AE/PP related.
However, it is a bit frustrating because it sometimes complicates the search and organization of files.
Any suggestion would be helpful.
Thanks in advance.

Bridge Version 10.0.1.126
Windows 10 Pro

How to reproduce:
Modify GPS position in the Metadata in Bridge. Click another field. Confirm Apply. Check the photo in Faststone Image Viewer by hovering the mouse at the right and then clicking on the Go to Google Maps button to see if it took. The attached lighthouse is on the east side of the island but the coordinates that come up in Faststone Image Viewer are still the original wrong coordinates. Correct coordinates are 46,8.4322N 62,30.0139W.

Expected result: the applied coordinates would update the JPG file.
Actual results: Bridge remembers the new coordinates but does not apply them to the JPG file.