/[gentoo]/xml/htdocs/doc/en/alsa-guide.xml
Gentoo

Diff of /xml/htdocs/doc/en/alsa-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.37 Revision 1.41
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.37 2004/06/15 07:21:07 bennyc Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.41 2004/08/29 14:15:34 swift Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link = "/doc/en/alsa-guide.xml"> 5<guide link = "/doc/en/alsa-guide.xml">
6<title>Gentoo Linux ALSA Guide</title> 6<title>Gentoo Linux ALSA Guide</title>
7<author title="Author"> 7<author title="Author">
38Guide, this guide is supposed to give you more information on this subject. 38Guide, this guide is supposed to give you more information on this subject.
39</abstract> 39</abstract>
40 40
41<license/> 41<license/>
42 42
43<version>1.5.0</version> 43<version>1.5.4</version>
44<date>May 18, 2004</date> 44<date>August 29, 2004</date>
45 45
46<chapter> 46<chapter>
47<title>The Advanced Linux Sound Architecture</title> 47<title>The Advanced Linux Sound Architecture</title>
48<section> 48<section>
49<title>What is ALSA?</title> 49<title>What is ALSA?</title>
98</p> 98</p>
99 99
100<p> 100<p>
101Users of 2.4 kernel sources will have to install the necessary ALSA drivers for 101Users of 2.4 kernel sources will have to install the necessary ALSA drivers for
102their soundcard. First find out what soundcard you have. An easy trick is to 102their soundcard. First find out what soundcard you have. An easy trick is to
103search for "audio" in <path>/proc/pci</path>: 103search for "audio" in the output of the <c>lspci</c> command. You can install
104it with <c>emerge pciutils</c>.
104</p> 105</p>
105 106
106<pre caption="Finding out the soundcard type"> 107<pre caption="Finding out the soundcard type">
107# <i>grep -i audio /proc/pci</i> 108# <i>lspci | grep -i audio</i>
108Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio 109Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 64).
109Controller (rev 64).
110</pre> 110</pre>
111 111
112<p> 112<p>
113Now go to the <uri link="http://www.alsa-project.org/alsa-doc">ALSA Soundcard 113Now go to the <uri link="http://www.alsa-project.org/alsa-doc">ALSA Soundcard
114Matrix</uri> and search for your soundcard. In the above example you should go 114Matrix</uri> and search for your soundcard. In the above example you should go
115to the "VIA" manufacturer. You will receive a table with the known chipsets of 115to the "VIA" manufacturer. You will receive a table with the known chipsets of
116that vendor. The chipset in the above example is "via82c686"; the "Details" link 116that vendor. The chipset in the above example is "via82c686"; the "Details" link
117then informs me that the driver is called <path>via82xx</path>. 117then informs me that the driver is called <path>via82xx</path>. This is all the
118information you need, so you can safely discard the rest of that document.
118</p> 119</p>
119 120
120<p> 121<p>
121Based on this information we can now install the <c>alsa-driver</c> for our 122Based on this information we can now install the <c>alsa-driver</c> for our
122soundcard. First edit <path>/etc/make.conf</path> and <e>add</e> a new option 123soundcard. First edit <path>/etc/make.conf</path> and <e>add</e> a new option
309<path>/usr/share/sfbank</path>. For instance, the SBLive has a sound font file 310<path>/usr/share/sfbank</path>. For instance, the SBLive has a sound font file
310called <path>8MBGMSFX.SF2</path> or <path>CT4GMSFX.SF2</path>. 311called <path>8MBGMSFX.SF2</path> or <path>CT4GMSFX.SF2</path>.
311</p> 312</p>
312 313
313<p> 314<p>
314After copying over the sound font, select them using <c>sfxload</c>: 315After copying over the sound font, select them using <c>asfxload</c>:
315</p> 316</p>
316 317
317<pre caption="Loading the sound font"> 318<pre caption="Loading the sound font">
318# <i>sfxload /usr/share/sfbank/8MBGMSFX.SF2</i> 319# <i>asfxload /usr/share/sfbank/8MBGMSFX.SF2</i>
319</pre> 320</pre>
320 321
321<p> 322<p>
322You must have this command run every time you boot, so it is adviseable to add 323You must have this command run every time you boot, so it is adviseable to add
323it to <path>/etc/conf.d/local.start</path> as well. 324it to <path>/etc/conf.d/local.start</path> as well.
340synthesizer. Start by emerging this package: 341synthesizer. Start by emerging this package:
341</p> 342</p>
342 343
343<pre caption="Installing Timidity++"> 344<pre caption="Installing Timidity++">
344# <i>emerge timidity++</i> 345# <i>emerge timidity++</i>
345</pre>
346
347<p>
348A sample configuration file will be installed for you in
349<path>/usr/share/timidity/config/timidity.cfg</path>. If you don't have a
350timidity++ configuration setup yet, you can just use this one.
351</p>
352
353<pre caption="Using the default Timidity++ configuration file">
354# <i>cp /usr/share/timidity/config/timidity.cfg /usr/share/timidity</i>
355</pre> 346</pre>
356 347
357<p> 348<p>
358For timidity to play sounds, it needs a soundfont. If you do not have any, 349For timidity to play sounds, it needs a soundfont. If you do not have any,
359install <c>timidity-eawpatches</c> which will give you some soundfonts. 350install <c>timidity-eawpatches</c> which will give you some soundfonts.

Legend:
Removed from v.1.37  
changed lines
  Added in v.1.41

  ViewVC Help
Powered by ViewVC 1.1.20