Stereo Tool

Ah... Yeah, you're not understanding me. I have only tested a drastic difference with 2048 samples. At 4096 samples, GUI up vs. down is not as dramatic. Given your processor's extra RAM bandwidth (DDR2 or DDR3 vs. DDR1) and newer microarchitecture (yours is K10, mine is K8), your processor is going to handle running out of cache better than mine.

Example numbers:

4096 latency, minimizing/traying the GUI gives around 8-15% decrease in load. Given that your system has better main memory bandwidth, the 3-4% difference you're seeing sounds about right to me.

As for your preset in the sharing section, the only one I see with you as the author is very old, designed for version 6.00. You need to create a new version and post it, otherwise when I load that older one, it will fill in some default behaviors because the entries are not listed in the old file that you posted (DJ-DOGGY v 2)

Very odd. I don't think Stereo Tool can cause this, it doesn't really look like clipping either. If I have to guess, different places in the buffer contain audio from different moments in time... Maybe too tight ASIO settings?

Looks like Fanboy FUD.
Translation of what you said:


You might have not noticed, given your "thorough reading", but various things that have been implemented used to bog down an i7, so your i5 would've taken a nose dive too. The reason they don't bog you down now is because the routines have been optimized.

We're nowhere near approaching "Development Hell", ala "Duke Nukem Forever". 6.10 was released on Feb 10, 2011. That is approaching 8 months. Hans has been busy with other things (the declipper, which was intended as a separately sold product included in ST without nag if registered), and has gone on a trip or two (or more)... In my opinion, the changes in "6.20" really merit a major revision number, up to 7.

So, if you think that 8 months with a lot of things going on for a single developer working on a project that's seen some dramatic improvements is "too long", then I've seen your type of "software developer" for many years myself. You are the type that over-promises to a manager, who then sets some hideously short timeline, so the product gets rushed to market, half-done and full of bugs and bloat, which then takes months or years to clean up.

One classic example of this in the gaming industry was Star Wars: Knights of The Old Republic II : The Sith Lords. Bioware made a fantastic game for the first one, but they passed it to Obsidian for KoTOR 2. Lucas Arts demanded a launch, so the game went out with large chunks of the storyline dead-ended in the game (the entire HK Factory, most notably), along with a slew of bugs. As such, the game was not as enjoyable as the first, and was downright confusing when you got to Malachor V, as you were missing the Bao-Dur / droid remote and G0T0 / HK droid backstory.

Less fanboi and less rage, mmmkay? The optimization phase does end up helping you, whether you understand it or not.

This was with ASIO off.

Something like this can still happen inside the sound card driver. I've seen something which might be somewhat similar on a Juli@ with too tightly configured latency settings (which apparently ALSO influence non-ASIO I/O).

What happens if you use another program which also sends input to output? For example - say - Winamp + LineIn plugin?

If i use line in plugin it works fine. But when i open stereo tool aside it with all different sound card settings i have same vertical lines in output.

Line in + Winamp out with the same sound cards that you are using in the Stand Alone Stereo Tool version? If so it must be a Stereo Tool problem.....

Yes, but i'm not completely sure why it would happen when i open stereo tool. There i have vac selected for in and outputs, and it only happens when i maximize the stereo tool window and move some screens around. Then i hear it on the winamp output.

Trying the same with breakaway and there it's fine. So i think something must be in stereo tool that creates this.

Ow wait. You hear it on the WINAMP output?! When you move around a stand alone Stereo Tool window? Then it must have something to do with the CPU load or the video card. Hm, that could actually be it - could it be that your video card is sharing some interrupts with the sound card?