I did some more testing, and it seems like an OBS problem, not the plugin. Manually muting and dragging the volume control does the same thing.I'm a little bit behind now - 1.20.1, compared to yesterday's 1.21.1 - so this might have been fixed already. Or it could be a problem in OBS and not the plugin. Anyway, I noticed that an audio source fade over 0.50 seconds has a pronounced "zipper" effect. I think I counted 5 distinct pops over that time. (Adv. SS is running every 50ms) Mute/unmute has a single pop that sounds about the same.
So I'm back to wondering now about the reliability of network comms in Adv. SS, given that WebSockets from one copy to another on the same machine is not reliable. If the sending part of Adv. SS is fine, and the transport is fine, and only the receiving part of Adv. SS needs work, then using Ardour for the receiving end might be okay? Not sure how to test that theory without a debugging environment.
Anyway, for controlling Ardour, other DAW's, physical consoles, and other audio tools, what would you think of adding support for OSC? Commands first, ignoring the response, then possibly eventually adding the response later as a condition.
I ended up writing a command-line utility to send OSC commands over UDP to a specific IP:port, all of which comes as arguments, so now I can control a Behringer X32 console from the Run action in Adv. SS, but it would be more convenient to have OSC built into Adv. SS.
@Warmuptill I can PM you the source for that utility if you'd like to use it for a starting point. It's pared down from a GUI app with wxWidgets that also controls that board, so it still has some remnants of that, but it should still be readable enough.