Re: 64-bit Mac build of 2.20 is now available!

Am Mi., 18. März 2020 um 07:49 Uhr schrieb Aaron Hill : > > On 2020-03-17 11:05 pm, Marnen Laibow-Koser wrote: > > AFAIK this was never proper syntax to begin with. Does it compile with > > LilyPond 2.18? I'd be surprised if it does. > > Definitely valid syntax in 2.18.2 [1]: > > > \version

Text problem

Hi, everybody! Could someone tell me how to put a syllable of a word in a grace (appoggiatura, for example)? Thank so much! Mariona

Re: 64-bit Mac build of 2.20 is now available!

Thomas Morley writes: > Am Mi., 18. März 2020 um 07:49 Uhr schrieb Aaron Hill > : >> >> On 2020-03-17 11:05 pm, Marnen Laibow-Koser wrote: >> > AFAIK this was never proper syntax to begin with. Does it compile with >> > LilyPond 2.18? I'd be surprised if it does. >> >> Definitely valid syntax i

Re: Text problem

Hi Mariona, See: http://lilypond.org/doc/v2.19/Documentation/notation/stanzas.html#stanzas-with-different-rhythms Otherwise, could you be more specific? Could you provide a short example? HTH Pierre Le mer. 18 mars 2020 à 09:48, Mariona Reixach a écrit : > Hi, everybody! > > Could someone tell m

Re: Peculiar behavior of barlines

Am Mo., 16. März 2020 um 19:23 Uhr schrieb Sami Amiris : > > Hello all. > > I would like the barlines that span both staves (not the barlines in each > individual staff alone) at the middle of the line to have the same behaviour > at the next end (to the right) and the start of the line below at th

Re: Text problem

El 18/3/20 a las 9:47, Mariona Reixach escribió: Could someone tell me how to put a syllable of a word in a grace (appoggiatura, for example)? Mariona, I hope this example clarifies the docs. { c'4 \appoggiatura d'8 c'4 c'4 c'4 } \addlyrics { Do Do % appogg, no syllable Do

Re: 64-bit Mac build of 2.20 is now available!

Marnen Laibow-Koser writes: > On Wed, Mar 18, 2020 at 12:57 AM Zone Dremik wrote: > >> Hello, convert.ly is not working as you described. Here are some code >> excerpts. >> Let me know if there is anything else I can send that would be helpful. >> >> From a file previously created with Frescobal

Re: Peculiar behavior of barlines

Hello and thank you for your reply. The reason for the not minimal example is because each staff has its own timing. This is polymetric notation, not simple notation. Each staff has its very own barlines, and when I put them in a group, the barlines are united only when the timing of the two stave

Re: TextSpanner shortcut

Aaron Hill wrote > span-type and span-text are for dynamic text spanners (e.g. > CrescendoEvent). You can set these music properties for a > TextSpanEvent, but Text_spanner_engraver will just ignore them. > > Instead, you should \override or \tweak the bound-details of TextSpanner > to attach

Re: Peculiar behavior of barlines

> The reason for the not minimal example is because each staff has its > own timing. [...] Well, the problem at hand is not related to polymetric notation at all, AFAICS; you can use standard stuff also to demonstrate the problem... Werner

Re: 64-bit Mac build of 2.20 is now available!

Dear David, Il giorno mer 18 mar 2020 alle ore 09:48 David Kastrup ha scritto: > For which version number then? Likely the one for issue 4800? I may be wrong, but shouldn't it be for the version containing the new convert-ly rule (that is, by now, later than 2.20.0)? If a user has already used

Re: 64-bit Mac build of 2.20 is now available!

Davide Liessi writes: > Dear David, > > Il giorno mer 18 mar 2020 alle ore 09:48 David Kastrup ha > scritto: >> For which version number then? Likely the one for issue 4800? > > I may be wrong, but shouldn't it be for the version containing the new > convert-ly rule (that is, by now, later tha

Re: TextSpanner shortcut

On 2020-03-18 3:51 am, foxfanfare wrote: Thank you Aaron for the explanation. I was trying the make-music solution as I was also trying to make a generic function, something like: c4-\mySpan "molto rit." d e f g1\stopTextSpan No worries. Does this help? \version "2.20.0" startTextSpan

Re: 64-bit Mac build of 2.20 is now available!

Il giorno mer 18 mar 2020 alle ore 13:07 David Kastrup ha scritto: > It doesn't make sense to have convert-ly produce non-working code for > version 2.19.40 . And convert-ly cannot promise to fix code that never > worked due to its combination of version statement and old syntax. > > It isn't gu

Re: TextSpanner shortcut

Aaron Hill wrote > No worries. Does this help? That's perfect! Thank you very much :) -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

Re: 64-bit Mac build of 2.20 is now available!

Davide Liessi writes: > Il giorno mer 18 mar 2020 alle ore 13:07 David Kastrup ha > scritto: >> It doesn't make sense to have convert-ly produce non-working code for >> version 2.19.40 . And convert-ly cannot promise to fix code that never >> worked due to its combination of version statement

Re: Vertical alignment of RehearsalMarks

Thanks, Dominic, that helped for the given example, but I see that I need to give a more complete example of the chord chart I am working on. I also narrowed down the problem: the distance between Staff & ChordNames is not the same in the two lines, but I need it to be for this to work. Luckily, b

Re: Peculiar behavior of barlines

Werner LEMBERG wrote >> The reason for the not minimal example is because each staff has its >> own timing. [...] > > Well, the problem at hand is not related to polymetric notation at > all, AFAICS; you can use standard stuff also to demonstrate the > problem... Thank you for your response. Ι

Re: TextScript baseline in Dynamics context

Stefano Troncaro wrote > Hi Kieren, I was not aware of that function. Thank you for sharing it and > thank you Harm for coding it! Very interesting function! But I think there is a bug when using a separate Dynamics line. See the following example: \version "2.20.0" << \new Staff \relative c'

Re: 64-bit Mac build of 2.20 is now available!

On Wed, Mar 18, 2020 at 6:49 AM David Kastrup wrote: > Marnen Laibow-Koser writes: [...] > > > > AFAIK this was never proper syntax to begin with. Does it compile with > > LilyPond 2.18? I'd be surprised if it does. > > It was prior to 2.18, and it was merely discouraged with 2.18 (in the >

Re: 64-bit Mac build of 2.20 is now available!

Marnen Laibow-Koser writes: > On Wed, Mar 18, 2020 at 6:49 AM David Kastrup wrote: > >> Marnen Laibow-Koser writes: > > [...] > >> >> >> > AFAIK this was never proper syntax to begin with. Does it compile with >> > LilyPond 2.18? I'd be surprised if it does. >> >> It was prior to 2.18, and it

Re: 64-bit Mac build of 2.20 is now available!

It was quite a few years ago that copied this code sample from the LilyPond Notation Reference v2.18.2 webpage: http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables I've compiled hundreds of Lead-Sheets with it, but haven't up-dated Lilypond since 2.18.2

version 2.18.2 - incorrect bar numbers with full measure rests

version 2.18.2 With 4/2 time, Bar numbers are incorrectly printed when using full measure rests. Even printing bar numbers for each measure is numbered incorrectly(attached sample). \context {\Score \override BarNumber.break-visibility = #all-visible } Is there a way to print them properly oth

Re: 64-bit Mac build of 2.20 is now available!

On Wed, Mar 18, 2020 at 12:18 PM Zone Dremik wrote: > It was quite a few years ago that copied this code sample from the > LilyPond Notation Reference v2.18.2 webpage: > > http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables > I've compiled hundreds of Le

Re: 64-bit Mac build of 2.20 is now available!

Marnen Laibow-Koser writes: > On Wed, Mar 18, 2020 at 12:18 PM Zone Dremik wrote: > >> It was quite a few years ago that copied this code sample from the >> LilyPond Notation Reference v2.18.2 webpage: >> >> http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-var

Re: 64-bit Mac build of 2.20 is now available!

David Kastrup writes: > Marnen Laibow-Koser writes: > >> On Wed, Mar 18, 2020 at 12:18 PM Zone Dremik wrote: >> >>> It was quite a few years ago that copied this code sample from the >>> LilyPond Notation Reference v2.18.2 webpage: >>> >>> http://lilypond.org/doc/v2.18/Documentation/notation/fl

Re: version 2.18.2 - incorrect bar numbers with full measure rests

Am 18.03.20 um 17:44 schrieb Eby Mani: With 4/2 time, Bar numbers are incorrectly printed when using full measure rests. Even printing bar numbers for each measure is numbered incorrectly(attached sample). \context {\Score \override BarNumber.break-visibility = #all-visible } Is there a wa

Re: version 2.18.2 - incorrect bar numbers with full measure rests

Hi eby, I don't get your point - all I can see is: two full-measure rests, and after these two measures, the third measure, consequently, is bar number 3. Why should it be 5? I you had provided your sample code, it'd probably be easier to understand what you had in mind. Is it about the breve res

Three voices in same staff, from two variables

Hi all, I'm new here, so hopefully this isn't too basic of a question... I'm trying to write out harmonizations for standard melodies, so my initial thought was to keep the melody in its own variable and the harmonies in another and then combine them using the "<< \\ >>" syntax (see below). This

Re: Three voices in same staff, from two variables

El 18/3/20 a las 20:41, Ben Rosen escribió: Perhaps I should use something more explicit involving "\new Voice"? Is there a way to do this that preserves the variable structure I've laid out or is there a better approach for this situation? Here is how I would write your music. \version "2.20

Confused newbie

Hello all, Total newbie here, so I apologize if I am posting this to an incorrect correct place. I just downloaded the 2.20 version, trying to run it on an old iMac using OS 10.5. While I get the initial “Successfully installed” window/file, when trying to compile after saving I get a “Fatal e

Re: Peculiar behavior of barlines

Hello all. Thomas Morley-2 wrote > \defineBarLine "||-end" #'("||" #f " !") > \defineBarLine "||-beg" #'("||" #f "!") > \defineBarLine "||-!" #'("||-end" "||-beg" "!") > \defineBarLine "|-dashedSpan" #'("|" "|" "!") > \defineBarLine "|-!" #'("|-dashedSpan" "|-dashedSpan" "!") > > Should do the

Re: Peculiar behavior of barlines

> What did I do wrong? You didn't finish the bar line definition in line 24: \defineBarLine "|-!" #'("|-dashedSpan" "|-dashedSpan" "

Re: Peculiar behavior of barlines

Actually I stand corrected! I made a mistake, I corrected it and it works fine! Thank you very much! This is the snippet! I know that it would do a lot for people like me, maybe it should be included in the section about barlines? Thank you once again! S.A. --

Re: 64-bit Mac build of 2.20 is now available!

On Wed 18 Mar 2020 at 16:18:02 (+), Zone Dremik wrote: > It was quite a few years ago that copied this code sample from the LilyPond > Notation Reference v2.18.2 webpage: > http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables > I've compiled hundreds

Re: 64-bit Mac build of 2.20 is now available!

On Tue, Mar 17, 2020 at 7:06 PM Marnen Laibow-Koser wrote: > On Tue, Mar 17, 2020 at 6:48 PM Marnen Laibow-Koser > wrote: > >> On Tue, Mar 17, 2020 at 6:43 PM Arle Lommel >> wrote: >> >>> Glad my feedback seems to be useful. >>> >>> [cutting a bit here] >>> >>> Thanks, this makes sense. I shou

Re: Three voices in same staff, from two variables

Thanks for your response! I think I managed to get what I wanted (and no compilation errors) using just your "\new Voice { \voiceOne \melody }" in the \score block. The actual piece is a little different than this simplified example, and it seems like I don't need the multiple "\new Voice" stateme

Re: version 2.18.2 - incorrect bar numbers with full measure rests

> My understanding of "full measure rests" is, it covers the full measure based > on the time signature. Thus R1 is sufficient for a measure that is in 4/2 > time. That understanding is wrong. A full measure rest has a duration like normal rests, thus you will have to scale it according to y