i just want to post a short explanation for people that are following the 2015 updates, here, and might be confused about what i mean when i'm talking about a streaming proxy service.

you might think i'm talking about streaming over the internet, and not understansd why that's important in trying to fix the mixer. in fact, the terminology is shared - streaming over the internet is largely the same thing as streaming over your operating system. it's more a question of who the clients are.

without getting into an undergraduate lecture on operating systems (and i'll remind you that i've completed 19.5 credits of a computer science degree at a high gpa), i'll just point out that your operating system streams almost everything, from a conceptual perspective. streaming, itself, refers to a transfer of data. all it means is that it is a continuous flow. so, your operating system will accept data from your sound card - or your video card - as a stream of data, just like your network card will accept data from your router in a stream. as you can set up network proxies, you can also set up local proxies, and the entire audio architecture of your computer almost certainly depends on this. it's the same basic thing over all over the major operating systems, but ksproxy.dll is a windows library that is very specifically audio-oriented.

so, i'm not talking about network streaming, i'm talking about how windows communicates with my sound hardware. but, if you can abstract it well enough, it's kind of the same idea as network streaming, just very, very local.

a hostile agent could absolutely take control of that audio stream and redirect it elsewhere. and, for a time, i felt that this was what was happening.

in the end, i decided that the actual problem had to do with a fluctuating magnetic field in the room and i had no option but to try to work around it rather than actually resolve it.

i'm not sure if most people would have even noticed it.