Quote:
@ClaveFremen: You're reporting completely distorted sound at latency 2048 in version 7.70. Version 7.70 has been available for months and you're the first to report this, so whatever you're seeing doesn't seem to happen to a lot of people. You are also saying that the problem disappears if you increase the buffer size in Foobar, which would seem to indicate that it's a buffering problem - but if the right channel is completely distorted it doesn't seem to match that (depending on what you mean by distorted - is it too loud, or a complete mess of different chunks of audio, or noise, or something else?). Can you try if that also disappears if you increase the buffer size? If not, can you make a recording of the distortion?
I suppose not much people using ST optimize Foobar settings or maybe doesn't notice them, I didn't too until I've started using headphones, with them they're much more noticeable.
Keeping ST GUI open or not makes no difference for both clicks/drops or the distortion at 2048 samples.
The distortion is also present at 120ms (or higher) buffer, I'll try to record it and post it.
Quote:
All of you: Are you both using Foobar with a VST wrapper? @ClaveFremen, Chibisteven only sees a problem with 192 kHz sample rate, what sample rate are you using?
Yes, I'm using a VST wrapper.
I'm not resampling, the tracks I'm using are plain 44100Hz ones.
Quote:
I've just installed Foobar + VST Adapter, and running the latest ST shows no problems, except indeed when I set the latency to 50 ms. Then anything I do on the system causes brief drops.
I confirm the problem is present only at 50ms buffer size (even doing nothing else on the PC), but version 7.60 works perfectly with that buffer size.
Quote:
Just to check: If you are talking about CPU load, are you checking the meter inside Stereo Tool or another tool? Only the value inside ST is useful to determine if there's a problem. It's under Configuration -> CPU & Latency.
CPU is under 30% while clicking.
image share
When 2048 samples are selected the CPU seen by ST goes to 100% (it's the dark red area, right?) but Task Manager reports under 30% CPU utilization.
url immagine
Quote:
Edit: I see that Foobar crashes when I open and close the VST GUI and then close Foobar. It appears to be an internal Foobar error though - it's definitely not something that's coming out of Stereo Tool... (It complains that some object already exists, a bug coming from ST would look very different, and when it happens ST has already been unloaded). Despite that, can you try if you also hear clicks if you never open the GUI?
The wrapper it's a bit buggy, sometimes it crash.
Opening the gui makes no clicks, sometimes when you close it.