Preset Management
Presets allow you to save, organize, and share complete mapping configurations. This guide explains how to manage presets in Gamepad MIDI.
What Are Presets?
A preset is a saved configuration that includes:
- All MIDI mappings for all controls
- Smoothing settings for each control type
- Touchpad settings
- Any other configuration options
Presets let you:
- Switch between different mapping setups instantly
- Create configurations for different DAWs or workflows
- Share your mappings with other users
- Back up your configurations
The Presets Menu
Access preset functions through the Presets menu in the mapping editor's menu bar.
Menu Options
- Create New Preset - Start a new preset from scratch
- Save Current Preset - Save changes to the active preset
- Rename Preset - Change the name of the current preset
- Delete Preset - Remove the current preset
- Export Preset - Save preset to a file for sharing
- Import Preset - Load a preset from a file
- [Preset List] - Load any saved preset
Creating a New Preset
Starting Fresh
- Click Presets in the menu bar
- Select "Create New Preset"
- Enter a name for your preset (e.g., "Ableton Live Synth")
- Click "OK"
Result:
- A new empty preset is created
- All existing mappings are cleared
- The preset name appears in the Presets menu
- You can now add mappings to this preset
From Current Configuration
If you have mappings you want to save:
- Configure your mappings as desired
- Click Presets → "Create New Preset"
- The current mappings will be saved in the new preset
Note: This doesn't clear your mappings; it creates a copy with a new name.
Saving Presets
Auto-Save
Gamepad MIDI automatically saves:
- The currently active preset when you make changes
- Your mappings when you close the application
- The last used preset (loaded on next launch)
Manual Save
To explicitly save changes:
- Click Presets in the menu bar
- Select "Save Current Preset"
- Changes are saved immediately
Unsaved Changes
If you have unsaved changes:
- The preset name in the menu shows as modified
- When switching presets, you'll be prompted to save
- When quitting, you'll be prompted to save
Loading Presets
From the Menu
- Click Presets in the menu bar
- A list of available presets appears
- Click the preset name you want to load
- If you have unsaved changes, you'll be prompted to save first
- The preset loads immediately
Result:
- All mappings are replaced with the preset's mappings
- Smoothing settings update
- The preset becomes the active preset
On Application Launch
Gamepad MIDI automatically loads:
- The last preset you had active
- Or starts with no preset if this is your first launch
Renaming Presets
To change a preset's name:
- Load the preset you want to rename
- Click Presets → "Rename Preset"
- Enter the new name
- Click "OK"
Rules:
- Names must be unique
- Use descriptive names for easy identification
- Special characters are allowed
Deleting Presets
To remove a preset:
- Load the preset you want to delete
- Click Presets → "Delete Preset"
- Confirm the deletion
- The preset is permanently removed
Warning: This action cannot be undone. Export presets before deleting if you might need them later.
Exporting Presets
Export presets to share with others or back up your configurations.
Export Process
- Load the preset you want to export
- Click Presets → "Export Preset"
- Choose a location to save the file
- Name the file (use the preset name or descriptive title)
- Click "Save"
File Format:
- Presets are saved as
.jsonfiles - Human-readable text format
- Contains all mapping and setting data
Backup Presets
Create backups by:
- Exporting important presets
- Storing the files in a safe location
- Cloud storage, external drives, etc.
Importing Presets
Load presets created by others or restore from backups.
Import Process
- Click Presets → "Import Preset"
- Navigate to the preset file (
.json) - Select the file
- Click "Open"
- Enter a name for the imported preset (default is the file name)
- Click "OK"
Result:
- The preset is added to your preset list
- It's immediately loaded and becomes active
- Original file remains unchanged
Troubleshooting Imports
Invalid file format:
- Ensure the file is a valid Gamepad MIDI preset
- Check that it's a
.jsonfile - Verify it wasn't corrupted during transfer
Duplicate names:
- If a preset with that name exists, choose a different name
- Or delete the existing preset first
Preset Organization
Naming Strategies
Use clear, descriptive names:
By DAW:
- "Ableton Live - Synth Control"
- "FL Studio - Mixer"
- "Logic Pro - Effects"
By Purpose:
- "Drone Synth"
- "Drum Triggering"
- "Live Performance"
- "Studio Production"
By Instrument:
- "Serum Filter Control"
- "Massive X Macros"
- "Battery 4 Drums"
Creating a Library
Build a collection of presets for different scenarios:
-
Default Preset
- Basic, versatile mappings
- Good starting point for new projects
-
DAW-Specific Presets
- Optimized for each DAW you use
- Matches your workflow
-
Instrument Presets
- Specific to certain plugins or hardware
- Quick setup for common instruments
-
Performance Presets
- Designed for live use
- Emphasis on playability and expression
-
Experimental Presets
- Test unusual mappings
- Explore creative possibilities
Preset Files Location
Presets are stored on your system:
Windows
C:\Users\[YourUsername]\AppData\Roaming\PoundingSystems\Gamepad\Presets\
macOS
~/Library/Application Support/PoundingSystems/Gamepad/Presets/
Linux
~/.config/PoundingSystems/Gamepad/Presets/
Note: These directories are created automatically when you save your first preset.
Accessing Preset Files
You can:
- Browse these folders directly
- Copy presets to/from other locations
- Back up the entire Presets folder
- Sync across computers using cloud storage
Working with Multiple Computers
Sync Presets Across Devices
Manual Method:
- Export presets on computer A
- Transfer files to computer B
- Import presets on computer B
Cloud Sync Method:
- Use a cloud service (Dropbox, Google Drive, etc.)
- Create symbolic links from the preset directory to your cloud folder
- Presets automatically sync across computers
Warning: Be careful with simultaneous editing on multiple machines to avoid conflicts.
Preset Best Practices
1. Start with a Template
Create a base preset with common mappings:
- Save it as "Template" or "Default"
- Use it as a starting point for new presets
- Modify and save under new names
2. Document Your Presets
Include purpose in the name:
- Not just "Preset 1" but "Ableton Drum Rack"
- Helps you remember what each preset does
3. Regular Backups
- Export important presets regularly
- Store exports outside the application directory
- Consider version control for complex setups
4. Test Before Performing
- Load your preset before a session
- Verify all mappings work as expected
- Keep a backup preset ready
5. Share with the Community
- Export and share useful presets
- Contribute to preset libraries
- Help other users get started quickly
Preset Modification Workflow
Making Changes to an Existing Preset
-
Load the Preset
- Select it from the Presets menu
-
Make Changes
- Add, edit, or delete mappings
- Adjust smoothing settings
- Test thoroughly
-
Save Changes
- Click Presets → "Save Current Preset"
- Or the changes auto-save
-
Export for Backup (optional)
- Presets → "Export Preset"
- Save to a safe location
Creating Variations
To create a variant of an existing preset:
- Load the original preset
- Click Presets → "Create New Preset"
- Give it a related name (e.g., "Synth Control v2")
- Make your modifications
- Both presets now exist independently
Troubleshooting
Preset Not Loading
Possible causes:
- File corruption
- Incompatible version
- Invalid JSON syntax
Solutions:
- Try importing the preset again
- Check the file in a text editor
- Restore from a backup
Changes Not Saving
Check:
- Do you have write permissions to the presets folder?
- Is the disk full?
- Is the application crashing before save?
Solution:
- Export the preset manually as a backup
- Check file permissions
- Move the presets folder if needed
Preset List Not Showing
Solutions:
- Restart the application
- Check that presets exist in the presets folder
- Try creating a new preset to refresh the list
Duplicate Preset Names
The application prevents duplicate names:
- Use unique names for each preset
- Delete old versions if needed
- Add version numbers or dates to names
Advanced: Manual Preset Editing
Presets are JSON files and can be edited manually.
Warning: Only edit presets if you understand JSON format. Incorrect syntax will prevent loading.
JSON Structure
{
"mappings": [
{
"controlType": "Axis",
"controlIndex": 0,
"mappings": [
{
"type": 0,
"channel": 1,
"ccNumber": 1,
"minValue": 0,
"maxValue": 127
}
]
}
],
"smoothingSettings": {
"leftStickFactor": 0.85,
"rightStickFactor": 0.85
}
}
Use Cases for Manual Editing
- Batch changing CC numbers
- Copying mappings between controls
- Adjusting multiple similar settings
- Creating presets programmatically
Next Steps
- MIDI Mapping Guide - Learn to create complex mappings
- Use Cases & Examples - See preset examples in action
- Smoothing Settings - Fine-tune your presets