Rename ASIOBridge to FlexASIO.

This is because the ASIOBridge name actually happens to be already used
by a software that does the exact same thing, but in reverse:

  http://vb-audio.pagesperso-orange.fr/Cable/

Changed the name to clear up any potential confusion going forward.

ASIOBridge.sln → FlexASIO.sln

@@ -1,7 +1,7 @@
 
 Microsoft Visual Studio Solution File, Format Version 11.00
 # Visual Studio 2010
-Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "ASIOBridge", "ASIOBridge.vcxproj", "{EFC61192-2DB9-46B1-BF85-98FC6EF1E6D1}"
+Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "FlexASIO", "FlexASIO.vcxproj", "{EFC61192-2DB9-46B1-BF85-98FC6EF1E6D1}"
 EndProject
 Global
 	GlobalSection(SolutionConfigurationPlatforms) = preSolution

ASIOBridge.vcxproj → FlexASIO.vcxproj

@@ -12,7 +12,7 @@
   </ItemGroup>
   <PropertyGroup Label="Globals">
     <ProjectGuid>{EFC61192-2DB9-46B1-BF85-98FC6EF1E6D1}</ProjectGuid>
-    <RootNamespace>ASIOBridge</RootNamespace>
+    <RootNamespace>FlexASIO</RootNamespace>
   </PropertyGroup>
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
   <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration">
@@ -83,23 +83,23 @@
     </ResourceCompile>
   </ItemDefinitionGroup>
   <ItemGroup>
-    <ClCompile Include="asiobridge.cpp" />
+    <ClCompile Include="flexasio.cpp" />
     <ClCompile Include="comdll.cpp" />
   </ItemGroup>
   <ItemGroup>
     <None Include="dll.def" />
-    <None Include="asiobridge.rgs" />
+    <None Include="flexasio.rgs" />
   </ItemGroup>
   <ItemGroup>
-    <ResourceCompile Include="asiobridge.rc" />
+    <ResourceCompile Include="flexasio.rc" />
   </ItemGroup>
   <ItemGroup>
-    <ClInclude Include="asiobridge.h" />
-    <ClInclude Include="asiobridge.rc.h" />
+    <ClInclude Include="flexasio.h" />
+    <ClInclude Include="flexasio.rc.h" />
     <ClInclude Include="util.h" />
   </ItemGroup>
   <ItemGroup>
-    <Midl Include="asiobridge.idl" />
+    <Midl Include="flexasio.idl" />
   </ItemGroup>
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
   <ImportGroup Label="ExtensionTargets">

README.md

@@ -1,13 +1,13 @@
-# ASIOBridge README
+# FlexASIO README
 Author: Etienne Dechamps <etienne@edechamps.fr>
-Website: https://github.com/dechamps/ASIOBridge
+Website: https://github.com/dechamps/FlexASIO
 License: General Public License, version 3
 
 ## DESCRIPTION
 
 Background: http://en.wikipedia.org/wiki/Audio_Stream_Input/Output
 
-ASIOBridge is an universal ASIO driver, meaning that it is not tied to
+FlexASIO is an universal ASIO driver, meaning that it is not tied to
 specific audio hardware. Other examples of universal ASIO drivers
 include ASIO4ALL, ASIO2KS, ASIO2WASAPI. Universal ASIO drivers use
 hardware-agnostic audio interfaces provided by the operating system to
@@ -17,14 +17,14 @@ ASIO drivers.
 
 While ASIO4ALL and ASIO2KS use a low-level Windows audio API known as
 "WDM-KS" (also called "DirectKS", "Kernel Streaming") to operate, and
-ASIO2WASAPI uses WASAPI (in exclusive mode), ASIOBridge uses an
+ASIO2WASAPI uses WASAPI (in exclusive mode), FlexASIO uses an
 intermediate library called PortAudio that itself supports a large
 number of operating system sound APIs, including MME, DirectSound,
 WDM-KS, as well as the modern WASAPI interface that was released with
 Windows Vista (ironically, PortAudio can use ASIO as well, nicely
-closing the circle). Thus ASIOBridge can be used to interface with any
+closing the circle). Thus FlexASIO can be used to interface with any
 sound API available with your system. At least that's the theory; in
-practice this is a very early version of ASIOBridge that doesn't have a
+practice this is a very early version of FlexASIO that doesn't have a
 configuration interface yet, so it will simply default to using WASAPI
 (in shared mode, *not* in exclusive mode) on most systems.
 
@@ -36,55 +36,55 @@ any other application, which makes it an interesting alternative to
 ASIO4ALL/ASIO2KS/ASIO2WASAPI, as these drivers always open devices in
 exclusive mode without giving you a choice.
 
-One interesting use case of ASIOBridge is that it allows the use of
+One interesting use case of FlexASIO is that it allows the use of
 RoomEQWizard while being able to choose the output channel on a 5.1/7.1
 system but *without* bypassing the Windows audio processing pipeline,
 which can be extremely useful in some scenarios. That's what I'm using
 it for.
 
-ASIOBridge should be able to run on any version of Microsoft Windows,
+FlexASIO should be able to run on any version of Microsoft Windows,
 even very old ones, at least in theory.
 
 ## HOW TO USE
 
-Just install it and ASIOBridge should magically appear in the ASIO
+Just install it and FlexASIO should magically appear in the ASIO
 driver list in any ASIO-enabled application. There is no configuration
 interface (see "caveats" below).
 
-To uninstall ASIOBridge, just use the Windows "add/remove programs"
+To uninstall FlexASIO, just use the Windows "add/remove programs"
 control panel.
 
 If you don't want to use the installer, you can install it manually by
 simply registering the DLL:
 
-    regsvr32 ASIOBridge.dll
+    regsvr32 FlexASIO.dll
 
 Use the `/u` switch to unregister.
 
 ## LIMITATIONS AND CAVEATS
 
 This is an early release, so there are lots of them.
 
-This a very early version of ASIOBridge developed over a single
+This a very early version of FlexASIO developed over a single
 week-end. It has not been tested in any extensive way, and is certainly
 not free from bugs and crashes.
 
-ASIOBridge doesn't yet comes with a configuration interface ("control
+FlexASIO doesn't yet comes with a configuration interface ("control
 panel" in ASIO terminology). The main reason is because programming GUIs
 takes a lot of time that I don't have (especially since I have zero 
 experience in GUI programming). This means that you are forced to use
-ASIOBridge defaults when it comes to system API and options, device
+FlexASIO defaults when it comes to system API and options, device
 selection, and buffer size. These defaults are as follows:
  - System API is forced to WASAPI, or if it's not available (pre-Vista
    OS), DirectSound. Note that WASAPI is used in *shared* mode, not in
    exclusive mode, so it behaves much like a typical Windows
    application.
- - ASIOBridge selects the default audio devices as configured in the
+ - FlexASIO selects the default audio devices as configured in the
    Windows audio control panel.
  - Preferred buffer size is hardcoded to 1024 samples (21.3 ms at
    48000Hz). This is purely arbitrary.
 Note that it is possible (and relatively easy) to change these settings
-by manually editing the source code and recompiling ASIOBridge. Not
+by manually editing the source code and recompiling FlexASIO. Not
 ideal, I know. Patches welcome.
 
 If you are using different hardware devices for input and output, each
@@ -99,36 +99,36 @@ WASAPI (at least on my test system) seems to require that the sample
 rate used by the application matches the sample rate configured for the
 device (which is configurable in the Windows audio control panel).
 Corollary: if you use ASIO in both directions, your input device's
-sample rate need to match the output device's, else ASIOBridge will not
+sample rate need to match the output device's, else FlexASIO will not
 return any usable sample rates. In some ways this could be considered a
 feature since it guarantees that no unwanted sample rate conversions
 will take place.
 
-ASIOBridge has not been designed with latency in mind. That being said,
+FlexASIO has not been designed with latency in mind. That being said,
 the current version should not add any latency on top of PortAudio
 itself. The thing is, due to the way ASIO works (static buffer sizes),
 PortAudio sometimes has no choice but to add additional buffering (which
-adds latency) in order to meet the requirements of both ASIOBridge and
+adds latency) in order to meet the requirements of both FlexASIO and
 the system API it's using.
 
-If you are not using WASAPI, ASIOBridge will be unable to display the
+If you are not using WASAPI, FlexASIO will be unable to display the
 channel names (i.e. "Surround Left", etc.) in the channel list. That's
 a limitation of PortAudio.
 
-ASIOBridge is Windows-only for now. That could change in the future, as
+FlexASIO is Windows-only for now. That could change in the future, as
 PortAudio itself is cross-platform.
 
-ASIOBridge is 32-bit only for now. Porting it to 64-bit is
+FlexASIO is 32-bit only for now. Porting it to 64-bit is
 straightforward, I just haven't gotten around to doing it yet.
 
 ## REPORTING ISSUES
 
 Just use the GitHub issue tracker:
-https://github.com/dechamps/ASIOBridge/issues
+https://github.com/dechamps/FlexASIO/issues
 
 ## DEVELOPER INFORMATION
 
-ASIOBridge currently uses the Microsoft Visual C++ 2010 toolchain,
+FlexASIO currently uses the Microsoft Visual C++ 2010 toolchain,
 though it should work just fine with any later version. You will need
 the following dependencies:
  - ASIO SDK (include only):

dll.def

@@ -1,4 +1,4 @@
-; Module-definition file for the ASIOBridge DLL
+; Module-definition file for the FlexASIO DLL
 ; Our DLL is just a COM class factory, so we only need to export the functions required by COM.
 ; We can't use declspec(dllexport) for those because the naming convention doesn't match (leading "@")