nekobee 0.1.5 review

nekobee is a DSSI soft synth plugin that emulates the sound of the TB-303 Bassline. nekobee is not an exact copy; rather than make

License: GPL (GNU General Public License) File size: 552K Developer: Gordonjcp

0

nekobee is a DSSI soft synth plugin that emulates the sound of the TB-303 Bassline.

nekobee is not an exact copy; rather than make it "just like the real thing", the design concentrates on modelling the circuitry and was adjusted by comparing the sounds achievable with it to those heard on classic acid house tracks.

It includes a switchable square/saw wave VCO, 24dB/octave VCF, an adjustable decay time for the VCF, a fixed decay time for the VCA, and an interesting bit of circuitry around the "Accent" control.

Installation:

The simplest way to compile this package is:

1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute `configure' itself.

Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for.

2. Type `make' to compile the package.

3. Optionally, type `make check' to run any self-tests that come with the package.

4. Type `make install' to install the programs and any data files and documentation.

5. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. There is also a `make maintainer-clean' target, but that is intended mainly for the package's developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.

Requirements:
dssi

What's New in This Release:
The plugin now supports MIDI continuous controllers for adjusting the knobs.
The values used are documented in the README file.
At the moment the only way to change them is by editing the relevant bits of code.