Camera RAW settings no saving in Bridge

[fdpryor]

~ Clicking on an image in Bridge, it opens in Camera Raw.

~ Default profile settings are applied to the image.

~ Clicking the "Done" button is supposed to 1. close the image back into Bridge and 2. SAVE the settings just made in Camer RAW to that image. Hovering over the Done button even explains this behavior. 

But that doesn't happen. The image closes and in Bridge it reverts to the color profile it had when it was captured. 

Brand new M1 Mac Mini and a brand new current install of Bridge and Photoshop installed through Adobe Creative Cloud.

[S_Gans]

Camera Raw edits are non-destructive, which means it never changes an original image. The indication that an edit was made, is shown with the little icon I highlighted below. Is this showing up for you? If you double click it, do you see what's been edited in the Camera Raw settings? Or, is this simply not showing up?

[fdpryor]

The user profile is not saving to the image. Not being associated with it. Specifically tonal and color balance tweaks specific to the particular set I'm working on do not remain associated with the image when the "Done" button is clicked. This is counter to the expected behavior, which is the behavior of the application up to this point and also counter to the behavior specified in the Tool Tips when you hover over the Done Button.

[TheDigitalDog]

In addition to the last answer, keep in mind there is some wonky behavior in ACR hosted by Bridge on M1 that isn't the case when Photoshop hosts ACR (new masking for one). This has to do with Bridge not yet being updated for M1 as PS has.

You might want to avoid using ACR hosted by Bridge until this is rectified.

[fdpryor]

As Bridge is critical to my workflow, this is not a preferred option.

[TheDigitalDog]

As Bridge is critical to my workflow, this is not a preferred option.

By @fdpryor

And that's fine, but with your M1, you can and should expect some issues. You can pretty much forget using Mask Subject, Sky, etc; it IS broken. Not the case when hosted in Photoshop. If such masking is critical to your workflow, then you better find another host.

[fdpryor]

The vast majority of the time all I'm doing in CR is applying a User Preset. Color balance (established from a grey/white/black target on set), and capture-stage sharpening. Critical, but nothing fancy. All the masking is done down stream in Photoshop on an Intel Mac Pro running Catalina.

Because Bridge stopped working on the capture station (it was an older machine running High Sierra) I had to get a Mac Mini to replace it. That's where I noticed the behavior in the current combinatio of ACR/Bridge.