Difference between revisions of "Tips And Tricks"
From Open Sound System
(Adding ossxmix tip) |
|||
| Line 1: | Line 1: | ||
| + | *Starting ossxmix minimized on startup | ||
| + | :The '-b' option starts ossxmix in the background - minimized to tray if tray support is compiled in, iconfied window if not. | ||
| + | :The '-S' option prevents ossxmix from trying to use a system tray. | ||
| + | :'ossxmix -Sb' will always start an iconified window. | ||
| + | #KDE: create a desktop shortcut in ~/.kde/Autostart with the command 'ossxmix -b'. | ||
| + | #:Alternative: create a desktop shortcut in the same place, with the command "ossxmix -Sb'. Go to Applications->"Advance options" and select "Place in system tray". | ||
| + | #Gnome: go to Control center->Session->"Startup Programs" and add "ossxmix -b". | ||
| + | #X11 in general: edit the Xsession file. Make sure the tray program runs before ossxmix, or use the '-S' switch as well. | ||
| + | #See [http://gentoo-wiki.com/HOWTO_Autostart_Programs] for info on other environments. | ||
| + | |||
| + | *Changing the default sound output used for /dev/dsp | ||
| + | # $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, followed by running 'ossdetect -v', the default device can be modified. | ||
| + | #: The root directory $OSSLIBDIR can be found by checking /etc/oss.conf. It is typically /usr/lib/oss/. | ||
| + | # Relink /dev/dsp to the desired /dev/oss/.../ device. If OSS insists on recreating /dev/dsp, simply add the appropriate linking command to $OSSLIBDIR/soundon.user. | ||
*Recording sound output of a program: | *Recording sound output of a program: | ||
# Many drivers offer a 'vol' mixer control. If this is used as a recording source, than the current sound output will be recorded. Note that this is the mixed total of all sound played, not of a single program. | # Many drivers offer a 'vol' mixer control. If this is used as a recording source, than the current sound output will be recorded. Note that this is the mixed total of all sound played, not of a single program. | ||
| Line 7: | Line 21: | ||
# OSS wrappers can be used to record the output of a program. vsound is one such wrapper. (vsound doesn't handle output to /dev/oss/* device nodes, but all OSS-supporting programs are/can be easily made to output to /dev/dsp). | # OSS wrappers can be used to record the output of a program. vsound is one such wrapper. (vsound doesn't handle output to /dev/oss/* device nodes, but all OSS-supporting programs are/can be easily made to output to /dev/dsp). | ||
#: vsound ossplay test.wav | #: vsound ossplay test.wav | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 22:34, 4 May 2008
- Starting ossxmix minimized on startup
- The '-b' option starts ossxmix in the background - minimized to tray if tray support is compiled in, iconfied window if not.
- The '-S' option prevents ossxmix from trying to use a system tray.
- 'ossxmix -Sb' will always start an iconified window.
- KDE: create a desktop shortcut in ~/.kde/Autostart with the command 'ossxmix -b'.
- Alternative: create a desktop shortcut in the same place, with the command "ossxmix -Sb'. Go to Applications->"Advance options" and select "Place in system tray".
- Gnome: go to Control center->Session->"Startup Programs" and add "ossxmix -b".
- X11 in general: edit the Xsession file. Make sure the tray program runs before ossxmix, or use the '-S' switch as well.
- See [1] for info on other environments.
- Changing the default sound output used for /dev/dsp
- $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, followed by running 'ossdetect -v', the default device can be modified.
- The root directory $OSSLIBDIR can be found by checking /etc/oss.conf. It is typically /usr/lib/oss/.
- Relink /dev/dsp to the desired /dev/oss/.../ device. If OSS insists on recreating /dev/dsp, simply add the appropriate linking command to $OSSLIBDIR/soundon.user.
- Recording sound output of a program:
- Many drivers offer a 'vol' mixer control. If this is used as a recording source, than the current sound output will be recorded. Note that this is the mixed total of all sound played, not of a single program.
- ossrecord -ivol blah.wav
- vmix loopback driver can record the output of a program. Set vmix_numloops to 1 (or more) in vmix.conf, and make the program output to the newly created /dev/oss/vmix0/loop0 device. Then record from that device. e.g.
- ossplay test.wav -d/dev/oss/vmix0/loop0 &
- ossrecord test2.wav -d/dev/oss/vmix0/loop0
- OSS wrappers can be used to record the output of a program. vsound is one such wrapper. (vsound doesn't handle output to /dev/oss/* device nodes, but all OSS-supporting programs are/can be easily made to output to /dev/dsp).
- vsound ossplay test.wav
