another strange thing that is maybe
related to this bug (<- i think so because i can remember that i´ve
had this some hours before the directsoundrerror message) :
you all know that sometimes the Asio/directsound out/in components save their status when the OSM gets created.
means, if for example aliasant saves a osm , uploads it and i download and open it, i see what aliasant is using, or at least how many output / inputs his soundcard has (until you enable/disable the component, then it show your outs/ins).
a few hours before the DS error i´ve opened a OSM from the forum that had a asioout component in it. strange here was that when i enabled the it, it has not refreshed to my soundcard setting (4 out´s) but the driver was activated with the status from the author(2 outs) and worked. this happend to me only one time, as said a few hours before the ds error.