Stereo Tool

New BETA2 is available.
Winamp DSP plugin: http://www.stereotool.com/download/dsp_ ... _BETA2.exe
Stand alone version: http://www.stereotool.com/download/ster ... _BETA2.exe
VST version: http://www.stereotool.com/download/vst_ ... _BETA2.dll


Edit: Just noticed that "Avoid distortion" (Final Limiter) is indeed not working - so there's probably still something wrong. Will check it tomorrow.

Exactly same ...
- Avoid distortion [final-limiter] not working (no sound if ON)
- Reduced CPU Usage [final-limiter] not working (no sound if ON and loudness OFF]
- and same .. http://img202.imageshack.us/img202/8071/stbug3421.jpg

I'm now seeing it here too (dunno why I didn't before). So at least I can now reproduce it. Tomorrow I'll try to find what's causing it.


Edit: I just tried if doubling the memory allocations again (eg. restoring the original allocations) would solve the problem, but it doesn't... - Will try to find out what's wrong tomorrow...

(I don't know if the problem on Bojcha's image is gone - I haven't seen that yet here. New version is uploaded... But it's probably very similar to previous version.)


Geez, I really screwed up. I just found 2 more bugs that are probably both causing problems.

Edit: Both are fixed now. Stand alone (just re-uploaded) version SEEMS ok to me (Avoid Distortion is working now).

Let me type a small explanation of why so much is going wrong in the last few versions.

Every filter in Stereo Tool (and a filter here is an internal Stereo Tool filter, for example Loudness consists of more than 20 different filters internally) needs some memory to store information: Filter parameters, data from the previous block of data for a smooth transition to the new block, volume levels, a Fourier-transformed (frequencies) version of the data, input data, output data etc.

For everything that needs to be stored, the software must request a block of memory to store the information in. So there are hundreds, probably even thousands of blocks of information. They are placed in memory in more or less random order, based on when I request them and where a big enough block of memory is available at that moment.

A few days ago I have reduced the memory usage of many of the filters, because most of them (but not all) were requesting twice as much memory than what is needed in the new setup.

Now here's the problem: If ANY of the blocks that I'm requesting isn't big enough, most of the time I don't get any warnings at all. I'm just writing outside of the block of memory that I requested. Sometimes that's unused memory - in that case either nothing goes wrong or Windows complains. But very often this means that I'm basically overwriting the data of one of the other filters.

If I'm overwriting data of another filter, for that other filter the data that it reads back will basically be random nonsense. And that can lead to all kinds of weird behavior. For example, I could have overwritten a large block of sample data from a previous step (which would lead to clicking etc.). Or I could be overwriting something simple like the lowpass frequency, resulting in very strange behavior.

What makes things even more problematic is that the order in memory is determined also by - for example - the Windows version. So what seems to work fine on one PC might crash or cause strange behavior on another. The Winamp plugin version will behave differently than the stand alone or VST version, and the SSE2 and non-SSE2 versions will also behave differently.

All 3 bugs are gone...
Beside that, many things changed

- sound is seems better ..
- this AGC solution seems better
- sound more constant
- Mem usage was 55MB, now 35MB
- Less CPU usage, from 30% to 28%
- .....

nice...

well I hope the winamp version works well because that's the one that i use..



like the saying goes...never give up..you'll solve the problems it just takes time.

GOOD LUCK.

just got hold of the beta version..( winamp )...going to play with it for a while and then ill report back.

( winamp dsp ) well it sounds good and it has not crashed or anything. so its looking good..still playing with the beta so if i hit problems ill let you know.

well i can confirm that the beta works on my laptop with out stuttering...but I still have to try it on the netbook.

looking good though.