User:Symphonick/unofficial csg work recordings: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
Line 51: Line 51:


===Tempo for untitled movements===
===Tempo for untitled movements===
You are not supposed to add a tempo to every work. Tempo/character should only be used for works which would be untitled otherwise. Movements in concertos, symphonies, sonatas and so on.
You are not supposed to add a tempo to every work. Tempo/character should only be used for works which are usually referred to by tempo. That is mostly for movements of generic multi-part works; concertos, symphonies, sonatas and so on. Works which would otherwise be untitled.
<br/>
<br/>
<pre>Concerto in D major, Op. 1: I. Allegro</pre>
<pre>Concerto in D major, Op. 1: I. Allegro
Adagio & Allegro, Op. XX</pre>
but not in<br/>
but not in<br/>
<pre>Nocturne in D-major, Op. 1</pre>
<pre>Nocturne in E-flat major, Op. 55 No. 2</pre>
You wouldn't refer to this work by tempo. And as said before; the same thing goes for all vocal works & works based on vocal works.


====no tempo from composer====
====no tempo from composer====
Line 61: Line 63:
<br/>
<br/>
<pre>Concerto in C major, Op. 2: [Allegro]</pre>
<pre>Concerto in C major, Op. 2: [Allegro]</pre>
or not make any difference at all?

====something I forgot goes here====


==Works and parts==
==Works and parts==

Revision as of 13:40, 1 July 2011

Status: Notes, questions & comments from the discussions about CSG for works & recordings & mb-style. This is NOT a guideline.

The docs for works & recordings should probably contain a disclaimer "for experienced editors" or somehting?

Applicability

There was a tendency to over-apply the former CSG, so we should start with a list of things where CSG is not used. Holst's "The Planet" suite, songs... Brian wrote something.

Work names

Should default to the "original" name. Seems like there's consensus about using an urtext score as source, if possible. Some composers have all works in one collection, ex. "Neue Mozart Ausgabe".


Language

  • Note that it's possible that parts of the title in an urtext edition can be translated, and we will have to look elswhere for the original language
  • original meaning I think I expect Stravinsky's "L'oiseau de feu" to have the French title (premiered in Paris by Ballets Russes), and not the composer's language (Жар-птица)

Aliases

should be standardized local versions of the workname (+ if the work really has another name; maybe 2 different common names in one langugage)


Worktype (only for generic works)

Sonata in F minor, Symphony in G major but not for works with titles or quotes:
Carmen, Op. ?? not Opera: Carmen or something Nun komm der Heiden Heiland, BWV 599 not organ chorale, BWV 599 "Nun komm"
same for songs If it's part of a collection with a generic title "3 songs for SATB", don't use the name of the collection. If the collection is a title by the composer "Kinderszenen" it should be used: Kinderszenen: Movement, op. x no y ??

Key (only for generic works)

"if there is a well defined and non-ambiguous title given by the author, additional information is extra." well said by caramel31

Catalog(s)

Pete happened to mention the comment field. Would it work for everything, or would we like to keep the standard catalog for generic works as a part of the title? Examples:

  • note that the comment field is a workaround, the ultimate goal is that catalogs will have their own field(s).

=Multi-part works vs. "freestanding" works

A work that is intended as an entity in it's own would stop here.

Movement numbers

I believe it's built in as a part of a bigger work, but do we have part of work AR yet? I recommend using the comment field if a movement number is needed for work disambiguation. Ex. a concerto could contain 3 movements like this:

Allegro
Largo
Allegro

Add a disambiguation comment for the allegro movements:

Allegro (1st movement)
Largo
Allegro (3rd movement)

Don't add anything to the titles. Sometimes opinion can differ about the boundarys of a movement, we will try to agree on a good urtext source for every composer.

Tempo for untitled movements

You are not supposed to add a tempo to every work. Tempo/character should only be used for works which are usually referred to by tempo. That is mostly for movements of generic multi-part works; concertos, symphonies, sonatas and so on. Works which would otherwise be untitled.

Concerto in D major, Op. 1: I. Allegro
Adagio & Allegro, Op. XX

but not in

Nocturne in E-flat major, Op. 55 No. 2

You wouldn't refer to this work by tempo. And as said before; the same thing goes for all vocal works & works based on vocal works.

no tempo from composer

can be in italics in the score. we could use brackets?

Concerto in C major, Op. 2: [Allegro]

or not make any difference at all?

something I forgot goes here

Works and parts

Recording names

Probably the least discussed. I think we have a consensus about using the default worktitle.


Keys & instrumentation

This will not be a copy from the work name, instead it will actually follow what's recorded. A flute piece played on the violin, a violin solo sonata transposed to viola. Sometimes a work can even be published with variants for more than one instrument by the composer.

  • if by the editor...?

Also the specific voice for a song could be different from the original.

  • what to to w. high/low voice versions? very common for piano + voice. Have heard berlioz nuits... in different keys.
  • don't add artificial keys?
  • A=415Hz belongs in the annotation

Disambiguation

It looks like we can finally get rid of the old UI-workaround, which meant that we had to add performers to the title of the release and releasegroup. However, we still need a way to distinguish between different recordings of the same work, so we ask that you add the primary performer(s) to the comment field for the recording. Try to keep it to a minimum, only what's needed to sepearate the recording from another recording of the same work.

Aliases

Not available, but there is an open ticket.

The recording-work performance AR

ongoing discussions