1: ModSynth.sf2:000:000
router_rules:
- clear
- {type: note, par1: 0-127*1+0, par2: 0-127*0+127}
- {type: cc}
- {type: pbend}
effects:
- lib: /usr/lib/ladspa/delay.so
audioports: mono
controls:
- {port: Delay, val: 0.3, link: 1/15, xfrm: 0-127=0-2.5}
router_rules:
- {type: note, chan: 1-16*1+0, par1: 0-127*1+0, par2: 0-127*1+0}
- {type: cc}
- {type: cc, chan: 1-1=2-16, par1: 7-7*1+0}
- {type: pbend}
- {type: kpress}
- {type: cpress}
cc: [3/91=80, 3/93=80]
fluidsettings:
synth.reverb.level: 0.9
synth.gain: 0.6
cclinks:
- {target: synth.reverb.room-size, link: 1/18, xfrm: 0-127=0-1}
init:
cc: [3/7=80, 1/73=0, 1/74=0]
Individual patches are denoted by the names in the
patches
item. Patches can contain instrument
settings for any number of MIDI channels, given as
<channel #>: <soundfont file>:<bank>:<preset>
MIDI channel numbers in bank files are numbered starting with channel 1, the way they are on
virtually all synthesizers, controllers, DAWs, etc. This is in contrast to FluidSynth, which numbers
channels beginning with 0. Patcher handles all of the translation between channel numbering schemes.
The keywords below are used to define various settings or messages to send, and can be used at bank-
level (i.e. no indentation), within individual patches, or in an optional
init
item. When a patch is
selected, bank-level keywords are applied first, then patch-level. Keywords in the
init
item are
applied
once
, when the bank is first loaded.
•
router_rules
- a list of rules for how FluidSynth should route MIDI messages. Each rule is
a mapping that must have a
type
key defining the type of MIDI message to route, and can also
include the keys
chan
,
par1
, and
par2
, which describe how to route/transform the messages.
These last three contain
router specifications
of the form
<min>-<max>*<mul>+<add>
or
SquishBox User Manual
page 7
