@Gotchakaboomba I haven't tested on as many images as you, but instead I tried applying the new Adaptive profile to event images that I was halfway through editing (to provide me with a direct before and after comparison) and since I prefer to edit towards a more flat target (not unrealistic HDR, but rather just more shadow and highlight detail than one usually gets with fill flash event images) and I was hoping that the Adaptive profile would work in my favor.  Unfortunately, it falls short.  I agree with your detailed observations.  One consistent artifact I'm encountering is a weird tonal shift between the edges of objects.  For example, between someone's face and the contrasty background lighting.  Applying the Adaptive profile not only reduces that contrast as expected, but also adds a weird flat gray "haze" across the faces along the side of the face with the contrasty background lighting.  Folds in clothing and other textures also look more flattened and lose depth (often making the clothing look mottled or stained instead of just lumpy or wavy).  I see these same types of tonal artifacts when using the Shadows/Hightlights tool in Photoshop and always have to push multiple sliders back and forth in the Shadows/Hightlights tool to find a balance in the settings that allows for recovering highlight and shadow while minimizing the tonal artifacts that appear in the modified image.  Since I'm having to do the same with the tonal sliders in ACR with the Adaptive profile for each image, it's not really saving me any editing time at this point.  It has promise though. ... View more

@Philli5CCD  Absolutely!  Using the Bridge to batch embed data in files works well (that's one of the ways I use it) and you can also batch-apply some global corrections (like color balance, exposure, contrast, etc.) to raw files and selected other filetypes like JPEG and TIF using the ACR plug-in.  What you can't batch-apply with the ACR plug-in within Bridge are exposure brush corrections, or create or edit masked selections to people or objects, or use tools like the AI Denoise tool, which can only be applied to each image one-at-a-time, but those are limitations within the ACR plug-in, not Bridge.  ... View more

Exactly!  I was more long-winded with my answer, but @melissapiccone is correct.  The confusion for many users comes from the fact that they only encounter the ACR plug-in from within Bridge, so they conflate the two tools as being the same.  Many folks have no idea that opening a camera raw file from within Photoshop will also launch the exact same ACR plug-in they see in Bridge.   That's why I advocated for watching the great demo videos that Adobe produces to explain features and tools.  Those videos are also helpful for understanding which applications to use for different needs.  I'd never use Photoshop for page layout, but folks do it every day because they don't know that InDesign is a much better tool for that purpose and they don't know that InDesign can also export layouts to JPEG or PNG.   It's a shame that so many people don't understand why Bridge is so useful and what it can do for them. ... View more

@Toastman3000Just to clarify, as explained in the video at the start of this thread, Bridge is a file management tool for the suite of Adobe applications.  Bridge is not an image editing tool.  From within Bridge, you can launch the Adobe Camera Raw (ACR) plug-in, but ACR is technically part of Photoshop.  The editing options available within ACR are essentially the same as with Lightroom (for example, within ACR you can create certain types of masks, apply exposure gradients, change white balance, adjust exposure, apply denoising, etc.), but within a different interface than what you'll see in ACR.  Lightroom is better/faster for making certain types of global edits to batches of files (making it great for event photographers).  It's possible to batch-edit raw files in ACR as well, but the workflow is different and not as efficient for batch editing.  My particular workflow doesn't require batch editing very often. You can also use the ACR tool to make certain types of edits to non-raw format files, but many tools in the ACR plug-in only work with raw files.  That being said, even if you use ACR to make some adjustments to a JPEG or TIF, you can always open that same JPEG again in ACR to revert it back to the default state provided that you didn't make additional changes to that same JPEG in Photoshop or another tool, so it's also non-destructive (to a point). And once you start adding adjustment layers to your image within Photoshop (for example, to composite elements from multiple files), you are already making the sorts of edits not possible directly in ACR or Lightroom. And providing you are creating those adjustment layers correctly, you still have non-destructive editing capabilities in your Photoshop file because those layers can be removed or turned off.   Each application is designed for a different workflow, even if there is some overlap in capabilities.  In Bridge and Lightroom, you can create collections of images and sort files, but Lightroom includes a database feature for managing those collections, whereas Bridge kinda sorta mimics that capability, but not really.  For my particular collaborative workflow, the database capabilities of Lightroom are useless, but the metadata embedding is essential.  However, I work with freelance photographers whose workflows depend on Lightroom and never use Bridge.  In most cases, they are delivering JPEGs to me, so it doesn't matter to me which tools they use to reach that JPEG endpoint. Similarly, you can create vector-format graphics and simple info graphics within the InDesign page layout application, but it's not a replacement for all the features available within Illustrator to create vector-format graphics.  I also see people use Photoshop for page layout and saving their files as PDFs, but it's not at all the same as using InDesign for page layout and exporting as PDF.  Bridge, ACR, Photoshop and Lightroom are designed for different needs.  Adobe makes lots of great videos available that provide overviews for all the different applications and tools which are terrific for seeing how the tools are designed to be used.  More often than not, when I'm cursing at software that's not working the way I want it to when trying a new feature, it turns out that I'm using that feature incorrectly.  Once I've watched the introductory video about that feature, my user experience is usually much improved.  😃 ... View more

Not sure what you're saying here, @Philli5CCD.  Bridge works with all Adobe applications (please view the video at the top of this thread).  One significant, but underappreciated, difference between Bridge and Lightroom for photography workflows is that Bridge allows you to embed metadata directly into supported files (individually or in batches), whereas Lightroom keeps the metadata in a separate location.  I prefer to embed metadata (and have my Adobe Camera Raw [ACR] edits) saved directly into my DNG files because that makes it easier to share my edited and tagged DNG files with co-workers who work in graphics and video and use Photoshop daily, but do not use Lightroom (or have it installed).  Those coworkers don't want to have to learn how to import Lightroom data files and deal with all the additional file directories and supporting files involved, but getting a few DNG files from me isn't a problem and it's easier to share those DNG files via Teams, email, Sharepoint, etc. than trying to do the same with Lightroom. Our workflow also generally uses ACR (launched from Bridge) for editing RAW files individually (or occasionally as two or three nearly identical images) rather than in large batches as Lightroom users typically do for event photography, so I never use Lightoom and instead work with Bridge and Photoshop in tandem.  I'm not a snob about Photoshop vs. Lightroom, BTW.  Lightroom has lots of great tools and features.  It's just not the best tool for my workflow -- especially since I work across a wide range of media and I use Bridge daily for previewing and tagging a variety of files in different formats and then bringing those files into my projects. ... View more

@johnrellis On my M3 Mac, everything works beautifully without any custom GPU settings.  On our Intel Macs at the office and my personal Intel Mac, I've modifed the ACR GPU settings, Photoshop GPU settings, and even tweaked the Bridge "Advanced" tab settings and various Cache settings trying to find a magic combination that works since the corrupted preview image started happening about a month ago for me on the Intel machines.  I'm working event as I respond to this, so I can't check what my current ACR GPU settings are on any of my Intel Macs, but I'm pretty sure at one point I've tried the combination you suggested (thanks for taking the time to do that, BTW). The problems I've encountered after turning off the GPU processing and with different custom settings have included ACR freezing up when making modifications to an image, or the interface lurching around unpredictably.  And within Photoshop, various tools in Photoshop (like the Liquify tool, Transform tool, and SmartObjects just not working after the interface appears for those tools), opened images filling with white blocks as a zoom in and out, clarge hunks of my images being filled with random blocks of noise when using the Legacy Save for Web tool, etc.   Again, my team and I weren't having any of these issues on our Intel Macs until recently.  Can't recall if it started after a macOS update or a Photoshop update.  I'm installing updates constantly on a lot of machines, so it all blurs together. ... View more

As noted in my earlier posts, I've tried every combination of settings for the graphics card within the Photoshop Performance settings.  Nothing I've tried resolves the problem in a way that allows me to use all the Photoshop features and tools as needed on my team's Intel-based Macs (and my personal Intel-based Mac) and I've had to constantly toggle between turning the GPU off and on and off again for routine edits to a single image.   Not having this issue on the one M3-chip Mac I have at the office, but we can't upgrade all our older machines at this time.   ... View more

Yep.  As I've noted, the solutions posted to this thread apply only to Lightroom so I'm still out of luck, so the suggestion that a bad (or non-updated) video driver is the culprit seems to be correct.  Another difference is that when I'm encountering the corruption in ACR, only the large preview is corrupted.  I can make additional edits in ACR (although purely via guesswork) before opening the images and the images are opening intact in Photoshop.  Folks using Lightroom are reporting the corruption in their processed files and not just the preview images. One thing I've tried since my first post last week about this issue has been to completely clear out all my caches via Adobe Bridge.  While it didn't resolve the corrupted previews issue for me*, flushing all my caches appears to have solved a different problem I was having with the AI Denoise tool in ACR (on our Intel chip Macs) that was causing every image to take 20 minutes to process and often failing at the last minute due to some unknown error.  After the cache flush, the same images are taking less than a minute each and (so far) they completing the Denoise process every time again.    *the first few images allowed me to make edits as expected without a corrupted preview, but then the corrupted preview issue re-appeared by the fourth image and every subsequent image until I restarted the Mac. ... View more

I'm having this issue on multple Intel-chip Macs,using ACR rather than Lightroom.  Clearing the cache and other suggestions has been fruitless as a permanent solution.  Turning off the GPU processing resolves the issue for the ACR modifications, but once I'm in Photoshop proper I have to enable GPU processing again in order to make additional edits to images using options such as the Liquify tool.  The constant process of turning the GPU on and off and on and off is a productivity killer.   ... View more

Thanks for your replies.  I've submitted a bug report to Adobe.   My wife is having the same issues with her Intel Mac as well and she's running an earlier version of macOS (Ventura), so that rules out macOS Sonoma as the cause.   ... View more

I appreciate the replies and the suggestions, but I've tried everything including disabling the integrated video card and re-starting the machines between changes to the video and memory settings -- just to be extra vigilant to make sure that I was starting with a clean slate each time.   While disabling the video card can often temporarily resolve the corrupted ACR image preview, as soon as I'm back in Photoshop from ACR and try to use many tools like Liquify and certain Transform and live object edits in my PSD file then I'm out of luck until I re-check the box in the Photoshop Settings panel to use the video card again.  That's created a serious productivity hit having to constantly turn the video card back on and off dozens of times. This happens with our work Intel Macs (which have all sorts of corporate-mandated software running in the background that I cannot disable because they are managed machines) and with my personal Intel Mac at home (which has different security products installed and running in the background) and I have complete Admin management on.   ... View more

I'm only seeing this on our Intel Macs and only in the last month or so after one of the ACR updates was pushed out.  We have 64 GB of RAM on most of those Intel Macs.  Restarting doesn't help.  Closing everything but Photoshop and Bridge doesn't help.  Changing memory allocation and video driver settings doesn't improve the situation.  Not having any problems with my M3 chip Mac, so it seems as if the developers have made some change to ACR that doesn't play well with the Intel-based Macs.  We are not in a position to replace multiple Intel-based Macs for several years, so this is a serious problem for us.   ... View more

As of a few months ago, my coworkers and I started having problems on our Intel-chip Macs where -- when editing raw-format images in Adobe Camera Raw (ACR) -- the image preview displays in a corrupted manner making it very hard to apply edits and preview edits in real time (see screen shot).  This is not happening when using ACR on my new M3-chip MacBook Pro.  The actual raw files are not corrupted and open just fine and the edits applied in ACR are showing up as applied when the files are opened in Photoshop or exported from ACR to other formats.  It's only the working preview image that is displaying as corrupted and this happens with DNG files and with native camera files (CR2, NEF, etc.) and only when using ACR on Macs with Intel-chips like the Core i9.  I've tried cycling through the different video card options (OpenGL and the like) to see if turning things on/off would resolve the problem on those Macs.  I've also tried changing my memory allocation and scratch disk settings.  No joy. The initial view of the selected images is fine.  The corrupted preview image happens only after non-exposure changes are made (for example, using the scaling/crop tool or the tools for correcting parallax).  This seems to be a bug with ACR where it wasn't tested adequately on with non M-series Macs. Is anyone else running into this?     corrupted ACR preview on Intel-chip Mac ... View more

It would still be nicer if that toolbar were dockable or appear as a contextual option across the top of the screen.  It's goofy that this particular tool doesn't behave like the rest of the Photoshop UI.  And once it's enabled again for one image you're editing, it remains enabled and floating over your other images as well until it's hidden/disabled again -- unlike the other docked and tabbed palettes that remain in place and off to the side once you're done with them.  (Of course there are a bunch of other tools in Photoshop that don't behave consistently either...but they don't hover over my images continually.) ... View more

@Weavedweller  It sounds as though you are conflating Adobe Camera Raw (ACR) with Bridge.  Bridge is used across the suite of Adobe products, not just with Photoshop.  Exposure settings are found within ACR when you select the option in Bridge to open a file in "Camera Raw". All the Raw editing tools (and more) are still in ACR, but the UX for ACR (several versions ago) migrated most of the tools into expanding drop-down palettes that you have to toggle open and closed.  It's a bit of a pain to constantly have to toggle between the palettes that I need and it appears that some controls are getting shuffled around between panels (or getting a different interface) whenever there's an ACR update, but none of the exposure adjustment tools have gone away. ... View more

Honestly, I'd love having the ability again to open multiple instances of Bridge -- not just the content windows.  For example, I used to be able to view the metadata panel for different folders simultaneously by having multiple instances of Bridge running.  This allowed me to view, compare, copy, and paste data from from related photo shoots.  For instance, shooting photos of a series of speakers at a conference on day 1 and then on day 2 photographing those same speakers making different presentations.  By having two instances of Bridge running on two different monitors, it allowed me visually scan through the images and metadata fields for day 1, match up people speaking on day 2 and then copy and paste their names and titles into the appropriate fields for day 2.  Now with Bridge 2023 I have to constantly navigate back and forth between folders with the ability to only see the metadata for one folder at a time.  This change has added HOURS my workflow. Not to mention that Bridge 2023 is much slower than the earlier versions and extremely buggy (for example, batch selecting and embedding data such as descriptions and titles into camera raw format files usually fails straight away or will generate a message indicating that Bridge is writing to the files, but when you click on the individual files once the "writing to the files" is complete, the metadata just added will not actually be in the files).  Honestly, I could go on for hours about all the things that are broken in the 2023 Bridge.  I have the exact same problems on multiple machines and I'm seriously considering alernatives.  Bridge used to be one of my favorite and most reliable tools.   ... View more

The current Bridge (2023) is unusable.  I'm running it on multiple machines and experiencing the same problems: VERY SLOW Metadata tagging is essentially impossible now.  While I can batch embed my templated info without issue, when I go to batch-embed fields like Keywords, or Headline, or Sublocation, etc. into DNG files, Bridge will just stall and stall and eventually I'll see the "Writing metadata" status at the bottom, but after a few minutes the text I added into any or all the fields will just go blank and nothing will actually have been embedded. When I use the tab key to move down the fields, pressing the tab key will occasionally randomly move the cursor and active field UP rather than down Persistent text shows up in some fields.  For example, I'll batch embed a Title in a folder of 400 DNG files.  Then move to a completely different project folder and select an image (or batch-select several images) to update the metadata and while the most of the other fields will show the metadata for the new file, the Title field will often show the Title for the previous project and won't let me embed or replace the Title with new text until I force-quite Bridge and navigate back to that folder Batch re-naming files in even a small folder with 30 or 40 images used to be immediate.  Now it will take 5 minutes or longer and frequently does not recognize or follow the preferences in the dialog box for where to save the newly renamed files.  For example, I may tell Bridge to copy the re-named files to a different folder, but Bridge will just re-name everything in the source folder regardless. Right now, I have a folder of 400+ images for which I've batch-tagged with a set of keywords (all images = same keywords) and when going back to batch-select specific images (in this case, different speakers at a podium), Bridge is telling me that the multiple files I've selected have different keywords and will not allow me to enter the additional name keyword.  If I select each individual image, I can see the same set of keywords in each image and append the additional name keyword, but only one-at-a-time.  I used to be able to batch-select dozens of images with identical keywords and see the list of keywords.  Now I can't.  And this is not a matter of there being an extra space or typo somewhere that makes Bridge think the content is different.  These are all images batch selected and batch tagged as a group in a single pass. I could go on with all sorts of things like this which are broken in Bridge 2023 and worked in all prior versions.  I'm VERY frustrated. ... View more