/[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.79 Revision 1.80
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.79 2007/05/07 07:08:24 nightmorph Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.80 2007/05/19 03:00:29 nightmorph Exp $ -->
3 3
4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5 5
6<guide link="/doc/en/alsa-guide.xml"> 6<guide link="/doc/en/alsa-guide.xml">
7<title>Gentoo Linux ALSA Guide</title> 7<title>Gentoo Linux ALSA Guide</title>
32<section> 32<section>
33<title>What is ALSA?</title> 33<title>What is ALSA?</title>
34<body> 34<body>
35 35
36<p> 36<p>
37ALSA, which stands for <e>Advanced Linux Sound Architecture</e>, provides 37ALSA, which stands for <e>Advanced Linux Sound Architecture</e>, provides
38audio and MIDI (<e>Musical Instrument Digital Interface</e>) functionality to 38audio and MIDI (<e>Musical Instrument Digital Interface</e>) functionality to
39the Linux operating system. ALSA is the default sound subsystem in the 2.6 39the Linux operating system. ALSA is the default sound subsystem in the 2.6
40kernel thereby replacing OSS (<e>Open Sound System</e>), which was used in the 40kernel thereby replacing OSS (<e>Open Sound System</e>), which was used in the
412.4 kernels. 412.4 kernels.
42</p> 42</p>
43 43
44<p> 44<p>
45ALSA's main features include efficient support for all types of audio 45ALSA's main features include efficient support for all types of audio
46interfaces ranging from consumer sound cards to professional sound 46interfaces ranging from consumer sound cards to professional sound
47equipment, fully modularized drivers, SMP and thread safety, backward 47equipment, fully modularized drivers, SMP and thread safety, backward
48compatibility with OSS and a user-space library <c>alsa-lib</c> to make 48compatibility with OSS and a user-space library <c>alsa-lib</c> to make
49application development a breeze. 49application development a breeze.
50</p> 50</p>
51 51
52</body> 52</body>
53</section> 53</section>
54<section> 54<section>
55<title>ALSA on Gentoo</title> 55<title>ALSA on Gentoo</title>
56<body> 56<body>
57 57
58<p> 58<p>
59One of Gentoo's main strengths lies in giving the user maximum control over 59One of Gentoo's main strengths lies in giving the user maximum control over
60how a system is installed/configured. ALSA on Gentoo follows the same 60how a system is installed/configured. ALSA on Gentoo follows the same
61principle. There are two ways you can get ALSA support up and running on your 61principle. There are two ways you can get ALSA support up and running on your
62system. We shall look at them in detail in the next chapter. 62system. We shall look at them in detail in the next chapter.
63</p> 63</p>
64 64
65</body> 65</body>
66</section> 66</section>
71<section> 71<section>
72<title>Options</title> 72<title>Options</title>
73<body> 73<body>
74 74
75<warn> 75<warn>
76The methods shown below are mutually exclusive. You cannot have ALSA compiled 76The methods shown below are mutually exclusive. You cannot have ALSA compiled
77in your kernel and use <c>media-sound/alsa-driver</c>. It <e>will</e> fail. 77in your kernel and use <c>media-sound/alsa-driver</c>. It <e>will</e> fail.
78</warn> 78</warn>
79 79
80<p> 80<p>
81The two options are: 81The two options are:
97if one doesn't work for you, try the other! We shall take a peek into both 97if one doesn't work for you, try the other! We shall take a peek into both
98before finally deciding on one. 98before finally deciding on one.
99</p> 99</p>
100 100
101<p> 101<p>
102If you were to use ALSA provided by the kernel, the following are the pros and 102If you were to use ALSA provided by the kernel, the following are the pros and
103cons: 103cons:
104</p> 104</p>
105 105
106<table> 106<table>
107<tr> 107<tr>
172<section id="lspci"> 172<section id="lspci">
173<title>Before you proceed</title> 173<title>Before you proceed</title>
174<body> 174<body>
175 175
176<p> 176<p>
177Whichever method of install you choose, you need to know what drivers your 177Whichever method of install you choose, you need to know what drivers your
178sound card uses. In most cases, sound cards (onboard and otherwise) are PCI 178sound card uses. In most cases, sound cards (onboard and otherwise) are PCI
179based and <c>lspci</c> will help you in digging out the required information. 179based and <c>lspci</c> will help you in digging out the required information.
180Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if you don't have it 180Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if you don't have it
181installed already. In case you have a USB sound card, <c>lsusb</c> from 181installed already. In case you have a USB sound card, <c>lsusb</c> from
182<c>sys-apps/usbutils</c> <e>might</e> be of help. For ISA cards, try using 182<c>sys-apps/usbutils</c> <e>might</e> be of help. For ISA cards, try using
183<c>sys-apps/isapnptools</c>. Also, the following pages <e>may</e> help users 183<c>sys-apps/isapnptools</c>. Also, the following pages <e>may</e> help users
184with ISA based sound cards. 184with ISA based sound cards:
185</p> 185</p>
186 186
187<ul> 187<ul>
188 <li> 188 <li>
189 <uri link="http://www.roestock.demon.co.uk/isapnptools/">The ISAPNPTOOLS 189 <uri link="http://www.roestock.demon.co.uk/isapnptools/">The ISAPNPTOOLS
215 215
216<p> 216<p>
217We now know that the sound card on the machine is a Sound Blaster Live! and the 217We now know that the sound card on the machine is a Sound Blaster Live! and the
218card manufacturer is Creative Labs. Head over to the <uri 218card manufacturer is Creative Labs. Head over to the <uri
219link="http://bugtrack.alsa-project.org/main/index.php/Matrix:Main">ALSA 219link="http://bugtrack.alsa-project.org/main/index.php/Matrix:Main">ALSA
220Soundcard Matrix</uri> page and select Creative Labs from the drop down menu. 220Soundcard Matrix</uri> page and select Creative Labs from the list. You will
221You will be taken to the Creative Labs matrix page where you can see that the SB 221be taken to the Creative Labs matrix page where you can see that the SB Live!
222Live! uses the <c>emu10k1</c> module. That is the information we need for now. 222uses the <c>emu10k1</c> module. That is the information we need for now. If
223If you are interested in detailed information, you can click on the link next to 223you are interested in detailed information, you can click on the link next to
224the "Details" and that will take you to the <c>emu10k1</c> specific page. 224the "Details" and that will take you to the <c>emu10k1</c> specific page.
225</p> 225</p>
226 226
227<p> 227<p>
228If you intend to use MIDI, then you should add <c>midi</c> to your USE flags in 228If you intend to use MIDI, then you should add <c>midi</c> to your USE flags in
270Now we will look at some of the options we will have to enable in the 2.6 270Now we will look at some of the options we will have to enable in the 2.6
271kernel to ensure proper ALSA support for our sound card. 271kernel to ensure proper ALSA support for our sound card.
272</p> 272</p>
273 273
274<p> 274<p>
275Please note that for ease of use, all examples show ALSA built as modules. It 275Please note that for ease of use, all examples show ALSA built as modules. It
276is advisable to follow the same as it then allows the use of <c>alsaconf</c> 276is advisable to follow the same as it then allows the use of <c>alsaconf</c>
277which is a boon when you want to configure your card. Please do <e>not</e> skip 277which is a boon when you want to configure your card. Please do <e>not</e> skip
278the <uri link="#alsa-config">Configuration</uri> section of this document. If 278the <uri link="#alsa-config">Configuration</uri> section of this document. If
279you still like to have options built-in, ensure that you make changes to your 279you still like to have options built-in, ensure that you make changes to your
280config accordingly. 280config accordingly.
299 <comment>(Old style /dev/mixer* and /dev/dsp* support. Recommended.)</comment> 299 <comment>(Old style /dev/mixer* and /dev/dsp* support. Recommended.)</comment>
300 &lt;M&gt; OSS Mixer API 300 &lt;M&gt; OSS Mixer API
301 &lt;M&gt; OSS PCM (digital audio) API 301 &lt;M&gt; OSS PCM (digital audio) API
302 302
303<comment>(You now have a choice of devices to enable support for. Generally, 303<comment>(You now have a choice of devices to enable support for. Generally,
304you will have one type of device and not more. If you have more than one 304you will have one type of device and not more. If you have more than one
305sound card, please enable them all here.)</comment> 305sound card, please enable them all here.)</comment>
306 306
307<comment>(Mostly for testing and development purposes, not needed for normal 307<comment>(Mostly for testing and development purposes, not needed for normal
308users unless you know what you are doing.)</comment> 308users unless you know what you are doing.)</comment>
309Generic devices ---&gt; 309Generic devices ---&gt;
310 310
311<comment>(For ISA Sound cards)</comment> 311<comment>(For ISA Sound cards)</comment>
312ISA devices ---&gt; 312ISA devices ---&gt;
313<comment>(IF you had the Gravis, you would select this option)</comment> 313<comment>(IF you had the Gravis, you would select this option)</comment>
314 &lt;M&gt; Gravis UltraSound Extreme 314 &lt;M&gt; Gravis UltraSound Extreme
315 315
316<comment>(Move one level back and into PCI devices. Most sound cards today are 316<comment>(Move one level back and into PCI devices. Most sound cards today are
317PCI devices)</comment> 317PCI devices)</comment>
318PCI devices ---&gt; 318PCI devices ---&gt;
319 <comment>(We now select the emu10k1 driver for our card)</comment> 319 <comment>(We now select the emu10k1 driver for our card)</comment>
320 &lt;M&gt; Emu10k1 (SB Live!, Audigy, E-mu APS) 320 &lt;M&gt; Emu10k1 (SB Live!, Audigy, E-mu APS)
321 <comment>(Or an Intel card would be)</comment> 321 <comment>(Or an Intel card would be)</comment>
329 329
330<p> 330<p>
331Now that your options are set, you can (re)compile the kernel and ALSA support 331Now that your options are set, you can (re)compile the kernel and ALSA support
332for your card should be functional once you reboot into the new kernel. Don't 332for your card should be functional once you reboot into the new kernel. Don't
333forget to update your GRUB configuration to use the newly built kernel. 333forget to update your GRUB configuration to use the newly built kernel.
334You can now proceed to <uri link="#alsa-utilities">ALSA Utilities</uri> and 334You can now proceed to <uri link="#alsa-utilities">ALSA Utilities</uri> and
335see if everything is working as it should. 335see if everything is working as it should.
336</p> 336</p>
337 337
338</body> 338</body>
339</section> 339</section>
340<section id="alsa-driver"> 340<section id="alsa-driver">
341<title>Using the ALSA Driver package</title> 341<title>Using the ALSA Driver package</title>
342<body> 342<body>
343 343
344<p> 344<p>
345So you've decided to go the <c>alsa-driver</c> way. Let's get started then. 345So you've decided to go the <c>alsa-driver</c> way. Let's get started then.
346There are a few minor things to be done to ensure only the drivers for your 346There are a few minor things to be done to ensure only the drivers for your
347sound card are compiled. Although this is not really necessary, it cuts down 347sound card are compiled. Although this is not really necessary, it cuts down
348on the unnecessary drivers that will be compiled otherwise. 348on the unnecessary drivers that will be compiled otherwise.
349</p> 349</p>
350 350
351<p> 351<p>
352If you don't have an idea of what drivers your sound card might need, please 352If you don't have an idea of what drivers your sound card might need, please
353take a look at the <uri link="#lspci">lspci</uri> section of this guide. Once 353take a look at the <uri link="#lspci">lspci</uri> section of this guide. Once
354you have your driver name (<c>emu10k1</c> in our example), edit 354you have your driver name (<c>emu10k1</c> in our example), edit
355<path>/etc/make.conf</path> and add a variable, <c>ALSA_CARDS</c>. 355<path>/etc/make.conf</path> and add a variable, <c>ALSA_CARDS</c>.
356</p> 356</p>
357 357
358<pre caption="Adding ALSA_CARDS to make.conf"> 358<pre caption="Adding ALSA_CARDS to make.conf">
359<comment>(For one sound card)</comment> 359<comment>(For one sound card)</comment>
361<comment>(For more than one, separate names with spaces)</comment> 361<comment>(For more than one, separate names with spaces)</comment>
362ALSA_CARDS="emu10k1 via82xx" 362ALSA_CARDS="emu10k1 via82xx"
363</pre> 363</pre>
364 364
365<p> 365<p>
366If you have compiled your kernel and want to use <c>alsa-driver</c>, please 366If you have compiled your kernel and want to use <c>alsa-driver</c>, please
367ensure the following before proceeding, else <c>alsa-driver</c> is likely to 367ensure the following before proceeding, else <c>alsa-driver</c> is likely to
368fail. The next code listing gives you one way of performing the checks. 368fail. The next code listing gives you one way of performing the checks.
369</p> 369</p>
370 370
371<note> 371<note>
372<c>genkernel</c> users can proceed with <uri link="#doc_chap2_pre6">Installing 372<c>genkernel</c> users can proceed with <uri link="#doc_chap2_pre6">Installing
429<section id="alsa-utilities"> 429<section id="alsa-utilities">
430<title>ALSA Utilities</title> 430<title>ALSA Utilities</title>
431<body> 431<body>
432 432
433<p> 433<p>
434<c>alsa-utils</c> forms an integral part of ALSA as it has a truckload of 434<c>alsa-utils</c> forms an integral part of ALSA as it has a truckload of
435programs that are highly useful, including the ALSA Initscripts. Hence we 435programs that are highly useful, including the ALSA Initscripts. Hence we
436strongly recommend that you install <c>alsa-utils</c> 436strongly recommend that you install <c>alsa-utils</c>
437</p> 437</p>
438 438
439<pre caption="Install alsa-utils"> 439<pre caption="Install alsa-utils">
440# <i>emerge alsa-utils</i> 440# <i>emerge alsa-utils</i>
441</pre> 441</pre>
442 442
443<note> 443<note>
444If you activated ALSA in your <uri link="#kernel">kernel</uri> <e>and</e> did 444If you activated ALSA in your <uri link="#kernel">kernel</uri> <e>and</e> did
445not compile ALSA as modules, please proceed to the 445not compile ALSA as modules, please proceed to the
446<uri link="#initscript">ALSA Initscript</uri> section. The rest of you need 446<uri link="#initscript">ALSA Initscript</uri> section. The rest of you need
447to configure ALSA. This is made very easy by the existence of the 447to configure ALSA. This is made very easy by the existence of the
448<c>alsaconf</c> tool provided by <c>alsa-utils</c>. 448<c>alsaconf</c> tool provided by <c>alsa-utils</c>.
449</note> 449</note>
450 450
451</body> 451</body>
452</section> 452</section>
460just letting your kernel automatically setup your sound card for you. Otherwise, 460just letting your kernel automatically setup your sound card for you. Otherwise,
461use <c>alsaconf</c> to configure your card, as shown below. 461use <c>alsaconf</c> to configure your card, as shown below.
462</p> 462</p>
463 463
464<note> 464<note>
465Please shut down any programs that <e>might</e> access the sound card while 465Please shut down any programs that <e>might</e> access the sound card while
466running <c>alsaconf</c>. 466running <c>alsaconf</c>.
467</note> 467</note>
468 468
469<p> 469<p>
470Another way to configure your sound card is to run <c>alsaconf</c>. Just type 470To configure your sound card just type <c>alsaconf</c> in a shell as root.
471<c>alsaconf</c> in a shell as root.
472</p> 471</p>
473 472
474<pre caption="Invoking alsaconf"> 473<pre caption="Invoking alsaconf">
475# <i>alsaconf</i> 474# <i>alsaconf</i>
476</pre> 475</pre>
477 476
478<p> 477<p>
479You will now see a neat menu guided interface that will automatically probe 478You will now see a neat menu guided interface that will automatically probe
480your devices and try to find out your sound card. You will be asked to pick 479your devices and try to find out your sound card. You will be asked to pick
481your sound card from a list. Once that's done, it will ask you permission to 480your sound card from a list. Once that's done, it will ask you permission to
482automatically make required changes to <path>/etc/modules.d/alsa</path>. 481automatically make required changes to <path>/etc/modules.d/alsa</path>.
483It will then adjust your volume settings to optimum levels, run 482It will then adjust your volume settings to optimum levels, run
484<c>update-modules</c> and start the <path>/etc/init.d/alsasound</path> service. 483<c>update-modules</c> and start the <path>/etc/init.d/alsasound</path> service.
485Once <c>alsaconf</c> exits, you can proceed with setting up the ALSA 484Once <c>alsaconf</c> exits, you can proceed with setting up the ALSA
486initscript. 485initscript.
487</p> 486</p>
491<section id="initscript"> 490<section id="initscript">
492<title>ALSA Initscript</title> 491<title>ALSA Initscript</title>
493<body> 492<body>
494 493
495<p> 494<p>
496We're now almost all setup. Whichever method you chose to install ALSA, you'll 495We're now almost all setup. Whichever method you chose to install ALSA, you'll
497need to have something load your modules or initialize ALSA and restore your 496need to have something load your modules or initialize ALSA and restore your
498volume settings when your system comes up. The ALSA Initscript handles all of 497volume settings when your system comes up. The ALSA Initscript handles all of
499this for you and is called <c>alsasound</c>. Add it to the boot runlevel. 498this for you and is called <c>alsasound</c>. Add it to the boot runlevel.
500</p> 499</p>
501 500
502<pre caption="Adding ALSA to the boot runlevel"> 501<pre caption="Adding ALSA to the boot runlevel">
503# <i>rc-update add alsasound boot</i> 502# <i>rc-update add alsasound boot</i>
504 * alsasound added to runlevel boot 503 * alsasound added to runlevel boot
505 * rc-update complete. 504 * rc-update complete.
506</pre> 505</pre>
507 506
508<p> 507<p>
509Next, just check the <path>/etc/conf.d/alsasound</path> file and ensure that 508Next, just check the <path>/etc/conf.d/alsasound</path> file and ensure that
510SAVE_ON_STOP variable is set to yes. This saves your sound settings when you 509SAVE_ON_STOP variable is set to yes. This saves your sound settings when you
511shutdown your system. 510shutdown your system.
512</p> 511</p>
513 512
514</body> 513</body>
515</section> 514</section>
539<section> 538<section>
540<title>Volume Check!</title> 539<title>Volume Check!</title>
541<body> 540<body>
542 541
543<p> 542<p>
544We've completed all the setups and prerequisites, so let's fire up ALSA. If 543We've completed all the setups and prerequisites, so let's fire up ALSA. If
545you ran <c>alsaconf</c>, you can skip this step, since <c>alsaconf</c> already 544you ran <c>alsaconf</c>, you can skip this step, since <c>alsaconf</c> already
546does this for you. 545does this for you.
547</p> 546</p>
548 547
549<pre caption="Start the service"> 548<pre caption="Start the service">
550# <i>/etc/init.d/alsasound start</i> 549# <i>/etc/init.d/alsasound start</i>
551</pre> 550</pre>
552 551
553<p> 552<p>
554Now that the required things have been taken care of, we need to check up on 553Now that the required things have been taken care of, we need to check up on
555the volume as in certain cases, it is muted. We use <c>alsamixer</c> for this 554the volume as in certain cases, it is muted. We use <c>alsamixer</c> for this
556purpose. 555purpose.
557</p> 556</p>
558 557
559<pre caption="Starting alsamixer"> 558<pre caption="Starting alsamixer">
568udevd; udevstart</c> to reload <path>/dev</path> entries and fire up 567udevd; udevstart</c> to reload <path>/dev</path> entries and fire up
569<c>alsamixer</c>. It should solve the issue. 568<c>alsamixer</c>. It should solve the issue.
570</impo> 569</impo>
571 570
572<p> 571<p>
573This is how the ALSA Mixer <e>might</e> look the first time you open it. Pay 572This is how the ALSA Mixer <e>might</e> look the first time you open it. Pay
574attention to the Master and PCM channels which both have an MM below them. 573attention to the Master and PCM channels which both have an MM below them.
575That means they are muted. If you try to play anything with <c>alsamixer</c> 574That means they are muted. If you try to play anything with <c>alsamixer</c>
576in this state, you will not hear anything on your speakers. 575in this state, you will not hear anything on your speakers.
577</p> 576</p>
578 577
579<figure link="/images/docs/alsa-mixermuted.png" short="AlsaMixer Muted" caption="The Alsa Mixer Main Window, Muted"/> 578<figure link="/images/docs/alsa-mixermuted.png" short="AlsaMixer Muted" caption="The Alsa Mixer Main Window, Muted"/>
580 579
587if you want to hear some output on your speakers. 586if you want to hear some output on your speakers.
588</warn> 587</warn>
589 588
590<ul> 589<ul>
591 <li> 590 <li>
592 To move between channels, use your left and right arrow keys. (&lt;- 591 To move between channels, use your left and right arrow keys. (&lt;-
593 &amp; -&gt;) 592 &amp; -&gt;)
594 </li> 593 </li>
595 <li> 594 <li>
596 To toggle mute, move to the specific channel, for example Master and press 595 To toggle mute, move to the specific channel, for example Master and press
597 the <e>m</e> key on the keyboard. 596 the <e>m</e> key on the keyboard.
598 </li> 597 </li>
599 <li> 598 <li>
600 To increase and decrease the volume levels, use the up and down arrow keys 599 To increase and decrease the volume levels, use the up and down arrow keys
601 respectively. 600 respectively.
602 </li> 601 </li>
603</ul> 602</ul>
604 603
605<note> 604<note>
606Be careful when setting your Bass and Treble values. 50 is usually a good 605Be careful when setting your Bass and Treble values. 50 is usually a good
607number for both. Extremely high values of Bass may cause <e>jarring</e> 606number for both. Extremely high values of Bass may cause <e>jarring</e>
608on speakers that are not designed to handle them. 607on speakers that are not designed to handle them.
609</note> 608</note>
610 609
611<p> 610<p>
612After you're all done, your ALSA Mixer should look similar to the one below. 611After you're all done, your ALSA Mixer should look similar to the one below.
613Note the 00 instead of the MM and also the volume levels for some optimum 612Note the 00 instead of the MM and also the volume levels for some optimum
614settings. 613settings.
615</p> 614</p>
616 615
617<figure link="/images/docs/alsa-mixerunmuted.png" short="AlsaMixer Unmuted" caption="Alsa Mixer ready to roll"/> 616<figure link="/images/docs/alsa-mixerunmuted.png" short="AlsaMixer Unmuted" caption="Alsa Mixer ready to roll"/>
618 617
684<section> 683<section>
685<title>Issues?</title> 684<title>Issues?</title>
686<body> 685<body>
687 686
688<p> 687<p>
689If for some reason you're unable to hear sound, the first thing to do would 688If for some reason you're unable to hear sound, the first thing to do would
690be to check your <uri link="#doc_chap3_pre6">alsamixer</uri> settings. 80% of 689be to check your <uri link="#doc_chap3_pre6">alsamixer</uri> settings. 80% of
691the issues lie with muted channels or low volume. Also check your Window 690the issues lie with muted channels or low volume. Also check your Window
692Manager's sound applet and verify that volumes are set to audible levels. 691Manager's sound applet and verify that volumes are set to audible levels.
693</p> 692</p>
694 693
695<p> 694<p>
696<path>/proc</path> is your friend. And in this case, <path>/proc/asound</path> 695<path>/proc</path> is your friend. And in this case, <path>/proc/asound</path>
697is your best friend. We shall just take a short look at how much info is made 696is your best friend. We shall just take a short look at how much info is made
698available to us there. 697available to us there.
699</p> 698</p>
700 699
701<pre caption="Fun with /proc/asound"> 700<pre caption="Fun with /proc/asound">
702<comment>(First and foremost, if /proc/asound/cards shows your card, ALSA has 701<comment>(First and foremost, if /proc/asound/cards shows your card, ALSA has
703picked up your sound card fine.)</comment> 702picked up your sound card fine.)</comment>
704# <i>cat /proc/asound/cards</i> 703# <i>cat /proc/asound/cards</i>
7050 [Live ]: EMU10K1 - Sound Blaster Live! 7040 [Live ]: EMU10K1 - Sound Blaster Live!
706 Sound Blaster Live! (rev.6, serial:0x80271102) at 0xb800, irq 11 705 Sound Blaster Live! (rev.6, serial:0x80271102) at 0xb800, irq 11
707 706
842also need to re-emerge any ALSA packages that use the <c>midi</c> flag, such as 841also need to re-emerge any ALSA packages that use the <c>midi</c> flag, such as
843<c>alsa-lib</c>, <c>alsa-utils</c>, and <c>alsa-driver</c>. 842<c>alsa-lib</c>, <c>alsa-utils</c>, and <c>alsa-driver</c>.
844</p> 843</p>
845 844
846<p> 845<p>
847If your sound card is one of those that come with on-board MIDI synthesizers 846If your sound card is one of those that come with on-board MIDI synthesizers
848and you would like to listen to some .mid files, you have to install 847and you would like to listen to some .mid files, you have to install
849<c>awesfx</c> which is basically a set of utilities for controlling the AWE32 848<c>awesfx</c> which is basically a set of utilities for controlling the AWE32
850driver. We need to install it first. If you don't have a hardware synthesizer, 849driver. We need to install it first. If you don't have a hardware synthesizer,
851you can use a virtual one. Please see the section on 850you can use a virtual one. Please see the section on
852<uri link="#vsynth">Virtual Synthesizers</uri> for more information. 851<uri link="#vsynth">Virtual Synthesizers</uri> for more information.
853</p> 852</p>
854 853
855<pre caption="Installing awesfx"> 854<pre caption="Installing awesfx">
856# <i>emerge awesfx</i> 855# <i>emerge awesfx</i>
857</pre> 856</pre>
858 857
859<note> 858<note>
860You will need to copy over SoundFont (SF2) files from your sound card's driver 859You will need to copy over SoundFont (SF2) files from your sound card's driver
861CD or a Windows installation into <path>/usr/share/sounds/sf2/</path>. For 860CD or a Windows installation into <path>/usr/share/sounds/sf2/</path>. For
862example a sound font file for the Creative SBLive! card would be 8MBGMSFX.SF2. 861example a sound font file for the Creative SBLive! card would be 8MBGMSFX.SF2.
863</note> 862</note>
864 863
865<p> 864<p>
866After copying over the Soundfont files, we can then play a midi file as shown. 865After copying over the Soundfont files, we can then play a midi file as shown.
867You can also add the <c>asfxload</c> command to 866You can also add the <c>asfxload</c> command to
868<path>/etc/conf.d/local.start</path>, so that the sound font is loaded 867<path>/etc/conf.d/local.start</path>, so that the sound font is loaded
869every time the system starts up. 868every time the system starts up.
870</p> 869</p>
871 870
872<note> 871<note>
873<path>/mnt</path> paths mentioned in the code listing(s) below will <e>not</e> 872<path>/mnt</path> paths mentioned in the code listing(s) below will <e>not</e>
874be the same in your machine. They are just an example. Please be careful to 873be the same in your machine. They are just an example. Please be careful to
875change the path to suit your machine. 874change the path to suit your machine.
876</note> 875</note>
877 876
878<pre caption="Loading Soundfonts"> 877<pre caption="Loading Soundfonts">
879<comment>(First, copy the Soundfont)</comment> 878<comment>(First, copy the Soundfont)</comment>
883<comment>(We load the specific Soundfont)</comment> 882<comment>(We load the specific Soundfont)</comment>
884# <i>asfxload /usr/share/sounds/sf2/8MBGMSFX.SF2</i> 883# <i>asfxload /usr/share/sounds/sf2/8MBGMSFX.SF2</i>
885</pre> 884</pre>
886 885
887<p> 886<p>
888You can now play midi files using a program like <c>aplaymidi</c>. Run 887You can now play midi files using a program like <c>aplaymidi</c>. Run
889<c>aplaymidi -l</c> to get a list of available ports and then pick one 888<c>aplaymidi -l</c> to get a list of available ports and then pick one
890to play the file on. 889to play the file on.
891</p> 890</p>
892 891
893<pre caption="Playing MIDI"> 892<pre caption="Playing MIDI">
894<comment>(Check open ports)</comment> 893<comment>(Check open ports)</comment>
921<p> 920<p>
922For timidity to play sounds, it needs a sound font. Fortunately, the ebuild will 921For timidity to play sounds, it needs a sound font. Fortunately, the ebuild will
923install some sound font packages for you. There are a few other font packages 922install some sound font packages for you. There are a few other font packages
924available in Portage, such as <c>timidity-freepats</c> and 923available in Portage, such as <c>timidity-freepats</c> and
925<c>timidity-eawpatches</c>. You can have multiple sound font configurations 924<c>timidity-eawpatches</c>. You can have multiple sound font configurations
926installed, and you can place your own in <path>/usr/share/timidity/</path>. To 925installed, and you can place your own in <path>/usr/share/timidity/</path>. To
927switch between different timidity configurations, you should use 926switch between different timidity configurations, you should use
928<c>eselect</c>. 927<c>eselect</c>.
929</p> 928</p>
930 929
931<pre caption="Changing configurations"> 930<pre caption="Changing configurations">
969<body> 968<body>
970 969
971<p> 970<p>
972You can have more than one sound card in your system simultaneously, provided 971You can have more than one sound card in your system simultaneously, provided
973that you have built ALSA as modules in your kernel (or have installed 972that you have built ALSA as modules in your kernel (or have installed
974<c>alsa-driver</c> instead). You just need to specify which should be started 973<c>alsa-driver</c> instead). You just need to specify which should be started
975first in <path>/etc/modules.d/alsa</path>. Your cards are identified by their 974first in <path>/etc/modules.d/alsa</path>. Your cards are identified by their
976driver names inside this file. 0 is the first card, 1 is the second, and so on. 975driver names inside this file. 0 is the first card, 1 is the second, and so on.
977Here's an example for a system with two sound cards. 976Here's an example for a system with two sound cards.
978</p> 977</p>
979 978
1018<title>A big thank you to...</title> 1017<title>A big thank you to...</title>
1019<body> 1018<body>
1020 1019
1021<p> 1020<p>
1022Everyone who contributed to the earlier version of the Gentoo ALSA Guide: 1021Everyone who contributed to the earlier version of the Gentoo ALSA Guide:
1023Vincent Verleye, Grant Goodyear, Arcady Genkin, Jeremy Huddleston, 1022Vincent Verleye, Grant Goodyear, Arcady Genkin, Jeremy Huddleston,
1024John P. Davis, Sven Vermeulen, Benny Chuang, Tiemo Kieft and Erwin. 1023John P. Davis, Sven Vermeulen, Benny Chuang, Tiemo Kieft and Erwin.
1025</p> 1024</p>
1026 1025
1027</body> 1026</body>
1028</section> 1027</section>

Legend:
Removed from v.1.79  
changed lines
  Added in v.1.80

  ViewVC Help
Powered by ViewVC 1.1.20