| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
as NULL has. This will (hopefully) simplify ports where the user
passes the device string.
|
|
|
|
| |
suggested by deraadt@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
single aucat instance to handle all audio and MIDI services. Since
this partially breaks compatibility, this is a opportunitiy to fix few
other design mistakes (eg ':' being used by inet6, type name vs api
name confusion, etc..). This leads to the following names:
type[@hostname][,unit]/devnum[.option]
The device number is the minor device number for direct hardware
access (ie the 'N' in /dev/audioN). For aucat, this is the occurence
number of the -f (or -M) option.
There's a compatibility hook to keep old names working if only one
aucat server is running.
|
|
|
|
|
|
|
|
|
| |
with almost the same syntax (roughly an extra -M option).
Thru boxes are created with aucat, and corresponding MIDI port
names have the "aucat" prefix instead of "midithru". The old
device name will still work some time for backward compatibility.
ok deraadt
|
|
|
|
| |
device names
|
|
|
|
|
|
| |
with the server. As we're at it use the same protocol for midi and
audio. Now, both audio and midi code use the same SNDIO_DEBUG environment
variable to turn on/off DPRINTF's.
|
|
|
|
|
| |
them in files named mio_<backend>.c
No behaviour change.
|
| |
|
|
|
|
|
|
| |
realtime. For now only the playback volume of individual streams can be
changed/monitored. To each stream is assigned a MIDI channel; the volume
is changed/monitored using the standard controller number 7.
|
| |
|
|
|
|
| |
strings. suggested by Thomas Pfaff
|
|
|
|
| |
a midi device name starting with a separator
|
|
|
|
| |
from Thomas Pfaff
|
|
|
|
|
| |
with open(2) and write(2) syscalls.
from Thomas Pfaff, jakemsr is fine with it
|
|
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@
|