-summary : JACK is a professional sound server daemon
+summary : JACK2 low-latency audio server for multi-core machines.
description: |
- JACK is a professional sound server daemon that provides real-time,
- low-latency connections for both audio and MIDI data between applications
- that implement its API.
+ JACK2 is a C++ version of the JACK low-latency audio server for multi-core machines. It is a new implementation of the JACK server core features that aims at removing some limitations of the JACK1 design. The activation system has been changed for a data flow model and lock-free programming techniques for graph access have been used to have a more dynamic and robust system.
- <Summary xml:lang="en">JACK is a professional sound server daemon</Summary>
- <Description xml:lang="en">JACK is a professional sound server daemon that provides real-time,
-low-latency connections for both audio and MIDI data between applications
-that implement its API.
+ <Summary xml:lang="en">JACK2 low-latency audio server for multi-core machines.</Summary>
+ <Description xml:lang="en">JACK2 is a C++ version of the JACK low-latency audio server for multi-core machines. It is a new implementation of the JACK server core features that aims at removing some limitations of the JACK1 design. The activation system has been changed for a data flow model and lock-free programming techniques for graph access have been used to have a more dynamic and robust system.
- <Summary xml:lang="en">JACK is a professional sound server daemon</Summary>
- <Description xml:lang="en">JACK is a professional sound server daemon that provides real-time,
-low-latency connections for both audio and MIDI data between applications
-that implement its API.
+ <Summary xml:lang="en">JACK2 low-latency audio server for multi-core machines.</Summary>
+ <Description xml:lang="en">JACK2 is a C++ version of the JACK low-latency audio server for multi-core machines. It is a new implementation of the JACK server core features that aims at removing some limitations of the JACK1 design. The activation system has been changed for a data flow model and lock-free programming techniques for graph access have been used to have a more dynamic and robust system.
<Summary xml:lang="en">32-bit libraries for jack-audio-connection-kit</Summary>
- <Description xml:lang="en">JACK is a professional sound server daemon that provides real-time,
-low-latency connections for both audio and MIDI data between applications
-that implement its API.
+ <Description xml:lang="en">JACK2 is a C++ version of the JACK low-latency audio server for multi-core machines. It is a new implementation of the JACK server core features that aims at removing some limitations of the JACK1 design. The activation system has been changed for a data flow model and lock-free programming techniques for graph access have been used to have a more dynamic and robust system.
<Summary xml:lang="en">Development files for 32-bit jack-audio-connection-kit</Summary>
- <Description xml:lang="en">JACK is a professional sound server daemon that provides real-time,
-low-latency connections for both audio and MIDI data between applications
-that implement its API.
+ <Description xml:lang="en">JACK2 is a C++ version of the JACK low-latency audio server for multi-core machines. It is a new implementation of the JACK server core features that aims at removing some limitations of the JACK1 design. The activation system has been changed for a data flow model and lock-free programming techniques for graph access have been used to have a more dynamic and robust system.
<Summary xml:lang="en">Development files for jack-audio-connection-kit</Summary>
- <Description xml:lang="en">JACK is a professional sound server daemon that provides real-time,
-low-latency connections for both audio and MIDI data between applications
-that implement its API.
+ <Description xml:lang="en">JACK2 is a C++ version of the JACK low-latency audio server for multi-core machines. It is a new implementation of the JACK server core features that aims at removing some limitations of the JACK1 design. The activation system has been changed for a data flow model and lock-free programming techniques for graph access have been used to have a more dynamic and robust system.