Stereo Tool

I'm using WatchCat for batch processing many wav files with stereo tool. WatchCat accepts my stereo tool key and there is no warning. I activated nothing unlicensed that I'm aware of. The preset works in stereo tool without an issue.
Where to look for what causes it to beep? There is exactly one input, one output and no processing chain, which I understand doesn't require a WatchCat license.
I'm running it with Wine. Is that an issue? Can you build a Linux version of WatchCat as well?

Interesting. I think the only thing that beeps is the Declipper, whereas the rest have a voice message (though I could be wrong). Are you licensed for the declipper? Can you try to export the preset from ST once more with the repair section unchecked and see if it still occurs?

I asked Hans, and he said only the Declipper and Delossifier beep (the latter a higher pitch). So make sure those are off entirely before re-exporting your preset. If it still beeps, there must be something wrong with how it's storing the license.

edit: Ah, it could very well be the paths system being messed up by WINE.
What version of Watchcat is being used?

This issue seems to appear quite random. For the last few runs, this didn't happen again. Always with the same preset that is, so that's not the issue here. I noticed, that WatchCat has issues moving or deleting the processed samples, though. Might be a wine problem and is no big deal as long as the processing works.

Could you at least put a visual warning in WatchCat, alerting that is currently processing audio without a license? That would prevent me from wasting time and resources, just to notice only afterwards that something went wrong.

I've posited this idea to Hans.

In the meantime, what version of Watchcat are you using?

It's the windows version I downloaded recently. It says:
WatchCat Version 2.0.14 (build 2d478b3) / build date Oct 5 2024

Hi. So, I've no updates other than learning that it's less trivial than I was assuming to port WatchCat to Linux.

However, since you're processing wavs, and also on Linux (and therefore likely have Terminal experience), have you considered writing a bash script for the Linux command line version? This might be the most effective way to go about it until you end up having to process something compressed.

EDIT: quote Tom in Discord:
Again, not quite as good as a GUI app, but increasing the functionality of the command-line version should help Linux users or those who know how to use a Terminal.

That would be great indeed. Of course, command line is good enough for batch processing purposes.