Import midi file and change staff properties

• May 3, 2015 - 10:02

Hi, sorry for my bad english.
However, I have a problem with midi file imported:
I generated a midi file with Reason (22 tracks instruments), but at the moment of import in Musescore 2.0, the result is an incomplete score and re generated full piano staff.
In my midi file the piano is only two parts, but after importing this midi file full score having a piano staff.
For me, the problem is this:
change the instruments for each tracks before importing, but this function is not implement in Musescore.
Also modified on Nightly the single tracks properties, not change the result at the moment of the export pdf file, the score is lost each instruments and compare the piano staff for a single instrument.
Modificated a staff properties in "Instruments", proceding with change a staff from piano staff to violin staff (for example), not change the result.
This problem about every midi file imported, also don't my files.
Don't is necessary the function "continues view" in this case.


Comments

Hello! In order to help you, please tell us which version of MuseScore you are using, and please post - as an attachment (see the File Attachments link below where you type your response) - the actual MIDI file you are having problems with and precise steps to reproduce the problem.

You can definitely change instruments for each track in MuseScore. The details depend on the version of MuseScore and on what specifically you want to change - just the playback sound, or also the clef, transposition, etc. That is why we need to know what version of MuseScore and why we need to see the actual score and the steps you are trying to follow.

In reply to by Marc Sabatella

Hi, I have the 1.3 and the 2.0 version of Musescore and import a midi file after work with Reason software, without processing a clef and other features, but only quantization.
The problem is the same for each midi file imported.
I have execute a test of the midi file "Take on me" one arrangement by Brandon Stumpf, in two version of Musescore (1.3 and 2.0) the problem is present.
In the file .jpg two examples of this situation without solving after modified the staff properties in "Instruments" link.
I can not load the midi files that I mentioned at the beginning , because it is a piece to be finished,
however this situation a repeat with every midi file.

Even if proceed with "Continue view", pdf file exported will be file examples.
My only problem is an export import pdf incomplete after getting a midi file.
The exported PDF file (like all midi files imported into MuseScore 1.3 and 2.0) is identical to the "Take on me" with I load in this tread.
Thanks

In reply to by Piccinesco

As I said, we really need the actual MIDI file and the precise step by step instructions to reproduce whatever problem you are seeing. In general, MIDI input should work wquite well in 2.0 with regard to guessing what instrument to use based on the MIDI program number used for each track. I don't see anything wrong with the picture you posted, but if I had the actual MIDI file, maybe I'd understand better.

In reply to by Marc Sabatella

I understand, I still had more than a test, in this case with Take on me (by downloading the midi file), repeat it creates the same problem that you can see in the file I have attached. The steps that I made are just two: I imported the midi file and then , using Nightly I set the maximum quantization according to the note from the shorter duration in the piece, that's all .
After I exported the file in pdf and the result is as what you can see in the attached file, it does not change anything .

In reply to by Piccinesco

But that's just it - I *dont* see any problem with the picture you uplaoded. It looks like a perfectly fine picture to me. How am I supposed to be able to tell there is a problem if I can't tell what you think it is *supposed* to look like, and *why* you think it is supposed to look different? That's why, again, we need the *actual MIDI file* you are having problems withm and a clear description of what *exactly* you think is wrong with the import.

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