Re: \beamExeceptions problem
Richard Shann writes: > On Mon, 2021-01-04 at 00:45 +0100, David Kastrup wrote: >> Richard Shann writes: >> >> > My understanding of the \beamExceptions function in 2.20 was that >> > you >> > should be able to pass it a complete bar beamed as you would wish >> > and >> > expect other bars with the same beat structure to be beamed to >> > match. >> >> But you did not pass \beamExceptions a bar beamed as you would wish. >> You passed it a bar with beaming depending on a combination of >> automatic >> beaming and beaming exceptions. > > ah, I see, thanks. [...] > I think I'll need to write a script to place manual beams throughout a > movement to match a sample bar, as thinking about it, it would be too > much to expect LilyPond to do this sort of thing. Beaming exceptions and rules go a long way actually, but it's optimistic that throwing some real music instead of manually designed patterns at \beamExceptions is going to do a comprehensive job. Even then, every beam in that real music needs to be explicitly manually beamed. -- David Kastrup
Re: \beamExeceptions problem
On Sun, 2021-01-03 at 22:34 +0100, Xavier Scheuer wrote: > On Sun, 3 Jan 2021 at 18:04, Richard Shann > wrote: > > > > My understanding of the \beamExceptions function in 2.20 was that > you > > should be able to pass it a complete bar beamed as you would wish > and > > expect other bars with the same beat structure to be beamed to > match. > > In this example barOne and barTwo have the same rhythm but only > barOne > > is beamed as desired. > > What have I got wrong? > > Hello Richard, > > I learned this \beamExceptions function thanks to you, thank you. :) > If you replace \beamExceptions \barOne by > \beamExceptions { 16[ 16] 16[ 32 32] 16[ 16] 16[ 32 32] } > you get the desired output. > > Not sure what's going on, but when putting only rhythm in the pattern > (like the example in the documentation) it seems to work. what's going on is that you added the beam end ] which I had failed to put there because, as David pointed out, the autobeaming did it for me. The inclusion of the note names is ok (and very useful if you are creating your template by copying a bar of music from your score). Richard Shann
Re: \beamExeceptions problem
On Mon, 2021-01-04 at 00:45 +0100, David Kastrup wrote: > Richard Shann writes: > > > My understanding of the \beamExceptions function in 2.20 was that > > you > > should be able to pass it a complete bar beamed as you would wish > > and > > expect other bars with the same beat structure to be beamed to > > match. > > But you did not pass \beamExceptions a bar beamed as you would wish. > You passed it a bar with beaming depending on a combination of > automatic > beaming and beaming exceptions. ah, I see, thanks. > > That doesn't work since at the current point of time, beaming > exceptions > _only_ affect beam ends. > > > In this example barOne and barTwo have the same rhythm but only > > barOne > > is beamed as desired. > > What have I got wrong? > > > > Richard Shann > > 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< > > \version "2.20" > > > > barOne = {g'16 b' b'[( a'32 g']) d'16[ c''16] c''16[( b'32 a'])} > > Beaming for 1/16 notes ends here after c''16] and nowhere > else. Beaming > for 32nd notes ends after g'32]) and a'32]) and nowhere else. Those > are > the beaming exceptions being generated by > > \beamExceptions \barOne > > as you can verify with > > \void \displayScheme \beamExceptions \barOne > I think I'll need to write a script to place manual beams throughout a movement to match a sample bar, as thinking about it, it would be too much to expect LilyPond to do this sort of thing. Richard Shann
Re: \beamExeceptions problem
Richard Shann writes: > My understanding of the \beamExceptions function in 2.20 was that you > should be able to pass it a complete bar beamed as you would wish and > expect other bars with the same beat structure to be beamed to match. But you did not pass \beamExceptions a bar beamed as you would wish. You passed it a bar with beaming depending on a combination of automatic beaming and beaming exceptions. That doesn't work since at the current point of time, beaming exceptions _only_ affect beam ends. > In this example barOne and barTwo have the same rhythm but only barOne > is beamed as desired. > What have I got wrong? > > Richard Shann > 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8>< > \version "2.20" > > barOne = {g'16 b' b'[( a'32 g']) d'16[ c''16] c''16[( b'32 a'])} Beaming for 1/16 notes ends here after c''16] and nowhere else. Beaming for 32nd notes ends after g'32]) and a'32]) and nowhere else. Those are the beaming exceptions being generated by \beamExceptions \barOne as you can verify with \void \displayScheme \beamExceptions \barOne -- David Kastrup
Re: \beamExeceptions problem
On Sun, 3 Jan 2021 at 18:04, Richard Shann wrote: > > My understanding of the \beamExceptions function in 2.20 was that you > should be able to pass it a complete bar beamed as you would wish and > expect other bars with the same beat structure to be beamed to match. > In this example barOne and barTwo have the same rhythm but only barOne > is beamed as desired. > What have I got wrong? Hello Richard, I learned this \beamExceptions function thanks to you, thank you. If you replace \beamExceptions \barOne by \beamExceptions { 16[ 16] 16[ 32 32] 16[ 16] 16[ 32 32] } you get the desired output. Not sure what's going on, but when putting only rhythm in the pattern (like the example in the documentation) it seems to work. Cheers, Xavier -- Xavier Scheuer