addlyric

2021-10-01 Thread Mahanidhi
Hello everyone,
I'm having trouble inserting the lyrics. If they are whole words no problem but 
if the words are broken like: mu-sic it is very difficult to have them exactly 
under the corresponding note. to insert the lyric I use the command addlyric{}
Thanks for the help.
Mahanidhi

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

Re: addlyric

2021-10-01 Thread Lukas-Fabian Moser

Hi Mahanidhi,

Am 01.10.21 um 11:44 schrieb Mahanidhi:
I'm having trouble inserting the lyrics. If they are whole words no 
problem but if the words are broken like: mu-sic it is very difficult 
to have them exactly under the corresponding note. to insert the lyric 
I use the command addlyric{}

Thanks for the help.


Your problem is hard to diagnose without a compilable example 
demonstrating your issue.


But note that for LilyPond, it's not mu-sic but mu -- sic:

%%%

\version "2.22"

\layout {
  ragged-last = ##f
}

\relative {
  \key e \major
  gis'8 a16 b~ b cis8 b16~ b8 fis~ 4~ | 2
} \addlyrics {
  Mu -- sic was my first love __
}

%%%

Although I have to admit that I managed to give an example that doesn't 
show LilyPond at its best: Tie directions are far from ideal here.


Lukas



Re: voiceOne and oneVoice

2021-10-01 Thread Leo Correia de Verdier
While this is certainly useful, one should be aware of what is happening. With 
the syntax 

soprano.1 = c’4

you are not defining a variable soprano.1 as c’4, you are defining the value 
corresponding to key 1 in an alist that is the value of variable soprano. This 
can be very powerful, useful and stylish, but also cause problems if you’re 
unaware of it, for instance: If you uncomment the fourth line in the following 
example it will stop working, since you overwrite the whole variable soprano 
containing the alist instead of creating a new variable with a shorter name. 

\version "2.22.1"
soprano.1 = e'4
soprano.2 = c'4
%soprano = d'4
\score { <<
  \soprano.1
  \soprano.2 >> }

There is more about alists in the documentation, and they’re used in very many 
places in lilypond. You can see them in the common structure Thing.property = 
value , for instance in overrides. 

Best
/Leo

> 30 sep. 2021 kl. 09:37 skrev Silvain Dupertuis :
> 
> Hi everyone,
> 
> One problem with this suggestion that Lilypond does not support the simple 
> use of digits in variable names.
> As far as I understand, it is because a digit following directly alphabetic 
> characters is interpreted as a duration.
> 
> I took me a long time to discover that there is a way out 
> (and I suggest these feature should be more accessible in the documentation!)
> 
> One can use numbered variables using a full-stop mark like these examples
> -- soprano.1, soprano.2 ... 
> -- mel.354, mel.521 -- using the song number in a songbook
> May-be other separation marks would work too. 
> One can also use quote marks for more sophisticated names, but it is more 
> complicated and rather inelegant...
> 
> Silvain
> 
> Le 30.09.21 à 07:52, Valentin Petzel a écrit :
>Hi David,
>> 
>> I'd say singleVoice would even be clearer.
>> But I think maybe it would also be a good idea if we had a synax like \voice 
>> number. Currently Lilypond only supports four voices, and any more requires 
>> knowledge about the scheme interface, but \voice1 \voice2, ... could 
>> directly support an arbitrary amount of voices.
>> 
>> Cheers,
>> Valentin
>> 
>> 30.09.2021 00:50:41 David Kastrup   
>> :
>> 
>>> Lukas-Fabian Moser   writes:
>>> 
 Hi Kira,
 
 Am 30.09.21 um 00:32 schrieb Kira Garvie:
> I realize this is a pretty basic question... but what is the
> difference between voiceOne and oneVoice? I am writing a multivoice
> keyboard-style hymn (as opposed to SATB chorale style) and the
> directions say to switch between oneVoice and voiceOne as needed for
> stem direction...
> "(d) Add voiceOne and oneVoice tags throughout to indicate stem
> direction. If
> there is no separately stemmed second part at the first note,
> oneVoice is assumed."
> Do I need to give an example?
 \voiceOne sets the layout for the current voice as if it is the first
 of several simultaneous voices.
 \oneVoice sets the layout for the current voice as if it is an only voice.
>>> It would probably be clearer if we had
>>> 
>>> \firstVoice and \soleVoice instead of \voiceOne and \oneVoice, respectively.
>>> 
>>> --
>>> David Kastrup
> 
> Visa citerat innehåll
>> Hi David,
>> 
>> I'd say singleVoice would even be clearer.
>> But I think maybe it would also be a good idea if we had a synax like \voice 
>> number. Currently Lilypond only supports four voices, and any more requires 
>> knowledge about the scheme interface, but \voice1 \voice2, ... could 
>> directly support an arbitrary amount of voices.
>> 
>> Cheers,
>> Valentin
>> 
>> 30.09.2021 00:50:41 David Kastrup  :
>> 
>>> Lukas-Fabian Moser   writes:
>>> 
 Hi Kira,
 
 Am 30.09.21 um 00:32 schrieb Kira Garvie:
> I realize this is a pretty basic question... but what is the
> difference between voiceOne and oneVoice? I am writing a multivoice
> keyboard-style hymn (as opposed to SATB chorale style) and the
> directions say to switch between oneVoice and voiceOne as needed for
> stem direction...
> "(d) Add voiceOne and oneVoice tags throughout to indicate stem
> direction. If
> there is no separately stemmed second part at the first note,
> oneVoice is assumed."
> Do I need to give an example?
 \voiceOne sets the layout for the current voice as if it is the first
 of several simultaneous voices.
 \oneVoice sets the layout for the current voice as if it is an only voice.
>>> It would probably be clearer if we had
>>> 
>>> \firstVoice and \soleVoice instead of \voiceOne and \oneVoice, respectively.
>>> 
>>> --
>>> David Kastrup
>> 
>> -- 
>> Silvain Dupertuis
>> Route de Lausanne 335
>> 1293 Bellevue (Switzerland)
>> tél. +41-(0)22-774.20.67
>> portable +41-(0)79-604.87.52
>> web: silvain-dupertuis.org  
> -- 
> Silvain Dupertuis
> Route de Lausanne 335
> 1293 Bellevue (Switzerland)
> tél. +41-(0

Related notes

2021-10-01 Thread Mahanidhi
Hi,
I've to join the notes "bf32 df ef" before the bar of the first line as the 
three notes of equal duration on the same line and in the next one but it 
doesn't happen automatically.
I tried with [ ] butthe stile is different.
Code without brackets:
\version "2.22.1"
\language "english"

\header {
title = " Jāgo āmār swapan"
arranger = "1971"
composer = "Sri Chinmoy"
tagline = ##f % toglie pie di pagina lilypond
}

\paper {
top-margin = 10
right-margin = 15
left-margin = 0
}

\layout {
\context {
\Score
\remove "Bar_number_engraver"
defaultBarType = "" }} % toglie le barre

\layout {
\context {
\Staff
\remove "Time_signature_engraver"
}} % tolgie il tempo

\layout {% to align
ragged-last = ##f
line-width = 195 % or some other number
}

\relative c'

{\key df \major
\time 4/4
\tempo "Moderate - slow" 4 = 72
df ff2. ef4 ff2. ef4 bf32 (cf df ef2. ) ef8(gf2) bf,32 df ef ff2.\bar "|"}
\addlyrics {Jā -- go ā -- mār swā -- pan __ sā -- thi __ }

\relative c'
{\key df \major ef4ff2 ef4. ff2. ef4 bf32 cf df ef2. b4^"rit." a g2 a\bar "|"}

Code with brackets:
\version "2.22.1"
\language "english"

\header {
title = " Jāgo āmār swapan"
arranger = "1971"
composer = "Sri Chinmoy"
tagline = ##f % toglie pie di pagina lilypond
}

\paper {
top-margin = 10
right-margin = 15
left-margin = 0
}

\layout {
\context {
\Score
\remove "Bar_number_engraver"
defaultBarType = "" }} % toglie le barre

\layout {
\context {
\Staff
\remove "Time_signature_engraver"
}} % tolgie il tempo

\layout {% to align
ragged-last = ##f
line-width = 195 % or some other number
}

\relative c'

{\key df \major
\time 4/4
\tempo "Moderate - slow" 4 = 72
df ff2. ef4 ff2. ef4 bf32 (cf df ef2. ) ef8(gf2) [bf,32 df ef ] ff2.\bar "|"}
\addlyrics {Jā -- go ā -- mār swā -- pan __ sā -- thi __ }

\relative c'
{\key df \major ef4ff2 ef4. ff2. ef4 bf32 cf df ef2. b4^"rit." a g2 a\bar "|"}

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

Re: Related notes

2021-10-01 Thread Lukas-Fabian Moser

Hi Mahanidhi,

Am 01.10.21 um 12:50 schrieb Mahanidhi:
I've to join the notes "*bf32 df ef*" before the bar of the first line 
as the three notes of equal duration on the same line and in the next 
one but it doesn't happen automatically.

I tried with [ ] butthe stile is different.


I'm not sure if I understand your question correctly.

In LilyPond, it's not

[bf32 df ef]

but

bf32[ df ef]

that is to say: beam brackets are postfix operators.

LilyPond has an excellent Learning Manual which contains a tutorial that 
one can work through in comparatively short time; it answers many 
questions you seem to have at the moment: 
https://lilypond.org/doc/v2.22/Documentation/learning/index.html


Lukas



Re: Related notes

2021-10-01 Thread Leo Correia de Verdier
You have put the bracket in the wrong place, in lilypond you do not put the 
opening bracket before the first node in the group, but after, the same way you 
would write a slur.

\version "2.22.1" 
\language "english"
\relative c' { bf32[ df ef ] }

Also, please make your code examples small, just enough to illustrate the 
problem. 

Hope that helped

/Leo

> 1 okt. 2021 kl. 12:50 skrev Mahanidhi :
> 
> Hi,
> I've to join the notes "bf32 df ef" before the bar of the first line as the 
> three notes of equal duration on the same line and in the next one but it 
> doesn't happen automatically.
> I tried with [ ] butthe stile is different.
> Code without  brackets:
> \version "2.22.1" 
> \language "english"
> 
> \header {
>   title = "  Jāgo āmār swapan"
>   arranger = "1971"
>   composer = "Sri Chinmoy"
>   tagline = ##f % toglie pie di pagina lilypond
> }
> 
> 
> \paper {
> top-margin = 10
> right-margin = 15
> left-margin = 0
> }
> 
> \layout {
>   \context {
> \Score
> \remove "Bar_number_engraver"
>  defaultBarType = "" }} % toglie le barre
> 
> \layout {
>   \context {
> \Staff
>   \remove "Time_signature_engraver"
> }} % tolgie il tempo
> 
> \layout {% to align
>   ragged-last = ##f
>   line-width = 195 % or some other number
> }
> 
> \relative c'
> 
> {\key df \major
>   \time 4/4
>   \tempo "Moderate - slow" 4 = 72
> df ff2. ef4 ff2. ef4 bf32 (cf df ef2. ) ef8(gf2)   bf,32 df ef   ff2.\bar "|"}
> \addlyrics {Jā -- go  ā  -- mār swā -- pan __ sā -- thi __ }
> 
> \relative c'
> {\key df \major ef4ff2 ef4. ff2. ef4 bf32 cf df  ef2. b4^"rit." a g2 a\bar 
> "|"}
> 
> Code with  brackets:
> \version "2.22.1" 
> \language "english"
> 
> \header {
>   title = "  Jāgo āmār swapan"
>   arranger = "1971"
>   composer = "Sri Chinmoy"
>   tagline = ##f % toglie pie di pagina lilypond
> }
> 
> 
> \paper {
> top-margin = 10
> right-margin = 15
> left-margin = 0
> }
> 
> \layout {
>   \context {
> \Score
> \remove "Bar_number_engraver"
>  defaultBarType = "" }} % toglie le barre
> 
> \layout {
>   \context {
> \Staff
>   \remove "Time_signature_engraver"
> }} % tolgie il tempo
> 
> \layout {% to align
>   ragged-last = ##f
>   line-width = 195 % or some other number
> }
> 
> \relative c'
> 
> {\key df \major
>   \time 4/4
>   \tempo "Moderate - slow" 4 = 72
> df ff2. ef4 ff2. ef4 bf32 (cf df ef2. ) ef8(gf2)   [bf,32 df ef ]  ff2.\bar 
> "|"}
> \addlyrics {Jā -- go  ā  -- mār swā -- pan __ sā -- thi __ }
> 
> \relative c'
> {\key df \major ef4ff2 ef4. ff2. ef4 bf32 cf df  ef2. b4^"rit." a g2 a\bar 
> "|"}
> 
> 
> Sent with ProtonMail Secure Email.
> 




Re: How to get warnings for unused parts of a file?

2021-10-01 Thread Omid Mo'menzadeh
Thank you for your reply. This is working, but like this:
main = #(if (not (defined? 'is-loaded-file))
  #{
\score { \vocal }
  #}
)

\main

Any idea why it wouldn't work without defining the main variable? It's fine
for me, but I don't get why the following snippet does not work for me:
#(if (not (defined? 'is-loaded-file))
  #{
\score { \vocal }
  #}
)

I'm using Lilypond 2.22.1 if that makes a difference.

On Tue, Sep 14, 2021 at 12:44 PM Leo Correia de Verdier <
leo.correia.de.verd...@gmail.com> wrote:

> There might be more elegant ways to do it (there probably is), but I have
> a variable I define in my output files, is-loaded-file and then I can use
> #(if (defined? 'is-loaded-file) … ) in the definition files to test. This
> requires a situation where there’s a clear separation between ”definition
> files” and ”output files”, but works quite well for me.
>
>
> > 14 sep. 2021 kl. 09:52 skrev Omid Mo'menzadeh :
> >
> > Hello all. This might be a weird thing to seek, but here is the scenario:
> > I have several files defining (but not using) different parts of the
> score, which other files use to construct several output types.
> >
> > But the problem is the command `lilypond -l WARNING -o /path/to/file.ly`
> does not show a warning for the following example file:
> > ghigh = \relative c {
> >   \clef "treble_8"
> >   \time 4/4
> >   \voiceOne
> >   c2 |
> > }
> >
> > It does, if I include the following part at the end of the file:
> > \book {
> >   \ghigh
> > }
> >
> > But the problem is that when I include it in another file, I get an
> extra output!
> >
> > A possible solution could look like an `if __name__ == "__main__"`
> clause in Python, but I don't know if we have a similar variable available
> in Lilypond.
> > Thanks in advance,
> > Omid
>
>


Re: How to get warnings for unused parts of a file?

2021-10-01 Thread Leo Correia de Verdier
Funny! 

I have no idea. Smarter people on this list will certainly know, though.


> 1 okt. 2021 kl. 13:31 skrev Omid Mo'menzadeh :
> 
> Thank you for your reply. This is working, but like this:
> main = #(if (not (defined? 'is-loaded-file))
>   #{
> \score { \vocal }
>   #}
> )
> 
> \main
> 
> Any idea why it wouldn't work without defining the main variable? It's fine 
> for me, but I don't get why the following snippet does not work for me:
> #(if (not (defined? 'is-loaded-file))
>   #{
> \score { \vocal }
>   #}
> )
> 
> I'm using Lilypond 2.22.1 if that makes a difference.
> 
> On Tue, Sep 14, 2021 at 12:44 PM Leo Correia de Verdier 
>  wrote:
> There might be more elegant ways to do it (there probably is), but I have a 
> variable I define in my output files, is-loaded-file and then I can use #(if 
> (defined? 'is-loaded-file) … ) in the definition files to test. This requires 
> a situation where there’s a clear separation between ”definition files” and 
> ”output files”, but works quite well for me.
> 
> 
> > 14 sep. 2021 kl. 09:52 skrev Omid Mo'menzadeh :
> > 
> > Hello all. This might be a weird thing to seek, but here is the scenario:
> > I have several files defining (but not using) different parts of the score, 
> > which other files use to construct several output types.
> > 
> > But the problem is the command `lilypond -l WARNING -o /path/to/file.ly` 
> > does not show a warning for the following example file:
> > ghigh = \relative c {
> >   \clef "treble_8"
> >   \time 4/4
> >   \voiceOne
> >   c2 |
> > }
> > 
> > It does, if I include the following part at the end of the file:
> > \book {
> >   \ghigh
> > }
> > 
> > But the problem is that when I include it in another file, I get an extra 
> > output!
> > 
> > A possible solution could look like an `if __name__ == "__main__"` clause 
> > in Python, but I don't know if we have a similar variable available in 
> > Lilypond.
> > Thanks in advance,
> > Omid
> 




Re: How to get warnings for unused parts of a file?

2021-10-01 Thread David Kastrup
"Omid Mo'menzadeh"  writes:

> Thank you for your reply. This is working, but like this:
> main = #(if (not (defined? 'is-loaded-file))
>   #{
> \score { \vocal }
>   #}
> )
>
> \main
>
> Any idea why it wouldn't work without defining the main variable? It's fine
> for me, but I don't get why the following snippet does not work for me:
> #(if (not (defined? 'is-loaded-file))
>   #{
> \score { \vocal }
>   #}
> )

#... at the top level is executed but not interpreted.  That is because
it may contain things like assignments where the value is irrelevant.

If you want to force interpretation of the result, use $ instead of # .
In fact, apart from requiring a variable name instead of a Scheme
expression behind it $ and \ behave the same, so you could write $main
instead of \main , and you could write $(if (not (defined? ... .

There is a wrinkle here: what happens if the condition is not met?  In
that case, $... would want to interpret whatever value (if #f #f)
returns.  This value is undefined, but Guile specifically returns
*undefined* (a special value) in this case and LilyPond has been wired
to do nothing given

$*undefined*

so this happens to work as expected anyway.

-- 
David Kastrup



Re: How to get warnings for unused parts of a file?

2021-10-01 Thread Jean Abou Samra

Le 01/10/2021 à 14:09, David Kastrup a écrit :

$*undefined*


I think you mean

$*unspecified*

Jean




Re: How to get warnings for unused parts of a file?

2021-10-01 Thread David Kastrup
Jean Abou Samra  writes:

> Le 01/10/2021 à 14:09, David Kastrup a écrit :
>> $*undefined*
>
> I think you mean
>
> $*unspecified*

Right.  Sorry.

-- 
David Kastrup



Re: How to get warnings for unused parts of a file?

2021-10-01 Thread Jean Abou Samra

Le 01/10/2021 à 15:05, David Kastrup a écrit :

Right.  Sorry.



No need to be sorry. Just happens.

It's not like there is no potential for confusion,
cf. commits 662c549602 and e12ee4107c0…

Jean



Re: Related notes

2021-10-01 Thread Leo Correia de Verdier
As you are writing the music in 4/4 time and merely hiding the barlines the 
beaming still behaves as in an (otherwise invisible) 4/4. The first three 32nd 
happen to fall in the same beat and are beamed together. The in the second 
group the second 32nd falls on the downbeat and the first note is the last 32nd 
of the previous beat, and so is beamed separate from the other. This was part 
of the reason I suggested \cadenzaOn (but that removes automatic beaming 
altogether).

> 1 okt. 2021 kl. 14:49 skrev Mahanidhi :
> 
> It works thank you all. But why is not automatic as the other ?
> Mahanidhi
> 
> Sent with ProtonMail Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> 
> Il venerdì 1 ottobre 2021 13:21, Leo Correia de Verdier 
>  ha scritto:
> 
>> You have put the bracket in the wrong place, in lilypond you do not put the 
>> opening bracket before the first node in the group, but after, the same way 
>> you would write a slur.
>> 
>> \version "2.22.1"
>> 
>> \language "english"
>> 
>> \relative c' { bf32[ df ef ] }
>> 
>> Also, please make your code examples small, just enough to illustrate the 
>> problem.
>> 
>> Hope that helped
>> 
>> /Leo
>> 
>>> 1 okt. 2021 kl. 12:50 skrev Mahanidhi mahani...@protonmail.com:
>>> 
>>> Hi,
>>> 
>>> I've to join the notes "bf32 df ef" before the bar of the first line as the 
>>> three notes of equal duration on the same line and in the next one but it 
>>> doesn't happen automatically.
>>> 
>>> I tried with [ ] butthe stile is different.
>>> 
>>> Code without brackets:
>>> 
>>> \version "2.22.1"
>>> 
>>> \language "english"
>>> 
>>> \header {
>>> 
>>> title = " Jāgo āmār swapan"
>>> 
>>> arranger = "1971"
>>> 
>>> composer = "Sri Chinmoy"
>>> 
>>> tagline = ##f % toglie pie di pagina lilypond
>>> 
>>> }
>>> 
>>> \paper {
>>> 
>>> top-margin = 10
>>> 
>>> right-margin = 15
>>> 
>>> left-margin = 0
>>> 
>>> }
>>> 
>>> \layout {
>>> 
>>> \context {
>>> 
>>> \Score
>>> 
>>> \remove "Bar_number_engraver"
>>> 
>>> defaultBarType = "" }} % toglie le barre
>>> 
>>> \layout {
>>> 
>>> \context {
>>> 
>>> \Staff
>>> 
>>> \remove "Time_signature_engraver"
>>> 
>>> }} % tolgie il tempo
>>> 
>>> \layout {% to align
>>> 
>>> ragged-last = ##f
>>> 
>>> line-width = 195 % or some other number
>>> 
>>> }
>>> 
>>> \relative c'
>>> 
>>> {\key df \major
>>> 
>>> \time 4/4
>>> 
>>> \tempo "Moderate - slow" 4 = 72
>>> 
>>> df ff2. ef4 ff2. ef4 bf32 (cf df ef2. ) ef8(gf2) bf,32 df ef ff2.\bar "|"}
>>> 
>>> \addlyrics {Jā -- go ā -- mār swā -- pan __ sā -- thi __ }
>>> 
>>> \relative c'
>>> 
>>> {\key df \major ef4ff2 ef4. ff2. ef4 bf32 cf df ef2. b4^"rit." a g2 a\bar 
>>> "|"}
>>> 
>>> Code with brackets:
>>> 
>>> \version "2.22.1"
>>> 
>>> \language "english"
>>> 
>>> \header {
>>> 
>>> title = " Jāgo āmār swapan"
>>> 
>>> arranger = "1971"
>>> 
>>> composer = "Sri Chinmoy"
>>> 
>>> tagline = ##f % toglie pie di pagina lilypond
>>> 
>>> }
>>> 
>>> \paper {
>>> 
>>> top-margin = 10
>>> 
>>> right-margin = 15
>>> 
>>> left-margin = 0
>>> 
>>> }
>>> 
>>> \layout {
>>> 
>>> \context {
>>> 
>>> \Score
>>> 
>>> \remove "Bar_number_engraver"
>>> 
>>> defaultBarType = "" }} % toglie le barre
>>> 
>>> \layout {
>>> 
>>> \context {
>>> 
>>> \Staff
>>> 
>>> \remove "Time_signature_engraver"
>>> 
>>> }} % tolgie il tempo
>>> 
>>> \layout {% to align
>>> 
>>> ragged-last = ##f
>>> 
>>> line-width = 195 % or some other number
>>> 
>>> }
>>> 
>>> \relative c'
>>> 
>>> {\key df \major
>>> 
>>> \time 4/4
>>> 
>>> \tempo "Moderate - slow" 4 = 72
>>> 
>>> df ff2. ef4 ff2. ef4 bf32 (cf df ef2. ) ef8(gf2) [bf,32 df ef ] ff2.\bar 
>>> "|"}
>>> 
>>> \addlyrics {Jā -- go ā -- mār swā -- pan __ sā -- thi __ }
>>> 
>>> \relative c'
>>> 
>>> {\key df \major ef4ff2 ef4. ff2. ef4 bf32 cf df ef2. b4^"rit." a g2 a\bar 
>>> "|"}
>>> 
>>> Sent with ProtonMail Secure Email.




Re: Related notes

2021-10-01 Thread Leo Correia de Verdier
Somewhat apart from the original subject, would there be a way to make lilypond 
assume there should be beams between all notes shorter than a quarter unless a 
beam break is specified when auto beaming is off, something like the opposite 
of the default behavior?

> 1 okt. 2021 kl. 15:25 skrev Leo Correia de Verdier 
> :
> 
> As you are writing the music in 4/4 time and merely hiding the barlines the 
> beaming still behaves as in an (otherwise invisible) 4/4. The first three 
> 32nd happen to fall in the same beat and are beamed together. The in the 
> second group the second 32nd falls on the downbeat and the first note is the 
> last 32nd of the previous beat, and so is beamed separate from the other. 
> This was part of the reason I suggested \cadenzaOn (but that removes 
> automatic beaming altogether).
> 
>> 1 okt. 2021 kl. 14:49 skrev Mahanidhi :
>> 
>> It works thank you all. But why is not automatic as the other ?
>> Mahanidhi
>> 
>> Sent with ProtonMail Secure Email.
>> 
>> ‐‐‐ Original Message ‐‐‐
>> 
>> Il venerdì 1 ottobre 2021 13:21, Leo Correia de Verdier 
>>  ha scritto:
>> 
>>> You have put the bracket in the wrong place, in lilypond you do not put the 
>>> opening bracket before the first node in the group, but after, the same way 
>>> you would write a slur.
>>> 
>>> \version "2.22.1"
>>> 
>>> \language "english"
>>> 
>>> \relative c' { bf32[ df ef ] }
>>> 
>>> Also, please make your code examples small, just enough to illustrate the 
>>> problem.
>>> 
>>> Hope that helped
>>> 
>>> /Leo
>>> 
 1 okt. 2021 kl. 12:50 skrev Mahanidhi mahani...@protonmail.com:
 
 Hi,
 
 I've to join the notes "bf32 df ef" before the bar of the first line as 
 the three notes of equal duration on the same line and in the next one but 
 it doesn't happen automatically.
 
 I tried with [ ] butthe stile is different.
 
 Code without brackets:
 
 \version "2.22.1"
 
 \language "english"
 
 \header {
 
 title = " Jāgo āmār swapan"
 
 arranger = "1971"
 
 composer = "Sri Chinmoy"
 
 tagline = ##f % toglie pie di pagina lilypond
 
 }
 
 \paper {
 
 top-margin = 10
 
 right-margin = 15
 
 left-margin = 0
 
 }
 
 \layout {
 
 \context {
 
 \Score
 
 \remove "Bar_number_engraver"
 
 defaultBarType = "" }} % toglie le barre
 
 \layout {
 
 \context {
 
 \Staff
 
 \remove "Time_signature_engraver"
 
 }} % tolgie il tempo
 
 \layout {% to align
 
 ragged-last = ##f
 
 line-width = 195 % or some other number
 
 }
 
 \relative c'
 
 {\key df \major
 
 \time 4/4
 
 \tempo "Moderate - slow" 4 = 72
 
 df ff2. ef4 ff2. ef4 bf32 (cf df ef2. ) ef8(gf2) bf,32 df ef ff2.\bar "|"}
 
 \addlyrics {Jā -- go ā -- mār swā -- pan __ sā -- thi __ }
 
 \relative c'
 
 {\key df \major ef4ff2 ef4. ff2. ef4 bf32 cf df ef2. b4^"rit." a g2 a\bar 
 "|"}
 
 Code with brackets:
 
 \version "2.22.1"
 
 \language "english"
 
 \header {
 
 title = " Jāgo āmār swapan"
 
 arranger = "1971"
 
 composer = "Sri Chinmoy"
 
 tagline = ##f % toglie pie di pagina lilypond
 
 }
 
 \paper {
 
 top-margin = 10
 
 right-margin = 15
 
 left-margin = 0
 
 }
 
 \layout {
 
 \context {
 
 \Score
 
 \remove "Bar_number_engraver"
 
 defaultBarType = "" }} % toglie le barre
 
 \layout {
 
 \context {
 
 \Staff
 
 \remove "Time_signature_engraver"
 
 }} % tolgie il tempo
 
 \layout {% to align
 
 ragged-last = ##f
 
 line-width = 195 % or some other number
 
 }
 
 \relative c'
 
 {\key df \major
 
 \time 4/4
 
 \tempo "Moderate - slow" 4 = 72
 
 df ff2. ef4 ff2. ef4 bf32 (cf df ef2. ) ef8(gf2) [bf,32 df ef ] ff2.\bar 
 "|"}
 
 \addlyrics {Jā -- go ā -- mār swā -- pan __ sā -- thi __ }
 
 \relative c'
 
 {\key df \major ef4ff2 ef4. ff2. ef4 bf32 cf df ef2. b4^"rit." a g2 a\bar 
 "|"}
 
 Sent with ProtonMail Secure Email.
> 




Re: Moving tuplet brackets

2021-10-01 Thread Paul Hodges
This was so simple, and just works as required, except for one thing.
Using priority 2000 puts the brackets above tempo indications and other
markup; I used Leo's value of 750 which did it exactly right.  Leo's
additional "avoid-scripts" and "avoid-slur" overrides were not needed,
in my case at least.

Thanks to you both,
Paul

On 28/09/2021 10:45:39, "Lukas-Fabian Moser"  wrote:

>
>>
>>In this case, I'm not sure what Harm did to ensure horizontal position of 
>>tuplet brackets. In the following solution, I'm doing a bit of a hack: I ask 
>>LilyPond to place the tuplet bracket outside everything else (that's the 
>>value of outside-staff-priority), and then I force them to be horizontal by 
>>letting LilyPond calculate the "usual" slope and afterwards forcing left and 
>>right y-position to the average value:
>
>Oh, I'm sorry, I didn't realise that the outside-staff-priority overrides the 
>manual setting of positions. Then of course it's much easier:
>
>\version "2.22"
>
>\relative {
>\tupletUp
>\override TupletBracket.bracket-visibility = ##t
>\override TupletBracket.outside-staff-priority = 2000
>\override TupletBracket.positions = #'(0 . 0)
>
>\tuplet 3/2 4 { b''8[(-> c) r] g[(-> fis) r] }
>}
>
>Lukas
>



Re: Beams over rests

2021-10-01 Thread Paul Hodges
Thanks - adjusting the Stem.details.beamed-length as required did the 
job, though as you say it requires adjustment for each individual case.  
So I gritted my teeth and did it - there were 54 instances (less than I 
would have guessed actually), so it was quite manageable.

To my surprise, mostly it looks quite good; there are a couple of bars 
in which no note has less than four leger lines, and these look more 
attenuated than I think is sensible - but the publishers will have to 
say.  Of course, if they agree a compromise in a few cases, the 
adjustment is very easy now the commands are in place.  Also, I've left 
beams which don't need this adjustment untouched - in a couple of cases 
tweaking them to match the extended beams either side of them might look 
better.

Thanks for the tip.
Paul

On 28/09/2021 10:14:26, "N. Andrew Walsh"  
wrote:

>Hi Paul,
>
>I'm sure you know of the override pair:
>
>\override Stem.stemlet-length = #0.5
>\override Stem.details.beamed-lengths = #'(4.75)
>( music with beamed rests here )
>\revert Stem.stemlet-length
>\revert Stem.details.beamed-lengths
>
>I'm not aware of any way to set this globally. Well, the first one can 
>be set once. You'll still have to use "[" and "]" to force beaming, and 
>you should, for the sake of Best Practices™, set the stemlet length 
>manually for each one.
>
>But this is the way I've had to do it; and while it's tedious to do 
>that for every affected beam, it ensures that they look good and work 
>properly.
>
>Cheers,
>
>A
>
>On Tue, Sep 28, 2021 at 11:08 AM Paul Hodges  wrote:
>>The composer I'm working on is very fond of having beams over rests -
>>and indeed it helps a lot in reading his more complex rhythms.  
>>However,
>>LilyPond is treating rests differently from notes, in that beam
>>positions are adjusted to suit the notes, whereas rests are then
>>adjusted to suit the beams.  So I get this kind of layout:
>>However, the publisher wants rests to remain in their standard 
>>position,
>>like this:
>>
>>with occasional compromises to this extent:
>>
>>
>>I can obviously force this in individual cases, but again, is there a
>>global adjustment I can make to get nearer to what I'm being asked 
>>for?
>>
>>Thanks,
>>Paul

lyric start

2021-10-01 Thread Mahanidhi
In this music the third line as two grace notes. The lylirc automatically 
starts from the note and not from the grace note.What's the code to tell 
Lilypand to start fron the grace note?
Thank you.

CODE:
\version "2.22.1"
\language "english"

\header {
title = " Jāgo āmār swapan"
arranger = "1971"
composer = "Sri Chinmoy"
tagline = ##f % toglie pie di pagina lilypond
}

\paper {
top-margin = 10
right-margin = 15
left-margin = 0
}

\layout {
\context {
\Score
\remove "Bar_number_engraver"
defaultBarType = "" }} % toglie le barre

\layout {
\context {
\Staff
\remove "Time_signature_engraver"
}} % tolgie il tempo

\layout {% to align
ragged-last = ##f
line-width = 195 % or some other number
}

\relative c'

{\key df \major
\time 4/4
\tempo "Moderate - slow" 4 = 72
df ff2. ef4 ff2. ef4 bf32 (cf df ef2. ) ef8(gf2) bf,32[df ef] ff2.\bar "|"}
\addlyrics {Jā -- go ā -- mār swā -- pan __ sā -- thi __ _ _ _ }

\relative c'
{\key df \major ef4ff2 ef4. ff2. ef4 bf32 cf df ef2. b4^"(rit.)" a g2 a\bar "|"}
\addlyrics {Jā -- go ā -- mār prā -- ner __ _ _ _ pran __ _ _ _ }

\relative c'
{\key df \major af4 \acciaccatura bf8 df2 ef4 ef2 f4 f2 \acciaccatura { f16 
gf16 } af2 bf af gf \bar "|"}
\addlyrics {Jā -- go ā -- mār cho -- kher jyo -- ti __ _ _ }

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

Re: lyric start

2021-10-01 Thread Thomas Morley
Am Fr., 1. Okt. 2021 um 20:53 Uhr schrieb Mahanidhi :
>
> In this music the third line as two grace notes. The lylirc automatically 
> starts from the note and not from the grace note.What's the code to tell 
> Lilypand to start fron the grace note?
> Thank you.
>
> CODE:
> \version "2.22.1"
> \language "english"
>
> \header {
>   title = "  Jāgo āmār swapan"
>   arranger = "1971"
>   composer = "Sri Chinmoy"
>   tagline = ##f % toglie pie di pagina lilypond
> }
>
>
> \paper {
> top-margin = 10
> right-margin = 15
> left-margin = 0
> }
>
> \layout {
>   \context {
> \Score
> \remove "Bar_number_engraver"
>  defaultBarType = "" }} % toglie le barre
>
> \layout {
>   \context {
> \Staff
>   \remove "Time_signature_engraver"
> }} % tolgie il tempo
>
> \layout {% to align
>   ragged-last = ##f
>   line-width = 195 % or some other number
> }
>
> \relative c'
>
> {\key df \major
>   \time 4/4
>   \tempo "Moderate - slow" 4 = 72
> df ff2. ef4 ff2. ef4 bf32 (cf df ef2. ) ef8(gf2)   bf,32[df ef]  ff2.\bar "|"}
> \addlyrics {Jā -- go  ā  -- mār swā -- pan __ sā -- thi __ _ _ _ }
>
> \relative c'
> {\key df \major ef4ff2 ef4. ff2. ef4 bf32 cf df  ef2. b4^"(rit.)" a g2 a\bar 
> "|"}
>   \addlyrics {Jā -- go  ā  -- mār prā -- ner __ _ _ _ pran __ _ _ _ }
>
>   \relative c'
> {\key df \major  af4  \acciaccatura  bf8 df2 ef4 ef2 f4 f2  \acciaccatura { 
> f16 gf16 } af2 bf af gf \bar "|"}
>\addlyrics {Jā -- go  ā  -- mār cho -- kher jyo -- ti __ _ _ }
>
> Sent with ProtonMail Secure Email.
>

http://lilypond.org/website/tiny-examples.html



Re: lyric start

2021-10-01 Thread Knute Snortum
On Fri, Oct 1, 2021 at 12:00 PM Thomas Morley  wrote:

>
> http://lilypond.org/website/tiny-examples.html
>

Just to expand on Thomas Morley's post.  Everyone on this list is a
volunteer.  People kindly take time out of their busy schedules to
offer advice on LilyPond.  Since their time is worth something, it's
polite to have your question as well researched as possible.  Part of
that research is making a "tiny example" or Minimal Working Example
(MWE).  Strip out everything in your code that does not demonstrate
the problem.  This makes the problem clearer to you and everyone.
Sometimes making a MWE actually solves the problem.

In your code, your question has nothing to do with the header, paper,
or layout sections.  Remove them.  Only the third verse demonstrates
the problem, so remove the first and second verse.  Now you have a
small amount of code that runs and produces the problem.  A little
formatting is also a good practice.

--
Knute Snortum



Re: lyric start

2021-10-01 Thread Valentin Petzel
Hello,

Simply use \set includeGraceNotes = ##t in the lyrics to have lyrics set the 
grace notes. Please note that for technical reasons you need to set such 
changes one syllable before the first one that should have the change, which 
makes it quite impossible to use this when the first note has a grace note. In 
such cases you’d need to either \set Lyrics.includeGraceNote = ##t in a layout 
block or specify it with in on \new Lyrics \with { ... } statement.

Cheers,
Valentin

signature.asc
Description: This is a digitally signed message part.


Can't figure out breaks in ensemble scores

2021-10-01 Thread Carlos Martinez
Hi, 

I am not able to figure out how to manage the breaks in the score generated by 
different files. 

I have setup the different files or parts example: Violin I, II Cello and 
Viola.. 

The score appears when I use \include. But the way it lays it out it goes like 
this

Layout of the score….
2 measures
3 measures
1 long measure
4 measures

I would like to manage where the breaks are…

Help…

Thanks! :)








Re: Can't figure out breaks in ensemble scores

2021-10-01 Thread Ralph Palmer
Greetings, Carlos Martinez -

On Fri, Oct 1, 2021 at 4:08 PM Carlos Martinez <
car...@newsoundmusicstudio.com> wrote:

> Hi,
>
> I am not able to figure out how to manage the breaks in the score
> generated by different files.
>
> I have setup the different files or parts example: Violin I, II Cello and
> Viola..
>
> The score appears when I use \include. But the way it lays it out it goes
> like this
>
> Layout of the score….
> 2 measures
> 3 measures
> 1 long measure
> 4 measures
>
> I would like to manage where the breaks are…
>
> Help…
>
>
It's very helpful to supply a minimal working example (MWE) that shows the
problem you want solved.

Without seeing an MWE, I do have a question or two. Do you have explicit
breaks in the included (i.e., parts) files? If so, the combined score will,
I believe, put a break in the score wherever there is a break in an
included file. When I have done multiple part transcriptions, I have waited
until I combined the parts, saw where LilyPond put the breaks (or where I
thought I would want the breaks), then put \break at those points in the
topmost part. If you want different break points for the individual parts,
you may have to do some finagling - like set up separate \include files
(without breaks) for the parts to go into the full score. You may also be
able to use "tags", but that's beyond my ability.

Hope this helps,

Ralph


-- 
Ralph Palmer
Seattle
USA
(he, him, his)
palmer.r.vio...@gmail.com


Re: Can't figure out breaks in ensemble scores

2021-10-01 Thread Carlos Martinez
Thank you! That work! Although I am still having one part that need to figure 
out one space…. But the score looks great now! Thanks!


> On Oct 1, 2021, at 21:12, Ralph Palmer  wrote:
> 
> Greetings, Carlos Martinez -
> 
> On Fri, Oct 1, 2021 at 4:08 PM Carlos Martinez 
> mailto:car...@newsoundmusicstudio.com>> 
> wrote:
> Hi, 
> 
> I am not able to figure out how to manage the breaks in the score generated 
> by different files. 
> 
> I have setup the different files or parts example: Violin I, II Cello and 
> Viola.. 
> 
> The score appears when I use \include. But the way it lays it out it goes 
> like this
> 
> Layout of the score….
> 2 measures
> 3 measures
> 1 long measure
> 4 measures
> 
> I would like to manage where the breaks are…
> 
> Help…
> 
> 
> It's very helpful to supply a minimal working example (MWE) that shows the 
> problem you want solved.
> 
> Without seeing an MWE, I do have a question or two. Do you have explicit 
> breaks in the included (i.e., parts) files? If so, the combined score will, I 
> believe, put a break in the score wherever there is a break in an included 
> file. When I have done multiple part transcriptions, I have waited until I 
> combined the parts, saw where LilyPond put the breaks (or where I thought I 
> would want the breaks), then put \break at those points in the topmost part. 
> If you want different break points for the individual parts, you may have to 
> do some finagling - like set up separate \include files (without breaks) for 
> the parts to go into the full score. You may also be able to use "tags", but 
> that's beyond my ability.
> 
> Hope this helps,
> 
> Ralph
> 
> 
> -- 
> Ralph Palmer
> Seattle
> USA
> (he, him, his)
> palmer.r.vio...@gmail.com