alsa-utils/seq/aconnect
Diego E. 'Flameeyes' Pettenò 6232f1c96c Make some static tables and strings constants.
By doing this we move them from the .data section to .rodata setion,
or from .data.rel to .data.rel.ro.

The .rodata section is mapped directly from the on-disk file, which is
always a save, while .data.rel.ro is mapped directly when using
prelink, which is a save in a lot of cases.

Signed-off-by: Diego E. 'Flameeyes' Pettenò <flameeyes@gmail.com>
2008-11-21 13:10:02 +01:00
..
aconnect.1 Fix aconnect man page 2007-01-08 11:46:12 +01:00
aconnect.c Make some static tables and strings constants. 2008-11-21 13:10:02 +01:00
Makefile.am i18nize some programs 2005-06-23 10:38:06 +00:00
README.aconnect - removed obsolete group option. 2002-07-17 12:05:15 +00:00

================================================================
	aconnect - control subscriptions
		ver.0.1.3
	Copyright (C) 1999-2000 Takashi Iwai
================================================================

aconnect is a utility to control subscriptions of two ports as the
third "manager" client.

For example, the following connects two ports, from 64:0 to 65:0.

	% aconnect 64:0 65:0

To disconnect the existing subscription, use -d option.

	% aconnect -d 64:0 65:0

To see which port is available as input port, run the following
command:

	% aconnect -i
	client 0: 'System' [type=kernel]
	    0 'Timer           '
	    1 'Announce        '
	client 64: '0: MIDI Synth' [type=kernel]
	    0 'card 0: synth-midi: 0'

Similary, to see the output ports, use -o flag.

	% aconnect -o
	client 64: '0: MIDI Synth' [type=kernel]
	    0 'card 0: synth-midi: 0'
	client 65: 'AWE Wave Table Synth : 0' [type=kernel]
	    0 'Emu8000 port 0  '
	    1 'Emu8000 port 1  '
	    2 'Emu8000 port 2  '
	    3 'Emu8000 port 3  '

The option -l together with -i or -o shows subscribers for each port.

Ports are connected exclusively when the option -e is specified.

For modifying time-stamp with a queue, use -r or -t option followed by
a queue index which updates the time-stamp.  Former uses real-time queue,
while the latter uses tick queue.  The queue must be used (not necessarily
owned) by the receiver client.