Re: beaming problem
Haipeng, Now that I have seen the two versions of beaming from Sibelius and LilyPond I would say this; As a performing orchestral musician myself, I would very much rather see the LilyPond version with sixteenths grouped as quarters rather than the Sibelius version with long groups of sixteenths. If you feel a strong need to show beat grouping then you should, at the very least, use subdivisions as Simon showed. Those long groups of sixteenths are, frankly, annoying to read without some sort of sub-grouping. -David - Original Message - From: Haipeng Hu hhpcompo...@gmail.com To: bobr...@centrum.is Cc: lilypond-user lilypond-user@gnu.org Sent: Friday, May 29, 2015 10:43:26 AM Subject: Re: beaming problem On 5/29/15, bobr...@centrum.is bobr...@centrum.is wrote: Haipeng, There was no attachment. -David - Original Message - From: Haipeng Hu hhpcompo...@gmail.com To: lilypond-user lilypond-user@gnu.org Sent: Friday, May 29, 2015 9:42:31 AM Subject: beaming problem Hello, I'm now composing an orchestral work, in which there are plenty of meter changes such as 5/4 and 6/4. Since I'm blind, I gave part of it to a teacher, and he told me that the beaming in 5/4 and 6/4 is incorrect. He told me the beaming must be clear for performance, so 5/4 must be 3/4+2/4, and 6/4 3+3. So, please look at the two pictures in zipped attachment. The one was directly from Lilypond, and the other from Sibelius, in which I imported the midi file. The beaming in Sibelius is correct, while in Lilypond, all 16th notes are grouped as 4th. I checked the time-signature-setting.scm, and found the setting for 6/4 is wrong. Although the comment says for 32nd notes, the line below it still groups 16ths as 4ths. Is this a mistake? Could anyone check the theory book for beaming rules and correct the scm file? I myself modified it and added 5/4, but don't know whether the problem has been solved. Thank you in advance! Regards Haipeng ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user Sorry, I'll post it again, perhaps it was lost at that time. Haipeng ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beaming problem
Hello, I'm now composing an orchestral work, in which there are plenty of meter changes such as 5/4 and 6/4. Since I'm blind, I gave part of it to a teacher, and he told me that the beaming in 5/4 and 6/4 is incorrect. He told me the beaming must be clear for performance, so 5/4 must be 3/4+2/4, and 6/4 3+3. So, please look at the two pictures in zipped attachment. The one was directly from Lilypond, and the other from Sibelius, in which I imported the midi file. The beaming in Sibelius is correct, while in Lilypond, all 16th notes are grouped as 4th. I checked the time-signature-setting.scm, and found the setting for 6/4 is wrong. Although the comment says for 32nd notes, the line below it still groups 16ths as 4ths. Is this a mistake? Could anyone check the theory book for beaming rules and correct the scm file? I myself modified it and added 5/4, but don't know whether the problem has been solved. Thank you in advance! Regards Haipeng You may wish to look at http://lsr.di.unimi.it/LSR/Item?id=528 and possibly also at http://lsr.di.unimi.it/LSR/Item?id=743 King regards, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on request or at public keyserver signature.asc Description: This is a digitally signed message part. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beaming problem
Haipeng, There was no attachment. -David - Original Message - From: Haipeng Hu hhpcompo...@gmail.com To: lilypond-user lilypond-user@gnu.org Sent: Friday, May 29, 2015 9:42:31 AM Subject: beaming problem Hello, I'm now composing an orchestral work, in which there are plenty of meter changes such as 5/4 and 6/4. Since I'm blind, I gave part of it to a teacher, and he told me that the beaming in 5/4 and 6/4 is incorrect. He told me the beaming must be clear for performance, so 5/4 must be 3/4+2/4, and 6/4 3+3. So, please look at the two pictures in zipped attachment. The one was directly from Lilypond, and the other from Sibelius, in which I imported the midi file. The beaming in Sibelius is correct, while in Lilypond, all 16th notes are grouped as 4th. I checked the time-signature-setting.scm, and found the setting for 6/4 is wrong. Although the comment says for 32nd notes, the line below it still groups 16ths as 4ths. Is this a mistake? Could anyone check the theory book for beaming rules and correct the scm file? I myself modified it and added 5/4, but don't know whether the problem has been solved. Thank you in advance! Regards Haipeng ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beaming problem
Hello,
Am 29.05.2015 um 11:42 schrieb Haipeng Hu:
Hello,
I'm now composing an orchestral work, in which there are plenty of
meter changes such as 5/4 and 6/4. Since I'm blind,
It’s so impressive that you are able to do this – write lilypond code,
read scm files etc. – without eyesight. Kudos!
I gave part of it
to a teacher, and he told me that the beaming in 5/4 and 6/4 is
incorrect. He told me the beaming must be clear for performance, so
5/4 must be 3/4+2/4, and 6/4 3+3. So, please look at the two pictures
in zipped attachment.
No attachment there…
The one was directly from Lilypond, and the
other from Sibelius, in which I imported the midi file. The beaming in
Sibelius is correct, while in Lilypond, all 16th notes are grouped as
4th. I checked the time-signature-setting.scm, and found the setting
for 6/4 is wrong. Although the comment says for 32nd notes, the line
below it still groups 16ths as 4ths. Is this a mistake? Could anyone
check the theory book for beaming rules and correct the scm file?
I believe that Lily’s current behaviour is carefully designed and will
comply with the relevant literature. If in 6/4 time 16th notes would be
beamed by half bars, the very long groups of 12 notes would be very
difficult to read, except if you use subdivision:
%
\version 2.19.20
\score {
{
\set subdivideBeams = ##t
\time 6/4
\set Timing.beamExceptions = #'()
\repeat unfold 24 c'16
}
}
%%
See also
http://lilypond.org/doc/v2.18/Documentation/notation/beams#setting-automatic-beam-behavior
for more information on using baseMoment, beatStructure, and beamExceptions.
HTH, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beaming problem
Thank you for your explanation, and I can manage how I want now. Regards Haipeng ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem
Wim,
you are missing the open [ for the groupings in the bottomstaff.
regards,
Shane
On Sun, Dec 28, 2014 at 12:32 PM, Wim van Dommelen m...@wimvd.nl wrote:
Hi,
I stumbled on a small beaming problem. Attached two small .PNG’s for what
should be there (never mind the 7/4, that is a writo), my experimental
output and below my compiling code as for what I tried. The problem is in
the second voice showing hickups in the second part of both measures where
the 1/16 notes are beamed special. When I don’t do the manual beaming I get
a pattern which the composer doesn’t like. It looks allright in the first
voice, I have about 10 of these and always the beaming in the second voice
breaks, the first voice is allright. May be that is a clue to where the
problem is?
Is there a possibility to get these beamings in a straigth line? Or is
this a bug I which should report?
Regards,
Wim.
My simple experimenting code, but not working as I want it to:
\version 2.18.0
VoiceI = \relative f' {
\time 7/8
e8.[ dis16] e8.[ dis16]
fis[
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
cis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
cis
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
b
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
b
cis] |
e8.[ dis16] e8.[ dis16]
fis[
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
cis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
cis
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
b
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
b
cis] |
}
VoiceII= \relative f' {
\time 7/8
fis16 e8. fis16 e8.
e16
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
e
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
e
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
fis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
e
fis] |
e16 fis8. e16 fis8.
e16
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
fis
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
fis
\set stemLeftBeamCount = #2
\set stemRightBeamCount = #1
e
\set stemLeftBeamCount = #1
\set stemRightBeamCount = #2
fis
e] |
}
\score {
\new StaffGroup {
\new Staff {
\VoiceI
}
\new Staff {
\VoiceII
}
}
}%end score
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem
Wim,
On Sun, Dec 28, 2014 at 11:47 AM, Shane Brandes sh...@grayskies.net wrote:
Wim,
you are missing the open [ for the groupings in the bottomstaff.
regards,
Shane
On Sun, Dec 28, 2014 at 12:32 PM, Wim van Dommelen m...@wimvd.nl wrote:
Hi,
I stumbled on a small beaming problem. Attached two small .PNG’s for what
should be there (never mind the 7/4, that is a writo), my experimental
output and below my compiling code as for what I tried. The problem is in
the second voice showing hickups in the second part of both measures where
the 1/16 notes are beamed special. When I don’t do the manual beaming I get
a pattern which the composer doesn’t like. It looks allright in the first
voice, I have about 10 of these and always the beaming in the second voice
breaks, the first voice is allright. May be that is a clue to where the
problem is?
Is there a possibility to get these beamings in a straigth line? Or is
this a bug I which should report?
Regards,
Wim.
Looks like Shane has found your problem, but I'd like to suggest a much
less tedious way to get what you're after:
\version 2.18.0
VoiceI = \relative f' {
\time 7/8
e8.[ dis16] e8.[ dis16]
\set subdivideBeams = ##t
fis[ cis cis b b cis] |
e8.[ dis16] e8.[ dis16]
fis[ cis cis b b cis] |
}
VoiceII= \relative f' {
\time 7/8
\set subdivideBeams = ##t
fis16 e8. fis16 e8.
e16[ e e fis e fis] |
e16 fis8. e16 fis8.
e16 fis fis e fis e] |
}
\score {
\new StaffGroup {
\new Staff {
\VoiceI
}
\new Staff {
\VoiceII
}
}
}%end score
You can read about this in the snippet subdividing beams at
http://lilypond.org/doc/v2.18/Documentation/notation/beams
--David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem
Hello,
Thanks for your anser.
The last line ov VoiceII should read (typo):
e16 [fis fis e fis e] |
JM
Le 28 déc. 2014 à 18:51, David Nalesnik david.nales...@gmail.com a écrit :
Wim,
On Sun, Dec 28, 2014 at 11:47 AM, Shane Brandes sh...@grayskies.net
mailto:sh...@grayskies.net wrote:
Wim,
you are missing the open [ for the groupings in the bottomstaff.
regards,
Shane
On Sun, Dec 28, 2014 at 12:32 PM, Wim van Dommelen m...@wimvd.nl
mailto:m...@wimvd.nl wrote:
Hi,
I stumbled on a small beaming problem. Attached two small .PNG’s for what
should be there (never mind the 7/4, that is a writo), my experimental output
and below my compiling code as for what I tried. The problem is in the second
voice showing hickups in the second part of both measures where the 1/16
notes are beamed special. When I don’t do the manual beaming I get a pattern
which the composer doesn’t like. It looks allright in the first voice, I have
about 10 of these and always the beaming in the second voice breaks, the
first voice is allright. May be that is a clue to where the problem is?
Is there a possibility to get these beamings in a straigth line? Or is this a
bug I which should report?
Regards,
Wim.
Looks like Shane has found your problem, but I'd like to suggest a much less
tedious way to get what you're after:
\version 2.18.0
VoiceI = \relative f' {
\time 7/8
e8.[ dis16] e8.[ dis16]
\set subdivideBeams = ##t
fis[ cis cis b b cis] |
e8.[ dis16] e8.[ dis16]
fis[ cis cis b b cis] |
}
VoiceII= \relative f' {
\time 7/8
\set subdivideBeams = ##t
fis16 e8. fis16 e8.
e16[ e e fis e fis] |
e16 fis8. e16 fis8.
e16 fis fis e fis e] |
}
\score {
\new StaffGroup {
\new Staff {
\VoiceI
}
\new Staff {
\VoiceII
}
}
}%end score
You can read about this in the snippet subdividing beams at
http://lilypond.org/doc/v2.18/Documentation/notation/beams
http://lilypond.org/doc/v2.18/Documentation/notation/beams
--David
___
lilypond-user mailing list
lilypond-user@gnu.org mailto:lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem
Shane, David and Jacques,
Thanks very much, both solutions work, David show the easiest one for a regular
set-up, but Shane solutions gives me also the opportunity to do a 3-3 division
when needed.
Thanks again!
Regards,
Wim.
On 28 Dec 2014, at 20:07 , Jacques Menu imj-muz...@bluewin.ch wrote:
Hello,
Thanks for your anser.
The last line ov VoiceII should read (typo):
e16 [fis fis e fis e] |
JM
Le 28 déc. 2014 à 18:51, David Nalesnik david.nales...@gmail.com
mailto:david.nales...@gmail.com a écrit :
Wim,
On Sun, Dec 28, 2014 at 11:47 AM, Shane Brandes sh...@grayskies.net
mailto:sh...@grayskies.net wrote:
Wim,
you are missing the open [ for the groupings in the bottomstaff.
regards,
Shane
On Sun, Dec 28, 2014 at 12:32 PM, Wim van Dommelen m...@wimvd.nl
mailto:m...@wimvd.nl wrote:
Hi,
I stumbled on a small beaming problem. Attached two small .PNG’s for what
should be there (never mind the 7/4, that is a writo), my experimental
output and below my compiling code as for what I tried. The problem is in
the second voice showing hickups in the second part of both measures where
the 1/16 notes are beamed special. When I don’t do the manual beaming I get
a pattern which the composer doesn’t like. It looks allright in the first
voice, I have about 10 of these and always the beaming in the second voice
breaks, the first voice is allright. May be that is a clue to where the
problem is?
Is there a possibility to get these beamings in a straigth line? Or is this
a bug I which should report?
Regards,
Wim.
Looks like Shane has found your problem, but I'd like to suggest a much less
tedious way to get what you're after:
\version 2.18.0
VoiceI = \relative f' {
\time 7/8
e8.[ dis16] e8.[ dis16]
\set subdivideBeams = ##t
fis[ cis cis b b cis] |
e8.[ dis16] e8.[ dis16]
fis[ cis cis b b cis] |
}
VoiceII= \relative f' {
\time 7/8
\set subdivideBeams = ##t
fis16 e8. fis16 e8.
e16[ e e fis e fis] |
e16 fis8. e16 fis8.
e16 fis fis e fis e] |
}
\score {
\new StaffGroup {
\new Staff {
\VoiceI
}
\new Staff {
\VoiceII
}
}
}%end score
You can read about this in the snippet subdividing beams at
http://lilypond.org/doc/v2.18/Documentation/notation/beams
http://lilypond.org/doc/v2.18/Documentation/notation/beams
--David
___
lilypond-user mailing list
lilypond-user@gnu.org mailto:lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beaming problem in 2.14
Added as http://code.google.com/p/lilypond/issues/detail?id=1706
--
Phil Holmes
- Original Message -
From: Stefan Thomas
To: lilypond-user
Sent: Thursday, June 23, 2011 12:31 PM
Subject: beaming problem in 2.14
Dear community,
the following code works fine in 2.12.3. but doesn't in 2.14.1.
Is there a possibility to get it working in 2.14.1?
\version 2.14.1
music = {
\clef bass r2 r4 r8 f,
r2 r4 g,8 r
r4 f, 8 r8 r2
}
beams = {
\repeat unfold 24 { s8[ s ] s[ s]} % this line causes the error!
}
\new Staff {
\context Voice { \beams } { \music}
}
--
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beaming problem in 2.14
On 6/23/2011 11:31 AM, Stefan Thomas wrote:
Dear community,
the following code works fine in 2.12.3. but doesn't in 2.14.1.
Is there a possibility to get it working in 2.14.1?
\version 2.14.1
music = {
\clef bass r2 r4 r8 f,
r2 r4 g,8 r
r4 f, 8 r8 r2
}
beams = {
\repeat unfold 24 { s8[ s ] s[ s]} % this line causes the error!
}
\new Staff {
\context Voice { \beams } { \music}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
I don't understand what you're after here. The 'beams' definition adds
up to 12 measures of beaming, much of which takes place in the middle of
rests, while the music itself is only three measures.
-David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem introduced with 2.13.60
I had the same problem in a score with these notes : d4-- c8-( g ~ g) g'-( f e) I had no problem before 2.13.60 Philippe -- View this message in context: http://old.nabble.com/Beaming-problem-introduced-with-2.13.60-tp31416244p31439163.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem introduced with 2.13.60
On Apr 20, 2011, at 4:01 AM, flup2 wrote: I had the same problem in a score with these notes : d4-- c8-( g ~ g) g'-( f e) I had no problem before 2.13.60 Philippe Your snippet compiles fine in the most recent development version. Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem introduced with 2.13.60
So do it here when running only that line. The problem is that, in a longer file (without changes from 2.13.33), here is what it looks like. I also receive a warning taille de hampe bizarre; vérifier la présence de liens étroits (the french version of the message quoted earlier about beam, narrow bounds etc.). http://old.nabble.com/file/p31440777/stem.jpg No problem with these measures alone, but in a whole score, the problem occurs Philippe -- View this message in context: http://old.nabble.com/Beaming-problem-introduced-with-2.13.60-tp31416244p31440777.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem introduced with 2.13.60
- Original Message - From: flup2 phili...@philmassart.net To: lilypond-user@gnu.org Sent: Wednesday, April 20, 2011 1:24 PM Subject: Re: Beaming problem introduced with 2.13.60 So do it here when running only that line. The problem is that, in a longer file (without changes from 2.13.33), here is what it looks like. I also receive a warning taille de hampe bizarre; vérifier la présence de liens étroits (the french version of the message quoted earlier about beam, narrow bounds etc.). http://old.nabble.com/file/p31440777/stem.jpg No problem with these measures alone, but in a whole score, the problem occurs Philippe This is a known bug that, as Mike says, has been fixed in the latest development version. That version is not yet publically available. -- Phil Holmes ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem introduced with 2.13.60
The problem still exists with the \stemUp and \stemDown commands and the
first bar removed:
\version 2.13.60
\language english
\relative c' {
\time 3/4
cs16 a'' a fs fs ef ef c c a fs( d) |
}
attachment: test.preview.png___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem
Thank you, Mats.
Here is an instance of the file in which the beaming problem arises, they're
eight separate files, the last one containing the score:
%*Bwv1057_01_fl1.ly**
\version 2.10.33
flautoa = \relative c' {
\set Staff.instrumentName = #Flauto I
%\set Staff.shortInstrumentName = #Fl. I
\set Score.skipBars = ##t
\time 3/8 \key f \major
c''4.~c4.~ c8 bes a r8 a16 bes c8 bes a g r8 g16 a bes8 a16 c f c a f e
g c
g e c a'8 g f r8 f16 g a8
g f e r8 e16 f g8 f4.~ f4.~ f16 d e f g a b32 [(a g f] e16) b e g c,8
a'4~
a4.~ a8 f a
d4.~ d16 g,, g b b d d b b d d g g4.~ g4.~ g8 f e r8 e16 f g8 f e d r8
d16
e f8 e r8 r8 d r8 r8
c r8 r8 R4.*3 r8 g'16 a g a bes a g a bes8~ bes16 a g a bes a bes d c
bes a
g a g a bes a bes c bes a bes c8~ c16 bes a bes c bes
%many more measures following
\bar||
}
%\score {\new Staff { \flautoa}}
%
%\midi {
% \context {
%\Score
%tempoWholesPerMinute = #(ly:make-moment 72 4)
%}
% }
%*Bwv1057_01_fl2.ly**
\version 2.10.33
flautob = \relative c' {
\set Staff.instrumentName = #Flauto II
%\set Staff.shortInstrumentName = #Fl. II
\set Score.skipBars = ##t
\time 3/8 \key f \major
a''16 c f c a f e g c g e c a'8 g f r8 f16 g a8 g f e r8 e16 f g8 c,4.~
c4.~ c8 bes a r8 a16 bes c8
bes a g r8 g16 a bes8 a16 c d e f g a32 [( g f e ] d16) a d f b,8 g'4~
g4.~
g16 e f g a bes! c32 [(bes a g] f16) c f a f4.~
f4.~ f4.~ f16 g, g b b d c e g e c e d b g b d f e8 d c r8 c16 d e8 d c
b
r8 b16 c d8 c r8 r8 b r8 r8
c r8 r8 R4.*3 r8 e16 f e f g f e f g8~ g16 f e f g f g bes a g f e f8
c16 d
c d ees d c d ees8~ ees16 d c d ees d
%Many more measures following
\bar||
}
%\score {
%
%
% \new Staff { \flautob}
%
%}
%
%\midi {
% \context {
%\Score
%tempoWholesPerMinute = #(ly:make-moment 72 4)
%}
% }
%*Bwv1057_01_vl1.ly**
\version 2.10.33
Violinoa = \relative c' {
\set Staff.instrumentName = #Violino I
%\set Staff.shortInstrumentName = #Vl. I
\set Score.skipBars = ##t
\time 3/8 \key f \major
f'8 r8 r8 g r8 r8 a r8 r8 R4.*3 f8 r8 r8 g r8 r8 a r8 r8 R4.*4
r16 a16 a f f d b8 r8 r8 r16 b'16 b g g e c8 r8 r8 r16 c'16 c a a f f8
r8
r8
r16 f16 f d d b b8 r8 r8 r16 d,16 d g g b c8 r8 r8 d r8 r8 e r8 r8
R4.*3 c8
r8 r8 d r8 r8
e\staccatissimo d\staccatissimo c\staccatissimo r8 c16 d e8 d c b r8
b16 c
d8 c r8 r8 R4. r8 bes g e [c16 c' c c] c8 r8 r8 R4. r8 ees c
%Many more measures following
\bar||
}
%
%\score {
%
%
% \new Staff { \Violinoa}
%
%}
%
%\midi {
% \context {
%\Score
%tempoWholesPerMinute = #(ly:make-moment 72 4)
%}
% }
%*Bwv1057_01_vl2.ly**
\version 2.10.33
Violinob = \relative c' {
\set Staff.instrumentName = #Violino II
%\set Staff.shortInstrumentName = #Vl. II
\set Score.skipBars = ##t
\time 3/8 \key f \major
c'8 r8 r8 e r8 r8 f r8 r8 R4.*3 c8 r8 r8 e r8 r8 f r8 r8 R4.*4
r16 f16 f f f f f8 r8 r8 r16 g16 g g g g g8 r8 r8 r16 a16 a a a a a8 r8
r8
r16 d,16 d d d d d8 r8 r8 r16 g,16 g g g g g8 r8 r8 b r8 r8 c r8 r8
R4.*3
g8 r8 r8 b r8 r8
g8\staccatissimo f\staccatissimo e\staccatissimo r8 e16 f g8 f e d r8
d16 e
f8 e r8 r8 R4. r8 g8 e c16 e f g a bes a8 r8 r8 R4. r8 c8 c
%Many more measures following
\bar||
}
%
%\score { \new Staff { \Violinob} }
%
%\midi {
% \context {
%\Score
%tempoWholesPerMinute = #(ly:make-moment 72 4)
%}
% }
%*Bwv1057_01_vla.ly**
\version 2.10.33
Viola = \relative c' {
\set Staff.instrumentName = #Viola
%\set Staff.shortInstrumentName = #Vla
\set Score.skipBars = ##t
\time 3/8 \key f \major \clef alto
a'8 r8 r8 g r8 r8 f r8 r8 R4.*3 a8 r8 r8 g r8 r8 f r8 r8 f, r8 r8
c'8 r8 r8 c, r8 r8 f r8 r8 r16 d'16 d d d d d8 r8 r8 r16 e16 e e e e e8
r8
r8 r16 f16 f f f f f8 r8 r8
r16 d16 d d d d g8 r8 r8 r16 d16 d d d d e8 r8 r8 d r8 r8 c r8 r8 R4.*3
e8
r8 r8 g r8 r8
g r8 r8 c,, r8 r8 g' r8 r8 g' r8 r8 c, r8 r8 R4. r8 g'8 e \set
Score.beatLength = #(ly:make-moment 3 8) c8. [ e16 f g] f8 r8 r8 R4. r8 a8
a
\set Score.beatLength = #(ly:make-moment 1 8)
%Many more measures following
\bar||
}
%
%\score { \new Staff { \Viola} }
%
%\midi {
% \context {
%\Score
%tempoWholesPerMinute = #(ly:make-moment 72 4)
%}
% }
%*Bwv1057_01_cnt.ly**
\version 2.10.33
Continuo = \relative c' {
\set Staff.instrumentName = #Continuo
%\set Staff.shortInstrumentName = #C.
\set Score.skipBars = ##t
\time 3/8 \key f \major \clef bass
Re: Beaming problem
I can't say why pasting the code from my file this forum generates errors
here:
Jayaratna wrote:
{ d'8\rest 8 8 g,8 g' f r8 8 8 }\\{d,8 f d s4. e8 g e }
a,8 a' g f a f d d' c
The error disappears as soon as I edit this post and reappears when I post
it or prewiew it. I am sorry, I also tried to attach a file but the list
rejects it.
Thank you,
Andrea
--
View this message in context:
http://www.nabble.com/Beaming-problem-tp17820561p17840581.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming problem
There are a number of problems with the beaming that have existed for a long time in LilyPond. However, you are lucky, since several of these have been fixed in the latest development version, 2.11.49. However, I'm confused that you see problems only in the score and not in the parts. Perhaps the problem is something else. If you send a small but complete example that illustrates the problem, I'm sure that you can get help from the mailing list. /Mats Jayaratna wrote: Dear subscribers, Typing this code in a 3/8 measure (version 2.10.33): e8 c16 c' c c I get a very strange strange autobeam: the second c second beam-line is not connected the following ones. The same is happening on these codes in different parts: f8 c16 d c d In this one I get the separation between the last bes and the c8 c16 bes a bes c8 I've tried some \set Score.measureLength = #(ly:make-moment 3 8) or \set Score.beatLength = #(ly:make-moment 3 8) but no results. Note that this strange thing is happening only in the score, and not in the parts. Thank you for your help, Andrea -- = Mats Bengtsson Signal Processing School of Electrical Engineering Royal Institute of Technology (KTH) SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: beaming problem
I may be superstitious, and I'd gather I'm using a far earlier version than
you, but when I start a tuplet I always explicity specify the note length even
if it's supposed to be the same as the previous note. So I'd write:
c16 [c c c] \times 2/3 {d16 [d c b c d e]}And although I don't suspect this any
more than my previous speculation, why are you using 4/6 rather than 2/3?
The other thing I do (which is a little more work) is I never use
auto-beaming...might be because of my earlier version (2.6.5) but the real
reason is that I like the visual cues in the code of how my beats fit together.
Hope this is a little help, but I gather I'm just babbling. :-)
Date: Sat, 5 Apr 2008 09:09:00 +0800From: [EMAIL PROTECTED]: [EMAIL PROTECTED]:
beaming problem
Hi,
This is the opening of my capriccio for violin and piano. I use the easy
tuplet writing method to set tuplet span to a quarter length, and my manual
beaming in the braces are correct (as I know). But the log file gave a lot of
warnings saying something I don't understand, perhaps a beaming problem. Could
anyone tell me what's the matter?
Haipeng
中 国 最 强 网 游 --- 网 易 梦 幻 西 游 ，166 万 玩 家 同 时 在 线
_
Use video conversation to talk face-to-face with Windows Live Messenger.
http://www.windowslive.com/messenger/connect_your_way.html?ocid=TXT_TAGLM_WL_Refresh_messenger_video_042008___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beaming problem
Hello list, hello Sami,
You wrote:
Try \set stemRightBeamCount and \set stemLeftBeamCount as in following
example (beam-count.ly from Lilypond tips and tricks:
http://www.lilypond.org/doc/v2.2/input/test/out-www/collated-files.html)
fragment = \notes {
#(override-auto-beam-setting '(end * * * *) 1 4)
f32 g a b b a g f
f32 g a
\set stemRightBeamCount = #1 b
\set stemLeftBeamCount = #1 b
a g f
}
This was not the solution for my case:
Instead of setting the short sixteenth beam to the left, it resulted in
disappearing the short sixteenth beam.
But Your help was helpful, indeed:
Because with Your help I was able to find in the documentation, what I
didn't know how to search for before. :-)
The solution was to add the following line:
\set Score.beatLength = #(ly:make-moment 3 16)
So I will post a little example with the correct solution for my case:
\include deutsch.ly
\score {
\context Staff \notes\relative c'' {
\key c \major \time 9/16
#(override-auto-beam-setting '(end * * * *) 3 16)
g'8 ( a,16 f'8 a,16 d8 c16 )
#(override-auto-beam-setting '(end * * * *) 6 16)
\set Score.beatLength = #(ly:make-moment 3 16)
c8 ( h!16 c8 cis16 )
#(override-auto-beam-setting '(end * * * *) 3 16)
cis g d' g g8. a h c4. r8.
}
}
Many thanks for Your help!
Best Regards Roland
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: beaming problem
Try \set stemRightBeamCount and \set stemLeftBeamCount as in following
example (beam-count.ly from Lilypond tips and tricks:
http://www.lilypond.org/doc/v2.2/input/test/out-www/collated-files.html)
fragment = \notes {
#(override-auto-beam-setting '(end * * * *) 1 4)
f32 g a b b a g f
f32 g a
\set stemRightBeamCount = #1 b
\set stemLeftBeamCount = #1 b
a g f
}
-Sami Huhtala
Roland Goretzki wrote:
Hi,
my version is 2.2.0.
In a piece with \time 9/16 I need almost notes in the form
eight sixteenth eight sixteenth eight sixteenth ...
and so on.
A little example:
a8 ( e16 g8 f16 d'8 d,16
g8 d16 f8 e16 g8 f16 )
a8 ( g16 e'8 e,16 c'8 e,16 )
I'm using the automatic beaming with
#(override-auto-beam-setting '(end * * * *) 3 16)
and this works properly:
|__||__||__|
| || || |
/ // // /
And now comes the problem:
Sometimes I need a beaming over six sixteenth, and the rest only three,
and I want it looking like:
|__||__||__|
| || || |
/ // // /
but if I use auto-beam-setting
#(override-auto-beam-setting '(end * * * *) 6 16)
or explicit [ ],
both result in looking like:
_
| |__ |__||__|
| | | || |
/ / / // /
I don't think, this is correct, and it is not plausible, and you have to
look twice to see, what it is.
Can anybody give the hint to me, how it is possible, to let show the
little sixteenth beam always to the left instead of to the right?
Thanks in advance
Best Regards Roland
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
