> - the system needs every period to be the same size (unless you are not > running in real-time or the remote load is *very* low, but then what > is the point?).
thats potentially a bit ugly, but in practice, its probably going to work, especially with JACK-driven clients/hosts. > - The system adds to the latency the equivalent of a single period. That > is, if your period size is 2ms for a total input-to-output latency of > 4ms, the system adds another 2ms to the latency, so total latency goes > to 6ms. does the metaplugin have a control output port called "latency"? this is an unofficial "standard" that swh (and perhaps the tap) plugins use to communicate latency to a host. it would allow ardour to keep tracks in sync that use this kind of processing. >If jack udp transport doesn't work adequately (haven't tested it), I >intend to adapt the code to work on top of jack too (should be reasonably >easy). jack.rtp is probably a better candidate :) it all sounds very interesting. --p