Asoundrc - Revision history

Oneirn: /* Referenced applications */ it has been over 5 years

2012-07-06T03:47:47Z

‎Referenced applications: it has been over 5 years

Lorenzopolidori: /* The .asoundrc file */

2012-05-01T09:01:13Z

‎The .asoundrc file

JeanGoulet: /* Bindings explained */

2011-07-28T15:16:36Z

‎Bindings explained

JeanGoulet: /* Bindings explained */

2011-07-28T15:12:42Z

‎Bindings explained

JeanGoulet: /* Bindings explained */

2011-07-28T15:07:41Z

‎Bindings explained

JeanGoulet: /* Bindings explained */

2011-07-28T15:03:39Z

‎Bindings explained

JeanGoulet: /* Bindings explained */

2011-07-28T14:56:59Z

‎Bindings explained

JeanGoulet: /* Virtual multi channel devices */

2011-07-28T14:00:42Z

‎Virtual multi channel devices

JeanGoulet: /* The Control device */

2011-07-28T13:58:12Z

‎The Control device

Perex at 07:24, 16 June 2011

2011-06-16T07:24:15Z

@@ Line 539: / Line 539: @@
 ==Referenced applications==
-*  '''aRTsd''' - the aRTs sound server is the basis of desktop sound for KDE.
+*  '''aRTsd''' - the aRTs sound server was the basis of desktop sound for KDE 3.
 *  '''ESD''' - the Enlightened Sound Daemon mixes several audio streams for playback by a single audio device.
 *  '''Ecasound''' - a commandline multitrack recorder and editor with various GUI apps.

@@ Line 10: / Line 10: @@
 ==The .asoundrc file==
-This file allows the you to have more advanced control over your card/device. The <code>.asoundrc</code> file consists of definitions of the various cards available in your system. It also gives you access to the pcm plugins in alsa-lib. These allow you to do tricky things like combine your cards into one or access multiple I/Os on your mulitchannel card.
+This file allows you to have more advanced control over your card/device. The <code>.asoundrc</code> file consists of definitions of the various cards available in your system. It also gives you access to the pcm plugins in alsa-lib. These allow you to do tricky things like combine your cards into one or access multiple I/Os on your mulitchannel card.
 ==Where does asoundrc live?==

@@ Line 389: / Line 389: @@
 The above example for a virtual multi channel device uses bindings to make the connections work. The following is a more advanced asoundrc for 2 RME Hammerfalls which is a professional multichannel sound device. Below is a full explanation of how bindings work.
   # This is for two RME Hammerfall cards. They have been conceptually split into rows
@@ Line 436: / Line 435: @@
   	slaves.b.channels 26;
-	# Use rme9652_0 ch 0-7 mapped to ALSA ch 0-7
+ 	# Use rme9652_0 ch 0-7 mapped to ALSA ch 0-7
-	bindings.0.slave a;
+ 	bindings.0.slave a;
   	bindings.0.channel 0;
   	bindings.1.slave a;
@@ Line 455: / Line 454: @@
   	bindings.7.channel 7;
-	# Use rme9652_0 ch 16-23 mapped to ALSA ch 8-15
+ 	# Use rme9652_0 ch 16-23 mapped to ALSA ch 8-15
   	bindings.8.slave a;
@@ Line 474: / Line 473: @@
   	bindings.15.channel 23;
-	# Use rme9652_1 ch 8-15 mapped to ALSA ch 16-23
+ 	# Use rme9652_1 ch 8-15 mapped to ALSA ch 16-23
   	bindings.16.slave b;

@@ Line 389: / Line 389: @@
 The above example for a virtual multi channel device uses bindings to make the connections work. The following is a more advanced asoundrc for 2 RME Hammerfalls which is a professional multichannel sound device. Below is a full explanation of how bindings work.
   # This is for two RME Hammerfall cards. They have been conceptually split into rows
@@ Line 434: / Line 435: @@
   	slaves.b.pcm rme9652_1;
   	slaves.b.channels 26;
-−
 	# Use rme9652_0 ch 0-7 mapped to ALSA ch 0-7
-−
 	bindings.0.slave a;
   	bindings.0.channel 0;
@@ Line 453: / Line 454: @@
   	bindings.7.slave a;
   	bindings.7.channel 7;
-−
 	# Use rme9652_0 ch 16-23 mapped to ALSA ch 8-15
-−
   	bindings.8.slave a;
   	bindings.8.channel 16;

@@ Line 435: / Line 435: @@
   	slaves.b.channels 26;
-        # Use rme9652_0 ch 0-7 mapped to ALSA ch 0-7
+	# Use rme9652_0 ch 0-7 mapped to ALSA ch 0-7
- 	bindings.0.slave a;
+	bindings.0.slave a;
   	bindings.0.channel 0;
   	bindings.1.slave a;
@@ Line 454: / Line 454: @@
   	bindings.7.channel 7;
-        # Use rme9652_0 ch 16-23 mapped to ALSA ch 8-15
+	# Use rme9652_0 ch 16-23 mapped to ALSA ch 8-15
   	bindings.8.slave a;
@@ Line 473: / Line 473: @@
   	bindings.15.channel 23;
- 	# Use rme9652_1 ch 8-15 mapped to ALSA ch 16-23
+	# Use rme9652_1 ch 8-15 mapped to ALSA ch 16-23
   	bindings.16.slave b;

← Older revision		Revision as of 15:03, 28 July 2011
Line 402:		Line 402:
	# \| 16 17 18 19 20 21 22 23 \|		# \| 16 17 18 19 20 21 22 23 \|
	# \| 26 27\|		# \| 26 27\|
−

@@ Line 390: / Line 390: @@
 The above example for a virtual multi channel device uses bindings to make the connections work. The following is a more advanced asoundrc for 2 RME Hammerfalls which is a professional multichannel sound device. Below is a full explanation of how bindings work.
-  # This is for two RME Hammerfall cards. They have been split into top row
+  # This is for two RME Hammerfall cards. They have been conceptually split into rows
-  # and bottom row with channels 0-7+16-25 on rme9652_0 and channels 8-15+26-27 on
+  # and will be mapped to ALSA channels 0-27: with channels 0-7 and 16-23 on rme9652_0 and channels 8-15 on
-  # rme9652_1. NB. channels 24-27 are used as two stereo channels while the others are mono.
+  # rme9652_1, and finally channels 24-25 of both cards, used as two stereo channels, mapped to ALSA channels 24-27 (while the others are mono).
-  # eg.             card1
+  # eg. ALSA channels on card1 = rme9652_0
   #     | 0  1  2  3  4  5  6  7       |
-  #     | 8  9  10 11 12 13 14 15 24 25|
+  #     | 8  9  10 11 12 13 14 15      |
-  #                 card2
+ #     |                         24 25|
-  #     | 16 17 18 19 20 21 22 23 24 25|
@@ Line 432: / Line 435: @@
   	slaves.b.pcm rme9652_1;
   	slaves.b.channels 26;
   	bindings.0.slave a;
   	bindings.0.channel 0;
@@ Line 448: / Line 454: @@
   	bindings.7.slave a;
   	bindings.7.channel 7;
   	bindings.8.slave a;
   	bindings.8.channel 16;
@@ Line 465: / Line 474: @@
   	bindings.15.channel 23;
-  	# Use rme9652_1
+  	# Use rme9652_1 ch 8-15 mapped to ALSA ch 16-23
   	bindings.16.slave b;
@@ Line 484: / Line 493: @@
   	bindings.23.channel 15;
-  	# stereo channels
+  	# stereo channels: slave a+b ch 24-25 mapped to ALSA ch 24-27
   	bindings.24.slave a;
@@ Line 500: / Line 509: @@
 There are two sound cards which are linked with a wordclock pipe. That allows them to keep sample sync with each other which is very important for multichannel work. If the sample rates are not in sync then your sounds become out of time with each other.
-Each sound card has a number of physical channels 19 + 10. They are represented in <code>/proc/asound/card</code>x as <code>pcm</code>X<code>c</code> (capture) and <code>pcm</code>X<code>p</code> (playback). Where X equals the number of the physical input/output (i/o) channels starting at 0.
+In this example each sound card has a number of physical channels being used: 18 (a) + 10 (b). They are represented in <code>/proc/asound/card</code>x as <code>pcm</code>X<code>c</code> (capture) and <code>pcm</code>X<code>p</code> (playback). Where X equals the number of the physical input/output (i/o) channels starting at 0.
 If you look at the lines:

@@ Line 327: / Line 327: @@
 ===Virtual multi channel devices===
-If you would like to link two or more ALSA devices together so that you have a virtual multi channel device it is possible. However this will not create the mythical "multi-channel soundcard out of el-cheapo consumer cards". The real devices will drift out of sync over time. It is sometimes helpful to make applications see for example, one 4 channel card to allow for flexible routing if they can't easily be made to talk to multiple cards (making use of JACK being one example).
+If you would like to link two or more ALSA devices together so that you have a virtual multi channel device it is possible. However this will not create the mythical "multi-channel soundcard out of el-cheapo consumer cards". The real devices will drift out of sync over time. It is sometimes helpful to make applications that can for example see one 4 channel card to allow for flexible routing if they can't easily be made to talk to multiple cards (making use of JACK being one example).
 Copy and paste the following into your asoundrc.

@@ Line 87: / Line 87: @@
 ===The Control device===
-The control device for a card is the way that programs modify various "controls" on the card. For many cards this includes the mixer, some cards, for example the rme9652, have no mixer. However, they do still have a number of other controls and some programs like JACK need to be able to access them. Examples include the digital I/O sync indicators, sample clock source switch and so on.
+The control device for a card is the way that programs modify various "controls" on the card. For many cards this includes the mixer (but some cards, for example the rme9652, have no mixer). However, they do still have a number of other controls and some programs like JACK need to be able to access them. Examples include the digital I/O sync indicators, sample clock source switch and so on.
 ==Aliases==

← Older revision		Revision as of 07:24, 16 June 2011
Line 1:		Line 1:
		+	{\| align="right"
		+	\| __TOC__
		+	\|}
	==Why asoundrc?==		==Why asoundrc?==