History log of /openbsd/lib/libsndio/mio_open.3 (Results 1 – 18 of 18)
Revision Date Author Comments
# 18bc0c2f 18-Dec-2018 jmc <jmc@openbsd.org>

"a" MIDI, not "an";


# f273b081 17-Oct-2017 schwarze <schwarze@openbsd.org>

add missing HISTORY; based on CVS logs and release announcements


# 3f2e611a 07-Jan-2016 ratchov <ratchov@openbsd.org>

Move sndiod man page to section 8.

suggested by deraadt, fixes from jmc, ok millert


# 5dfee228 14-Sep-2015 schwarze <schwarze@openbsd.org>

Remove useless quoting from .Fo and .Fn function names, to prevent
development of a cargo cult in case people look at existing files
for examples. This achieves a consistent .Fo and .Fn quoting styl

Remove useless quoting from .Fo and .Fn function names, to prevent
development of a cargo cult in case people look at existing files
for examples. This achieves a consistent .Fo and .Fn quoting style
across the whole tree.

show more ...


# 0064b033 05-Mar-2014 ratchov <ratchov@openbsd.org>

say this is the "sndio" api, as we have other audio/midi apis,
makes "man -k" happier.

ok jmc, schwarze


# eeb374f4 04-Jul-2013 ratchov <ratchov@openbsd.org>

remove FILES sections because it's incomplete, wrong and doesn't give
any useful information


# 86f9d4cd 05-Jun-2013 tedu <tedu@openbsd.org>

use fancy .In macro for includes. from Jan Klemkow. ok jmc schwarze


# 091bf160 06-Apr-2013 ratchov <ratchov@openbsd.org>

explain what "default" means in sndio.7 rather than {sio,mio}_open.3,
with tweaks from jmc


# f7e031c0 15-Sep-2012 stsp <stsp@openbsd.org>

Improve instructions for handling non-blocking I/O with poll(2) and
the mio_* functions. As per suggestion from jmc tidy up spacing in
RETURN VALUES section and Xr poll(2). ok jmc ratchov


# 57838383 14-Sep-2012 stsp <stsp@openbsd.org>

Have mio_open(3) document all return values in the RETURN VALUES section.
And don't document the return value of mio_pollfd() twice, one instance
of which was incorrect. ok jmc, ratchov


# 9f9aa69f 23-May-2012 ratchov <ratchov@openbsd.org>

Make the "default" string a valid device name that has the same effect
as NULL has. This will (hopefully) simplify ports where the user
passes the device string.


# 7207b069 11-Apr-2012 ratchov <ratchov@openbsd.org>

Use "unsigned int" rather than "unsigned". No object change.
suggested by deraadt@


# d351df76 09-Dec-2011 ratchov <ratchov@openbsd.org>

mention sndiod rather than aucat when talking about the server


# 8825335a 17-Oct-2011 ratchov <ratchov@openbsd.org>

Remove midicat since aucat can now be used instead of midicat
with almost the same syntax (roughly an extra -M option).
Thru boxes are created with aucat, and corresponding MIDI port
names have the "

Remove midicat since aucat can now be used instead of midicat
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

show more ...


# 82bfc72b 16-Apr-2011 ratchov <ratchov@openbsd.org>

Make aucat audio and midi backends share the same code to communicate
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

Make aucat audio and midi backends share the same code to communicate
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.

show more ...


# 85e7b1fe 26-Jul-2009 ratchov <ratchov@openbsd.org>

rephrase description of (MIO_IN | MIO_OUT) mode
from Thomas Pfaff, ok jmc@


# 4c244198 25-Jul-2009 ratchov <ratchov@openbsd.org>

use const qualifier in libsndio, making it slightly more consistent
with open(2) and write(2) syscalls.
from Thomas Pfaff, jakemsr is fine with it


# 6efede29 25-Jul-2009 ratchov <ratchov@openbsd.org>

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 m

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@

show more ...