Stereo Tool

Ok, great Does it also have any effect if you change settings, and are they kept when you restart Stereo Tool? Because I don't know if I should be saving the settings or the ASIO driver does (as I think you said).

All is good!
When i configure asio for soundcard, it ask me to restart aplication.... restart .. ASIO settings remembered.
I just found that my MAYA44usb have 48, 128, 256, 512 samples.. 64 is missing
But anyway it is working at 48kHz at 48 samples, at buffer size is 1.7ms (512)
I'll check again all with Juli@ tomorrow. Maya44usb is only up to 48kHz.

edit:
(512) With Loudness OFF and Final Limiter ON i can set buffer size to 1.0ms

oh a "asio config" button !

it's working too on my soundcard

I'm testing now, i'm feeding very soft music through stereo tool and listening to the radio with sound cranked up high. I have to set the buffer higher and higher because i still here a click after some time. I'm now at 5,5 ms @ granularity of 256. When i find the max, i will test the previous version again.

edit now @ 7.6 ms and i have to set it probably even higher.
It takes quite a long time before the click appears.

I'm now going to test the previous version. It's higher then previously measuring without music.
edit now @ 5,7 ms for version 25 will update when it gets higher.

The strange thing is sometimes the green balk is almost filled till the end but when i set the buffer size higher the balk is flickering more.

Both versions tested at realtime priority, CPU load is around 35 till 40%.
DPC latency Absolute Maximum is 59 us, most of the time around 8 till 15 us.
Tested with http://www.thesycon.de/deu/latency_check.shtml

eldoradofm: I have to guess what's going on here... Since you get occasional clicks, it's not that your CPU cannot handle it, but apparently sometimes something else gets more priority than the processing.

Since Bojcha gets much lower values it's probably something on your system.

1. Windows doesn't really support real-time processing of any kind - 'real-time' priority doesn't really mean anything. Lots of things are running on the background, which can interfere.

Could you try this?
- Close all programs that you don't need
- Make sure nothing is running on the background (virus scanners are particularly bad)
- I don't think that this will help, but: Set the Screen update speed to 0.

This probably won't help, and then we it gets nasty:
- Turn off any Windows service that is not absolutely necessary. Especially 'ARP' requests are bad.


Questions:
- Do you have a multicore system? If so, what's the CPU load on the core that has the biggest load?
- What happens if you reduce the 'Quality' slider or turn some filters off? Or if you select Bypass? --> If this helps, I might have an idea.

I'll do some more testing. This is my CPU load with version 25, version 26 is about the same i'm using E6500 dual core CPU.

edit: I'll do some testing with 40 Hz tone like bojcha did.

eldoradofm: I got some advice from someone that might help. I'll build another version tonight where the maximum 'schedule out' time for the processing thread is reduced from 16 ms (the default setting in Windows) to 1 ms. That MIGHT help a lot.

I'll also try to spread the processing better over the 2 cores (with the changes in BETA26 I think that's now possible without risking a latency increment, which would be there in earlier versions).

Testing now with bypass all selected. I can set buffer to 1.4 ms no clicks so far.

edit: I'm using on board graphics. When i select Windows Task Manager and move it over the Stereotool screen, CPU load goes from 2% to about 57% and i see flickering effect in the stereotool window. I've tried the same with ba and there's no flickering and no increasing of CPU load.

Set buffer to 1.5 ms now, there was a click in 1.4ms setting.

Tested some different granularity settings. With 48, 64 and 128 samples i here clicks even with buffer of 5000ms. I'm now testing at 512 sample it's about the same as with 256. I'll wait for the new version and then do some more testing.

@ Eldorado
192kHz test with 256samples and/or more, 48kHz with 64 and/or more.

I am geting now same minimum buffer size.
192kHz/256samples - 2.7ms (was 2.8) FM Out
48kHz/64samples - 2,7ms (was 4.0ms) Normal out

I have clicks too when i move mouse, or whole window, even when one old hdd in case is working. But when all is minimizes and i kill all unnecessary processes, all is good.

Hmmm.. that not happens with BA Asio.

Is there a difference between "Audio Realtime priority" and "Realtime priority" >

All tests at 192 KHz using FM transmitter output. I'm now testing with BA Asio. Till now all ok @ 256 samples, no clicks there and not minimized.