MIDIDEVICE(N) LOCAL MIDIDEVICE(N)NAME
mididevice — tclmidi command to create a MIDI device and modify the con‐
figuration
SYNOPSIS
mididevice DeviceName [midithru value] [slave MasterDevID]
[channel_on ChannelList] [channel_off ChannelList]
mididevice DevID [close] [midithru [value]] [slave MasterDevID]
[channel_on [ChannelList]] [channel_off [ChannelList]]
mididevice
DESCRIPTION
mididevice is a tclmidi(1) command that creates a MIDI device and allows
you to modify the configuration of an existing device if tclmidi was
built with device support. A device driver for some MIDI interfaces is
included with this release for the following architectures:
BSD/OS
Linux
FreeBSD
SVR4
The first form of mididevice is used when the device is created for the
first time. The second form is used once the device has been created.
The first parameter is the device identifier. In the first case, it
should be a path name for the device. Something like, /dev/midi0. In
the second form it is a device identifier returned from a call to the
first form. In the third form, mididevice returns a “1” or “0”. A “1”
is returned if tclmidi was built with MIDI device support and a “0” is
returned if it does not have device support.
The remaining arguments are parameters or commands that can be used to
query or modify the device configuration.
close This command can only be used once a device has been created
by the first form of this command. It closes the device.
Once the device has been closed, it cannot be used again
until it is reopened by a call to the first form of the
mididevice command.
midithru Without a value, this command returns the status of
midithru. It will return “on” if midithru is enabled, and
“off” if it is disabled. If a value is specified is should
be a boolean value from one of, “on”, “yes”, “1”, “off”,
“no” or “0”. The device will be conigured to the specified
value.
slave This command allows the device to be made a slave to
another. When a device is a slave, it will be synchronized
to the master. It will not begin playing until the master
device does and will stay in time with the master. Each
device can only have one master, but a master device can
have any number of slaves. The MasterDevID is the device ID
of the master device as returned from a call to the first
form of mididevice. The slave feature is useful if you want
to play a MIDI song that has more than 16 channels, and you
have multiple hardware MIDI interfaces.
channel_on Without an argument, this command returns the current list
of all channels that are active. With an argument, it will
add a list of channels to the current active list. The
active list is a list off all channels that will receive
events. If a channel is inactive, any events on it will be
masked. By default, all channels are active.
channel_off This is similar to the channel_on option, but returns a list
off all channels that are inactive. If an argument is spec‐
ified, it will remove a list of channels from the current
active list.
RETURN VALUES
In the first form, mididevice returns a device ID that can be used in
later calls to mididevice or calls to other functions that deal with the
MIDI interface. In the second form it returns values according to the
options specified. See the list above for details. In the third case,
mididevice returns a “1” or “0” depending if tclmidi was built with
device support or not.
SEE ALSOtclmidi(1), midifeature(n), midiplay(n), midirecord(n), midistop(n),
midiwait(n)AUTHOR
Mike Durian - durian@boogie.com
BSD July 11, 1994 BSD
