Add metronome sound when exporting mp3

• Jan 8, 2017 - 15:56
Reported version
P2 - Medium
S5 - Suggestion

As the title says. Even when I have specifically saved a score again after turning on the metronome, the exported mp3 has no metronome click.


This is deliberate. The metronome is not part of your score, it is just a temporary aid for playback. If you wish to include a click track in your score, you can create one manually.

However, someday a feature could be added to optionally allow these temporary settings like metronomes or play panel settings to be included in export as well, so I am reclassifying this as a feature request.

Reported version 2.1 3.0

I know for a fact that the metronome was exported in mp3 files in earlier version of musescore (at least until about two years ago). Are you sure that this has been removed by design and is not a bug?

Or maybe I am just confusing things and I have maybe produced these files with Sibelius? ;) If so then I'm sorry and, yeah I would definitely find this a useful feature. The built in metronome does a lot of useful stuff that would be quite a lot of extra work in a separate drum track. In make case - with contemporary music I usually have a change of tempo marking almost every singly bar. So I could not just copy the same bar of drums to the whole score...

Well, if in your opinion is not importatnt that is certainly bad news for me and the way I use musescore for studying complicated music. This is really something I would need very much.

Hi. I am interested in how a constant metronome click would vary from a constant drum click, and would appreciate it if you would expand on this idea.

The only way I could see this as being a problem is if you are changing the denominator of the time sig., and I don't think that would change the metronome.

Perhaps I'm missing something and I would appreciate being more informed.


Reported version 3.0 2.1

The point of MP3 export is to produce a recording of your actual score, so if it isn't in the the score, it normally doesn't belong in the export. Sounds like you are trying to produce something different from a recording of your actual score - like maybe, you are trying to create a practice track. Often a better way to do that is to use the mobile app, or you could record the audio of the playback using Audacity or the like. Or simply use MuseScore for your practice. So there are definitely ways of generating practice tracks already. It's simply a feature request to have yet another way of doing this. It's not a bad idea, but do realize that generating practice tracks is getting outside the primary purpose of MuseScore (which is about notation first and foremost).

FWIW, some general things to know about the issue tracker, to help in classifying issues you file:

"Priority" doesn't necessarily how important something is to the person submitting it the issue -it really needs to reflect the needs of MuseScore users in general. Basically, without knowing for absolute certainly that an issue is higher than average priority for MuseScore users in general, you should simply use "normal" for all bugs and feature requests.

There is basically no such thing as "major" or "critical" for feature requests. I suppose if some new music notation were invented and instantly became a worldwide standard, it would be critical that we start supporting it, but we already support everything we absolutely need to.

For bugs, "Critical" means a crash, score corruption, or other loss of data/work. "Major" typically means a key feature is essentially unusable. And by "key feature", that normally means something relating to notation. For the most part, unless playback produces entirely the wrong results or crashes the program, nothing relating to playback is likely to be consider major or critical. Especially if the playback itself works fine for *its* primary intended purpose - hearing your actual score - but happens to not work as well for alternate purposes such as generating practice tracks.

"Component" should almost always be "Code" - that's what we would need to change in order to implement almost all bugs or feature requests.

The "Version" field is generally used to specify the first version to *have* the issue. No need to try to second guess which version might possibly be the first to contain a fix.

I understand. Just for clarification about the wrong labelling.
As you know this was not originally a feature request but a bug report, because my believe was that the recording of the click was broken and that it used to work in earlier versions, which now proved to be not the case. So since we know more now we can change the labelling ;)
Thank you for your time anyway.

@xavierjazz the metronome uses a higher pitched click on the one by default. When I have a score where time signatures constantly change randomly between for example 3/2 - 4/4 - 7/8 - 3/16 .... and so on, I think that creating a drum part that achieves the same would be a lot of extra work, while just switching on the metronome is no work at all.
Recording with audacity is for sure a solution I had already thought of myself. Just not as clean, simple and elegant as if when it could just be done by export.

Reported version 2.1 2.2

This would be an extremely useful feature, as I have musicians & students who practice to an MP3 of their own part, and there is no baseline for tempo when there is no starting count-in or click track. As this is only required on audio not on the actual score it makes sense to include as an optional export feature rather than write into the score itself. Very useful for teaching and practicing. In fact a better solution for me would be the ability to select the parts to include in an audio export as well as a metronome, for example the whole brass section, or the rhythm section.

Meanwhile, though, if you do create your own click track, you can make it invisible in the score via Edit / Instruments.

Also, you can already select which parts get included in the audio via View / Mixer.

Title metronome not recorded on exported mp3 Add metronome sound when exporting mp3
Priority P2 - Medium
Regression No
Workaround No
Workaround No Yes

Workaround is to add a percussion staff, fill the first measure with the desired rhythm and the rest with measure repeats, then hide that staff