home tune search software learn abc discuss about blog Starbound/LOTRO contact  

  [abc standard: home | current | route-map | updating | proposals]


Transposition proposal - summary

This page contains the thirteenth draft of a proposal to extend the transcription capabilities within abc. It involves only minor changes from the twelfth draft:

  • K: and V: modifiers combine with other modifiers in the same field (as before) but can't be repeated
  • shift-score and shift-sound have been shortened to score and sound (following a suggestion from Jef)
  • instrument=<note>;abc=concert and instrument=<note>;abc=written have now been changed very slightly to instrument=<note>;abc@concert and instrument=<note>;abc@written

The important aspects of this proposal are the same as versions 10, 11 & 12:

  • A single system for transposition (rather than the dual high/low-level systems proposed previously) consisting of the well-establised shift-score and shift-sound operators, now shortened to score and sound, which allow the typeset score and playback to be modified independently
  • transposition by interval (e.g. C to G), rather than by semitones as previously
  • instrument synonyms for score and sound, to give an intuitive specification for transposing instruments
  • shift shorthand for combined score and sound transpositions

I have included some notes and comments at the end.

4.6 Clefs and key/voice parameters

Additional text for section 4.6 Clefs and transposition

This section discusses support within abc for clefs and other features which affect the placement of the notes relative to the staff. It briefly mentions transposition, because the relevant syntax appears in the K:key and V:voice fields, but this topic is discussed in full in section 13, Transposition.

Clef, transposing instrument and related indications appear as modifiers to the K:key and V:voice fields; the possible modifiers are:

[clef=]<clef name>[<line number>][+8|-8] stafflines=<lines> octave=<number>
  score=<note1><note2> sound=<note1><note2> shift=<note1><note2>

(where <…> denotes a value, […] denotes an optional parameter, and | separates alternative values).

Within a given voice, the modifiers of each K: or V: field are inherited from the previous K: or V: field, unless overriden - see scope and inheritance of modifiers for more details.

… unchanged …

… unchanged …


  • The transpose=<semitones> modifier of abc 2.1 and earlier is now deprecated (replaced by the sound modifier - see transposition).
  • The middle=<pitch> modifier of abc 2.0 and earlier has been compromised in terms of what it was supposed to do and how it has actually been implemented. It is therefore deprecated.

TODO: Update deprecated list.

… unchanged …

4.6.1 Scope and inheritance of modifiers

As a fundamental rule, within each voice, each successive V: or K: field inherits the modifiers of the previous V: or K: field, unless it specifically overrides them.

Note: in other words, within a voice V: inherits from a K: field as well as from another V: field (and vice-versa).

Recommendation: In single-voice tunes these modifiers will normally be applied to the K: field. In multi-voice tunes it is recommended that they are only applied to V: fields (an additional V: field can even be introduced if one of the modifiers needs to change at a K: change). If a single-voice tune contains V: fields (for example, if it is a part extracted from a multi-voice score), then it is recommended that modifiers are applied to the V: fields.

Within each K: or V: field, modifiers may be arranged in any order and their effect is combined; however, they may not be repeated (if they are, software should issue a non-fatal error message). In the specific case of score or sound modifiers mixed together with shift or instrument modifiers, replace the latter with their score and sound equivalents. For example, shift=CG score=GF becomes score=CG sound=CG score=GF and so the second score combines with the first to give sound=CG score=CF.

However, modifiers written in each successive K: or V: field override modifiers inherited from previous fields. For example, [V:1 shift=CG][V:1 score=GF] represent two different fields and so modifiers of the first are overridden by modifiers of the second. To evaluate their effects, first expand the shift in the first field to give [V:1 score=CG sound=CG][V:1 score=GF]. The second field then inherits both modifiers but specifically overrides the score to result in [V:1 sound=CG score=GF].

Finally note that there are two ways to specify octave shifts and, for example, octave=1 is equivalent to shift=Cc. However these operators can be used independently and so neither overrides the other.

13 Transposition

13.1 Transposition operators

The fundamental transposition operators are sound and score which act as modifiers for K:key and V:voice fields:

  • score=<note1><note2> transposes the typeset score according to the specified interval (the playback is not affected)
  • sound=<note1><note2> transposes the playback according to the specified interval (the typeset score is not affected)

Transpositions are applied to notes, grace notes, chords and key signatures.

The transposition interval is specified by two notes, <note1><note2>. Here <note1> refers to the transcribed abc code and <note2> refers to the rendered output (i.e. the typeset score in the case of score or the playback in the case of sound).

Example: In the following the typeset score is raised by a fifth and is rendered the same as if the abc code was transcribed as [K:D] efga. The playback is lowered by a tone and is rendered the same as if the abc code were [K:F] GABc.

K:G score=CG sound=DC

Note: The interval system is clear with regard to enharmonics so, for example, the interval C to _G is distinct from C to ^F. However, to compute transpositions it may be helpful to use the MusicXML concept of specifying the interval as a combination of diatonic steps and semitones. Both of these can be easily calculated and make it simple to work out what the resulting note is using the diatonic steps to give the letter and the semitones to indicate whether it is flat, natural or sharp.

Examples: C to ^F is 6 semitones in 3 diatonic steps - C to D, D to E, E to F (as opposed to C to _G which is 6 semitones in 4 diatonic steps). Using this interval:

  • Eb (_E in abc code) transposes to A since A is 3 steps (letters) above E (in the cycle ABCDEFG) and the A is natural, since that note is 6 semitones above Eb
  • G transposes to C# (^c in abc code) since C is 3 steps above G and C# is 6 semitones above G
  • C# transposes to F## (^^F in abc code) since F is 3 steps above C and F## is 6 semitones above C#

Notes for developers: You should correct any transposition which goes beyond the specified abc limits to available key signatures, K:Cb (7 flats) to K:C# (7 sharps), and double/triple accidentals. For example, in principle K:C# score=CG raises the key up to K:G# (8 sharps), so to keep with the limits it should be rendered as K:Ab (4 flats).

TODO (elsewhere in the standard): Limit the range of key signatures supported by abc to K:Cb (7 flats) through to K:C# (7 sharps). (Also limit accidentals - e.g. double sharp and double flat accidentals should be supported, but triples are entirely optional.)

To specify the same transposition for both score and sound, just use shift=<note1><note2> as a shorthand.

Example: The following two K:key fields are equivalent

K:G score=CG sound=CG
K:G shift=CG

13.2 Writing abc code for transposing instruments

Transposing instruments sound notes at a different pitch to which they are written. For example, a C written on a Bb clarinet score would be sounded as a Bb (and similarly a written D would be sounded as a C).

This section uses written pitch (i.e. the pitch that is written on a transposing instrument's score) and concert pitch (i.e. the pitch that is actually sounded) to distinguish between the two.

Note: The term "concert pitch" is also used elsewhere in the musical lexicon to indicate "play A (above middle C) at 440Hz". However, here it refers to the pitches that transposing instruments actually sound.

There are two ways of writing abc code for transposing instruments:

  1. The abc code can be transcribed at concert pitch with score=<note1><note2> modifiers used to transpose the typeset scores appropriately. If preferred the instrument=<note>;abc@concert modifier can be used as a synonym for score=<note>c sound=cc. Here the abc= is optional so this could be written instrument=<note>;concert.
  2. The abc code can be transcribed at written pitch with sound=<note1><note2> modifiers used to transpose the playback appropriately. If preferred the instrument=<note>;abc@written modifier can be used as a alternative for sound=c<note> score=cc. Again the abc= is optional so this could be written instrument=<note>;written.

In both cases the typeset score is rendered at written pitch by default.

If a concert pitch score is required the I:concert-score instruction can be applied, either in the file header or the tune header. For transcriptions at concert pitch this has the effect of cancelling all of the score modifiers (and the instrument=<note>;abc@concert alternative). For transcriptions at written pitch it has the effect of altering sound modifiers (and the instrument=<note>;abc@written alternative) to shift modifiers.

Note 1: The <note> in the instrument=<note> syntax is a note and not a key (so that different octaves may be specified and so that the letter b is not ambiguous). Therefore, for a Bb instrument you must write instrument=_B and not instrument=Bb.

Note 2: The rationale for including sound=cc (which is in effect a transposition from a note to itself) as part of the synonym for instrument=<note>;abc@concert and score=cc as part of instrument=<note>;abc@written is to completely cancel the previous transposing instrument setting, so that everything works when a voice switches from abc encoded at written pitch to abc encoded at concert pitch, or vice-versa.

The following example illustrates the principles of writing for transposing instruments.

13.2.1 Transposing instruments - extended example

Suppose a Bb clarinet player and a violinist wish to play the same piece which simply consists of the notes CDEF in the key of C.

Since the violin is not a transposing instrument, the violinist's part is written (and sounded):

V:1 name=violin

For the clarinet part, there is a choice. If, say, the composer of the piece prefers to work at concert pitch, the clarinet part can be transcribed as sounded, either using score:

V:2 name=clarinet score=_Bc

or using instrument as a alternative:

V:2 name=clarinet instrument=_B;abc@concert

This will be rendered by abc typesetting software according to the shift (i.e. [K:D] DEFG) but sounded as transcribed (i.e. CDEF). If a concert pitch score is required it can be typeset by adding an I:concert-score instruction.

Alternatively, if the composer wants the abc code at written pitch, the same piece can be transcribed:

V:2 name=clarinet sound=c_B

or using instrument as a alternative:

V:2 name=clarinet instrument=_B;abc@written

This will be rendered by abc typesetting software as transcribed (DEFG) but sounded according to the shift (i.e. CDEF). Again, if a concert pitch score is required it can be typeset by adding an I:concert-score instruction.

Note: Written pitch voices will almost always need their own K: field to set the key correctly (which will be different from concert pitch voices).

The whole piece could then be transcribed at concert pitch as:

V:1 name=violin
V:2 name=clarinet instrument=_B;abc@concert

or at written pitch as:

V:1 name=violin
V:2 name=clarinet instrument=_B;abc@written

In either case the typeset score will be rendered at written pitch (and the playback at concert pitch). To obtain a concert pitch score, add an I:concert-pitch instruction in the file or tune header.

Re-transposition: Finally, suppose that the clarinet player has fallen ill and is to be replaced by an alto sax player who now needs a transposed part to read. If the abc code has been transcribed at concert pitch this is extremely easy by replacing instrument=_B;abc@concert with instrument=_E;abc@concert in the clarinet part (the name can also be changed too):

V:2 name="alto sax" instrument=_E;abc@concert

If the abc code has been transposed at written pitch (in this case for a Bb instrument), it is a little harder.

The instrument=_B;abc@written can remain, as it is adjusting the playback to concert and also will serve as a reminder that the part was originally transcribed at written pitch for a Bb instrument.

To adjust the score, consider that the Bb clarinet score is written a major second higher than it is sounded (so C is written D) whereas the alto sax is written a major sixth higher than it is sounded (so C is written A). Since the abc code is already transcribed a tone higher, it needs to be raised by a further fifth (i.e. a major sixth less a major second) and so one way to do it is to use score=CG (or score=DA if that is easier to think about). The resulting code is:

V:2 name="alto sax" instrument=_B;abc@written score=CG

This can be thought of as a reminder that the part is encoded at written pitch for a Bb instrument but the score is additionally transposed a fifth higher (i.e. for an instrument a fifth lower).

Another way to express this is to use the fact that a second V: field overrides parts of the first. In this following excerpt, the first V: field shows details of the original transcription for clarinet, whilst the second shows the re-transposition adjustments for alto sax:

V:2 name=clarinet instrument=_B;abc@written
V:2 name="alto sax" score=CG

Depending on how you think about re-transposition, a further way to do this is to write:

V:2 name="alto sax" instrument=_E;abc@written shift=CG

This can be thought of as a reminder that the score is at written pitch for an Eb instrument but that the abc is encoded for an instrument a fifth lower (so needs to be raised by a fifth).

Once again overriding can be brought into play - however, both new modifiers (instrument and shift) are required for the re-transposition to work and so in fact the second V: field completely overrides everything in the first:

V:2 name=clarinet instrument=_B;abc@written
V:2 name="alto sax" instrument=_E;abc@written shift=CG

One final way to do this, if you consider that the instrument modifier is ambiguous (the abc is encoded for a Bb instrument but the score will be typset for an Eb instrument) is just to use score and sound modifiers:

V:2 name="alto sax" score=CG sound=c_B

However, these examples suggest that, all other things being equal, it is rather more flexible to transcribe the abc code at concert pitch rather than at written pitch.

Finally note that all of the transposing instrument information would normally be collected up in the tune header to make it more visible (it only needs to appear in the body if something changes halfway through, such as a switch from Bb clarinet to A clarinet). So the written pitch clarinet to alto sax re-transposition excerpt could be transcribed as:

T:Duet for violin and clarinet (actually played on an alto sax)
V:1 name=violin
V:2 name=clarinet instrument=_B;abc@written
V:2 name="alto sax" score=CG

13.2.2 Transposing instrument examples

The following table lists some example transposing instruments and the modifiers they would need

abc at concert pitch abc at written pitch
Instrument score=<n1><n2> instrument=<n>;abc@concert sound=<n1><n2> instrument=<n>;abc@written
piccolo score=c'c instrument=c';abc@concert sound=cc' instrument=c';abc@written
Bb clarinet score=_Bc instrument=c';abc@concert sound=c_B instrument=c';abc@written
soprano sax score=_Bc instrument=_B;abc@concert sound=c_B instrument=_B;abc@written
A clarinet score=Ac instrument=A;abc@concert sound=cA instrument=A;abc@written
alto flute score=Gc instrument=G;abc@concert sound=cG instrument=G;abc@written
cor anglais score=Fc instrument=F;abc@concert sound=cF instrument=F;abc@written
alto sax score=_Ec instrument=_E;abc@concert sound=c_E instrument=_E;abc@written
tenor sax score=_B,c instrument=_B,;abc@concert sound=c_B, instrument=_B,;abc@written

13.3 Transposing a file

To transpose an entire file, use the instruction I:score <note1><note2>, I:sound <note1><note2> or, as a shorthand for both, I:shift <note1><note2>. When placed in the file (or tune) header they have the the effect of adding the corresponding score=, sound= or shift= modifiers to every K: and V: field in the file (tune) which will then be combined with existing modifiers.

Example: The following excerpts are equivalent; in the former the I:score cC (downwards octave transposition) is applied to the K: field and combines with the existing score modifier to give the latter.

I:score cC
K:C score=_Bc
K:C score=_BC

Notes and comments on the proposal

Although this proposal is relatively straightforward, the use of shorthands means that an issue has arisen with the way that instrument and shift are overridden by each other or, in part, by score or shift. For example, in the following excerpt the shift setting completely overrides the instrument setting (because they are both defined in terms of score and shift):

K:C instrument=_E;abc@written
K:C shift=CG

(The same issue does not arise if they are included in the same field as they are considered to combine.)

This is regarded as counter-intuitive by a number of contributors to the debate and as a result an alternative model has arisen where shift and instrument are considered independent of score and shift - this is discussed in proposal version 14

Other notes:

  • One mechanism missing from the proposal is allowing provision for clefs which change between a concert pitch score its written pitch counterpart. However, since transposing instruments are always typeset at written pitch (except when I:concert-score is present), that means we just need something like concert-clef=treble (which would only apply when I:concert-score is present) to handle this.
  • A recurring question is whether independent score and sound modifiers are actually necessary. I have discussed this separately in the independent-shift use-case.

Chris Walshaw, July 2014

abc/standard/v2.1/proposals/transposition/v13.txt · Last modified: 2014/07/25 11:22 by cwalshaw
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki