MIDI Export
I am exporting a multi-instrument score to a MIDI file. The intention is to play this in a sequencer application.
When I open the file in the application, the uppermost track appears with a Meta label and cannot assigned to an instrument. Is this a problem with Musescore? Is it something to do with the first track being exported as Track Zero?
Comments
Which OS?
Which MuseScore version?
Please attach the files concerned both MIDI and MSCZ for examination.
Hopefully we will then be able to shed light on the matter.
In reply to Which OS? Which MuseScore by ChurchOrganist
Please find attached the MSCZ and MIDI files, as requested. The OS is Windows 7.
I exported a WAV file from Musescore and the result was excellent. I used custom SF2 sounds for the instruments.
I wish to use the audio file as a backing-track for my choir, but it would be useful to have a scrolling cursor on the score while I am conducting. The continuous mode in Musescore 2 would be ideal for this, but I don't really want to rely upon a beta version during performance!
The sequencer that I have in mind is MIDI Maestro. This is optimized for live use, but it gives the first track a META label that cannot be edited.
In reply to Files as requested by Wyvern
It doesn't even really play inside MuseScore either, only the 2 percossion staves play.
Ah, I see some other instruments (the singing voices) had been muted!?!
Still even after unmuting those Handbells and Piano don't play.
Hmm, I got them to sound, by adding Piano and Handbells afreash, copy/paste their notes across and removing the old instrument.
In reply to It doesn't even really play by Jojo-Schmitz
Hi JoJo,
I used custom SF2 sounds for the Handbells and Piano, which probably explains why they wouldn't play when you tried.
In reply to Handbells and Piano by Wyvern
Ah, thanks for the clarification.
In reply to Files as requested by Wyvern
Hi Wyvern :)
I've had a look at the MIDI file.
There are meta events at the beginning to send key and time signature to the sequencer which are obviously being interpreted wrongly by MIDI Maestro.
I've loaded the SMF into Anvil Studio AND Sonar X2 and both interpret track one normally, so it looks as though you need to get onto MIDI Maestro support on that one.
The other problem is that you've run into this bug amongst others with MIDI export :)
#11175: Drums don't export to MIDI
Those have now been fixed so try a Nightly build and see if your drums are there in the file :)
I'm trying the demo of MIDI Maestro so I'll let you know :)
EDIT: I've just tried a demo of MIDI Maestro with your MIDI file, and couldn't see any problems. Are you sure you had Edit mode switched on?
In reply to Hi Wyvern :)I've had a look by ChurchOrganist
MIDI Maestro places the handbells in Track 0 and treats them as META data. Although the Track can be re-named, any editing is "greyed-out" so the track cannot be re-assigned to an instrument.
I will contact MIDI Maestro support for advice.
Incidentally, I am using a Hot Hand Ring to control the volume and tempo of MIDI files. This allows me to add some human interpretation to backing tracks while directing the choir.
Kind regards,
Stephen
In reply to Hi ChurchOrganist :) Edit mode is on! by Wyvern
No - MIDI Maestro puts the handbells in Track one and there is no problems at all with editing.
See screenshot
![MidiMaestroSS.png]()
Maybe you have a different version?
In reply to No - MIDI Maestro puts the by ChurchOrganist
The only part with four single crotchets in the first bar is the piano. However, the notes are middle C and the A below it. The handbells are much later!
I have taken a screenshot of what happens on my system:
![Screenshot_.png]( "Screenshot_.png")
It appears to be META data on Track 0 mixed with the handbell notes.
As you suggest, I will check the version that I am using.
Kind regards,
Stephen
In reply to I'm even more confused! by Wyvern
I should have mentioned that I added the four single crotchets to see if the track was editable for MIDI events!
Sorry about that!
In reply to I'm even more confused! by Wyvern
OK I've worked out why.
You attached the wrong SMF - the one you had exported from 1.3
So of course it worked!
I've just tried it with a fresh export from 2.0 beta and getting exactly the same symptoms.
It's possible that the RPNs are adversely affecting it - they were causing problems in Sonar.
See this thread: http://musescore.org/en/node/37431
I'll try with my latest self build which has removed the RPNs from MIDI export and see if that solves the problem, then report back.
In reply to OK I've worked out why. You by ChurchOrganist
I have been shifting between versions 1.3 and 2.0 using Music XML to try to get things working. Obviously I got mixed-up.
What is an RPN? I only know it as "Reverse Polish Notation" - used in early HP calculators!
I ran a version 1.3 midi file through Anvil Studio, corrected a time signature, and fed the file to MIDI Maestro. The latter program showed Track 1 as a Meta track with three initial entries, otherwise it was empty.
Track 2 had the handbells, with both voices together.
Thank you for your continued help.
In reply to Sorry about the export from MS 1.3! by Wyvern
RPN stands for Registered Parameter Number
These are assigned by the MMA, and are currently only a few: http://en.wikipedia.org/wiki/General_MIDI#RPN
In reply to OK I've worked out why. You by ChurchOrganist
OK I can finally do a full report on this, having examined both the 1.3 export and the 2.0 beta export in a MIDI parser.
Removing the RPNs makes no difference at all to the problem in MIDI Maestro.
1.3 exports time signature information in a separate track, and then note events in a series of other tracks for each instrument.
2.0 beta exports time signature meta events in the first track along with the instrument note events.
MIDI Maestro obviously assumes that time signature meta events will be in a separate track and marks everything else on that track as meta events, although accessing the Event list shows them as the correct events.
Both Anvil Studio and Sonar X2 correctly interpret time signature meta events from 2.0 beta SMF export.
MIDI MAestro support should be informed of this errant behaviour in their application.
Whilst it is considered good practice to include time signature and tempo information in a separate track sequencers should not presume this behaviour.
In reply to OK I can finally do a full by ChurchOrganist
Your detailed investigation and expertise are much appreciated.
I will forward your recommendations to MIDI Maestro support.
Kind regards,
Stephen
In reply to OK I can finally do a full by ChurchOrganist
Please find attached a working MuseScore 2.0 file, and the MIDI file that it creates.
I saved the MuseScore 2.0 file as a Music XML file, and imported it into MuseScore 1.3. I then created a MIDI file using MuseScore 1.3. This version of the MIDI file is also attached.
It is clear, merely on size alone, that the MS 2.0 MIDI file is incomplete. In fact, it seems to comprise a single track with the META data we discussed, followed by the Handbells note data. The other tracks are empty.
I assume that MS 2.0 MIDI functionality is still under development. I will, therefore,use the XML>MS 1.3 method to create MIDI files until advised otherwise.
In reply to MS 2.0 MIDI Export by Wyvern
That is a known problem and has already been fixed.
#35276: Exported MIDI doesn't feature all tracks
#11175: Drums don't export to MIDI
Try the latest nightly.
In reply to That is a known problem and by ChurchOrganist
Kind regards,
Stephen
if it's MusesScore 2.0 Beta, then it's probably Musescore's problem, it's still in Beta after all. I never have had any problems exporting MIDI in MuseScore 1.3, using Cakewalk software.
If it is a Musescore 2.0 bug, you should
a) find out for sure if it's a bug and report the bug
b) export it into music XML and open it in Musescore 1.3 (2.0 and 1.3 are not backwards-compatible (I'm pretty sure), so you'd have to export it to music XML) and export to MIDI with Musescore 1.3, or open the mXML in the sequencer if you can.
c) or just wait for the development to proceed and fix the bug
d) or maybe make multiple MIDI files with the tracks in different positions (example:first export trumpet, trombone, tuba, then export trombone, trumpet, tuba and just importing both MIDIs into your sequencer and deleting the tracks you don't want)
Even if this doesn't solve whether there is a bug or not, I hope it's helpful!
In reply to Options if it is a bug by joseph.branden…
The first track in the MuseScore 2.0 version is a two-voice hand-bells part. I have used a custom SF2 soundfont to render the sound and it works well when played directly.
I exported the the MuseScore 2.0 file as music XML and opened it in MuseScore 1.3. The hand-bells part was then played as a drum-set with very strange results!
I next changed the hand-bells part (in MuseScore 1.3) to a standard GM piano and saved it as a MIDI file.
I imported the MIDI file into another notation program that gave the following error: "Bad meta event FF [0x0a] d. Next errors will be ignored.
The notation program did show the various staves correctly, but the first "hand-bells/piano" staff had merged voices and incorrect timing.
Thank you for your interest!