Stereo Tool

I tested same as you simple clipper and advanced cliper ON , mpx clipper OFF, if anabled looks the same.

_________________
Urban Junglist

What about the Hard limit ? turn it off ! Only Simple clipper and MPX clipper at 100% too.
One more - what CPU you have ? I guess Intel , right ?

hard limit off , intel cpu

_________________
Urban Junglist

Yeah , i knew it.. so remember one thing - AMD sees it all. Nothing is hidden for it .

Ok there was indeed a bug: If the Pre Limiter was not enabled the Adjust Volume slider was ignored!

I've fixed that and rewrote the algorithm a bit further, it's now very close to how it was before but still at a lower CPU load.

dj_szpajda, what software do you use to get this display?

Adobe Audition

_________________
Urban Junglist

Now it`s fair dj_szpajda to test beta14 again with Pre-Limiter off if it was on. And tell us what is the result . If the same like before - i will be right that AMD sees it all .

Windows stand alone: http://www.stereotool.com/download/ster ... 41-015.exe
Winamp DSP: http://www.stereotool.com/download/dsp_ ... 41-015.exe
VST32: http://www.stereotool.com/download/vst_ ... 41-015.dll

Changes:
Attempt #2: Redesigned Simple Clipper. Reduced CPU load.

Older changes:
- Reduced the memory usage
- Fixed most of the Stereo Image artifacts!!! "Deprecated" is removed from the sliders that were marked with it. See (*) for a cool new possibility!
- Removed some more unnecessary steps (AZIMUTH 2x, Stereo Boost 2x). 10 remaining.
Fixed 'Post filter for DC offset' problem.
52. Check CPU load. Start with checking if there's anything left that uses the 'unnecessary steps'. Sevdah Web preset: Data still gets converted 58 times... I think I need to do this one first, it should have some effect on the CPU load. 28 removed - next convert the 2 IIR filters so they can be optimized and the merge/split around it can be removed. I'm not measuring any effect from this though (but it makes the code simpler which is also good)
53. Noise Gate/Stereo Boost: Pre-calculate 1-cos() and sqrt() values.
55. Check MemoryPool behavior for cache improvements -> No effect measured, and might make behavior less constant.
56. Check if we can go in opposite direction for each next step to improve cache.
57. Check if lazy reverse FFT is an option. -> No, difficult and gain does not even seem to be measurable.
58. Created a separate class that performs the processing chain. Currently the same code is repeated twice (once for normal processing, once for low latency processing) - which means that a lot of code is duplicated and it's difficult to add extra chains. Most, not all, of that code is now moved elsewhere. (although the low latency chain is not yet modified, but that should now be relatively easy)

Hans,
Unless you're still uploading the link is broken.