Re: Beaming error

2024-09-30 Thread Knute Snortum
On Mon, Sep 30, 2024 at 10:52 AM wrote: > Richard, > > Add a line (see the first one) > Change beat structure > > { > \set Timing.beamExceptions = #'() > \set subdivideBeams = ##t > \set baseMoment = #(ly:make-moment 1/8) > \set beatStructure = 1,1,1,1,1,1,1,1 > > \tuplet 3/2 { c'16 16

RE: Beaming error

2024-09-30 Thread carsonmark
Richard, Add a line (see the first one) Change beat structure { \set Timing.beamExceptions = #'() \set subdivideBeams = ##t \set baseMoment = #(ly:make-moment 1/8) \set beatStructure = 1,1,1,1,1,1,1,1 \tuplet 3/2 { c'16 16 16 } \repeat unfold 4 c'32 \repeat unfold 8 c'32

Re: beaming of eighth note question for 4/4

2024-07-15 Thread Mats Bengtsson
is appropriate. Paul From: Paul Scott To: Lilypond-User Mailing List Sent: 15/07/2024 7:53 Subject: Re:

Re: beaming of eighth note question for 4/4

2024-07-15 Thread Paul Hodges
where changing locally to the pattern you want is appropriate. Paul From: Paul Scott To: Lilypond-User Mailing List Sent: 15/07/2024 7:53 Subject: Re: beaming of eighth note question for 4/4 Oops! Here is the MWE: \version "2.25.18" \fixed c' {   \ti

Re: beaming of eighth note question for 4/4

2024-07-14 Thread Paul Scott
Oops! Here is the MWE: \version "2.25.18" \fixed c' {   \time 4/4   c8 8 8 8 r8 8 8 8 c8 8 8 r8 8 8 8 8 \break   c8 8 8 8 r8 8 8[ 8] c8[ 8] 8 r8 8 8 8 8 } On 7/14/24 11:50 PM, Paul Scott wrote: Much printed music that I try to duplicate seems to be beamed like the 2nd line of this MWE but the

Re: Beaming question

2022-11-29 Thread Molly Preston
Thank you! Both these examples helped! I ended up using the \beatstructure because I realized I had to do it for the whole measure. -Molly On Mon, Nov 28, 2022 at 2:09 PM James.Correa wrote: > > I think this is what you are looking for: > > \version "2.22.2" > > \score { > \absolute { > > \tup

Re: Beaming question

2022-11-28 Thread James.Correa
I think this is what you are looking for: \version "2.22.2" \score { \absolute { \tuplet 3/2 { f ''16 [ c'' \once \set stemRightBeamCount = #1 f'' } \once \set stemLeftBeamCount = #1 c'' f'' ) ] | %m67 } } --- James Correa Composer - guitarist - sound designer http://www.jamescorrea.net http:/

Re: Beaming question

2022-11-27 Thread Martín Rincón Botero
Hi Molly, you can subdivide beams. F. ex.: \score { \absolute { \set subdivideBeams = ##t \set baseMoment = #(ly:make-moment 1/8) \set beatStructure = 2,2,2,2 \tuplet 3/2 { f ''16 c''f'' } c''f''

Re: Beaming with magnifyStaff and stopStaff

2022-03-21 Thread Knute Snortum
On Sun, Mar 20, 2022 at 7:21 PM Shane Brandes wrote: > > values greater than 1 also yield odd results. ... >> I have run into another possible-bug-certainly-ugly issue that I found >> trying to create an ossia bar. ... >> Is it a bug that I should post on the bugs list? Is there a work-around? I

Re: Beaming with magnifyStaff and stopStaff

2022-03-20 Thread Shane Brandes
values greater than 1 also yield odd results. On Sun, Mar 20, 2022 at 6:41 PM Knute Snortum wrote: > Hi all, > > I have run into another possible-bug-certainly-ugly issue that I found > trying to create an ossia bar. When a musical figure has beams and the > staff is reduced in size with magnify

Re: Beaming across voices and staffs

2021-09-17 Thread Paul Hodges
I forgot to comment directly on this. I often find it necessary to create a temporary extra "dummy" voice to provide the continuity required for slurs, ties, and beams. Sometimes the extra notes get merged, but often one or other of them needs to be hidden if merging cannot be contrived. Pau

Re: Beaming across voices and staffs

2021-09-17 Thread Paul Hodges
The best/easiest solution may depend on the surrounding context. But the immediate thing that comes to mind for your limited example is: \score { \new PianoStaff << \new Staff = "up" {\clef G c''8[ \change Staff = "low" c8]} \new Staff = "low" {\clef F r8 \change Staff = "up" r8}

Re: Beaming across voices and staffs

2021-09-17 Thread Lukas-Fabian Moser
Hi Niels, Am 17.09.21 um 12:04 schrieb Niels: See the following example: \version "2.20.0" \score {   \new PianoStaff   <<     \new Staff {\clef G c''8 r}     \new Staff {\clef F r8 c}   >> } Is it possible to have a beam between the c'' and the c when they are different voices and different

RE: Beaming in nested tuplets

2021-05-30 Thread Mark Stephen Mrotek
Mark, Is this acceptable? \version "2.22" tune = \relative c'' { \clef treble b2^"A" \tuplet 3/2 { \tuplet 5/4 { b16 cis cis b \set stemRightBeamCount = #1 d } \tuplet 5/4 { \set stemLeftBeamCount = #1 f16 a, a bes \set stemRightBeamCount = #1 c } \tuplet 6/4 { \set stemLef

RE: Beaming in 4/4 and justify staves

2020-04-09 Thread Cristopher Bonn
Sorry! Believe it or not, I am new to mailing lists as well... Did I do it correctly now? Cristopher

Re: Beaming in 4/4 and justify staves

2020-04-09 Thread Noeck
Hi Christopher, >> 1) How can I have this beaming in 4/4 as default? see attached image. > http://lilypond.org/doc/v2.19/Documentation/learning/automatic-and-manual-beams \version "2.20.0" \relative { \overrideTimeSignatureSettings 4/4 % whenever you use \time 4/4 1/8 % use 8th notes

Re: Beaming in 4/4 and justify staves

2020-04-09 Thread Aaron Hill
On 2020-04-09 1:45 pm, Mark Stephen Mrotek wrote: No question is stupid – only some responses! See my post history for examples. :P -- Aaron Hill

RE: Beaming in 4/4 and justify staves

2020-04-09 Thread Mark Stephen Mrotek
Christopher, No question is stupid – only some responses! For 1) look here http://lilypond.org/doc/v2.19/Documentation/learning/automatic-and-manual-beams For 2) look here http://lilypond.org/doc/v2.19/Documentation/notation/changing-spacing Mark From: lilypond-user [mailto:lilyp

Re: beaming in tuplets

2018-04-14 Thread David Kastrup
Noeck writes: > Am 12.04.2018 um 22:48 schrieb Urs Liska: >> Additionally remove the tuplet bracket >> >>   \omit TupletBracket > > Or, if you want to keep them in case there is no beam (for quavers etc.): > > \override TupletBracket.bracket-visibility = #'if-no-beam > > Joram > > > PS: Why is i

Re: beaming in tuplets

2018-04-14 Thread Noeck
Am 12.04.2018 um 22:48 schrieb Urs Liska: > Additionally remove the tuplet bracket > >   \omit TupletBracket Or, if you want to keep them in case there is no beam (for quavers etc.): \override TupletBracket.bracket-visibility = #'if-no-beam Joram PS: Why is it "bracket-visibility" and not j

Re: beaming in tuplets

2018-04-13 Thread David Kastrup
Urs Liska writes: > Am 12.04.2018 um 20:45 schrieb Mark Stephen Mrotek: >> >> Marco, >> >> Got the 3’s on each group – see attached. >> > > Finally you can tell LilyPond to automatically group consecutive tuplets: > >   \set tupletSpannerDuration = #(ly:make-moment 1 8) > > which removes the need

Re: beaming in tuplets

2018-04-12 Thread Marco Bagolin
Thank you all :-) 2018-04-12 22:48 GMT+02:00 Urs Liska : > > > Am 12.04.2018 um 20:45 schrieb Mark Stephen Mrotek: > > Marco, > > > > Got the 3’s on each group – see attached. > > > > > Rather than manually counting beamlets you can set beam subdivisions: > > \set subdivideBeams = ##t > \se

Re: beaming in tuplets

2018-04-12 Thread Urs Liska
Am 12.04.2018 um 20:45 schrieb Mark Stephen Mrotek: Marco, Got the 3’s on each group – see attached. Rather than manually counting beamlets you can set beam subdivisions:   \set subdivideBeams = ##t   \set baseMoment = #(ly:make-moment 1 8) and remove the manual beams. Additionally remo

Re:RE;re; beaming with cadenzaOn

2017-06-03 Thread Sam Frybyte
Date: Thu, 1 Jun 2017 12:08:09 +0100 From: "Phil Holmes" To: "Sam Frybyte" , "lilypond user group" , Subject: Re: RE;re; beaming with cadenzaOn Message-ID: Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" - Origina

RE: beaming with cadenzaOn

2017-06-01 Thread Mark Stephen Mrotek
Sam, Perhaps http://lilypond.org/doc/v2.18/Documentation/notation/beams Mark -Original Message- From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Sam Frybyte Sent: Wednesday, May 31, 2017 10:16 AM To: lilypond user group Subject: beaming with c

Re: RE;re; beaming with cadenzaOn

2017-06-01 Thread Brian Barker
At 03:47 01/06/2017 -0700, Sam Frybyte wrote: Date: Wed, 31 May 2017 18:29:51 +0100 From: Brian Barker Just as you would beam any other notes: follow the a8 with a left bracket "a8[" and the ges8 with a right bracket "ges8]". It doesn't work. It does for me - and clearly also for Mr Holmes.

Re: RE;re; beaming with cadenzaOn

2017-06-01 Thread Phil Holmes
- Original Message - From: "Sam Frybyte" To: "lilypond user group" ; Sent: Thursday, June 01, 2017 11:47 AM Subject: RE;re; beaming with cadenzaOn Date: Wed, 31 May 2017 18:29:51 +0100 From: Brian Barker To: lilypond user group Cc: Sam Frybyte Subject: Re: be

RE;re; beaming with cadenzaOn

2017-06-01 Thread Sam Frybyte
Date: Wed, 31 May 2017 18:29:51 +0100 From: Brian Barker To: lilypond user group Cc: Sam Frybyte Subject: Re: beaming with cadenzaOn Message-ID: <58f7952b048a4...@rgout06.bt.lon5.cpcloud.co.uk> (added by postmas...@btinternet.com) Content-Type: text/plain; charset="us-asc

Re: beaming with cadenzaOn

2017-05-31 Thread Brian Barker
At 10:16 31/05/2017 -0700, Sam Frybyte wrote: If there is a time signature the beaming of 8th notes with acciaccaturas between them is created as I expect. in version. 2.18.2 with \cadenzaOn \stemUp\acciaccatura c'8 \stemNeutral a8 \stemUp\acciaccatura b8 \stemNeutral ges8 \times 2/3 {f1

Re: Beaming across rests

2016-11-13 Thread Manuela
Try this code snippet: A function to repeatedly print a given pattern with different notes -- View this message in context: http://lilypond.1069038.n5.nabble.com/Beaming-across-rests-tp196586p196588.html Sent from the User mailing list archive at Nabb

Re: beaming a phrase across piano staves

2016-09-25 Thread Urs Liska
\crossStaff is intended for chords with notes in two staves that are connected by one *stem*. What you want is the \change command: http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-keyboards#changing-staff-manually HTH Urs Am 26.09.2016 um 00:11 schrieb Ryan Michael: >

Re: Beaming, partcombine and pickups

2016-09-16 Thread Rutger Hofman
On 09/16/2016 06:24 AM, David Wright wrote: On Thu 15 Sep 2016 at 17:15:02 (-0600), David F. wrote: I have a song in 9/8 time with a pickup of three eighth notes. I expect Lilypond to beam those three eighth notes together, but it does not when I combine two voices with partcombine. Am I doi

Re: Beaming, partcombine and pickups

2016-09-15 Thread David Wright
On Thu 15 Sep 2016 at 17:15:02 (-0600), David F. wrote: > I have a song in 9/8 time with a pickup of three eighth notes. I expect > Lilypond to beam those three eighth notes together, but it does not when I > combine two voices with partcombine. > > Am I doing something wrong? Is Lilypond doin

Re: Beaming over a rest before a subdivision

2016-01-13 Thread Urs Liska
Am 13.01.2016 um 10:08 schrieb Mark Knoop: > At 22:57 on 12 Jan 2016, Urs Liska wrote: >> Am 12.01.2016 um 20:59 schrieb Werner LEMBERG: What should the behavior of the *last* one be here? >>> No beams over the rest. >> Well, default behaviour is to break the beam at all rests here (see

Re: Beaming over a rest before a subdivision

2016-01-13 Thread Mark Knoop
At 22:57 on 12 Jan 2016, Urs Liska wrote: >Am 12.01.2016 um 20:59 schrieb Werner LEMBERG: >>> What should the behavior of the *last* one be here? >> No beams over the rest. > >Well, default behaviour is to break the beam at all rests here (see >attached). Not sure if this is relevant to your c

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Werner LEMBERG
>> No beams over the rest. > > But if the user manually enters the beam enclosing the rest there > should be *something*. Ah, ok, I missed this. > And I think a single beam is better here than a number of steamlets. I agree. Werner ___ lilypond

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Kieren MacMillan
Hi Urs, > Well, default behaviour is to break the beam at all rests here (see attached). ew > But if the user manually enters the beam enclosing the rest there should > be *something*. +1 > What would be nice too […] is adding a stemlet, > but without implicitly adding beamlets. Yes. n.b. Yo

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Urs Liska
Am 12.01.2016 um 20:59 schrieb Werner LEMBERG: >> What should the behavior of the *last* one be here? > No beams over the rest. Well, default behaviour is to break the beam at all rests here (see attached). But if the user manually enters the beam enclosing the rest there should be *something*.

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Urs Liska
Am 12.01.2016 um 19:57 schrieb Kieren MacMillan: > Hi Urs, > >> Ah well, producing stemlets is the responsibility of user input code. > Indeed. =) > I have some syntactic sugar for just such efforts. > >> Find attached a solution *with* stemlets (\override >> Staff.Stem.stemlet-length = 1) > Fr

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Werner LEMBERG
> What should the behavior of the *last* one be here? No beams over the rest. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Kieren MacMillan
Hi Urs, > Ah well, producing stemlets is the responsibility of user input code. Indeed. =) I have some syntactic sugar for just such efforts. > Find attached a solution *with* stemlets (\override Staff.Stem.stemlet-length > = 1) From the standpoint of clarity [of beat division/subdivision], t

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Urs Liska
Am 12.01.2016 um 18:16 schrieb Urs Liska: >>> What should the behavior of the *last* one be here? >> > Stemlet, for sure. (IMO) > Unfortunately producing stemlets is a completely different business > which I haven't discovered yet (don't even know where this might take > place). > > Urs > Ah wel

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Urs Liska
Am 12.01.2016 um 18:11 schrieb Kieren MacMillan: > Hi Urs, > >> I must say I find the attached image (with 1/16 subdivision and rests >> before each division) pretty clear. > “Pretty clear”? Yes. > > Could it be clearer? Definitely. > I can’t tell if, for example, the 64ths should be phrased 3+5

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Kieren MacMillan
Hi Urs, > I must say I find the attached image (with 1/16 subdivision and rests > before each division) pretty clear. “Pretty clear”? Yes. Could it be clearer? Definitely. I can’t tell if, for example, the 64ths should be phrased 3+5 or 4+4; beamlets and/or stemlets would definitely help make t

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Urs Liska
Am 12.01.2016 um 17:49 schrieb Urs Liska: > > Am 12.01.2016 um 17:28 schrieb Mark Knoop: >> At 17:15 on 12 Jan 2016, Werner LEMBERG wrote: b) have *no* beamlets at all and let the subdivision be calculated as usual (fourth attachment) >>> This is what I prefer. >>> >> +1. Gould see

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Urs Liska
Am 12.01.2016 um 17:28 schrieb Mark Knoop: > At 17:15 on 12 Jan 2016, Werner LEMBERG wrote: >>> b) have *no* beamlets at all and let the subdivision be calculated >>>as usual (fourth attachment) >> This is what I prefer. >> > +1. Gould seems to always use stemlets with beamlets when the bea

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Mark Knoop
At 17:15 on 12 Jan 2016, Werner LEMBERG wrote: >> b) have *no* beamlets at all and let the subdivision be calculated >>as usual (fourth attachment) > >This is what I prefer. > +1. Gould seems to always use stemlets with beamlets when the beam count > 2. -- Mark Knoop _

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Werner LEMBERG
> b) have *no* beamlets at all and let the subdivision be calculated >as usual (fourth attachment) This is what I prefer. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Urs Liska
Am 12.01.2016 um 16:47 schrieb Urs Liska: > Hi Kieren, > > thanks for info and opinion. (I really have to get hold of Gould's book > finally ...). > > If I'd implement that > > \relative c'' { > a32 [ a a r a16 a ] > \set subdivideBeams = ##t > \set baseMoment = #(ly:make-moment 1/8) > a

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Urs Liska
Am 12.01.2016 um 16:37 schrieb Kieren MacMillan: > Hi Urs, > >> I see two approaches to this: >> >> a) have the number of beams correspond to the actual duration of the >> note (third attachment) >> b) have *no* beamlets at all and let the subdivision be calculated as >> usual (fourth attachment)

Re: Beaming over a rest before a subdivision

2016-01-12 Thread Kieren MacMillan
Hi Urs, > I see two approaches to this: > > a) have the number of beams correspond to the actual duration of the > note (third attachment) > b) have *no* beamlets at all and let the subdivision be calculated as > usual (fourth attachment) > > Any opinions (or references to what the books say)?

Re: Beaming small problem

2015-10-22 Thread Jacques Menu
Hello Pierre and Joram, Thanks for the solution, and a nice day! JM > Le 21 oct. 2015 à 17:58, Noeck a écrit : > > Hi Jacques, > > you need two voices: > > \version "2.19.28" > > PartPOneVoiceOne = \relative fis { > \clef "bass" > \key d \major > \time 4/4 > \voiceOne > fis8[ fis fis f

Re: Beaming small problem

2015-10-21 Thread Noeck
Hi Jacques, you need two voices: \version "2.19.28" PartPOneVoiceOne = \relative fis { \clef "bass" \key d \major \time 4/4 \voiceOne fis8[ fis fis fis] \oneVoice fis8[ eis16 dis cis8 b] | % 2 } PartPOneVoiceTwo = \relative fis, { \voiceTwo fis8 fis' fis fis } \new Staff<<

Re: Beaming small problem

2015-10-21 Thread Pierre Perol-Schneider
Hi Jacques, How about: \version "2.19.28" PartPOneVoiceOne = \relative fis, { \clef "bass" \key d \major \time 4/4 << { \voiceOne fis'8 [ 8 8 8 ] } \\ { fis,8 [ fis'8 8 8 ] } >> fis8 [ eis16 dis16 cis8 b8 ] | % 2 } { \PartPOneVoiceOne } See also: http:

Re: beaming question

2015-06-19 Thread Marc Hohl
Am 20.06.2015 um 04:04 schrieb William Zeitler: I want to do like the attached gif: notice the broken 16th note beams. Please do not introduce a new topic by answering to an existing thread, this causes confusion. (More in the score dictates that this needs to be 6/8. Meanwhile the general qu

Re: beaming rule which beams across barlines?

2015-06-11 Thread tisimst
Kieren, It looks like this issue is hard-coded, forcing a beam to terminate at the end of a measure (see scm/auto-beam.scm, in the function "default-auto-beam-check", in the conditional statements starting at around line 100). My Scheme-fu is not enough for to adjust this function appropriately. M

Re: beaming problem

2015-05-29 Thread Haipeng Hu
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

2015-05-29 Thread bobr...@centrum.is
; > To: bobr...@centrum.is > Cc: "lilypond-user" > Sent: Friday, May 29, 2015 10:43:26 AM > Subject: Re: beaming problem > > On 5/29/15, bobr...@centrum.is wrote: > > Haipeng, > > > > There was no attachment. > > > > -David > > >

Re: beaming problem

2015-05-29 Thread Michael Gerdau
> >> 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

Re: beaming problem

2015-05-29 Thread Simon Albrecht
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

Re: beaming problem

2015-05-29 Thread bobr...@centrum.is
Haipeng, There was no attachment. -David - Original Message - > From: "Haipeng Hu" > To: "lilypond-user" > 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

Re: Beaming problem

2014-12-28 Thread Wim van Dommelen
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 wrote: > > Hello, >

Re: Beaming problem

2014-12-28 Thread Jacques Menu
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 a écrit : > > Wim, > > On Sun, Dec 28, 2014 at 11:47 AM, Shane Brandes > wrote: > Wim, > > you are missing the ope

Re: Beaming problem

2014-12-28 Thread David Nalesnik
Wim, On Sun, Dec 28, 2014 at 11:47 AM, Shane Brandes 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 wrote: > >> Hi, >> >> I stumbled on a small beaming problem. Attached two small .

Re: Beaming problem

2014-12-28 Thread Shane Brandes
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 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 experi

Re: Beaming and grace notes

2014-12-01 Thread Keith OHara
On Mon, 01 Dec 2014 12:28:54 -0800, Knute Snortum wrote: * Is there a way to keep this structure and get rid of the warning? The warning is about being unable to fit the beam between the notes, because you forced the stem directions in such a way to force the beam between the staves LilyPon

Re: Beaming and grace notes

2014-12-01 Thread Knute Snortum
I'm still working on the measure. Keith's solution works well, but when I fit it into my structure I get a beam-slope warning. Below is a "minimal" example, which is quite large, that prints just the one measure. The warning is written into the code. * Is there a way to keep this structure and

Re: Beaming and grace notes

2014-11-30 Thread Keith OHara
On Sat, 29 Nov 2014 07:44:39 -0800, Knute Snortum wrote: I've attached a picture of the measure. [Debussy Prelude #2, "Voiles"] This piece uses a whole-tone scale (not in the part with the cross-staff grace notes of Knute's example, but most of the rest of the piece) so I would be tempted

Re: Beaming and grace notes

2014-11-30 Thread Shane Brandes
a short snippet for educational use constitutes fair use. S. On Sun, Nov 30, 2014 at 10:01 AM, Knute Snortum wrote: > You are correct; the original is missing a treble clef. I am using an early > edition that has passed into public domain to transcribe, but so far I've > found three errors in t

Re: Beaming and grace notes

2014-11-30 Thread Knute Snortum
You are correct; the original is missing a treble clef. I am using an early edition that has passed into public domain to transcribe, but so far I've found three errors in the score. I'm using a later edition to double check from but I'm still transcribing from the earlier one so my transcription

Re: Beaming and grace notes

2014-11-30 Thread Rutger Hofman
On 11/29/2014 07:49 PM, Knute Snortum wrote: Ah, I see. Use two voices so one is the eighth note and the other is the grace notes with their duration divided over the eighth. This also gets me the slur. Thank you. Knute Snortum (via Gmail) On Sat, Nov 29, 2014 at 10:31 AM, Keith OHara mailt

Re: Beaming and grace notes

2014-11-30 Thread Rutger Hofman
Is the original correct? I would guess that a treble clef has been forgotten in the upper staff, at the moment the staff is crossed in the "grace note" run. How else can the run, and especially the cross-staff chords in the last four 1/32 notes make sense? Rutger On 11/29/2014 07:49 PM, Knute

Re: Beaming and grace notes

2014-11-29 Thread Knute Snortum
Ah, I see. Use two voices so one is the eighth note and the other is the grace notes with their duration divided over the eighth. This also gets me the slur. Thank you. Knute Snortum (via Gmail) On Sat, Nov 29, 2014 at 10:31 AM, Keith OHara wrote: > On Sat, 29 Nov 2014 07:44:39 -0800, Knute

Re: Beaming and grace notes

2014-11-29 Thread Urs Liska
Am 29. November 2014 19:31:22 MEZ, schrieb Keith OHara : >On Sat, 29 Nov 2014 07:44:39 -0800, Knute Snortum >wrote: > >> Thank you both for your relies. Keith, your second suggestion is >what I >> need, if I could designate a zero length note. >> >> Requirements: >> >> * An actual eighth note >

Re: Beaming and grace notes

2014-11-29 Thread Keith OHara
On Sat, 29 Nov 2014 07:44:39 -0800, Knute Snortum wrote: Thank you both for your relies. Keith, your second suggestion is what I need, if I could designate a zero length note. Requirements: * An actual eighth note * Grace notes need to "attached" with a beam to the eighth note * Grace notes

Re: Beaming and grace notes

2014-11-29 Thread Knute Snortum
Thank you both for your relies. Keith, your second suggestion is what I need, if I could designate a zero length note. Requirements: * An actual eighth note * Grace notes need to "attached" with a beam to the eighth note * Grace notes add no duration to the measure I've attached a picture of th

Re: Beaming and grace notes

2014-11-27 Thread Thomas Morley
2014-11-27 23:08 GMT+01:00 Keith OHara : > Knute Snortum gmail.com> writes: > >> I want to start a run of grace notes with a note with a normal head. > >> ...but with the c' beamed to the d'. > > If these notes all happen before the beat, then > \relative c' { >\grace { <\tweak #'font-size #0

Re: Beaming and grace notes

2014-11-27 Thread Keith OHara
Knute Snortum gmail.com> writes: > I want to start a run of grace notes with a note with a normal head.  > ...but with the c' beamed to the d'. If these notes all happen before the beat, then \relative c' { \grace { <\tweak #'font-size #0 c>32 d e f g a b } c8 } This looks like it might

Re: Beaming on the quarter note

2014-11-17 Thread Guy Stalnaker
Peter, This was an excellent suggestion. I now have a BeamingOverrides variable in my standard header which I insert in the \score << [here] >> of my LY file. Works like magic. As I almost always write choral music where delineating visually beats is an aid in singing (one's average Chancel

Re: Beaming on the quarter note

2014-11-16 Thread peter
> "Guy" == Guy Stalnaker writes: Guy> Phil, That was what I found :-) But unless I'm mistaken, one must Guy> use those directives for *every* time signature change. Thus if I You can do it once for each time signature you're going to use. \version "2.18.2" \score { << % Beam 4/4 at cro

Re: Beaming on the quarter note

2014-11-16 Thread jimmyg521
m: pe...@chubb.wattle.id.au To: Guy Stalnaker Cc: Phil Burfitt , lilypond-user Mailinglist Sent: Sun, 16 Nov 2014 8:23 PM Subject: Re: Beaming on the quarter note >>>>> "Guy" == Guy Stalnaker writes: Guy> Phil, That was what I found :-) But unless I'm mistaken,

Re: Beaming on the quarter note

2014-11-16 Thread Guy Stalnaker
Phil, That was what I found :-) But unless I'm mistaken, one must use those directives for *every* time signature change. Thus if I have shifting ?/4 meters, every time the meter changes I have to add the directives because each ?/4 meter requires a different beat grouping. I know I can create a V

Re: Beaming on the quarter note

2014-11-16 Thread Phil Burfitt
- Original Message - From: "Guy Stalnaker" To: "lilypond-user Mailinglist" Sent: Sunday, November 16, 2014 10:39 PM Subject: Beaming on the quarter note All, I've done the search and found much of relevance, but nothing that gives me what I want. I'd like beaming restricted to quar

Re: Beaming until barline

2014-11-01 Thread Gilberto Agostinho
David Nalesnik-2 wrote > By the way, part of this can be made a little prettier: Thanks David, I also appreciate slim and pretty codes :) Take care, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/Beaming-until-barline-tp167937p168235.html Sent from the User ma

Re: Beaming until barline

2014-11-01 Thread David Nalesnik
On Fri, Oct 31, 2014 at 6:32 PM, Gilberto Agostinho < gilbertohasn...@gmail.com> wrote: > David Nalesnik-2 wrote > > The attached file is what I come up with. > > Absolutely fantastic, David! Thanks really a lot, this function is > looking really great! > Glad I can help! By the way, part of thi

Re: Beaming until barline

2014-11-01 Thread Pierre Perol-Schneider
Hi David, 2014-10-31 20:39 GMT+01:00 David Nalesnik : > You could scale the stencil. That way you wouldn't need to reconstruct > the beam from what you find in 'beaming. > But of course! Thanks much David! Cheers, Pierre ___ lilypond-user mailing li

Re: Beaming until barline

2014-10-31 Thread Gilberto Agostinho
David Nalesnik-2 wrote > The attached file is what I come up with. Absolutely fantastic, David! Thanks really a lot, this function is looking really great! Take care, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/Beaming-until-barline-tp167937p168182.html Se

Re: Beaming until barline

2014-10-31 Thread David Nalesnik
Hi, On Fri, Oct 31, 2014 at 2:39 PM, David Nalesnik wrote: > > You could scale the stencil. > This will break down if you have sub-beams because the entire beam is stretched. Thankfully, the coordinates of the various beam segments are cached, and resetting these does get a response from ly:be

Re: Beaming until barline

2014-10-31 Thread David Nalesnik
On Fri, Oct 31, 2014 at 2:39 PM, David Nalesnik wrote: > Of course this will only produce good results with flat beams! > > No, that should be OK. I was just thinking that the horizontal scaling might cause the beam to pull away from the stems, but in the examples I've tried, the distortion is

Re: Beaming until barline

2014-10-31 Thread David Nalesnik
Hi, On Fri, Oct 31, 2014 at 11:44 AM, Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com> wrote: > > > but, as you can see, it's limited to one beam... :( > Any help from schemers ? > You could scale the stencil. That way you wouldn't need to reconstruct the beam from what you find in 'b

Re: Beaming until barline

2014-10-31 Thread Gilberto Agostinho
Hi Pierre, On 31/10/14 17:44, Pierre Perol-Schneider wrote: but, as you can see, it's limited to one beam... :( This new function great! For my particular composition the limitation won't be a problem as I only use a single beam, but if anyone could make this function more flexible, then it

Re: Beaming until barline

2014-10-31 Thread Pierre Perol-Schneider
Hi Gilberto, Well, I've found this : \version "2.19.15" beamLength = #(define-music-function (parser location myLength) (number?) (define (myBeamLength grob) (let* ((beam (ly:beam::print grob)) (beam-extent-x (ly:stencil-extent beam X)) (beam-length-x (interval-leng

Re: Beaming until barline

2014-10-31 Thread Pierre Perol-Schneider
Hi Gilberto, 2014-10-26 20:35 GMT+01:00 Gilberto Agostinho : > If anyone still has any other ideas/suggestions, they are highly > appreciated. > Just a rough idea : \version "2.19.15" beamLength = #(define-music-function (parser location myLength myPosition) (number? number?) #{ \once\o

Re: Beaming until barline

2014-10-31 Thread Gilberto Agostinho
Hi Pierre, On 31/10/14 08:50, Pierre Perol-Schneider wrote: Actually no. I did reply "to all". Strange that you've got it as a private message. That's indeed strange, have a look on this thread at nabble: http://lilypond.1069038.n5.nabble.com/Beaming-until-barline-td167937.html#a167952 If you

Re: Beaming until barline

2014-10-31 Thread Pierre Perol-Schneider
Hi Gilberto, 2014-10-31 3:37 GMT+01:00 Gilberto Agostinho >: > Hi Pierre, > > Thank you so much for your answer. Oddly enough, it did not appear as a > reply in our forum at Nabble, did you mean to send it privately to me? > Actually no. I did reply "to all". Strange that you've got it as a pri

Re: Beaming until barline

2014-10-31 Thread Gilberto Agostinho
Currently I am using this function written by Pierre Perol-Schneider: \version "2.19.15" beamLength = #(define-music-function (parser location myLength myPosition) (number? number?) #{ \once\override Beam.stencil = #(lambda (grob) (grob-interpret-markup grob #{ \mark

Re: Beaming until barline

2014-10-26 Thread Gilberto Agostinho
Hi Pierre, Schneidy wrote > 'didn't make any trial yet but maybe this code could bring you some > inspiration : > http://lists.gnu.org/archive/html/lilypond-user/2013-05/msg00549.html Thank you very much for the link, but I couldn't make it work. Apparently, that function only deals with beams t

Re: Beaming until barline

2014-10-26 Thread Pierre Perol-Schneider
Hi Gilberto, 2014-10-26 16:01 GMT+01:00 Gilberto Agostinho : > So does anyone have any suggestions on how to extend the beam exactly until > the barline? > 'didn't make any trial yet but maybe this code could bring you some inspiration : http://lists.gnu.org/archive/html/lilypond-user/2013-05/

Re: Beaming question

2013-07-10 Thread Urs Liska
Am 10.07.2013 13:55, schrieb Urs Liska: Am 10.07.2013 13:52, schrieb Nick Payne: This works: \version "2.17.21" { \set subdivideBeams = ##t \set baseMoment = #(ly:make-moment 1 16) a'16[ r r a'] \stopStaff s2 \startStaff a'32[ r r a'] } Thank you. Of course I thought about sub

Re: Beaming question

2013-07-10 Thread Urs Liska
Am 10.07.2013 13:52, schrieb Nick Payne: On 10/07/13 19:03, Urs Liska wrote: Hi, I need to achieve a beaming as in the attached png, i.e. beams over rests with only one beam throughout the time. a) Is it really true that I have to do that manually in the way I did it in the attached file? Th

  1   2   3   >