Re: Beam issue
Thanks William for your help.
On 9/23/2023 1:09 PM, William Rehwinkel wrote:
See
https://lilypond.org/doc/v2.25/Documentation/notation/setting-automatic-beam-behavior
In engraving from the Romantic and Classical periods, beams often
begin midway through the measure in 3/4 time, but modern practice is
to avoid the false impression of 6/8 time (see Gould, p. 153). Similar
situations arise in 3/8 time. This behavior is controlled by the
context property beamHalfMeasure, which has effect only in time
signatures with 3 in the numerator:
\relative a' {
\time 3/4
r4. a8 a a |
\set Timing.beamHalfMeasure = ##f
r4. a8 a a |
}
Thanks,
-William
On 9/23/23 14:32, Rajesh Baskar wrote:
Hi,
In a normal musical notation when you have a time signature of 3/4
and have a dotted note, eighth note, eighth note and an eighth note -
that the first eighth note should have "no beam". This is how other
software like MuseScore and Finale works. Why does Lilypond do this?
I know there is a \noBeam markup but in my case this is be difficult
to use as I'm dynamically generating the notation.
Any advise will be helpful. See the attached image for illustration.
Thanks,
Raj
\version "2.22.2" \language english \header { tagline = ##f }
\score {\new Staff
{\set Staff.midiInstrument = #"acoustic grand" \key c \major
\time 3/4 \clef bass e,4. d,8 c, e, \bar "||"} \layout { \context {
\Score proportionalNotationDuration = #(ly:make-moment 1/2) } } \midi
{ \tempo 1 = 72}}
Re: Beam issue
See
https://lilypond.org/doc/v2.25/Documentation/notation/setting-automatic-beam-behavior
In engraving from the Romantic and Classical periods, beams often begin
midway through the measure in 3/4 time, but modern practice is to avoid
the false impression of 6/8 time (see Gould, p. 153). Similar situations
arise in 3/8 time. This behavior is controlled by the context property
beamHalfMeasure, which has effect only in time signatures with 3 in the
numerator:
\relative a' {
\time 3/4
r4. a8 a a |
\set Timing.beamHalfMeasure = ##f
r4. a8 a a |
}
Thanks,
-William
On 9/23/23 14:32, Rajesh Baskar wrote:
Hi,
In a normal musical notation when you have a time signature of 3/4 and
have a dotted note, eighth note, eighth note and an eighth note - that
the first eighth note should have "no beam". This is how other software
like MuseScore and Finale works. Why does Lilypond do this? I know there
is a \noBeam markup but in my case this is be difficult to use as I'm
dynamically generating the notation.
Any advise will be helpful. See the attached image for illustration.
Thanks,
Raj
\version "2.22.2" \language english \header { tagline = ##f }
\score {\new Staff
{\set Staff.midiInstrument = #"acoustic grand" \key c \major
\time 3/4 \clef bass e,4. d,8 c, e, \bar "||"} \layout { \context {
\Score proportionalNotationDuration = #(ly:make-moment 1/2) } } \midi {
\tempo 1 = 72}}
--
+ --- +
| William Rehwinkel - Oberlin College and |
| Conservatory '24 |
|will...@williamrehwinkel.net |
| PGP key:|
| https://ftp.williamrehwinkel.net/pubkey.txt |
+ --- +
OpenPGP_signature
Description: OpenPGP digital signature
Re[2]: Beam issue
Hi Raj
Alternatively, you can set beamHalfMeasure to #f to allow normal beaming
(all 6 quavers beamed in 3/4) except when the beam would start
mid-measure. See NR 1.2.4 towards the end:
\relative a' {
\time 3/4
r4. a8 a a |
\set Timing.beamHalfMeasure = ##f
r4. a8 a a |
}
This preserves the normal beaming of quavers as Gould recommends except
for this situation.
Trevor
-- Original Message --
From "Jakob Pedersen"
To lilypond-user@gnu.org
Date 23/09/2023 20:17:15
Subject Re: Beam issue
Hi Raj
I don't know why Lilypond does what it does, but you can achieve what
you desire by using
\overrideTimeSignatureSettings 3/4 1/4 1,1,1 #'() \time 3/4
in stead of just \time 3/4
Best wishes,
Jakob
On 23.09.2023 20.32, Rajesh Baskar wrote:
Hi,
In a normal musical notation when you have a time signature of 3/4 and
have a dotted note, eighth note, eighth note and an eighth note - that
the first eighth note should have "no beam". This is how other
software like MuseScore and Finale works. Why does Lilypond do this? I
know there is a \noBeam markup but in my case this is be difficult to
use as I'm dynamically generating the notation.
Any advise will be helpful. See the attached image for illustration.
Thanks,
Raj
\version "2.22.2" \language english \header { tagline = ##f }
\score {\new Staff
{\set Staff.midiInstrument = #"acoustic grand" \key c \major
\time 3/4 \clef bass e,4. d,8 c, e, \bar "||"} \layout { \context {
\Score proportionalNotationDuration = #(ly:make-moment 1/2) } } \midi
{ \tempo 1 = 72}}
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
Re: Beam issue
Hi Raj
I don't know why Lilypond does what it does, but you can achieve what
you desire by using
\overrideTimeSignatureSettings 3/4 1/4 1,1,1 #'() \time 3/4
in stead of just \time 3/4
Best wishes,
Jakob
On 23.09.2023 20.32, Rajesh Baskar wrote:
Hi,
In a normal musical notation when you have a time signature of 3/4 and
have a dotted note, eighth note, eighth note and an eighth note - that
the first eighth note should have "no beam". This is how other
software like MuseScore and Finale works. Why does Lilypond do this? I
know there is a \noBeam markup but in my case this is be difficult to
use as I'm dynamically generating the notation.
Any advise will be helpful. See the attached image for illustration.
Thanks,
Raj
\version "2.22.2" \language english \header { tagline = ##f }
\score {\new Staff
{\set Staff.midiInstrument = #"acoustic grand" \key c \major
\time 3/4 \clef bass e,4. d,8 c, e, \bar "||"} \layout { \context {
\Score proportionalNotationDuration = #(ly:make-moment 1/2) } } \midi
{ \tempo 1 = 72}}
Re: strange detached beam issue
Thanks, you were right. There was an unterminated Slur.outside-staff-priority
override that was causing the problem. This snippet displays the flying beam:
\version "2.24.1"
top = { \change Staff = "upper" \voiceTwo }
bottom = { \change Staff = "lower" \voiceOne }
upper = \relative c'' {
\override Slur.outside-staff-priority = #300
\time 2/2
\key c \major
\voiceOne
r8 bes'\mf( a gis a ees d cis |
d bes a gis a ees d cis |
d) bes'\dim( a\! gis a ees d cis |
d[ \bottom bes a gis] a[ ees d)] r8 |
\top
\oneVoice
r8\p
}
lower = \relative c' {
\clef bass
a4 r8 \top bes'( a gis a ees |
d cis d \bottom \voiceTwo bes a gis a ees |
d cis d bes' a gis a ees |
d cis d bes a gis a cis |
\oneVoice
fis,4)
}
\score {
\layout {
\context {
\Staff
\consists Merge_rests_engraver
}
\context {
\PianoStaff
\override StaffGrouper.staff-staff-spacing.basic-distance = #11
\override TextScript.avoid-slur = #'outside
\override TupletBracket.bracket-visibility = ##f
}
}
\new PianoStaff {
<<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
>>
}
}
> On Aug 16, 2023, at 3:51 AM, Paul Hodges wrote:
>
> I note some other differences between your image and what the code sample
> generates, in the slur and dynamic positions.
>
> I can't suggest what in particular is happening, but if this happened to me,
> I'd be looking for an earlier tweak or override which hadn't been cancelled.
>
> Paul
>
>
> From: Jin Choi
> To:
> Sent: 15/08/2023 23:11
> Subject: strange detached beam issue
>
> I have a section of piano music where two voices start in the treble clef and
> subsequently move down into the bass clef. When the right hand moves down,
> the beam stays in the treble clef unattached to anything:
>
> When I try to isolate this section, the problem does not occur. I am
> mystified as to what is going on. What might be some things I could try?
Re: strange detached beam issue
I note some other differences between your image and what the code sample generates, in the slur and dynamic positions. I can't suggest what in particular is happening, but if this happened to me, I'd be looking for an earlier tweak or override which hadn't been cancelled. Paul From: Jin Choi To: Sent: 15/08/2023 23:11 Subject: strange detached beam issue I have a section of piano music where two voices start in the treble clef and subsequently move down into the bass clef. When the right hand moves down, the beam stays in the treble clef unattached to anything: When I try to isolate this section, the problem does not occur. I am mystified as to what is going on. What might be some things I could try?
Re: strange detached beam issue
Yes, I noted that the problem doesn’t occur in my snippet. I will try to add
things to it until I can get it to happen. In my full text, I have just had it
happen again, in a similar passage where both parts leave the upper stave.
Forcing a voice to “hold open” the staff again fixes it for me.
> On Aug 15, 2023, at 9:37 PM, William Rehwinkel
> wrote:
>
> It should be noted that on 2.25.7 this doesn't happen on my machine, and the
> beam renders correctly (after running convert-ly on your snippet, it didn't
> change anything).
>
> -William
>
> On 8/15/23 18:11, Jin Choi wrote:
>> I have a section of piano music where two voices start in the treble clef
>> and subsequently move down into the bass clef. When the right hand moves
>> down, the beam stays in the treble clef unattached to anything:
>>
>>
>>
>>
>> When I try to isolate this section, the problem does not occur. I am
>> mystified as to what is going on. What might be some things I could try?
>>
>> \version "2.24.1"
>>
>> top = { \change Staff = "upper" \voiceTwo }
>> bottom = { \change Staff = "lower" \voiceOne }
>>
>> upper = \relative c'' {
>> \time 2/2
>> \key c \major
>> \voiceOne
>> r8 bes'\mf( a gis a ees d cis |
>> d bes a gis a ees d cis |
>> d) bes'\dim( a\! gis a ees d cis |
>> d[ \bottom bes a gis] a[ ees d)] r8 |
>> \top
>> \oneVoice
>> r8\p
>> }
>>
>> lower = \relative c' {
>> \clef bass
>> a4 r8 \top bes'( a gis a ees |
>> d cis d \bottom \voiceTwo bes a gis a ees |
>> d cis d bes' a gis a ees |
>> d cis d bes a gis a cis |
>> \oneVoice
>> fis,4)
>>
>> }
>>
>> \score {
>> \layout {
>> \context {
>> \Staff
>> \consists Merge_rests_engraver
>> }
>> \context {
>> \PianoStaff
>> \override StaffGrouper.staff-staff-spacing.basic-distance = #11
>> \override TextScript.avoid-slur = #'outside
>> \override TupletBracket.bracket-visibility = ##f
>> }
>> }
>> \new PianoStaff {
>> <<
>> \new Staff = "upper" \upper
>> \new Staff = "lower" \lower
>> >>
>> }
>> }
>>
>
> --
> + --- +
> | William Rehwinkel - Oberlin College and |
> | Conservatory '24 |
> |will...@williamrehwinkel.net
> |
> | PGP key:|
> | https://ftp.williamrehwinkel.net/pubkey.txt |
> + --- +
Re: strange detached beam issue
It should be noted that on 2.25.7 this doesn't happen on my machine, and
the beam renders correctly (after running convert-ly on your snippet, it
didn't change anything).
-William
On 8/15/23 18:11, Jin Choi wrote:
I have a section of piano music where two voices start in the treble clef and
subsequently move down into the bass clef. When the right hand moves down, the
beam stays in the treble clef unattached to anything:
When I try to isolate this section, the problem does not occur. I am mystified
as to what is going on. What might be some things I could try?
\version "2.24.1"
top = { \change Staff = "upper" \voiceTwo }
bottom = { \change Staff = "lower" \voiceOne }
upper = \relative c'' {
\time 2/2
\key c \major
\voiceOne
r8 bes'\mf( a gis a ees d cis |
d bes a gis a ees d cis |
d) bes'\dim( a\! gis a ees d cis |
d[ \bottom bes a gis] a[ ees d)] r8 |
\top
\oneVoice
r8\p
}
lower = \relative c' {
\clef bass
a4 r8 \top bes'( a gis a ees |
d cis d \bottom \voiceTwo bes a gis a ees |
d cis d bes' a gis a ees |
d cis d bes a gis a cis |
\oneVoice
fis,4)
}
\score {
\layout {
\context {
\Staff
\consists Merge_rests_engraver
}
\context {
\PianoStaff
\override StaffGrouper.staff-staff-spacing.basic-distance = #11
\override TextScript.avoid-slur = #'outside
\override TupletBracket.bracket-visibility = ##f
}
}
\new PianoStaff {
<<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
>>
}
}
--
+ --- +
| William Rehwinkel - Oberlin College and |
| Conservatory '24 |
|will...@williamrehwinkel.net |
| PGP key:|
|https://ftp.williamrehwinkel.net/pubkey.txt |
+ --- +
OpenPGP_signature
Description: OpenPGP digital signature
Re: strange detached beam issue
I solved the issue, but still don’t understand why it happened.
Apparently, when both voices leave the top staff, the staff or some context or
something just goes away at that point, even though it’s in use later? I just
added a third parallel voice that sits in the top staff and s1*4 to hold it
open, and that fixed the beaming issue. I have no idea why that worked, or why
it works in the standalone snippet and not in my original case.
> On Aug 15, 2023, at 6:11 PM, Jin Choi wrote:
>
> I have a section of piano music where two voices start in the treble clef and
> subsequently move down into the bass clef. When the right hand moves down,
> the beam stays in the treble clef unattached to anything:
>
>
>
> When I try to isolate this section, the problem does not occur. I am
> mystified as to what is going on. What might be some things I could try?
>
> \version "2.24.1"
>
> top = { \change Staff = "upper" \voiceTwo }
> bottom = { \change Staff = "lower" \voiceOne }
>
> upper = \relative c'' {
> \time 2/2
> \key c \major
> \voiceOne
> r8 bes'\mf( a gis a ees d cis |
> d bes a gis a ees d cis |
> d) bes'\dim( a\! gis a ees d cis |
> d[ \bottom bes a gis] a[ ees d)] r8 |
> \top
> \oneVoice
> r8\p
> }
>
> lower = \relative c' {
> \clef bass
> a4 r8 \top bes'( a gis a ees |
> d cis d \bottom \voiceTwo bes a gis a ees |
> d cis d bes' a gis a ees |
> d cis d bes a gis a cis |
> \oneVoice
> fis,4)
>
> }
>
> \score {
> \layout {
>\context {
> \Staff
> \consists Merge_rests_engraver
>}
>\context {
> \PianoStaff
> \override StaffGrouper.staff-staff-spacing.basic-distance = #11
> \override TextScript.avoid-slur = #'outside
> \override TupletBracket.bracket-visibility = ##f
>}
> }
> \new PianoStaff {
><<
>\new Staff = "upper" \upper
>\new Staff = "lower" \lower
>>>
> }
> }
>
strange detached beam issue
I have a section of piano music where two voices start in the treble clef and
subsequently move down into the bass clef. When the right hand moves down, the
beam stays in the treble clef unattached to anything:
When I try to isolate this section, the problem does not occur. I am mystified
as to what is going on. What might be some things I could try?
\version "2.24.1"
top = { \change Staff = "upper" \voiceTwo }
bottom = { \change Staff = "lower" \voiceOne }
upper = \relative c'' {
\time 2/2
\key c \major
\voiceOne
r8 bes'\mf( a gis a ees d cis |
d bes a gis a ees d cis |
d) bes'\dim( a\! gis a ees d cis |
d[ \bottom bes a gis] a[ ees d)] r8 |
\top
\oneVoice
r8\p
}
lower = \relative c' {
\clef bass
a4 r8 \top bes'( a gis a ees |
d cis d \bottom \voiceTwo bes a gis a ees |
d cis d bes' a gis a ees |
d cis d bes a gis a cis |
\oneVoice
fis,4)
}
\score {
\layout {
\context {
\Staff
\consists Merge_rests_engraver
}
\context {
\PianoStaff
\override StaffGrouper.staff-staff-spacing.basic-distance = #11
\override TextScript.avoid-slur = #'outside
\override TupletBracket.bracket-visibility = ##f
}
}
\new PianoStaff {
<<
\new Staff = "upper" \upper
\new Staff = "lower" \lower
>>
}
}
