“it doesn’t work” has to be placed against the experience of X thousand users, none of whom having any problems with a somewhat similar set up.
So “it doesn’t work” is not absolute but really should be qualified as “it doesn’t work with my configuration”
Don’t get me wrong, from your perspective, it’s not useable, and that must be very annoying / frustrating,
What we need to help you to discover is what is it that is different about your (non-working) set up, and say, that of @ed66 ? {Actually , Scaler has never crashed on me since I got it some time ago (Win 10, Live 11) and I use it alongside some chunky plugins.
So we’d like to help, but as above perhaps you could give us a run down on your gear and environment. (Opsys version / video card etc) . Confirm you are loading
Scaler2.vst3 (31,101 Kb long) located in c:\Program Files\Common Files\vst3\scaler .
(added later) For a definitive test, the MD5 checksum is
b0f0a2a91db2c006e805225d608e8f78
You can use Hashcalc at SlavaSoft HashCalc - Hash, CRC, and HMAC Calculator to check this
There is potentially one telling test. Download Cantabile Lite (free) from
https://www.cantabilesoftware.com/free-vst-host
Install and fire it up. In the routing window, rick click and add the plugin
Pick ‘scaler2’ (VST3) from the drop down menu
It should connect to the default audio output, but if not just wire up with the output and main speakers.
Now double click in the plugin box to fire it up
What this will tell us/you definitively whether the problem lies either {1} with Scaler itself with your op system or {2} with the LIVE environment.
This whole op should not take more that 10 minutes or so, which I think is worth it to nail down where the problems lie.