You might still have another Ubuntu-supplied package of Audacity installed. If so, try uninstalling that earlier package.
Are you running JACK, if so you have to use JACK host in Audacity, not ALSA. Are you running any other sound servers except Pulse?
Gale
I uninstalled the old version (using apt-get remove audacity), then reinstalled it, but it still went with 1.3.12. How do I force it to use the PPA?
I do have JACK installed, but it wasn’t running, and even with it running the drop-down menu for selecting the host in Audacity is still empty.
Synaptic has a way to force the version:
SynapticHowto - Community Help Wiki .
Otherwise, maybe update Ubuntu. They won’t support you if you run an obsolete distro.
Do you need to add privileges to your account to use audio:
AddUsersHowto - Community Help Wiki ?
Do you need to log in as root? Someone a few weeks ago said that was necessary in Audacity on a Linux system, but I don’t know anyone else who suggested that.
Really, I would just upgrade Ubuntu. Ubuntu intended you to be using Audacity 1.3.12 when they released 10.10 Maverick, not 2.0.2.
Gale
Logging in as root didn’t do it, so I guess I’ll just have to get around to upgrading Ubuntu. . .
Did you try quitting Audacity and resetting audacity.cfg ( Audacity Manual … tml#stored ) ?
– No.
or Transport > Rescan Audio Devices.
Default capture device number: -1
Default playback device number: -1
No devices found
it is usually better to completely uninstall it [packaged binary] before compiling your own version
– Understood. Actually the installations are on separate disks (Lucid w/ Aud 1.3 one one disk, Precise [clean install] w/ Aud 2 on another).
– BTW i am simply sticking w/ 2.0.0 for now – unless someone knows of a compelling reason to upgrade.
Ed
You should always try that, just in case.
You can check the changes for 2.0.1 and 2.0.2 (and any 2.x versions) here:
Missing features - Audacity Support .
Very few people have reported that 2.0.0 records but 2.0.1 or 2.0.2 finds no audio devices. Maybe you should try the latest Audacity version again when Ubuntu release 12.10. I assume you updated to 12.04.1 release already using Update Manager.
Gale
Did you try quitting Audacity and resetting audacity.cfg ( > Audacity Manual > … tml#stored ) ?
You should always try that, just in case.
I did, it didn’t change anything.
Ok, so I just updated to 12.04, and I’m still having the same problem. Any ideas?
And which version of Audacity, installed how?
Audacity 2.0.2. Installed from source.
When running ./configure there is section of the output (near the end of the output) that looks something like this:
Configuration summary:
Target ...................... i686-pc-linux-gnu
C++ bindings ................ no
Debug output ................ no
ALSA ........................ yes
ASIHPI ...................... no
OSS ......................... yes
JACK ........................ yes
Find that part and post what yours says.
Here’s what it says:
Configuration summary:
Target ...................... i686-pc-linux-gnu
C++ bindings ................ no
Debug output ................ no
ALSA ........................ no
ASIHPI ...................... no
OSS ......................... yes
JACK ........................ no
But I know I have ALSA, because the alsamixer does affect the sound coming from software other than Audacity.
Update: With JACK running, I get this:
Configuration summary:
Target ...................... i686-pc-linux-gnu
C++ bindings ................ no
Debug output ................ no
ALSA ........................ no
ASIHPI ...................... no
OSS ......................... yes
JACK ........................ no
I thought that might be the problem. If Audacity is compiled without ALSA support then you won’t be able to use ALSA or Jack.
You are probably missing libasound2-dev
On Debian based distributions, the easiest way to install all dependencies for Audacity is:
sudo apt-get build-dep audacity
(“restricted” multi-media repositories must be enabled)
That did it! Thanks!
One other thing: Can I suggest that you make the compile fail if libasound2-dev isn’t installed?
What about people that use OSS and don’t have ALSA?
Maybe you could check to see if either of those was present. Basically just make it such that once compiled, something will work.
Well really “sudo apt-get build-dep audacity” (which is recommended for Debian based systems) sorts that out by resolving all necessary dependencies.