Midi file not importing
I am trying to import a midi file which I created in garageband and then exported to Logic Pro to then export again as a midi file. When I try to upload this logic midi file into Musescore 2.1, it gives me this: Load failed. Bad midi file. MThd expected. I am able to upload this same file into Musescore 1.2 although it is extending notes that show up as tied notes. I've included the Logic Pro mid file and the mscz file from Musescore 1.2. Any suggestions? Thank you.
| Attachment | Size |
|---|---|
| Sara's Song vocals.mid | 1.89 KB |
| Sara's Song vocals.mscz | 5.89 KB |
Comments
Why using the outdated MuseScore 2.1 (and 1.2) rather than the latest 2.3.1 (and 1.3)?
2.3.1 does import that MIDI file without problems.
In reply to Why MuseScore 2.1 and 1.2… by Jojo-Schmitz
One of my Macs is old--10.6.8--and I have to use the 1.2 with it. However, I was wrong about using the 2.1 on my newer Mac; it's actually 2.3.1. And the midi file has suddenly opened in Musescore 2.3.1 although it is stating that it is a corrupted file. And the file still shows unnecessary tied notes that were not there on the original midi file in GarageBand.
In reply to One of my Macs is old--10.6… by VivianSlade
MIDI is not a notation format but a playback format. It's lacking lots of information that would be necessary to guarantee good notated results when moving files between programs. So it's completely normal that different programs might display the same MIDI file differently.
When I import your MIDI file into 2.3.1, there is no corruption, and no unnecessary tied notes. Only when I load the MSCZ file do I see corruption and unnecessary ties. That's because 1.2 had a number of bugs - long since fixed - that would cause corruptions that it was unable to detect (while 2.3.1 does detect them), and also it's MIDI import is nowhere near as sophisticated.
So basically, stick to 2.3.1 and you should be fine. But if you do find yourself being forced to use 1.2 sometimes, just realized sometimes it will create corrupt scores you will need to fix later when loading into 2.3.1. See https://musescore.org/en/node/54721 for advice on this.
As for the ties, they show up because you overlapped your notes slightly in an effort to play legato. MuseScore 1/2 is being very literal about this and using ties to show you the overlaps. MuseScore 2.3.1 is much smarter about this, and it will ignore slight overlaps to produce more readable results.
If you find yourself needing to import MIDI files into 1.2, try "quantizing" them first. Not sure if GarageBand provides that option, but basically this means cleaning up the overlaps and making other changes to make it easier to convert to notation.
In reply to MIDI is not a notation… by Marc Sabatella
@VivianSlade:
See your repaired score: 1Sara's Song vocals.mscz
In reply to See your repaired score: … by cadiz1
Thank you for help, Cadiz.
In reply to MIDI is not a notation… by Marc Sabatella
Thanks so much, Marc.
In reply to One of my Macs is old--10.6… by VivianSlade
Mac OS X 10.6+ 64-bit can cope with MuseScore 1.3, only Mac OS X 10.6+ 32-bit Core Duo stops at MuseScore 1.2.
In reply to Mac OS X 10.6+ 64-bit can… by Jojo-Schmitz
Thank you, Jojo. Very kind of you to respond.