Stereo Tool

Hmmm... OK. I'm just trying to get some boom out, and thought I might've found a bug...

Actually you both wrong....partially
I wanted to ask same question, and many other question.. but i am still waiting 6.20 to be done.

Anyway...
a) i found that slider not needed!
b) it works from 0-300Hz (always)! and it kills those freqs. totally at "0"
c) other sliders are more important just need to be done little more different.

a) because it works before final bass level, so it can be easy boosted again later in next filters. Most important sliders are "After Punch clip it bellow" and "Never Dynamically raise bass level above". THERE should be ALL: highs, voice vibration, and other sounds detection, to lower bass when needed. That's why happens "punch holes" !
But if detection for highs is on "After Punch clip it bellow", "Punch holes" *should* be gone"
Ofcourse Clip start and end freq. are important too, for strict clip bass.

Jesse can explain this better then me, how this should work.. if he wants.

BETA062:
Some more declipper improvements.
- Until now, the declipper only looked at the current block of data (4096 samples or even less) to determine if clipping occurs and where it does. Added a mode with history. And you can now choose between looking at the short time result, long time result, the minimum of the two (very greedy) or the maximum of the two (very conservative, default setting). In this last mode you can lower the level of the long term result, which might be useful if too many samples are not detected.
- In most cases, if clipping occurs the histogram of samples has an area on the top that sticks out. *IF* tilt detection functions properly, this area should be more or less symmetrical. If it's not, you can now select the filter to make it symmetrical, which means that less samples will be considered to be clipped. This should work perfectly for most tracks, but it results in some missed clipping for tracks like the Metallica track (equalizer used AFTER clipping, determining tilt is not possible).

I've changed some default values to better match the new behavior. I have optimized it for conservative behavior - this means that for normal clipping it works perfectly, but very few other samples will be marked as clipped. For the Metallica track it means that in some cases not all clipping is recovered.

For more aggressive restoring:
- Disable 'Forcibly make restored samples higher than original clipped samples'
- Disable 'Only detect symmetrical clipping'

For VERY aggressive restoring:
- Also replace 'both' by 'either'

If you're not using MP3s, set 'MP3 additional sample removal - nr of samples' to 0.

I think that it's safe (and if it is, it is definitely better) to enable 'No declipping when tilt cannot be determined'. Will run some tests to confirm this tomorrow.

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

TODO:
- Fix loading changed multiband frequencies
- Add buffer and filter for SCA output (SCA1 ok, SCA2 ok)
- Finish AGC improvement - make mono value configurable (replace checkbox by slider) 1 hour --> NO, not needed - anything else needed? -> NO
- Fix Punch
- Check what to do with new filters (such as bass AGC) - keep them, remove them, change them? --> KEEP
- Save new BASS_AGC setting in VST mode
- Loudness: Annoying cracking sound in bass. Slightly present in 5.00, worse in 6.00, maybe even worse in 6.10. Only when bass is too loud. Much worse than in Final Limiter (at same input level!) - so this clearly indicates a bug. Most likely cause: The filter that was added to remove bass artifacts....... - No, it's the louder bass. But it can be fixed by changing some settings. Default settings updated, and behavior for 'not Very strict' improved. Also Deep bass boost and Very deep bass protection are enabled for latency 512 now.
- Fix crash at program close
- Fix VST plugin version (does not run)
- Dynamically drop 'Allow louder highs, even if it causes vibrations' to 0 when bass filter suspects noticeable voice vibrations. 1-2 hours
- Reduce Loudness CPU load days?
- Check and remove static variables
- Finish new de-essing filter (check what to do with the settings, remove at least some!) 1 day
- Convert Multiband input to MONO, then use arrays [2][4096] --> should give speedup. - FAILED
- Natural Dynamics: Fix or remove transient boost
- Natural Dynamics: Add expected + strength slider per band
- Finish declipping filter (clipping level detection + level reduction in dB). 1. Figure out why removal of unwanted frequencies causes flat lines at high quality setting with small overlap. This causes distortion, with this fixed repairs are MUCH better. 2. Fix MP3 correction, automatically scale down when this deteriorates the sound. --> TOP part fails!
- Declipping filter: Fix low latency behavior
- Always oversample clipping (configurable)
- Declipping filter: Change detection at lower input levels.
- "Test Right Channel" in "FM Transmitter Calibration" does not work since v6.10 (standalone) (bojcha)
- Declipper window close function - check! - Seems ok
- Scopes black background?
- Add AGC start level
- Declipping filter: Add comparting of sample history to make sure loud bursts are still detected properly (now, with 16 blocks of history, 65 samples are removed even when ignoring just 0.1%). I should also check the current block (probably with a margin of a factor 2).
- Declipping filter: Use reliability of tilt detection to determine movement speed; slowly move to default tilt (configurable!)
- Declipping filter: Far too many samples are marked as 'maybe/probably' clipped. Histogram not used or not cleared?
- Declipping filter: Optimize tilt detection for performance. SSE2 for maximum. And keep separate smaller histograms to determine the maximum (should perform much better).
- Declipping filter: Cleaned histogram must be mirrorred. After cleanup, mirror center is place where SIGMA above == SIGMA below! Only use on the lower end. Then run cleanup again! The result should contain approximately the same amount of data above and below. If not, that indicates incorrect detection.
- Declipping filter: Add a long term histogram, and use maximum of short term and long term start clipping level detection.
- Declipping filter: Check if 'No declipping when tilt cannot be determined' can safely be turned on.
- Declipping filter: Add setting and saving of new sliders (history size, percentage of highest samples to drop, tilt detection range start, end and precision)
- Declipping filter: Optimize peak matching for performance: Move determination to extra preprocessing step; try to change if statements to min/max or something.
- RDS issue reported here: viewtopic.php?f=15&t=3703&p=11524#p11524 partially solved
- Natural Dynamics: Voices, especially in chorus, still sound weird.
- Natural Dynamics: Smooth out different bands more to reduce low-bitrate-MP3-like sounds.
- Natural Dynamics: Optimize situation with no interaction between bands for performance.
- Update presets? (BASS_AGC etc.) 1 day
- Finish blind interface
- Channels L/R swap in stand alone version when changing filtering/quality (?) (eldoradofm)
- Move pre-emphasis to end of processing 1 day
- Save all new settings, also through VST interface
- Change version number 1 hour
- Release 1 hour
- Add lowpass filter for stereo signal (will cause a lot of extra latency!) - it might be possible to avoid this latency using a Hilbert transform
- Add smarter clipping detection. Maybe something much simpler suffices: Current clipping detection with threshold + flat line detection
- Declipping filter: Automatically override the 3 clipping level sliders if the clipping level is detected very clearly (clear thin spike in sample value histogram). - NONSENSE, this is already done by the histogram function. But it can be made a BIT better - I think - by automatically LOWERING the 'always clipped' slider if a lot of data is present at the highest few bins (but care is needed for DBN - Jack is Back like tracks)
- Declipping filter: Create a new histogram after declipping, clean up and subtract from original.

i think i more like declipper from beta 60 and 61.

beta062: For metalica track short term is better. or "both" but with long term at x0.10-0.20.

Bojcha, can you tell me what's better in BETA060/061? The declipping is a bit more greedy there (although it should be possible to get a very similar behavior in BETA062 by turning the symmetrical checkbox off, and setting the MP3 level back to 75% where it was before, and possibly by switching to short term level detection).

The whole idea of this new version is to avoid unnecessary repairs, such as in DBN - Jack is Back. In the tracks that I checked (including MP3 files) it looks like ALL the clipping is being caught in version 062, with very little false positives. But in some cases (mainly Metallica-like tracks) there will indeed be more clipping left than in versions 060/061 - unless you change the settings.


Note: I have a BETA063 coming up where more settings can be changed (they were hard coded before).

That's what i said ..
With beta062 i need to set "short term".. to get similar as beta61.
It's true that beta062 is less greedy, i checked metalica track with beta061 .. and declipper is perfectly tuned for that track (btw awesome declip!).. with beta062 i just need to set "short term" OR "both" but with "Long term x0.20".

I also checked "Jack is Back" with beta061 (i love that track because it's good for testing presets and how's actually bass comes out!)...
Little boost on bass but it's OK. i'll check with beta062.. but if it's same then again beta061 is better.

Checked.. Really less bass boost with beta062 (almost none), and that second drum is less distorted..
Then it's better Just "Short term" instead both.

Ah ok. Tracks like the Metallica track however are probably very rare, and if I have to choose default settings I think I should try to keep already good tracks (DBN - Jack is Back) unaltered rather than getting the best possible output for (I expect) VERY rare tracks like this Metallica track.

The big question here is: Are there many OTHER tracks out there which also sound better in BETA061? If not I prefer staying on the safe side. If there are, I'll have to agree and switch to BETA061-like processing (preferably NOT by only looking at the short term, but by turning Symmetrical off, which seems to have a comparable result).

I agree, safe side is always better... and yes turning Symmetrical off is closer to betaa061.

I can just listen some tracks and report.

Is "Never consider samples...lower then: too low at -18dB ?
i just found one track where declipper actually ruin track.. but with this setting at -9dB all is ok.

edit: ah, cannot be at -9 .. at least -15... but actually -18 is good.

edit2:
- Interesting track for declipper http://www8.zippyshare.com/v/34663179/file.html
- This one have that short drum (or whatever it is) and trought declipper stand too much and sound like 'crack' thttp://www13.zippyshare.com/v/45839823/file.html
- This one is impossible to solve (?) (start of song) Ke$ha Your Love Is My Drug - Just lower input and it's good.
- Next is nice done http://www2.zippyshare.com/v/62319466/file.html / http://www15.zippyshare.com/v/6731210/file.html
- damn .. why they use this square samples - http://www11.zippyshare.com/v/15817308/file.html

wow @ "Welcome To My Hood" that's sooooo bad.