I'm not
that familiar with jack internals, but writing a new jack driver
(like the firewire one, and oss one) would be a much, much better idea
than writing some alsa-over-network monstrosity for too many reasons to
list.
Err.. yeah I'd have to agree.
wrong model. a given jackd has a single driver. a new jack client,
sure.
and in fact, jlc and i have done some tentative experiments with
*live network audio* using jackd and ices w/jack support using only
our DSL connectivity. the model that ices uses is more or less
perfect, i think. just a client with some ports that happen to send
audio to the rest of the world. only the user knows that, other apps
just think its a regular client. jack doesn't care either, so everyone
who has a different idea of how to actually connect the endpoints can
do their own thing and everyone can coexist.
oh, and a small correction. VST System Link has basically nothing to
do with networked audio. its concerned with providing a common clock
and transport control across a network. it does *not* distribute audio
across the network at all.
--p
