Stereo Tool

Fine feature, sounds really good, specially on headphones! (didn't tested it on speakers yet, don't use FM)

While on the topic of stereo enhancement, I note a recent article which touched on this issue of "too much stereo" for today's earbud & headphone-wearing set. One pull-quote:
For the record, count me under the "can't get enough stereo".

NY Times article: http://www.nytimes.com/2014/01/13/busin ... tereo.html

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

Changes:
Redesigned Simple Clipper. CPU load *should* be lower.

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)


Feedback still wanted for this:
(*) To solve problems with mono FM reception (or mono listening, for example if someone plays a stream on a phone), the following is now possible:
- Enable Stereo Image with default settings (it will do nothing)
- Lower the 'Image phase amplifier maximum angle' slider. This will reduce sounds in anti-phase that would cause audio cancellation when reception is mono! The lower you set it the better mono reception will sound (but at some point you might still get some artifacts, and the stereo effect gets somewhat reduced).

`im not see any issue with the simple clipper but let`s see now.
Also not seeing any lower load.without any processing ( enabled only AGC, MB and simple clipper +FM panel) looks like i see 1-2% more load . With previous beta was 16% with sometimes changing to 17% , now is 18 and sometimes jumps to 22 . This is with GUI down to the tray. i don`t know what is goin on. Simple clipper was good anyway.

P.S: Oh no! New "redesign" causes more distortion , see.. this tilt not exist in previous beta.this is the space after 15000 Hz to pilot signal.

Rollback to beta13... don`t like this picture...

Confirmed, lower Cpu at about 3-5%

_________________
Sexy Girls in your city

Chris , are you sure you look at ST load ? 3-5% . This is not true at all. even that i see about between 1 and 2% increase

Picture from beta13 . see, no tilt

yes.. i dont see Upper Cpu. its a bit lower.

_________________
Sexy Girls in your city

I can't see anything wrong in last beta.

_________________
Urban Junglist

Simple clipper is NOT suitable for FM!!!

Hans , i`m not saying what is suitable , but show the difference only . New disign has distortion that is showed on my pictures. both are Simple clipper.
I don`t understand is this purposely to make Simple clipper this way? Cause this distort was not exist before. I will not use new betas till this problem is clear again . It should not be there.

@dj_szpajda : You don`t see anything wrong ?
What clipper do you use ? i see it`s Advanced , not Simple . Show us picture with Simple one. Then go back to beta13 and see the difference with Simple clipper at 100% slider both betas