Re: How to lengthen stems in beamed groups

2024-06-29 Thread Flaming Hakama by Elaine
> -- Forwarded message --
> From: Knute Snortum 
> To: lilypond-user@gnu.org
> Cc:
> Bcc:
> Date: Wed, 26 Jun 2024 09:46:29 -0700
> Subject: How to lengthen stems in beamed groups
> Hi list,
>
> I'm hoping someone can give me insight into how to lengthen stems in
> beamed groups globally.
>
> LilyPond usually makes good assumptions and has great defaults, but in
> this situation it fails to create good stem lengths in beamed groups.  I've
> attached some sample code that illustrates the problem.  With the following
> line commented out, you can see that the stems are too short
> (stem-too-short.png):
>
> \override Stem.details.beamed-lengths = #'(3.5 4.1)
>
> With the above line uncommented, the stem lengths are better, except the
> second measure, right hand, third beat (stem-lengths-better.png).
>
> My questions are these: How do I tell LilyPond what length the shortest
> stem in a beamed group should be? (I tried playing
> with Stem.details.beamed-minimum-free-lengths, but its behavior seemed
> chaotic.)  And is there a better way to control stem lengths in beamed
> groups?
>
> --
> Knute Snortum
>


This may be too broad of a brush, since it also affects non-beamed stems.

  \override Stem.length-fraction = #(magstep 1.2)

But this is what I use, and I don't mind the extra-long non-breamed stems.


\version "2.24.0"
\language "english"

global = {
  \time 12/8
  \key f \major
}

rightHand = \relative {
  \global
  d''4.~\startTrillSpan d16\stopTrillSpan c bf a g f  bf8 g' e!  c bf g' |
  \noBreak
  a,16 g f e f a  d, f d bf g e'  f bf, a g a c  f,4 r8 |
}

leftHand = \relative {
  \global
  \clef bass
  f16 d bf a bf d  f, bf d f e! d  e c bf a bf c  g bf e g f e |
  f8 a, d  bf8.\trill a32 bf c8  f,4 r8  r16 c' a c f,8 |
}

\score {
  \new PianoStaff <<
\new Staff {
  \override Stem.length-fraction = #(magstep 1.2)
  \rightHand
}
\new Staff {
  \override Stem.length-fraction = #(magstep 1.2)
  \leftHand
}
  >>
  \layout {
indent = 0
\context {
  \Score
  % defaults = #'(3.26 3.5 3.6)
  \override Stem.details.beamed-lengths = #'(3.5 4.1)
  % defaults = #'(1.83 1.5 1.25)
  %\override Stem.details.beamed-minimum-free-lengths = #'(1.83 3.33)
  % defaults = #'(1.0 0.5 0.25)
  %\override Stem.details.stem-shorten = #'(1.0 0.5 0.25)
}
  }
}


HTH,


Elaine Alt
415 . 341 .4954   "*Confusion is
highly underrated*"
ela...@flaminghakama.com
Producer ~ Composer ~ Instrumentalist ~ Educator
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


Re: Output lilypond file with variables/functions applied?

2024-06-29 Thread Dmitri Volkov
displayLilyMusic seems to be exactly what I was looking for, thank you 
very much!


On 2024-06-29 5:07 p. m., Timothy Lanfear wrote:

On 29/06/2024 21:16, Dmitri Volkov wrote:
Is there a way to get Lilypond to output a file with variables and 
functions applied?


The displayLilyMusic function covers at least the case of 
transposition, and possibly other things as well.


See 
https://lilypond.org/doc/v2.24/Documentation/notation/displaying-lilypond-notation



--
Timothy Lanfear, Bristol, UK.





Re: Output lilypond file with variables/functions applied?

2024-06-29 Thread Dmitri Volkov
Thank you for the response! New to Lilypond and was not aware of tags, 
I'll have to play around with them.




Re: Output lilypond file with variables/functions applied?

2024-06-29 Thread Timothy Lanfear

On 29/06/2024 21:16, Dmitri Volkov wrote:
Is there a way to get Lilypond to output a file with variables and 
functions applied?


The displayLilyMusic function covers at least the case of transposition, 
and possibly other things as well.


See 
https://lilypond.org/doc/v2.24/Documentation/notation/displaying-lilypond-notation



--
Timothy Lanfear, Bristol, UK.


Re: Output lilypond file with variables/functions applied?

2024-06-29 Thread Simon Albrecht

Hi Dimitri,

On 29.06.24 22:16, Dmitri Volkov wrote:

Hello,

Is there a way to get Lilypond to output a file with variables and 
functions applied?


No, there isn’t. Depending on your setup, the best tool for this purpose 
may be within the editor (Frescobaldi or other?), possibly using the 
python-ly library if you want to work on the command line (though I 
haven’t used that directly myself), or you’ll want to use a different 
approach:


My use case is that I want to manually change the accidentals of some 
specific pitches that were re-pitched using transpose for better 
readability.


That sounds like you might want to use tags for those specific notes. I 
call those tags cisharm and transharm: one alternative is this side of 
an enharmonic transformation, the other is on the other side of the 
transformation.


%%
\version "2.24.3"
\tagGroup cisharm,transharm

music = {
  \tag cisharm { cis'1 }
  \tag transharm { des'1 }
}

\keepWithTag cisharm \music
\transpose c cis \keepWithTag cisharm \music
\transpose c cis \keepWithTag transharm \music
%%

Hope that helps!



Output lilypond file with variables/functions applied?

2024-06-29 Thread Dmitri Volkov

Hello,

Is there a way to get Lilypond to output a file with variables and 
functions applied? For example, if I have a file like:


-
\version "2.24.3"

stuff = { c4 c4 c4 c4 | }

\stuff
\stuff
\transpose c4 d4 { \stuff }
\stuff
-

then is there a way to get Lilypond to output something like the following?

-
\version "2.24.3"

stuff = { c4 c4 c4 c4 | }

c4 c4 c4 c4 |
c4 c4 c4 c4 |
d4 d4 d4 d4 |
c4 c4 c4 c4 |
-

My use case is that I want to manually change the accidentals of some 
specific pitches that were re-pitched using transpose for better 
readability.


Thank you!
~Dmitri



Re: Windows users - Call for testing

2024-06-29 Thread Michael Käppler




Am 29.06.2024 um 01:10 schrieb Paul Hodges:

I've compiled seven choral scores of varying complexity with no problems.

My most complex instrumental scores will have to wait until I have
time to update them manually - convert-ly can't cope with them.

Paul

Thanks for testing!




Re: Windows users - Call for testing

2024-06-29 Thread Michael Käppler




Am 29.06.2024 um 00:31 schrieb Jean Abou Samra:

Le vendredi 28 juin 2024 à 22:22 +, bobr...@centrum.is a écrit :

Michael,

I'm sorry, but I don't really understand what your code does, nor do
I know what to do with it in a real score.  If you want to throw a
score at me using it I'll be happy to run LilyPond 2.25.17 (Guile
3.0) and let you know the results.


I think he was just asking you to try any real score that you have.
Not somehow inserting the test code into it.

Yes, exactly. It would be great if you could run the patched release on some
real scores you have available.





Re: Windows users - Call for testing

2024-06-29 Thread Mats Bengtsson


  
  


On 2024-06-27 12:28, Michael Käppler
  wrote:

Hi all,
  
  I recently tried to fix some of the remaining problems that we
  have with
  
  Lilypond (or, more precisely, Guile)
  
  running under Windows, e.g.
  
  
https://lists.gnu.org/archive/html/bug-lilypond/2024-04/msg7.html
  
  
  I made a experimental release based on an upgrade to Guile 3.0.10
  and
  
  the bugfixes.
  
  I would really love to see it tested by Windows users before we
  
  incorporate the changes
  
  into our next development release.
  
  
  You can download the release here:
  
https://drive.google.com/file/d/1yjXZ_2vUQeNi-3djbXQmyhUB_sInpxr3/view?usp=sharing
  
  

I've tested processing a 94 page score and at least a quick
  inspection couldn't reveal any problems or differences compared to
  the official Linux version. The test was on Windows 10. 

   /Mats

  




Re: alternate time signatures

2024-06-29 Thread Jean Abou Samra

> I thought I had this solved before but I can't find it.  I need to set the 
> time signatures 9/8 and 3/4 side-by-side surrounded by parentheses at the 
> beginning of a score.

See https://lsr.di.unimi.it/LSR/Item?id=782

alternate time signatures

2024-06-29 Thread bobr...@centrum.is
I thought I had this solved before but I can't find it. I need to set the time 
signatures 9/8 and 3/4 side-by-side surrounded by parentheses at the beginning 
of a score. 

-David