Beaming conventions
-
- Posts: 2677
- Joined: 05 Oct 2015, 14:25
- Location: Raleigh, NC USA
Re: Beaming conventions
I agree with you about the position of the dot, MJCube. As you say, it would be too far away if positioned under the other dot. And in this case, having the dot near the note could help the eye thread its way through the complexity of the voice leading.
M1 Mac mini (OS 12.4), Dorico 5, Finale 25.5, GPO 4, Affinity Publisher 2, SmartScore 64 Pro, JW Plug-ins, TG Tools, Keyboard maestro
-
- Posts: 2677
- Joined: 05 Oct 2015, 14:25
- Location: Raleigh, NC USA
Re: Beaming conventions
Here is an edited Finale version of the excerpt which brings the note-heads closer together than in the Dorico default and moves the dot under discussion:
M1 Mac mini (OS 12.4), Dorico 5, Finale 25.5, GPO 4, Affinity Publisher 2, SmartScore 64 Pro, JW Plug-ins, TG Tools, Keyboard maestro
Re: Beaming conventions
Thanks, John – I like it! What is your opinion of breaking the secondary beams for the last eight 32nd notes?
-
- Posts: 2677
- Joined: 05 Oct 2015, 14:25
- Location: Raleigh, NC USA
Re: Beaming conventions
Thank you, MJCube, I appreciate that.
I think that Arnstein was correct in thinking that strictly on practical grounds one should always break secondary beams to clarify such patterns when they appear in orchestral parts. He always broke secondary beams for groups of 8 16ths or 32nds into 4 + 4, 12 into 4 + 4 + 4 etc.
However, when such patterns appear in solo or chamber music, it would depend on what the composer is expressing. I can imagine cases where secondary beam breaks would be visually disruptive and suggest an inner accentuation where none is desired. Examples by JS Bach come to mind:
But what is your opinion?
I think that Arnstein was correct in thinking that strictly on practical grounds one should always break secondary beams to clarify such patterns when they appear in orchestral parts. He always broke secondary beams for groups of 8 16ths or 32nds into 4 + 4, 12 into 4 + 4 + 4 etc.
However, when such patterns appear in solo or chamber music, it would depend on what the composer is expressing. I can imagine cases where secondary beam breaks would be visually disruptive and suggest an inner accentuation where none is desired. Examples by JS Bach come to mind:
But what is your opinion?
M1 Mac mini (OS 12.4), Dorico 5, Finale 25.5, GPO 4, Affinity Publisher 2, SmartScore 64 Pro, JW Plug-ins, TG Tools, Keyboard maestro
Re: Beaming conventions
This is done in MuseScore 2
Before edit: After 11 edits: What is the standard in Dorico, and how many editing steps is needed?
Before edit: After 11 edits: What is the standard in Dorico, and how many editing steps is needed?
Re: Beaming conventions
LilyPond output:
I see that both MuseScore and LP have the same horizontal dots alignment.
The code:
Code: Select all
\version "2.19"
\layout {
indent = 0
}
\markup\italic "Default output:"
{
\clef "G_8"
\key a\major
\omit Staff.TimeSignature
<<
{
\voiceOne
| % mes.13
b16 cis'32 d'! e'8 d'16 cis' b8
cis'16 b32 cis' d' e' fis' g' a' e' g' fis' e' d' cis' b
} \\
{
\voiceThree
| % mes.13
gis!8. a16 fis a a gis s2
} \\
{
\voiceTwo
| % mes.13
e8. cis16 d!8 e a,2
}
>>
}
\markup\italic "After two edits:"
{
\clef "G_8"
\key a\major
\omit Staff.TimeSignature
%% Edit 1:
\set Timing.beamExceptions = #'()
\set Timing.beatStructure = 2,2
<<
{
\voiceOne
| % mes.13
%% Edit 2:
\offset positions #'(1.4 . 1.4) Beam
b16 cis'32 d'! e'8 d'16 cis' b8
cis'16[ b32 cis' d' e' fis' g' a' e' g' fis' e' d' cis' b]
} \\
{
\voiceThree
| % mes.13
gis!8. a16 fis a a gis s2
} \\
{
\voiceTwo
| % mes.13
e8. cis16 d!8 e a,2
}
>>
}
\markup\italic "Alternative after three edits:"
{
\clef "G_8"
\key a\major
\omit Staff.TimeSignature
%% Edit 1:
\set Timing.beamExceptions = #'()
\set Timing.beatStructure = 2,2
<<
{
\voiceOne
| % mes.13
%% Edit 2:
\offset positions #'(.8 . .8) Beam
b16 cis'32 d'! e'8 d'16 cis' b8
cis'16[ b32 cis' d' e' fis' g' a' e' g' fis' e' d' cis' b]
} \\
{
\voiceThree
| % mes.13
%% Edit 3:
\offset positions #'(-.6 . -.6) Beam
gis!8. a16 fis a a gis s2
} \\
{
\voiceTwo
| % mes.13
e8. cis16 d!8 e a,2
}
>>
}
Re: Beaming conventions
Actually, MuseScore 2 can do with less edits. I counted EACH item that has to be moved, yet these can be multiple selected and edited with ONE command.
Re: Beaming conventions
Well actually, to be honest, I need some other edits to reach the Finale output (whit a pseudo Dorico G clef for the fun):
The code:
Code: Select all
\version "2.19"
%% Not needed:
%\include "myTools.ily"
%\dorico
\layout {
indent = 0
}
global = {
\clef "G_8"
\key a\major
\time 2/2
\numericTimeSignature
%\omit Staff.TimeSignature
}
\markup\italic "Default output:"
{
\global
<<
{
\voiceOne
| % mes.13
b16 cis'32 d'! e'8 d'16 cis' b8
cis'16 b32 cis' d' e' fis' g' a' e' g' fis' e' d' cis' b
} \\
{
\voiceThree
| % mes.13
gis!8. a16 fis a a gis s2
} \\
{
\voiceTwo
| % mes.13
e8. cis16 d!8 e a,2
}
>>
}
\markup\italic "After two edits:"
{
\global
%% Edit 1:
\set Timing.beamExceptions = #'()
\set Timing.beatStructure = 2,2
<<
{
\voiceOne
| % mes.13
%% Edit 2:
\offset positions #'(1.4 . 1.4) Beam
b16 cis'32 d'! e'8 d'16 cis' b8
cis'16[ b32 cis' d' e' fis' g' a' e' g' fis' e' d' cis' b]
} \\
{
\voiceThree
| % mes.13
gis!8. a16 fis a a gis s2
} \\
{
\voiceTwo
| % mes.13
e8. cis16 d!8 e a,2
}
>>
}
\markup\italic "Alternative after three edits (lower beams):"
{
\global
%% Edit 1:
\set Timing.beamExceptions = #'()
\set Timing.beatStructure = 2,2
<<
{
\voiceOne
| % mes.13
%% Edit 2:
\offset positions #'(.7 . .7) Beam
b16 cis'32 d'! e'8 d'16 cis' b8
cis'16[ b32 cis' d' e' fis' g' a' e' g' fis' e' d' cis' b]
} \\
{
\voiceThree
| % mes.13
%% Edit 3:
\offset positions #'(-.5 . -.5) Beam
gis!8. a16 fis a a gis s2
} \\
{
\voiceTwo
| % mes.13
e8. cis16 d!8 e a,2
}
>>
}
\markup\italic "Alternative after four edits (strict beaming):"
{
\global
%% Edit 1:
\set Timing.beamExceptions = #'()
\set Timing.beatStructure = 2,2
%% Edit 4:
\set strictBeatBeaming = ##t
<<
{
\voiceOne
| % mes.13
%% Edit 2:
\offset positions #'(.7 . .7) Beam
b16 cis'32 d'! e'8 d'16 cis' b8
cis'16[ b32 cis' d' e' fis' g' a' e' g' fis' e' d' cis' b]
} \\
{
\voiceThree
| % mes.13
%% Edit 3:
\offset positions #'(-.5 . -.5) Beam
%% Edit 4:
\set strictBeatBeaming = ##t
gis!8. a16 fis a a gis s2
} \\
{
\voiceTwo
| % mes.13
e8. cis16 d!8 e a,2
}
>>
}
\markup\italic "Alternative after five edits (dots):"
{
\global
%% Edit 1:
\set Timing.beamExceptions = #'()
\set Timing.beatStructure = 2,2
%% Edit 4:
\set strictBeatBeaming = ##t
<<
{
\voiceOne
| % mes.13
%% Edit 2:
\offset positions #'(.7 . .7) Beam
b16 cis'32 d'! e'8 d'16 cis' b8
cis'16[ b32 cis' d' e' fis' g' a' e' g' fis' e' d' cis' b]
} \\
{
\voiceThree
| % mes.13
%% Edit 3:
\offset positions #'(-.5 . -.5) Beam
%% Edit 4:
\set strictBeatBeaming = ##t
gis!8. a16 fis a a gis s2
} \\
{
\voiceTwo
| % mes.13
%% Edit 5:
\once\dotsUp
e8. cis16 d!8 e a,2
}
>>
}
-
- Posts: 2677
- Joined: 05 Oct 2015, 14:25
- Location: Raleigh, NC USA
Re: Beaming conventions
Here are the 6 edits in the Finale version. Each edit is one action only and took only seconds to accomplish with my trusty mouse.
If I were using Dorico, it would have taken 7 edits, 4 to adjust the middle voice notes, 1 to adjust the dot on the lower voice, 1 to restore the secondary beam break, and 1 to raise the beam on the top voice. I have no idea how involved these edits would have been in Dorico.
If I were using Dorico, it would have taken 7 edits, 4 to adjust the middle voice notes, 1 to adjust the dot on the lower voice, 1 to restore the secondary beam break, and 1 to raise the beam on the top voice. I have no idea how involved these edits would have been in Dorico.
M1 Mac mini (OS 12.4), Dorico 5, Finale 25.5, GPO 4, Affinity Publisher 2, SmartScore 64 Pro, JW Plug-ins, TG Tools, Keyboard maestro
Re: Beaming conventions
Luckily, there's no need to fin that out, since it does most of them automatically, or with settings specified before entering the piece.John Ruggero wrote: I have no idea how involved these edits would have been in Dorico.
The only two exceptions are the beams in the upper voice and the augmentation dot (both 2 steps). Personally, I would never have offset the dot (but would have needed to spend the extra time aligning it if I was using Finale), so for me, that leaves a single step.