Stereo Tool

Stereo Tool 7.71 BETA013

Windows 32 bit:
Windows stand alone: http://www.stereotool.com/download/ster ... 71-013.exe
Winamp DSP: http://www.stereotool.com/download/dsp_ ... 71-013.exe
Windows 32 bit VST: http://www.stereotool.com/download/vst_ ... 71-013.dll

Issues reported by DJ_DOGGY should now all be solved. Note: Junk around tones is still there if you enable Sparkling Highs without Protect Tones enabled. But that's intentional. Enable Protect Tones to get rid of it.

CHANGES:
- Attempt to reduce effect on volume of using Leif's clipping method.
- Fix DJ Doggy's reported errors (19 kHz, junk around tones).
- Ignore frequencies above a specific frequency -> Should lower TOTAL CPU load by another 10-20% (now fully implemented except at lower Quality settings)

OLD CHANGES:
- Fixed the lowpass bug that was introduced in 009. Although it has probably always been there! As a side effect, the output is also slightly louder (about 0.02 dB) with no negative effects.
- Fixed distortion introduced in 009/010. Extra highs are still there though! See new 'Sparkling highs' section under Advanced Clipper -> Sound
- Fix optimizations
- Fix code #warnings
- Improved highs filtering in Clipper (both Composite and Normal); sound has more brilliance and suffers much less from ducking on loud sounds.
- Fix bug: NAN's can occur at certain input sample rates (40960 Hz among others)
- Fixed downsampling/resampling issues.
- Made several changes to the Clipper that affect the sound! Sound should now be more open en brighter (but it might have more distortion in some cases, I hope not though).
- CPU: Added 'Ignore high frequencies above'.
- Big Composite Clipper CPU load improvement: Added a new slider ('Oversampling Quality' or something like that); CPU load reduction is HUGE and effect on peak control (for values above 4) seems very small.
- Solved a number of warnings that I added in the last few days
- Some small optimizations
- New Highs Gap Protection improved, now similar in behavior to the old one. I had to add 1 extra step (slightly higher CPU load).
- Fixed problems in 771-004. Some optimizations are disabled - I need to fix that.
- Fix CPU measurement for high loads (jumps to 95% for unknown reason). -> Showing real average instead of median now. Median in dark red.
- Difference in measured CPU load is bigger than expected after CPU load measurement update - check why - DONE, is indeed big! Separate slider added to show both processing and total CPU usage.
- CPU: Clipper: Reduced default number of Bass Clipper steps from 4 to 1
- CPU: Clipper: Implemented Leif's mirrorring method for Stokkemask and optimized steps using Omnia interface, much fewer steps for same result.
- Added option to add a text in the title bar to easily recognize multiple instances.
- EXCEPTION OCCURRED IN HttpServer: Got unknown widget ID.
- CPU: Clipper: Highs gap protection: Use 1 step for non-FM.
- Check if COMMON_STATIC still improves performance, if not remove it -> Does not, removed.
- Redesigned parameter classes and moved everything around for integration with other products.
- Remove Stokkemask mode for non-composite FM clipper (it's probably not working correctly and more heavy than the composite clipper)
- Fixed small bug in Composite clipper FM overhead level compensation calculation. Might make the same setting very marginally louder (less than 0.05 dB)
- Fix crash reported in previous post
- Improved CPU load measurement (small part of code wasn't included, it is now).
- CPU: Composite clipper: Optimize Stokkemask: Skipping outer parts of window
- CPU: Composite clipper: Optimize Stokkemask: Fixed 'Skip smoothing' mode to be compliant, all other modes removed.
- CPU: Composite clipper: Optimize Highs Gap Protection (trick from Leif Claesson that he uses in the Omnia.9 - nearly no CPU load needed anymore!)
- CPU: Added some #pragma's to make compiler generate more efficient code
- RDS: Added some character conversions (Euro -> E, ` -> '). (not yet tested)
- GUI: Allow drawing scopes in half-height to have more headroom above and below.

TODO 7.71:
- Fix downsampling and Quality slider problems: Lower Quality setting
- Turning "Bandpass" Highpass filter OFF doesn't really turn it off (!)
- Optimize Chain function: Move stuff to ProcessingChain if possible.
- Remove "Take some shortcuts" under CPU, probably broken! And has not much effect anyway. -> Hm, no, must have been in use for the tests. Ugh... TEST to check what is better: ON (which will probably allow more sounds through) or OFF.
- Synchronization is broken in 008 (was ok in 007)
- Another bug in latest beta - ST doesn't remember FM settings - presets from the fm list start up with stereo and rds encoding off
- Fix MPX display sample rate issue
- Fix Stokkemask in Leif's mode with Quality < 3
- VST multiple instances fails
- Make VST window bigger
- Fix Mac VST version (not recognized apparently)
- Fix Linux version (someone mentioned that it crashes after a few minutes, on Ubuntu 14.04)
- Clipper highs improvement
- GUI integration for Multiband?
- Instability in compressor behavior [WesKeene, Bojcha]

TODO:
- Noise learning Micha
- Change default preset (it still uses Classic compressor etc!)
- EQ with 'standard' sliders.
- Make BS412-like graph for levels
- Add 'warm' noise before clipper (requested by Andrew Palmquist, might help with PPM as well)
- CPU: Clipper: Optimize Advanced Bass Distortion Protection

TO DO WITH LEIF:
- Clipper issues Leif / Wolf Stahl (probably the same thing)

Meters frozen.

_________________
control point
control point2

Same here. Scopes work. No meters.

Same here with the meters.

But same as before for the "Ignore freqs" issue. Unwanted signal that appears in bottom is still there.

Rebuilding now for meters. I will try to reproduce that 'Ignore freqs' issue again - I have seen it in the past but yesterday when I was testing I didn't see it anymore. Not sure why... At what frequency did you set it here?

I don`t know. May be when you test , forgot to apply any signal ? Because without signal , this issue is not there.

Just saying , This is the only way not to see it .

Edit : I set it to the lowest possible - 16000 . And this bad signal is exactly on 16000 Hz
If you set it 18000 , it will be at 18000 but with lower amplitude.

Stereo Tool 7.71 BETA014

Windows 32 bit:
Windows stand alone: http://www.stereotool.com/download/ster ... 71-014.exe
Winamp DSP: http://www.stereotool.com/download/dsp_ ... 71-014.exe
Windows 32 bit VST: http://www.stereotool.com/download/vst_ ... 71-014.dll


CHANGES:
Meters working again.

OLD CHANGES:
- Attempt to reduce effect on volume of using Leif's clipping method.
- Fix DJ Doggy's reported errors (19 kHz, junk around tones).
- Ignore frequencies above a specific frequency -> Should lower TOTAL CPU load by another 10-20% (now fully implemented except at lower Quality settings)
- Fixed the lowpass bug that was introduced in 009. Although it has probably always been there! As a side effect, the output is also slightly louder (about 0.02 dB) with no negative effects.
- Fixed distortion introduced in 009/010. Extra highs are still there though! See new 'Sparkling highs' section under Advanced Clipper -> Sound
- Fix optimizations
- Fix code #warnings
- Improved highs filtering in Clipper (both Composite and Normal); sound has more brilliance and suffers much less from ducking on loud sounds.
- Fix bug: NAN's can occur at certain input sample rates (40960 Hz among others)
- Fixed downsampling/resampling issues.
- Made several changes to the Clipper that affect the sound! Sound should now be more open en brighter (but it might have more distortion in some cases, I hope not though).
- CPU: Added 'Ignore high frequencies above'.
- Big Composite Clipper CPU load improvement: Added a new slider ('Oversampling Quality' or something like that); CPU load reduction is HUGE and effect on peak control (for values above 4) seems very small.
- Solved a number of warnings that I added in the last few days
- Some small optimizations
- New Highs Gap Protection improved, now similar in behavior to the old one. I had to add 1 extra step (slightly higher CPU load).
- Fixed problems in 771-004. Some optimizations are disabled - I need to fix that.
- Fix CPU measurement for high loads (jumps to 95% for unknown reason). -> Showing real average instead of median now. Median in dark red.
- Difference in measured CPU load is bigger than expected after CPU load measurement update - check why - DONE, is indeed big! Separate slider added to show both processing and total CPU usage.
- CPU: Clipper: Reduced default number of Bass Clipper steps from 4 to 1
- CPU: Clipper: Implemented Leif's mirrorring method for Stokkemask and optimized steps using Omnia interface, much fewer steps for same result.
- Added option to add a text in the title bar to easily recognize multiple instances.
- EXCEPTION OCCURRED IN HttpServer: Got unknown widget ID.
- CPU: Clipper: Highs gap protection: Use 1 step for non-FM.
- Check if COMMON_STATIC still improves performance, if not remove it -> Does not, removed.
- Redesigned parameter classes and moved everything around for integration with other products.
- Remove Stokkemask mode for non-composite FM clipper (it's probably not working correctly and more heavy than the composite clipper)
- Fixed small bug in Composite clipper FM overhead level compensation calculation. Might make the same setting very marginally louder (less than 0.05 dB)
- Fix crash reported in previous post
- Improved CPU load measurement (small part of code wasn't included, it is now).
- CPU: Composite clipper: Optimize Stokkemask: Skipping outer parts of window
- CPU: Composite clipper: Optimize Stokkemask: Fixed 'Skip smoothing' mode to be compliant, all other modes removed.
- CPU: Composite clipper: Optimize Highs Gap Protection (trick from Leif Claesson that he uses in the Omnia.9 - nearly no CPU load needed anymore!)
- CPU: Added some #pragma's to make compiler generate more efficient code
- RDS: Added some character conversions (Euro -> E, ` -> '). (not yet tested)
- GUI: Allow drawing scopes in half-height to have more headroom above and below.

TODO 7.71:
- Fix downsampling and Quality slider problems: Lower Quality setting
- Turning "Bandpass" Highpass filter OFF doesn't really turn it off (!)
- Optimize Chain function: Move stuff to ProcessingChain if possible.
- Remove "Take some shortcuts" under CPU, probably broken! And has not much effect anyway. -> Hm, no, must have been in use for the tests. Ugh... TEST to check what is better: ON (which will probably allow more sounds through) or OFF.
- Synchronization is broken in 008 (was ok in 007)
- Another bug in latest beta - ST doesn't remember FM settings - presets from the fm list start up with stereo and rds encoding off
- Fix MPX display sample rate issue
- Fix Stokkemask in Leif's mode with Quality < 3
- VST multiple instances fails
- Make VST window bigger
- Fix Mac VST version (not recognized apparently)
- Fix Linux version (someone mentioned that it crashes after a few minutes, on Ubuntu 14.04)
- Clipper highs improvement
- GUI integration for Multiband?
- Instability in compressor behavior [WesKeene, Bojcha]

TODO:
- Noise learning Micha
- Change default preset (it still uses Classic compressor etc!)
- EQ with 'standard' sliders.
- Make BS412-like graph for levels
- Add 'warm' noise before clipper (requested by Andrew Palmquist, might help with PPM as well)
- CPU: Clipper: Optimize Advanced Bass Distortion Protection

TO DO WITH LEIF:
- Clipper issues Leif / Wolf Stahl (probably the same thing)

Ok I managed to reproduce it again now. Apparently it also disappears if you set the lowpass filter far away from this freq (which I did yesterday when I tested it to make sure that I would see it).

Edit: Whoops! There was a bug in my lowpass-filter code (which has been there forever, but normally the peak would be at 22.050 or 24 kHz and far less big). I've fixed it and the spike is reduced by 22 dB now, there's still something there though so there must be another bug somewhere.

Edit: I can't get rid of it completely it seems, but you shouldn't be using frequencies this close to the maximum used frequency anyway (ignore above 16 kHz with 15.5 kHz audio), so in normal use it should never be a problem.

Great !

I guess the rest of problem is in the "Ignore freqs" code .

Doggy, what signal you put on input?

_________________
control point
control point2