- +

DESIGN GOALS

• Jack should allow streaming of low-latency, high-bandwidth data between independent applications.
• Although not a requirement, Jack should support any streaming data type, not just audio.
• In an active Jack setup, there will be one server and one or more Jack plugins. It will be possible to run multiple Jack servers, but each server will form an independent Jack setup. Jack will not define any interfaces between Jack servers.
• Applications connected using Jack may have their own graphical interfaces. Jack will not make any specifications as to different GUI toolkits or libraries. As a consequence of this requirement, different parts of a running Jack setup may be spread across multiple processes.
• Jack should provide full, sample accurate synchronation (ie. totally synchronous execution of all client plugins)
• To represent audio data, Jack should use 32 bit IEEE floats, normalized to value range [-1,1].
• Only noninterleaved audio streams will be supported.

more ...