I have a single MIDI file that has multiple tracks of instruments. I have a .cpr template (Cubase 14 Pro) that has a matching number of instrument tracks each loaded with an instrument corresponding to a respective track in the MIDI file. But these instrument tracks have no MIDI data in them. When I import the single MIDI file into the project that has the template installed, I get multiple MIDI tracks appearing BELOW the instrument tracks. I believe I can copy each such MIDI track once it is in the Project to its corresponding instrument track. But is there any way during import to automatically make each track in the single MIDI file go into its corresponding instrument track ? It is very tedious to copy each MIDI track once its been imported into my Project (via importing the single multitrack MIDI file) into its corresponding instrument track.) Or is there some other way to avoid having to copy each MIDI track into its corresponding instrument track ? -Bob
Unfortunately importing a MIDI file into Cubase does not work as you would like. It assumes that HALion Sonic which is a 16-channel MIDI multi-timbral instrument will be able to meet your needs since it is fully equipped with all the prerequisites related to the MIDI standard.
However, this could be the subject of a feature request for a future version of Cubase. It could work like this:
1 - Cubase detects that the MIDI file contains 10 MIDI tracks and it is able to know the nature of each track, i.e.: bass, guitar 1, guitar 2, drums, etc.
2 - It offers in a dialog provided for this purpose to either import the MIDI file as is (therefore inserting HALion Sonic with the existing MIDI tracks) or to create an Instrument track with the plugin of our choice and associate this instrument track with one of the MIDI tracks of the file. However, this alternative could pose a problem with the various CCs contained and associated with a MIDI track, because not all plugins have a standard MIDI implementation.
Currently, the way importing a MIDI file works with Cubase ensures compatibility that meets the requirements and standards of the MIDI implementation. This means that a file can have any origin, if it respects this MIDI implementation, the file can be imported without problem.
Many thanks for the time and cogent response Rene.
I saw many criticisms of CB being way behind the times on this, especially for such a respected and long popular platform seeking to become “PRO” as now designated with Cubase “PRO”. But I nevertheless wondered if I was missing something and thankfully I’ve now been assured the answer is “NO” and been spared wasted time searching. THANKS !
Which leads me to a related question: How would YOU most efficiently go about solving the problem of linking the 10 instrument tracks assigned to instruments in the template I imported with their corresponding 10 MIDI tracks of data I subsequently imported ?
I’m kind of a newb and am about to start researching how to mass copy all 10 MIDI tracks into the instrument tracks to maintain their respective alignment. Or how to mass convert 10 MIDI tracks to instrument tracks (if that’s even possible). Or … Or…
Again, many thanks for responding !
Best,
Bob
I wouldn’t use a template at all. I would use the other route. Importing the midi file to an empty project and replace the instruments with alternatives. It is possible to use presets on his.
And there is no need to convert midi tracks to instrument tracks.
BTW holding SHIFT during drag&drop will fix one direction of movement. If you drag up or down the timeline position is locked.
There is no real solution to the current situation. Importing a MIDI file is always linked to HALion Sonic (VSTi Rack). If I remember correctly, the export order of the tracks is preserved during import. Considering this, the idea of using a (multi-timbral) preset in HALion Sonic could save some manipulations. The track settings when exporting must match the settings of your preset(s) in HALion Sonic, otherwise I don’t really see the use of it.
The real solution would be for Steinberg to implement a MIDI import panel appearing every time a .mid or .midi or .kar file is opened in Cubase. In this panel, the user could have better control of the MIDI import by selecting the existing tracks in the file and applying settings to them that could be linked to HALion Sonic with MIDI track or even choose the VST Instruments we want. Having the ability to move a track vertically, thus redefining the order of the tracks which would ensure better compatibility with presets in HALion Sonic.
It is certain that the implementation of such a panel is not as simplistic to achieve as the description I make here. But I am convinced that the engineers at Steiberg would know how to do things brilliantly.
Now, is this a priority? I don’t think so, however, we can always request it as a feature request.