Stereo Tool

The cost of 4.22 is around 1000 Units, the cost of 5.00 BETA is around 1200 units (compared with presets).

Great job, I'm gonna test it out, having a party, so stereo tool will blast my visitor's ears away tonight

Ok, that's odd - if 4.22 is 1000, 5.00 BETA should be around 500. How do you measure it? And on what hardware (AMD?) - And using which preset(s)?

Don't blast their ears away! You'll ruin my potential customer base

StereoTool Standalone
add, installation makes shortcut to desktop?

Very impressive work hvz! I like your new toy a lot. The reduced processing prower demand was one of my wishes and it's here!
Don't you think about making a foobar plugin version? I've used the Winamp DSP bridge with foobar for your plugin this far, but with this new version when i play lossless audio there's an annoying stutter and animation also lags in Stereo Tool's window. I guess foobar doesn't provide enough audio data to your plugin or so.

About the stutter: Can you try what happens when you select a lower latency setting (I know that doesn't seem to make sense, but I think I might have done something wrong in the multicore support; using a lower latency setting disables using multiple cores). And can you check the CPU load? (Because eurodancetest just reported an increased CPU load instead of a reduced CPU load as I expected).

About foobar: No plans yet... (And no time, which is the reason why I have no plans for it yet)

Darkbyte, I just realized something: In the old version (4.22), the processing was done more spread in time. In this new version, when a block of data has arrived, ALL the processing is done at once, every 93 ms at 44.1 kHz/4096 samples latency.

So indeed, if the buffer size is very small you might get very fast stuttering even if the CPU load did not go up (but please check that first - I know that the CPU load must be a lot lower on Intel CPU's, but I'm less certain about AMD's).


Edit: Oww... I think I didn't read things correctly.

Please try the following:
- Go to the "Configure audio and display" (or something like that) window
- There, DISABLE the removal of the remaining end of tracks. This MIGHT help to get rid of the stuttering, IF it's caused by this gap removal. (Probably not though)
- And you can configure the visualization delay to match the buffer size of your player (by default that's 2 seconds)


This won't help if the CPU load is too high. So please still check that.

Dunno how you do it, but this release is far beyond what I expected! I usually try out all the beta versions, but I waited until this was released before changing from 4.22. I run just a simple shoutcast stream with a 64KB AAC+ and 128 AAC+ on a P4 3Ghz HT CPU. With 4.22 with everything going my CPU would run between 50-62% set on MED quality. With this release i'm down to 28-38% load on the highest quality settings! The sound quality changes are huge! When I listen to my streams on head phones they are so much clearer in the highs then ever before. The bass seams to more fluid and you can tell the highs don't get reduced due to high bass nearly as much as 4.22.

Question: Just the animation. The input levels turn red once in a while. This is new to me since I'm coming from 4.22. I've tried to search to find a description for it, but couldn't. What is this telling me? The track input contains clipping? Just curious. Thanks again for this awesome tool!

-n4-

Hi Nuke,

Turning input/output meter in red mean clip. I know this is little confusing because there is question. "How this song can be clipped when it's at 0dB?" Simple, if you play it in winamp and song is compressed in mp3 with 0dB peek level, after you play there is overshots in decoding/encoding process.
So, actually what is needed is just set player's Gain (preamp) to at least -1dB (or lower).