Skip to content

Instantly share code, notes, and snippets.

@SteveALee
Last active December 6, 2023 09:31
  • Star 21 You must be signed in to star a gist
  • Fork 2 You must be signed in to fork a gist
Star You must be signed in to star a gist
Embed
What would you like to do?
Build audacity with ASIO support on Windows

Build your own Audacity for Windows with ASIO driver support

!!NB!! This builds Audacity 3.3.3 by default. If you want 3.4.2 then use "build-audacity.cmd -v3.4.2" Other versions are unlikely to build due to project changes.

ko-fi

Due to licensing restrictions the Audacity team cannot provide a prebuilt version with Windows ASIO driver support. But with this guide and script you can easily build your own Audacity with ASIO support.

Drivers are the glue between an audio program like Audacity and external hardware like a mixer or sound interface. The drivers usually used on Windows have limitations which can be overcome if you use ASIO drivers for your hardware. Specifically, low latency (delay) and multi channel support are available with ASIO drivers.

The Audacity program is the "go to" solution for many audio recording and editing tasks. However, unlike many more advanced DAWs, it doesn't support Windows ASIO drivers "out of the box". Fortunately, Audiacity's standard MME support is fine for most uses. That said, common reasons for needing ASIO include using digital audio or music equipment that only comes with ASIO drivers, such as Behringer mixers (which actually suggest using the less efficient ASIO4ALL ASIO to WDM bridging driver). Another common reason is to take advantage of the low latency or multiple channels supported by ASIO. Note that Audacity really is not a good multichannel solution, so if that is required a DAW might be a better bet.

While it is possible to build your own Audacity with ASIO support by following the instructions this usually requires considerable technical skills.

But have no fear, the instructions and script provided here make it easy to build your own version of Audacity with ASIO support. You just need a suitable Windows PC. The script installs all required tools and builds a 64 bit release version of Audacity with ASIO for you using the official build instructions.

NB. If you do use this to build Audacity with ASIO support you must not redistribute it due to the ASIO SDK licensing terms - see below.

Here's a brief blog post explaining why I needed ASIO and it includes a screen shot. But note, since writing that, I discovered my McMillen K-Mix digital interface mixer facilities alow routing of inputs 3 & 4 to the main outputs on 1 and 2 so can use the default MME Audacity build after all. For playback from PC, I found the HiFi Driver and ASIO Bridge from VB Audio lets me re-route PC audio out to channels 3 & 4 on the K-Mix, Leaving Channels 1 & 2 free for instruments and Mics.

Licensing

The reason for Audacity's lack of ASIO support is licensing, not technical. Steinberg do not alow the ASIO SDK to be redistributed (as required by open source projects). In addition, Audacity is GPL licensed and so is incompatible with the ASIO SDK licence redistribution rules.

Detailed instructions

The script installs a set of development tools that are known to build Audacity. Due to the complex nature of such tools, any other versions of them on your PC may not work correctly. Thus this scipt should be run on a clean PC without any developer tools. No support can be offered otherwise.

If you would rather not install these tools (Git for Windows, Visual Studio, CMake, Python and Conan), or you already have versions of them or even if you are having build problems, you can install a virtualisation program and a matching Developer Virtual Machine from Microsoft. This will provide an isolated environment to build in, but will be slower. In most cases VirtualBox will be a good choice (import the Microsoft supplied .ova appliance file). The Visual Studio pre installed in the VM must be uninstalled first to avoid problems. Windows also includes an isolated Sandbox VM environment that is known to work as well. In both cases you can copy the built files to where they will be run from by sharing a folder with the VM.

This video by @Renamesk walks you through the process, but the tool installation method has changed.

  • Ensure you have a PC (or VM) with Windows 10 or 11 installed.
  • Make a new folder C:\projects.
  • Click on the 'raw' button at the top of the script (below) in this Gist.
  • Use the browser Save As feature to save the script as \projects\build-audacity.cmd (be careful there's no ".txt" added at the end).
  • open a new Windows cmd terminal (Windows + R keys and then type cmd)
  • Type cd \projects and enter key.
  • Install required tools and build by typing build-audacity.cmd and enter (use -v3.4.2 if requred).
    • Follow the prompts, pressing a key to start each tool's installer (when previous has finished).
    • NB for Visual Studio, make sure you check the "desktop development with C++" workload
    • If you have a non English Windows or Visual Studio then you must also install the English language packs.
  • Come back later - it will take at least 10 minutes.
  • Audactiy will be launched to test it was built correctly.
    • See the program location printed out at the end of the build so you can run it again.
    • Optionally copy the specified folder to where you want to run Audacity from, optionally renaming it.

If you have any ASIO drivers installed for active connected hardware you should find ASIO is now available in the the Audacity driver selection combo box which probably currently shows 'MME' selected (you may need to show using menu item View -> Toolbars -> Device toolbar).

NB: The Audacity settings and preferences are stored in a folder "Portable Settings" next to the audacity program. If you want to use settings in the user's home directory then delete this folder.

ko-fi

When things go wrong

As with any complex software build there are many moving parts (including Windows itself) and things can sometimes go wrong. Here are some tips if you hit build errors.

If everyhting falls or you just want to shortcut lots of painful debugging then try a Microsoft Windows Virtual machine (VM) as mentioned above.

  • make sure you have latest script
  • make sure you are in a folder C:\projects in the cmd window
  • ensure you are an administrator on your Windows 10 or 11 64 bit PC (ie not a organisational PC)?
  • run the script with --cleanall and try again
  • uninstall all the tools and installers (Python, cmake, Visual Studio) and then reboot before trying again
    • note having other versions of any of the tools installed may well cause problems - remove them
  • ensure you ticked the specified options when installing Visual Studio and Python, reinstall if unsure
  • read the error output - clues are often buried in reams of impenetrable text
  • disable any Anti Virus - the built-in Microsoft one is usually not a problem
  • if your PC is not English make sure you have EN language packs installed for Windows and VS

Thanks

  • @diogodh for finding and fixing the bug with conan installations
  • The Audacity team for an fantastic audio tool

ko-fi

@echo off
rem Version: 2.4.0
rem
rem Build audacity with ASIO support on Windows
rem See the following gist for details
rem https://gist.github.com/SteveALee/da24c2be633340b8791066dd98eb5d0b
rem
rem Options (only one may be specified)
rem
rem --install or none - install tools and build
rem --build - build
rem --rebuild - cleanall and build
rem --clean - remove built files
rem --cleanall - remove fetched and built files
rem --cleaninstall - remove downloaded installation files
rem --getonly - only get the filesnot
rem --noget - buld but don't fetch again from git
rem -vj.m.p version - default is 3.3.3 (using conan 1.29, else conan 2.0.13)
rem
rem MIT licence
rem steve@opendirective.com
TITLE Build Audacity with ASIO
setlocal
rem Clean up arguments
set TARGET=%1
set VERSION=%2
rem substring on empty var fails within parenthesis
if not [%TARGET%] == [] set TARGET_PREFIX=%TARGET:~0,2%
if [%TARGET_PREFIX%] == [-v] (
set TARGET=%2
set VERSION=%1
)
if [%TARGET%] == [] set TARGET=--install
if [%VERSION%] == [] (
set AUDACITY_REL=3.3.3
) else (
set AUDACITY_REL=%VERSION:~2%
)
set VISUALSTUDIOVER=2022\Community
set VISUALSTUDIOCMAKE=Visual Studio 17 2022
set VSDIR=%ProgramFiles%\Microsoft Visual Studio\%VISUALSTUDIOVER%
set PROJROOT=C:\projects
set AUDACITY=%PROJROOT%\audacity
set AUDACITY_BUILD=%PROJROOT%\audacity-asio
set EXEDIR=%AUDACITY_BUILD%\Release
set INSTALLFILEDIR=bin
rem More vaiables set for --install
if [%AUDACITY_REL:~0,3%] == [3.4] (set CONAN_VER=2.0.13) else (set CONAN_VER=1.59.0)
rem check projroot exists
if /I not [%~dp0] == [%PROJROOT%\] (
echo.
echo Error: This script must be run in %PROJROOT% - see %%PROJROOT%% in file
echo.
if not exist %PROJROOT% (
echo Create %PROJROOT
goto exit
) else (
echo cd to %PROJROOT%
goto exit
)
)
echo.
echo Building Audacity %AUDACITY_REL% 64 bit release with ASIO support...
echo.
if not [%TARGET%] == [--install] if not [%TARGET%] == [--cleaninstall] goto clean
if [%TARGET%] == [--cleaninstall] echo Cleaning installation files... & rmdir /s/q %INSTALLFILEDIR% 2> :null
rem Get tools
rem ANSI escape sequences do not work in if () block so we use goto
set git-url=https://github.com/git-for-windows/git/releases/download/v2.43.0.windows.1/Git-2.43.0-64-bit.exe
set GITPATH=%ProgramFiles%\Git\cmd\
set vs2022-url=https://aka.ms/vs/17/release/vs_community.exe
rem Conan is installed later
rem Note Conan 1.59 has dependency issues with python 3.12
set python-url=https://www.python.org/ftp/python/3.11.0/python-3.11.0-amd64.exe
set PIPPATH=%LOCALAPPDATA%\Programs\Python\Python311\Scripts\
echo   
echo.
echo Fetching tools..
echo 
mkdir %INSTALLFILEDIR% 2> :null
curl -L %git-url% -o %INSTALLFILEDIR%\g4w.exe
curl -L %vs2022-url% -o %INSTALLFILEDIR%\vs.exe
curl -L %python-url% -o %INSTALLFILEDIR%\python.exe
echo   
echo.
echo Installing tools...
echo.
echo IMPORTANT!! Follow the instructions below for each installer
echo Close each installer when it is done before starting next
echo.
echo Git for Windows
echo Choose the option "Git from the command line"
pause
%INSTALLFILEDIR%\g4w.exe
echo.
echo Visual Studio: make sure you select the Workload "Desktop development with C++"
echo You can uncheck "Start After installation"
pause
%INSTALLFILEDIR%\vs.exe
echo.
echo Python: make sure you select "Add python.exe to PATH"
pause
%INSTALLFILEDIR%\python.exe
echo.
echo.
echo 
set installing=true
where /q pip & if ERRORLEVEL 1 path %PATH%;%PIPPATH%
where /q git & if ERRORLEVEL 1 path %PATH%;%GITPATH%
call :clean --rebuild
goto exit
rem subroutine
:cleanall
echo Cleaning source and built files... & rmdir /s/q %AUDACITY% %AUDACITY_BUILD% 2> :null
where /q conan & if ERRORLEVEL 0 echo Cleaning conan modules... & conan remove -f * 2> :null
exit /B
:clean
if not [%TARGET%] == [--getonly] (
if /I [%TARGET%] == [--clean] echo Cleaning built files... & rmdir /s/q %AUDACITY_BUILD% 2> :null & goto exit
if /I [%TARGET%] == [--cleanall] call :cleanall & goto exit
if /I [%TARGET%] == [--rebuild] call :cleanall
)
rem Launch cmake-gui
rem VS doesn't include this with it's cmake
rem if [%TARGET%]==[--gui] cmake-gui -Daudacity_has_asio_support=On -DAUDACITY_BUILD_LEVEL=2 -S %AUDACITY% -B %AUDACITY_BUILD% & goto build
:checktools
rem ensure tools are installed
if not [%TARGET%] == [--noget] (
where /q git & if ERRORLEVEL 1 echo Git for Windows does not appear to be installed. Re run with "--install" & goto exit /b
)
if not [%TARGET%] == [--getonly] (
if not exist "%VSDIR%\VC\Auxiliary\Build\vcvars64.bat" echo Visual Studio does not appear to be installed. Re run with "--install" & goto exit /b
if not defined VisualStudioVersion call "%VSDIR%\VC\Auxiliary\Build\vcvars64.bat"
where /q python & if ERRORLEVEL 1 echo Python does not appear to be installed. Re run with "--install" & goto exit /b
where /q conan & if ERRORLEVEL 0 pip show --version conan | findstr /R /C:"Version: %CONAN_VER%" & if ERRORLEVEL 1 echo conan %CONAN_VER% not found & pip uninstall -y -q conan
where /q conan & if ERRORLEVEL 1 echo installing conan %CONAN_VER% & pip install conan==%CONAN_VER%
)
rem Get source code
:getcode
if /I not [%TARGET%] == [--clean] (
if /I not [%TARGET%] == [--cleanall] (
if /I not [%TARGET%] == [--noget] (
echo Fetching code for Audacity %AUDACITY_REL%...
echo.
git clone -b Audacity-%AUDACITY_REL% --depth 1 https://github.com/audacity/audacity/ %AUDACITY%
if ERRORLEVEL 1 echo Error: cannot fetch the Audacity code. Try the --cleanall or --noget options & goto exit
)
)
)
if /I [%TARGET%] == [--getonly] goto exit
if not exist %AUDACITY%\CMakeLists.txt echo The code files appear to be missing from %AUDACITY%. & goto exit
:build
cd %AUDACITY%
cmake -G "%VISUALSTUDIOCMAKE%" -DCMAKE_CONFIGURATION_TYPES=Release -Daudacity_has_asio_support=On -DAUDACITY_BUILD_LEVEL=2 -S %AUDACITY% -B %AUDACITY_BUILD% & if ERRORLEVEL 1 echo Error: Cannot create Audacity buildfiles & goto exit
:build
cd %AUDACITY_BUILD%
set msbuild="%VSDIR%\MSBuild\Current\Bin\MsBuild.exe"
%msbuild% ALL_BUILD.vcxproj -p:configuration=Release
if ERRORLEVEL 1 echo Error: cannot build Audacity & goto exit
rem Settings stored with files rather than home directory
rem See https://manual.audacityteam.org/man/portable_audacity.html
mkdir %EXEDIR%\"Portable Settings"
cd %PROJROOT%
rem All done
echo 
echo.
echo Congratulations!
echo Your new Audacity %AUDACITY_REL% with ASIO support will now launch.
echo The ASIO options will appear if you have ASIO drivers and connected hardware
echo In future just run the audacity.exe. No need to install.
echo.
echo %EXEDIR%\audacity.exe
echo.
echo Or copy the folder
echo.
echo %EXEDIR%\
echo.
echo and run the included audacity.exe
echo.
echo Note settings and preferences are stored in "%EXEDIR%\Portable Settings"
echo If you want to use settings in the user's home directory then delete this folder.
echo.
echo 
start %EXEDIR%\audacity.exe
if defined installing exit /B
:exit
cd %PROJROOT%
endlocal
@Sky3RN
Copy link

Sky3RN commented Jun 20, 2023

It doesn't work with me..

I get stuck on the splash screen. I think portaudio_x64.dll is the issue. I tried swapping the portaudio dll with the original one and Audacity started but with no ASIO, I also copied the new compiled to the original Audacity and it didn't start (splash screen only). So yeah this file is causing trouble but I don't know why and how to solve it.

I spent hours and hours trying to compile and compile it again. Still stuck on the splash screen. Grrr.
Sometimes I get the popup asking for the ASIO I wand to use and splash screen again.

This is why I'm trying to compile Audacity with ASIO : audacity/audacity#4784

@SteveALee
Copy link
Author

@Sky3RN sorry to hear it does not work. Sadly I cannot offer any advice or support other than on this script that build Audacity. Just some random un tested thoughts.

  • I assume you have 64 bit Windows? Hard to image not these days :-P
  • Maybe something to do with French Language Windows? I know you need the English language pack to keep Visual Studio happy.
  • May be there is an Audacity log where startup errors are recorded? Did you explore the Windows error log?
  • You indicate a specific ASIO driver is causing problems so can you try another? Perhaps for other hardware? I don't know if the ASIO4ALL hack is compatible with Audacity.

Good luck.

@Sky3RN
Copy link

Sky3RN commented Jun 21, 2023

  • I assume you have 64 bit Windows? Hard to image not these days :-P

Sorry I didn't mention it. Yes, it's Win 10 64 bits.

  • Maybe something to do with French Language Windows? I know you need the English language pack to keep Visual Studio happy.

I've tried with French language, both French and English language, and also English language only. Same thing everytime.

  • May be there is an Audacity log where startup errors are recorded? Did you explore the Windows error log?

Yup, it might be, but I don't know where to find it. 😁 It's easier on Linux.. I'm not really familiar with Windows.

  • You indicate a specific ASIO driver is causing problems so can you try another? Perhaps for other hardware? I don't know if the ASIO4ALL hack is compatible with Audacity.

I tried with 2 different ASIO, one for my PreSonus StudioLive 16.0.2 and one for my Zoom UAC-232 (which is why I'm trying to compile Audacity). I never use the sh*tty ASIO4All. :)

@SteveALee
Copy link
Author

@Sky3RN

It's easier on Linux.. I'm not really familiar with Windows.

Any reason not to stick with Linux? It's been a decent desktop experience for a long time now. Is it availability of other software? Out of Interest which distro?

I tried with 2 different ASIO,

So it fails with two different manufacturer's drivers? Might be safe to assume doesn't work with any ASIO drivers? Hmm. I only have a McMillen ASIO driver. Will try to test a new build with it over next few days to ensure something did't go wrong when I bumped the Audacity build version.

never use the sh*tty ASIO4All.

Good plan. AFAIK it's only for use with ASIO only apps when you have no ASIO drivers. Trouble is many manufacturers got lazy and suggest you use it rather than supplying ASIO drivers. Not multi channel and not latency gains. Sigh. As you say "sh*tty " :)

@Sky3RN
Copy link

Sky3RN commented Jun 21, 2023

@SteveALee

It's easier on Linux.. I'm not really familiar with Windows.

Any reason not to stick with Linux? It's been a decent desktop experience for a long time now. Is it availability of other software? Out of Interest which distro?

The reason is more complicated than that !
I use Linux everyday for my "everyday tasks" as I could say. I use Windows only for two things : Recording / Mixing, and video editing.
I never use Audacity, I'm not a big fan of this software. But the reason why I'm trying to get this thing fixed is : As a sound engineer and YouTuber talking about sound, a lot of my audience are noobs using Audacity and nothing else. I recently did a video testing the new Zoom UAC-232 which is capable to record in 32 bits float, and I noticed it doesn't work on Audacity. In fact, it works fine with Audacity on Linux, but not with Audacity on Windows. By "doesn't work" I mean it's recognized but doesn't record in 32 bits float in Audacity for Windows 10.
That's why I'm trying to know why. And all of my researches led me to this point : Maybe it could come from this ASIO not supported natively on Audacity.

I tried with 2 different ASIO,

So it fails with two different manufacturer's drivers? Might be safe to assume doesn't work with any ASIO drivers? Hmm. I only have a McMillen ASIO driver. Will try to test a new build with it over next few days to ensure something did't go wrong when I bumped the Audacity build version.

Exactly, failed with the PreSonus driver and the Zoom driver. I've seen your script installs Audacity 3.3.2 and now the official release is 3.3.3, maybe it could be the cause ? I don't know. I'm not an expert in dev !

never use the sh*tty ASIO4All.

Good plan. AFAIK it's only for use with ASIO only apps when you have no ASIO drivers. Trouble is many manufacturers got lazy and suggest you use it rather than supplying ASIO drivers. Not multi channel and not latency gains. Sigh. As you say "sh*tty " :)

😁😁😁

@SteveALee
Copy link
Author

@Sky3RN So I'm a little confused now. Are you using both drivers with the same 32 bit capable Zoom hardware and get the same failure - hang during splash screen? Or different hardware for each driver and same failure? Or something else?

For your info I've found Audacity only adds the ASIO support UI when the hardware is connected using the ASIO driver. Might be relevant?

I'll look up your tube channel :)

I'll bump the version but I think you have same problem with both 3.3.2 with this script and 3.3,3 with Audacity project build?

@AdamWardUK
Copy link

@Sky3RN
Can't advise on this (not my area at all), but it occurred to me that testing https://www.wavosaur.com/ might help scope where the problem is - it supports ASIO without (being closed source) portaudio, so can perhaps help identify the issue as with portaudio itself or the underlying Windows support? And it might have some useful logging.

@Sky3RN
Copy link

Sky3RN commented Jun 21, 2023

@SteveALee

@Sky3RN So I'm a little confused now. Are you using both drivers with the same 32 bit capable Zoom hardware and get the same failure - hang during splash screen? Or different hardware for each driver and same failure? Or something else?

In fact, I have 3 soundcards plugged, all used "at the same time", I'm simply switching from one to another when needed, for multiple usages. So the failing is here with whatever soundcard and ASIO driver I use.

For your info I've found Audacity only adds the ASIO support UI when the hardware is connected using the ASIO driver. Might be relevant?

I've tried to compile with 2 of 3 soundcards disconnected, keeping connecting only the Zoom UAC-232 and.. Same issue !

I'll look up your tube channel :)

I don't know if you'll understand, it's all in French. :p

I'll bump the version but I think you have same problem with both 3.3.2 with this script and 3.3,3 with Audacity project build?

I'm trying right now to try with 3.3.3 (modified the "3.3.2" into "3.3.3" in the script) but keeps on failing.. Even with only 1 soundcard connected.

@AdamWardUK

Can't advise on this (not my area at all), but it occurred to me that testing https://www.wavosaur.com/ might help scope where the problem is - it supports ASIO without (being closed source) portaudio, so can perhaps help identify the issue as with portaudio itself or the underlying Windows support? And it might have some useful logging.

I'll have a look but I don't know how to proceed and I don't have enough time these days ! :/

@SteveALee
Copy link
Author

I bumped the Audacity version to 3.3.3 - https://github.com/audacity/audacity/releases/tag/Audacity-3.3.3

@SteveALee
Copy link
Author

@Sky3RN Compiling is independent of any sound hardware. The issue is how Audacity reacts when it runs. Perhaps having all hardware connected at once is confusing audacity. But you say even with just one. Or all the drivers?

I will double check it works with my ASIO hardware and let you know.

No I don;t speak French - looks good though. My wife is learning :)

@SteveALee
Copy link
Author

@Sky3RN did you try an ASIO DAW or some such to confirm the problem is with Audacity?

@SteveALee
Copy link
Author

@AdamWardUK oh, I see you suggested that too - thanks

@Sky3RN
Copy link

Sky3RN commented Jun 21, 2023

@SteveALee

I bumped the Audacity version to 3.3.3 - https://github.com/audacity/audacity/releases/tag/Audacity-3.3.3

Maybe I'm not sure what does "bumped" mean, but it looks like a real Audacity without ASIO.
As I told you before Audacity works fine, it's the version compiled with ASIO who doesn't work. So yeah, the 3.3.3 works, but 3.3.3 with ASIO doesn't work. Same for the 3.3.2.
I don't know if you see what I mean ?

Perhaps having all hardware connected at once is confusing audacity. But you say even with just one. Or all the drivers?

I tried with all hardware connected at the same time, and only with one connected.
Something's blocking and I can't find what and why..

No I don;t speak French - looks good though. My wife is learning :)

πŸ‘πŸ‘

did you try an ASIO DAW or some such to confirm the problem is with Audacity?

Yep. As far as it's my job, I'm using everyday Mixcraft, sometimes ProTools or Cakewalk or Studio One. Never had any issues with them.

To resume : Audacity works fine but doesn't record in 32 bits float, that's why I'm trying to compile it with ASIO, and when it's compiled it doesn't open and get stuck on the splash screen. Sometimes it asks for the ASIO driver but still gets stuck, and most of the other times I don't have the popup for ASIO selection.
I tried to compile and recompile again and again and again, I don't know how to force this popup to be shown ! It's seem to be a random thing.

@SteveALee
Copy link
Author

@Sky3RN I'm afraid I've run out of ideas for you. I just clean built 3.3.3 and it works fine with my McMillen K-mix ASIO driver. I needed to turn on the Device toolbar to see the ASIO option. It offers all 9 channels. I just didn't try any audio. But you don't get that far. :(

So I can only think it is a Windows issue - unlikely, an Audactity bug, an ASIO driver issue, or a audacity/driver compatibility issue.

In theory compiling twice will have been enough as installed drivers have no influence on the build, only the audacity version number
If you already had visual studio or python installed they may have been issues but I expected a build failure.
Note the --cleanall option deletes all fetched and built files but not the install tools. Try that an uninstalling the tools if you really want to

I can only wish you the best of luck. Sorry.

@Sky3RN
Copy link

Sky3RN commented Jun 22, 2023

@SteveALee I understand ! Nop unfortunately !

I used to think it's a Windows issue too, but I tried on 2 different computers. One is my main desktop, the other one is my laptop and they don't have the same setup at all. But they mostly have the same ASIO drivers installed (Zoom, PreSonus, ASIO Link Pro).
I tried with and without any gear connected, same issue : Stuck on the splash screen.

I might think it could be a driver compatibility issue but.. Which one ? I'll have to uninstall all the drivers to find out the messing one ! I'll try.

I use the --cleanall option ! ;-) And I already tried to uninstall the tools and reinstall everything with your script !

Well, thank you so much for your time and your kindness. I guess the only thing to do now is looking deeply on the Internet.

@SteveALee
Copy link
Author

@Sky3RN

I might think it could be a driver compatibility issue but.. Which one ? I'll have to uninstall all the drivers to find out the messing one ! I'll try.

Sadly that is probably your sensible next step. Uninstall all and add one at a time. Don't you just love computers! I'd try only the 32 bit one first as that's a bit unusual. I assume Audacity supports 32 bit OK?

@Giermann
Copy link

@Sky3RN

And I already tried to uninstall the tools and reinstall everything with your script !

Remember: the script offered here and the post-installed tools are only to compile Audacity!!
They neither affect the runtime of an ASIO build, nor are they necessary on every target machine.

You already wrote, that you checked your built portaudio_x64.dll with an original distribution and vice versa. Another option would be to share (NO - not to publish, only to share for testing) your built DLL with another person and/or get a running version from him or her. That way you could verify if it is really a driver issue with your drivers or a fault at build time.

@SteveALee
Copy link
Author

SteveALee commented Jun 22, 2023

@Sky3RN thanks @Giermann

I assumed you had no errors in the build and audacity was launched at the end? It seems so from what you say.

if you want to check for any errors / warnings you can run the following to build and send all output the file out.txt. But again I can;t really support you on build errors

build-audacity.cmd --clean > out.txt 2>&1

@Sky3RN
Copy link

Sky3RN commented Jun 22, 2023

@SteveALee

Sadly that is probably your sensible next step. Uninstall all and add one at a time. Don't you just love computers! I'd try only the 32 bit one first as that's a bit unusual. I assume Audacity supports 32 bit OK?

I just tried ! I've uninstalled all of my ASIO drivers, recompiled Audacity and.. Still doesn't work.
Yes it normally should support 32 bits float because it's working on Linux natively, didn't have to compile with ASIO.

@Giermann

Another option would be to share (NO - not to publish, only to share for testing) your built DLL with another person and/or get a running version from him or her. That way you could verify if it is really a driver issue with your drivers or a fault at build time.

I will try that !

@SteveALee

I assumed you had no errors in the build and audacity was launched at the end? It seems so from what you say.

I guess there was no error, but everytime I get a "121 avertissements" (I guess in English it's "121 warnings").

Here's the output file : http://pastebin.fr/129044

@htdSoundTech2020
Copy link

htdSoundTech2020 commented Sep 2, 2023

@SteveALee

It's easier on Linux.. I'm not really familiar with Windows.

Any reason not to stick with Linux? It's been a decent desktop experience for a long time now. Is it availability of other software? Out of Interest which distro?

The reason is more complicated than that ! I use Linux everyday for my "everyday tasks" as I could say. I use Windows only for two things : Recording / Mixing, and video editing. I never use Audacity, I'm not a big fan of this software. But the reason why I'm trying to get this thing fixed is : As a sound engineer and YouTuber talking about sound, a lot of my audience are noobs using Audacity and nothing else. I recently did a video testing the new Zoom UAC-232 which is capable to record in 32 bits float, and I noticed it doesn't work on Audacity. In fact, it works fine with Audacity on Linux, but not with Audacity on Windows. By "doesn't work" I mean it's recognized but doesn't record in 32 bits float in Audacity for Windows 10. That's why I'm trying to know why. And all of my researches led me to this point : Maybe it could come from this ASIO not supported natively on Audacity.

I tried with 2 different ASIO,

So it fails with two different manufacturer's drivers? Might be safe to assume doesn't work with any ASIO drivers? Hmm. I only have a McMillen ASIO driver. Will try to test a new build with it over next few days to ensure something did't go wrong when I bumped the Audacity build version.

Exactly, failed with the PreSonus driver and the Zoom driver. I've seen your script installs Audacity 3.3.2 and now the official release is 3.3.3, maybe it could be the cause ? I don't know. I'm not an expert in dev !

never use the sh*tty ASIO4All.

Good plan. AFAIK it's only for use with ASIO only apps when you have no ASIO drivers. Trouble is many manufacturers got lazy and suggest you use it rather than supplying ASIO drivers. Not multi channel and not latency gains. Sigh. As you say "sh*tty " :)

😁😁😁

The drivers from zoom for their smaller devices have always set the datachunk and native sample rate the computer will be "looking" for from the device. When this doesn't match up (usually DAW software to datachunk size for speed and memory use, Native sample rate to what's on the device itself) you can get all kinds of issues, from sound not showing up to driver not showing up. Also, 32bit windows doesn't exactly have an audio capability for 32bit float natively. I know this because every audio app I've tried in the 32bit versions only goes as high as 24bit. With Linux, you didn't have this problem because linux was 64bit only for a long while before 64bits became the norm for most Windows installations. If you are stuck with a 32bit windows, you are almost always limited to 24bits, 96k, accept with one or two software titles (can't remember which). If you are compiling a 64bit version and still don't get 32bit float (I've had no experience with your device here, so grain of salt), it may be connected to the driver, though I have seen that the device can use 24bit and the system 32 without problems in Adobe Audition. My experience with zoom devices has been that there is a driver interface that you can access to set the sample rate and the data chunk, but the device must be set to the right mode or you will not get audio; or you will get a message in your DAW that it isn't working. My H6 has 2 drivers installed. One is a simpler L\R stereo driver, another is the multitrack driver. If I set the device to Stereo for the connection and the PC for Multitrack, no go. If I set the data chunk wrong, the sound fragments. The sample rate can be higher than the project file, but lower and it'll stutter and possibly flag errors, showing you a thousand popup messages for all the samples you drop.
And the ASIO4ALL driver is not actually an ASIO driver, but an attempt at a clone of it. While I have always had access to the 32bit driver in 32bit Audacity, I haven't tried 64bits.
Here are the possibilities I can see:

  1. The DLL you are using is corrupted, replace it with a clean download.
  2. The DLL may be flagged as a "Dangerous" file by an AV like Windows Defender, fix that by allowing the file.
  3. The script is downloading new versions that mismatch (unlikely, but possible)
  4. If the DLL is the result of a Build operation, the build is done but one of the binaries or project files is missing or corrupted.
  5. You need to set your path variables on your own, since you may have UAC issues with that (a nasty little gift from Windows 7 that is helpful on occasion).

@SteveALee
Copy link
Author

@htdSoundTech2020 Thank you for your insights! It's a little hard to parse the one big paragraph but some thoughts.

  • This gist only automates the Audacity project build so any technical issues using Audacity need to be raised with the project team,
  • While the 32 Bit float audio resolution is not directly related to platform bit size, it makes sense 64 bits is required. To be honest older 32 bit platforms are likely to hit all sorts of support issues.
  • Yes ASIO4ALL is not ASIO - but this point confuses many due to the inaccurate name ASIO-fake or fauxASIO would be better. It makes normal windows sound appear to be the ASIO interface that Apps that require ASIO drivers demand. You don't get any of the ASIO benefits.

@mateusfig
Copy link

mateusfig commented Oct 9, 2023

No success. I tried it many time, many ways, with different Audacity version from 3.2.0. I uninstalled the previous Python and CMkake and installed this script's version. No way... I don't know what to do anymore. Always it end up with erros.

@Giermann
Copy link

Please post the errors here!
I didn't test the latest version yet, but I'm sure we'll find a solution... :)

@SteveALee
Copy link
Author

SteveALee commented Oct 10, 2023

Thanks @Giermann

@mateusfig I just did a full install and build and got no errors so the basic script is fine. SO perhaps somehting with you PC? There IS a lot of output, especially now conan is used but that's all normal "Noise". In addition to telling us what the errors are...

  • What version of Windows?
  • try the --cleanall command line option

@mateusfig
Copy link

Thanks @Giermann

@mateusfig I just did a full install and build and got no errors so the basic script is fine. SO perhaps somehting with you PC? There IS a lot of output, especially now conan is used but that's all normal "Noise". In addition to telling us what the errors are...

  • What version of Windows?
  • try the --cleanall command line option

Thanks for your feedback.

I use Windows 10 Pro (19045.3448).

I tried --cleanall a few times.

I will try build once again and I will try post the erros in the end of the proccess.

@SteveALee
Copy link
Author

Best of luck - do try grabbing a fresh copy of the script - just in case. I should put a version number at the top

@mateusfig
Copy link

mateusfig commented Oct 10, 2023

@SteveALee

I just tried once again with no success, using 2.0.1 scriptt version.

I appended the full output from cmd: https://pastebin.com/z69hRC8x

@SteveALee
Copy link
Author

@mateusfig @Giermann O wow,

so it seems to be barfing when trying to link to create a libsndfile conan component

That in turn maybe caused by this:

C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(249,5): warning MSB8065: Custom build for item "C:\Users\mmachado.conan\data\libsndfile\1.0.31__\build\899d2c53f1b9e4a7deb461e3cf1716f2d4fd697d\build\CMakeFiles\bf18e4cabeda36cd82ee3e51ae56b6cc\sndfile.def.rule" succeeded, but specified output "c:\users\mmachado.conan\data\libsndfile\1.0.31__\build\899d2c53f1b9e4a7deb461e3cf1716f2d4fd697d\build\src\sndfile.def" has not been created. This may cause incremental build to work incorrectly. [C:\Users\mmachado.conan\data\libsndfile\1.0.31__\build\899d2c53f1b9e4a7deb461e3cf1716f2d4fd697d\build\sndfile.vcxproj]

There were a LOT of warnings for that file which to me is a code smell but might have been expected.

I noticed some output text "VersΓ£o do MSBuild 17.7.2+d6990bcfa para .NET Framework" and previously a French native had problems which caused us to mention in the Gist instructions that English language packs might be required for both Windows and Visual Studio. The errors don't indicate language filename problems, but perhaps something to do with incremental build (why?)

Otherwise I'll have to pass over the @Giermann

When I have time I'll compare to me logs

@mateusfig
Copy link

@SteveALee ,

Loads of errors...

My native language is portuguese. My Visual Studio has english language package, but my Windows 10 doesn't. I will try installing english language pack on Windows 10.

@mateusfig
Copy link

mateusfig commented Oct 10, 2023

That's the CMakeError.log content:

https://pastebin.com/CDFDwjev

@SteveALee
Copy link
Author

@mateusfig is that after installing the Windows EN language pack? It seems it cannot locate the [we function in MSVC (the C compiler included in Visual Studio)

As we have no idea what kind of mess Microsoft might have made of language dependencies (if any) I I would uninstall/reinstall everything and be sure to run --cleanall. Sorry for this pain.

@Giermann
Copy link

@mateusfig
First of all, markdown language seems not to be the best choice to paste large text files. Maybe you should better use another service, for example pastebin.com and only copy the link to the files here.
If you are able to do that, it would be much easier to follow other comments if you paste your files there and then edit your comments - thank you very much!

But now to your issue: I just started a fresh run of the provided script on a (nearly) clean install of Windows (German) and the build succeeded without errors.
Then I compared the output and also identified the already mentioned warning "MSB8065" to be the main difference. For some reason, it is not creating the "sndfile.def" in libsndfile which finally leads to error "LNK1104".

A Google search returned a similiar issue (reported at StackOverflow) when the manually set date of a computer was before the creation of the source files. So I did some tricks to verify that, but was only able to verify it with a date after 12th of September, because git refuses to connect to sites with invalid SSL certificates.
But even this completed successfully (all runs with 121 warnings).
So, I don't know how to continue from here...

@SteveALee
Copy link
Author

SteveALee commented Oct 11, 2023

@Giermann Great work. Thanks for confirming it can work! I agree with your error detection - that was the first I saw.

As far as I recall git doesn't preserve file timestamps on clone/fetch (a right pain). So as long as a --cleanall or otherwise deleting the source was was done , forcing the files to be re fetched they'd have to be dated before current clock time - unless there is a really weird clock thing happening. Perhaps if localisation of time format is different between Windows GUI and command line - clutching at a straw there. I'm also stuck I'm afraid.

@mateusfig
Copy link

@mateusfig is that after installing the Windows EN language pack? It seems it cannot locate the [we function in MSVC (the C compiler included in Visual Studio)

As we have no idea what kind of mess Microsoft might have made of language dependencies (if any) I I would uninstall/reinstall everything and be sure to run --cleanall. Sorry for this pain.

I don't have installed EN language pack still. I will try it. I guess also this is the problem.

@mateusfig
Copy link

@mateusfig First of all, markdown language seems not to be the best choice to paste large text files. Maybe you should better use another service, for example pastebin.com and only copy the link to the files here. If you are able to do that, it would be much easier to follow other comments if you paste your files there and then edit your comments - thank you very much!

But now to your issue: I just started a fresh run of the provided script on a (nearly) clean install of Windows (German) and the build succeeded without errors. Then I compared the output and also identified the already mentioned warning "MSB8065" to be the main difference. For some reason, it is not creating the "sndfile.def" in libsndfile which finally leads to error "LNK1104".

A Google search returned a similiar issue (reported at StackOverflow) when the manually set date of a computer was before the creation of the source files. So I did some tricks to verify that, but was only able to verify it with a date after 12th of September, because git refuses to connect to sites with invalid SSL certificates. But even this completed successfully (all runs with 121 warnings). So, I don't know how to continue from here...

I'm sorry for my long text post. I just corrected this with pastbin.com

My issue is kind of weird. I will try the build on another computer (no EN language package also) and see what I 'll get.

@mateusfig
Copy link

@mateusfig is that after installing the Windows EN language pack? It seems it cannot locate the [we function in MSVC (the C compiler included in Visual Studio)
As we have no idea what kind of mess Microsoft might have made of language dependencies (if any) I I would uninstall/reinstall everything and be sure to run --cleanall. Sorry for this pain.

I don't have installed EN language pack still. I will try it. I guess also this is the problem.

I installed EN language pack and got same issue.

@Giermann
Copy link

Did you already try on another computer?
Can you also try to change line 137 in the script and modify "-Daudacity_has_asio_support=On" to "-Daudacity_has_asio_support=Off"?
I'm pretty sure, the problem is related to the build in general, not ASIO specific.

If this also fails, it would be time to open an issue to get support from the Audacity team:
https://github.com/audacity/audacity/issues

@Giermann
Copy link

Giermann commented Oct 13, 2023

Another idea: the issue leading to MSB8065 seems to be compiler dependent.
You could try to use another version of Visual Studio, i.e. 2019 instead of 2022.

To do so, uninstall all components (Python, cmake, Visual Studio and its installer), reboot and try again with a fork of Steves script, which I modified to choose the VS version:
https://gist.github.com/Giermann/c3f88ee2a147f9a688a2ca76e1334a54
Set VISUALSTUDIO_REL in line 34 to either 2019 or 2017 and then start from scratch with "--install" and so on...

@SteveALee
Copy link
Author

SteveALee commented Nov 4, 2023

I updated to Audacity 3.4.0 and switched to using the "cmake" that comes with Visual Studio. This means the cmake-gui option is no longer available.

I also cleaned up the flow so the --install option no longer required a new cmd window to be opened .

@SteveALee
Copy link
Author

Due to the number of issues with Audacity 3.4.0 this builds 3.3.3. If you want 3.4 then use "build-audacity.cmd -- install -v3.4"

Copy link

ghost commented Nov 10, 2023

All I get is "Error: Cannot create Audacity buildfiles" over and over cmake just gives a conan error when I try to build in there. I have been at this all day somehow I feel Audacity is just not worth my time.

@SteveALee
Copy link
Author

SteveALee commented Nov 11, 2023

@ZardozXerxes So sorry to hear your frustration. Tech build can so often be like that, there are so many variables to get lined up. Can you use the release Audacity without ASIO while you try to figure this out?

I've just tried again and all is well with the script. So there's something not quite right with your setup. We'd need more info to help.

Are you building 3.3.3 (the default) or -3.4.1 (needs -v3.4 option)? 3.3.3 is still the most reliable.

Please ensure you have followed the instructions EXACTLY. Here are some key points

  • Do you definitely have the latest script version 2.2.2? Re download to be sure.
  • Are you an administrator on your WIndows 10 or 11 64 bit (ie not a organisational PC)?
  • Make sure you are in a folder C:\projects in the cmd window
  • If your PC is not English make sure you have EN language packs installed for Windows and VS
  • Ensure you ticked the specified options when installing Visual Studio and Python (you probably did)
  • You could try the --cleanall and then --cleaninstall options (seperately) to delete any files lying around

Best of luck!

@SteveALee
Copy link
Author

@ZardozXerxes I did find a small bug but only if not using the specified --install option. Please try new script version 2.2.3

Copy link

ghost commented Nov 11, 2023

I already have Audacity but I need to record from my UA Apollo Twin X line in and that can only be done via ASIO.
Yes I had version 2.2.2, I just ran the scrip I did not change the version so I presume it was 3.3.3, yes I am admin, yes I am in the specified folder, I am in English, I had already specified the options from trying and failing to build it myself using Cmake, I tried the --cleanall a few times but not the --cleaninstall as I was just following the instructions as written, that said I did clear the entire project folder a few times. I will try the new script. Unrelated but I think this might be a typo "follow the prompts, pressing a ket to start each tool's installer in turn".

Copy link

ghost commented Nov 11, 2023

I tried the new script many times and got the same error, I thought it might be a conan version error or conflict so I checked if it was already installed and it was not, so I tried installing it first and then with it uninstalled. Here is the error in full.

conan install: error: unrecognized arguments: --install-folder C:/projects/audacity-asio\conan-install-release
ERROR: Exiting with code: 2
Restoring global Conan config...
Traceback (most recent call last):
File "C:\projects\audacity\conan\conan_runner.py", line 339, in
subprocess.check_call(conan_options)
File "C:\Users****\AppData\Local\Programs\Python\Python312\Lib\subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['conan.exe', 'install', 'C:\projects\audacity\conan', '--build=missing', '--install-folder', 'C:/projects/audacity-asio\conan-install-release', '--output-folder', 'C:/projects/audacity-asio', '--remote', 'audacity-binaries', '--profile:build', 'C:/projects/audacity-asio\profile-build.profile', '--profile:host', 'C:/projects/audacity-asio\profile-host-release.profile']' returned non-zero exit status 2.
CMake Error at cmake-proxies/cmake-modules/AudacityDependencies.cmake:202 (message):
Conan failed to install dependencies (1) C:/Users/Sam
Cartman/AppData/Local/Programs/Python/Python312/python.exe
Call Stack (most recent call first):
CMakeLists.txt:572 (include)

-- Configuring incomplete, errors occurred!
Error: Cannot create Audacity buildfiles

I found a program installed called something like conan version manager I think it was installed by Visual studio, I uninstalled it and got further and now have another error.

pkgconf/2.0.3: pkgconf/2.0.3: ERROR: Package '2d91722813283545a5bec8be869b6396b7c40537' build failed

pkgconf/2.0.3: WARN: Build folder C:\Users*.conan\data\pkgconf\2.0.3__\build\2d91722813283545a5bec8be869b6396b7c40537\build-relwithdebinfo
ERROR: pkgconf/2.0.3: Error in build() method, line 92
meson.configure()
ConanException: Error 9009 while executing meson setup --native-file "C:\Users*
.conan\data\pkgconf\2.0.3__\build\2d91722813283545a5bec8be869b6396b7c40537\build-relwithdebinfo\conan\conan_meson_native.ini" "C:\Users*.conan\data\pkgconf\2.0.3__\build\2d91722813283545a5bec8be869b6396b7c40537\build-relwithdebinfo" "C:\Users*.conan\data\pkgconf\2.0.3__\build\2d91722813283545a5bec8be869b6396b7c40537\src" -Dprefix="C:\Users*.conan\data\pkgconf\2.0.3__\package\2d91722813283545a5bec8be869b6396b7c40537"
Restoring global Conan config...
Traceback (most recent call last):
File "C:\projects\audacity\conan\conan_runner.py", line 339, in
subprocess.check_call(conan_options)
File "C:\Users*
\AppData\Local\Programs\Python\Python312\Lib\subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['conan.exe', 'install', 'C:\projects\audacity\conan', '--build=missing', '--install-folder', 'C:/projects/audacity-asio\conan-install-release', '--output-folder', 'C:/projects/audacity-asio', '--remote', 'audacity-binaries', '--profile:build', 'C:/projects/audacity-asio\profile-build.profile', '--profile:host', 'C:/projects/audacity-asio\profile-host-release.profile']' returned non-zero exit status 1.
CMake Error at cmake-proxies/cmake-modules/AudacityDependencies.cmake:202 (message):
Conan failed to install dependencies (1) C:/Users/****/AppData/Local/Programs/Python/Python312/python.exe
Call Stack (most recent call first):
CMakeLists.txt:572 (include)

-- Configuring incomplete, errors occurred!
Error: Cannot create Audacity buildfiles

@SteveALee
Copy link
Author

SteveALee commented Nov 11, 2023

@ZardozXerxes Oh dear.

I just released script 2.2.4 so you should try that (though earlier should have worked) As there is so much I do not know about your set up best you do a clean build from the top.

I did spot you have python 3.12 and I got errors building due to conan dependency problems. The script installs python 3.11 Use that!

  • Uninstall Visual Studio and Python and their installers - 4 programs
  • run "build-audacity.cmd --cleanall"
  • run "build-audacity.cmd" or "build-audacity.cmd -v3.4.1" The --install option is now the default

If that doesn work I'm at a loss

@SteveALee
Copy link
Author

SteveALee commented Nov 11, 2023

[Update] The --install option is now the default as that is most likely what post people will want. The --build option will build with out installing build tools first.

Copy link

ghost commented Nov 12, 2023

@SteveALee Yes I thought of that too and uninstalled all versions of python but the result was the same. 2.24 is not working, the same as the last. The only things installed now are Git For Windows and Visual Studio before I run the script. This is the first thing I have ever tried to build from git hub (and probably the last after this) so I have no idea why it isn't working.

@SteveALee
Copy link
Author

@ZardozXerxes

2.24
What is that? The script will build 3.3.3 or 4.2.1. The dependencies are way too complex to support more

The only things installed now are Git For Windows and Visual Studio before I run the script
Why is VS installed. I suggested you uninstalled it first. I know it's slow but otherwise you are not in a state I can support. What VS pre installed before you tried to build? If s owhat version? i try to be clear in the instructions that if you already have a dev env setup then they may well be problems due to tool dependencies.

Oh you should check no CMAKE is installed.

You can't really blame github -this is gist (lol) though yes it does fetch the source from git. That's incredibly common. The problem is most likely something to do with your specific PC config being out side the tested bounds. It happens sadly. So do you build other software? Again that indicates you might have a dev env on your PC that might clash.

@scerazy
Copy link

scerazy commented Nov 13, 2023

@ZardozXerxes

Stop complaining, spring up plain Win 1x VM in whatever (Hyper-V, Virtualbox, VMware player etc) and run the script. The result will be surprising, it will just work

after you can ditch the VM and get back to your setup

@SteveALee
Copy link
Author

SteveALee commented Nov 13, 2023

@scerazy I quite forgot that option! Thanks. I see MS have just updated the VMs. I'll make it stand out more in the notes.

@SteveALee
Copy link
Author

Audacity 3.4.2 tested. use -v34.2 option - see notes

@lammersma
Copy link

Hi @SteveALee , thanks for this amazing script.
I have used the Sandbox in Windows 11. Maybe a bit slower, the whole process took almost an hour, but worked great.
I had some issues with the result. It kept crashing. First it complained about missing avformat dll's. I installed FFMpeg to solve that issue. The second was the language. Audacity used 'Dutch' as language. After switching it to English, I was able to record all 15 tracks of the Rodecaster Duo.
BTW, I used the version of a few days ago. I will try to build the new script as well to get Audacity 3.4.2

Thanks again for the amazing script! And I just bought you a Ko-fi :)

@SteveALee
Copy link
Author

@lammersma wow, I completely forgot about sandbox! I tried once when it launched and found it a bit buggy. Thanks for the tip. That is rather slow, but VirtulBox is not fast (VMware player is useless if using Hyper-V, eg for WSL).

I think there are plenty of crashing bugs left in 3.4.x :D but 3.4.2 does seem better. I'll leave the script defaulting to 3.3.3 for a bit longer.

The Language thing is weird. Maybe the sandbox is not quite localised correctly. Good to know you fixed it and it is actually useful!! Even better to know you brought me a ko-fi!!

Copy link

ghost commented Nov 17, 2023

@scerazy

I came here for help not trolling and disrespect, nothing I have said is complaining I am just trying to get it to work.
Creating a VM is not a solution, this should work without a clean version of windows or its not much use to anybody.

@Sky3RN
Copy link

Sky3RN commented Nov 17, 2023

@SteveALee

I bumped the Audacity version to 3.3.3 - https://github.com/audacity/audacity/releases/tag/Audacity-3.3.3

Maybe I'm not sure what does "bumped" mean, but it looks like a real Audacity without ASIO. As I told you before Audacity works fine, it's the version compiled with ASIO who doesn't work. So yeah, the 3.3.3 works, but 3.3.3 with ASIO doesn't work. Same for the 3.3.2. I don't know if you see what I mean ?

Perhaps having all hardware connected at once is confusing audacity. But you say even with just one. Or all the drivers?

I tried with all hardware connected at the same time, and only with one connected. Something's blocking and I can't find what and why..

No I don;t speak French - looks good though. My wife is learning :)

πŸ‘πŸ‘

did you try an ASIO DAW or some such to confirm the problem is with Audacity?

Yep. As far as it's my job, I'm using everyday Mixcraft, sometimes ProTools or Cakewalk or Studio One. Never had any issues with them.

To resume : Audacity works fine but doesn't record in 32 bits float, that's why I'm trying to compile it with ASIO, and when it's compiled it doesn't open and get stuck on the splash screen. Sometimes it asks for the ASIO driver but still gets stuck, and most of the other times I don't have the popup for ASIO selection. I tried to compile and recompile again and again and again, I don't know how to force this popup to be shown ! It's seem to be a random thing.

Hey guys, it still doesn't work with me. πŸ™„
I've tried to turn my Windows in English only, installed EN lang-packages for VS, etc.. Done everything's written on this README part, also tried to download ASIO SDK as in the video, etc..
Nothing seems to work at all, I still get stuck on the splash screen of Audacity. Tried on 2 computers. Same result. Even with the new 3.4.2 version.
How-the-hell did you all make it work ?!

Maybe.. Can anyone send me his compiled and working Audacity-ASIO version ? To see if it works fine with me ?

Copy link

ghost commented Nov 17, 2023

@SteveALee
"You can't really blame github -this is gist (lol)" - I am not blaming anything I just said that this will be the last time I try to build anything from Github, also I a am not just referencing this script page as I mentioned before I came here I was trying to build it on my own directly from github and that wasn't working thats why I ended up here.
I already said "The only things installed now are Git For Windows and Visual Studio" so no Cmake is not installed.

@SteveALee
Copy link
Author

@scerazy @Sky3RN @ghost I'm sorry you are all having problems. Sadly there is such a incredibly wide range of possible PC configs that some will just fail. I have tested on the few I have access to. This all takes time and I provide this as a voluntary service for the Audacity community.

If you do not want to run a VM as a hopefully clean working environment then can you try another PC? You can just copy the built files. What you can't do is give to other people under steinbergs licence conditions. Someone just mentioned success building with the windows Sandbox, a kind of simple built in VM.

If it build but does not run then I suggest talking to the project devs. FYI Audacity on my main PC takes ages to start, the splash dissappears but it does eventually start up.

I wish you luck.

@SteveALee
Copy link
Author

@scerazy @Sky3RN @ghost do make sure you grab the latest script and use the --cleanall. Also uninstall VS and python for the best chance of it working.

@Sky3RN
Copy link

Sky3RN commented Nov 17, 2023

If you do not want to run a VM as a hopefully clean working environment then can you try another PC? You can just copy the built files. What you can't do is give to other people under steinbergs licence conditions. Someone just mentioned success building with the windows Sandbox, a kind of simple built in VM.

My goal is to make it work on a real Windows machine, not a VM. I need it to work for a real time usage, and most of all, not for me but for all the people who are trying to record in 32 bits float as I mentioned before. But this is a struggle.. Argh.
I don't know what Sandbox is and if it's too hard to make it work it's not worth it. I mean, I'm a sound engineer making videos on YouTube to explain why people should buy a 32 bits float soundcard and it works fine with any DAW but not with Audacity, and noobs people who are watching my videos use Audacity. πŸ˜… If it wasn't for them, I would have never used Audacity. I hate this Audashitty. πŸ˜ƒ
In that way, people won't use VMs or Sandbox or something else. They need it to work on their own machine. They don't even know how to access an URL without using Google. πŸ™„

If it build but does not run then I suggest talking to the project devs. FYI Audacity on my main PC takes ages to start, the splash dissappears but it does eventually start up.

I already tried to tell them but they are closed-minded like Β« The problem doesn't come from Audacity Β» blah blah blah.

@scerazy @Sky3RN @ghost do make sure you grab the latest script and use the --cleanall. Also uninstall VS and python for the best chance of it working.

I already tried this a bunch of time !

@haberl333
Copy link

After compiling Audacity with ASIO successfully for nearly one year by using this great build-tool I got strange results in the last week: The build process (build-audacity.cmd version 2.2.6) is running in my VM (Win 10) successfully, but the started Audacity version 3.4.2 is missing the "Libraries" command in Edit->Preferences. Normally it is listed between Import/Export and Directories. Therefore I can't use ffmpeg in Audacity any more and can only open .aup3 projects, no audio import or export. Looking in Help->About Audacity->Build Information it says ffmpeg is enabled. I also tried to install FFmpeg for Windows in my virtual machine and rebuild it, but without success. This problem started with version 3.4.1. I would be greatful for any advice.

@SteveALee
Copy link
Author

SteveALee commented Nov 19, 2023

@haberl333 I have just been informed there is a change to the build process to build everything but the build docs were not updated. You're the second person to have ffmpeg problems. My basic smoke test passed though.

I'll look at this ASAP.

@haberl333
Copy link

Thanks for this quick answer. I just found a solution/workaround. Up till Version 3.4.0 alpha it was sufficient, to copy all files from release directory in my VM to any directory in my main machine, add subdir Portable Settings to get a new portable version (I cannot bring myself to delete old running versions). And that is the problem with the latest builds like you mentioned. To workaround this I installed an official Audacity without ASIO (exactly same version!) and then copied all the self builded files on it, and voila I found Libraries command again. Moreover I copied all the files of the official install directory in c:\program files\audacity... back to my personal local directory with Portable Settings subdir included and also this version now works well...

Nevertheless many thanks for your build-command file, and I hope you will find time for future updates .

BTW: I also had problems in the beginning with version 3.4.0. And I solved it, by cleaning my VM from my Visual Studio Community version included C# support.

@SteveALee
Copy link
Author

Hmm thanks. It was always possible to copy the built version files without officially making in any sort of portable app. Seems I need to dig. Progress hey!?

@SteveALee
Copy link
Author

SteveALee commented Nov 19, 2023

Yeah, I suggested removing provided VS in windows dev VM as is an unknown.

@SteveALee
Copy link
Author

Updated script to build all components including plugins for FFmpeg etc. Also creates the "Portable Settings" folder for preferences.

Thanks @haberl333 and Ed Witles for helping to identify and fix the issue.

@SteveALee
Copy link
Author

[Update] Version: 2.4.0 of script now installs Git for Windows. Also better at updating path on install.

@rhcaldwell
Copy link

Truly a labor of love, thanks for doing it. I’m going to give it a shot.

@SteveALee
Copy link
Author

@rhcaldwell definitely made with love and quite a bit of labour given windows cmd script! Lol. It usually just works. Good luck.

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