Stereo Tool

I know. I touched over 20,000 lines of code this week so like I said the risk of breaking things is really there. I thought that I had tested everything - but I guess not.

I think I have already fixed the lowpass issue (there was an extra call to it at the end of the processing that didn't seem to do anything, but yesterday evening I saw that it caused part of the changes between 029 and 030).

I think I've fixed the issues now (output is nearly identical to 029 again, the difference is below -90 dB and is most likely caused by rounding differences).

Bojcha just pointed me to a possible audio quality improvement in the clipper that I'll look into soon.

But before I do that I first want things to be ok again.

BETA031:
Fixed the issues in BETA030, I've tested several presets and the output is identical to that of BETA029 (except for some rounding errors, below -90 dB).

Winamp/DSP: http://www.stereotool.com/download/dsp_ ... 22-031.exe
Stand alone: http://www.stereotool.com/download/ster ... 22-031.exe
VST: http://www.stereotool.com/download/vst_ ... 22-031.dll
Command line: http://www.stereotool.com/download/ster ... 22-031.exe


IMPORTANT: LOW LATENCY OUTPUT IN THE STAND ALONE VERSION IS BROKEN AND MIGHT EVEN CAUSE CRASHES. SO MAKE SURE TO TURN IT OFF BEFORE UPGRADING! The good news here is that with the new design it should be pretty simple to get a much better working low latency output which might even have a lower latency than before.

Hans, like the beta30, beta31 standalone version, not working.
No audio comes, by any means and when closed gives always a problem.
The beta29, it works correctly.

_________________
by GAP
"Less is More" (Bob Katz)

Is that with low latency output disabled? I just ran a test here and it seems to work fine.

if I have low latency output disabled, but no audio goes in or out.
I did the same with the beta30.

_________________
by GAP
"Less is More" (Bob Katz)

I had a weird, freaky thing happen with your latest preset that was similar to this. At first there was no audio, then I was getting a burst of garbled noise, then some audio, then some garbled noise, then silence, rinse and repeat... CPU usage was maxed out too. I think it has something to do with preemphasis and the related hole-puncher code.

Nope. It's not the pre-emphasis. It's the quality slider. The setting you have in your preset (approx half quality) eats my CPU. Things were so bad that it took 10 minutes from the time I pressed CTRL-ALT-DEL to bring up Task Manager to the point where I was able to End Task. Raising the quality slider back up to full makes that issue go away.

@Brian: Thanks! I'll try to fix that tonight.


In the mean time, last night I tried to implement the trick that I expected to improve the audio quality, but that failed. After that I ran a test to see what the fix that would double the cpu load would do - and that effect is HUGE. So I guess everyone will need to buy a new pc for the next version (yes, I know that that's unacceptable - i'm now trying to figure out a solution that at least gets closer to that sound without doubling the cpu load.)

There is a small chance that this change helps in unexpected ways and would allow far less high strictness settings in the clipper. But I have not yet tested that. If that's the case the cpu load might not have to double after all...

Are the chances genuine that things could get worse to the level of being perceptible to human ears when more and more things are compounded upon this release? Would it be ok to take beta 31 as a reference for your future work?

Apologize if my questions sound baseless. Given the fact the differences I hear between VST and Winamp DSP plugins are termed as rounding and/or bit-depth differences, I am little shaky to take anything after beta29 in a good faith.

_________________
visit website