6 MIDI import issues
1) open attached 12T-trimmed1.mid
2) playback, notice that it was playing back with the ties problem (see issue David created for me).
*3) notice the score shows "Trombone" and "Violin", but it was both played using default (piano), i.e. SF instruments not being used.
4) File > Parts, New, click the 2 instruments, create part, OK. Click the new tab created. Playback. Now it is using the actual SF instruments!
*5) The staff labeled "Trombone" sounds like trombone. Don't get too excited that the staff labeled "Violin" sounded like piano. Check the MIDI file itself and you'll notice that actually it IS a piano track! In other words, MIDI import got the words "Violin" incorrectly from the MIDI file. (Background: this MIDI was created by Sibelius, which mangles MIDI data badly -- the order of the instruments could be different from the order of the text/tracks...)
*6) Notice that it was created with a Treble Staff and not Grand Staff. That's the case even when the MIDI import reads it as text "Piano" and identify playback with piano (with a longer piece).
*7) Notice the Violin score has a different key signature from the Trombone staff. With a longer piece with 5 instruments, most of the instruments have different key signature! That's very confusing when they are not transpositional instrument. (As a side note, this is a dodecaphonic piece with all 12 notes occur. No key signature was specified in the original score.)
*8) The composer is picked up, but not the title of the piece. The composer is put in a weird location on the score.
*9) There is no double bar at the end.
10) Save the score as .mscz. Close all scores/parts. Open the saved mcsz. Playback. Notice the playback instruments are now correct. This shows item 3 issue was caused by MIDI import not initializing instruments. All the other issues noted previously remain.
The 6 issues are marked with *. I think *8 may have been reported by someone before, and obviously workaround is possible, so it is low priority for me. Item 2 has no * as it was reported already. Sorry I first reported the issues on the forums as I was not aware of this issue tracker as a newbie. Thanks for listening and a great program!
| Attachment | Size |
|---|---|
| 12T-trimmed1.mid | 2.12 KB |
Comments
Environment Info: r1667 (0.94+) my first installation. Windows XP, 1GB RAM, trying different Soundfonts. MIDI score exported from Sibelius 4 (no MusicXML export).
On 2nd thought, the score does not have to be implemented as ties at all (see item 2). For example, Each time we see a note from MIDI that is stacked on top of another unevenly that would otherwise require a tie, we implement it as a 2nd voice. Since we have up to 4 voices per staff. That should take care of most needs. Chords does not require a separate voice at all, since it stacks evenly. I tried this representation on MuseScore via manual input, and it sounds correctly. Don't know if this approach is easier or harder to implement. At least it should be easier to read than ties. (User can interchange voices if it's not exactly what they want to see.) Just an idea...
r1723: The workaround described above to get correct instrument sounds no longer works. (The ties problem reported elsewhere was resolved.)
Expected Behavior:
a) MIDI import will receive correct instrument sounds (when SF2 was selected).
b) MIDI import will give same key signatures (considering transposing instruments) to all instruments.
c) MIDI import will get the correct instrument text attached to staff.
d) MIDI import will generate grand staff for piano.
e) composer text is picked up.
f) double bar at the end of score.
Current Behavior:
a) only piano-like sound for all instruments.
b) Nearly every instrument gets a different key signature not related to one another.
c) MIDI import got the wrong instrument text attached to staff.
d) MIDI import generated treble staff for piano.
e) composer text is not picked up.
f) single bar at the end of score.
I'm on revision 2959, and here's what I get upon import:
My score shows Bassoon and Piano (not violin) as a grand staff (but with bass clef on top and treble on the bottom!) The "right" soundfonts were used for me, I think. I heard a bassoon and a piano. So would the issue now be just with the importer?
I attached a picture of it. It looks kinda messy when compared to my music player playing it. I have plugged this into LMMS and totem, and both see it as bassoon and piano. Is that the correct instrumentation?
There is still no double bar at the end.
I didn't get either the title or composer.
Hello,
I have just downloaded MuseScore (1.1, 4611) so that I can convert my midi files to manuscript. I am coming out of Reason 6. I am running Windows 7 pro. Every time I have tried to open a midi file, the program automatically closes. I seem to be able to work through the program if i do not try to open a midi file, but that is not what i need. Any ideas? Thanks.
Just to cover the original report :).
For shlaw's problem, see: #14446: Opening a MIDI file causes crash
In the current nightlies I found that some of the reported and other issues are present:
- no double bar line at the end - but if it is not an end of the piece (fragment) - is there a need in such double bar line?
- the MIDI file contains lyrics track, with track name = piece title and lyrics = composer, maybe I'll add a support of the title of such kind if there is no "official" title in the MIDI
- no copyright and different keysig, compared to the png above (but maybe it's another, similar score)
@trigger
- no double bar line at the end : yes. I would put a double barline at end, always. It's easy to remove and in 95% of the case, users will need to add it.
- trackname and lyrics with title, I would not generalize this except if you have evidence that it happens often. What often happen is that the first track is reserved for metadata but I don't think there is a way to know where the title is.
- Copyright is particular metadata even in MIDI http://www.sonicspot.com/guide/midifiles.html so if Musescore finds a copyright event in the first track, it seems reasonable to use it as copyright metadata.