Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

[092325]: README Maximize Restore History

Download this file

README    129 lines (89 with data), 4.4 kB

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128

DSSI
----

This is the Disposable Soft Synth Interface specification & example
code repository.

You'll find here:

  doc/RFC.txt -- proposed DSSI specification -- read this first

  dssi/dssi.h -- DSSI header file -- the comments define those parts
  of the spec dealing with host/plugin interaction (not covered in RFC)

  dssi-jack-host/dssi-jack-host.c -- a simple JACK/ALSA-sequencer plugin host

  examples/dssi_osc_send.c
  examples/dssi_osc_update.c -- simple DSSI OSC test programs

  examples/trivial_synth.c -- a quite useless but fairly clear
  illustrative synth plugin

  examples/less_trivial_synth.c -- a synth that actually does some
  basic synthesis

  examples/less_trivial_synth_qt_gui.cpp -- a very simple Qt GUI
  for the above

  fluidsynth-dssi/ -- an example DSSI implementation of FluidSynth,
  with a GTK+ GUI


Requirements
------------

To build the example code you will need:

  ALSA 0.9/1.0.x
  JACK
  LADSPA
  liblo-0.9 or above: http://www.plugin.org.uk/liblo/
  pkgconfig with PKG_CONFIG_PATH set appropriately to pick up liblo

To build the less_trivial_synth Qt GUI, you will need:

  Qt 3

To build the fluidsynth-dssi plugin and GUI, you will need:

  FluidSynth 1.0.3 or newer (libraries, headers, and source code)
  GTK+ 1.2.x

Build
-----

Run "make" from the top-level directory.  There is no configure script.

You will need to ensure PKG_CONFIG_PATH is set correctly to locate the
liblo.pc pkgconfig file.  You may also need to set the QTDIR and/or
QTINCDIR variables, and FLUID for the location of the Fluidsynth
sources if you want to build fluidsynth-dssi.  (FLUID should not be a
relative path, and you _must_ build against the same version of
fluidsynth as you have the library for installed.)

For example, to build on Debian with my local fluidsynth source
installation I use

  FLUID=`pwd`/../fluidsynth-1.0.4-2 QTDIR=/usr QTINCDIR=/usr/include/qt3 make

After compiling, optionally test the host and example plugins (see
below) and then run "make install" from the top-level directory to
install the dssi header, dssi.pc pkgconfig file, and the host and
examples.  The default install prefix is /usr/local.

Test
----

Make sure JACK is running, cd to ./examples and run:

  $ export DSSI_PATH=`pwd`
  $ ../jack-dssi-host/jack-dssi-host less_trivial_synth.so

A synth GUI should pop up, with an ALSA sequencer input and JACK
output (connected by default to the first alsa_pcm out).  If you
connect a MIDI keyboard (or vkeybd) to its ALSA MIDI input, you should
be able to play it and use MIDI controllers to adjust its parameters:
MIDI CC1 (the modulation wheel) controls timbre, and controllers 72,
73, 75 and 79 control release, attack, decay and sustain respectively
(some keyboards already have controls set up for these values).

What has actually happened (if it worked) is that the host has
been started, has loaded the first synth plugin (labelled LTS) found
in the given .so file, has located the GUI executable that the make
procedure installed into examples/less_trivial_synth/LTS_qt,
instantiated the plugin, started the GUI and is now managing the MIDI
input from ALSA, control changes from the GUI and audio out to JACK.

You may also run multiple synth instances simultaneously with this
host.  If you have built both the examples and FluidSynth-DSSI, and
installed them to /usr/local, you may run:

  $ export DSSI_PATH=/usr/local/lib/dssi
  $ export PATH=$PATH:/usr/local/bin     # if it's not there already
  $ jack-dssi-host -2 less_trivial_synth.so -3 fluidsynth-dssi.so

This will create two less_trivial_synth instances and three
FluidSynth-DSSI instances.  Note that the instances are assigned
consecutive MIDI channels, and their outputs are spread across all
of the available JACK physical outputs.

Licensing
---------

The DSSI API itself (dssi.h) is licensed under the GNU Lesser General
Public License.  See COPYING for details.

The jack-dssi-host is provided under a BSD-style license.  This means
you can do anything you want with it so long as you retain the
copyright attribution and license information.  See the source files
for details.

FluidSynth-DSSI is provided under the GNU General Public License.  See
fluidsynth-dssi/COPYING for details.

Licensing for the files in the examples directory may vary: please
check the individual files for details.  Most of them are in the
public domain, which means you can use them for anything you want.