Contact
This page is about MuseScore Studio, the free and open source music notation program created by Muse Group.
For other queries, see:
- MuseScore.com website and mobile apps
- MuseHub, MuseSounds, and MuseSounds Manager or use Buy Now (submenu) > Report a problem for the relevant product in MuseHub
- Muse Group company and careers
For non-urgent matters, open an issue on this repository (create a blank issue if it doesn't fall into one of the main categories). Or you can use Discord.
For urgent matters, post in any suitable channel within MuseScore's Discord server (e.g. #development). Tag a team member in your message by typing the @ symbol followed by their username. For example, type @Peter Jonas to tag our community ambassador, Peter Jonas.
If the message can't be shared publicly, click on a team member in the Discord server and use the option to send them a message. Make sure your message is polite, short (if possible), and specific (not generic like "Can I ask you a question?"), otherwise it's likely to be ignored.
Important
Don't contact the development team about topics that can be discussed in open community channels, such as bug reports and support queries (unless it would involve sharing sensitive information).
Problems should be reported on the issue tracker, unless it's urgent in which case you should contact the development team.
Remember to check for existing issues before posting in the tracker. If the problem has already been reported, use the thumbs-up reaction (👍) to indicate that it affects you as well. Avoid commenting unless you have something useful to add, as this creates unnecessary spam that slows down the development team.
Important
When posting or commenting in the tracker, keep your message as concise as possible while including all relevant information. Don't be offended if a team member edits your message for brevity, or hides it when it's no longer relevant. This is necessary to avoid wasting time re-reading outdated information.
Most topics are covered in the MuseScore Studio Handbook. You can try asking the AI questions in the searchbox, but you might have more luck with standard search or browsing the table of contents on the left.
We also have:
- Video tutorials on our YouTube channel and on the Home > Learn page within MuseScore 4 itself.
- Written tutorials, how-tos, and links to accessibility-related content on the website.
- A community-led support forum and Discord server (e.g. the
#supportchannel).
Tip
The forum is the best place for most questions since it's open to everyone and easily searchable. If you need a quick answer, you could ask on the forum and then post a link to your question in the Discord server.
Ask in the Discord server's #translation channel.
If you need help compiling MuseScore or writing plugins, ask in the Discord server's #development channel. For build errors, it helps if you screenshot the error message. For more complex errors, create a blank issue on GitHub and paste your build log inside a <details> section or upload it as a .txt file.
<details><summary>Build log</summary>
```
YOUR LOG HERE!
```
</details>Build log
YOUR LOG HERE!
Tip
If you want advice about how to implement something, you could ask in the #development channel. However, it's usually better to come up with a solution yourself and submit it as a pull request for others to comment on. Even if it's just a partial solution, it gives people something to work with, and they will be more inclined to help once they've seen that you've given it a proper try yourself.
The MuseScore.org forums and Discord server are the place to discuss all matters relating to the desktop app.
There's also GitHub Discussions, but it doesn't get as much traffic so it might be a while before your post is noticed.
Important
The issue tracker should not be used for extended discussion. When debate is likely, a valid strategy is to create a placeholder issue in the tracker that links to somewhere else where the conversation can happen (usually a forum post or a GitHub discussion thread). Once a consensus is reached, you can write an actionable summary inside the issue.
Join the Discord server to get the latest news and hang out with the contributor community! The Discord server replaces the Telegram chats, IRC channel, and email mailing list that were previously used for coordinating MuseScore's development.
| MuseScore's Discord Server: https://discord.gg/HwHhXEbJ4r |
|---|
| If clicking the link doesn't work, use the ➕ (Add a Server) button in Discord to join manually. |
It's not just developers in the server, users are welcome too! The server has multiple channels for discussing various topics. You can join a channel by selecting it in the channel list on the left of the screen. The description at the top of each channel page tells you what the channel is used for.
You can pause notifications for a particular channel via the bell menu 🔕 in the top right of the channel page, or for the server as a whole by clicking on the server name (MuseScore) and going to Notification Settings. We recommend setting it to Only @mentions so you'll still be notified when somebody tags you with @username.
When a channel has unread messages, its name will be highlighted in the channel list. You can disable this highlight for channels you don't care about by using the Mute Channel option in the bell menu 🔕, or by muting the server as a whole in MuseScore > Notification Settings.
MuseScore's server has a voice channel called 🔊Ensemble, which you can join to speak to other people. Please wear headphones in this channel to avoid creating an echo for other users, or mute your microphone when you're not speaking. Ideally, do both!
When you're in a voice channel, there's an option to enable video (from your webcam) or start screen-sharing. During video calls, you'll probably want to hide any non-video participants, which you can do via a three dots menu ⋯ in the top right. The Grid/Focus button to the left of the three-dots menu is also useful.
