OpenScore: Bruckner Symphony No.5

OpenScore: Bruckner Symphony No.5

Outline Instructions

Transcription group

A new transcription group has been created on for this project:

We shall use this group for question-and-answer topics and for news updates.

Because this project involves a long and complex symphony, we are looking for experienced transcribers with a previous history on OpenScore projects.

MuseScore version

This transcription project starting in March 2019 will use MuseScore 3.0, and you must have updated your installed software at least to version 3.0.5 (or later, as more updates are released).

IMSLP edition for transcription

We are very fortunate that a high-quality scan of Bruckner’s Symphony No.5 was uploaded to IMSLP in February 2019 as IMSLP #562139, so we shall use this as the source:,_WAB_105_(Bruckner,_Anton)

As at March 2019, the high-quality scan #562139 has page 5 twice (and page 6 missing): so for page 6 only it may be necessary to use either the low-quality scan of the same edition (IMSLP #518282) or the high-quality scan of the Nowak edition (IMSLP #563860) uploaded to IMSLP in March 2019.

Score templates

A separate template is provided for each movement of the symphony, with system breaks, measure numbers and rehearsal letters already inserted to match the IMSLP edition.  In the case of Movement 3, there are two separate templates for the Scherzo and the Trio: this is because in the original edition the measure count starts again at 1 for the Trio.  The IMSLP editions display the measure number every 10 measures, and we shall use this convention throughout the transcription project.  The final completed OpenScore edition will probably revert to the usual convention of displaying measures only at the start of each system.

Separate staff for each instrument

The templates use a separate staff for each instrument (e.g. one staff for Flute 1, and another staff for Flute 2).  We have to use this approach to allow generating instrument parts later on.  So for passages where two instruments play in unison (“a due” or “a 2”), you must copy the transcribed part into the second staff as well.

You do not need to create a separate stave where Violins 1 or Violins 2 have a short divisi passage. Please do not add or remove instrument staves.

Language to be used

For instrument names, our templates use German long and short instrument names as defined in MuseScore 3.0. In many cases, the German short names used in MuseScore 3.0 differ from the short names used in the 1935 edition.

For musical directions we shall use the German (or Italian) directions, exactly as printed in the IMSLP #562139 edition of 1935.  


A Google Sheet is provided with translations into English, just as a guide to transcribers:

Please do not use the English terms in your transcription!


For allocation of a movement, potential transcribers can post a request as a comment on the Google Sheet which is provided (see link above).


Transcription response in MuseScore will slow down after some pages of input of a full score, so it is recommended that you submit your transcription for review after each completed batch of 10 pages.  If you have to delete work already done because of a slow response in MuseScore, please change the opening measure number where you start the next section of transcription so that the first measure number matches the IMSLP edition.  

Review team

The initial OpenScore reviewer is DanielR (Dan Rootham), and the final reviewer and approver for OpenScore will be shoogle (Peter Jonas).  Any questions can be directed to DanielR (either start a new public topic in the transcription group, or send private email to

Author:        Dan Rootham

Version:        3

Date:        2019-03-12