alsa-utils/seq/aconnect
Jaroslav Kysela feb9c4cdec reshuffle included files to include config.h as first
config.h may contain defines like _FILE_OFFSET_BITS which influence
the system wide include files (off_t types, open -> open64 function
usage etc.).

Related: https://github.com/alsa-project/alsa-utils/pull/223
Signed-off-by: Jaroslav Kysela <perex@perex.cz>
2023-08-30 18:48:23 +02:00
..
aconnect.1 aconnect: Add UMP support 2023-06-06 15:44:57 +02:00
aconnect.c reshuffle included files to include config.h as first 2023-08-30 18:48:23 +02:00
Makefile.am Makefiles - use AM_CPPFLAGS instead INCLUDES 2014-05-07 10:55:59 +02: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.