Tips And Tricks - Revision history

Cesium: /* ALSA Emulation */

2012-07-07T09:05:09Z

‎ALSA Emulation

Cesium: Protected "Tips And Tricks": Excessive spamming ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2011-07-10T14:10:43Z

Protected "Tips And Tricks": Excessive spamming ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

Cesium: rollback

2011-07-10T14:10:21Z

rollback

184.172.50.126: /* OSSLIBDIR location */

2011-07-10T13:41:28Z

‎OSSLIBDIR location

81.25.142.26: /* Using multimedia keys with OSS */

2011-07-10T08:04:33Z

‎Using multimedia keys with OSS

Cesium: Reverted edits by 220.88.69.93 (talk) to last revision by Cesium

2011-07-10T04:32:08Z

Reverted edits by 220.88.69.93 (talk) to last revision by Cesium

220.88.69.93: /* Changing the default sound output */

2011-07-10T01:54:41Z

‎Changing the default sound output

Cesium: Protected "Tips And Tricks" ([edit=autoconfirmed] (expires 04:30, 5 June 2011 (UTC)) [move=autoconfirmed] (expires 04:30, 5 June 2011 (UTC)))

2011-05-29T04:30:51Z

Protected "Tips And Tricks" ([edit=autoconfirmed] (expires 04:30, 5 June 2011 (UTC)) [move=autoconfirmed] (expires 04:30, 5 June 2011 (UTC)))

Cesium: Reverted edits by 138.73.16.5 (talk) to last revision by Cesium

2011-05-29T04:30:22Z

Reverted edits by 138.73.16.5 (talk) to last revision by Cesium

Show changes

138.73.16.5: Undo revision 2285 by Cesium (talk)

2011-05-29T02:53:43Z

Undo revision 2285 by Cesium (talk)

Show changes

@@ Line 175: / Line 175: @@
 === ALSA Emulation ===
 *There are two main methods to achieve this:
-**libasound2's pcm-oss plugin:
+<ol>
-*** Easiest method, but will not work with all programs. It works by making libasound use OSS via the pcm-oss plugin.
+<li>libasound2's pcm-oss plugin:
-*** First, install the pcm-oss plugin. It is included in the alsa-plugins distribution.
+* Easiest method, but will not work with all programs. It works by making libasound use OSS via the pcm-oss plugin.
-**** Debian: install libasound2-plugins package.
+* First, install the pcm-oss plugin. It is included in the alsa-plugins distribution.
-*** Make sure an ~/.asoundrc file exists. It should contain the lines below:
+** Debian: install libasound2-plugins package.
    pcm.!default
+   {
@@ Line 190: / Line 192: @@
      device /dev/dsp
+   }
-:* OSSv4 cuckoo module:
+</pre></li>
-:** Harder, and will fail on some systems. It works by representing OSSv4 drivers as a soundcard to the ALSA modules, and supplying a "driver" for them.
+<li>
-:** Note that using pcm-oss conflicts with cuckoo - libasound needs to output to ALSA's device files, so rename ~/.asoundrc if you were using pcm-oss before doing this.
+libasound2's pulseaudio plugin:
-:**: Also, nearly all the commands below require root permissions.
+* Another easy method. Again, libasound must be set up to use Pulseaudio (which is done by default with many distros). Then Pulseaudio must be [[Configuring_Applications_for_OSSv4#Pulseaudio|set up to use OSS]].
-:** First, we need to get the ALSA modules back:
+</li>
-:*** Goto /lib/modules/$(uname -r)/, and extract the sound-preoss.tar.bz2 file.
+<li>
-:*** We need to prune out the OSS emulation modules, since these might conflict with actual OSS, so run "rm -rf kernel/sound/core/oss".
+OSSv4 cuckoo module:
-:** Second, goto /usr/lib/oss/cuckoo, and run "make install".
+* Harder, and will fail on most systems. It works by representing OSSv4 drivers as a soundcard to the ALSA modules, and supplying a "driver" for them.
-:** You can now run "modprobe cuckoo", and test with "speaker-test" etc. whether this works.
+* Note that using pcm-oss conflicts with cuckoo - libasound needs to output to ALSA's device files, so rename ~/.asoundrc if you were using pcm-oss before doing this.
-:** To make this stick, we need to edit the startup script, so that it loads cuckoo after loading OSS. Edit $OSSLIBDIR/soundon.user, and add "modprobe cukoo" before "exit 0" line.
+*: Also, nearly all the commands below require root permissions.
-*A general problem with ALSA emulation is that some programs probe for driver support in the order "ALSA, OSS". So programs that were using OSS by default may now try to use the emulation with possibly inferior results. So if there are problems after installation, make sure the program uses the OSS support rather than the emulation.
+** First, we need to get the ALSA modules back:

@@ Line 14: / Line 14: @@
 # Alternative: $OSSLIBDIR/etc/installed_drivers influences the order of sound cards set by ossdetect. By removing other devices or moving the desired sound card to the first place, the default device can be modified. After the change, restart OSS and run "sudo ossdevlinks -v -r" and it will relink /dev/dsp for you.
-Always the best content from these prodigious wtriers.
+==== OSSLIBDIR location ====
 === Recording sound output of a program ===
@@ Line 52: / Line 54: @@
 :*See 'vmixctl' manpage for more details.
-Your arictle was excellent and erudite.
+=== Using multimedia keys with OSS ===
 === ALSA Emulation ===

@@ Line 14: / Line 14: @@
 # Alternative: $OSSLIBDIR/etc/installed_drivers influences the order of sound cards set by ossdetect. By removing other devices or moving the desired sound card to the first place, the default device can be modified. After the change, restart OSS and run "sudo ossdevlinks -v -r" and it will relink /dev/dsp for you.
-==== OSSLIBDIR location ====
+Always the best content from these prodigious wtriers.
-<span id="OSSLIBDIR"></span>
-* The OSSv4 root directory $OSSLIBDIR can be found by checking /etc/oss.conf. It is almost always /usr/lib/oss/.
 === Recording sound output of a program ===

@@ Line 54: / Line 54: @@
 :*See 'vmixctl' manpage for more details.
-=== Using multimedia keys with OSS ===
+Your arictle was excellent and erudite.
-# First, we should check if the keys are recongnized by X11 or some other program. Run xev, and see if pressing the keys elicits a response.
-#* If it does not, than we must make the keys be recognized by X11/WM/etc., before they can be used for anything. This is outside the scope of this wiki, but is documented at [http://en.gentoo-wiki.com/wiki/Multimedia_Keys] and at [http://wiki.archlinux.org/index.php/Extra_Keyboard_Keys]. Some WMs, once set up, will automatically connect the multimedia keys to appropriate functions.
-# If/once the keys are recognized, does it work out of the box?
-#* If not, it may be a function of old gstreamer version. Gnome uses gstremaer for this, but older gstreamer didn't support OSSv4. See [[Configuring_Applications_for_OSSv4#Gnome_Volume_Applet]] for a possible solution.
-#* If the above does not work or is not applicable, we can connect the keys to external scripts which will perform the appropriate function (See examples below). The method to connect external scripts to keys is better described at [http://en.gentoo-wiki.com/wiki/Multimedia_Keys] and at [http://wiki.archlinux.org/index.php/Extra_Keyboard_Keys] again.
-#** For example in KDE, you can start the "Control Center", enter "Regional & Accessibility" -> "Input Actions", click on "New Action" and make its type "Keyboard Shortcut -> Command/URL", and then set the multimedia key to launch the script. (Names can be different due to localizations).
-−
-===== External scripts which can control volume =====
-====== mute.sh ======
- #!/bin/sh
- CTRL=vmix0-outvol
- touch $HOME/.volume
- VOLUME=$(cat $HOME/.volume)
- CURRENT=$(ossmix | grep $CTRL | awk '{print $4}' | awk -F : '{print $1}')
- if [ $CURRENT = "0.0" ]; then
-       ossmix $CTRL $VOLUME
-       > $HOME/.volume
- else
-       VOLUME=$(ossmix | grep $CTRL | awk '{print $4}' | awk -F : '{print $1}')
-       ossmix $CTRL 0
-       echo $VOLUME > $HOME/.volume
- fi
-−
-====== ossvol ======
-If you want the ability to mute and then unmute/increase volume at the same time the following script is one option. (This script relies on OSSv4.1 functionality - see note on ossmix below).
-−
-[http://ossvol.sourceforge.net ossvol]:
-−
- #!/bin/bash
-−
- # ossvol is a simple script to manage oss volume levels and muting.
-−
- # Script by: Daniel J Griffiths <ghost1227@archlinux.us>
- # Configure stuff
- VOLSTORE=~/.volume
- CHANNEL="vmix0-outvol"
- ARGUMENT=$2
- # You shouldn't have to edit below here.
- err() {
-    echo "$1"
-    exit 1
-−
- usage() {
-    echo "usage: ossvol [option] [argument]"
-    echo
-    echo "Options:"
-    echo "     -i, --increase - increase volume by [argument]"
-    echo "     -d, --decrease - decrease volume by [argument]"
-    echo "     -t, --toggle   - toggle mute on and off"
-    echo "     -h, --help     - display this"
-    exit
-−
- toggle() {
-    if [ -f $VOLSTORE ]; then
-        ossmix $CHANNEL `cat $VOLSTORE`
-        rm $VOLSTORE
-    else
-        VOLUME=$(ossmix $CHANNEL | awk '{print $10}' | awk -F : '{print $1}')
-        ossmix $CHANNEL 0
-        echo $VOLUME > $VOLSTORE
-    fi
-−
- increase() {
-    if [ -f $VOLSTORE ]; then
-        TMPVOL=`cat $VOLSTORE`
-        NEWVOL=`expr $TMPVOL + $ARGUMENT`
-        ossmix $CHANNEL +$NEWVOL
-        rm $VOLSTORE
-    else
-        ossmix $CHANNEL +$ARGUMENT
-    fi
-−
- decrease() {
-    if [ -f $VOLSTORE ]; then
-        TMPVOL=`cat $VOLSTORE`
-        NEWVOL=`expr $TMPVOL - $ARGUMENT`
-        ossmix $CHANNEL -- -$NEWVOL
-        rm $VOLSTORE
-    else
-        ossmix $CHANNEL -- -$ARGUMENT
-    fi
-−
- case "$1" in
-    '-i'|'--increase')
-    increase
-    ;;
-    '-d'|'--decrease')
-    decrease
-    ;;
-    '-t'|'--toggle')
-    toggle
-    ;;
-    ''|'-h'|'--help')
-    usage
-    ;;
-    *)
-    err "Unrecognized option \`$1', see ossvol --help"
-    ;;
- esac
-−
-OSSv4.1 includes an ossmix which allows you to change volume in a relative fashion: 'ossmix vmix0-vol -- -2' and 'ossmix vmix-vol +2'. The two scripts below can be used to have this functionality in OSSv4.0:
-−
-====== lowervolume.sh ======
-  #!/bin/sh
-  CTRL=vmix0-vol
-  VOL=$(ossmix | grep $CTRL | awk '{print $4}' | awk -F : '{print $1}')
-  VOL=$(echo $VOL | awk '{print $1-2}')
-  ossmix -- $CTRL $VOL
-−
-====== raisevolume.sh ======
-  #!/bin/sh
-  CTRL=vmix0-vol
-  VOL=$(ossmix | grep $CTRL | awk '{print $4}' | awk -F : '{print $1}')
-  VOL=$(echo $VOL | awk '{print $1+2}')
-  ossmix $CTRL $VOL
-−
-You may wish to modify a different mixer control than vmix0-vol. In that case, you will need to change the value of CTRL above.
 === ALSA Emulation ===

← Older revision		Revision as of 04:32, 10 July 2011
Line 1:		Line 1:
−	~~If my porblem was~~ a ~~Death Star~~, this ~~article~~ is a ~~photon torpedo~~.	+	=== Changing the default sound output ===
		+	<span id="Changing the default sound output used for /dev/dsp"></span>
		+	#* The typical method is to relink /dev/dsp to the desired /dev/oss/.../ device. e.g.
		+	#:: sudo ln -sf /dev/oss/oss_sbxfi0/pcm0 /dev/dsp
		+	#:The device node matching the desired sound output can be discovered by running 'osstest' (and seeing which node produces the desired output) or by examining 'ossinfo -a' (displays list of nodes).
		+	#* It's highly recommended to make vmix attach to the newly default device. vmix is OSSv4's software mixer and multiple programs will usually not be able to use the output at the same time if it's not attached. Since the default output was changed, vmix will have to be set to attach to the new output.
		+	#*: In OSS 4.1 and above, add a "vmixctl attach" to be run after OSS is loaded. This can be done by [[Tips And Tricks#Running a command immediately after OSS is loaded\|editing the soundon.user file]]. It is also recommended to also add "vmix_no_autoattach=1" line to the [[Tips And Tricks#OSSLIBDIR\|$OSSLIBDIR]]/conf/osscore.conf file (so vmix won't use the old default too). "vmixctl attach" syntax looks like this:
		+	#*: vmixctl attach /dev/oss/oss_sbxfi0/pcm0 /dev/oss/oss_sbxfi0/pcmin0
		+	#*::The second and third argument represent output and input nodes for vmix to attach to, allowing full duplex when /dev/dsp is used. However, the third argument can be omitted in some cases. See "vmixctl" manpage for explanation.
		+	#*: In OSS 4.0 you'll need to set vmix_masterdev in [[Tips And Tricks#OSSLIBDIR\|$OSSLIBDIR]]/conf/vmix.conf file.
		+	#* Modern OSs put /dev on a ramdisk (i.e. it gets erased in boot), so we need to make sure the new correct setting remains. OSSv4.2 and above stores /dev/dsp setting in [[Tips And Tricks#OSSLIBDIR\|$OSSLIBDIR]]/etc/legacy_devices, so these should be saved automatically as long as OSS is shut down properly (You can run "sudo ossdevlinks" to save this manually).
		+	#:: OSSv4 before version 4.2 requires editing the [[Tips And Tricks#OSSLIBDIR\|$OSSLIBDIR]]/soundon.user file again and placing the relinking command there. This would also work with newer OSSv4 versions.
		+	# Alternative: If the default output is set to an onboard soundcard and you're using another card, you can just disable onboard audio in the BIOS, and it won't be seen by OSS.
		+	# Alternative: $OSSLIBDIR/etc/installed_drivers influences the order of sound cards set by ossdetect. By removing other devices or moving the desired sound card to the first place, the default device can be modified. After the change, restart OSS and run "sudo ossdevlinks -v -r" and it will relink /dev/dsp for you.
		+
		+	==== OSSLIBDIR location ====
		+	<span id="OSSLIBDIR"></span>
		+	* The OSSv4 root directory $OSSLIBDIR can be found by checking /etc/oss.conf. It is almost always /usr/lib/oss/.

	=== Recording sound output of a program ===		=== Recording sound output of a program ===

@@ Line 1: / Line 1: @@
-=== Changing the default sound output ===
+If my porblem was a Death Star, this article is a photon torpedo.
-<span id="Changing the default sound output used for /dev/dsp"></span>
-#* The typical method is to relink /dev/dsp to the desired /dev/oss/.../ device. e.g.
-#::  sudo ln -sf /dev/oss/oss_sbxfi0/pcm0 /dev/dsp
-#:The device node matching the desired sound output can be discovered by running 'osstest' (and seeing which node produces the desired output) or by examining 'ossinfo -a' (displays list of nodes).
-#* It's highly recommended to make vmix attach to the newly default device. vmix is OSSv4's software mixer and multiple programs will usually not be able to use the output at the same time if it's not attached. Since the default output was changed, vmix will have to be set to attach to the new output.
-#*: In OSS 4.1 and above, add a "vmixctl attach" to be run after OSS is loaded. This can be done by [[Tips And Tricks#Running a command immediately after OSS is loaded|editing the soundon.user file]]. It is also recommended to also add "vmix_no_autoattach=1" line to the [[Tips And Tricks#OSSLIBDIR|$OSSLIBDIR]]/conf/osscore.conf file (so vmix won't use the old default too). "vmixctl attach" syntax looks like this:
-#*: vmixctl attach /dev/oss/oss_sbxfi0/pcm0 /dev/oss/oss_sbxfi0/pcmin0
-#*::The second and third argument represent output and input nodes for vmix to attach to, allowing full duplex when /dev/dsp is used. However, the third argument can be omitted in some cases. See "vmixctl" manpage for explanation.
-#*: In OSS 4.0 you'll need to set vmix_masterdev in [[Tips And Tricks#OSSLIBDIR|$OSSLIBDIR]]/conf/vmix.conf file.
-#* Modern OSs put /dev on a ramdisk (i.e. it gets erased in boot), so we need to make sure the new correct setting remains. OSSv4.2 and above stores /dev/dsp setting in [[Tips And Tricks#OSSLIBDIR|$OSSLIBDIR]]/etc/legacy_devices, so these should be saved automatically as long as OSS is shut down properly (You can run "sudo ossdevlinks" to save this manually).
-#:: OSSv4 before version 4.2 requires editing the [[Tips And Tricks#OSSLIBDIR|$OSSLIBDIR]]/soundon.user file again and placing the relinking command there. This would also work with newer OSSv4 versions.
-# Alternative: If the default output is set to an onboard soundcard and you're using another card, you can just disable onboard audio in the BIOS, and it won't be seen by OSS.
-# Alternative: $OSSLIBDIR/etc/installed_drivers influences the order of sound cards set by ossdetect. By removing other devices or moving the desired sound card to the first place, the default device can be modified. After the change, restart OSS and run "sudo ossdevlinks -v -r" and it will relink /dev/dsp for you.
-−
-==== OSSLIBDIR location ====
-<span id="OSSLIBDIR"></span>
-* The OSSv4 root directory $OSSLIBDIR can be found by checking /etc/oss.conf. It is almost always /usr/lib/oss/.
 === Recording sound output of a program ===