JACK Audio Connection Kit



Have you ever wanted to take the audio output of one piece of software and send it to another? How about taking the output of that same program and send it to two others, then record the result in the first program? Or maybe you're a programmer who writes real-time audio and music applications and who is looking for a cross-platform API that enables not only device sharing but also inter-application audio routing, and is incredibly easy to learn and use? If so, JACK may be what you've been looking for.

 

JACK has been around for a long time, but it's useful to remind those who don't know about it

 

Is there any latency?

 

Does using JACK add latency?
There is NO extra latency caused by using JACK for audio input and output. When we say none, we mean absolutely zero. The only impact of using JACK is a slight increase in the amount of work done by the CPU to process a given chunk of audio, which means that in theory you could not get 100% of the processing power that you might get it if your application(s) used ALSA or CoreAudio directly. However, given that the difference is less than 1%, and that your system will be unstable before you get close to 80% of the theoretical processing power, the effect is completely disregardable.​

Source
http://jackaudio.org/faq/no_extra_latency.html

For More answers
http://jackaudio.org/faq/​

 

Last edited: Sep 27, 2015

I been telling people about Jack Audio for years..........better than Asio4All!