Stereo Tool

Could you try what happens if you set the Task Manager priority to Low?

No it's not, but true if i don't touch anything.

beta28 is still on transmitter and work very good. But when i am on remote it starts to click, moving windows around, refreshing desktop, make same clicks.

beta30E - still same clicks/pops, realtime ON.

i checked
taskmgr = low, explorer.exe = low .. same again.

Beta 29 (i believe) with GUI set at IDLE was perfect for me. The GUI still worked and no clicks even while rendering with sony vegas.

For the GPGPU solution I was thinking of using OpenCL which I believe is supported by ATI's HD 4870 card. I'll keep looking into it

_________________
<-- I like this guy!

About OpenGL etc.: Processing will be very difficult to convert. It's probably possible, but remember that I need a 100-times performance boost to do what I described before - anything less than that doesn't work. And still a 100 times performance boost would only work for latency 512. So this is not going to be easy.

I have seen the results of people who have tried to convert complex video processing algorithms to the GPU, who couldn't get much more than a 2-4 times performance boost...

When i set the priority of taskmgr to low and stereotool to high it's much harder to create clicks with resizing the task manager window. Didn't hear any with buffer of 10ms so far. But they are there with buffer of 6 ms. This was tested with granularity of 512.

I've added some timing logging, and though I cannot reproduce the clicks, I do now see the difference in timing. So that should help...

@Hans
Can you set Affinity to two or one core., fill desktop with icons, open any folder full with files and resize it...
just for testing..

Based on logging, during task manager full screen show/hides:
- ASIO thread does get some small hiccups, upto about 8 000 CPU cycles (that's really very little)
- Processing thread gets hiccups of about 3 500 000 cycles. WAAH!

So there's definitely still a big difference between the ASIO thread and my own (highest possible priority) thread w.r.t. priority handling. I think it must then indeed have something to do with the fact that the ASIO thread is created by a driver.

This would mean that I indeed need to do my processing INSIDE the ASIO thread. But that will be a lot of work - and I'll postpone that for the next version (not 6.01).

Great you found something now. What for program do you use to show this?