New answers tagged

2

Although the solution below is not a fix to what seems to be a minor bug, you can use it as a workaround to automatically blacklist devices on startup (log in). The solution ...is a small script that remembers your blacklisted items on log in. It runs with two arguments: get and set. The first is to read the current blacklisted items, the second will (re-) ...


0

The issue was solved by forcing a restart after the computer had frozen. Still not sure whether it's a hardware or software issue or a combination of the two.


0

Try checking out Ubuntu's own sound card issues page, it has helped me a few times in the past and gives you simple instructions on testing and re-enabling sound cards: https://help.ubuntu.com/community/SoundTroubleshooting


0

First and foremost check the Mic by recording and running the following command in a terminal window: Make sure the device is not set to Mute, then type arecord test.wav and speaking into your microphone. To stop this command press Ctrl+C. This will test basic recording functionality by creating test.wav in your HOME directory. Open this file to ...


3

Most modern sound adapters have output monitoring channels. Unity/Gnome default sound settings tool (part of unity-/gnome-control-center) does not list them on input tab. Install PulseAudio volume control tool (part of upstream project) sudo apt-get install pavucontrol Run it and go to Input Devices tab. Look down to the right corner, Show: drop list, ...


2

This wiki page covers how to create a dummy audio input using PulseAudio, which can then be recording using Audacity. It uses the PulseAudio Volume Controller (which is available in the default repos, sudo apt-get install pavucontrol), and creates an application stream which Audacity will read as input. It is much better explained on the above wiki page.



Top 50 recent answers are included