I’ve been going round in circles for over a day now - so would really appriciate some help!
I have a module in the form of a .so file (it’s actually an Aurora module to generate sine wave sweeps: (aurora-plugins).
In /usr/share/audacity/ I make a “modules” directory.
I copy the .so file into the /usr/share/audacity/modules/ directory.
I restart audition, and see no change at all.
What else do I need to do??? My preferences menu does not include a “modules” section in which to enable the module, like some sources on the web suggest. Do all version of audacity support modules? I found somewhere that if audacity wasn’t built with a particular flag, it maybe wouldn’t support modules - does the ubuntu software centre version support modules?
I’m using Audacity 2.0.0 installed from the software center in Ubuntu 12.04 LTS.
How do I install modules in audacity 2.0.0 for Windows?
I’ve been going around in circles now for over a day so would really appriciate some help!
So far I’ve copied the module .dll file into the modules folder of the Audacity program files and restarted Audacity and the machine. Nothing changes.
What am I missing?
I’m using an Aurora module (aurora-plugins website), which I have confirmed is definately a module instead of a plug-in.
I’m using Windows Vista.
I’m using Audacity 2.0.0
I think you are getting confused between “modules” and “plug-ins”.
A “module” needs to be specifically written for Audacity and compiled from the source code at the same time as Audacity is compiled.
There are currently 3 modules available, but they are only available as source code. “Modules” are still an experimental feature.
A “Plug-in” is an add-on feature that can be loaded into Audacity on demand.
Audacity has pretty good plug-in support and there are hundreds of plug-ins readily available for Audacity.
As I am the author of the Aurora modules, I give you more infos on how thay should be installed.
Foirst of all, here we are referring to Aurora MODULES, not to Aurora plugins.
The latter are for Adobe Audition, not for Audacity, and can be downlaoded here:
aurora-plugins web site
The compete Aurora suite contains 16 plugins, which allow for making impuls respons emeasurmenets with the MLS, IRS and ESS methods, to compute acoustical parameters according to ISO3382, to compute STI according to IEC61268/16, to perform the time history analysis according to ITU-P56, and to compute inverse filters (including cross-talk cancellation filters).
Currently, just a subset of the Aurora Plugins was ported into Aurora Modules for Audacity:
AcousticalParameters
Convolver
Kirkeby
SineSweepGenerator
TimeHistoryAnalyzer
XFunctions
The STI module is currently under porting (Beta testing).
These modules can be downloaded from my web site.
Currently, the version available on my web site is the one compiled for Audacity 2.0.0. So these modules will only work if the installed version is this one: http://sourceforge.net/projects/audacity/files/audacity/2.0.0/
We did not yet recompile the Aurora modules for more recent versions of Audacity (2.0.1, 2.0.2, etc.).
For employing the Aurora modules, they must be copied inside the Modules directory of Audacity.
The default location of the directory Modules is:
on Windows: C:Program FilesAudacityModules
on OSX/MAC: /Applications/Audacity/Modules
on Ubuntu : /usr/share/audacity/modules
After copying the modules (which are .DLL files under Windows, and .SO files under OSX/Linux) in the Modules directory and restarting Audacity, the new options should appear in the menus.
For infos and support about the port of Aurora modules for Audacity, you can use the Aurora forum.
Steve, sorry, but I think that here you are misinformed, and hence you are posting misleading infos.
First of all, the Aurora web site is up and running since 9 years now.
Till now, Aurora reached more than 10000 users worldwide. Most of them are acousticians or professional audio engineers.
Second, you should not confuse Aurora PLUGINS with Aurora MODULES.
The first are XFM modules for CoolEditPro and Adobe Audition. They are shareware, and are often employed for free by students of courses related to audio, acoustics, digital sound processing, music technology, etc.
The latter are MODULES for Audacity (NOT PLUGINS!). Of course they are completely free.
Hence, the Aurora modules must be copied (after unzipping, unrarring, decompressing, etc.) insides the Modules directory of Audacity.
The default location of the directory Modules is:
on Windows: C:Program FilesAudacityModules
on OSX/MAC: /Applications/Audacity/Modules
on Ubuntu : /usr/share/audacity/modules
After copying the modules (which are .DLL files under Windows, and .SO files under OSX/Linux) in the Modules directory and restarting Audacity, the new options should appear in the menus.
Be aware that the modules are “matched” with a SPECIFIC version of Audacity. You cannot employ the modules compiled for Audacity 2.0.0 under Audacity 2.0.1, they are not going to work…
For infos and support about the port of Aurora modules for Audacity, you can use the Aurora forum.
Perhaps you could make that a bit more clear on your forum as the first thing that I read on your forum says: "You can download the new Aurora for Audacity plugins here:
Thank you for making your work freely available.
Unfortunately I had a few problems when I tried the modules with Audacity 2.0.0 on Debian Squeeze 32 bit.
The Aurora Sine Sweep Generator produced the following two tracks with the default settings:
I’m not sure if that is what it is intended to do
Aurora Acoustical Parameters cause Audacity to freeze.
Aurora Time History caused Audacity to crash.
[TimeHistoryAnalyzer] INIT
[TimeHistoryAnalyzer] PROMPT-USER
(Audacity:18584): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 17
** (Audacity:18584): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
Segmentation fault
As explained in my post, the current release of Aurora modules is compiled for Audacity 2.0.0 - they do not work properly with later versions, such as 2.0.2,
Regarding the Aurora web site I will investigate that strange behavior. The site looks perfect from my home, either with Safari, Chrome and Firefox…
What is the cost of registration? Your site doesn’t say.
Do your Audacity modules have the built-in crash “feature”?
What changed in Audacity after 2.0.0 that prevents your modules working (apart from the build date restriction, and that 2.0.2 Modules Preferences has no way to turn them on)?
There is no cost for registration. Aurora for Audacity si free, and it will always remain free. We want also to make it open-source, but we are getting problems with patents/copyright… I really hate all of this legal stuff, I think that any programmer should be able to release his code as open-source, if he wants, without being limited by those laws which were created for protecting inventors and innovators, but are actually impeding them to do what they want with their inventions…
There is no “russian roulette” in the Audacity version of Aurora. This, indeed, does not menas that the plugins never crash. They are still in beta version, so please, if they crash, report me what’s happened…
Unfortunately the management of external modules change almost every time Audacity is updated. With proper setup, we managed to run our Aurora modules under Audacity 2.0.1 without recompiling. This revealed to be impossible under Audacity 2.0.2 and later, due to removal of some functionality form the Modules interface in Audacity.
I was really hoping that, with the official release of Audacity as stable version 2.0.0, most of its feature were to remain stable and backward compatible. Unfortunately this is not happening… I undertand that almost no one else is developing external modules for Audacity. But the Aurora modules are an established asset, with more than 10000 users worldwide (most of them unregistered, indeed. Less than 1000 users did register Audacity for Audition). They are mostly acousticians, sound engineers or telecommunication engineers. It would be nice to find enough cooperation from the Audacity development team, so that we can rely on a stable set of features from the host program, which should always keep compatibility with the past. An external module compiled for 2.0.0 should work without any problem under subsequent versions…
Only at 3.0.0 it should be required to modify external modules, for becoming compatible with the new main version…
I’m not aware of significant changes to module support other than the build date restriction and the added options in preferences.
I’ve been using the Nyquist Work-Bench module (from http://audacity.homerow.net/index.php?dir=modules%2F) for several years without modification to the module, so I’m unsure what the problem is - if you could clarify, I’ll be happy to look into it.
Steve, thanks for pointing this out. It seems that we did employ by error some sort of “reserved” style name (“advert”) in our CSS style sheet.
I was not aware of “reserved names” for styles, however I am not a good HTML programmer. Several guys of my staff did modify the Aurora pages during these 10 years, so I do not even know who was responsible for defining such a crappy style name…
I have just modified it to “testorosso”.
I hope that this makes the pages fully browsable for everyone…
Regarding the incompatibility of Aurora modules with current version of Audacity, I will submit your offer of help to Simone Campanini, the researcher who is responsible of the Audacity port of Aurora.
He wil provide more technical info.
Thanks in advance!
The other link came from searching Google for “AURORA Plug-ins”. The top three hits go to the obsolete address, so it seems like a good idea to set up some sort of redirect.
