Hopefully this is a simple fix. I have a MIDI track that I moved to an instrument track. I want the last note of the song to be longer so I extended the last notes to bar 112 rather than 111 (where they initially ended). Problem is, when I play it back, even though it shows the note spanning 2 bars, it still only plays for the duration of the first bar. I have reopened the project (on multiple PC’s) and the issue still exists.
Is this expected behavior and I did something wrong to get it to play both bars? Is there another quick way to get this to work?
Is it possible the instrument’s sound decays faster than is needed to go beyond the one bar? To give an extreme example, if the sound were something like a xylophone, it wouldn’t likely even last one bar, no less two, so holding the sound out an extra measure would make no difference. In a less extreme case, there is a virtual fiddle I use that has two modes of dealing with note length. One mode lets the sound die out naturally, while the other loops it so you can hold it as long as you like. In the latter case, extending a note for an extra measure would keep it going, but, in the former case, odds are it would not (though it would depend on how long the measures were versus the natural decay timing of the fiddle).
The only other thing I can think of off the top of my head is if there is some sort of volume automation going on, be it in the MIDI data (e.g. CC11 or CC7, or perhaps CC1 for instruments that use mod-wheel for volume), or on the audio side (i.e. fader automation).
Maybe I’m completely misunderstanding what you’re asking–but from the screenshot I can see that the MIDI part ends with bar 111, because that’s where the dark grey section ends–so even if you extend the notes through 112, you aren’t going to hear them until you also extend the part.
You just need to mouse over the MIDI part at the lower corner, from the far right, and drag it to the right another bar.
In my experience, the MIDI part boundary is only a consideration for hearing the note if the start of the note occurs prior to the start of the part (i.e. left boundary) or after the end of the part (i.e. right boundary). Notes that start within the part but continue after the end of the part are still heard in their entirety. (This is something I see a lot when comping instrument tracks from multiple takes.)
My interpretation of the original question was that the C4 and D#4 near the end of the clip used to be one measure long (i.e. ending at the start of bar 111), but then were extended by an additional measure (i.e. ending at the start of bar 112 as shown in the screenshot), but, for whatever reason, the note still only sounded as if it were one measure in length, with the sound ending at the start of bar 111. If that interpretation is correct (and it may not be), then the notes are fully within the part, so it wouldn’t even matter if Cubase did cut off notes at the end of a part. That is why, in my response, I was speculating on other reasons a note’s sound may cut off prematurely, be it the design of the sound itself or effects of other MIDI data on the note where that other MIDI data may not have been adjusted to take the note’s extended length into account.
To clarify, I have several instruments doing this and it’s something I have seen with Cubase 10, 12, 13, and now 14… it’s fairly consistent. The instruments that I am using on these are strings. If I shorten the instrument, the sound duration shortens as expected and if I extend them to the original duration that works as expected as well. It’s when I go beyond the original duration that is the issue.
There’s no automation on these channels and I removed all other automation (which shouldn’t have impacted this anyways) and it didn’t make a difference.
The ‘fix’ that I ended up using was to re-export the MIDI from the original application with a longer duration.
The issue that I was having is that the original MIDI that I imported stopped at the beginning of bar 111. I extended it to end at the beginning of bar 112 (I guess in hindsight I should have posted before/after images) but no matter how much I extended the notes, it would still end at the beginning of bar 111. However, making the duration shorter worked just fine and then extending it again to the original value was fine as well.
I eventually ‘resolved’ it by updating the score in my other app to have longer notes at then end and then re-exporting/importing it.
I’m glad you found a workaround. I have to say, though, that it sounds pretty bizarre. I wonder if somehow the other app was adding some MIDI information that wasn’t apparent in the key editor. My first thought as if it did something like add a hard CC7 (volume) value of 0 at the end of bar 111 (and 112 once you extended it in the other app). But, if you removed all CCs from the track, that should rule that out, and I’m clueless on what other sort of MIDI data (if any) might do a similar thing.
It might be interesting to see whether, if you now try extending it to the start of measure 113, it still cuts it off at measure 112. If so, it might then be interesting to look at the track in the List Editor to see if there is something specific happening near the end of measure 111 or at the start of measure 112.
