Skip to content

Sonicware Liven TextureLab MIDI CC chart, NRPN and OSC map

The Sonicware Liven TextureLab MIDI implementation: 35 CC, each named, for Claude (MCP), SuperCollider or any OSC app.

Device Sonicware Liven TextureLab
Vendor Sonicware
OSC prefix /liven_texturelab
Source πŸŽ›οΈ Derived from an Electra One community preset
Revision per Electra preset
Upstream electra-preset
Driver file devices/sonicware/liven_texturelab.json
Not tested on the device yet

This driver comes from documentation or community data and has not been checked on real hardware. If you own one, a quick test and a pull request promoting it helps everyone β€” see CONTRIBUTING.

How do you control it?

Find the MIDI ports, then start the bridge with this driver:

osc-bridge detect        # prints the ready-to-run line for what is plugged in
osc-bridge run --device devices/sonicware/liven_texturelab.json --out-port <N> --in-port <M>

Then send OSC to 127.0.0.1:7777, for example:

osc-bridge osc-send /liven_texturelab/size 63

From Claude or any MCP client, the osc-bridge mcp server exposes this driver as liven_texturelab: ask β€œwhat can the Sonicware Liven TextureLab do?” and it reads this map with list_routes. See the MCP guide.

MIDI CC and NRPN parameters (35)

OSC address CC NRPN (MSB/LSB) Range Nature Section
/liven_texturelab/size 33 0–127 continuous
/liven_texturelab/timing 34 -63–63 continuous
/liven_texturelab/desnity 35 0–127 continuous
/liven_texturelab/difiusion 36 0–127 continuous
/liven_texturelab/timing_fix 34 0–127 continuous
/liven_texturelab/shape 42 0–127 continuous
/liven_texturelab/jitter 43 0–127 continuous
/liven_texturelab/rnd_shap 47 0–127 continuous
/liven_texturelab/rnd_size 48 0–127 continuous
/liven_texturelab/sample 32 0–127 continuous
/liven_texturelab/pitch 37 -24–24 continuous
/liven_texturelab/position 38 0–127 continuous
/liven_texturelab/lenght 39 0–127 continuous
/liven_texturelab/speed 40 -63–63 continuous
/liven_texturelab/blend 41 0–127 continuous
/liven_texturelab/pos_rnd_rate 45 0–127 continuous
/liven_texturelab/pos_rnd_depth 46 0–127 continuous
/liven_texturelab/direction 44 0–127 continuous
/liven_texturelab/velocity 21 0–127 continuous
/liven_texturelab/rate 7 0–127 continuous
/liven_texturelab/depth 9 0–127 continuous
/liven_texturelab/attack 61 0–127 continuous
/liven_texturelab/release 62 0–127 continuous
/liven_texturelab/list 68 0–127 continuous
/liven_texturelab/cutoff 69 0–127 continuous
/liven_texturelab/resonance 70 0–127 continuous
/liven_texturelab/reverb_typ 71 0–127 continuous
/liven_texturelab/shimmer 72 0–127 continuous
/liven_texturelab/fadereverb_mix 73 0–127 continuous
/liven_texturelab/destination 49 0–127 continuous
/liven_texturelab/waveform 50 0–127 continuous
/liven_texturelab/fade_in 51 0–127 continuous
/liven_texturelab/retrigger 52 0–127 continuous
/liven_texturelab/rate 53 0–127 continuous
/liven_texturelab/depth 54 0–127 continuous

Performance MIDI

Notes, pitch bend and any CC are also available: /liven_texturelab/note/on <note> <velocity>, /liven_texturelab/cc/<number> <value>, /liven_texturelab/pitchbend <0-16383>, /liven_texturelab/program_change <n>.

Limitations

Imported from an Electra One community preset. The mapping reflects the preset author's editorial choices: parameter naming, ranges, and which params are exposed. Untested on hardware in this repo.

Frequently asked questions

Which MIDI CC controls the filter cutoff on the Sonicware Liven TextureLab?

CC 69 (0–127), named /liven_texturelab/cutoff in SynthHub's map.

How many parameters of the Sonicware Liven TextureLab can be controlled over MIDI?

SynthHub's map of the Sonicware Liven TextureLab lists 35 MIDI CC parameters, each with its number, range and a readable name; the full chart is on this page.

Can an AI agent like Claude control the Sonicware Liven TextureLab?

Yes: SynthHub's hosted MCP server knows the Sonicware Liven TextureLab's MIDI map, and its browser relay lets the agent send it parameter changes or load a sound, each sound change confirmed by you.