Stereo Tool

Its enabled on Loudness and highpass is 50-16100

" Supafly Inc - Catch Me When I'm Falling " is a track that makes cuts (mutes) ... try it on FM.

_________________
Sexy Girls in your city

I checked that track with your preset ... all good...

- even if i set highpass from 50 to 30Hz.
- even if i set post-amp from 0.92 to 1.00
- even if i set "composite limiter" from 100 to 105%

So definitely ST is not problem.

Ask Camclone to measure your deviation.

I am sure 400 % that he is overmodulating..

75 khz are enough for stereotool , believe me!
i sound as loud as 180 and 200 khz stations...and i play at 75 khz!

THE LATEST versions of stereotool are the cleanest and the loudest FM sound processor in the world ( if used with a clean spectrum soundcard.. )
I have tested and streched all sound processors made by ..humans


IT IS TIME FOR A HARDWARE STEREOTOOL VERSION !
FORGET BREAKAWAY AND MBL blabllablablalbla..

xD

@camclone

Might be a good idea to make a high pass filter.
From what I know is that most of the outputs of the soundcard on the MB's is being fed with single rail Voltage. Bassically it means that it gets +5 Volt or +12 Volt fed and the output is at half of this when there is no audio. They normally place a capacitor and a resistor to GND to remove the DC component.
I've personally seen some weird results when using low Q capacitors, mismatching impedance etc.

My personal opinion would be to get a circuit after that with an opamp that has a simple high pass filter and is being fed by a symmetrical power supply (+12V and -12V for example). That way you almost have a 0 Ohm output impedance and you can get controlled DC removal.
http://www.electronics-tutorials.ws/fil ... ter_6.html

Excellent presentation! thanks!

Maiby stereotool finnaly SHOULD have an extra DC blocker after the MPX clipper ...for people like me who ...wanna have loudness and max bass ...and 100% stable frequency at FM !

thanks anyway for that special program called... stereotool
i hope to see it in hardware box like orban omnia soon!

Agreeeeeeee!!!!!! 10000%.... i also need high Bass and high Loudness ON

_________________
Sexy Girls in your city

Adding a DC remover AFTER Stereo Tool won't work because if there IS an offset, the whole waveform will be shifted outside the -75 kHz/+75 kHz area.

What might be possible is to build a highpass filter into every Loudness step (there already IS a lowpass filter there).

But actually that shouldn't be needed either, if both the highpass filter and 'forcibly remove...' are enabled. Because Loudness can in that case never add more DC offset than what's already there. (Times the Loudness setting, that is).

(Transport: TODO list from page 32):

What remains for version 5.10:
- Disable separate pre-emphasis and relaxed clipping when FM processing is enabled. It's currently too confusing. ■ DONE
- Remove remaining spikes -> behavior is incorrect, it should partially maintain spikes that are really big (= difficult to get rid of). ---> Looking into this I found that I need to do something very different, and I also need to do that for normal (non-web based) processing: ■ DONE
- Add 'maximum mirror reflection' and make it configurable. ■ DONE
- Add an extra slower Hard Limit phase, or let the volume come up slower when the peaks get really loud, to avoid bass artifacts in xylophone sounds. Easy to do where hard_limit_volume[] is used. ■ DONE
- Also fix the singleband behavior (AGC style on/off). ■ DONE, default is OFF again, built-in presets with Loudness get ON
- Fix Loudness distortion caused by louder bass and lower highs. ■ DONE
- Use 'large file mode' for command line version. ■ BUSY, waiting for reply ■ DONE
- Fix hangups for switching between Singleband AGC/non-AGC switching. ■ DONE
- Save all new settings to disk (INI and VST): 'maximum mirror reflection', 'multiband constant frequency', ... ■ DONE (?)
- Reduce Loudness window height a bit. ■ DONE (?)
- Fix Punch artifacts ■ DONE
- Fix 'dirty punch' due to different handling of the very deep lows and deep lows. -> Must follow Lowpass filter settings. ■ DONE
- Attempt to make bass filtering below 90% more strict in Loudness ■ DONE
- Enforce limiting strictness even if Punch is enabled. ■ DONE
- (Optional) add FM hiss filter - removes FM hiss from input signal, useful for re-transmitting ■ DONE
- Fix Very deep bass distortion protection artifacts (or remove it) ■ DONE - not perfect but won't get better than this
- Set Allow louder lows to +10000 (or remove it) ■ DONE
- Fix settings in presets to closer match modern CD sound (less highs etc.), using the Median display. ■ BUSY
- Fix Allow louder highs behavior. Attempt to replace it by a highs AGC. And rename to de-esser. ■ DONE
- Test what happens if I (constantly) allow more distortion! ■ DONE
- Move strictness to lowest freqs only? Currently audio is also kept below configured midlow level (100%) instead of below configured verylow level (90%). ■ DONE, using separate settings instead now -> Low freq area is still needed for voice vibrations!
- Check if voice vibration filter can be set much softer due to strict bass clipping. ■ DONE, no... But since it's not needed to also reduce the bass during Punch it's not too bad.
- Replace current filtering by bass clipping in each clipper step? (Lower CPU usage and better "S" protection expected). 1 day + testing + waiting for feedback
- Make VST version working again on all hosts! 2 days?
- Update FM presets for louder highs ■ BUSY 2 hours
- Check which 'New Loudness bass processing' sliders must be kept, and place them at correct location. 1 hour, but wait for feedback first
- Display de-esser and voice vibration filter effects 1 hour, to find correct location
- Check the new presets (including Bojcha's). 1 day
- Check and add good new presets (also in the 'share your settings' forum). 1 day
- Loading and saving new setting in STS file 1 hour
- Loading and saving new setting in VST plugin 1 hour
- Release 5.10
- UPDATE DOCUMENTATION

Later:
- Protect Multiband against steep valleys
- 192 kHz FM output
- 400 Hz tone, Bessel null tones? [eldoradofm]
- Stable scope (see viewtopic.php?f=14&t=2726&start=10 . Probably solution is to find the loudest tone, with boost for the lows, and then lock to that).

Beta50 (non-Michi !!! ) still crashing Acon Effect Chainer.
I have tried hundreds of (most free) VST plugins with the Acon chainer.
No problems (except some very rare exceptions - AIXcoustic Electri-Q is the only one I remember) with any other VST plugin (32 bit VST2.X).
The only problem that occurs from time to time is, that it is impossible to move buttons or sliders for many (most or all ?) plugins created with Synth Edit and/or Synth Maker (not sure if both or only one of these).
So if Stereo Tool crashes the Acon chainer then there is still something completely wrong in the code for the VST version.
IMO this should (must) be fixed before a release of version 5.10 (or an alternative release without VST version) !
As part (an addition) to Flat Frequency Response option ?
Or as an individual option ?
Anyway.
It should be an option (and not a fixed unchangeable setting).
If you change the GUI text from "FLAT FREQUENCY RESPONSE" to "FFR" then there is enough space to place it as an individual option.
Especially in conjunction with a new detailed and up to date documentation every (new !) user that wants to go into details will know what the shortcut FFR means.
It is problem that until now the new options for loudness cannot be saved.
It would be better to release a RC version (based on the last beta) with all options (and saving !) as the final 5.10 release version (except built-in selected community presets).
And then one or two week deadline to give users the oppurtunity to update their own shared presets (based on older versions with other options !!!) to the new capabilities of the RC (final release 5.10) version.
It is not good (odd) to release a new version with built-in community presets (created with older versions with different options than the release version).

For all expert users a full-featured RC version has no disadvantage (no need to wait desperately for the official public 5.10, because the RC has everything except the selected community presets).
The advantage is a clean 5.10 public release (without somehow outdated or suboptimal community presets).


PS: Thank you very much for your special Michi MB Beta50 build !
I had not the time to compare it seriously (in detail) with the standard frequency bands (to tweak the multiband from scratch).
With presets (based on the standard frequency bands) it would be a miracle that the different bands leads to better sound.
Till next weekend I hope to know if it helps (or is nonsense worse than the standard bands ?).

For me the VST problem is not important (no need for it).
The good message is:
I have no problem to use multiple Stereo Tool DSP versions (even without multiple cloned .DLL !) at the same time (it is possible to load the same Stereo Tool .DLL in different DSP slots of my host).
Most of the time I use it to compare different beta versions (of course with multiple .DLL)
The only problem is (was) to identify the different betas.
It would be easier if you name every beta (instead of "5.02") inside the window title bar.
So here is my confession:
I took (and still take) all my criminal energy and patch every installed DSP .DLL with a simple editor (change the title bar info "5.02" to individual "5.10bxy").
And then I copy and paste different builds to different plugin folders.
Is this a crime (to patch the .DLL title bar identification for my private use only !) ?