How to prevent Cubase 12 from making new track when midiparts are dragged to existing midi track?

How to prevent Cubase 12 from making new track when midiparts are dragged to existing midi track?
Best regards.


If you mean you drag the MIDI Part below the existing tracks (in the arranger area), it’s not possible to disable the function. Sorry.

1 Like

Its when I try to drag e.g. a drumfill-midi part to a drum-midi track. I just want to drop it at the position in the drumtrack, where I want it to be. But then: New track is made with the midi part, and then I have to drag it to the drum track - and then I have delete the newly made track…just anoying

From where do you drag the MIDI part initially?
I cannot reproduce the problem yet.


If you drag in the given track only, you can hold the Ctrl/Cmd down to Constrain Direction.

I drag mostly from mediabay…
But midifiles draged from explorer does the same

Hi @erikpre

A short video would be very useful to better help you.

You can try to increase this setting and see if it improves your situation:

Drag Delay

Allows you to set up a delay in ms that is used when you move events. This is useful to avoid accidentally moving events when you click on them in the Project window.


1 Like


If you drop it to the existing track, the MIDI Part ends up in the given track. If you drop it below the existing tracks, it creates a new track.

Using grooves from “Handy Drums” you get grooves both in “midi type 0” and “midi type 1”
Using midi type 0 a new miditrack is automatically made, when you drag a midi file from mediabay (or explorer) to a existing miditrack. Using midi type 1 the midifile you drag is placed exactly where you want it in the existing track. (Never heard of the different midi types, but never mind.)


Interesting… I would expect the other way around. The main difference between SMF0 and SM1 is, that SMF1 allows multiple tracks. In SMF0 all channels (all MIDI data) are in one track.

But it somehow rings a bell to me. I think Cubase tries to dissolve the Tempo data, therefore it expects 2 tracks. Something like this…

In any case, I’m glad, you found a solution, and thank you for sharing!