Bug#317142: RFP: dssi-dev -- DSSI (pronounced "dizzy") is an API for audio plugins, with particular application for software synthesis plugins with native user interfaces
Package: wnpp
Severity: wishlist
Debian's rosegarden4 1.0 package is built with no DSSI support, which has been
a great source of consternation and confusion to Rosegarden's users who run
Debian. We at Rosegarden are preparing to release version 1.2, and we really
hope that our new release will be made available to Debian users with synth
plugin support available. In order for that to be likely, first Debian needs
to package DSSI, so the Rosegarden package maintainer can build against the
API.
The dssi package includes the API, which should probably be a
dssi-dev package, and will serve only as a build-dep for applications like
Rosegarden at compile time. It also includes some example hosts and example
plugins, all end-user runtime files, which should probably be a separate
dssi-examples or dssi-plugins package (or perhaps two packages, one each of
dssi-example-hosts and dssi-plugins.)
There are also three more refined end-user plugins available from DSSI, called
fluidsynth-dssi, xsynth-dssi and hexter. These should be packaged too. I
elected to mention them in this report rather than creating separate WNPPs for
each of them because I thought that would be less obnoxious than flooding the
database with individual requests. Forgive me if this was a bad choice.
Thanks for picking this up.
* Package name : dssi-dev
Version : 0.9
Upstream Author : Sean Bolton <smbolton@jps.net>
* URL : http://dssi.sourceforge.net
* License : GPL
Description : DSSI (pronounced "dizzy") is an API for audio plugins, with particular application for software synthesis plugins with native user interfaces
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.25-1-multimedia-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Reply to: