Frequently Asked Questions

SnappySnap is a VST3/AU plugin that hosts other plugins (synthesizers or effects) and adds real-time parameter morphing between saved states called "snapshots." You save different parameter configurations, then smoothly blend between them using a fader or 2D XY pad. It is made by Electric Smudge, an indie developer.

SnappySnap itself runs as a VST3 plugin (all platforms) and AU plugin (macOS only). It can host VST3 and AU plugins inside it. VST2 plugins are not supported.

No. SnappySnap is a plugin-only tool designed to run inside a DAW (Digital Audio Workstation). There is no standalone application. It requires a host like Ableton Live, Logic Pro, FL Studio, Bitwig, Cubase, Reaper, GigPerformer, etc.

SnappySnap hosts instrument plugins (synthesizers) and appears as an instrument in your DAW. Put it on a MIDI/instrument track.

SnappySnapFX hosts effect plugins and appears as an audio effect. Put it on an audio/bus/return track.

Same features, different plugin category. Both are included with one license purchase.

No. While both are plugin hosts, they serve very different purposes. Blue Cat's Patchwork is a universal plugin host focused on loading multiple plugins in series/parallel chains for modular routing. SnappySnap hosts a single plugin and provides snapshot morphing, 2D XY-pad blending, breeding, drift, randomization, macros, and AI integration via MCP. They actually complement each other well.

No. Ableton's built-in instruments are internal to the DAW and not available as VST3 or AU plugins. This is an Ableton architecture limitation, not a SnappySnap limitation. The same applies to other DAW-internal instruments like Logic's Alchemy or FL Studio's Sytrus.

No. SnappySnap hosts one plugin per instance. To morph multiple plugins simultaneously, load multiple instances of SnappySnap in your DAW and use the Link feature to synchronize them.

• macOS: 13 (Ventura) or later. Both Intel and Apple Silicon Macs are natively supported (Universal Binary).
• Windows: 10 or later.
• Not supported: macOS Catalina (10.15) or older, Windows 8 or older, Linux.

Not currently. While the development framework (JUCE) theoretically supports Linux, the plugin hosting and scanning layer would need substantial rework to support native Linux plugin formats. It's not on the immediate roadmap, but feedback is noted.

macOS:

Windows:

Important (Windows): SnappyScanner.exe must remain installed. It's required for plugin scanning.

Download the latest version from your dashboard at https://electricsmudge.com/dashboard. On macOS, you may need to delete the old plugin files first if the version doesn't update properly:

1. Delete old files from /Library/Audio/Plug-Ins/VST3/ and /Library/Audio/Plug-Ins/Components/
2. Optionally delete the plugin cache: ~/Library/Application Support/SnappySnap/plugin_cache.json
3. Install the new version
4. Rescan plugins in your DAW

If the AU version still shows the old version number after updating, this is a macOS component caching issue. Delete the old .component files, reinstall, then restart your Mac or rescan AU validation.

If the installer won't proceed past the destination screen, check your macOS version. SnappySnap requires macOS 13 (Ventura) or later. If you're on Catalina (10.15) or earlier, the installer's compatibility check will prevent installation. You'll need to update your macOS.

SnappySnap is not yet signed with an Apple Developer ID certificate. This is a known issue. Run these commands in Terminal to fix it:

Or right-click the file in Finder and select Open to bypass Gatekeeper once.

This is the most commonly reported issue. Ableton Live 12+ implements strict code signature validation. As of SnappySnap v3.3.0, the build pipeline issue causing this has been fixed.

If you're running an older version, run both quarantine removal AND code signing commands:

Then restart Ableton and rescan plugins in Preferences > Plug-Ins.

Note: The quarantine removal alone is often not enough for Ableton. You need BOTH the xattr command AND the codesign command. The AU version may work without code signing since Ableton handles AU validation differently.

The xattr command only removes the quarantine flag. Ableton 12+ also requires valid code signatures. You need the additional codesign step:

Yes. SnappySnap is a Universal Binary running natively on both Intel and Apple Silicon Macs.

The installer is not yet EV code-signed. Click "More info" then "Run anyway" to proceed.

Some antivirus software (including Malwarebytes browser extensions) may flag the download as suspicious because the installer isn't code-signed. Temporarily disable the antivirus extension, download the installer, then re-enable it.

Try these steps: 1. Temporarily disable antivirus/firewall browser extensions 2. Try a different browser (Chrome, Firefox, Edge) 3. Clear your browser cache and retry

Fully tested and confirmed working: - Ableton Live 11+ - Bitwig Studio - FL Studio 24+ - Logic Pro - Cubase / Nuendo - Reaper - GigPerformer

It depends on whether the DJ software supports VST3 or AU plugin formats. Many DJ platforms like Traktor or VirtualDJ have limited or no VST3 support. Check your specific DJ software's plugin compatibility.

1. Make sure SnappySnap (instrument) is on a MIDI/instrument track, not an audio track.
2. Make sure SnappySnapFX (effect) is on an audio/effect track, not an instrument track.
3. Load a hosted plugin first (click "Load Plugin").
4. Verify the hosted plugin itself produces sound.
5. Check your DAW's MIDI routing to ensure MIDI reaches the track.
6. Open the hosted plugin's GUI and check its own volume/settings.

If Ableton becomes unresponsive when opening certain plugin interfaces from within SnappySnap (e.g., Arturia synths), this may be a plugin-specific compatibility issue. Check which plugins trigger the freeze and try: - Updating to the latest SnappySnap version - Checking log files for scan errors - Testing with other hosted plugins to isolate the issue

In Reaper, load SnappySnap (instrument version) before SnappySnapFX in the signal chain. Loading them in the wrong order can cause project reload crashes.

2 machines per license.

Yes. Go to https://electricsmudge.com/dashboard, deactivate the old machine, then activate on the new machine with the same license key.

No. The old machine will be detected as a different machine_id. Deactivate it in your dashboard (or contact support), then re-activate with your license key.

The license is per-machine, not per-DAW. If one DAW sees it as licensed, all should. If you're using multiple user accounts on the same Mac, each account has its own Application Support folder with separate license files.

Check that: 1. Your internet connection is working 2. No firewall/VPN is blocking api.electricsmudge.com 3. Try temporarily disabling firewall/antivirus 4. Try again later (server may be temporarily down)

Make sure you're logging in at https://electricsmudge.com/dashboard with the same email address used during purchase. If it still doesn't appear, contact support with your order confirmation details.

Only for initial activation and periodic license checks (approximately every 30 days). You can use it offline for up to 30 days between checks.

Typically 1-5 minutes depending on how many plugins you have installed. Subsequent loads use the cache and are nearly instant.

This usually means a specific plugin is hanging the scanner (not crashing, just freezing past the timeout).

Fixes: 1. Wait - each plugin has a 10-second timeout 2. If stuck for more than 10 minutes, close and reopen the plugin. The problematic plugin will be added to the failed list. 3. Check the log file to identify which plugin is causing the hang: - macOS: ~/Library/Application Support/SnappySnap/Logs/ - Windows: %AppData%\SnappySnap\logs\ 4. Move suspected problematic plugins out of the scan directory temporarily 5. Delete the cache file and rescan: - macOS: ~/Library/Application Support/SnappySnap/plugin_cache.json - Windows: %LocalAppData%\SnappySnap\plugin_cache.json

Known slow-scanning plugins: iZotope products and IK Multimedia products are known to cause scanning hangs. This is addressed in v3.2.7+ with cached plugin descriptions that skip re-scanning on project reload.

Possible causes: - The plugin is VST2 only (not supported - SnappySnap requires VST3 or AU) - The plugin crashed during scanning and is now on the failed list - It's a DAW-internal instrument (not a standalone VST3/AU plugin)

Fix: Try clicking "Rescan All" in the Plugin Browser. You can also clear the plugin cache file to reset the failed list and start fresh.

If you get an error about missing SnappyScanner, verify that C:\Program Files\SnappySnap\SnappyScanner.exe exists. If missing, reinstall SnappySnap.

The main principle: the more knobs and faders (variable parameters) a plugin exposes, the better morphing will work. Plugins like Massive are great because nearly all their controls are exposed as automatable parameters.

For the most predictable results, stay within the context of a single preset and create variations by tweaking parameters within it. The ideal workflow is:

1. Load a plugin and select a starting preset
2. Tweak some parameters and save Snapshot 1
3. Tweak differently and save Snapshot 2
4. Continue building up to 12 snapshots as variations of the same base preset
5. Morph between these variations for smooth, musical results

This approach works much better than loading completely different presets on each snapshot, because the underlying plugin architecture (oscillator types, filter modes, effect routing) stays consistent, and only the continuous parameters change.

1D (Fader): Linear blend between snapshots in order. Think of it as a smart crossfader - if you have 2 snapshots, the top is Snapshot 2 and the bottom is Snapshot 1, with smooth interpolation between them. Add more snapshots and the fader evenly distributes them along its range. The "Snappy" parameter.

2D (XY Pad / "Snap Void"): Spatial blend based on distance to all snapshot positions. Move the cursor on the pad and nearby snapshots have more influence. More expressive and organic. Two completely different systems.

Reset All clears your snapshots and settings but does not unload the hosted plugin. The plugin remains loaded with its current state.

Load Plugin fully resets everything - it unloads the current plugin and loads a new one with a clean state. When switching between different plugins, always use Load Plugin to ensure a clean slate.

Parameters may be protected from morphing for several reasons:

1. Sanity Mode is ON (default): Protects volume, gain, pitch, mode, and other "dangerous" parameters
2. Macro bound: Parameters bound to macros are always controlled by the macro
3. Always-critical parameters: Bypass, MIDI channel, preset, program, etc. are always protected
4. Partial snapshots: If snapshots were saved with Learn Mode, only learned parameters morph

Make sure: 1. You have at least 2 snapshots saved with different parameter values 2. Both snapshot slots actually have data (check that the buttons show names, not "+") 3. The snapshots were saved with different parameter positions 4. If using Learn Mode, make sure parameters were learned before saving

Yes! Save each preset as a different snapshot. However, when morphing between vastly different presets, be aware that: - Discrete parameters (filter types, oscillator modes) will jump rather than blend smoothly - Turn Fast Recall OFF when using different plugin presets per snapshot to ensure full state restoration (wavetables, samples, etc.) - Enable Sanity Mode to protect structural parameters

Elastic mode adds momentum and inertia to morph transitions. Instead of jumping instantly, the morph position follows the target with acceleration/deceleration. Three levels: Low (responsive), Medium (smooth), Hard (very gradual). Works with both 1D fader and 2D XY pad. Great for smooth, musical transitions.

Breeding combines two parent snapshots using a genetic algorithm. Set a Crossover rate (blend ratio between parents) and Mutation rate (random variation). The result is a new parameter combination related to both parents but with unexpected variations. Great for sound design exploration.

The order matters: 1. Click "Macro Learn" button 2. First, turn the macro knob (M1-M8) you want to assign 3. Then, touch/move the parameter in the hosted plugin 4. The macro automatically binds and renames to the parameter name 5. Learn mode stays active for rapid multi-binding - disable when done

Common mistake: Touching the plugin parameter first and then the macro knob. It must be macro knob first, then plugin parameter.

Macro-bound parameters are excluded from morphing, randomization, and breeding. The macro has highest priority over all other parameter control. This is useful for keeping critical parameters (like filter cutoff) under your direct control while everything else morphs.

The slider next to the Randomize button controls the maximum deviation:

• Below 100%: "Nudge" randomization - each parameter deviates by a percentage from its current value. At 5%, a parameter at 0.50 might move to somewhere between 0.475 and 0.525. This is great for subtle variations.
• 100%: Absolute random - parameters can jump to any value regardless of their current position.

Tip: For minimal, musical variations, set the slider to 1-5%. This creates subtle timbral shifts without dramatic changes.

The Random Amount slider controls the maximum drift per parameter. Tips: - Use Learn Mode to limit randomization to only the parameters you want - Keep Sanity Mode ON to protect volume, pitch, and mode parameters - Start with very low Random Amount values (5-15%)

1. Enable "MIDI Trig" toggle in the plugin
2. Select a base octave (C-2 to C8)
3. Send MIDI notes: C = Snapshot 1, C# = Snapshot 2, D = Snapshot 3 ... B = Snapshot 12
4. Only snapshots with saved data respond
5. Trigger notes are consumed and NOT passed to the hosted plugin

Check that: - MIDI Trig is enabled - The correct base octave is selected - The MIDI channel matches your input (or is set to Omni) - The snapshot slots have saved data

• Direct Recall (default): Instantly loads snapshot parameters, like clicking the snapshot button
• Morph Blend: Sets the morph fader position proportionally for smooth blending. Pairs well with Elastic mode

Toggle between these via the "Recall" checkbox in the MIDI trigger row (available in v3.2.7+).

Drift automatically moves the morph position using Perlin noise, creating evolving sounds without manual input. Three modes: - Free: Random wandering from current position - Anchored: Wanders around an anchor point with gravity pulling back - Orbit: Rotates in a circular path around the anchor

In Free mode, the random walk can sometimes spend extended time in one area. This is inherent to random movement.

Fix: Switch to Anchored mode with the Gravity parameter set to pull back toward your desired center point. This ensures balanced movement. The Depth parameter controls maximum distance from the anchor.

Use the Speed parameter (0-10, exponential scale). Lower values = slow gentle movement, higher values = fast chaotic movement.

Not currently. This is a noted feature request. For now, use the Speed parameter to approximate your desired movement rate.

Drift Record lets you capture the generative drift movement as DAW automation: - Record OFF (default): Drift changes sound but doesn't write to DAW automation lanes - Record ON: Drift output is captured as automation data in your DAW. Hit Record in your DAW, let drift wander, and capture the organic path.

• Inner cursor (white dot): Your manual anchor position
• Outer cursor (glowing ring): The actual drift position where sound is calculated
• Connecting line: Shows the drift offset from your anchor

• macOS: ~/Library/Application Support/SnappySnap/presets/
• Windows: %LocalAppData%\SnappySnap\presets\

You can change this location in the plugin settings.

16 banks x 128 presets = 2,048 total. Additional capacity via custom preset folders.

Yes. Presets are plain XML files. Copy them from your preset folder and share. The recipient needs the same hosted plugin installed. Plugin paths may differ between OS, so the recipient may need to reload the plugin.

If the hosted plugin was updated and its parameter layout changed, cached values may not match. Try disabling Fast Recall and reloading the preset.

A performance optimization that restores snapshots/presets using cached parameter values instead of the plugin's full state restoration. - ON: Near-instant switching (~2ms). Best for live performance. May miss internal plugin state not exposed as parameters. - OFF: Full state restoration (~250ms). More accurate. Best for studio work with complex presets.

Tip: If you're using different plugin presets on each snapshot, keep Fast Recall OFF for accurate wavetable/sample restoration.

Possible causes and fixes: 1. GPU shaders: Disable shaders in the info panel to save GPU resources 2. Hosted plugin is CPU-heavy: Reduce polyphony or use a lighter plugin 3. Drift mode at high speed/chaos: Lower the Speed and Chaos values 4. Multiple instances: Disable shaders when running many SnappySnap instances

Note on CPU reporting: On multi-core systems (like Apple Silicon), CPU percentages are reported per-core. A reading of 190% means approximately 1.9 cores worth of processing, not that the CPU is overloaded.

1. Enable Elastic Mode for smoother transitions
2. Increase your DAW buffer size (512+ samples)
3. Enable Sanity Mode to protect volume/gain parameters from sudden jumps
4. Use Learn Mode to reduce the number of parameters being morphed

This is a rare reported issue. If you experience it, please note which plugin was loaded, what actions preceded the problem, and whether Sanity Mode was on/off. Send session logs for investigation.

No. SnappySnap itself adds zero latency. Any latency comes from the hosted plugin.

Plugins that expose most of their parameters as automatable VST3/AU parameters work best. Generally: - Great: Vital, Serum, Massive X, Phase Plant, FabFilter, Valhalla, Soundtoys - Good with caveats: Pigments (needs preset param protection), Kontakt instruments (complex state) - Limited: Plugins with heavy internal routing, modular architectures, or unexposed parameters

FX plugins generally handle morphing better than synthesizers since they tend to have more continuously variable parameters.

This is a VST3 limitation, not a SnappySnap issue. Some plugins don't expose all their parameters as automatable parameters to the host - they keep certain controls internal. SnappySnap can only access what the plugin makes available through the standard VST3/AU interface.

Some plugins use non-standard parameter types for note selections and toggle matrices that don't get captured by SnappySnap's parameter-based snapshot system.

Workaround: Turn off Fast Recall. This uses full state restoration instead of parameter-only capture, which has better compatibility with special control types.

Waves plugins, particularly OVox, may show blank AU interfaces or fail to pass audio through in FX mode. This is a compatibility issue with how Waves handles audio routing in non-standard hosting environments. Other plugin brands typically work without issues.

No. Wavetables, samples, and internal preset data are internal state not exposed as automatable parameters. SnappySnap can only control parameters that the plugin exposes to the host.

SnappySnap includes a built-in MCP (Model Context Protocol) server that lets Claude Desktop read and control plugin parameters. Claude can view parameters, set values, trigger randomization, and manage snapshots.

No. MCP works on Claude's free plan. You do not need a paid subscription.

Step-by-step:

1. Open SnappySnap in your DAW with a plugin loaded
2. Click the info button ("i") and enable MCP
3. Note the port (usually 3001) and copy the bearer token shown
4. Edit your Claude Desktop config file:
5. macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

6. Windows: %AppData%\Claude\claude_desktop_config.json

7. Add this configuration:

Replace YOUR_TOKEN_HERE with the actual token from SnappySnap's info panel. Keep the word "Bearer" - only replace the token portion.

1. Start Claude Desktop (or fully restart it after config changes)
2. Look for the hammer/tools icon in Claude Desktop's chat input - this confirms MCP connection

• SnappySnap must be running in your DAW BEFORE launching Claude Desktop
• The endpoint must be exactly /mcp (not / or /sse)
• Use mcp-remote version 0.1.12 to 0.1.30 (not the latest - newer versions may break)
• The bearer token regenerates every DAW session - copy it fresh each time
• Node.js must be installed on your system for npx to work
• The port may vary (3001, 3002, 3003) - match what's shown in SnappySnap's info panel

If Claude Desktop shows errors like "Unexpected token S, Shutting d... is not valid JSON", the MCP server is crashing on launch.

Fixes: 1. Update to the latest SnappySnap version (v3.3.0 fixes protocol negotiation) 2. Verify MCP is enabled in SnappySnap's info panel 3. Make sure SnappySnap has a plugin loaded and is running in your DAW 4. Check for port conflicts on port 3001 5. Ensure the endpoint URL ends with /mcp 6. Copy a fresh bearer token

This is typically a protocol version mismatch. Claude Desktop updates frequently and may use a newer protocol version than SnappySnap supports.

Fix: Update to SnappySnap v3.3.0, which includes proper protocol version negotiation (graceful fallback instead of crashing).

MCP integration is officially tested with Claude Desktop only. Third-party MCP clients may work but are not guaranteed. Some users have successfully created custom bridges for other AI tools - reach out to support if you'd like to share your setup.

If SnappySnap freezes when loading, MCP initialization may be blocking the main thread.

Fix: Edit ~/Library/Application Support/SnappySnap/settings.xml (macOS) or %LocalAppData%\SnappySnap\settings.xml (Windows) and set:

This is fixed in v3.3.0 where MCP startup runs off the main thread.

Correct - the MCP server is built into the plugin itself. You don't install a separate npm package. Use mcp-remote to connect to SnappySnap's built-in server endpoint.

This usually means the GPU rendering has been auto-disabled due to a detected incompatible graphics setup. Check the info panel - if the GPU Render toggle is disabled/locked, SnappySnap has detected an issue.

Possible fixes: - Update your GPU drivers - Check your DAW + GPU combination (AMD GPU + Ableton on Windows is a known problem config) - The plugin should still function with a basic/fallback visual mode

Disable shaders in the info panel. This switches to static background images and saves GPU resources. Particularly useful when running multiple instances or on laptops.

Use the S/M/L buttons in the top-right area of the plugin to change scale: - S = 1.5x (707 x 594) - M = 1.75x (824 x 693) - L = 2.0x (942 x 792)

This is a known OpenGL context handling issue. Workaround: Use the S/M/L buttons instead of drag-resizing.

Some minimal hosts (SAVIHOST, Mixcraft) may not handle SnappySnap's window sizing correctly. Try the S/M/L size buttons. Test in a fully supported DAW to confirm the issue is host-specific.

Click "Show Plugin" button. If the window appears off-screen, try closing and reopening it. On Windows, clicking hosted plugin GUIs may steal keyboard focus from the DAW - this is a known Windows-specific issue.

Two themes available: Void (dark purple, default) and Teal (teal accents). Switch via the theme selector in the top section of the UI. Theme changes are instant and persist across sessions.

SnappySnap LE is a free, feature-limited version: - 2 snapshot slots (instead of 12) - 1D morph fader only (no XY pad) - No macros, breeding, drift, MIDI triggers, Link, or MCP - Void theme only

It keeps the core engine: Fast Recall, Sanity Mode, parameter protection, and the same out-of-process scanner.

This is a known issue being investigated, particularly affecting the Logic Pro AU version. Make sure both snapshots are properly saved with different parameter values. If it still doesn't work, try these steps: 1. Save Snapshot A with one set of parameter values 2. Change parameters significantly 3. Save Snapshot B 4. Move the morph slider

• LE: Permanent free access to basic A/B morphing. Good for trying the core concept.
• 7-day trial: Full features unlocked (XY pad, 12 snapshots, drift, breeding, macros, everything). Best "try before you buy" experience. Start it from the info panel.

Purchase a license and activate it. No reinstall needed - LE and Full are separate plugins that can coexist.

• AAX (Pro Tools) support - On the radar for the future
• Multiple Link Groups - Named groups with separate Leader/Follower sets
• Customizable CC assignments - For bank/preset/snapshot switching
• Plugin compatibility list - Community-driven list of which plugins work best
• Tempo-synced drift - Drift speed tied to DAW BPM
• Tooltips on buttons - Hover hints for UI elements
• Per-parameter modulators - Dedicated LFOs, envelopes, random generators
• Inverted Learn Mode - Select parameters to EXCLUDE rather than include
• Controllable morph speed - Adjustable transition time between snapshots
• AU/VST3 filter in plugin browser - Separate listings for different formats
• Learned parameter indicator - Visual confirmation of which parameters are assigned

Check the changelog: https://electricsmudge.com/changelog

https://electricsmudge.com/dashboard - View active machines, deactivate devices, access downloads, and view purchase receipts.

Refund requests can be initiated through the dashboard. Before requesting, consider updating to the latest version as many reported issues have been resolved in recent updates.

Email delivery issues may occur due to spam filtering. Check your spam/junk folder, try a different email address, or contact support for manual verification.

• macOS: ~/Library/Application Support/SnappySnap/Logs/
• Windows: %AppData%\SnappySnap\logs\

The plugin automatically rotates the last 5 session logs (SnappySnap_1.log through SnappySnap_5.log).

1. SnappySnap version (click the "i" button to check)
2. DAW name and version
3. Operating system (macOS version or Windows version)
4. Hosted plugin name (if relevant)
5. Steps to reproduce the issue
6. Log files (zip and upload)
7. Screenshots or screen recordings if applicable

Upload them to https://swisstransfer.com/ (or any file sharing service) and share the link with support.

Delete the settings.xml file: - macOS: ~/Library/Application Support/SnappySnap/settings.xml - Windows: %LocalAppData%\SnappySnap\settings.xml

Delete the plugin_cache.json file: - macOS: ~/Library/Application Support/SnappySnap/plugin_cache.json - Windows: %LocalAppData%\SnappySnap\plugin_cache.json

1. Keep Sanity Mode ON unless you intentionally want to morph volume/pitch/mode parameters
2. Use Learn Mode for surgical control over which parameters morph and randomize
3. Close hosted plugin GUI before randomizing to avoid crashes with some plugins
4. Back up your presets folder before updating
5. Disable shaders if running multiple instances or on battery power
6. Use Fast Recall ON for live performance, OFF for studio accuracy
7. Try Elastic Mode for smoother, more musical morph transitions

For the latest updates, visit https://electricsmudge.com/changelog For account management, visit https://electricsmudge.com/dashboard Need help? Include your version, DAW, OS, and logs when reporting issues.