Global Settings
Use Global Settings for template size, timing, keyswitch behavior, display preferences, and plugin scanning paths.
Template and Performance
| Setting | Description |
|---|---|
| Outputs | Sets how many output rows are active, from 1 to 64. |
| Input Delay | Groups notes played within the delay window so chords are interpreted together. Lower values feel tighter; higher values are more forgiving, give the engine a smoother performance, and can reduce unwanted micro notes. |
| Mixer Cores | Controls hosted-instrument processing distribution. Increase this for larger hosted templates if your system benefits from parallel processing. |
| Row Labels | Output row names appear in the routing matrix, mixer, MIDI export, and module editors. |
Keyswitch Settings
Keyswitches
Sets the number of active keyswitch slots, up to 12. Use fewer slots when you want the keyswitch range to occupy less of your controller.
Lowest Keyswitch Note
Sets the first MIDI note in Filament's keyswitch range. The default is MIDI note 21, displayed as C0 in Filament.
KS Through
Enables a separate note zone that passes through to hosted instruments. Use this for sample-library keyswitches inside Filament. Set the through-zone start note and count so it does not collide with Filament's own keyswitch range.
Display Controls
These controls are preference settings for readability and comfort. They do not change the sound of a project.
UI Scale
Scales the interface from 50% to 200% in 5% steps. You can also resize the plugin with the drag handle in the bottom-right corner; this adjusts the interface scale in the same way.
Text Size
Adjusts text independently from the overall UI scale.
Brightness and Contrast
Fine-tunes the interface for different monitors and rooms.
Theme
Switches the interface theme. Use reset controls if you want to return display settings to their defaults.
Plugin Folder
Filament scans standard AU/VST3 plugin locations, but you can add a custom plugin folder when your instruments live outside the default paths.
After changing plugin folders, rescan or reopen the plugin browser before assuming a newly installed instrument is unavailable.