Stereo Tool
https://forums.stereotool.com/

Stereo Tool 7.71 BETA
https://forums.stereotool.com/viewtopic.php?t=6087
Page 1 of 35

Author:  hvz [ Wed Jun 17, 2015 6:09 am ]
Post subject:  Stereo Tool 7.71 BETA

Stereo Tool 7.71 BETA001

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

I've been working the last 2 weeks on performance optimizations, in part together with Leif Claesson (Breakaway/Omnia.9).

No big changes in audio quality (I hope!), but a lot of CPU load optimizations! Mainly in the Composite Clipper (Advanced Clipper as well, but not so much) and Stokkemask filter.

(Composite Clipper with Stokkemask and *New* Highs Gap Protection uses about 30% less CPU power than in version 7.70).

CHANGES:
- 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:
- 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
- CPU: Clipper: Optimize Advanced Bass Distortion Protection
- Fix Mac VST version (not recognized apparently)
- Fix Linux version (someone mentioned that it crashes after a few minutes, on Ubuntu 14.04)
- Instability in compressor behavior [WesKeene, Bojcha]
- 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)
- VST multiple instances fails

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

Author:  mpex2006km [ Wed Jun 17, 2015 9:48 am ]
Post subject:  Re: Stereo Tool 7.71 BETA

Well done Hans. Nice cpu improvements. I have to suggest some things for the new version

1: A way to insert numerical values from the keyboard.
2: Extend composite clipper drive
3: Put a "Difference" button in DC.
4: Make UPspeed and Downspeed , release and attack in AGC.
5: Make Natural Dynamics react less when dynamic material is present and more when less dynamic material is present.

These are some of my ideas.
Thank you very much and keep that wonderful work

Author:  Bojcha [ Wed Jun 17, 2015 8:15 pm ]
Post subject:  Re: Stereo Tool 7.71 BETA

Very nice update. CPU usage much lower in clipper!

Author:  DJ-DOGGY [ Wed Jun 17, 2015 10:45 pm ]
Post subject:  Re: Stereo Tool 7.71 BETA

If you enable the "Stokkemask FM" in advanced clipper , options are still greyed out

Author:  DJMark [ Thu Jun 18, 2015 12:24 am ]
Post subject:  Re: Stereo Tool 7.71 BETA

No Mac betas?

Author:  hvz [ Thu Jun 18, 2015 1:24 am ]
Post subject:  Re: Stereo Tool 7.71 BETA

Quote:
No Mac betas?
No, Mac problem isn't solved yet.

Author:  laroyj [ Thu Jun 18, 2015 1:44 am ]
Post subject:  Re: Stereo Tool 7.71 BETA

don't know how it comes but gets always downloaderror for thes 7.71beta and the 7.70 standalone32bit ?
mislukt - downloadfout (under google chrome)

Author:  weskeene [ Thu Jun 18, 2015 10:48 pm ]
Post subject:  Re: Stereo Tool 7.71 BETA

I started a thread with AGC suggestions here. viewtopic.php?f=16&t=6069

Author:  unnamed [ Fri Jun 19, 2015 10:51 pm ]
Post subject:  Re: Stereo Tool 7.71 BETA

yep - another releases, another betas, another features... but old processing modules has still some lacks of MANDATORY improvements:


bandpass:
- selectable mid/side filter aka monobass (side signal hipass filter with db/octave control, range 0-500hz)

phase rotator:
- parametric eq style controls for phase delay draw line

stereo enh:
- selectable range for boosting (in acr & old boost) - hipass and lowpass filters with db/oct control, not from/to type
- REAL post enhances correliation limiter for preventing out-of-phase problems (with gr meter)

agc:
- peak or rms type (selectable)
- "normal" attack and release times (in .x db/s steps, not .xxxxxxxxxx db/s style)
- real progressive release
- window algorithm
- "normal" sidechain parametric eq (typical 5 bands with freq/octaves/gain control)
- internal itu sidechain filters (selectable) (and light grey visible under main draw line in eq?)
- gate with slowdown and freeze tresholds
- selectable crossover in 2/3 band mode
- "simple" post agc compressor like a "main" agc (feedforward and feedback with paraeq sidechain)
- additional treshold or mix level for bass band would be nice
- new mb coupling/link style (with turn off coupling/link option)

equalizer:
- 5 band standard parametric eq with gain, octave and frequency control.

mb1/mb2:
- selectable option for disable ALL behaviors (interias, shapes, etc...)
- new standard style crossovers for bands with frequency and db/oct slope - like this: http://i.imgur.com/B7C1RFc.png

bassbost:
- selectable pre or post multiband compressor

singleband:
- parametric eq in sidechain...
- disable behaviors option...

fm transmitter:
- new bs412 gain reduction meters like a agc (for compressor, limiter, debasser, deesser)
- bs412 compressor att and rel times in .x db/s steps...
- mpx dbr meter with selectable measure times (1-60 seconds)

GUI:
- MANUAL TYPE INPUT like a modern vst plugins: double left mouse click - input box, single mouse left click with ctrl key pushed - reset to default
- if module isn't active/disabled - grayed module isn't showing in meterings block (for gui appearance improve)
- PROPER module places in meterings block and processing menu (stereo enh over agc, really?)
- not mandatory, but nice: option for more refreshing rate for meterings (like a supersmooth 60fps experience)


my conclusion: FIRST refresh/modif all old modules for "modern" standards/controls/features, then add new...

Author:  Slawomir B. [ Sat Jun 20, 2015 2:26 pm ]
Post subject:  Re: Stereo Tool 7.71 BETA

Well as for the above comments made by unnamed, it's really difficult not to agree with at least some of them. Clearly his main point was to emphasize that it is not only the amount of features which makes a software quality good - it is also the way of delivering them to the end user.

And here are a few major flaws in the GUI only, that affect end-user experience:

1. The modules/sections are ofcourse presentend in an incorrect order (stereo enhancer, phase rotation...), as unnamed said.
2. It is not always clear how each module/section corresponds to the other, since we were never presented with any kind of block diagram (which would be very nice, BTW).
3. The units presented don't always stick to any standard - so yes, db/octave; db/s and so on are welcome everywhere
4. EQ drawing really does appear unprofessional.
5. Ridiculous increments in at least some sliders, e.g. 6.80017 (I believe one or two decimals are enough) don't make things easier for us (it's easier to edit ini file in notepad than to actually use GUI for modifying a number of parameters)
6. ITU-BS412 graph is extremely hard to read.
7. The user can't resize windows from certain sections, which makes them difficult to read and modify (ST adjusts everything by itself, not ncessarily in an optimal way). One aspect of this was mentioned by unnamed too - if the module/section is not in use - instead of being greyed-out it could be hidden.

Additionally, maybe it would be good to change fewer whings at a time, instead of packing a whole bunch of them with every release - it might minimize the risk of some bugs being undiscovered unless the release is already out there.

As for the CPU usage - why, why, why and once again why not use more threads for signal processing? The latency is not that important in most of the cases, since hardly anyone uses processed sound for on-air monitoring anyway.

Regards,
Slawomir

Page 1 of 35 All times are UTC+02:00
Powered by phpBB® Forum Software © phpBB Limited
https://www.phpbb.com/