clipper_from_oz wrote in post #18306594
thought I would update this thread (as I did for another thread) regarding Lightroom Brush tool slowdowns
"On the weekend I decided to again carefully compare Lightroom and PS ACR regarding bad brush lag/slowdown but this time I used the export as a smart object/File option in Lightroom export.
In previous tests I had either converted the Lightroom RAW with brush edits to a TIFF and then further edited in PS ACR or alternatively exported an unedited Lightroom RAW to PS and recreated the brush tool edits in PS ACR from scratch similar to how I had done this in Lightroom ACR . On both of these tests PS showed very little brush tool lag or spinning ball behaviour which pointed back to Lightroom being the culprit.
Anyway this new Lightroom resource Test i decided to try had me exporting the Lightroom RAW files( with multiple brush tools that lagged badly) as a smart object/ file to PS. Then ffter importing to PS I opened file as a smart file in PS ACR. Opening as a smart object/file meant that the brushes and edits created in Lightroom also appeared in PS RAW. ANd this is where the similarity finished. The difference of performance was like light and day. PS ACR had absolutely minimum lag with all brushes operating perfectly ....not only this but there was no regular spinning beach ball or hanging till changes initiated caught up with themselves on the subsequent screen render . In addition to this whilst I was running PS I had lightroom still open and various other apps so it appeared RAM and GPU and app optimization/prioritization were all working as they should.
Ive passed this on to Adobe engineering today ( That PS ACR handles exactly same RAW file /edit config perfectly ) and hopefully they can now focus on getting some patches done ASAP rgds
Just got below email back a few Mins ago from Adobe Level 2 Tech support guy who is handling my case. Looks like there are other subscribers also dealing with engineering over this tool Brush lagging mess "Hi Kevin
Thank you so much for your Observation on the same. We have already sent your request to Engineering and they might add you in Pre-Release for upcoming versions of Lightroom. We are very much aware about the issue and has received quite a few request from other subscribers as well. I apologize for the inconvenience caused, Hopefully it will be resolved in forth coming version of Lightroom.
XXXXXXXXXX| Sr. Technical Support Consultant | Customer & Employee Experience | Adobe Systems, Inc. |
Clipper the simplest way to open an image in ACR, complete with your LR editing would be to write the Metadata to file. This can be found under the Metadata menu option, or using Ctrl/Cmd+S. This will write the edits of the selected image(s) to a .XMP file. If you then go to Bridge you will see the edits applied to that image in the browser, and when you open it in ACR you can't tell that it was previously edited in LR.
If you do edit in ACR, when it writes the data to the .xmp file and you go back to LR, LR will see that it was edited in another program and flag the image. If you click the flag it will ask you if you want to read from the .xmp and update the image in LR, or write the original data that is in the LR catalogue back to the .xmp.
This could be a useful workaround for those occasions where you need to do lots and lots of work with local brushes, if ACR is not suffering from slowdowns.