Stereo Tool

Never mind. The presets I used seem to have somehow saved the window size of an older version. The size is correct when loading a fresh instance of the plug-in.
In foobar2000 it works fine, but Reaper also exhibits crackling. Stereo Tool, even the original 6.20, is affected, too. The larger the latency, the more prominent the crackling is. Changing the multicore option has no effect. I'm going to reboot later and repeat the tests.

BETA011:
Fixed some bugs:
- Improved closing/minimizing performance with nod32 (virus scanner). Empty windows *may* be fixed. (If not, the window is now completely empty).
- Clip output button loading/saving was indeed not implemented.
- De-esser setting was not saved in VST version.

Winamp DSP plugin: http://www.stereotool.com/download/dsp_ ... 21-011.exe
Stand alone version: http://www.stereotool.com/download/ster ... 21-011.exe
VST version: http://www.stereotool.com/download/vst_ ... 21-011.dll
VST version (No SSE2): http://www.stereotool.com/download/vst_ ... 21-011.dll
Command line version: http://www.stereotool.com/download/ster ... 21-011.exe
Linux command line version: http://www.stereotool.com/download/ster ... ETA621-011 NOT AVAILABLE
Linux GUI version: http://www.stereotool.com/download/ster ... ETA621-011 NOT AVAILABLE
DECLIPPER Winamp DSP plugin: http://www.stereotool.com/download/dsp_ ... 21-011.exe
DECLIPPER VST version: http://www.stereotool.com/download/vst_ ... 21-011.dll

TODO:
- Create dual core support flag in Audio class
- I need to check if the new thread has the right priority
- Currently I create a thread of each portion of data that arrives, it's probably better to have a single thread process all the data.
- Found a bug in the non-SSE2 version of the clipper. Should be easy to fix.
- Now I have this, it's probably better to use Loudness as limiter of the perfect declipper output instead of the final limiter which is used now, but is less good.
- Convert declipper to use 2 cores as well. - Detection part too
- Fix memory bug in declipper clipping detection.
- Declipper: Combine 2 multicore parts into 1 (avoids an expensive 'join' phase)
- Check if thread priority is copied correctly (also for ASIO threads called from driver level).
- Combine 2 multicore threads into 1. (Move them up 1 level from Audio to Common)
- If needed (hiccups?), make it possible to disable multicore.
- Improved closing/minimizing performance with nod32 (virus scanner). Empty windows *may* be fixed. (If not, the window is now completely empty).
- Clip output button loading/saving was indeed not implemented.
- De-esser setting was not saved in VST version.

Could it be that the programs in which you hear crackle use a very low latency (probably ASIO) output? If so, you probably need to increase the buffer size. Stereo Tool operates on the audio in bursts. It needs - at the highest latency - 2048 new samples, then it starts processing and blocks for a while. Increasing the buffer size should fix this.

Yes it works with other Players. I think you forgot to read my message on the last page. There i write that it is working with adobe audition 3.0.1 perfectly without any crackling!

Yes Big improvement. Minimizing is now very fast and closing stereo tool too.

@eldoradofm (lol I typed 'eldoradiofm'):
I think I've now also fixed the hangup-on-closing issue in the stand alone version. (Not really sure, but I couldn't reproduce it anymore):

Stand alone version: http://www.stereotool.com/download/ster ... 1-011A.exe

hvz, I don't know what you done to achieve that, but before version 6.20, mono material sounded awful in Stereo Tool. It sounded like everything was in a small room with a lot of echo. In version 6.20, all the echo was gone and seems that since 6.21 Beta 9 my mono material now have more crispness and all instruments can be heard more easily. Thank you very much for the amazing work, your program just makes listening music a much better experience. (P.S.: my stereo material always sounded nice, but now it sounds much better too)

Oops, was the same link as before, fixed it now (thanks to eldoradofm for notifying me)

Yes, I use ASIO with a latency of 256 samples. Increasing the latency indeed fixed the problem. Well, since I don't need a low latency when working with the declipper, it's not a big issue for me.

I just discovered (when doing some final performance checks) that the Multicore button only functions in the stand alone version.

-> Now it does. To my surprise, even without it enabled this version performs (slightly) better than 6.20 - I had feared the opposite.