do we really need another incompatible jackd? i would like to connect pd with other audio applications, but as you said, it's not possible to connect a jack enabled application to k_jack~. also pd is not an audio server... it's the application which should connect to jackd and not implement a jack like system?
how could i connect alsaplayer (jack enabled) to k_jack~? what modifications to the alsaplayer source code / makefile are needed?
Kjetil S. Matheussen wrote:
k_jack V0.0.0.5 ALPHA - EXPERIMENTAL
ABOUT
k_jack currently consists of k_jackd~, libk_jack and libaipc.
k_jackd~ is a jack server external for pure-data.
libk_jack is (supposed to be) a (somewhat) libjack compatible library.
Jack applications that want to contact k_jackd~ instead of jackd must (somehow) be linked with libk_jack and libaipc instead of libjack.
k_jackd~ does not speak with libjack, and jackd does not speak with libk_jack.
libaipc is a library for audio interprocess communication, based on code from the vstserver. A preview version is included with this version of k_jack. (API is not settled.)
By using libaipc for interprocess communication, and letting PD take care of various low/mid/high-level audio-stuff, only a few hundred lines of code is currently used for this implementation of a simple jack system.
k_jackd~ and libk_jack are not based on the jack sourcecode found at jackit.sf.net, except for protos in the header files.