The Four main words in parentheses above are the keywords that make up the entire pulseaudio abstraction. Audacity or another audio / streaming app.) Your mic will ideally stream audio from Alsa (Source) into the stream (Source-Input) and at the other end of the stream (Sink-Input) it will feed into its output / destination (Sink, e.g. Think of a stream as a pipe, but for sound. This app will let you configure pa streams. This is short for Pulseaudio Preferences. Since you have nowhere to post command line output, I will recommend 2 pulseaudio gui packages that will get you up and running. Once again, if you see your device model name, you're good. You're good.Īlternatively, when you run the command that I included in my comment, or the one from above look through the names of all the device.\* entries. If this command gives the name of your headphones in its output then don't worry about Google. Once you find the recommended, check that against the results of lsmod | grep Audio. It may be called an "audio card", "Device Driver", or similar. Getting the first two from your specs, and the first few results should contain something (at least close to) official from launchpad,, etc. This doesn't mean that it is the correct driver. Otherwise Pulseaudio would not be detecting it.
You can check pactl list cards to be sure, but I guarantee that your device is linked to a driver.
As I said, there are other features, i.e the ins / outs, etc., but these mostly facilitate the main duties listed above. Alsa is a driver database (among other things) whose job it is to connect your hardware with the proper "sound card" which actually refers to, again, a driver that provides access to that hardware (the physical sound card for which the alsa "sound card" is an abstraction.) It is more or less responsible for getting your hardware properly mapped into udev. I do not believe that alsa is your problem. Any hing how to progress on this? What's the respective roles of pulseaudio, pavucontrol, alsamixer? I tried this: /title/PulseAudio/… but Alsamixer interface is obscure. On my computer, the microphone sound is correctly detected in pavucontrol, but it's marked as unplugged and not present in audio parameters. As the question will disappear along with the bounty, I will include it, word for word, below, in hopes that it can be somewhat useful to users in the future. This answer is to a question provided via a separate user's bounty of this question.
0 kommentar(er)
