Stereo Tool

The beta turned off Bass Boost and Loudness by default, even though the preset I had loaded had them enabled. Might check that behavior. Still checking to see if there are other problems.

VST hangs too, although CPU usage isn't all that high here.

O you're right. I added a separate box to enable Loudness but forgot to add backward compatibility.
Bass boost is odd though - I didn't change anything there. But I'll check it.

Problem is that in some cases I'm writing data to elements that don't exist anymore (for example, FM synchronization data in the stand alone version caused the hanging in that version). Don't know yet what the problem in the VST version is. I guess I should try to add something to find these bugs when compiling instead of when the software is running. But that isn't that easy...

Stand alone version that doesn't hang: http://www.stereotool.com/download/ster ... 3-053A.exe

Will look into the VST hangup and Loudness (and Bass Boost?) load issue later.

Hans, did you also set all use of the former "Loudness" as a item for registration?

I get a warning here using my default settings with Loudness on +1.5 dB

Ah, that. I don't expect too much improvement from removing it, and it's too much work for now - however I'll make sure that everything I design from now on will take this into account. And I'm definitely converting Loudness (which is already nearly converted) and Hard Limit soon - because a big customer is requesting a new feature that requires me to change it. Those two happen to be some of the easiest ones to convert.
Cannot only be CPU load related, must be a real bug... (Once you click the X, the window updating should stop immediately). I'll try what happens if I run it on 1 core (you have 1 core right?) and check the code.
Not always? Does this happen with specific file types? (I'm guessing .wav and .flac files, NOT .mp3 files)
There's no way Windows can ever see an STS file unless you dragged it to or opened it in Winamp yourself. So I'll assume that this is a user error for now...

Hm yes. The old behavior was actually sort of a "bug". Because at low values in the old interface it was almost impossible to see whether Loudness was enabled or disabled, I didn't detect it in my registration code if the Loudness value was really low. But this did allow people who noticed this (including you apparently) to use Loudness without paying for it. That 'loophole' is now fixed... Sorry

I'll send you a PM.

VST version works fine here; I may have fixed something when I fixed the stand alone version. Will build it again & post it here.

Loudness (Advanced clipper) is indeed off when i load preset from previous betas where it was enabled.