diff options
author | Alexandre Ratchov <ratchov@cvs.openbsd.org> | 2009-07-25 08:44:28 +0000 |
---|---|---|
committer | Alexandre Ratchov <ratchov@cvs.openbsd.org> | 2009-07-25 08:44:28 +0000 |
commit | 0844fac57a53bca70c73354af3517b8bea149328 (patch) | |
tree | 38194a88aaef0f05f48c3bc6df1dec993ead1163 /share | |
parent | 8c4eca591954bdaedc99cf39f7f3f83fdc5ae579 (diff) |
Currently midi capable programs can control midi hardware, but
cannot cooperate with other programs. The aim of this change is
to allow any program to send midi data to other programs as they
were midi hardware. For instance, this change should solve the
longstanding problem of using a midi sequencer with software
synthesizers. More precisely:
- new midicat(1) utility (actually hardlink to aucat(1)).
it creates software midi thru boxes, allowing programs
to send midi messages to other programs as they were
midi(4) hardware.
- new midi api in libsndio (see mio_open(3)), to access
midi(4) devices and midicat(1) sockets in a uniform way.
- new device naming scheme <service>:<unit>[.<option>],
common to audio and midi.
- new sndio(7) manual describing concepts and naming
The current audio device naming still works, but people having
scripts or configuration files containing device names could read
the sndio(7) man page and slowly start updating device names.
discussed with jakemsr@ and deraadt@, help form jmc@
Diffstat (limited to 'share')
0 files changed, 0 insertions, 0 deletions