Stereo Tool

Hans

I instal the standalone version, and windows give me an error message

Gebeurtenisnaam van probleem: APPCRASH
Naam van de toepassing: StereoTool.exe
Versie van toepassing: 0.0.0.0
Tijdstempel van toepassing: 510e8d61
Naam van foutmodule: StereoTool.exe
Versie van foutmodule: 0.0.0.0
Tijdstempel van foutmodule: 510e8d61
Uitzonderingscode: c0000005
Uitzonderingsmarge: 00051425
Versie van besturingssysteem: 6.2.9200.2.0.0.256.48
Landinstelling-id: 1043
Aanvullende informatie 1: 5861
Aanvullende informatie 2: 5861822e1919d7c014bbb064c64908b2
Aanvullende informatie 3: f3d5
Aanvullende informatie 4: f3d5be0cad2787556264647dc02181c3

_________________
Garbage in is Garbage out !

Using VST 026 in Virtual DJ does crash Virtual DJ.

Same here, seems there is a wrong in 026

Standalone version chrashes

_________________
----------------------------------------------------------------------------
AIRCHAIN-GURU professional independant airchain consultancy.
Orban/Omnia/Vorsis/DSPX/Aphex/Inovonics
----------------------------------------------------------------------------

26 - DSP version has continuous clicking sound when highs gap protection is enabled. Either always or pre-emphasised, it doesn't matter.

Otherwise, comparing the behavior without gap protection or pre-emphasis between 25 and 26, 26 does indeed use less CPU, but only when the level coming into the clipper is lower (soft passages). Track I tested with was "Time" - Pink Floyd. During the intro, load is in the 50s vs. 60s for beta025. Clocks chiming...goes up to 60s, then drops back to 50s until the singing starts, at which time it goes back up to the 60s.

VST version works fine for so long Highs Protection is kept disabled. If enabled, it makes the host application to crash.

Other than that, Output Amplification and Input Amplification parameters seem to have been supplanted by Output Level and SingleBand Drive, yet the former parameters still show up in sts file when saved.

_________________
visit website

Ok, confirmed. Crashes seem to be related to certain settings (I tested several before uploading these versions and they all worked).

Did I miss the explanation of why the AGC Target Output level value is significantly higher than previously?

Beta025 introduced this change, and it is still present in 026.

Previously, my AGC Target Output was -7.00. Starting with 025, it is now -4.85 Not sure if this is just a cosmetic change.

I observed (and reported) the inaccuracy for both VST and DSP versions in beta25. It's been taken care of in beta26 at least for VST.

_________________
visit website

BETA027:
First, some explanation.

While looking at some hotspots with VTune, I observed that the code that the compiler generated was in many cases sub-optimal. So I've been Googling and trying things until I managed to get the compiler to produce more optimized (and in some cases, but not all, also smaller) code.

The problem with this is that I have to 'make promises(*)' to the compiler so it can optimize more aggressively. If I don't keep my promise, the behavior is 'undefined' - in most cases it will lead to crashes or stuttering sounds.

I have now tested this version with all the built-in web and FM presets, didn't find any issues.

(*) Example: I'm only going to use values that are a multiple of 4.

Stand alone: http://www.stereotool.com/download/ster ... 04-027.exe
Winamp DSP: http://www.stereotool.com/download/dsp_ ... 04-027.exe
VST: http://www.stereotool.com/download/vst_ ... 04-027.dll


Oddly, for some reason I'm not seeing an improvement in the clipper anymore - before it was almost 10% faster. Still checking...


EDIT: STILL CRASHES IF QUALITY < 100%. AND APPARENTLY IN SOME OTHER CASE AS WELL.

I can confirm that. My music that is @ 192KHz, 32 bits crashes 027 program instantly, however an MP3 @ 44.1KHz, 16 bits will play just fine.