Critical workflow flaw in Nuendo 15

Nuendo
1

Hello Steinberg Team,

I am writing to express my deep concern and frustration regarding a critical workflow flaw in Nuendo 15 that regularly leads to a loss of work.

Currently, if a user accidentally loads a Track Preset onto an existing track that already has custom insert slots and plugin chains dialed in, there is absolutely no way to revert this action.

  • The standard Undo (Ctrl+Z / Cmd+Z) button becomes grayed out and inactive.
  • The MixConsole History remains completely blank regarding this action.

It seems that during the implementation of the Track Preset feature, Nuendo technically deletes the old channel state and replaces it with a new one. However, in a flagship, high-end professional post-production and audio workstation like Nuendo 15, such destructive behavior without any safety net is unacceptable. Users should not have to manually lock inserts or constantly dig into .bak files just to recover from a single accidental click.

My Request:
Please bridge the gap between Track Presets and the MixConsole History. Loading a Track Preset must be registered as an undoable action, allowing users to restore their previously built custom insert chains instantly.

This issue significantly slows down the professional workflow and causes unnecessary stress during tight deadlines. I highly hope the development team will address this oversight in the upcoming maintenance updates.

Thank you for your time and understanding.

Best regards

2

Yes, agreed. It’s little things like this that make a big difference in everyday workflow with Nuendo. Please post this issue here, so it will get the attention it needs: Nuendo 15.0.30 - Bug Collection Thread - June 2026 | OPEN for posting - #7 by Electriks

3

Gotta ask, why would you use a Track Preset on a track that’s already set up…and regularly? But I agree, you should be able to undo the damage…though you can always just set it up again.

4

Thanks for the input! I completely agree that having a working Undo is the ultimate goal here.

To answer your question: in high-end post-production, sound design, or game audio, we often work with massive templates and tight deadlines. Here are a few quick examples of why this happens:

  1. Creative experimentation: You might have a perfectly dialed-in vocal/dialogue chain, but you want to instantly test a completely different processing vibe (e.g., a specific “futuristic radio” or “monster voice” track preset) on the same track without creating duplicate tracks and moving clips around.
  2. Misclicks & Human Error: When browsing hundreds of presets in a rush, a single accidental double-click on the wrong item can instantly wipe out hours of custom plugin tweaking.

When a project has hundreds of tracks and a client is standing behind you, “just setting it up again” isn’t really an option — especially if you don’t remember the exact parameters of 5 different plugins in that specific chain. That’s why a safety net like Undo or MixConsole History is so crucial for a professional DAW.