Copy link to clipboard
Copied
Hi,
Since recents updates, Lightroom takes forever to export files with a watermark applied.
I use watermark for years to show my customers the photos online and never had any specific issue when exporting photos with LRC but since recently, when applying a 400Ko watermak, the export takes really really long time.
After some tests, I can confirm it comes from watermark because normal export without watermarks is arround 10x faster than with watermark on.
Sync is not activated.
Copy link to clipboard
Copied
Try disabling GPU in preferences, better?
Copy link to clipboard
Copied
In Performances ?
I'm using an Apple Mini M1
Copy link to clipboard
Copied
See:
https://discussions.apple.com/thread/252854357
Copy link to clipboard
Copied
Thanks, so should I use Graphic Processor instead or Graphic Processor for treating images?
Copy link to clipboard
Copied
Try differing settings, even off; any difference?
Copy link to clipboard
Copied
Nothing changes unfortunately. The only difference is occuring if I export with or without watermark.
Copy link to clipboard
Copied
I have the same issue- tried to export 198 images on Mac cpu hit the roof and wouldn't export. Upgraded to the latest version and tried again, same. Tried 10 images, it made an attempt but no good. I'm trying to deliver images- this is absolutely useless as a program now. these are watermarked
Copy link to clipboard
Copied
I made a brand new watermark- that seems to go much faster- so it looks like the error is converting the old watermarks- still slower than it used to be though
Copy link to clipboard
Copied
I have the same issue. The slowness of the export with watermark is directly proportional to the size of the watermark. If I set it to be a small writing in size 10 or so, it goes super fast, but if I do what I really want to do, which is a large faint watermark, it's SUPER slow. This happens the same with or without GPU. Also, this is happening with a super fast brand new Macbook pro and with a 2 year old macbook pro. It's NOT happening on my PC. It seems that this bug is only with the latest Mac updates.