Just downloaded b1460, now I get an Initialization error.
5/31/2012 8:19:22 AM Error Error initializing ASIO device 0: Integer overflow
Never seen before, nothing changed other than new build installed. 
As I use WASAPI, everything seems to play fine.
Which build did you use before?
Well, using the power of Previous Versions in Win 7, all previous builds that I have available going back two months exhibit the issue, so that points to something else. Wonder if a Windows Update has done something to ASIO. (or some DLL is loaded still).
Previous build I used last week was b1457 and all was well!
Humm… Let me poke around some more.
OK, further prodding, it doesn’t like my BlackMagic Intensity Pro card (Broadcast Video/Audio) in Asio, that was my device 0. So, as I don’t need that on mAirlist, I’ve disabled the card in mAirList config. I’m guessing that an upgrade to the drivers must have changed something. Call off the hounds… 8)
“Integer overflow” rather sounds like an error inside mAirList. Perhaps an invalid buffer size or so? Don’t know.
I doubt many users will have a broadcast video card in their PC 
Found out what happened, my box is dual boot (W7 & Linux) and I went to Linux yesterday which forced a firmware upgrade on the card! Sigh!
actually, I’m very impressed that you had allowed users to disable cards in the config. That makes mAirList very powerful and configurable. Just need to try and spread the word in the US now.
The ability to disable sound cards is the killer feature everybody in the US has been looking for in an automation system? 
No, seriously - mAirList shortly initializes every soundcard during initialization to determin parameters like the number of available channels/speakers etc. This is an issue with some ASIO cards that do not like to be initialized when already in use in DirectSound mode, possibly by another application. Leftover drivers from removed sound cards are another issue.
Most of the time in these situations, you don’t want to use ASIO anyway, so the warning message is just annoying. This is why the “disable” checkbox as wadded.