screenshots

lissadron.png

description

A software synth for the norns platform making extensive use of seeded randomness.

Concept, sound engine and implementation by LFSaw.
You might also like haven.

If you like what I do, please also have a look at my bandcamp page.

lissadron-cover1.jpg

install

from maiden type ;install https://github.com/tai-studio/lissadron

Lissadron contains a dedicated sound engine, so a reset might be required. If the reset results in a supercollider fail, just reboot the norns and it should be fine. The engine is quite heavy and takes some time for loading. Lissadron uses global clock, which requires 200424 to run.

{.links-list}

demos

Documentation

The underlying synthesis engine is monophonic and consists of four voices, each playing in harmonic relation to the base frequency determined by the note parameter.

Each voice has a plentytude of parameters that are controlled by the two meta-parameters x0 and x1. Influence of the two meta-parameters on the sound as well as the harmonic structure of the voices are chosen at random. The powerful part of the system lies in the possibility to retrigger the randomisation by providing a different random seed. This also makes it possible to save and recall the (seemingly random) state of the system.

The integrated sequencer allows to step through random seedsm, based either on the intenal clock, or an externally provided one. By an integrated euclidean trigger-pattern distributor, a broad variety of rythms can be created.

The norns-native interface is:

K2 seed--	-- increase random seed by one
K3 seed++	-- decrease random seed
<shift>-K2 seed - 131
<shift>-K3 seed + 131
E1 amp 		-- legato
E2 x0  		-- meta parameter, different for each seed
E3 x1  		-- meta parameter, different for each seed
<shift>-E1 note 
<shift>-E2 seq_steps
<shift>-E3 seq_freq

K1 <shift>

Parameters (controlled e.g. via MIDI mapping) are

Releases and issues

Here is the current release. The dust project manager always points to the git head of the master branch, so you should be save.

For a changelog, see release page. Please file issues in the corresponding github issue tracker (and possibly provide a pull request to fix the issue).