Quote:
Thanks for the tip. Unfortunately ST is using too many resources on my computer causing Winamp to crash which happened when I was trying a bunch of different presets.
Right now I'll just stick with what I'm using, I don't want to mess up my computer.
I did set the usage to low it still crashes.
This shouldn't be a factor if you can run Win 10. This software works on computers specced as low as Raspberry Pi's, and I recall people running older versions on WinXP. Something else must be going on.
So it's being used as a DSP plugin in Winamp? Version 10.30? That's the primary test platform, so if you happened to find a bug, it needs to be investigated.
There are various versions of the software, such as the Stand-alone app (which requires a little more configuration than the DSP plugin and a virtual device driver to push it through), and there are VST plugins. The plugin versions require a basic license to work without a license nag, but the standalone doesn't, and VBcable is also free.
Still, I wonder if there's something wrong or incorrectly set with the CPU settings in the DSP plugin. When you said you set the usage to low, what exactly did you do?
Try navigating to Application Settings, Resource Usage, Resource Allocation cell, then adjust the processing thread distribution setting to see if it changes. One can distribute the CPU cores individually here as well. There's also the Audio Quality slider as well as the Limit CPU selector. Try dropping one of those to trade some quality for freeing up resources.
Again, this shouldn't be very necessary. My PC is from 2016 and it runs at a mere 7% CPU usage with lots of bells and whistles (though not all). Something else must be happening causing the crashes.