dbfsd(1) [debian man page]
DBFSD(1) General Commands Manual DBFSD(1) NAME
dbfsd - DB Fourier Synthesis Daemon SYNOPSIS
dbfsd [options] DESCRIPTION
The audio daemon dbfsd serves as the backend part to the DBMix-project. It allows to connect several audio streams and combines them into one, using high quality Fourier synthesis. Connections currently transfer data via pipes; a network (socket) connection method is being developed, but not yet included. Use dbcat to push audio streams into dbfsd. The mixer settings are controlled via dbmixer. Dbfsd actually can handle two different output destinations: one is the master device, usually used for the main output; the second one is referred to as the cueing device, which is handy for so-called pre-fade listening. That is, one can check the starting position of the next song, or adjust its pitch before sending it to the main output. Obviously, for stereo output to both the master and the cueing device, two sound cards (or a sound card with two distinct output channels) are needed. The -e switch offers a way to cue with only a sin- gle sound card, but output is reduced to mono streams. OPTIONS
-a dev Set master output device to dev. (Default: /dev/dsp.) -b dev Set cue output device to dev. (Default: /dev/dsp2.) -c Enable cue output. (Default: cueing disabled.) -d Print out debug messages to console. (Default: debugging disabled.) -e Output cue as left channel of master out. This option also enables cue output even if -c is not set. (Default: cue to both chan- nels of cue output device.) -h Print summary of available options. -n max Allow at most max input channels. (Default: 4.) -o Send master output to stdout. (Default: send output to master output device.) -r n Set number of OSS output fragments to n. Decreasing this number will reduce latency between, say, starting dbcat, and hearing the results of that action. Too low a value, however, will results in drop-outs in the stream. This value can also be adjusted via the preferences dialog in the dbmixer application. (Default: 128.) -s n Set number of input channels that should be created as sockets to n. (Default: 0.) -v Print version information. (Default: no version information.) FILES
/tmp/chn_comm Pipe to input channel n. Direct use of the pipes is deprecated, use dbcat instead. The pipes expect audio input in unsigned 16bit PCM format at 44.1kHz. SEE ALSO
dbcat(1), dbin(1), dbmixer(1), dbmix(7). AUTHOR
This manual page was written by Daniel Kobras <kobras@debian.org>, for the Debian GNU/Linux system (but may be used by others). It is heavily based on DBMix's README file written by Robert Michael S Dean. July 23, 2002 DBFSD(1)
Check Out this Related Man Page
7(16 December 2012) 7(16 December 2012) NAME
dsp - Open Sound System audio devices DESCRIPTION
/dev/dsp is the default audio device in the system. It's connected to the main speakers and the primary recording source (such as micro- phone). The system administrator can set /dev/dsp to be a symbolic link to the desired default device. The ossinfo utility can be used to list the available audio devices in the system. /dev/dsp_mmap, /dev/dsp_ac3, /dev/dsp_multich and /dev/dsp_spdifout are default audio devices for specific applications such as games or media (DVD) players. DIRECT ACCESS AUDIO DEVICE FILES
OSS 4.0 (and later) will create audio devices under /dev/oss/<device> directory. For example /dev/oss/sblive0/pcm0 is the first audio device that belongs to the first Sound Blaster Live! or Audigy card in the system. These direct devices are used when an application needs to access specific audio device (instead of the default one). You can use the ossinfo(1) utility with the -a option to get a list of the available audio devices in the system. LEGACY AUDIO DEVICE FILES
Traditionally OSS has created device files like /dev/dsp0 to /dev/dspN for each audio device in the system. OSS 4.0 still supports this legacy naming. These files are symbolic links to the actual device files located under /dev/oss. The ossdevlinks(8) utility is used to manage these links and it will be automatically invoked when OSS is started. COMPATIBILITY
o The /dev/dsp (default() audio device file will be supported by all OSS implementations and versions. o The special purpose audio default devices (such as /dev/dsp_mmap) are only supported by OSS 4.0 and later. o The legacy audio device files (such as /dev/dsp1) are supported by all OSS versions and implementations. o New style audio device files (under /dev/oss) are only supported by OSS 4.0 and later. However some independent OSS implementations may only support the legacy naming even they are otherwise OSS 4.0 compatible. o /dev/dsp0 doesn't exist in all Linux systems which use /dev/dsp for the same purpose. In such systems /dev/dsp points to the first audio device and /dev/dsp1 to the second. PROGRAMMING INFORMATION
See the Audio Programming section of the OSS Programmer's Guide (DSP(2)) for more info. OPTIONS
None FILES
o /dev/dsp Default audio device o /dev/dsp_mmap Default audio device for applications using mmap(2) o /dev/dsp_ac3 Default audio device for applications sending Dolby Digital (AC3) audio to an external receiver. o /dev/dsp_multich Default multichannel (4.0-7.1) audio output device o /dev/dsp_spdifout Default digital audio (S/PDIF) output device o /dev/oss/<driver>/pcmN Direct access device files for individual audio devices. o /dev/dsp0 to /dev/dspN Legacy style direct access audio device files. AUTHOR
4Front Technologies OSS Devices 7(16 December 2012)