Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

oss_madi(7) [debian man page]

oss_madi(7)							    OSS Devices 						       oss_madi(7)

NAME
oss_madi - RME HDSP MADI and AES32 audio driver DESCRIPTION
Open Sound System driver for RME HDSP MADI and AES32 audio interfaces. This driver has been developed for RME HDSP MADI but it also supports HDSP AES32. The driver has been tested under Linux and Solaris under x86 and Sparc. The internal engine of the card supports 64 playback channels and 64 recording channels. Only the first channels are connected to the actual input and output ports of the card. The mixer section of the card has recording level settings for all inputs. There is also an output mixer. Each output channel has mixer sliders for corresponding input channel and corresponding audio playback channel. There is a full 64x(64+64) mixing matrix supported by the hardware. For the time being this mixer matrix cannot be accessed directly by the applications. However support for the SNDCTL_MIX_MATRIX_WRITE and SNDCTL_MIX_MATRIX_READ ioctl calls can be added in the future. DEVICE FILES
By default the driver will create input and output device files for each 32 stereo pairs. This can be changed by editing the settings in oss_madi.conf (see below). The application can set the devices to use 1, 2, 4, 8, 16, 32 or 64 channels. The device file being used selects the first channel slot within the available channels. For example pcm0 and pcmin0 sill select channel 0. Equally well pcm1 and pcmin1 will select channel slot 2 (assuming that madi_devsize option is set to 2). The first device (pcm0 and pcmin0) can be set to use up to 64 channels. The last devices (pcm31 and pcmin31) only support 1 or 2 channel mode. The other device files support channel configurations where the last channel doesn't exceed the number of total channels (madi_maxchannels). Also the driver will not let two device files to share any of the channels with some other open device file. This channel allocation mechanism gives maximum flexibility to the user. It is possible to use some output channels by multi channel appli- cation while the others are available for other applications. This works as long the channel allocations by different applications don't overlap. OPTIONS
o madi_maxchannels Number of channels supported by the driver. The default is 64 which is also the maximum. This parameter can be set to a lower value if full 64 channels are not required. With less channels the mixer/control panel interface will require less space on screen. o madi_devsize By default this parameter is set to 2 which means that a device file will be created for each stereo channel pair. Possible values are 1, 2, 4, 8, 16, 32 or 64. LIMITATIONS
o The current driver doesn't support all control panel features of the card. For example sampling rate is fixed to 48 kHz. More features will be added on contract. o Use of mmap() is and will not be supported. o Virtual mixer is not supported (yet). FILES
/etc/oss4/conf/oss_madi.conf Device configuration file. AUTHOR
4Front Technologies 16 December 2012 oss_madi(7)

Check Out this Related Man Page

Tcl_GetStdChannel(3)					      Tcl Library Procedures					      Tcl_GetStdChannel(3)

__________________________________________________________________________________________________________________________________________________

NAME
Tcl_GetStdChannel, Tcl_SetStdChannel - procedures for retrieving and replacing the standard channels SYNOPSIS
#include <tcl.h> Tcl_Channel Tcl_GetStdChannel(type) Tcl_SetStdChannel(channel, type) ARGUMENTS
int type (in) The identifier for the standard channel to retrieve or modify. Must be one of TCL_STDIN, TCL_STDOUT, or TCL_STDERR. Tcl_Channel channel (in) The channel to use as the new value for the specified standard channel. _________________________________________________________________ DESCRIPTION
Tcl defines three special channels that are used by various I/O related commands if no other channels are specified. The standard input channel has a channel name of stdin and is used by read and gets. The standard output channel is named stdout and is used by puts. The standard error channel is named stderr and is used for reporting errors. In addition, the standard channels are inherited by any child processes created using exec or open in the absence of any other redirections. The standard channels are actually aliases for other normal channels. The current channel associated with a standard channel can be retrieved by calling Tcl_GetStdChannel with one of TCL_STDIN, TCL_STDOUT, or TCL_STDERR as the type. The return value will be a valid channel, or NULL. A new channel can be set for the standard channel specified by type by calling Tcl_SetStdChannel with a new channel or NULL in the channel argument. If the specified channel is closed by a later call to Tcl_Close, then the corresponding standard channel will automatically be set to NULL. If Tcl_GetStdChannel is called before Tcl_SetStdChannel, Tcl will construct a new channel to wrap the appropriate platform-specific stan- dard file handle. If Tcl_SetStdChannel is called before Tcl_GetStdChannel, then the default channel will not be created. If one of the standard channels is set to NULL, either by calling Tcl_SetStdChannel with a NULL channel argument, or by calling Tcl_Close on the channel, then the next call to Tcl_CreateChannel will automatically set the standard channel with the newly created channel. If more than one standard channel is NULL, then the standard channels will be assigned starting with standard input, followed by standard out- put, with standard error being last. See Tcl_StandardChannels for a general treatise about standard channels and the behaviour of the Tcl library with regard to them. SEE ALSO
Tcl_Close(3), Tcl_CreateChannel(3), Tcl_Main(3), tclsh(1) KEYWORDS
standard channel, standard input, standard output, standard error Tcl 7.5 Tcl_GetStdChannel(3)
Man Page