Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building with support for ASIO #9

mberz opened this issue Mar 3, 2019 · 2 comments

Building with support for ASIO #9

mberz opened this issue Mar 3, 2019 · 2 comments


Copy link

mberz commented Mar 3, 2019

There is currently no support for ASIO (or any other API than WME) on Windows. Would it be possible to add support for building with support for ASIO?
This would require to get the ASIO SDK from Steinberg as a dependency.

The Portaudio documentation gives some information on how to build with MinGW and ASIO support.

Copy link

scopatz commented Mar 4, 2019

So, section 2.3 of their license says:

The Licensee will not sell, license, give-away and/or distribute the Licensed Software
Developer Kit or parts of it for the use as software developer kit in any way, for
example, integrated in any framework application, on any medium, including the
Internet, to any other person, including sub-licensors of the Licensee or companies
where the Licensee has any involvement. This includes re-working any part of the
SDK or ASIO specification, or reverse-engineering any part of the SDK or any products
based upon.

So basically, we are not allowed to redistibute it at all, unfortunately. Given their license, you have a couple of options:

  1. Try to negotiate with them a new license that allows Numfocus to redistribute thier SDK.
  2. Make a recipie that installs activation scripts, that then installs the software on the user's machine when the package in activated. This isn't perfect, but it will work and is what the conda-forge cudatoolkit package does. That option works less well here because the user still needs to have a signed license agreement with Stienberg.

Copy link

bburan commented Dec 9, 2021

It seems that the catch is with including the SDK in the portaudio-feedstock repository, right? What if the build recipe was configured such that it automatically downloads and unpacks the SDK during the build process? The final product (the portaudio binary) would not contain the SDK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

3 participants