ASIO support in Audacity 2.4.2

[micsthepick]

@doubleO7 no worries, I’m thinking that a couple of projects later in the dependency chain were left intentionally broken in the windows build, as two were failing when I built it too

[Apesbrain]

Maybe someone can tell me how exactly I can insert this patch into the source code.

sure, use this tool: https://git-scm.com/docs/git-apply
it comes with git, so assuming that you managed to clone audacity/wxwidgets with the correct 3.1.3-audacity-fixes branch, then all you need to do is open a terminal in the audacity repo and run

Code: Select all

git apply asio.patch

sent from my phone

Not sure what I was doing wrong earlier, but with this instruction I got ASIO to build on 2.4.2. Thanks.

[jademan]

OK, I (finally!) got Audacity 2.4.2 with ASIO to compile on Windows 10.

I would like to share with you my steps, so that you may/might be able to duplicate them. My thanks to steve, Apesbrain and micsthepick whose posts gave me the solution I only had to duplicate and document; and to Steve A Lee for the 2.4.1 version of this cmd file.

1) I have previously download Visual Studio Community Edition 2017. See https://visualstudio.microsoft.com/vs/older-downloads/
2) I have previously downloaded and intstalled git; if you haven't done this do this now. See https://git-scm.com/download/win
3) Download and install win32 installer for cmake-3.19.1 from https://cmake.org/download/
4) Download current python 3.9 from https://www.python.org/downloads/windows/
5) Create c:\proj242 directory
6) Download latest ASIO SDK from https://www.steinberg.net/en/company/developers.html
then unzip the ASIO SDK folder and move the folder to c:\proj242.
7) Rename this folder to "ASIOSDK"
8) copy the following code build-audacity.txt to c:\proj242\build-audacity.cmd [Note .cmd extension!]
This will download the source code for audacity widgets, audacity 2.4.2, then compile, cmake, and build everything.

build-audacity.txt

rename to build-audacity.cmd

(2.68 KiB) Downloaded 46 times

9) copy the next segment of code and save it to c:\proj242\asio2.patch

asio2.patch

this is the updated asio patch file

(2.4 KiB) Downloaded 48 times

10) There should be two files and one folder in c:\proj242:
build-audacity.cmd
asio2.patch
ASIOSDK
11) Press Windows-R and type "cmd"
12) type "cd c:\proj242", then type "build-audacity"
13) The compiled progam will be built to C:\proj242\audacity\win\bin\Release\Audacity.exe

[roadsterUK]

OK, I (finally!) got Audacity 2.4.2 with ASIO to compile on Windows 10.

I would like to share with you my steps, so that you may/might be able to duplicate them. My thanks to steve, Apesbrain and micsthepick whose posts gave me the solution I only had to duplicate and document; and to Steve A Lee for the 2.4.1 version of this cmd file.

Thank you for putting in this effort and documenting it so thoroughly. To me the fact that you have needed to do this illustrates where the entire process has gone wrong so I'll be sticking with 2.4.1 and falling back on Studio One as my recording software if necessary.

[steve]

To me the fact that you have needed to do this illustrates where the entire process has gone wrong

I'm not sure what that means, but the reason why this is necessary is because:
Building with ASIO support requires using the ASIO SDK source code, but the ASIO SDK license prohibits distribution of the source code. Audacity's open source license requires that the full source code is freely available, so it is impossible to distribute an ASIO version of Audacity without violating one or other license.

[micsthepick]

I'm not sure what that means, but the reason why this is necessary is because:
Building with ASIO support requires using the ASIO SDK source code, but the ASIO SDK license prohibits distribution of the source code.

would it be possible to have an automated build (such as GH actions) with no artifacts that verifies that the ASIO build succeeds?

[stevelee]

> would it be possible to have an automated build (such as GH actions) with no artifacts that verifies that the ASIO build succeeds?
Top

That's a very good suggestion plus a runtime smoke test too. It's a real shame to break existing functionality on a release, especially a patch release.

However most cloud-located CI/CD systems like GitHub actions are Linux based
I can only think of [Azure DevOps](https://azure.microsoft.com/en-gb/services/devops/) offering Windows VM/Containers. I've used it when it was relatively new ) and it was impress if aimed at large corps. II believe now integrates with GitHub. There's a free tier and perhaps OSS pricing. I could explore it's used if there is sufficient interest.

Anyway you're welcome to use [my script](https://gist.github.com/SteveALee/da24c ... dd98eb5d0b) if it helps. It's MIT licensed and could easily be adapted to build using any specified release.

[steve]

would it be possible to have an automated build (such as GH actions) with no artifacts that verifies that the ASIO build succeeds?

As far as I'm aware, the ASIO SDK cannot be included in the source code (that would probably constitute "distribution" and so violate Steinberg's license), so it would need to be downloaded from Steinberg at build time. I don't know if Steinberg allow downloading to bypass their license acceptance page, or any form of automated downloading of their SDK. Even if they do allow that now, they have every right to block such downloads at any time without notice.

Anyway you're welcome to use [my script]

The current /win/build.txt seems to say that MSVC is only used for building WxWidgets. On Linux, WxWidgets may be built with cmake. Can WxWidgets be built with cmake on Windows? If so, it may be possible to make it easier to use the script by removing the requirement for "Visual Studio Community 2017". Perhaps worth looking at?