Plus considering that midi over jack is being
implemented too you would
have both midi and audio over ethernet
through jack, available to any jack client without the application
needing to be changed.
That would be convenient, yes. But at the implementation
level there is
quite a bit of difference between MIDI traffic and audio traffic. MIDI
is much less forgiving of errors, or much more if you know which errors
to make. You can do a lot of smart things when doing MIDI over a network
that you can't do with audio, a la MWPP or whatever it's called now.
That said, if you've got the bandwidth and latency issues worked out for
audio, MIDI should be a piece of cake and you may not need to worry
about the smart things you can do with it.
FWIW, I've implemented basic MIDI over TCP/IP at [1], which is loosely
based on MWPP and needs some TLC, but already outperforms aseqnet.
1.
http://hans.fugal.net/music/nmidi-0.1.0.tar.gz
--
.O. Hans Fugal | De gustibus non disputandum est.
..O
http://hans.fugal.net | Debian, vim, mutt, ruby, text, gpg
OOO | WindowMaker, gaim, UTF-8, RISC, JS Bach
---------------------------------------------------------------------
GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460