Stereo Tool

Phoenix: True, it doesn't happen with ASIO. But currently ASIO is only supported in the stand alone version...
Hm.... All the non-text string settings SHOULD BE stored by the VST host. I have some parameters (RDS text etc.) that are very difficult to encode using the VST interface, that's why I'm putting those in the .INI file.

The problem with putting other values in the INI file as well is that if you use multiple ST instances, they would share the same ini file and hence revert to each others settings.

Can you explain what goes wrong exactly? And is this specific for Stereo Tool or does it happen in other VST plugins as well?

One note:
De-Esser - Different (default) settings needed for FM mode, non-FM mode and non-FM mode with pre-emphasis, for same effect.

For example:
- FM mode = 65536
- Non-FM mode = ~21849
- Non-FM mode (with 15us pre-emphasis) = ~30041

- Replace current filtering by bass clipping in each clipper step? Or at least lower the number of filtering steps. (Lower CPU usage and better "S" protection expected). ■ DONE

Winamp DSP plugin: http://www.stereotool.com/download/dsp_ ... 510-65.exe
Stand alone version: http://www.stereotool.com/download/ster ... 510-65.exe
VST version: http://www.stereotool.com/download/vst_ ... 510-65.dll
VST version (No SSE2): http://www.stereotool.com/download/vst_ ... 510-65.dll
Command line version: http://www.stereotool.com/download/ster ... 510-65.exe
Linux command line version: http://www.stereotool.com/download/ster ... BETA510-65 (not available)
Linux GUI version: http://www.stereotool.com/download/ster ... BETA510-65 (not available)

By default, the less strict filtering (which uses a lot less CPU processing power) is selected. But it's (a bit) less strict.

I'm not sure which version sounds better. The less strict version does - as I expected - better preserve the bass during loud 'S' sounds, which is good. I expect slightly more highs distortion caused by loud bass sounds (because the bass isn't lowered as strictly, and later in the process), but when comparing the audio between the two versions the difference appears to be very small. So I'm not really sure. The new (less strict, less CPU intensive) clipping method is definitely good enough to select as default setting, as most users will probably not really be interested in extremely strict bass clipping.

Bojcha, what do you mean by 'same effect'?

I'm basically using this de-esser to protect low and mid frequencies against really loud highs. That should normally not even be needed for non-preemphasized audio.
If you want to lower those highs (as an extra processing step, not to protect the mids and lows), then you do need to change the setting (also depending on how high Loudness is set).

Is that what you mean, or am I overlooking something?


By the way, is it just me or are there really too much highs in the FM Europe Stereo preset? Or is the de-esser ruining things? Some time ago I adjusted the settings to get close to the Orban sound in frequency content (which you requested if I recall correctly), but now - at least for some tracks - it just seems overdone, and the highs are constantly really loud (for example Beyonce - Halo). I should add that for many other tracks it sounds good... (but I normally like really loud highs. So if even I start to think it's too much it's probably a lot too much).

De-Esser
In FM mode i can see "black" reduction at default 65536
But if FM mode is disabled, there is not reduction at all, so settings must be lower (if de-esser is needed)

I still have beta64 at transmitter site, and tested CPU usage for "Stric" On and OFF

ON ~32%
OFF ~30%
-----------

About new sliders
First, sliders "Highs vs Lows" There you adjust freq for bass Strict and not in "from 0 upto.."
Anyway, all that sliders can be removed,
- "highs vs lows" adjusted to 350/750
- "From 0 upto" adjusted to 350 and removed.
- Clip lowest bass fro 0 up to Default 150Hz and removed
- "Then Rize AT" 350Hz and removed
- "Clip highs feedback" and "but never reduce bass below" default settings and removed.

That's just what i think.

Am I the only one using VST plugin here? It's surprising no one here has ever encountered what I do? For I'm pretty certain there's no nag in my setup. Hans, I'd elaborate what exactly I mean. Let's say I open a file in a wave editor. I resample it to 192 KHz using the wave editor's resampler. So it's a non-live effect wherein Windows resampler doesnot come into picture(anyways I use ASIO output from the editor). Now I try using VST plugin(I'm NOT using any FM Processing). The sound I get is similiar to a cassette player playing a track faster than the normal speed. And this effect varies with the sampling rate. So, 48KHz sounds less chirpier than 192 KHz. And on the other hand if I resampled to 32 KHz, a female voice sounds like Darth Vader. Now this wasn't the case with ST 5.02. Well I'd not say something's wrong but I expected Stereo Tool VST to behave in pretty much the same way as some other VST plugins (like Wave or Ozone iZotope) do. In other VST plugins the last used settings in the same session come preloaded. Whereas ST reverts to defaults in the same session each time it's invoked. I primarily use Audition(ST doesnot work in it now) and SoundForge. Anyways this was more of an ancillary request which you can well ignore.
It's the resampling thing that actually needs attention(presuming everything's good at my end).
For most cases it does sound good on tracks which have a warm, groovy bass. A track which has a loud, slamming bass or a part which has shrill tones, it does sound annoying. It's largely because of the equalizer in MB I guess. I keep it disabled anyways for I use ST to transcode files. Not certain what FM pundits would have to say about it.

_________________
visit website

There IS bit more highs, better will be with just EQ before mb.

Agree

_________________
Sexy Girls in your city

Tested Beta65 standalone, in 512 latency mode, the highs are filtered differently. Looks like 6 KHz LPF.

Hi,
Staying objective to your post, would like to know are you using an inbuilt preset or a custom preset which was saved from an older beta release of stereo tool. Please double check if the 'Allow louder highs' parameter in that preset has a huge negative value. If it' so you've to re-improvise it I guess. Something I experienced first hand.

Regards,
phoenix

_________________
visit website