Empty beats

• Jun 18, 2012 - 16:42

I've imported a midi in musescore to use for sheet music and backtrack. The problem is that some of the beats turn out empty. There no rests, just nothing. And I'm unable to add any notes to these parts. Does anyone know how to solve this? If so I would be ever grateful.


Comments

In reply to by Jonnvoll

Looks like that with measure 15that "C AltoOcarina" just disappears?
The same thing happens in measure 29 to "guitare" and in measure 31 to "basse" and "instrument trad"

Could it be that in the midi file you imported those instrumnets stop to exists at these measures? I don#t know enough about midi...

Can you attach the midi file here too?
If you try to import it in the latest nightly build (see the download pages and scroll down a bit), do you see the same problem?

I've opened the score you attached with 1.2 and find it very strange - 4 different key signatures for a start!

There are also obviously invisble tempo markings to as the pulse is not consistent, and evidence of corruption.

We really need a copy of the original MIDI file to examine to see why this is happening.

In reply to by Jonnvoll

I don't know enough about MIDI files to say what might have caused this, but it appears the result of the conversion is corrupt, and that's why those bars are empty, and why you can't edit them. That is, there is a bug somewhere - normally, those bars would have rests, and you,d be able to edit them. The answer probably is, there is nothing you can do to edit those bars, except to figure out how to regenerate the file differently so it isn't corrupted.

In reply to by Jonnvoll

I opened the MIDI in Sonar 3 last night just before I went to bed, and discovered that the reason for the empty bars is that the tracks concerned do not go up to the end marker, but finish at the point where they have nothing more to play.

I would have expected MuseScore to add rests to the score to compensate for this, but apparently it didn't, which means there is an error in the MIDI conversion algorithm in 1.2.

Glad to hear that the file imports OK in 2.0.

It is quite common to have MIDI tracks that do this - in my backing track programming days I would use clips of MIDI data and copy and paste them as needed, and would very often end up with blank spaces in the track for an instrument - so I'm surprised the algorithm wasn't correct.

Do you still have an unanswered question? Please log in first to post your question.