Stereo Tool

I have been able to 'kinda' reproduce one issue of these 4, but not the others. There definitely IS a bug here.

1. Every time I hit the 'Restart sound cards' button, the ASIO buffer filling changes. If I change the buffer size (which *should* have the same effect), the correct filling is restored. This is definitely a bug. It seems to be unrelated to whether I use normal output (however, normal output could very well trigger the same effect - it does not here though, but when I enable the normal output, the normal output buffer is not filled as it should. This is also a bug.)
2. Hiccups occur at too small buffer sizes (this makes sense, the program detects an empty output buffer which means a hiccup, and restarts the whole audio layer to synchronize everything again). I have been unable to reproduce the described issue that the hiccups keep occurring if you increase the buffer size again.
3. ASIO card not in use does not play plopping sounds here. It does when I enable it (but that makes sense)
4. Using a Juli@ card on this test system...

Wich microsoft has recently decided to stop developing updates and is announced 'end of life' !!

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

Well lets start fixing the bug you can reproduce, maybe the other bugs dissapear to, you never know!

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

My WindowsXP instalation is EOL for about 6 years ago, since i made my own ISO where i disabled many things. I am still using it everywhere. So nothing to worry about XP (except some new hardware - like haswell)

Crap! I just looked at my pc's screen and I noticed that I have probably tested with version 7.23 instead of 7.41.

Testing again - now with 7.41 - shows:
1. The bug that I saw with the Restart button is no longer present.
2. Long ASIO latency when normal output enabled: Not reproduced here. Latency does not change.
3. Hiccups occur with small Normal buffer size, if I increase it again the hiccups are gone.
4. When hiccups occur and FM output is disabled, I hear no plops.
In other words, everything seems to behave as it should.

Question: Which sound card did you use for Normal Output? Was that also the Marian? If so, could you try another? Here I cannot open normal output on my Juli@ card - it shows an error message.

Normal output was a REALTEK onboard sound device, FM output was Marian.

When both outputs enabeled, FM latency was way to high (no buffer filling visable) when increasing asio buffer size all of a sudden latency went DOWN and green buffer filled...

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

Today i got several crashes in Adobe Audition CC with the 64 bit Version of StereoTool.

Here are 2 Crashes from the Windows Event Log. Its always the same Error Point:

Name der fehlerhaften Anwendung: Adobe Audition CC.exe, Version: 6.0.0.732, Zeitstempel: 0x518ade79
Name des fehlerhaften Moduls: vst_stereo_tool_64.dll, Version: 0.0.0.0, Zeitstempel: 0x530e9808
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000001a45d0
ID des fehlerhaften Prozesses: 0x2f80
Startzeit der fehlerhaften Anwendung: 0x01cf3d531d1f6660
Pfad der fehlerhaften Anwendung: C:\Program Files\Adobe\Adobe Audition CC\Adobe Audition CC.exe
Pfad des fehlerhaften Moduls: C:\Program Files\VstPlugins\vst_stereo_tool_64.dll
Berichtskennung: f13176ed-a954-11e3-826c-240a64dee42f

Name der fehlerhaften Anwendung: Adobe Audition CC.exe, Version: 6.0.0.732, Zeitstempel: 0x518ade79
Name des fehlerhaften Moduls: vst_stereo_tool_64.dll, Version: 0.0.0.0, Zeitstempel: 0x530e9808
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000001a45d0
ID des fehlerhaften Prozesses: 0x2e20
Startzeit der fehlerhaften Anwendung: 0x01cf3d4d99bcb0f9
Pfad der fehlerhaften Anwendung: C:\Program Files\Adobe\Adobe Audition CC\Adobe Audition CC.exe
Pfad des fehlerhaften Moduls: C:\Program Files\VstPlugins\vst_stereo_tool_64.dll
Berichtskennung: 562ba001-a946-11e3-826c-240a64dee42f


Its always the Error Offset 0x00000000001a45d0. This does not happens with older Versions of StereoTool.

@Hans Can you please check your VST Version? What i did was, when i used the VST Plugin in a Multi Track Project and then moved around the timeline. sometimes i move around and played some pieces. then after sometimes i get an appcrash. the whole application crashes.

I managed to reproduce it, however the address that I see is 028A7B65. The cause is too aggressive compiler optimization. I'll try to fix it asap.
Edit: Or not. I was testing it with the 32-bit version but it turns out that I loaded the non-SSE2 version. I did find a bug there which is fixed now. (Not strange that no-one reported it, it was a bug in the composite clipper in the Pentium 3 build ).

I have tested the debug and release 32 bit VST's and they seem to work fine. I'll test the 64 bit versions later (but I need to setup a better test environment for 64 bit first - also to be able to check what happens at the reported error location).


Ok, both addresses that you mentioned are in the compressor. If that is indeed correct, then you shouldn't get crashes if you disable all compressors (SB, MB, SB in AGC).

I have checked both addresses (from this and from your previous post), fortunately both are at a differently optimized version of exactly the same code. But... I haven't been able to find anything suspicious there. I will send you a version with extra logging at the spot of the crash in a PM.

So.... Is the average Joe OK to use this new version, or should we be waiting for these diagnostics to work their way through?