In the presentation you mentioned the fact the complier switch in VS2005 you could convert unsafe method calls to the newer safe ones and you also give an example of using current complier settings and setting the size of dest by calling size of 'dest'.
I have heard a number of views about the "_s" extentions to the API (not ANSI C+++ complaint etc) and the complaints about the warnings the complier gives you about depricated CRT API calls (the method calls are not depriated accrdnig to the standards). So
why could you have not under the covers converted the users code to the newer methods without a complier switch or converted the complier to check method calls to check the size of the destination buffer being used and then provide a user high level warning?
Can we get more information on creating and adding system effects to the Audio streams.
If you're an IHV, sure. Contact your Microsoft TAM. .
But surely you don't need to be a hardware vendor to write stream effects within the Audio engine ( the vertical boxes on top of the audio engine.), or have I missed the point that this is contained on hardware. During ther video it was disscussed that the
streams can have effects added to them at this point in the audio process, or did it mean in a derived class of IRenderClient