Skip to content
Peter Jonas edited this page Feb 5, 2024 · 2 revisions

This page is about queries relating to the MuseScore desktop software, which is soon to be renamed MuseScore Studio.

For queries about the MuseScore.com website and mobile apps, see https://intercom.help/musescore. For Muse Hub queries, see https://musehub.zendesk.com/.

MuseScore is part of Muse Group. For queries about the company and careers, see https://mu.se/.

Contact the development team

For urgent matters that can't be resolved with help from the community alone, post in any suitable channel within MuseScore's Discord server. 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.

If it's not urgent, but still requires attention from the development team, you can open an issue on this repository. Notice the blank issue option, which you may use if your query doesn't fall into one of the main issue categories.

Get help

User support

The answers to most questions can be found in the MuseScore Handbook. See Exploring the handbook for details of its usage.

Video tutorials are available on our YouTube channel and on the Home > Learn page within MuseScore 4 itself.

We also have written Tutorials, How-tos, and links to accessibility-related content.

If you can't find the information you need, please ask for help in the Support Forum. You can also ask in the Discord server's #support channel, but the forum is better because it's more easily searchable.

If you need a quick answer, you could ask on the forum then post a link to your question in the Discord server.

Translation support

Ask in the Discord server's #translation channel.

Development support

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 or save your build log as a .txt file and attach it to your post.

If you want advice about how to implement something, you could ask in the #development channel. However, it's usually best if you 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 us something to work with, and people will be more inclined to help once they've seen that you've given it a proper try yourself first.

Report problems

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.

When posting or commenting in the tracker, keep your message as concise as possible while including all relevant information. Don't be offended if the development team 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.

Discuss ideas

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.

The issue tracker is not to be used for extended discussion. When debate is likely, one strategy is to create a placeholder issue in the tracker and use it to link to a discussion in the forums or on GitHub Discussions. Once a consensus is reached, you can write an actionable summary inside the issue.


MuseScore's Discord server

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.

Notifications

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.

Voice channels

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.

image

Testing

Translation

Compilation

  1. Set up developer environment
  2. Install Qt and Qt Creator
  3. Get MuseScore's source code
  4. Install dependencies
  5. Compile on the command line
  6. Compile in Qt Creator

Beyond compiling

  1. Find your way around the code
  2. Submit a Pull Request
  3. Fix the CI checks

Misc. development

Architecture general

Audio

Engraving

Extensions

Google Summer of Code

References

Clone this wiki locally