getting my head around windows audio drivers.

    Apr 11 2013 | 11:09 pm
    I'm building an app that needs to run on both mac and windows. I have used macs for the past 10 years and windows machines for the past 10 days so my experience is slightly biased! The app I have built is intended for teachers with no technical experience to use, because of this there is a significant demand that everything works straight out of the box, something that has become an issue with windows audio drivers. If you mention the word driver to many of the teachers I'm working with they would run a mile, so I need the app to default to one driver that will work for anyone - I basically have to decide for them! My question then, which driver would be best to choose? there appear to be issues with many of them:
    ad_mme incurs a significant latency problem on all of the machines I have tested my app onad_directsound no latency, works perfectly once an input is selected but outputs a shrill scream that is very high in amplitude if input device is set on none during startup.ad_portaudio Windows Directsound this look promising but, no scream, low latency, would all windows machines have this driver installed? What is the ad_portaudio part and how does this differ from ad_directsound?
    I would value any feedback or input! :)

    • Jun 26 2013 | 10:36 am
      it would be good if somebody could add to this. I am used to working with OSx, so am not entirely sure why there is the plethora of choices with regards Windows drivers. However, i am running a project at the moment on a windows machine, and none seem to be entirely stable. It would be nice to know what people who use Windows as their primary OS think of this issue, and then pass on their advice.
    • Jun 26 2013 | 11:16 am
      isn't there something like ASIO_FOR_ALL on Windows ? i heard it's some kind of standard...