The Client’s Challenge
I was recently contacted by a talented R&B soul singer preparing for an upcoming live show. His process was both smart and creative: he was taking commercially produced MIDI backing tracks and elevating them within Cubase, replacing the generic sounds with the far superior instruments and effects available in a modern DAW.
But he’d hit a maddening wall. He would painstakingly select the perfect electric piano in HALion Sonic, carefully balance its volume, and place it just right in the stereo field. Yet, every single time he restarted the track, his choices would vanish. The sound, volume, and panning would instantly snap back to the original, basic settings embedded in the file. It was a creative groundhog day, and the frustration was mounting, threatening to derail his show preparation.
Client Environment
- DAW: Steinberg Cubase
- Plugin: HALion Sonic SE
- Workflow: Importing commercial General MIDI (GM) backing tracks
- Symptoms: VST instrument patch, volume, and pan settings resetting on playback.
Diagnosis
This wasn’t a bug or a fault in Cubase. In fact, Cubase was performing its duties perfectly. The issue was a classic case of a ‘Ghost in the Machine’—hidden instructions buried within the MIDI file itself.
The symptoms—sound selection, volume, and pan all resetting simultaneously at the start of playback—pointed directly to controller data embedded at the very beginning of the MIDI region. These commercial files were created for maximum compatibility, designed to play correctly on any device that understands the General MIDI standard.
Understanding MIDI Controller Data
Think of a MIDI file not just as sheet music for a robot, but as a complete theatrical script. It contains:
- The Notes: The musical performance itself.
- The Stage Directions: Controller messages that tell the instruments *how* to play.
At the start of my client’s files were specific ‘stage directions’: Bank/Patch Change messages (e.g., ‘use the grand piano sound’), CC7 (set master volume to this level), and CC10 (set the pan position to this value). Every time he hit play, Cubase would read these instructions first, obediently resetting his custom settings before playing a single note.
The Fix
Fortunately, the solution is straightforward. We don’t need to hunt for individual controller messages; Cubase has a powerful, built-in function to surgically remove this setup data while preserving the musical performance.
Double-click the MIDI region in your Cubase project to open the Key Editor.
Select all MIDI data. The quickest way is with the keyboard shortcut Cmd+A (on Mac) or Ctrl+A (on Windows).
Navigate to the main menu at the top of the screen and click on MIDI > Functions > Delete Controllers.
Upon performing this action, we could immediately see in the controller lanes that the problematic patch and volume data was gone. Crucially, Cubase is intelligent enough to leave essential performance data like sustain pedal information and pitch bend untouched. The ‘script’ was now cleansed of its unwanted stage directions, giving my client full and final control over his sound.
Additional Reflections
Legacy Architecture vs. Modern Workflow
This case is a perfect example of a contextual conflict. The embedded MIDI data isn’t an error; it’s a feature from a different era. General MIDI was designed in the 90s to ensure a song file from one device would sound recognisably similar on another. A piano part would trigger a piano sound, a bass part a bass sound, and so on. This was revolutionary for its time.
Today, with vast, multi-gigabyte sample libraries and infinitely customisable VST instruments, that rigid instruction set becomes a hindrance. The modern workflow is about taking a MIDI performance and having complete creative freedom over the sound source. The problem my client faced wasn’t a fault, but simply a legacy system clashing with his modern creative intent.
The Logical Editor: For Surgical Strikes
While the ‘Delete Controllers’ function was the perfect hammer for this particular nail, I also showed my client Cubase’s Logical Editor. This is an incredibly powerful tool that acts more like a surgeon’s scalpel. With it, you could, for example, create a script to delete only volume (CC7) messages that occur within the first beat of a track, or to convert all sustain pedal data to a different controller. It’s the next level of MIDI manipulation for when you need precise, conditional editing.
My client was delighted. The fix was simple, the explanation empowering, and he could get back to the important work of creating his custom backing tracks, confident that he was now the sole director of his project.
Expert Support for Your Studio
If you are seeking professional help with Cubase MIDI patch change problems, VST instruments resetting, or other complex MIDI controller issues, one-on-one remote support services are available from Audio Support.
Not sure it’s the same problem? Ask a question first
