Re: Using partCombine with beamed melismata in cadenza mode

[Knute Snortum]

I've also found that this works most of the time:

    lilypond 2.22 "search words"

--
Knute Snortum


--
Knute Snortum



On Thu, Jun 17, 2021 at 5:15 AM Phil Holmes <mail@philholmes.net> wrote:
>
> On 17/06/2021 12:51, Brent Annable wrote:
>
> Hi Phil,
>
> I was here:
>
> https://lilypond.org/doc/v2.20/Documentation/notation/multiple-voices#automatic-part-combining
>
> I see now in the URL that the version is 2.20, but this is where Google sent 
> me when I searched for "Lilypond partcombine" (without the quotation marks). 
> Should I always check to see where I end up, or was this a cached page, or 
> will it perhaps be taken down at some point?
>
> Brent.
>
> On Thu, 17 Jun 2021, 9:29 pm Phil Holmes, <mail@philholmes.net> wrote:
>>
>> On 17/06/2021 12:19, Brent Annable wrote:
>> > Hi all,
>> >
>> > I'm trying to use \partCombine to merge two parts with beamed eighth notes 
>> > in cadenza mode (see attached). What I want is for the three eighth notes 
>> > in the lower part to merge into chords with the upper part, but Lilypond 
>> > doesn't seem to want to do it. When I take out the [ ] beaming marks, it 
>> > merges the second two notes, but the first one (tied to the previous 
>> > e-flat) still won't merge with the part above it.
>> >
>> > Is there a way to get \partCombine to do this?
>> >
>> > Regards,
>> >
>> > Brent.
>> >
>> > PS: I've noticed that the online documentation still says to use 
>> > \partcombine with a lower-case "c", but when I try that I get error 
>> > messages. It only works for me in version 2.22.1 when I use camel case 
>> > (\partCombine).
>>
>> Are you sure you're actually using the 2.22 documentation?  See:
>>
>> http://lilypond.org/doc/v2.22/Documentation/notation/multiple-voices#index-part-combiner
>>
>> where the c is clearly upper case.
>>
>> --
>> Phil Holmes
>>
> Unfortunately Google frequently fails to direct you to the latest 
> documentation, so it's better to start from the lilypond site and use the 
> documentation index.  We leave old versions of the docs for people who are 
> still using old versions of lilypond.
>
> --
> Phil Holmes