Software

Pd-L2Ork K12 Module
The fastest way to get a working L2Ork-compatible software setup is to:

  1. install “Burrito Supreme” version of Pd-L2Ork
  2. install L2Ork Compositions & Abstractions

The “Burrito Supreme” installer will provide you with all components necessary to have a setup equivalent to that of Pd-extended. The L2Ork abstractions are necessary only if you want to create/perform pieces specific to the L2Ork ensemble setup. These are not necessary for running the K12 module.

The instructions and download links for each of these steps are provided below.

IMPORTANT! Binary releases of Pd-L2Ork are currently provided primarily as a deb package. If you are installing a deb file and find specific dependencies not satisfied, please contact us to report such inconsistencies. If you are looking to compile your own version of pd-l2ork or wish to use a script-based tarball installer and want to make sure you have all the necessary libraries Pd-L2Ork relies on, the easiest thing is to copy and paste the following apt-get code (please note the following package names have been tested with Ubuntu; other distributions’ package names may vary):

sudo apt-get install bison flex automake qjackctl tcl-dev tk-dev libasound2-dev libjack-jackd2-dev libtool libbluetooth-dev libgl1-mesa-dev libglu1-mesa-dev libglew-dev libmagick++-dev libftgl-dev libgmerlin-dev libgmerlin-avdec-dev libavifile-0.7-dev libmpeg3-dev libquicktime-dev libv4l-dev libraw1394-dev libdc1394-22-dev libfftw3-dev libvorbis-dev ladspa-sdk dssi-dev tap-plugins ladspa-foo-plugins invada-studio-plugins-ladspa blepvco swh-plugins mcp-plugins cmt blop slv2-jack omins ubuntustudio-audio-plugins rev-plugins libslv2-dev dssi-utils vco-plugins wah-plugins fil-plugins mda-lv2 libmp3lame-dev libspeex-dev libgsl0-dev portaudio19-dev python-dev libsmpeg0 libjpeg62 tkpng flite1-dev libgsm1-dev libfftw3-dev libgtk2.0-dev subversion git libstk0-dev libsndobj-dev libfluidsynth-dev x-ttcidfont-conf defoma tclxapian

The said code will install the necessary libraries and their supporting dev components. This will enable you not only to run the software but also build it from the source, should that prove necessary. Having dev libraries installed should have no negative impact on your system beyond taking up a bit more of the HD space than the libraries alone.

Download Pd-L2Ork

Complete (a.k.a. ‘Burrito Supreme’) Installer

Source Code

  • Source tree snapshot on Pd-L2Ork Git
    • Entire pd-l2ork source with latest changes
    • Does not include L2Ork-specific abstractions
    • Install instructions for devs
    • USE THIS TO:
      • If you are using a Linux distribution that does not run prebuilt binary version
      • compile pd-l2ork from source or contribute to the development

Individual Externals

Changelog

L2Ork Compositions & Abstractions

  • PD-L2Ork Compositions & Abstractions1 (temporarily down)
    • Necessary for opening L2Ork patches
    • Provides core infrastructure for UI, streamlined implementation of core DSP techniques, networking, and input device data analysis
    • Also includes a snapshot of the RjDj Library
    • USE THIS TO:
      • gain access to various useful abstractions commonly used inside L2Ork-specific patches
      • ensure 100% compatibility with L2Ork environment

1 These are continually evolving, so please make sure to communicate questions/concerns on the L2Ork-Dev mailing list.

Install Instructions

IMPORTANT! All Pd-l2Ork installer tarballs use unique identifiers/paths, so they should coexist happily next to other installs of Pd. This, however, also means that they may not be able to find externals belonging to other preexisting Pd installs and that is a good thing since Pd-l2Ork changes some of the files externals may rely upon and as such mixing Pd-l2Ork with externals from other Pd iterations may result in unexpected crashes and instabilities. Therefore, to ensure maximum stability please couple Pd-L2Ork only with externals provided on this page or recompile your own making sure you are referencing appropriate source files.

As of September 2014, Pd-L2Ork deb installer conflicts only with the cyclist package that is an optional package for Pd-extended, and the deb installer should warn you of these conflicts prior to installing. Since cyclists is an optional package and pd-l2ork provides identical binary in the same location, removing the cyclist package will ensure that you can seamlessly run Pd-L2Ork and other Pd flavors on the same machine.

Deb installer (recommended)

This is by far the easiest way to install Pd-L2Ork. To install deb version, simply double-click on the downloaded deb file or type the following command in the terminal from the folder where the downloaded deb file is located:

sudo dpkg -i pd-l2ork*deb

This will install all the supporting libraries, warn you of any conflicts with other packages (e.g. pd-utils), as well as set up pd-l2ork on your machine.

If you encounter errors due to missing packages, this is most likely because you did not install supporting libraries listed at the top of this page. You can, however, correct this easily by running the following command:

sudo apt-get -f install

If everything goes well, you will be presented with an option of installing a collection of packages. Please review that you are ok with installing/removing suggested packages and if so, press “Y” to continue. Once this process is complete, pd-l2ork should be installed and ready for use.

Script-Based Installer (for custom installs)

Script-based installer provides precompiled binaries that are by default installed in /usr/local folder. If you need to recompile your own version see the Compiling Pd-L2Ork from Source section below instead. To install, unzip the tarball and simply run the install script.

tar -jxf pd*.tar.bz2
cd pd*
sudo make install

This will install everything with the /usr/local prefix.

Running Pd-L2Ork

Once install process is complete, to run Pd-l2ork simply type:

pd-l2ork
Please note that running pd-l2ork with no start-up flags will provide you with default (conservative) settings which will likely result in poor audio performance. For optimal perfomance you will ideally need a lowlatency kernel, an audio group with real-time privileges, using JACK audio server, and running pd-l2ork with -rt flag. The easiest way to achieve this is to:

        1. Use qjackctl to configure and start JACK server with real-time privileges
        2. Start pd-l2ork (or pd-l2ork-k12) using the shortcut from the application menu
If you are using Ubuntu Unity and have the shortcut in the Ubuntu Launcher, right-clicking on the shortcut will provide you with additional options.

Compiling Pd-L2Ork from Source

IMPORTANT! Compiling is typically not for the faint of heart. Pd-L2Ork, however, tries to make this a relatively simple 3-step process. First you will need to make sure to install all the dev packages (or their counterparts in your respective Linux distribution) listed at the top of this page. Once ready, click on the arrow below for the step-by-step instructions.

Introduction

The easiest way to create your own installer tarball or deb package containing pd-l2ork and all supporting 3rd party externals is to simply download the latest snapshot from the git repository. When retrieving the source for the first time, in a new empty folder type:

git clone git://github.com/pd-l2ork/pd.git pd-l2ork

Alternately, if you simply need to update your local snapshot with the latest changes, go into the root git directory (if you used the command above, it will be the pd-l2ork folder) and type:

git stash
git pull

Once you have the latest version of the source, simply compile using l2ork’s nifty tar_em_up.sh script.

For other options available through the tar_em_up.sh install script, run the script without any flags, namely by typing:

./tar_em_up.sh

Creating Deb Installer

For compiling the deb installer (a.k.a. deb package) do the following:

cd pd-l2ork/l2ork_addons
./tar_em_up.sh -B

This will recompile entire source tree (including externals) using default “–enable-jack –enable-alsa –enable-fftw” Linux flags and create a “Burrito Supreme” deb in the folder where the original git folder was created containing the pd-l2ork/ folder. Once the tarball is created, to install it on your own computer, go back to the appropriate directory and install it using deb tools (e.g. gdebi, dpkg, etc.):

cd ../../
dpkg -i pd-l2ork--.deb

Creating Script-Based Installer

For script-based tarballs do the following:

cd pd-l2ork/l2ork_addons
./tar_em_up.sh -F

This will recompile entire source tree (including externals) using default “–enable-jack –enable-alsa –enable-fftw” flags and create a “Burrito Supreme” tarball in the folder where the original git snapshot was downloaded (the one containing the pd-l2ork/ folder). Once the tarball is created, to install it on your own computer, go back to the appropriate directory, decompress the tarball and run the installer using the same instructions as the “Burrito Supreme” installer:

cd ../../
tar -jxf pd-l2ork--.tar.bz2
cd pd*
sudo make install

Questions? Please contact us via the L2Ork-Dev public mailing list.

Share