hi,if i save a project in cubase 14 pro with a preset in dune cm,if i close the project and next time i open it dune cm has the default preset loaded,not the preset i saved in the project
anyone any experience with this?

 

Spoiler: Source: Perplexity KI

When saving a project in Cubase 14 Pro using a preset in Dune CM, the synth often reverts to its default preset when reopening the project, instead of recalling the preset that was saved. This is a common issue with Dune CM and similar entry-level or lite plugin editions in Cubase, and several users have reported this behavior.

Why Dune CM Does Not Recall Presets

Dune CM and its BE edition can only recall presets saved in their "active" bank (usually Bank A), and many users find that saving or selecting presets from other banks or custom presets does not persist correctly between project sessions. When a project is reopened, the plugin restores the first patch of its active bank by default, which does not match the saved state you expect.

Workarounds and Possible Solutions

Saving the desired preset as an FXP (VST patch) via Cubase's patch management can sometimes preserve the sound, though this limits patch naming options.
Ensuring that "Save Bank" (as FXB) is used for entire banks, and "Save Patch" (as FXP) for single presets, then manually loading these saved patches each time may help.

Some users reset Cubase's preferences to address general saving/loading issues, especially if this problem also impacts other plugins; steps include moving the preference folders and relaunching Cubase to rebuild its configuration.
If permission errors appear on MacOS, manually creating the correct Library/Audio/Presets folder and assigning permissions may solve preset saving issues.

For persistent problems, consider contacting Steinberg or Synapse support, as some cases relate to software or OS-level bugs that may require updates or fixes.

Saving Strategies in Cubase

Always save your custom patch as an FXP after programming it, and try to keep it within the active preset bank.
Use Cubase's "Save Effect Preset" function from the plugin window, if available, to ensure that the preset is stored with the project correctly.
When using third-party plugins that don’t recall presets reliably, it may be necessary to reload your custom presets manually after opening a project.

This preset recall issue is well-documented among users of Dune CM and Cubase and is a limitation of the CM/BE editions of Dune. Consider upgrading to the full version of Dune if preset management is critical for your workflow.

Spoiler: Source: Grok KI

It looks like you're running into a common quirk with Dune CM (the Compact Music edition of Synapse Audio's Dune), especially when integrated with Cubase projects. This isn't a full-blown bug but stems from how Dune CM handles preset banks and how Cubase stores/recalls plugin states. I'll break it down based on user reports and developer insights from audio forums, then share some practical workarounds that should get your custom presets sticking on reload.

Why This Happens

• Dune CM's Preset Limitations: Unlike the full Dune editions, CM is restricted to just 127 user preset slots (essentially "Bank A"). It doesn't fully support saving or recalling from additional banks (like B or C) in a host like Cubase. If your custom preset is stored or initialized outside Bank A (e.g., via tweaks or external saves), Dune defaults back to the first patch in Bank A on project load. This is by design for the CM edition to keep it lightweight, but it trips up project recall.
• Cubase's Project Saving: Cubase 14 Pro embeds plugin states (including presets) directly into the .cpr project file for portability. However, for VST2/3 plugins like Dune CM, the recall relies on the plugin's internal bank/program change system. If Dune can't reliably "remember" the bank/program index across sessions, it falls back to defaults. VST3 presets saved via Cubase's menu sometimes don't load reliably in older Dune versions due to format mismatches (e.g., .vstpreset vs. Dune's native .fxp/.fxb).
• This issue has been echoed in threads dating back years (e.g., on KVR Audio and AudioSEX forums), but it's more pronounced in CM than full Dune. No widespread reports of it being fixed in recent updates, as CM is a legacy edition.

Solutions and Workarounds
Here are steps that have worked for users in similar setups (Cubase + Dune CM). Start with the quickest ones.

1. Save Your Preset Directly in Dune's UI (Recommended First Fix):
   • Open Dune CM in your Cubase track.
   • Tweak your preset to taste.
   • In Dune's interface, click the PATCH button (middle section), then Save Patch > choose "As FXP" (not VST3). Name it and save to a dedicated folder (e.g., Documents/Synapse/Dune CM Presets).
   • Back in Dune, select your new saved patch from the list (it should now be in Bank A).
   • Save the Cubase project.
   • On Reopen: Dune should load the exact patch since it's now pinned to a reliable slot in Bank A. If it still defaults, manually reselect the patch once—future loads should stick.
   • Why this helps: Bypasses Cubase's preset management and uses Dune's native format, which is more stable for project recall.
2. Use Cubase Track Presets to "Lock" the Dune State:
   • With your Dune preset loaded and track set up (MIDI, routing, etc.), right-click the track header in Cubase > Create Track Preset (or use the Track Presets tab in the Inspector).
   • Name it (e.g., "Dune CM Bass Lead") and save. This bundles the entire track state, including the plugin preset.
   • Save your project.
   • On Reopen: If Dune still defaults, delete the track and re-insert it using your saved Track Preset (via MediaBay or the preset menu). This forces a full reload of the embedded state.
   • Pro Tip: For multiple Dune instances, save them as separate track presets and build a template project with them pre-loaded.
3. Bank Management for Multiple Presets:
   • If you're dealing with banks: In Dune, click BANK > Save Bank > "As FXB" for Bank B/C tweaks. Save the .fxb file alongside your .fxp patches in the same folder.
   • Load the bank first via Dune's menu, then select the patch. This keeps everything self-contained.
   • Note: Avoid relying on Cubase's VST Preset menu for Dune CM—stick to FXP/FXB for compatibility.
4. Check/Reset Permissions and Paths (If Above Fails):
   • Ensure Cubase has full disk access (on macOS: System Settings > Privacy & Security > Full Disk Access > enable Cubase). On Windows, run as admin once.
   • Verify Dune CM's preset folder: Defaults to ~/Documents/Synapse Audio/Dune CM (macOS) or C:\Users\[YourName]\Documents\Synapse Audio\Dune CM (Windows). If corrupted, delete the contents (back up first) and rescan plugins in Cubase (Studio > Studio Setup > VST Plug-in Manager > Rescan).
   • Update Dune CM if possible (check Synapse Audio's site—last update was years ago, but patches exist). Also, confirm Cubase 14 is fully updated (Help > Check for Updates).

Quick Test

• Create a minimal test project: New VST instrument track > load Dune CM > pick/tweak a preset > save as FXP in Dune > save project > close/reopen.
• If it loads correctly now, scale up to your full project.

If none of this clicks (e.g., you're on a specific OS or have multiple Dune instances), drop more details like your OS, Dune version, or if it's VST2/3. You could also post on the Steinberg Forums or Synapse Audio support—they're responsive for legacy stuff like CM. Hang in there; once dialed in, Dune CM is a beast for those analog-modeled sounds!