I’m exporting MIDI from a track where there are long gaps with no notes. Cubase decides to cut these gaps out and export the MIDI file as multiple events (or regions, or whatever they’re called now). The only way around this is to insert a long midi note to bridge the gap. This is clunky and ridiculous. Has it been fixed in a new version??? I’m still on v.10.5.
Hi,
How do you know, Cubase is exporting it like this? In the SMF (Standard MIDI File), there are no MIDI Parts defined at all.
I’m sorry but I have no idea what you’re trying to communicate.
Hi,
I’m sorry, English is not my first language…
How do you know, Cubase is exporting it the way, you described? Where do you import the MID file to, to see the result?
There was a two letter typo
He’s referring to the MIDI engineering specification:
1 Like
Yes, when I import the exported MIDI file, I get two separate regions.
Hi,
It can still be on the import side, not export.
into what program? When troubleshooting it is necessary to give each detail. Even though *you * might know, other don’t.
OK.
- I programmed a MIDI part in Cubase 10.5 on a Windows 10 computer.
- The part has a section in the middle where there are no notes for approximately 50 bars.
- I export the MIDI track as a MIDI file, ensuring the entire length of the track is selected in the timeline.
- I import said file back into Cubase 10.5. (a new blank session).
- The resultant MIDI track has two MIDI regions - the 50 bar section with no notes is blank.
Any other info you need?
Hi,
We still don’t know, if the MIDI Parts are divided during the export or the import.
In any case, I would consider this as a feature. I can’t imagine, this is a bug. There must be a specific code to do this.
OK I have to revisit this as it’s still an issue even in Cubase 13, and it’s severely affecting my workflow.
Just to reiterate the problem:
I have a MIDI track that has several sections where there are no notes for more than a bar. If I export this file, and then import it, the result is mutiple MIDI events.
Yes, I am selecting ‘Export Locator Range’.
I’ve tried to import this file in 3 different DAWs; Cubase, Logic, and Pro Tools, and I get the same split event problem.
This is particularly troublesome when the MIDI track does not start at the beginning of the project because to someone who isn’t familiar with the song, they have no idea if the track is lined-up properly.
Can anyone help?
Here is a screenshot. The top MIDI event is the track that is exported, and below it is how it looks after being imported.
Hi,
Thank you for the screenshot. It helps to understand.
But I don’t see any issue. Cubase (and other DAWs) just splits the MIDI Parts to multiple parts, if there is a long gap. The MIDI data are exactly the same before the export and after the import.
Thanks for the reply.
Are there any helpful people who have any ideas?
First of all: This is a User forum, no need to be so rude when people are helping you. Sometimes I am just gobsmacked.
Now, looking at your screenshot: How did you manage to dislocate the imported MIDI track in a way that it does not line up with the original MIDI track? I can’t tell because you are not providing any helpful details…
It is as simple as that: select the MIDI track, set the locators and export File/Export/MIDI File > Range between locators.
Import the file back in any given project and each event will sit exactly at the right spot. Like it is supposed to do. In other words, no need to know the project.
I could ask: What’s not to like about the gaps in between? This way it just takes one look and you know right away what’s going on in the track. However, I will not ask. If you prefer to have one long MIDI part - have at it. Just take the Pencil Tool and draw, take the Glue Tool and glue.
Hi,
@Reco29 , I don’t see any dislocation. I can see only the gap between the two MIDI Parts. Am I right, @jmauz ?
There is nothing wrong on this gap. The DAWs do it this way for better further editing. You can easily glue them.
As I mentioned in an earlier post, when I send MIDI tracks to other people who use different DAWs, often times they get confused and nervous when they see this behavior. Then they have to call me in a panic asking why the MIDI tracks “aren’t lining up” and I have to explain to them this is how Cubase does it. This takes time and creates unnecessary stress.
If you’ve ever worked on high pressure projects with tight deadlines, you’ll understand that all must be done to keep editors, producers, and directors calm. Telling them to ‘just glue it together’ isn’t professional and adds steps to their workflow. Again, unnecessary stress.
Just an FYI - this does NOT happen to me in C14P or N13 tested with both Ableton Live 12 and Logic 11.1.2 (on an iMac Intel MacOS 15.4.1). All component parts are imported as single midi “events.” The only difference I see if that Ableton will create an event/region beginning at the timeline while Logic places “cropped” regions where the first midi “event” (datum) exists. But I don’t see what you’re seeing even after importing it back into C14P or N13.
I’ve tried as many combination of exporting with/without markers and/or the locator ranges.
I should point out this is also the same behavior for exporting from Live and importing into Logic (though Live you have to export them individually).
This must be frustrating, particularly when it becomes more of an “emotional” issue than a “technical” one. Honestly, for what it’s worth, if the only problem you have with high-stress deadlines where you’re forced to actually exchange MIDI files is a highlighted bar showing or not showing, I’d call that a good day. Tempo/signature changes, instrument changes, quantization issues, etc would be what I’d worry about, but that’s a different thread…
Maybe you can post a test MIDI export and I’ll test it from my side.
2 Likes
Thanks for the 411 Thor! I guess it might be time to upgrade!
And yes, your perspective is accurate - this issue pales in comparison to the plethora of things that go wrong while collaborating with people on other DAWs. That said, when everything else is corrected, this seems to be a consistent nagging issue that won’t go away.
Hi,
This is how several DAWs work like. This is not on Cubase side, this is not on Cubase-export side. This is, how the DAWs import the MIDI file(s).
In the MIDI File, there is no instruction to say “split-MIDI-Parts On/Off”. It doesn’t exist in the MIDI File. It’s up to the DAW how does it import.