Menu
Advanced MIDI Editing Using Cubase’s MIDI Modifiers. Gary Hiebner on Aug 31, 2016 in Cubase 0 comments. Share: Language. What I find great about these tools is that they don’t actually change your original MIDI part in the MIDI editor, but they are applied. So you could program in a MIDI part and then later decided to use maybe.
![Midi Midi](/uploads/1/2/5/5/125566010/805385514.jpg)
Using Cubase 7's powerful new Chord Track, you can completely rework your existing compositions. The original project with the chord sequence extracted from a MIDI piano part. Note the Chord Track Inspector panel settings as discussed in the main text. Cubase 7's Chord Track presents the tantalising possibility of changing a chord sequence that has already been recorded, and forcing your various MIDI tracks and monophonic audio parts to fit the new sequence.
I can best explain how to make use of the Chord Track by taking you through an example, audio illustrations of which you can find on the SOS web site at. The first screenshot shows a simple piano, drums, bass and guitar (both DI'ed and played back through the VST Amp Rack) recording and a vocal arrangement for a song section. After several listens, though, I've decided that the chords seem too boring. Here's how to add a little something extra. Ignoring the audio parts for the moment, select the MIDI piano part.
You can then execute the Project/Chord Track/Make Chords menu option. The small dialogue box that opens has a few options but, for now, use the default settings. Cubase will add a Chord Track to the project and populate it with the chords from the MIDI piano part. It will also add scale markers to indicate the scale (or scale changes) that occur during the sequence.
You can instruct the Chord Track to ignore notes shorter than a particular length, and two further options dictate how much detail Cubase extracts from the MIDI performance. Alternative bass notes can be chosen (for example, for chord inversions), as can tensions (additional notes beyond the standard triad that give the chord its flavour). In this example, the original chords were simple major chords (A, D and E). The revised chord sequence modified using the Chord Editor and Chord Assistant. The original (top lane) and revised (bottom lane) piano pats are also shown.
The revised part was created by setting the track to follow the Chord Track using Chords mode. The Chord Track itself doesn't make a sound by default: it's simply a chord and scale template that other tracks can be made to follow. However, you can audition your chords by choosing a MIDI channel or a new virtual instrument as the monitor output destination, and it can be useful to have a piano instrument or something similar set up specifically for the purpose.
Before I show you how to get another track to respond to the Chord Track, let's use the track to make some changes to the existing chords. There are a number of ways to do this. The Chord Editor enables you to make manual changes to individual chords, and chord changes can also be moved, added or deleted. The full version of Cubase, though, includes the Chord Assistant, which can do some of your creative thinking, even if you're 'harmonically challenged'! The behaviour of the Chord Assistant depends on what you select in the Chord Track.
Select a single chord event and the Chord Assistant will offer you a number of alternatives for that chord. Select multiple events and the Chord Assistant instead presents a menu of suitable chord progressions. This is particularly useful if you want to experiment with adding an additional chord change or two: simply enter some new events (they'll have an 'X' displayed in them), select the chord events surrounding them, and see what the Chord Assistant offers up. Dragging the Complexity slider right generates increasingly sophisticated suggestions. The Cadence settings provide further fine-tuning possibilities, but for the sake of simplicity we'll stick with the defaults.
The Chord Editor makes it easy to manually edit your Chord Track chord sequence. My initial chord progression consists of two sequences, each repeated twice, and as the Chord Assistant's algorithm uses some knowledge of music cadence (the sense that a phrase resolves itself to a satisfying musical end point), it's a good idea to focus work on these sorts of self-contained sequences. The second screenshot shows the changes to the Chord Track after a little experimentation. In some places (bars 1-4 and 9-12), I simply used the Chord Editor to add a little more colour. However, for bars 5-8, I used the Chord Assistant to suggest an alternative sequence. The Assistant generated a list of possibilities, which I auditioned while looping playback, by clicking on suggestions in the list.
Any other tracks that are set to follow the Chord Track will then automatically attempt to adjust themselves to fit the new chord sequence. If you select a single chord, the Chord Assistant will offer you some alternatives. Getting those other tracks to respond to the Chord Track requires you to consider a few settings. First, in the Chord Track's Inspector panel, you have to make a choice between Basic, Piano or Guitar Voicings, as the chords generated by each are constructed in different ways. The voicing setting can be applied to the whole track, as in this example, or to individual chords, via the Info line. I suggest you start with the Basic and Automatic Voicings, because once you've got your head around them, it's easier to experiment with the others.
These Voicings still force a target track to follow the Chord Track, but they do so by moving your existing notes as little as possible. Adding a negative mapping offset will also ensure that you catch any notes that are played very slightly ahead of a chord change but should be considered part of that chord. To get the original piano part to follow the new chord sequence, visit its Track Inspector's Chord Track section. There are a number of settings to choose from, but Chord mode is a good way to demonstrate the effect because this forces the MIDI part to follow the root note of the new chords, thus making the chord changes a little more obvious to the ear than Auto mode does. If you select multiple events in the Chord Track, the Chord Assistant will suggest alternative chord sequences. The process of slaving the bass and vocal audio tracks to the Chord Track can be broken down into three steps.
First, open the audio part in the Sample Editor and, with the VariAudio tab selected, set the Chord Track display mode in the Toolbar. This colour-codes the pitch segments: green if the note is part of the current chord; blue if the note is part of the scale but not the chord; or red if it belongs to neither. They're useful clues as to which notes might work. Next, set the Follow Chord Track mode in the track's Inspector panel. There are a number of options but for something simple like this, the Auto, Chord or Scale options are a sensible starting point.
Each will re-pitch the audio in slightly different ways, so you need to experiment, but you can use the Reset button if you need to start again! For both tracks, the Chords option got me closest to a suitable result. If that goes really well, step three (manual tweaking) may be unnecessary, but I did find myself wanting to make adjustments: I used Variaudio to change the pitch of a couple of notes, using the multi-colour segment display to help identify likely target pitches, and then applied a little pitch straightening.
If you make manual corrections after applying automatic Chord Track re-pitching, remember to turn off Follow Chord Track in the track's Inspector, as your tweaks may otherwise get overwritten! Having done all this, use the Audio/Realtime Processing/Flatten function to make your changes permanent, and your job is done. Setting the VariAudio display to Chord Track mode provides useful colour-coding of the pitch segments. There are some limitations to be aware of.
First, the strummed electric guitar part hasn't been tweaked to follow the new chords — and that's because this is a polyphonic part, which Variaudio can't process. The only option (other than the third-party Celemony Melodyne Editor software) is to replace the part with a new take. Other than this, the only practical limitation for most people is that the further you pitch-shift audio, the more likely it is that you'll hear unwanted artifacts from the processing. Even then, though, you can often usefully employ the pitch-shifted part as a guide track. I deliberately used basic Chord Track settings to demonstrate how the process works, but even with such simple settings you can perform miracles. I could just as easily have used the same approach to transform the 'major' feel of the progression into a 'minor' one. The various 'voicing' options can also be used in a similar way to generate more sophisticated results, and they're particularly helpful if you're trying to write MIDI parts for specific instruments, such as guitar or piano.
All contents copyright © SOS Publications Group and/or its licensors, 1985-2019. All rights reserved. The contents of this article are subject to worldwide copyright protection and reproduction in whole or part, whether mechanical or electronic, is expressly forbidden without the prior written consent of the Publishers. Great care has been taken to ensure accuracy in the preparation of this article but neither Sound On Sound Limited nor the publishers can be held responsible for its contents. The views expressed are those of the contributors and not necessarily those of the publishers. Web site designed & maintained by PB Associates & SOS.
This post covers how to use Cubase to send midi information to the Axe FX II in order to change pre-sets and/or scene changes on the Axe FX. It also covers sending Bank Changes to access pre-sets numbered higher than 127, e.g.
The tutorial was made with Cubase 6.07 and Axe FXII Firmware 9.0 Full Release. The tutorial assumes that you already have basic Cubase knowledge and will show how to use Cubase to automate Bank, Pre-set and Scene Changes.
(Scene Changes are available in Firmware 9.0 and later) Why would you want to do this? There could be a couple of reasons to automate changes from Cubase to the Axe FXII.
You don’t own an MFC-101 or similar foot controller. You do own an MFC-101 or similar foot controller but want to use a DAW as an alternative when in a studio situation.
For playing along to a backing track and selecting a different pre-set or scene for the solo for example. For playing along to a track you are working on and want to automate a pre-set or scene to kick in at a certain point in the track. When re-amping to automate the pre-set or scene to use for the chorus or solo for example There may be others but the above are the main reasons I can think of to do this so without further ado here is the how to. Setting Up The Axe FXII as a Midi Device in Cubase This is the first thing we need to do as if the Axe FXII is not set up as a Midi Device the following steps of the tutorial will not work. Ensure the Axe FXII is connected to the computer via a USB cable into a USB2.0 0r compatible port. Power up the Axe FXII. Start Cubase Note: The USB Connection is used to transport the Midi information.
If for some reason you use the Midi In port of the Axe FXII for this it will still work but this guide doesn’t cover setting up alternative connection scenarios. However as long as you take care of getting the midi connectivity set up the Cubase part of the guide is the same. Open up Cubase and the project you want to work with. Open up Midi Device Manager Devices/Midi Device Manager.
Click Install Device. The Add MIDI Device window opens select Define New and click OK. The Create New Midi Device opens, give it a name Axe FXII as indicated in the red circle and click OK. The Axe FXII Device Window now opens.
Note that all midi channels 1-16 are added. If you are using the default midi channel of 1 for the Axe FXII, highlight channels 2-16 and click the delete key of your keyboard to delete them as they are not needed. After deleting channels 2-16 click the + button indicated by the blue arrow and it can be verified that only Channel 1 is available. Close the Axe FX II device Window. It can now be seen in the Midi Device Manager, that the Axe FXII is now installed as a Midi device.
In the output section shown underlined in red select AXE-FX II Midi in. Close the window. The Axe FXII is now installed as a Midi Device that Cubase can control. This will now be available to all projects in Cubase. Add Midi Track The next set of steps is in the project where we want to add automation of pre-set changes we need to add a midi track.
In Cubase open the project if it isn’t already open. Right click in the area shown and click Add Midi Track Click Add Track The track now exists but has nothing in it.
Using the Pencil tool draw in the midi track just added from start to finish of the track. This is step is important as otherwise the next steps for adding changes to the Midi Track won’t work. With the midi track selected, set the Midi in and out as shown in the red circle in the diagram below. Not connected on this track we don’t need to receive any Midi. On the output select Axe FXII Midi in. We are sending via the Midi Output of Cubase to the Midi in of the Axe FX II, and make sure 1, is selected for the midi channel.
The In Place Editor So that when we add events such as Program changes or CC messages for Bank or Scene changes add the In Place Editor to the midi track. With the midi track selected go to Midi/Open In-Place Editor shown in red.
(Ignore List Editor for now) Now the In-Place Editor will be visible in the midi track Left Mouse click the little grey square Velo which is short for velocity. Then click Setup In the Midi Controller Setup dialog use the.