| | 13 | |
| | 14 | = Download = |
| | 15 | The tarballs are available at the usual location: |
| | 16 | |
| | 17 | * http://ladish.org/download/ |
| | 18 | * http://ladish.org/download/ladish-1-with-deps.tar.bz2 |
| | 19 | * http://ladish.org/download/ladish-1-with-deps.tar.bz2.sig |
| | 20 | * http://ladish.org/download/ladish-1.tar.bz2 |
| | 21 | * http://ladish.org/download/ladish-1.tar.bz2.sig |
| | 22 | |
| | 23 | There are two tarballs. ladish-1-with-deps.tar.bz2 is XXXXXXXXXXXXXXXXXXX MiB and |
| | 24 | bundles the major dependencies that are usually needed for running |
| | 25 | ladish: |
| | 26 | * flowcanvas |
| | 27 | * LADI Tools |
| | 28 | * a2jmidid |
| | 29 | * jack2 |
| | 30 | |
| | 31 | All of these are either development (git/svn) versions or release |
| | 32 | versions that are patched to work better with ladish. The last released |
| | 33 | versions of these dependencies are expected work with ladish. The most |
| | 34 | serious "incompatibility" is that the jack2 mainline is missing the |
| | 35 | no-self-connect changeset. This changeset adds option to jack that |
| | 36 | allows prevention of jack apps self connection to "hardware" ports |
| | 37 | (usually system:playback_N). As such self-connecting apps are not rare |
| | 38 | at all, without it, the studio/room separation is not-effective and |
| | 39 | the workflow can get very confusing. |
| | 40 | |
| | 41 | If you are compiling the software by yourself, then you should |
| | 42 | probably use this "fat" tarball. |
| | 43 | |
| | 44 | The ladish-1.tar.bz2 tarball is XXXXXXXXXXXXXXXXX KiB and contains only ladish |
| | 45 | itself. It is expected to be used mainly by packagers. |
