Tempo marks, etc.in parts extraction

• Feb 7, 2017 - 21:18

A question: How do the players know about tempo settings in an orchestral piece? (I usually enter accelerandos, rit. allarg. etc. under each part in the full score, but NOT certain things like Allegro equals m.m. quarter note =120, etc. I've never seen a full conductor's score of 24 or more staves with a stack of (column, really1) allegros or largos, etc. over each instrument.(Usually over a system or the top of the score) So how does one handle this in a new score? Do you have to put in the tempo marks on each staff and then set Invisible for the full score, or what.? I will appreciate any enlightenment on this.


Comments

If I understand correctly, it's the contrary, in MuseScore there are SYSTEMS things which appear on each part when you make the individual parts . For example the TITLE, the COMPOSER, the TEMPO, The letters for Measures .All these, don't appear on the full score on each stave, but only on the top above the first ligne . When you pass in individual part, each part gets title composer, tempo etc.....

When you enter the tempo (using either palette or alt-T) it only shows up above the top staff in the conductors score, but it is passed to each part extracted. This is true of all system text (which is what tempo is a part of). You can turn any text into system system text by right clicking it (or clicking the"..." button to the right of text on something from the lines palette), selecting Text Style and checking system flag under the font size.

In reply to by mike320

Thank You . Another question I have is, what happens for winds and brass in pairs normally written on one staff, like FL 1 and 2 , Horns 1 and 2, etc.in the full score. These never get separate staves in a full score, unless there is a 3rd one like FL 3, which would have its own staff. etc. Do the players look at the same printed parts, like two flute players share the part, but one takes the top notes Fl 1 and the other the fl 2 notes? Or can MS extract ONLY fl 1 and ONly fl 2 on separate sheets (parts).

In reply to by delhud2

This could possible be done, but is pretty tricky: extract that FL1+2 part twice, Name one Flute 1, the other Flute 2, then in FL1 make all voice 2 notes and rests invisble (and maybe silent) and in FL2 do the same foa all voice 1 notes and rests. In the next major version this should be simpler, thanks to a project of 2016 GSoC

In reply to by delhud2

MuseScore can currently only extract 1 line of music into 1 part, it cannot split it into 2 different parts, so the 2 flautists would have to read each part off of the same sheet in MS.

When I transcribe scores, I generally keep the format of the full score I am transcribing from. As long as the 2 lines of music do not cross, they generally are on a single line for music and not very difficult for a musician to read. When they start crossing, the score will have 2 lines of music for as many measures as needed. At that point I add a new line as in the score. The unfortunate side effect is that the line stays there empty when not needed in continuous view that I use to enter the score. When I switch the score to pages, I hide empty staffs so only pages with music show up on the score. I do the same with the parts, except I extract both flutes as "Flute 1 & 2" and adjust the line breaks to have multiple lines only when needed. I do something similar when an oboist doubles English Horn. Having transcribe several score it has become apparent that with practice, reading 2 parts off of 1 line would not be difficult. The printers take measures to make it as easy as possible to distinguish the two parts.

The "french" horn lines normally do not cross, because horn players specialize in low and high notes, so multiple lines for horns I & II are rare with the exception of mostly late romantic pieces where there are 8 horns total in the score and various numbers of horns are on a line in the full score. Mahler was terrible at this. Because of the enormity of such scores, I have not considered what I would do if I were asked to separate such a score into parts. The process is too slow in version 2.x that it would take a large amount of time to make each change. When 3.0 comes out the process should be much faster, so I'll probably look at it then if not asked to before then.

As far as what the musicians are used to seeing, the horn players are used to the 2 parts on a line for the above reasons. This is true of both classical and concert band music. I'm not sure what Flute and oboe players are used to since I have never seen a classical flute or oboe part printed individually. In concert band I saw both individual and combined parts for the flutes (individual lines seemed to be far more common) and never saw more than one oboe part.

In 3.0 there are going to be provisions to show multiple lines of music on one line in a score, so the flexibility will be greatly increased. I'm not sure of all the details for its implementation, mostly because no one knows for sure since the code is still being written. I'll wait until the file format is finalized before I start testing 3.0 like I did with 2.1. It's called unstable, but the files will always be able to be opened in any 2.x version of MS.

In reply to by mike320

Do you by any chance do paid work on MS services? I had been referred there once or twice. i would only do that if my Opera got hopelessly involved in parts tech issues and it would probably have to be part of the requested funding process from whatever organization agree to perform it. L(A grant!)

In reply to by mike320

P.S. to mike220, Thanks for the info! My Anasazi opera will never be in 3.0 After the endless hours of work correcting layout errors, etc.the original 1.3 files after they had been opened and saved to be 2.0.3 files, I would never go through that again for yet another version of MS. I was told that I could keep 2.0.3 indefinitely on my computer to use, long after newer versions of MS came out. I might do a new score or two on a new version later. Del

In reply to by delhud2

Realistically, if you've already fixed your layout errors on moving from 2.0.3, then you should be in good shape for 3.0. As explained before, it is errors *already present in your score* that caused it to look bad when the layout changed as it did from 1.3 to 2.0.3 (and would also have happened even within 1.3 if/when you changed staff size, page size, or anything else really).

Once you've corrected the errors that were already present in your score, that should mean it will continue to look good despite whatever other layout changes occur in the future - whether those changes are due to new versions of MuseScore or just changes you make to page size etc. So again, if you actually corrected the errors you had originally made, they will of course remain corrected, and there will be very little work involved in making things look even better with 3.0 (which will feature be greatly improved layout over 2.0.by default, just as 2.0 is greatly improved by default over 1.3). But it will be quite a while before 3.0 is ready.

In reply to by delhud2

Realistically, while scores published before 1990 or so usually combined two flutes on one staff, scores since then are as likely as not to have separate staves, but most notation programs, like MuseScore, don't directly support the ability to generate separate parts if they are one one staff in the score. So its become quite common to have scores presented this way. Probably most conductors don't *like* this trend, but it it what it is. As mentioned, a future version of MuseScore should remove this limitation. Meanwhile, you'd have to do the parts manually - create two copies of the part, delete the notes of the other voice etc.

If you what textual hints to propagate to all parts, use System text. If it applies only to one os some parts, use staff text.
Tempo text, voltas, measure numbers, rehearsal marks are system based, so to proagate to all parts and always show up along with the top staff.
Hairpins and (de-)crescendo lines are parts based, so propagate only to their parts

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