lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cross-staff stems


From: William Rehwinkel
Subject: Re: cross-staff stems
Date: Wed, 22 Mar 2023 20:30:15 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.9.0

Dear Mark,

I found that the error was applying "\crossStaff" to the lower notes instead of the higher ones, applying them to the upper notes (whos stems will extend further below the stem) seems to have fixed the issue.

Thanks,
-William

On 3/22/23 20:24, Mark Stephen Mrotek wrote:
Jean,

Attached is a MWE

Want stem to connect c and a, also c an g.

Thank you for your kind attention.

Mark

*From:*Jean Abou Samra [mailto:jean@abou-samra.fr]
*Sent:* Wednesday, March 22, 2023 4:41 PM
*To:* Mark Stephen Mrotek <carsonmark@ca.rr.com>; 'lilypond-user' <lilypond-user@gnu.org>
*Subject:* Re: cross-staff stems

Le mercredi 22 mars 2023 à 14:28 -0700, Mark Stephen Mrotek a écrit :

    Hello!

    My piano score has four voices each coded as a variable.
    At a single place I want a cross stem between the tenor and alto voice.
    The directions at
    
https://lilypond.org/doc/v2.16/Documentation/notation/common-notation-for-keyboards#cross_002dstaff-stems
 
<https://lilypond.org/doc/v2.16/Documentation/notation/common-notation-for-keyboards#cross_002dstaff-stems>
    were followed  yet the stems were not created.

    The snippet for the above directions does not use variables yet
    imbeds the notation within the \PianoStaff.
    Does imply that cross-staff stem is available only in that format?

    Thank you for your kind attention,

First, the documentation page you link to is for LilyPond 2.16, which is an ooold version (more than 10 years old). Google search results can be problematic in that regard; it often works to replace the version number with your version number in the URL, in this case replacing 2.16 with 2.24, the current stable version. That said, this snippet does still work in 2.24 unchanged.

Do you have an example allowing to reproduce your problem? (No, whether you structure your input with variables won't make a difference.)


--
+ ---------------------------------------------- +
|    William Rehwinkel - Oberlin College and     |
|                           Conservatory '24     |
|          william@williamrehwinkel.net          |
| PGP key:                                       |
| https://williamrehwinkel.net/static/pubkey.txt |
+ ---------------------------------------------- +

Attachment: cross2.ly
Description: Text document

Attachment: OpenPGP_0x55FE8F99DD713D20.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]