Published on MuseScore.org

Podpora

This chapter describes how to find help using MuseScore: the best places to look, the best way to ask a question on the forums, and tips for reporting a bug.

Překlad

You can help translate the MuseScore software and documentation into your own language, as mentioned in Development / Translating.

Software translation

  1. Ask in the forum to improve translation
  2. Connect to Transifex/MuseScore http://translate.musescore.org, which will redirect you to https://www.transifex.com/projects/p/musescore
  3. Select the language and then the section you want to help with (MuseScore, Instruments, Start Center or tours)
  4. Click on the "translate" button (the button text will depend on your language...)
  5. Search for "strings" (informational meaning) you want to translate (you could filter "already translated items")

Here is a technical explanation: Continuous translation for MuseScore 2.0

Website and handbook translation

See Translation instructions

See also

Obnovení továrního nastavení

    MuseScore has the option to revert back to the standard built-in presets or "factory-settings". This can be necessary if your settings are corrupted. Warning: Reverting to factory settings removes any changes you have made to the preferences, palettes, or window settings. This is not a commonly needed procedure; consult the forums first, as there may be a way to solve your problem without resetting everything.

    Via menu

    If MuseScore still starts, it is possible to revert from within MuseScore.
    Go to Help→Revert to Factory Settings. A warning dialog will appear:

    Revert to factory settings

    Clicking Yes resets all MuseScore's settings as if the program was installed for the first time, and MuseScore will immediately restart. No will safely cancel the revert.

    Via command line

    If MuseScore does not start, you must run this process via the command line.

    Instructions for Windows

    1. If you have MuseScore open, you need to close it first (File→Quit)
    2. Type ⊞ Win+R to open the Run dialog. Alternatively select "Start" using your mouse and type "run," then click the "Run" program.
    3. Click Browse...
    4. Look for MuseScore3.exe on your computer. The location may vary depending on your installation, but it is probably something similar to My Computer → Local Disk → Program Files → MuseScore 3 → bin → MuseScore3.exe

    5. Click Open to leave the Browse dialog and return to the Run dialog. The following text (or something similar) should display in the Run dialog

      C:\Program Files\MuseScore 3\bin\MuseScore3.exe (actually %ProgramFiles%\MuseScore 3\bin\MuseScore3.exe)

      For the 32-bit version of MuseScore in a 64-bit version of Windows, the location is

      C:\Program Files (x86)\MuseScore 3\bin\MuseScore3.exe (actually %ProgramFiles(x86)%\MuseScore 3\bin\MuseScore3.exe)

      For the Windows Store version (Windows 10), it is pretty well hidden, search for it via Windows Explorer

    6. Click after the quote and add a space followed by a hyphen and a capital F: -F

    7. Press OK

    After a few seconds, MuseScore should start and all the settings reverted to "factory settings".

    For advanced users, the main preference file is located at:

    • C:\Users\[USERNAME]\AppData\Roaming\MuseScore\MuseScore3.ini
      (actually %APPDATA%\MuseScore\MuseScore3.ini)

    The other preferences (palettes, session, shortcuts, workspaces...) are in:

    • C:\Users\[USERNAME]\AppData\Local\MuseScore\MuseScore3\ (actually %LOCALAPPDATA%\MuseScore\MuseScore3\)

      For the Windows Store version (Windows 10), these are pretty well hidden, search for them via Windows Explorer

    Instructions for MacOS

    1. If you have MuseScore open, you need to quit the application first (MuseScore→Quit)
    2. Open Terminal (in Applications/Utilities, or via Spotlight search) and a session window should appear

    3. Type (or copy/paste) the following command into your terminal line (include the '/' at the front):

      /Applications/MuseScore\ 3.app/Contents/MacOS/mscore -F

    This resets all MuseScore preferences to factory settings and immediately launches the MuseScore application. Note that you cannot quit the Terminal without quitting MuseScore. You can safely quit MuseScore, quit the Terminal, and then reopen MuseScore in the normal fashion, ready to continue using.

    For advanced users, the main MuseScore preference file is located at ~/Library/Preferences/org.musescore.MuseScore3.plist.
    The other preferences (palettes, session, shortcuts, workspaces...) are in ~/Library/Application\ Support/MuseScore/MuseScore3/.

    Instructions for Linux

    The following is true for Ubuntu, and most likely all other Linux distributions and UNIX-style operating systems.

    1. If you have MuseScore open, you need to quit the application first (File→Quit)
    2. From the Ubuntu main menu, choose Applications→Accessories→Terminal. A Terminal session window should appear

    3. Type, (or copy/paste) the following command into your terminal line (Ctrl+Shift+V to paste in Terminal):

      mscore -F

      Or, if you are using the AppImage version, you must first use the cd command to change directory to wherever you saved the AppImage. For example, if you saved it to your Desktop (and there is only one):

      cd ~/Desktop
./MuseScore*.AppImage -F

    This resets all MuseScore preferences to factory settings and immediately launches the MuseScore application. You can now quit Terminal, and continue using MuseScore.

    For advanced users, the main MuseScore preference file is located at ${XDG_CONFIG_HOME:-~/.config}/MuseScore/MuseScore3.ini.
    The other preferences (palettes, session, shortcuts, workspaces, …) are in ${XDG_DATA_HOME:-~/.local/share}/MuseScore/MuseScore3/.

    See also

    Hlášení chyb a žádosti o funkce

      Before filing bug reports or feature requests in the Issue Tracker it is recommended first to post it in the relevant Forum so others may help establish a bug as genuine, or provide ideas and second opinions for new features.
      Include a link to such discussion when creating the Issue.

      Bug reports

      Before posting in the issue tracker:

      • Try to reproduce the issue with the latest nightly. You may also view the version history to check whether it has been fixed/implemented already.

      • Please include as much of the following information as you know and limit each issue to one report:

        • Version/revision of MuseScore you are using (e.g. version 3.0, revision 871c8ce). Check Help → About... (Mac: MuseScore → About MuseScore...).
        • Operating system being used (e.g. Windows 7, macOS 10.12 or Ubuntu 14.04)
        • Describe the precise steps that lead to the problem (where do you click, what keys do you press, what do you see, etc.).
          If you are not able to reproduce the problem with the steps, it is probably not worth reporting it as the developers will not be able to reproduce (and solve) it either. Remember that the goal of a bug report is not only to show the problem, but to allow others to reproduce it easily.

      • Please remember:

        • Attach the score that shows the problem, at least a minimal example —use the "File attachments" option at the bottom of the page, just above the Save and Preview buttons when you're typing your post.

      Feature requests

      When posting in the Issue Tracker:

      • Be brief, but describe the goal as precisely as you can
      • Describe the context in which the new feature is intended to work
      • Suggest a specific workflow, if you can

      Cross linking issues

      When you write a comment in a forum topic, you can refer to an issue in the issue tracker using the following notation: ´[#number]´
      That way the link in the comment will include the issue title and reflect the current status of the issue. Furthermore, it'll lead to the forum topic being listed in the issue itself.
      Type [#153286] get #153286: Change instrument causes a crash