>> > www.ladspa.org/ladmea/ >> >> but ladmea, like jack, is designed with a general assumption that >> synchronous execution is possible. the issue that VST Link solves is >[...] > >Hmm, not so - LADMEA is designed very much with asynchronous operation in >mind (the clock and latency requirement stuff for instance). It's designed >to handle LAN or even WAN multimedia. Whether or not operation is >synchronous is up to the actual exchange implementation. If JACK was >modified to be a LADMEA exchange this would be synchronous - but this isn't >the only option.
oh that's right - LADMEA was one of those designs in which the entire graph can be stalled by a single way-upstream "producer" node being delayed. am i remembering this right? >And the nice thing is that (hopefully!) a tolerant client written using JACK >but talking to it through LADMEA would be able to use an asynchronous >exchange without any code change. JACK clients don't know that they are executed synchronously. They only know that they register 0-3 callbacks (with 1 or 2 more possible), and those they register (if any) will be called in a dedicated thread "at the appropriate time". They have no clue about the context in which they execute except that everything that should be set up a certain way during the callback execution definitely is. --p
