2020. 3. 3. 20:25ㆍ카테고리 없음
What should I do if I get errors building Audacity?Audacity provides ready-built installer programs for Windows and Mac, but Audacity can also be built fromon any platform. With a little knowledge, building is a great way tocustomize Audacity!
For help, please see the Wiki documentation for, and.If you still cannot build Audacity, please ask on the board on the. Please tell us whether you are building from a release tarball or Audacity HEAD.
On Windows, please give all the instances of 'ERROR' in the Visual Studio output window (including Linker errors). For Mac and Linux, please provide the last lines of the configure or make output that fail. For Linux, also tell us which distribution and release you are using (for example, Ubuntu 11.10 or Fedora 16).
Windows: How do I install Audacity, and do I have to uninstall a previous version first?Save: On the,left-click the 'installer' link to save it to your computer. Check thebrowser preferences if necessary to find out where your downloads aresaved. Alternatively, right-click over the link, 'Save Target As' or'Save Link As' and choose the location to save the file to. Thendouble-click the downloaded.exe file to start the installer.
You mustbe an administrator on the computer to do this, or follow the prompts toconfirm your permission to install.Run: Using Internet Explorer and a few other browsers, youcan left-click the 'installer' link and select an option to 'Run' thefile. This launches the Audacity setup immediately. Note: Some security programs will query or block installers running from the computer's temporary space.Updating a previous installation: If you install a new Audacityversion after installing a previous one, the installer will offer toinstall to the same directory as the previous installation.
If theprevious installation was Audacity 1.2 or 2.x, the installationdirectory is normally Program FilesAudacity (or Program Files(x86)Audacityon 64-bit Windows). As long as you don't change the installationdirectory, Audacity will install over the previous 1.2 or 2.x version,and any extra plug-ins you added to the 'Plug-Ins' folder will still beavailable.If the previous version was 1.3.x, please uninstall 1.3before installing the current 2.x version. After uninstalling 1.3, anyextra plug-ins you added to that version will remain, and you can movethem to the 'Plug-Ins' folder of the new installation.Updating optional libraries: If upgrading from Audacity 1.3.6 or earlier, you must update to the MP3 encoding library. Otherwise there is no need to upgrade LAME or unless this is indicated in the for the new version of Audacity. Windows: How can I fix 'Application configuration incorrect' when first launching Audacity after installation?You may see the error Application configuration incorrect or error 14001when launching Audacity after installation. This mainly affects someWindows XP or 2000 machines. This can be fixed by downloading andinstalling the appropriate Microsoft 'Redistributable Package' asfollows:.
Audacity Vst Plugins
for 32-bit Windows. for 64-bit Windows.Be sure to get the correct package according to whether you have32-bit or 64-bit Windows. To check if you have 64-bit Windows,right-click over My Computer and choose Properties. If 64-bit is not mentioned, you have 32-bit.
Windows: How do I uninstall Audacity?Audacity can be uninstalled by choosing ' Add/Remove Programs' or ' Uninstall a program'in the Windows Control Panel. Select 'Audacity' from the list andfollow the instructions which will launch the Audacity uninstallprogram. Make sure you quit Audacity before uninstalling, or you willreceive errors that some files could not be removed.If the Control Panel cannot uninstall Audacity, open the folderin which you installed Audacity and double-click 'unins000.exe' (thisfile might have other numbers in the name). This requires 'unins000.dat'(or similar) to be present in the installation folder.If you still cannot uninstall Audacity,the installer again. Install Audacity to the same location youinstalled it to before (which happens by default). This will replace theuninstall files with good copies, then you can run the uninstalleragain.Uninstallation leaves your Audacity settings intact, in case youwant to install Audacity again at some time in the future. If you wantto remove your settings as well, delete Audacity's folder forapplication data whose location is given.See also.
Mac OS X: Why do I see 'unidentified developer', 'Mac App Store' or 'damaged' messages when I launch Audacity?On OS X 10.7.5 and later, the Applefeature controls launching of applications downloaded from theinternet. If Gatekeeper won't launch Audacity because it is 'from anunidentified developer' or 'not downloaded from the Mac App Store',right-click or control-click on the Audacity application in Finder,choose 'Open', then in the dialog box that appears, choose 'Open'. Youshould then be able to launch Audacity normally on subsequent occasions.Occasionally, you may see an error message that 'Audacity isdamaged and can't be opened. You should move it to the Trash.' If thismessage persists when you right-click or control-click over Audacity,open Apple menu System Preferences Security & Privacy: General tab.Under the header 'Allow applications downloaded from:', choose'Anywhere'. Audacity should now launch.
It would now be advisable tochange the 'Anywhere' preference back to a more restrictive setting. Mac OS X: How can I solve Audacity not appearing then crashing every time I launch it?If you launch Audacity but see nothing except a Mac crash report, this is most likely due to incompatible (AU) plug-ins on your system. Currently, Audacity automatically loads all Audio Units that it detects each time you launch it.To prevent the crash it will be necessary to either edit thesettings file to disable loading of Audio Units, or to determine fromthe crash report(s) which Audio Units are failing then move them toanother location where Audacity cannot detect them.If the crash occurs after pressing OK on the dialog, then one of the plug-ins you enabled in the dialog is causing the crash. In that case you can use the dialog to do one of the following:.
Uncheck all (or individual) VST effects to prevent them loading then click OK. Click Cancel to load none of the effects but be presented with the installation dialog again at next Audacity launch.Alternatively you can identify the VST plug-in which crashed from the Mac crash report and move it to another location.For help with editing audacity.cfg and locating or moving AU or VST plug-ins, please see ' on our.See also. How do I reset my Audacity settings?Uninstalling Audacity does not automatically repair or reset your settings in Audacity.
If you are trying to fix a problem with Audacity, take one of the following actions. Quit Audacity and using the audacity.cfg settings file. There is then no need to uninstall and re-install. Alternatively, Windows users may run the installer and in the'Select Additional Tasks' screen, put a check in the 'Reset Preferences'box. Complete the installation. On launching Audacity, a dialog willappear where you can confirm if you want to reset preferences just thisonce, or not.See also.
Alternative zip download for Lame 3.98.2. Download from the external download site. Extract the contents of the zip to a folder called'LameLibraryv3.98.2forAudacityonOSX' anywhere you have fullpermissions (such as your Desktop). Click Audacity then choose 'Libraries' on the left. Click 'Locate.'
Under 'MP3 Export Library', then 'Browse.' In the 'Locate Lame' dialog. Navigate to and open the folder you extracted the zip to, select 'libmp3lame.dylib', click 'Open' then 'OK' and 'OK'.This is a good solution if Audacity does not recognize or workcorrectly with libmp3lame.dylib when installed to/usr/local/lib/audacity.You should now be able to export MP3s without any further configuration, choosing File then selecting 'MP3 Files' in the.In case of difficulty, or if you have an older version of Audacity, please view our on the.
Some Linux distributions (for example, Ubuntu) nowpackage Audacity with MP3 encoding and FFmpeg support already linkeddynamically to the relevant system libraries. In these packaged buildsthere is no need to locate LAME or FFmpeg, so Audacity will have no'Libraries' Preferences. Users compiling Audacity from source code can similarly removethe 'Libraries' Preferences by configuring Audacity with-disable-dynamic-loading then build Audacity linked to both system LAMEand FFmpeg. Otherwise, users building Audacity from source must locatea compatible build of LAME in the 'Libraries' Preferences as.Most distributions have some sort of package manager that fetchessoftware packages from the Internet and installs them for you. Openthat package manager, search for LAME, and install it if it is notalready installed.Installing LAME on Ubuntu 11.10 and laterIn Ubuntu 11.10 and later the default package manager is the 'UbuntuSoftware Center'. Locating LAME. Open Audacity, click Edit then on 'Libraries' in the list on the left.
In 'MP3 Export Library' check if a LAME version number displaysto right of 'MP3 Library Version'. If so, LAME has been detected andyou should now be able to export MP3 and skip the remainder of theseinstructions. If the MP3 Library is stated as 'not found':. Click the 'Locate.” button.
In the 'Locate Lame' dialog that appears, click 'Browse'. In the 'Where is libmp3lame.so.0?'
Dialog, navigate to thelocation you noted in step 9, select 'libmp3lame.so.0', click 'Open',then 'OK' and 'OK' to exit PreferencesIf your distribution does not have a LAME package, please view these on the. Alternative zip download for FFmpeg 0.6.2.
Download from the external download site. Extract the contents to a folder called'FFmpegv0.6.2forAudacityonOSX' anywhere you have full permissions(such as your Desktop) then follow the instructionsto locate libavformat-52.dylib using the Libraries Preferences. This isa good solution if Audacity does not recognize or work correctly withlibavformat-52.dylib when installed to /usr/local/lib/audacity. You can also build Audacity from SVN and link to a system copy of FFmpeg built from source, using. Some Linux distributions (for example, Ubuntu) nowpackage Audacity with MP3 encoding and FFmpeg support already linkeddynamically to the relevant system libraries. In these packaged buildsthere is no need to locate LAME or FFmpeg, so Audacity will have no'Libraries' Preferences.
Users compiling Audacity from source code can similarly removethe 'Libraries' Preferences by configuring Audacity with-disable-dynamic-loading then build Audacity linked to both system LAMEand FFmpeg. Otherwise, users building Audacity from source must locate acompatible build of FFmpeg in the 'Libraries' Preferences as.You may download (or build) a suitable FFmpeg library for your own purposes. To build, obtain the source code from the.If you download a pre-built library, this might be either a 'shared' or'static' build. A static build consists of a single libavformatlibrary, whereas a shared build has at least three libraries(libavformat, libavcodec and libavutil). It is recommended to use ashared build, but Audacity will also work with a static build.If you compile Audacity from source code, it will link to theinstalled FFmpeg headers, which should always be compatible with aninstalled FFmpeg binary. Locating the FFmpeg library manuallyIf you installed FFmpeg while Audacity was running, or if youinstalled FFmpeg to a non-default location, Audacity will ask you toconfigure Preferences to locate the FFmpeg library.
To do this, access then the 'Libraries' tab on the left:As seen in the image above, the 'FFmpeg Library Version' will say 'not found'. To correct this:. Click the 'Locate.'
Button to right of 'FFmpeg Library'. If a 'Success' message indicates Audacity has nowautomatically detected the library and asks if you want to detect themmanually, click 'No', then OK to close Preferences. If the 'Locate FFmpeg' dialog appears, click 'Browse.' . Navigate to the avformat library, and select it. It may havedifferent names, such as 'avformat-52.dll' on Windows,'libavformat-52.dylib' on Mac or 'libavformat.so.52' on Linux. Click 'Open' then 'OK', and 'OK' again to close Preferences.'
FFmpeg Library Version' should now show a number. If not, you mayhave installed the wrong libraries. Click the 'Download.' Button toobtain the correct library for your operating system. You can alsochoose Help to see diagnostic information about FFmpeg detection.Why do I receive an error when I export to an FFmpeg format?If you receive a 'cannot find audio codec' error when exporting to anFFmpeg format, the FFmpeg library you are linking to does not supportthis codec.
To export to this format, you will need a build of theFFmpeg library that supports this codec.Distributable libraries will not include support for AMR WB (wideband), due to licensing issues. Exporting to AMR WB will return theerror 'FFmpeg cannot find audio codec 0x 12001'. To obtain AMR WB exportsupport, you could build FFmpeg yourself from and enable the relevant library in the configure step. How do I install VST plug-ins?Audacity supports almost all VST effect plug-ins on Windows and MacOS X.
On first use, Audacity scans automatically for VST effects thenpresents you with an to choose which effects to load. The VST effects that you checkmark will be loaded when you click OK.The list will include any real-time VST effects or VST instrument(VSTi) plug-ins that are detected but neither of these are currentlysupported and so will not load even if you enable them in the dialog.To install new VST effects, place them in the “ Plug-ins”folder inside the Audacity installation folder. On Windows, this isusually under Program Files (or Program Files (x86) on 64-bit Windows);on Mac OS X, it is usually in the 'Applications' folder. VST effectswill also be found if they are added to (or already exist in) various. To display the newly added plug-ins:. Go to the.
Under 'VST Effects', put a check mark in 'Rescan VST effects next time Audacity is started'. Restart Audacity then click OK in the 'Install VST Effects'dialog to load your new plug-ins and any other VST effects which youcheckmark. Why do some VST plug-ins not work or display incorrectly?On Windows and Mac OS X, Audacity will by default display VST effectplug-ins with a full graphical interface where the plug-in suppliesthis. Any plug-in that requires to be left open while processing audiowill not work correctly. Real-time VST effects and VST instrument (VSTi) plug-ins are not currently supported.If any plug-in displays incorrectly, you can uncheck 'Display VST effects in graphical mode' in the to display a simpler tabular interface for the plug-in (this also affects all other plug-ins). How do I install plug-ins on Linux?Individual and plug-ins can be installed by putting the plug-ins into the Audacity Plug-ins folder:. /usr/share/audacity/plug-ins if Audacity was installed from a repository package.
/usr/local/share/audacity/plug-ins if you compiled Audacity from source code.These locations are usually set as read-only, so the plug-ins willneed to be copied as root (for example, by issuing an appropriate rootcommand in the terminal, or by using the terminal to open a file managerapplication with root permissions). Note that updating the repositorypackage of Audacity may remove plug-ins that are not part of thepackage.Alternatively you can create a folder called.audacity-files in your home directory, create a sub-folder called plug-ins then put your plug-ins into that. (Note: the dot in the name.audacity-filesindicates that it is a hidden folder). This folder is then accessiblewithout root permissions and will not be modified by installing a newAudacity package.Many LADSPA plug-in packages are available in the repositories ofmost major Linux distributions. If Audacity is installed from arepository package it should automatically find plug-ins in theirinstalled location of /usr/lib/ladpsa, but Audacity compiled from sourcemay not find LADSPA plug-ins there.If necessary you can set an environment variable to indicate toAudacity where LADSPA plug-ins are installed.
For Debian-baseddistributions this can be done by entering the following code at thecommand prompt (change to your account user name):export LADSPAPATH=$LADSPAPATH:/home//.ladspa:/usr/local/lib/ladspa:/usr/lib/ladspaIf you wish this path to be set each time you boot, the LADSPAPATH environment variable may be added to /.profile or this file may be added if it does not exist. An example of how to add the LADSPAPATH environment variable:LADSPAPATH=$LADSPAPATH:/home//.ladspa:/usr/local/lib/ladspa:/usr/lib/ladspaexport LADSPAPATHFor OpenSuse 64, LADSPA plug-ins may be found in /usr/lib64/ladspa. This path can be set by adding the following line to your /etc/environment file:LADSPAPATH=/usr/lib64/ladspa.