Date / time stamp ...

• Apr 5, 2010 - 19:00

Is there a mechanism in MuseScore for entering and printing the current date and/or time on a score? I am thinking of a field that updates dynamically each time a score is opened, closed or printed and reflects the current date and time.

The application that I am thinking of is a situation where I have created a score and given copies to one or more other musicians that I work with. As time goes on, the score is edited, corrected or transposed, and I need to distribute new copies to my fellow musicians. In an effort to avoid confusion as to which copy is the correct one, I would like the date it was printed to appear in the lower right corner of the 1st page of the score. In so doing, each musician can know, unambiguously, which copy of the score is the most recent and should be replaced in their 'book'.

Thoughts or ideas would be appreciated.

Ken Parrish
aka (EulerOperator)
Lowell, MA


Better than nothing, you may manually add a sequential version number somewhere in the score (as programmers still do for source codes in many cases!).

Not as handy as you describe, of course, but it wold get the job done; and you do not even have to care numbers are really sequential as long as they always increase...


In reply to by Miwarre

I second the suggestion for a date/time stamp, that could be toggled on/off per score and which would update itself automatically on Save. The copyright field might be a good place for it, or else right under the title. Ideally you could set the format (that is 6/15/2020 10:35:55 AM, or 15 June 2010 16:44, or whatever.) I'm not so interested in version numbers.

In reply to by Marc Sabatella

For date (creation and current, $D and $d), yes, but not for time and also not for different date formats (seems fixed to dd MMM yyyy, e.g. 21 Jun 2013 or 13 May 2013, i.e. not even considering the user locale, which e.g should make it "13. Mai 2013" for me)

So I'd suggest a) a $T and $t (for creation and current time) to be added (should be easy) and b) some localisation here.

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