iPad with Symphonix Evolution doesn’t show the notes of MuseScore midi files in the correct bars
I prepared a number of midi files with MuseScore 1.3 and exported these to my iPad. On the iPad running under iOS 7.0.2 I can play these files with Symphonix Evolution (Vicario). This app shows the bars and notes for midi files while playing them. But the app has a problem with midi files prepared by MuseScore. It shows the notes between the G bar and the F bar instead of using the correct bar.
Is there a way to correct this problem?
Comments
Is a current nighly build causing the same problem?
In reply to Is a current nighly build by Jojo-Schmitz
I created the midi file today with MuseScore and I played it today on the iPad as well so it is newly build. Is that what you are asking me?
In reply to I created the midi file today by John.Reijers
No, I'm talking about this , a prerelease of the upcoming verision 2.0
In reply to No, I'm talking about this, a by Jojo-Schmitz
Thank you for this idea.
I ran MuseScore in the following versions
• MuseScoreNightly-2013-10-22-1910-178bfe6.7z
• MuseScoreNightly-2013-10-22-1321-e6cbbab.7z
I opened a file in *.mcsz format that I had prepared with MuseScore version 1.3 in both these versions.
Both offered me then only the possibility to store a file in *.mscz format. They did not offer other file formats such as for instance the *.mid format.
In reply to Thank you for this idea. I by John.Reijers
Both certaintly do, although not in File->Save or File->Save As like 1.x but in File->Export
In reply to File->Export by Jojo-Schmitz
Thanks for the additional information. Indeed I could create the midi files by using the Export button. But unfortunately these midi files have the same problem as the files exported from version 1.3.
By the way I made a mistake in the description of the error.
The notes of the tenor party are shown in the vertical direction too low, somewhere between the G staff and the F staff. It looks somewhat as if they are in a place that would be valid if only the G staff would have been used and the G staff would have been in the middle. Furthermore all bows that bind certain groups of notes are missing.
In reply to Thanks for the additional by John.Reijers
Can you share one of the MuseScore files that shows the problem on MIDI export and attach it to a reply here?
In reply to Can you share one of the by Jojo-Schmitz
Here you have a file as requested. As you can see I added the word ‘cymbal’ to the file name in order to discern it from the version made with MuseScore 1.3
In reply to Here you have a file as by John.Reijers
I asked for the musescore file, not the midi :-)
In reply to I asked for the musescore by Jojo-Schmitz
Here it is. This mvsz file was created with version 1.3.
I hope that this will be ok for you. Else I will have to make a new one.
In reply to Here it is. This mvsz file by John.Reijers
OK, so that is a single staff score, the 'instrument' being named Tenor, but using a grand piano sound. Clef being a treble clef 8vb, which is the standard clef for Tenor (but not for piano)
Exporting to MIDI of course keeps mit at a single staff.
Importing that MIDI in a nighly build shows it as the instrument being a single staff grand piano and the notes alternating between a normal treble clef and a bass cleff, which are the standard clefs for that Instrument.
As far as I know MIDI just doesn't carry enough Information for a treble clef 8vb to be detected, just pitches, length, velocity, sound. No way to distinguish e.g. a Soprano from a Tenor, it only sees 'Choir Aahs' in both cases.
In the nightly builds you can tell the MIDI Import to disallow clef changes, but even then it'd still put everything in a normal treble clef, not an 8va one, so all notes down by an octave.
And for your MIDI player to display it as you want, you probably need to cange the clef in the score to a normal treble cleff and move the entire score up an octave? Then it would look right, but of course sound an octave higher...
Unfortunatly the MuseScore Player App for iPad still isn't available (there is one for Android), that should solve the display and the sound problem together, with MIDI you can only have one or the other and even that not completly (e.g. slurs won't show, as MIDI doesn't carry those accross, and lyrics get lost too).
In reply to OK, so that is a single staff by Jojo-Schmitz
Hello Jojo Schmitz,
Thank you for your analysis. Although I know nothing of the programming conventions of MuseScore you gave me the hint to solve my problem.
You made me clear that the settings in the opening menu of the score determine how the notes in the staffs will be exported to the midi file. So in my case, when I want to create a score for a tenor singer, I have to choose as instrument for instance a Tenor recorder. That will result in a score with only one staff and MuseScore will place all notes in the G staff.
I tested this idea with a few notes only and that gave me the result I was looking for.
Unfortunately I could not find a way to change the instrument settings in the opening menu in a completed score. So I have to type the score once more. But at least I know now how to create a correct looking score.
Thank you very much.
John Reijers
In reply to Hello Jojo Schmitz, Thank you by John.Reijers
right-click on a staff->staff properties->instruments, then change it. Or, in this particular case just drag a plain G clev from the Palette onto the first measure of the staff.
After that you'd need to 'transpose' it up an Oktave, select all->Ctrl-Up