some markdown fixes: table and local links
This commit is contained in:
Robin Gareus
parent
d64fafd349
commit
d8c76eebb7
|
|
@ -10,18 +10,19 @@ _Are we going to have two JACKs forever?_ No. However nobody forsees a sane wa
|
|||
|
||||
Here is a feature listing/comparison of the different jack implementations. Note that this list does not include tschack, Torben Hohn's experimental branch of Jack 1.
|
||||
|
||||
|| *Feature_' || '''Jack 1''' || '_Jack 2* ||
|
||||
|| Implements the JACK C API || Yes || Yes ||
|
||||
|| Supports multiple processors (SMP) || No || Yes(1) ||
|
||||
|| Allows apps to connect/disconnect without disrupting audio || No || Yes ||
|
||||
|| Has (optional) DBUS support(2) || No(6) || Yes ||
|
||||
|| Can be used with [wiki:WalkThrough/Dev/NetOne netjack1] || Yes || Yes ||
|
||||
|| Can be used with [wiki:WalkThrough/User/NetJack2 netjack2] || No || Yes ||
|
||||
|| Is under active development || Yes || Yes ||
|
||||
|| Supports Linux/*nix/POSIX OS's || Yes || Yes ||
|
||||
|| Supports OS X || Yes || Yes(4) ||
|
||||
|| Supports Windows || No || Yes(5) ||
|
||||
|| Supports Solaris/OpenSolaris || Yes? || Yes ||
|
||||
| *Feature_' | '''Jack 1''' | '_Jack 2* |
|
||||
|------------------------------------------------------------|:------------:|:----------:|
|
||||
| Implements the JACK C API | Yes | Yes |
|
||||
| Supports multiple processors (SMP) | No | Yes(1) |
|
||||
| Allows apps to connect/disconnect without disrupting audio | No | Yes |
|
||||
| Has (optional) DBUS support(2) | No(6) | Yes |
|
||||
| Can be used with [[WalkThrough_Dev_NetOne netjack1]] | Yes | Yes |
|
||||
| Can be used with [[WalkThrough_User_NetJack2 netjack2]] | No | Yes |
|
||||
| Is under active development | Yes | Yes |
|
||||
| Supports Linux/*nix/POSIX OS's | Yes | Yes |
|
||||
| Supports OS X | Yes | Yes(4) |
|
||||
| Supports Windows | No | Yes(5) |
|
||||
| Supports Solaris/OpenSolaris | Yes? | Yes |
|
||||
|
||||
(1) Jack2 can run in 2 different modes : "asynchronous" when the server does not wait for graph end for a given cycle but just write the outputs computed at the previous cycle. In this case an extra period of latency is added. Jack 2 can also be run in "synchronous" mode, when the server waits for the graph activation end in a given cycle, in which case it works like Jack 1.[[BR]]
|
||||
(2) DBUS support helps in integrating with [PulseAudio](http://www.pulseaudio.org/) and [LADI](http://ladish.org/wiki/ladi) .[[BR]]
|
||||
|
|
@ -37,4 +38,4 @@ Other differences that don't lend themselves to feature tables:
|
|||
* Jack 1 uses less RAM than Jack 2.
|
||||
* SMP support is not always as valuable as you would think. If your applications are chained INPUT --> A --> B --> C --> OUTPUT, then it will _not_ be able to utilize multiple processors. However, if you applications are independently generating audio to the OUTPUT, that is when "parallel" sub-graph exist in the global graph, then they can be.
|
||||
* Jack 2 allocates 2 threads on the client side, one for real-time computation (the one that calls the "Process" callback) and one to handle all non real-time notifications (server context changes). Jack 1 only use 1 thread for real-time computation and notification handling.
|
||||
* Jack 2 has a master/slave back-end model. This design allows you to, for instance, load MIDI backends along with a master backend which can be audio or network: like "jackd -X coremidi -d coreaudio" jackd -X coremidi -d net" on OSX, or "jackd -X winmme -d portaudio" , "jackd -X winmme -d net" on Windows.
|
||||
* Jack 2 has a master/slave back-end model. This design allows you to, for instance, load MIDI backends along with a master backend which can be audio or network: like "jackd -X coremidi -d coreaudio" jackd -X coremidi -d net" on OSX, or "jackd -X winmme -d portaudio" , "jackd -X winmme -d net" on Windows.
|
||||
|
|
|
|||
|
|
@ -259,4 +259,4 @@ now we must make sure that the -U <uuid> option specifies this parameter to jack
|
|||
|
||||
|
||||
|
||||
see also: [wiki:WalkThrough/User/jack_session]
|
||||
see also: [[WalkThrough_User_jack_session]]
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ It now even supports lossy compression, so its possible to use it over internet.
|
|||
|
||||
## Basic terminology used in this document
|
||||
JACK::
|
||||
If you're stuck there, I suggest you read WalkThrough/User/GettingStarted first :-)
|
||||
If you're stuck there, I suggest you read [[WalkThrough_User_GettingStarted]] first :-)
|
||||
|
||||
NetJack::
|
||||
It is the generic name used for the functionality covered in this document.
|
||||
|
|
|
|||
|
|
@ -182,7 +182,7 @@ If you need, for particulary reasons to set another Multicast address or UDP Por
|
|||
jack_load netmanager -i "-a xxx.xxx.xxx.xxx -p port"
|
||||
|
||||
|
||||
Alternatively, internal clients can be configurated and loaded using the jack server DBUS service, when Jack2 has been compiled with DBUS support (see http://trac.jackaudio.org/wiki/WalkThrough/User/jack_control).
|
||||
Alternatively, internal clients can be configurated and loaded using the jack server DBUS service, when Jack2 has been compiled with DBUS support (see [[WalkThrough_User_jack_control]]).
|
||||
|
||||
You have to be careful because NetJack doesn't check if the Multicast IP or the UDP Port is correct. So if you have some network error (typically 'Can't bind multicast address : Invalid Argument' or something else), first check if it's a valid multicast address and an authorized free port.
|
||||
|
||||
|
|
@ -285,7 +285,7 @@ to print possible parameters for the audioadapter component (will be printed on
|
|||
|
||||
to load the audioadapter with 4 input/output JACK ports.
|
||||
|
||||
Alternatively, internal clients can be configurated and loaded using the jack server DBUS service, when Jack2 has been compiled with DBUS support (see http://trac.jackaudio.org/wiki/WalkThrough/User/jack_control).
|
||||
Alternatively, internal clients can be configurated and loaded using the jack server DBUS service, when Jack2 has been compiled with DBUS support (see [[WalkThrough_User_jack_control]]).
|
||||
|
||||
----
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ then start `jacksmtray`
|
|||
you might want to look at this screencast:
|
||||
http://hochstrom.endofinternet.org/files/pyjacksm-cast01.ogv
|
||||
|
||||
a developer walk through is available at WalkThrough/Dev/JackSession.
|
||||
a developer walk through is available at [[WalkThrough_Dev_JackSession]].
|
||||
|
||||
# apps supporting jack-session
|
||||
|
||||
|
|
@ -38,4 +38,4 @@ a developer walk through is available at WalkThrough/Dev/JackSession.
|
|||
* *bristol* is reported to have jack-session support too
|
||||
* *connie* http://bitbucket.org/horo/connie
|
||||
* *lv2_jack_host* svn http://drobilla.net/software/slv2
|
||||
* *ingen* svn http://drobilla.net/software/ingen
|
||||
* *ingen* svn http://drobilla.net/software/ingen
|
||||
|
|
|
|||
Loading…
Reference in New Issue