Exporting multiple midi tracks like the procedure for exporting multiple audio tracks?

[a.t. vish]

I have not seen a way to export multiple midi tracks of a project the same way one would export multiple audio tracks.  I dont want just ONE midi file with seperate track info (MIDI Format 1).  I have, say, 20 seperate midi tracks in my project, and I want to export them, and end up with 20 seperate midi files, so I can import them separately into another device that utilizes midi commands.  What am I missing?

 

 

[OutrageProductions]

You can select all clips in a MIDI track, bounce them into one clip event, then drag & drop the clip to a folder in the browser or to a directory in Windows File Explorer (like desktop et al) one at a time.

Not sure what happens if you try to do that with multiple tracks simultaneously. 

Might be smart to make sure that all tracks start at bar 1 beat 1 so they will all line up in new project. 

Edited January 14 by OutrageProductions

[Sock Monkey]

Midi is totally different than audio. 
in other words there’s no option to export midi as stems. Only Audio. 

Most Daw’s you simply drag the midi from a project to a windows folder. It’s all a typical Window move like any other data. So you can drag a bunch of data by using Ctrl . 

Edited January 14 by Sock Monkey

[David Baay]

17 hours ago, OutrageProductions said:

Not sure what happens if you try to do that with multiple tracks simultaneously. 

Dragging out a selection of multiple clips will get you one file per clip, whether separated by time, tracks or lanes of a track.

[a.t. vish]

Ya, thanks for the info.  The next obstacle is the time grid.  That is, each of these midi files line up with an associated audio clip in my project.  When I export the multiple audio files, I need the midi data that is synced to also export in some way that I can drop into another device and have the midi line up correctly with the associated audio.  I can export audio in various ways so that each audio file starts at time '0'.  But I cant think of a way to also export the associated midi so it is also at time '0', thus lining my commands up with the audio file.  I think I will have to simply transfer each individual set of audio and associated midi to a new project, starting at the beginning of a track, and export each set individually for this to work.

[msmcleod]

7 hours ago, a.t. vish said:

Ya, thanks for the info.  The next obstacle is the time grid.  That is, each of these midi files line up with an associated audio clip in my project.  When I export the multiple audio files, I need the midi data that is synced to also export in some way that I can drop into another device and have the midi line up correctly with the associated audio.  I can export audio in various ways so that each audio file starts at time '0'.  But I cant think of a way to also export the associated midi so it is also at time '0', thus lining my commands up with the audio file.  I think I will have to simply transfer each individual set of audio and associated midi to a new project, starting at the beginning of a track, and export each set individually for this to work.

The easiest way is to just save your project as a Standard MIDI File.  The positions of all of your MIDI clips will be retained within that.

Alternatively, you could add a text event at time zero in each MIDI clip.  You could then drag/drop the clips to a folder.  

[a.t. vish]

The on going saga...so I jumped through a million hoops to finally get audio files and midi files exported with the correct time stamps to load into another device.  But now I see that the 'Patch' changes in the midi data I had in my Cakewalk project (which triggered a Line6 HXFX to change scenes) are not included in the Format 1.  I need Format 1 because I need the midi to stay with its associated audio tracks.  I cant export 42 midi track individually using Format 0...WTF?  Why would a midi export file not contain this Patch info??  I understand when you reimport it to Cakewalk, it automatically assigns the patch change to the channel, but its an EXPORT file.  Presumably, one is taking it someplace else, other than Cakewalk.

[Sock Monkey]

Did you enter the patch changes in the track header?  That information definitely is stored in midi files. 
Patches entered with in the vst instruments are not included in midi. And midi type 1 is what you need for multiple tracks. Type 0 is all tracks are combined together. 

[a.t. vish]

The Patch info is in the MIDI track.  I attached the screen shot of my MIDI data.  Neither Format 1 nor 0, has the patch data line when I import back into Cakewalk.  I ultimately am not importing this back into Cakewalk, Im importing it into a device that is going to read MIDI and send these patch changes to my HXFX pedal.  I need a Patch change to be included.

[David Baay]

32 minutes ago, a.t. vish said:

Neither Format 1 nor 0, has the patch data line when I import back into Cakewalk

CW should import the initial patch change to the Patch widget and put it back In the file on export.

[David Baay]

On 1/16/2025 at 6:53 PM, a.t. vish said:

When I export the multiple audio files, I need the midi data that is synced to also export in some way that I can drop into another device and have the midi line up correctly with the associated audio. 

You’ll need to insert a dummy MIDI event at time zero in each track - something innocuous like CC123 or CC64=0.

[sjoens]

On 1/16/2025 at 11:19 PM, msmcleod said:

Alternatively, you could add a text event at time zero in each MIDI clip.  You could then drag/drop the clips to a folder.

 

On 1/23/2025 at 3:57 PM, David Baay said:

You’ll need to insert a dummy MIDI event at time zero in each track - something innocuous like CC123 or CC64=0.

For those watching at home, this is important as simply extending the "clip" end to the zero point won't work.  Empty space before the 1st event will be deleted.

BTW, it can be any kind of event so long as something is there to retain the clip length.