Create instruments in your own language

• Oct 13, 2019 - 01:34

Hi.
I am trying to create several instruments and I have followed the steps of another thread, which refers to manipulating the instruments.xml file.
This does not work for those who do not use English, in my case I use Spanish.
I have seen that Musescore ignores instruments.xml and works with instruments_en.qm in the "Locale" folder,
This file is compressed, how is it solved?

Thanks and best regards.

Comments

• Oct 13, 2019 - 01:46

The instruments you create in a new instruments.xml file can have their names written in Spanish. Place this file that contains only new instruments on your computer somewhere. Tell MuseScore where this file is by opening Preferences under the edit (or MuseScore) menu. In the Score tab, put the path to it in Instrument list 2, include the name of the file since it can be anything you want it to be.

Reply

• Oct 13, 2019 - 09:37

So maybe we can have a preference option somewhere (probably in advanced preferences? it's my new good friend) to set the language of instruments, overruling the language of the software's UI? Because even if I use the Chinese or English version of MuseScore most often, I sometimes want to let the instrument names be Italian by default, because this is the tradition of writing classical pieces in classical style.

Reply

• Oct 13, 2019 - 12:36

Nuh, that's a different issue requesting the names of instruments change depending on the user's language setting. So even if I add instruments under Chinese environment, when I open the score under English environment, I see the instruments' names in English.

Reply

• Oct 13, 2019 - 14:27

This simple change should do the trick, I think:

diff --git a/mscore/preferences.cpp b/mscore/preferences.cpp
index 3bed296b2..0117b7a21 100644
--- a/mscore/preferences.cpp
+++ b/mscore/preferences.cpp
@@ -102,7 +102,7 @@ void Preferences::init(bool storeInMemoryOnly)
             {PREF_APP_STARTUP_FIRSTSTART,                          new BoolPreference(true)},
             {PREF_APP_STARTUP_SESSIONSTART,                        new EnumPreference(QVariant::fromValue(SessionStart::SCORE), false)},
             {PREF_APP_STARTUP_STARTSCORE,                          new StringPreference(":/data/My_First_Score.mscx", false)},
-            {PREF_UI_APP_STARTUP_SHOWTOURS,                        new BoolPreference(true)},
+            {PREF_UI_APP_STARTUP_SHOWTOURS,                        new BoolPreference(true, false)},
             {PREF_APP_WORKSPACE,                                   new StringPreference("Basic", false)},
             {PREF_EXPORT_AUDIO_NORMALIZE,                          new BoolPreference(true)},
             {PREF_EXPORT_AUDIO_SAMPLERATE,                         new IntPreference(44100, false)},

Edit, I see, https://github.com/musescore/MuseScore/pull/5382 is doing excatly that ;-)

Reply

• Oct 13, 2019 - 15:13

The user can already turn off the tours whenever they want to, making MuseScore do it automatically doesn't make any sense.

When you start MuseScore the first time, it asks if you want advanced or basic work space, it also asks if you want to see the tours and turns them on or off accordingly. If you later change your mind about tours, you can use Edit->Preferences and check or uncheck the tours check box.

Reply

• Oct 13, 2019 - 15:15

True, but totally unrelated to that setting being also available in the advanced settings,

I guess you're missunderstanding what this is about: it removes a setting from being shown in the Advanced preferences that is shown in the Common prefereces already, so removes a redundancy. It is not about changing that setting in any form or shape.

Reply

• Oct 13, 2019 - 14:03

Changing languages of instruments in a score when you change languages of the program is a rather complicated issue. I work in the English US environment most of the time. Many scores I work with have instruments in Italian, French and German and occasionally other languages. I don't want these instrument names to change because I changed my program language to Spanish (or one of several other languages) to help someone in that forum.

A workaround recommended to people who do not speak a language like Italian who want their instruments in Italian is to change the program language to Italian, create a score, then change back to their native language. Changing the language of the score with the program language would eliminate this.

As for some of the languages being confused in the instruments (discussed elsewhere), I remember there was a bilingual translator for Chinese and Japanese a few months ago who messed things up on the Japanese side and upset several of the Japanese translators because he was translating to Chinese. It sounds like he probably put some Japanese into the Chinese as well. I for one recognize the difference between Japanese and Chinese when I see them, but I don't read either language nor do I ever use MuseScore in either of these languages, so I haven't seen the inconsistencies.

Reply

• Oct 13, 2019 - 16:21

It seems that with the solution given by Mike it works.
I have created a file with the instruments in a group, I have added the start and end Musescore directives and they appear in "All instruments", the created group.

Now I have to fight with the intervals, because they are transcriptionist instruments, with patience.

Reply

• Oct 14, 2019 - 15:59

Does anyone know why Musescore behaves like this?
I have a score with two Txistus in F # and a Silbote in B.
The actual tone is B.
I put it on, I hit the "concert tone" button and I switch.
It changes to the harmonic tone with 7 flats, Cb.
I want that if I switch the button the tone of B appears to me.
Thank you.

Some images

Attachment Size
Imagen2.png 15.69 KB
Imagen4.png 18.86 KB
Imagen6.png 18.04 KB

Reply

• Oct 23, 2019 - 15:12

Hi Mike
He followed the steps in the tutorial and it works but he continues to put the wrong key Gb major.
It goes back to the same thing, and it is a huge inconvenience and it makes insurmountable to make scores due to the harmony, as you will see in the image.
I have all the other instruments working correctly but the Txistu in F # with this inconvenience is going to be impossible.
This work that I am doing in collaboration with another person is to freely incorporate these instruments with the soundfont to Musescore and it is necessary that the key be correct, because the purpose is that people transcribe txistu scores and can hear them, if it is already complicated to Being a transpositor instrument, this complicates it even more.

Do you know any solution that works?
Greetings.

Attachment Size
Imagen1.png 7.96 KB
Imagen2.png 7.07 KB

Reply

• Oct 23, 2019 - 15:58

The link I provided works, you are doing something wrong.

You must enter keys in concert pitch. In the case of sharps (like the key of B) you need to transpose to a key that has sharps, like the key of A, then transpose up one step from A to B. It seems to be easier to go up with sharps and down with flats, but I don't think this is a requirement. I believe the concert pitch to get the key of A on the F# instrument is Eb (I hope I did my math right).

Reply

• Oct 23, 2019 - 16:51

I have done the test again and I continue to place Gb major, I am using musescore 2.3.2 but this does not have to do because I have tried with 3 and exactly the same.
Anyway, even if you get results, this is not worth anything, if it does not change automatically it makes no sense to make the instrument, many people who are going to use it have no knowledge to make frills.

Reply

• Oct 23, 2019 - 18:01

If you want the enharmonic key signature, you enter the key signature into the score.

Select the entire instrument (or section of the instrument's measures)

Transpose to the known key (A which is concert Eb)

Make sure the correct selection is made

transpose up a major second making sure transpose key signature is checked (as it is by default)

The tutorial was created while version 2 was current and works on version 3 as well.

If you want, attach your score and I'll fix it.

Reply

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