[atouu]

Speed up wine by keeping wineserver running in the background.

The background process has a timeout of 2 minutes and only runs when needed.

Result with moresampler (multithread-synthesis off, multithreading handled by OpenUtau):

Before	After

[stakira]

Could you check if the below is true?

"The entire daemon logic could be replaced by a single call to wineserver --persistent (or wineserver -k + background wineserver) which is the canonical way to keep wineserver alive, rather than spawning a cmd.exe /c timeout process. That eliminates the :: hack, the 120-second arbitrary timeout, and most of the lifecycle management. Alternatively, if the cmd.exe approach is kept, the lock/sleep/Exited-handler dance can be simplified to a Lazy<Process> or Interlocked.CompareExchange pattern that avoids sleeping under a lock."

[atouu]

I chose the cmd.exe approach to not rely on another binary which is wineserver since I'm not sure if wineserver path is guaranteed to be placed next to wine binary and I think adding another preference for it is cumbersome. :: is just a comment in batch, just to display the purpose in process name. Thread.Sleep under a lock is intentional since I noticed that continuing right away after cmd.exe can cause issues, we need to wait for wineserver first. I think Lazy and Interlock is unnecessary.