Skip to main content

​
Presets and Settings

This guide covers everything you need to know about saving patches, managing presets, and configuring plugdata to work the way you want.

​
Saving and Loading Patches

​
Saving Patches

Save the current patch to its existing location:
  • Press Cmd/Ctrl+S
  • Or select File > Save
If the patch hasn’t been saved before, you’ll be prompted to choose a location.

​
Loading Patches

1

Open File

Press Cmd/Ctrl+O or select File > Open
2

Browse to Patch

Navigate to your .pd file
3

Open in New Tab

The patch opens in a new tab (or replaces empty untitled patch)
Recent Files: Access recently opened patches from the Home panel or File > Open Recent

​
File Format Notes

Pure Data files (.pd):
  • Text-based format
  • Fully compatible with vanilla Pd and Pd-Extended
  • Can be edited in text editor (advanced)
  • Version control friendly
Abstractions:
  • Saved as separate .pd files
  • Referenced by name in parent patches
  • Must be in search path or same directory
Don’t rename .pd files used as abstractions without updating references in parent patches.

​
Managing Presets

​
Plugin Presets (DAW Mode)

When running as a plugin, presets are managed by your DAW:
1

Create Preset

Use your DAW’s preset save function:
  • Saves all parameter values
  • Saves current patch state
  • Stored in DAW preset format
2

Recall Preset

Load presets through DAW interface:
  • All parameters restored
  • Automation data remains separate
3

Share Presets

Export using DAW’s preset sharing features
What’s Saved:
  • All [param] parameter values
  • GUI object states (number boxes, sliders, etc.)
  • Array contents (if marked to save)
  • Current patch selection (if saved with project)
What’s NOT Saved:
  • Temporary states (metro running, etc.)
  • Audio buffer contents
  • Network connections
  • MIDI controller mappings (DAW-dependent)

​
Standalone Presets

In standalone mode, manage presets manually: 
# Save state to file
[write my-preset.txt(
  |
[textfile]

# Load state from file  
[read my-preset.txt(
  |
[textfile]
Or use state-saving abstractions:
  • [preset] object for snapshots
  • [state] from ELSE library
  • Custom save/load systems
Create a preset management subpatch to handle save/load operations for your entire patch.

​
Application Settings

Configure plugdata to match your workflow:

​
Accessing Settings

1

Open Settings

Press Cmd/Ctrl+, or select File > Settings
2

Choose Category

Click categories on the left:
  • Audio
  • MIDI
  • Theme
  • Paths
  • Key Mapping
  • Advanced
3

Adjust Settings

Modify settings as needed - most take effect immediately

​
Audio Settings

Available in standalone mode onlyDevice Selection:
  • Choose audio input/output devices
  • Set sample rate (44100, 48000, 96000 Hz)
  • Configure buffer size for latency vs performance
Channel Configuration:
  • Input channels to enable
  • Output channels to enable
  • Multi-channel routing
Driver Type (platform-dependent):
  • macOS: CoreAudio
  • Windows: ASIO, DirectSound, WASAPI
  • Linux: ALSA, JACK
Available in plugin modeSettings inherited from DAW:
  • Sample rate matches DAW project
  • Buffer size set by DAW
  • I/O configuration set by track routing
Plugin-specific:
  • Oversampling enable/disable
  • Latency compensation
  • Thread count for processing
Recommended Buffer Sizes:
  • Low latency (live performance): 64-128 samples
  • Balanced: 256-512 samples
  • High CPU projects: 512-1024 samples

​
MIDI Settings

Configure MIDI input and output:
1

Enable MIDI Devices

  • Check boxes next to available MIDI devices
  • Input devices for receiving MIDI
  • Output devices for sending MIDI
2

Channel Configuration

  • Enable specific MIDI channels if needed
  • All channels enabled by default
3

Test MIDI

  • MIDI indicator in statusbar blinks on activity
  • Use [notein] or [ctlin] to receive
  • Use [noteout] or [ctlout] to send
MIDI settings are separate for standalone and plugin modes. Configure each independently if you use both.

​
Path Configuration

​
Search Paths

Plugdata searches for abstractions and externals in specified directories:
1

Open Path Settings

Settings > Paths panel
2

Add Search Path

Click + and select a directory containing:
  • Abstraction .pd files
  • External libraries
  • Help files
3

Organize Paths

  • Drag to reorder (searched in order)
  • Remove unused paths
  • Use relative paths for portable setups
Default Paths:
  • Built-in ELSE library
  • Built-in Cyclone library
  • User documents folder
  • Application support folder
Adding Custom Libraries:
  1. Download or create library folder
  2. Add folder to search paths
  3. Restart plugdata (some externals)
  4. Access objects by name

​
Path Best Practices

Create a project folder structure:
my-project/
├── main.pd
├── abstractions/    # Add to search path
│   ├── synth.pd
│   └── effect.pd
├── samples/
│   └── audio.wav
└── data/
    └── presets.txt
Add my-project/abstractions/ to search paths.
For patches that work on any system:
  • Keep abstractions in same folder as main patch
  • Use relative paths for file access
  • Document any required external libraries
  • Avoid absolute paths (C:/Users/...)
For patches used across projects:
  • Create a central library folder
  • Add to search paths on all systems
  • Version control library separately
  • Document dependencies clearly

​
Theme and Appearance

​
Choosing a Theme

1

Open Theme Settings

Settings > Theme panel
2

Select Theme

Choose from built-in themes:
  • Light theme
  • Dark theme
  • Custom themes
3

Preview Changes

Changes apply immediately for preview

​
Customizing Appearance

Available Options:
  • UI Scale - Overall interface size
  • Font - Interface font family and size
  • Object Colors - Default object colors
  • Connection Style - Line thickness and curvature
  • Grid Settings - Grid spacing and visibility
Increase UI Scale on high-DPI displays or for better readability during live performances.

​
Object Theme Manager

Customize individual object appearance:
  1. Select objects
  2. Open Inspector panel
  3. Modify in Appearance section:
    • Background color
    • Outline color
    • Text color
    • Border width
Save custom themes for reuse across patches.

​
Keyboard Shortcuts

​
Viewing Shortcuts

Access the keyboard shortcuts reference:
  • Settings > Key Mapping panel
  • See all available commands and current mappings
  • Search for specific actions

​
Customizing Shortcuts

1

Open Key Mapping

Settings > Key Mapping panel
2

Find Command

Browse or search for the command to modify
3

Assign Shortcut

  • Click in the shortcut field
  • Press desired key combination
  • Conflicts are highlighted
4

Apply Changes

Changes take effect immediately
Shortcut Tips:
  • Use modifiers (Cmd/Ctrl, Shift, Alt) to avoid conflicts
  • Stick to conventions (Cmd/Ctrl+S for save, etc.)
  • Document custom shortcuts for collaboration
  • Export/import shortcut configs for consistency

​
Advanced Settings

​
Performance Options

Number of threads for audio processing:
  • Auto (recommended) - Matches CPU cores
  • Manual - Set specific count
  • More threads = better performance on multi-core CPUs
  • Too many threads can increase overhead
Digital signal processing configuration:
  • Oversampling - Reduce aliasing (increases CPU)
  • Limiter - Prevent output clipping
  • Denormal prevention - Avoid CPU spikes
Visual performance settings:
  • Framerate limit - Cap GUI updates
  • Reduce animations - Faster on slower systems
  • Disable shadows - Reduce GPU usage

​
Advanced Patch Settings

Available per-patch:
  • Canvas properties (size, position)
  • GOP settings (graph on parent)
  • Audio latency compensation
  • MIDI channel routing
Most users don’t need to modify advanced settings. Defaults work well for typical use cases.

​
Settings Files and Locations

​
Settings Storage

Plugdata stores settings in platform-specific locations: macOS: 
~/Library/Application Support/plugdata/
  ├── settings.json
  ├── keymaps.xml
  └── themes/
Windows: 
C:/Users/[User]/AppData/Roaming/plugdata/
  ├── settings.json  
  ├── keymaps.xml
  └── themes/
Linux: 
~/.config/plugdata/
  ├── settings.json
  ├── keymaps.xml  
  └── themes/

​
Backup and Transfer

To backup or transfer settings:
  1. Locate settings folder (see above)
  2. Copy entire folder
  3. Paste to new system in same location
  4. Restart plugdata
Manually editing settings files can cause issues. Use the Settings panel when possible.

​
Plugin vs Standalone Differences

​
Plugin Mode

Settings controlled by DAW:
  • Audio device and sample rate
  • Buffer size
  • Input/output routing
Settings in plugdata:
  • MIDI device selection
  • GUI preferences
  • Keyboard shortcuts
  • Paths and libraries
Presets:
  • Saved by DAW
  • Recalled via DAW preset system
  • Can be shared as DAW preset files

​
Standalone Mode

Full control over:
  • Audio device selection
  • Sample rate and buffer size
  • All input/output configuration
Presets:
  • Manual save/load systems
  • Custom preset management in patch
  • File-based storage

​
Troubleshooting Settings

Solutions:
  • Check file permissions on settings folder
  • Ensure enough disk space
  • Try resetting to defaults
  • Check for conflicting settings files
Check:
  • Correct audio device selected
  • Device not in use by other app
  • Sample rate matches device capabilities
  • DSP enabled (power button in statusbar)
Verify:
  • MIDI device enabled in settings
  • Device connected and powered on
  • Using correct MIDI objects in patch
  • MIDI indicator blinking on activity

​
Next Steps

Build docs developers (and LLMs) love

Get started for freeTalk to us