An R&B and soul singer’s HALion Sonic sounds in Cubase kept switching back every time he restarted a track, because the commercial MIDI files he was using carried patch, volume and pan information that was resent from the start of each file.
He was making his own backing tracks for an upcoming show. His method was to download commercially produced MIDI backing tracks, import them into Cubase, and use the instruments and effects plugins in Cubase, which sound better than the General MIDI sounds, to mix and master his own versions. His question for me was why, when he selected a different sound in HALion Sonic and then restarted the track, the sound kept switching back to the one originally chosen by the creator of the MIDI file. The volume and the panning position kept changing back as well.
When the backing tracks were commercially created, they came with patch and bank information so that the file could be played back on any system. The MIDI player reads that information and knows to select, say, a piano for channel 1, a bass for channel 2 or a drum kit for channel 10. It also tells the player what volume to set for each instrument and where to pan it. That information is at the beginning of a MIDI file, so every time my client restarted the file and played it back, the patch information was being sent again.
Deleting the controllers in Cubase
Fortunately there’s a very straightforward solution to this, and I talked him through it.
- Selected all of the MIDI information.
- Opened the MIDI menu on Cubase’s top menu bar and chose Delete Controllers.
- Looked at the MIDI regions to check that the patch and volume information had gone.
Delete Controllers removes the data about which instruments to use but keeps controllers such as sustain and pitch bend, so the musical performance stays intact.
With that information removed, he was able to make his own patch changes and volume adjustments without anything resetting.
I also showed him that if there was other information left, for example expression, which could be controlling the volume, we could use other MIDI tools in Cubase such as the Logical Editor, with a preset to strip out only certain controllers.
He was delighted that this frustrating problem was solved and that he could move on with creating his own backing tracks. If you’re working with hardware sounds rather than plugins, I’ve also written up a case where I set up a Roland keyboard patch list in Cakewalk so a client could control the keyboard’s sounds from his DAW.
Not sure it’s the same problem? Ask a question first
