Watermark 3 Pro will not run on PS 23.5 / Windows 11

mlaterz

UPDATE 2 - Tried turning on a 1 px stroke for the text watermark and the batch run just quits on the first image. Is there a plan to fix this bug?
UPDATE 1 - I changed to source & target folders are the same, removed the stroke from the font of the text watermark and removed text from Copyright Notice. It now works. Not really fast but I can live with it, for now. Anyway, something in those selections is buggy. Support feedback would be appreciated. TIA.
ORIGINAL - I just purchased Watermark Pro 3. I have PS 23.5 on Windows 11. I set the plugin up to batch run a set of PNG to PNG files (identified and verified the input for a text logo with a 1px stroke; no image resize, sharpening or action applied, etc. When I press run, it seems to start on the first file, then nothing. No output, no message. Please advise. TIA.

Thomas

Hi,

can you please post screenshots of all the settings you made in the plugin?
What's the dimension of your source images?

mlaterz

Thomas images sizes range from 1700-1300 to 4700-2400 pixels. screenshots coming.

mlaterz

Thomas

mlaterz

Thanks. I can't reproduce that the batch is not running when stroke is checked. But I can reproduce that if PNG is selected as output format and the source file is quite large it can take very long to save the file (a minute and more!) and it may seem that the plugin and PS froze. There may be a better (faster) algorithm to save as PNG. I need to look into this more.

Can you please try the following:
1) Choose PNG as output format with large source files (maybe choose only 3 so it doesn't took forever), click on "Run Batch" and give it some time to see if it only takes very long and this is the issue.
2) Choose another output format (PNG/PSD) with the same other settings and see if it works.

mlaterz

Thomas --- OK - I assume with Add Stroke checked.

mlaterz

No Go - with Add Stroke checked neither png to png nor png to jpg work. images sizes approx. 3000-1800. I gave each attempt 5 to 7 minutes.

Thomas

mlaterz I tested multiple scenarios but can't reproduce it here. Can you send me some of the PNG's you are trying to watermark to thomas at pixelsucht dot net
Also a short screenvideo would help me to see what exactly is going on. Thanks.

Thomas

mlaterz Can you please also try to choose another font.

mlaterz

I sent an email a copy of one of the test images. --- Email:
I changed the font to a standard font, Arial Bold MT, color white; checked Add Stroke, 1 px, color black. Everything else remained the same [as the screen shots above.]. Attached is one of three images in the test folder; all three have the same attributes as this one. NOTE: Before I checked Add Stroke, but after I changed font, I ran a test and the plugin worked fine.

Thanks for your help.

Mike LaTerz

Thomas

mlaterz

It's possible that you created a preset with the custom font, then the font was uninstalled/disabled and you loaded the preset again?
So the plugin tried to run with a font that was not installed and this caused the problem.

mlaterz

Thomas No. No such scenario. The fonts have not changed. I created the presets after the problem was discovered.

Thomas

NOTE: Before I checked Add Stroke, but after I changed font, I ran a test and the plugin worked fine.

I do not quite understand, so now everything works?

mlaterz

Thomas No. The problem remains, no matter what font I use. When I select Add Stroke, the Batch will not run. --- You asked if there were any changes to fonts, in coordination with setting presets. My answer is there were no changes to fonts. I simply selected a standard font and ran the test first without Add Stroke selected which worked normal. Then, I selected Add Stroke, same problem - the batch does not run.

Thomas

mlaterz Ok. I also can't reproduce it with your PNG. Strange. Can I take a look with TeamViewer? If so please download it from https://www.teamviewer.com/ start it look for the ID and Password and send it to me by mail.

mlaterz

All set. Thank you, Thomas. Well done!

Thomas

The problem could be solved by uninstalling and reinstalling the plugin from the Creative Cloud App.