Matrix:Soundcard

2014-08-27T23:22:56Z

Sellsky: /* The .asoundrc file */ Software volume control for e. g. Asus Xonar XD/XDG

<noinclude>{| align="right"
| __TOC__
|}
==Template Matrix:Soundcard==

This is the generic ALSA module template which is intended to give an overview for '''all''' sound modules.

If you want to add specific hardware information or information for a specific module, please '''DO NOT modify''' this template. Add extra information above and/or bellow to the specific Matrix:Module-* page instead. Please read the [[Matrix:Description|Universal Soundcard Description]] for more details.

</noinclude>==Introduction for {{{name|unknown}}} soundcard==

There are two ways of getting Linux drivers to work, you can either compile them into the kernel or build them separately as modules. Read the [http://www.tldp.org/ Kernel-HOWTO] for details of how to compile a kernel.

'''You must turn on the sound support soundcore module.''' This is in the kernel. Look in the sound drivers directory and it should be the first option. Most people enable the module setting. That way you can load and unload the module manually if you have multiple soundcards/devices or if you intend to debug or use cutting edge software which may cause your drivers to halt sometimes. Of course it also means you have more control of your system.

Most modern distros come with <tt>soundcore</tt> compiled as a module. You can check this in numerous ways. The easiest way is to type:

modinfo soundcore

If this command returns that you have this module, then you don't need to recompile your kernel.

==Quick installation==

This explains how to build from source tarballs. See [[GIT_Server]] for instructions on getting and using the latest source from git repositories.

Type the following commands in the shell of your choice.

Make a directory to store the alsa source code in:

cd /usr/src
mkdir alsa
cd alsa
cp /downloads/alsa-* .

Now unzip and install the <tt>alsa-driver</tt> package:

bunzip2 alsa-driver-xxx
tar -xf alsa-driver-xxx
cd alsa-driver-xxx
./configure --with-cards={{{module|unknown}}} --with-sequencer=yes ; make ; make install

Now unzip and install the <tt>alsa-lib</tt> package:

cd ..
bunzip2 alsa-lib-xxx
tar -xf alsa-lib-xxx
cd alsa-lib-xxx
./configure ; make ; make install

Now unzip and install the <tt>alsa-firmware</tt> package:

cd ..
bunzip2 alsa-firmware-xxx
tar -xf alsa-firmware-xxx
cd alsa-firmware-xxx
./configure ; make ; make install

Now unzip and install the <tt>alsa-utils</tt> package:

cd ..
bunzip2 alsa-utils-xxx
tar -xf alsa-utils-xxx
cd alsa-utils-xxx
./configure ; make ; make install

Now insert the modules into the kernel:

modprobe snd-{{{module|unknown}}} ; modprobe snd-pcm-oss ; modprobe snd-mixer-oss ; modprobe snd-seq-oss

Now adjust your soundcard's volume levels. All mixer channels are muted by default. You must use a native mixer program to unmute appropriate channels, for example <tt>alsamixer</tt> from the <tt>alsa-utils</tt> package. Note that some usb-audio devices do not have internal mixer controls. Run:

alsamixer

You can also look at the utils/alsasound file. This script is designed for the ''RedHat Linux'' distribution, but it can also be used with other distributions which use System V style rc init scripts. This will allow you to load your modules at boot time. If you don't want to do this you can of course compile them into the kernel instead and save yourself the hassle of coming to terms with the rc init scripts.

===Setting up modprobe and kmod support===

Before you send a mail complaining that "I don't have <tt>/etc/modules.conf</tt>, where do I find it ……" ‒ the <tt>/etc/conf.modules</tt> has been deprecated with a few distro's, but in your case it may still be <tt>/etc/conf.modules</tt>. Basically they are both the same, but recent version of <tt>modutils</tt> use <tt>/etc/modules.conf</tt> instead. Nothing to worry about as such, optionally please update to the latest version of <tt>modutils</tt>. This should solve your problem.

Here's the example for this card. Copy and paste this to the bottom of your <tt>/etc/modules.conf</tt> file.

{{Note|'''Debian GNU/Linux users''' need to save this information into a file in the <tt>/etc/modutils/</tt> directory (eg. <tt>/etc/modutils/alsa</tt>) and run <tt>update-modules</tt>.<br>

Note also that the kernel module '''soundcore''' has been renamed in Debian kernels >2.6.23 into '''snd'''. A workaround is to put a symlink at /lib/modules/x.x.xx/kernel/sound/soundcore.ko pointing to '''snd.ko'''}}

# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-{{{module|unknown}}}
# module options should go here

# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0

# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss

To copy and paste the above to your <tt>/etc/modules.conf</tt> file follow these [http://www.alsa-project.org/alsa-doc/doc-php/file-edit.php instructions].

==modules.conf==

This is a short explanation of what happens in the <tt>/etc/modules.conf</tt> file.

===Native devices===

After the main multiplexer is loaded, its code automatically requests the top level sound card module. String <tt>snd-card-''%i''</tt> is requested for native devices where ''%i'' is the sound card number, counted from zero (the first sound card) to seven (the eighth sound card). String <tt>sound-slot-''%i''</tt> is requested for native devices where ''%i'' is slot number for the corresponding ALSA owner (which is basically the sound card number). The options line allows you to set various configuration options before the module is loaded. String <tt>id</tt> (or <tt>snd_id</tt>) lets you set the name of the card which is then returned in the <tt>/proc/asound/cards</tt> file, i.e. to user space applications. Other options may be available depending on the specific card. Options for these cards are found in the <tt>INSTALL</tt> file or above.

username@hostname# pico /etc/modules.conf

# ALSA portion
alias snd-card-0 snd-hda-intel
alias snd-card-1 snd-cmipci
options snd-cmipci id="first" mpu_port=0x330

# OSS/Free portion
alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1

{{Note|
''For drivers older than 0.9.0rc5 use:''

<nowiki>options snd-cmipci snd_id="first" snd_mpu_port=0x330</nowiki>
|NB}}

{{Note|The "<tt>snd_</tt>" prefix has been removed from the module options to fit with the kernel standard.|NB}}

===Autoloading OSS/free emulation===

At this point we are finished with the configuration for ALSA native devices, but you may also need autoloading for the OSS/Free emulation modules, an ALSA add-on. At this time only one module does not depend on any others, thus must be loaded separately: <tt>snd-pcm1-oss</tt>. String <tt>sound-service-''%i''-''%i''</tt> is required for OSS/Free service where the first ''%i'' is the slot number/sound card number and the second ''%i'' is the service number.

username@hostname# pico /etc/modules.conf

# OSS/Free portion - card #1
alias sound-slot-0 snd-card-0
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss

# OSS/Free portion - card #2 (cmipci)
alias sound-slot-1 snd-card-1
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-12 snd-pcm-oss

The alias for <tt>snd-seq-oss</tt> is not necessary on the second device, because there is only one <tt>/dev/sequencer</tt> regardless how many devices you have.

===The .asoundrc file===

[[Asoundrc|This file]] allows you to have more advanced control over your card/device. For most setups the default, system-wide configuration is sufficient. You may change this file only for special setup. The <tt>.asoundrc</tt> file consists of definitions for the various sound devices available in your system. It also provides access to the pcm plugins in <tt>alsa-lib</tt>. These allow you to do tricky things like combine your cards into one or access multiple I/O streams on your multi-channel card.

Below is the most basic definition (only example - not required to define at all).

Make a file called <tt>.asoundrc</tt> in your home and/or root directory:

vi ~/.asoundrc

Copy and paste the following into the file, then save it:

pcm.{{{module|unkown}}} {
type hw
card 0
}

ctl.{{{module|unknown}}} {
type hw
card 0
}

====Software volume control====
If your card doesn't have hardware volume control (e. g. Asus Xonar XD/XDG), you might want to create software Master control. Edit .asoundrc as follows.

pcm.softvol {
type softvol
slave {
pcm "dmix"
}
control {
name "Master"
card 0
}
}

pcm.!default {
type plug
slave.pcm "softvol"
}

Restart alsa, then open a music player, play a file and close the player. Then check alsamixer, as you should have a Master volume control. Note that this control doesn't have a mute option.

==Links==
[[Category:Module]]
'''Generic'''

* Keep up to date with the news at [http://www.mstation.org/ M-Station]
* The most current book about Linux audio is [http://www.nostarch.com/lms.htm Linux Music and Sound] (September 2000)
* Find more applications at [http://sound.condorow.net/ Sound & MIDI Software For Linux SourceForge]
* For professional quality, low latency audio routing use [http://jackaudio.org/ JACK] ‒ the “Jack Audio Connection Kit”.

'''Specific'''
* [[Special:Whatlinkshere/Matrix:{{PAGENAME}}|Users of this module]]
* [http://www-old.alsa-project.org/alsa-doc/doc-php/template.php?module={{{module}}}#notes Old User contributed notes] at www-old.alsa-project.org (old page)<noinclude>

==Template Matrix:Soundcard – bottom notes==

If you have additional ''specific'' links, add them directly after this template to the specific Matrix:Module-* page. You can also add specific hardware notes to paragraphs below. Please read the [[Matrix:Description|Universal Soundcard Description]] for more details.

'''DO NOT modify''' this template with specific module information.
</noinclude>

AlsaProject - User contributions [en]

Matrix:Soundcard