Re: offset for lyrics does not offset the lyric hyphens

[Br. Gabriel-Marie | SSPX]

Sorry, I didn't realize embedded images didn't show.  I've 
attached them this time.


On 7/5/2016 9:10 PM, Br. Gabriel-Marie | SSPX wrote:

Mr. Morley,

I want to achieve the numbering to line up at the front of 
the lyrics.  The script that your other self created to 
number the stanza lines does not line them up - it does, 
indeed, get the numbering, but not the justification of 
the numbers.


That's why I haven't given up using /instrumentName /for 
the numbering. /instrumentName /will line up the numbers 
at the front.  (Problem with this, as I've mentioned, is 
that if the clef does not have the extra spacing provided 
by the three sharps in the key signature, then the lyrics 
can overlap the numbers.  )


You can see in the second attachment the difference here.  
If the words are longer then the numbers move and don't 
line up with the numbers on the next staff.



On 7/5/2016 2:08 PM, Thomas Morley wrote:

It's not clear to me at which position exactly?
Below (if any) the Clef, KeySignature/Cancellation, TimeSignature,
BarLine or else?
Righ-/center-/left-aligned?

Let's clear that first and then look for a method to avoid collisions.

Cheers,
   Harm




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: offset for lyrics does not offset the lyric hyphens

[Br. Gabriel-Marie | SSPX]

Mr. Morley,

I want to achieve the numbering to line up at the front of 
the lyrics.  The script that your other self created to 
number the stanza lines does not line them up - it does, 
indeed, get the numbering, but not the justification of the 
numbers.


That's why I haven't given up using /instrumentName /for the 
numbering. /instrumentName /will line up the numbers at the 
front.  (Problem with this, as I've mentioned, is that if 
the clef does not have the extra spacing provided by the 
three sharps in the key signature, then the lyrics can 
overlap the numbers.  )




You can see the difference here.  If the words are longer 
then the numbers move and don't line up with the numbers on 
the next staff.





On 7/5/2016 2:08 PM, Thomas Morley wrote:

It's not clear to me at which position exactly?
Below (if any) the Clef, KeySignature/Cancellation, TimeSignature,
BarLine or else?
Righ-/center-/left-aligned?

Let's clear that first and then look for a method to avoid collisions.

Cheers,
   Harm


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Installing on Ubuntu Studio

[David Wright]

On Tue 05 Jul 2016 at 08:36:00 (-0300), Marcelo Carneiro de Lima wrote:
> Thanks for the reply. When I say "Gui" I mean the same interface I have on
> Mac OS, for instance. I mean the possibility to work directly on Lilipond
> without Frescobaldi or Denemo, writing code on Lilypond's own text editor
> and compiling it in Lilypond as well. When I downloaded Lilipond for Linux
> and installed it, no icon for launch the software appears, no direct access
> to it, just by Frescobaldi. So, I cannot work only with Lilypond's
> software, I have to use others, like Denemo and Frescobaldi. Instead of the
> 'pond' icon, like when I installed it on Mac, I have...nothing.

You might perhaps want to post your question on the Ubuntu Studio
mailing list at https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
because this is really something that they will know more about.
LilyPond is not a GUI program; it runs from a command line using the
facilities of a shell to provide the different options. There are
countless Window Managers and Desktop Environments available in linux
and it's up to each one of them (or the distribution's packagers) to
decide how they deal with non-GUI executable binaries, whether through
icons, menus, or whatever.

If you're desperate to have an icon, then you could look at how your
desktop provides icons for other programs that are simple binaries.
Most low-level system programs will probably be like that.
Alternatively, your File Manager (whichever of the similarly countless
nummber) may provide File Associations so that double-clicking on a
.ly file will run LilyPond on it.

In the meantime, https://help.ubuntu.com/community/UbuntuStudio/UsingTheTerminal
shows how to get a terminal in Ubuntu Studio so that you can try issuing
the commands in the LP documentation examples.

Cheers,
David.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: slurs and repeats

[Martin Tarenskeen]

On Tue, 5 Jul 2016, Stephen MacNeil wrote:


Hi Martin

not sure if there is a better way but .


Thank you all for suggestions. I have now solved it with something like 
this (the \shape coordinates needs some finetuning but this is the 
general idea):




\version "2.19.44"

music = \relative {
  \partial 4
  c'8( d |
  \repeat volta 2 {
e4) g g4. a8 | g4 e c4. d8 |
  }
  \alternative {
{
  e4 e d c | d2.
  \shape #'((0 . 0) (0 . 0) (0 . -0.2) (2.5 . 0.5)) Slur
  c8( d) |
}
{ e4 e d d | c2. }
  }
  \bar "|." 
}


\score {
  \new Staff {
\music
  }
  \layout {}
}



P.S. This is not really the score I am working on, but just a tiny example 
for my own LilyPond education, to post in this list and to learn from the 
answers :-)


M.T.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: slurs and repeats

[Martin Tarenskeen]

On Tue, 5 Jul 2016, Marc Hohl wrote:


Am 05.07.2016 um 11:42 schrieb Martin Tarenskeen:
[...]

 I need a (partial) slur at the end of the first ending to indicate it's
 slurred back to the first e' of the repeated segment. Just like the
 pickup bar (\partial 4) is slurred to that same note.


Have you considered drawing the slur to the d and tweak its appearance so 
that it looks like a "half" slur?


Good idea. I have thought of that, but have to do some reading and 
experiments to do it.


--

MT

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: offset for lyrics does not offset the lyric hyphens

[Thomas Morley]

2016-07-05 20:11 GMT+02:00 Br. Gabriel-Marie | SSPX :
> Mr. Morley,  I thought I did open a new thread on the user list...

As you intended to report a bug, I wrongly assumed we're on the
bug-mailing-list.
Sorry for that.

> Well, I only recall one alternative and that is using Harm's (is that the
> same as Abraham?) stanza script.

Thomas Morley = Harm

Both are aliases, though ...

> But like I mentioned, the numbers end up
> in various places. Using instrumentName always puts them in the same place.
> I would be glad to avoid using instrumentName if I can get things to work
> out the way I want.  I want the numbers to appear in the same place on every
> line instead of varying positions.
>
> I'll start a new thread to ask Mr. Harm about fixing the number positions.

It's not clear to me at which position exactly?
Below (if any) the Clef, KeySignature/Cancellation, TimeSignature,
BarLine or else?
Righ-/center-/left-aligned?

Let's clear that first and then look for a method to avoid collisions.

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: offset for lyrics does not offset the lyric hyphens

[tisimst]

On Tue, Jul 5, 2016 at 12:43 PM, BGM [via Lilypond] <
ml-node+s1069038n192248...@n5.nabble.com> wrote:

> Mr. Morley,  I thought I did open a new thread on the user list...
>
> Well, I only recall one alternative and that is using Harm's (is that the
> same as Abraham?) stanza script.  But like I mentioned, the numbers end up
> in various places. Using instrumentName always puts them in the same
> place.  I would be glad to avoid using instrumentName if I can get things
> to work out the way I want.  I want the numbers to appear in the same place
> on every line instead of varying positions.
>
> I'll start a new thread to ask Mr. Harm about fixing the number positions.
>
> On 7/5/2016 12:38 PM, Thomas Morley wrote:
>
> Abraham already mentioned better alternative commands.
>
> I'm afraid you've confused two threads. This one was about lyric
text/hyphen collisions, or so I thought.

- Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/offset-for-lyrics-does-not-offset-the-lyric-hyphens-tp192237p192249.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: offset for lyrics does not offset the lyric hyphens

[Br. Gabriel-Marie | SSPX]

Mr. Morley,  I thought I did open a new thread on the user 
list...


Well, I only recall one alternative and that is using Harm's 
(is that the same as Abraham?) stanza script.  But like I 
mentioned, the numbers end up in various places. Using 
instrumentName always puts them in the same place.  I would 
be glad to avoid using instrumentName if I can get things to 
work out the way I want.  I want the numbers to appear in 
the same place on every line instead of varying positions.


I'll start a new thread to ask Mr. Harm about fixing the 
number positions.


On 7/5/2016 12:38 PM, Thomas Morley wrote:

Abraham already mentioned better alternative commands.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: offset for lyrics does not offset the lyric hyphens

[Thomas Morley]

2016-07-05 17:05 GMT+02:00 Br. Gabriel-Marie | SSPX :
>
> Hey!  I think I may have found a possible bug.
>
> So, I have been playing around with the use of instrumentName and 
> shortInstrumentName for uses of numbering lyrics.
>
> Now, when have a key signature that doesn't take up much horizontal space on 
> the bar then it is possible that the numbers may overlap some of the lyric 
> text.
>
> So you can use
> \override Lyrics.LyricText #'extra-offset = #'(2 . 0)
>
> to move the lyric text around so that it is out of the way of the numbers.
>
> However, this causes a few problems:
> 1.  Since it is an offset it does not affect how the text lines up with the 
> music notes - but I think this is correct procedure for an offset.
> 2. And this is the bug (I think) - hyphenated lyrics move, but their -- 
> hyphens do not move with them.  So the offset causes the lyric words to 
> overlap their hyphens.

Since this is exactly how 'extra-offset is supposed to work: no bug.
Abraham already mentioned better alternative commands.
In general: you can't go wrong regarding 'extra-offset as a last, last
resort. I _always_ try to avoid it.

>
> All of that having been said, is there a way to move the text along with the 
> notes?  In other words, can I push the music with its lyrics to the right a 
> little bit somehow to get space?
>
> (I'm still playing with Harm's stanza trick; but I like the instrumentName 
> method better because it keeps the numbers in the same place on every bar and 
> doesn't shift position on account of word lengths)

Please open new thread(s) on the user-list, so that it is better
searchable in the archives later on.
Ofcourse a minimal example including the lily-version, showing the
problem is always conditio sine qua non.

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ly:parser-parse-string again

[David Kastrup]

Urs Liska  writes:

> Am 05.07.2016 um 18:01 schrieb David Kastrup:
>
>> The alternative is cloning a fresh parser.  There might be some
>> incentive to carry over the current notename language automatically.
>> But it does not make sense to carry over the whole state stack when
>> cloning.  So what to do if we are not actually in notemode currently?
>
> Makes sense.
> But actually one would rather expect the default to be active just like
> with regular files.

Regular files don't get a fresh parser.  They get the parser in the
state where \maininput in ly/init.ly leaves it.

You'll notice that ly/init.ly sets up the default notename language
before that.

I'm not saying that this is all fabulous.  But in the current state,
including/interpreting LilyPond files via Scheme code is more or less
playing around with internals, and the internals have behavior tied to
LilyPond's architecture more than to user expectations.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: slurs and repeats

[Marc Hohl]

Am 05.07.2016 um 11:42 schrieb Martin Tarenskeen:
[...]

I need a (partial) slur at the end of the first ending to indicate it's
slurred back to the first e' of the repeated segment. Just like the
pickup bar (\partial 4) is slurred to that same note.


Have you considered drawing the slur to the d and tweak its appearance 
so that it looks like a "half" slur?


Marc





___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ly:parser-parse-string again

[Urs Liska]

Am 05.07.2016 um 18:01 schrieb David Kastrup:
> Urs Liska  writes:
>
>> Am 05.07.2016 um 16:00 schrieb David Kastrup:
>>> Urs Liska  writes:
>>>
 Well, first of all I wouldn't have thought of it, so I felt very
 embarrassed at first. But actually the problem is that my function is
 kind of an adaptor. It includes a number of files (i.e. all from a
 directory that match a pattern), and each file defines the same
 variables (e.g. \music, \lyricText and \bcFigures). The function wants
 then to either rename them so they can independently be used in a score
 or rather store them in a tree where the function building the score
 will later fetch them from.

 So, within my function I have to iterate over the list of files, include
 them and process the variables that are defined within the files.
>>> So build a string that includes the list of files and processes the
>>> variables.
>>>
>> Argh.
>> Yes, it's tedious to build that string, even within a loop.
> Use
>
> (with-output-to-string
>   (lambda ()
> ...
>
> for building the string.  That makes the control flow of your program
> independent from the structure of the string you piece together.

Thanks for that pointer. Indeed it makes the code much cleaner.

For anybody interested, the results are visible at
https://git.openlilylib.org/bfsc/kayser/blob/karlsruhe/includes/lib/file-handling.ily#L124

>
>> But it works, and the include works as well.  Thanks for the pointers
>> - I wouldn't have thought in that direction because it would have felt
>> like just another level of indirction although it is actually the
>> opposite.
> The alternative is cloning a fresh parser.  There might be some
> incentive to carry over the current notename language automatically.
> But it does not make sense to carry over the whole state stack when
> cloning.  So what to do if we are not actually in notemode currently?

Makes sense.
But actually one would rather expect the default to be active just like
with regular files.
I don't specify a language in the regular .ly file, so it would be
natural to have Dutch as the default in include files as well.
But the other approach is significantly cleaner anyway, so I'm happy now.

Urs

>
> That's all in a bit of an icky state.
>


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: slurs and repeats

[Stephen MacNeil]

Hi Martin

not sure if there is a better way but .
Do you mean like

\relative {

\partial 4

c'8( d | % this slur is OK

\repeat volta 2 {

e4) g g4. a8 | g4 e c4. d8 |

}

\alternative {

{ e4 e d c | d2. c8 d -\tweak control-points #'((-2 . -3.8) (-1 . -4.5) (0
. -4.5) (1 . -4)) ( <> ) | } % this slur is not allowed?

{ e4 e d d | c2. r4 } % ) added after e4

}\break

e -\tweak control-points #'((-1 . -3) (-.5 . -3.2) (0 . -3.4) (.7 . -2.8))
( <> ) r2.|

}


I didn't bother to make it look nice.. you have to do some work :)


all this and more can be found reading the docs!

http://lilypond.org/doc/v2.18/Documentation/notation/modifying-shapes

HTH
Stephen
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ly:parser-parse-string again

[David Kastrup]

Urs Liska  writes:

> Am 05.07.2016 um 16:00 schrieb David Kastrup:
>> Urs Liska  writes:
>>
>>> Well, first of all I wouldn't have thought of it, so I felt very
>>> embarrassed at first. But actually the problem is that my function is
>>> kind of an adaptor. It includes a number of files (i.e. all from a
>>> directory that match a pattern), and each file defines the same
>>> variables (e.g. \music, \lyricText and \bcFigures). The function wants
>>> then to either rename them so they can independently be used in a score
>>> or rather store them in a tree where the function building the score
>>> will later fetch them from.
>>>
>>> So, within my function I have to iterate over the list of files, include
>>> them and process the variables that are defined within the files.
>> So build a string that includes the list of files and processes the
>> variables.
>>
>
> Argh.
> Yes, it's tedious to build that string, even within a loop.

Use

(with-output-to-string
  (lambda ()
...

for building the string.  That makes the control flow of your program
independent from the structure of the string you piece together.

> But it works, and the include works as well.  Thanks for the pointers
> - I wouldn't have thought in that direction because it would have felt
> like just another level of indirction although it is actually the
> opposite.

The alternative is cloning a fresh parser.  There might be some
incentive to carry over the current notename language automatically.
But it does not make sense to carry over the whole state stack when
cloning.  So what to do if we are not actually in notemode currently?

That's all in a bit of an icky state.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ly:parser-parse-string again

[Urs Liska]

Am 05.07.2016 um 16:00 schrieb David Kastrup:
> Urs Liska  writes:
>
>> Well, first of all I wouldn't have thought of it, so I felt very
>> embarrassed at first. But actually the problem is that my function is
>> kind of an adaptor. It includes a number of files (i.e. all from a
>> directory that match a pattern), and each file defines the same
>> variables (e.g. \music, \lyricText and \bcFigures). The function wants
>> then to either rename them so they can independently be used in a score
>> or rather store them in a tree where the function building the score
>> will later fetch them from.
>>
>> So, within my function I have to iterate over the list of files, include
>> them and process the variables that are defined within the files.
> So build a string that includes the list of files and processes the
> variables.
>

Argh.
Yes, it's tedious to build that string, even within a loop. But it
works, and the include works as well.
Thanks for the pointers - I wouldn't have thought in that direction
because it would have felt like just another level of indirction
although it is actually the opposite.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: offset for lyrics does not offset the lyric hyphens

[tisimst]

On Tue, Jul 5, 2016 at 9:26 AM, tisimst [via Lilypond] <
ml-node+s1069038n192239...@n5.nabble.com> wrote:

> Also, the hyphen is controlled with the Lyrics.LyricHyphen grob. Likewise,
> the underscore extender is controlled by the Lyrics.LyricExtender grob.
>

And I know that you want to keep all \overrides in a \layout block, but a
positional \override isn't really appropriate there unless you really meant
to apply it globally, which I consider unlikely. Rather, it should really
only be used at the individual moment(s) needed using the \once command.

Just some thoughts,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/offset-for-lyrics-does-not-offset-the-lyric-hyphens-tp192237p192240.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: offset for lyrics does not offset the lyric hyphens

[tisimst]

Also, the hyphen is controlled with the Lyrics.LyricHyphen grob. Likewise,
the underscore extender is controlled by the Lyrics.LyricExtender grob.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/offset-for-lyrics-does-not-offset-the-lyric-hyphens-tp192237p192239.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: offset for lyrics does not offset the lyric hyphens

[tisimst]

On Tue, Jul 5, 2016 at 9:12 AM, BGM [via Lilypond] <
ml-node+s1069038n192237...@n5.nabble.com> wrote:

> ...SNIP...
> \override Lyrics.LyricText #'extra-offset = #'(2 . 0)
> ...SNIP...


FYI, using 'extra-offset will ONLY affect the grob to which it applies and
nothing else. Try using 'X-offset, 'self-alignment-X or 'parent-alignment-X
instead.

HTH,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/offset-for-lyrics-does-not-offset-the-lyric-hyphens-tp192237p192238.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

offset for lyrics does not offset the lyric hyphens

[Br. Gabriel-Marie | SSPX]

Hey!  I think I may have found a possible bug.

So, I have been playing around with the use of 
instrumentName and shortInstrumentName for uses of numbering 
lyrics.


Now, when have a key signature that doesn't take up much 
horizontal space on the bar then it is possible that the 
numbers may overlap some of the lyric text.


So you can use
\override Lyrics.LyricText #'extra-offset = #'(2 . 0)

to move the lyric text around so that it is out of the way 
of the numbers.


However, this causes a few problems:
1.  Since it is an offset it does not affect how the text 
lines up with the music notes - but I think this is correct 
procedure for an offset.
2. And this is the bug (I think) - hyphenated lyrics move, 
but their -- hyphens do not move with them.  So the offset 
causes the lyric words to overlap their hyphens.



You can see the overlap here in wo -- rds, wi -- th, and 
stanz -- as


I have attached a minimal example.

All of that having been said, is there a way to move the 
text along with the notes?  In other words, can I push the 
music with its lyrics to the right a little bit somehow to 
get space?


(I'm still playing with Harm's stanza trick; but I like the 
instrumentName method better because it keeps the numbers in 
the same place on every bar and doesn't shift position on 
account of word lengths)

\header {
title = "Instrument Name with Offset Test"
}




verses = \new Voice = "verses" \relative c'' {
\time 4/4
\key c \major
a4 b4 c4 d4 | e4 d4 f2  \bar "||"
}


wordsOne = \new Lyrics  \with{ instrumentName= "1" shortInstrumentName= "1"} \lyricsto "verses" {
 Here are some wo -- rds to sing
}
wordsTwo = \new Lyrics  \with{ instrumentName= "2" shortInstrumentName= "2"} \lyricsto "verses" {
And line up wi -- th them -- selves
}
wordsThree = \new Lyrics  \with{ instrumentName= "3" shortInstrumentName= "3"} \lyricsto "verses" {
See the stanz -- as line up in place
}

\score {
		<<
\new Staff{   \verses }
   \wordsOne
\wordsTwo
   \wordsThree
		>>
	\layout {
		\override Lyrics.LyricText #'extra-offset = #'(2 . 0)%  allows the Lyric text's starting point to be shifted left or right
	}
}



offset test.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ly:parser-parse-string again

[David Kastrup]

Urs Liska  writes:

> Well, first of all I wouldn't have thought of it, so I felt very
> embarrassed at first. But actually the problem is that my function is
> kind of an adaptor. It includes a number of files (i.e. all from a
> directory that match a pattern), and each file defines the same
> variables (e.g. \music, \lyricText and \bcFigures). The function wants
> then to either rename them so they can independently be used in a score
> or rather store them in a tree where the function building the score
> will later fetch them from.
>
> So, within my function I have to iterate over the list of files, include
> them and process the variables that are defined within the files.

So build a string that includes the list of files and processes the
variables.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ly:parser-parse-string again

[David Kastrup]

Urs Liska  writes:

> Am 05.07.2016 um 15:15 schrieb David Kastrup:
>> Urs Liska  writes:
>>
>>> I'm once more struggling with the commands to include files within
>>> Scheme functions.
>>>
>>> In the attached .ily files one defines a music expression while the
>>> other uses it in a Staff definition.
>>>
>>>
>>> However, this time I get strange errors with the parse-string function
>>> as that doesn't even seem to be able to parse the first file properly.
>>> The first error is
>>>
>>> levelOne.ily:3:19 <0>: error: wrong type for argument 2. Expecting
>>> music, found "c"
>>>
>>> music = \relative
>>>
>>> c' { c }
>>>
>>> followed by numerous consecutive errors that are probably neglectable.
>>>
>>> I would very much appreciate any further clarification and assistance as
>>> I really don't have a clue how to proceed.
>> Try selecting a note name language.
>
> This seems to do the trick, although it seems hacky to require explicit
> language in all include files.

Creating a blank parser for processing a file in its own semantic nest
is hacky.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ly:parser-parse-string again

[Urs Liska]

Am 05.07.2016 um 15:15 schrieb David Kastrup:
> Urs Liska  writes:
>
>> I'm once more struggling with the commands to include files within
>> Scheme functions.
>>
>> In the attached .ily files one defines a music expression while the
>> other uses it in a Staff definition.
>>
>>
>> However, this time I get strange errors with the parse-string function
>> as that doesn't even seem to be able to parse the first file properly.
>> The first error is
>>
>> levelOne.ily:3:19 <0>: error: wrong type for argument 2. Expecting
>> music, found "c"
>>
>> music = \relative
>>
>> c' { c }
>>
>> followed by numerous consecutive errors that are probably neglectable.
>>
>> I would very much appreciate any further clarification and assistance as
>> I really don't have a clue how to proceed.
> Try selecting a note name language.
>

This seems to do the trick, although it seems hacky to require explicit
language in all include files.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ly:parser-parse-string again

[Urs Liska]

Am 05.07.2016 um 15:27 schrieb David Kastrup:
> Urs Liska  writes:
>
>> Hi,
>>
>> I'm once more struggling with the commands to include files within
>> Scheme functions.
>>
>> In the attached .ily files one defines a music expression while the
>> other uses it in a Staff definition.
>>
>> I can happily make that work using regular \includes or by calling
>> ly:parser-include-string twice. But I need to wrap this into a Scheme
>> function to include multiple files from within a function and process
>> the results (the music expressions from the files) within the same function.
>>
>> I am not surprised that the second approach (using
>> ly:parser-include-string twice within the function) doesn't work. Last
>> time this question popped up I learned that any definition from inside
>> the included file will only be visible after the function has returned.
>> (uncomment second example to see it "in action").
> Perhaps you should unlearn that.  It's nonsensical.  The problem rather
> is that ly:parser-include-string pushes a string on the input stack, so
> your includes are processed in reversed order.
>
> Why would you even do multiple ly:parser-include-string calls in one
> function instead of building _one_ string and including that?
>

Well, first of all I wouldn't have thought of it, so I felt very
embarrassed at first. But actually the problem is that my function is
kind of an adaptor. It includes a number of files (i.e. all from a
directory that match a pattern), and each file defines the same
variables (e.g. \music, \lyricText and \bcFigures). The function wants
then to either rename them so they can independently be used in a score
or rather store them in a tree where the function building the score
will later fetch them from.

So, within my function I have to iterate over the list of files, include
them and process the variables that are defined within the files.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ly:parser-parse-string again

[David Kastrup]

Urs Liska  writes:

> Hi,
>
> I'm once more struggling with the commands to include files within
> Scheme functions.
>
> In the attached .ily files one defines a music expression while the
> other uses it in a Staff definition.
>
> I can happily make that work using regular \includes or by calling
> ly:parser-include-string twice. But I need to wrap this into a Scheme
> function to include multiple files from within a function and process
> the results (the music expressions from the files) within the same function.
>
> I am not surprised that the second approach (using
> ly:parser-include-string twice within the function) doesn't work. Last
> time this question popped up I learned that any definition from inside
> the included file will only be visible after the function has returned.
> (uncomment second example to see it "in action").

Perhaps you should unlearn that.  It's nonsensical.  The problem rather
is that ly:parser-include-string pushes a string on the input stack, so
your includes are processed in reversed order.

Why would you even do multiple ly:parser-include-string calls in one
function instead of building _one_ string and including that?

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ly:parser-parse-string again

[David Kastrup]

Urs Liska  writes:

> I'm once more struggling with the commands to include files within
> Scheme functions.
>
> In the attached .ily files one defines a music expression while the
> other uses it in a Staff definition.
>
> I can happily make that work using regular \includes or by calling
> ly:parser-include-string twice. But I need to wrap this into a Scheme
> function to include multiple files from within a function and process
> the results (the music expressions from the files) within the same function.
>
> I am not surprised that the second approach (using
> ly:parser-include-string twice within the function) doesn't work. Last
> time this question popped up I learned that any definition from inside
> the included file will only be visible after the function has returned.
> (uncomment second example to see it "in action").
>
> So I thought I had to use ly:parser-parse-string together with
> ly:parser-clone to make the definitions available earlier, and in
> another context this worked
> (https://github.com/openlilylib/oll-core/blob/master/oll-core.ily#L59).
>
> However, this time I get strange errors with the parse-string function
> as that doesn't even seem to be able to parse the first file properly.
> The first error is
>
> levelOne.ily:3:19 <0>: error: wrong type for argument 2. Expecting
> music, found "c"
>
> music = \relative
>
> c' { c }
>
> followed by numerous consecutive errors that are probably neglectable.
>
> I would very much appreciate any further clarification and assistance as
> I really don't have a clue how to proceed.

Try selecting a note name language.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

ly:parser-parse-string again

[Urs Liska]

Hi,

I'm once more struggling with the commands to include files within
Scheme functions.

In the attached .ily files one defines a music expression while the
other uses it in a Staff definition.

I can happily make that work using regular \includes or by calling
ly:parser-include-string twice. But I need to wrap this into a Scheme
function to include multiple files from within a function and process
the results (the music expressions from the files) within the same function.

I am not surprised that the second approach (using
ly:parser-include-string twice within the function) doesn't work. Last
time this question popped up I learned that any definition from inside
the included file will only be visible after the function has returned.
(uncomment second example to see it "in action").

So I thought I had to use ly:parser-parse-string together with
ly:parser-clone to make the definitions available earlier, and in
another context this worked
(https://github.com/openlilylib/oll-core/blob/master/oll-core.ily#L59).

However, this time I get strange errors with the parse-string function
as that doesn't even seem to be able to parse the first file properly.
The first error is

levelOne.ily:3:19 <0>: error: wrong type for argument 2. Expecting
music, found "c"

music = \relative

c' { c }

followed by numerous consecutive errors that are probably neglectable.

I would very much appreciate any further clarification and assistance as
I really don't have a clue how to proceed.

Urs

PS: The actual context is
https://git.openlilylib.org/bfsc/kayser/blob/score/includes/lib/file-handling.ily#L124
(the unfinished stuff starting from L. 143), but I'm not sure if that's
sufficiently retraceable from that page)

\version "2.19.43"

% Including them one after another works fine
%%{

#(ly:parser-include-string "\\include \"levelOne.ily\"")
#(ly:parser-include-string "\\include \"levelTwo.ily\"")

%}

% Wrapping the includes in a Scheme function doesn't work
% because \music will only be visible when the expression
% has been fully evaluated (i.e. after leaving the function).
%{

includeBoth =
#(define-void-function ()()
   (ly:parser-include-string "\\include \"levelOne.ily\"")
   (ly:parser-include-string "\\include \"levelTwo.ily\""))

\includeBoth

%}


% Using ly:parser-parse-string with a parser clone doesn't
% work either because it seems not to be able to parse
% the (first) file in the first place.
%{

includeBoth =
#(define-void-function ()()
   (ly:parser-parse-string (ly:parser-clone)
 "\\include \"levelOne.ily\"")
   (ly:parser-parse-string (ly:parser-clone)
 "\\include \"levelTwo.ily\""))

\includeBoth

%}

\version "2.19.43"

music = \relative c' { c }\version "2.19.43"

\new Staff \music
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Installing on Ubuntu Studio

[Urs Liska]

This may also be useful for clarifying (sorry for the somewhat cryptic
location, but that is "unmerged" content:

https://bookbranches.openlilylib.org/showcase/toolchain/index.html


Am 05.07.2016 um 14:11 schrieb Andrew Bernard:
> Hi Marcelo,
>
> I see. The so called GUI on the mac is just LilyPad, a very crude
> basic text editor which also allows you to run the lilypond command.
> It can hardly be described as a GUI platform for lilypond.
>
> This tool is not available on Linux systems precisely because Linux
> users have a superabundance of powerful text editors available to them
> such as emacs, vi, and gedit and things like Atom nowadays. Using
> emacs and the command line on linux is a fast, powerful and effective
> way of working. Urs Liska has written extensively on the power and
> advantage of a full text based workflow for engraving.
>
> As far as Frescobaldi goes, it is difficult to imagine anybody
> objecting to it. It offers a reasonable text editor, but more
> importantly point and click in the PDF which takes you directly to the
> location in the source code file that produced that object (which by
> the way you can still do with emacs and so on anyway,s ince that is a
> lilypond feature and not a Frescobaldi one). Also, highlighting source
> code allows you to jump to tha point in the score immediately. I
> prodcude extraordinarily dense scores for colleagues of the New
> Complexity School, and without Frescobaldi I would be utterly lost.
>
> Hope this my be useful.
>
> Andrew
>
>
>
>
> On 5 July 2016 at 9:36:00 PM, Marcelo Carneiro de Lima
> (marcelo.arc...@gmail.com ) wrote:
>
>> Thanks for the reply. When I say "Gui" I mean the same interface I
>> have on Mac OS, for instance. I mean the possibility to work directly
>> on Lilipond without Frescobaldi or Denemo, writing code on Lilypond's
>> own text editor and compiling it in Lilypond as well. When I
>> downloaded Lilipond for Linux and installed it, no icon for launch
>> the software appears, no direct access to it, just by Frescobaldi.
>> So, I cannot work only with Lilypond's software, I have to use
>> others, like Denemo and Frescobaldi. Instead of the 'pond' icon, like
>> when I installed it on Mac, I have...nothing.
>>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Installing on Ubuntu Studio

[Andrew Bernard]

Hi Marcelo,

I see. The so called GUI on the mac is just LilyPad, a very crude basic
text editor which also allows you to run the lilypond command. It can
hardly be described as a GUI platform for lilypond.

This tool is not available on Linux systems precisely because Linux users
have a superabundance of powerful text editors available to them such as
emacs, vi, and gedit and things like Atom nowadays. Using emacs and the
command line on linux is a fast, powerful and effective way of working. Urs
Liska has written extensively on the power and advantage of a full text
based workflow for engraving.

As far as Frescobaldi goes, it is difficult to imagine anybody objecting to
it. It offers a reasonable text editor, but more importantly point and
click in the PDF which takes you directly to the location in the source
code file that produced that object (which by the way you can still do with
emacs and so on anyway,s ince that is a lilypond feature and not a
Frescobaldi one). Also, highlighting source code allows you to jump to tha
point in the score immediately. I prodcude extraordinarily dense scores for
colleagues of the New Complexity School, and without Frescobaldi I would be
utterly lost.

Hope this my be useful.

Andrew




On 5 July 2016 at 9:36:00 PM, Marcelo Carneiro de Lima (
marcelo.arc...@gmail.com) wrote:

Thanks for the reply. When I say "Gui" I mean the same interface I have on
Mac OS, for instance. I mean the possibility to work directly on Lilipond
without Frescobaldi or Denemo, writing code on Lilypond's own text editor
and compiling it in Lilypond as well. When I downloaded Lilipond for Linux
and installed it, no icon for launch the software appears, no direct access
to it, just by Frescobaldi. So, I cannot work only with Lilypond's
software, I have to use others, like Denemo and Frescobaldi. Instead of the
'pond' icon, like when I installed it on Mac, I have...nothing.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Installing on Ubuntu Studio

[Blöchl Bernhard]

"... I mean the possibility to work directly
on Lilipond without Frescobaldi or Denemo, writing code on Lilypond's
own text editor and compiling it in Lilypond as well ..."

http://lilypond.org/doc/v2.18/Documentation/usage/command_002dline-usage


Am 05.07.2016 13:44, schrieb Phil Holmes:


I assume the editor that ships with the Mac is the little LilyPad
editor. This is a very rudimentary text editor, and can be replaced
with any other text editor of your choice. On my Linux system I use
gedit, but there are many other editors that you can use.

--
Phil Holmes

- Original Message -
FROM: Marcelo Carneiro de Lima
TO: Andrew Bernard
CC: lilypond-user@gnu.org
SENT: Tuesday, July 05, 2016 12:36 PM
SUBJECT: Re: Installing on Ubuntu Studio

Thanks for the reply. When I say "Gui" I mean the same interface I
have on Mac OS, for instance. I mean the possibility to work directly
on Lilipond without Frescobaldi or Denemo, writing code on Lilypond's
own text editor and compiling it in Lilypond as well. When I
downloaded Lilipond for Linux and installed it, no icon for launch the
software appears, no direct access to it, just by Frescobaldi. So, I
cannot work only with Lilypond's software, I have to use others, like
Denemo and Frescobaldi. Instead of the 'pond' icon, like when I
installed it on Mac, I have...nothing.
Thanks
Best Regards
Marcelo

Em segunda-feira, 4 de julho de 2016, Andrew Bernard
 escreveu:

Hi Marcelo,

There is no GUI for lilypond on Linux, only command line, as per any
UNIX tool. Frescobaldi is a fine GUI environment many find.

Andrew

On 5 July 2016 at 9:20:23 AM, Marcelo Carneiro de Lima
(marcelo.arc...@gmail.com) wrote:

Hi,
Despite the fact that the installations seemed to be fine, I cannot
access Lilypond Gui (texts, menus, etc).

--

MARCELO CARNEIRO
(21) 9382-3621
(21) 3497-0193
Skype: Carneiro3729

-

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Installing on Ubuntu Studio

[Phil Holmes]

I assume the editor that ships with the Mac is the little LilyPad editor.  This 
is a very rudimentary text editor, and can be replaced with any other text 
editor of your choice.  On my Linux system I use gedit, but there are many 
other editors that you can use.

--
Phil Holmes


  - Original Message - 
  From: Marcelo Carneiro de Lima 
  To: Andrew Bernard 
  Cc: lilypond-user@gnu.org 
  Sent: Tuesday, July 05, 2016 12:36 PM
  Subject: Re: Installing on Ubuntu Studio


  Thanks for the reply. When I say "Gui" I mean the same interface I have on 
Mac OS, for instance. I mean the possibility to work directly on Lilipond 
without Frescobaldi or Denemo, writing code on Lilypond's own text editor and 
compiling it in Lilypond as well. When I downloaded Lilipond for Linux and 
installed it, no icon for launch the software appears, no direct access to it, 
just by Frescobaldi. So, I cannot work only with Lilypond's software, I have to 
use others, like Denemo and Frescobaldi. Instead of the 'pond' icon, like when 
I installed it on Mac, I have...nothing.
  Thanks
  Best Regards
  Marcelo 

  Em segunda-feira, 4 de julho de 2016, Andrew Bernard 
 escreveu:

Hi Marcelo,


There is no GUI for lilypond on Linux, only command line, as per any UNIX 
tool. Frescobaldi is a fine GUI environment many find.


Andrew






On 5 July 2016 at 9:20:23 AM, Marcelo Carneiro de Lima 
(marcelo.arc...@gmail.com) wrote:

  Hi,

  Despite the fact that the installations seemed to be fine, I cannot 
access Lilypond Gui (texts, menus, etc). 


  -- 

  Marcelo Carneiro
  (21) 9382-3621
  (21) 3497-0193
  Skype: Carneiro3729




--


  ___
  lilypond-user mailing list
  lilypond-user@gnu.org
  https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Installing on Ubuntu Studio

[Urs Liska]

This editor is just that, a text editor.

If yiu don't want to use a bigger solution you can always use your OS's default 
text editor - and the command line to start compilation. 

HTH
Urs

Am 5. Juli 2016 13:36:00 MESZ, schrieb Marcelo Carneiro de Lima 
:
>Thanks for the reply. When I say "Gui" I mean the same interface I have
>on
>Mac OS, for instance. I mean the possibility to work directly on
>Lilipond
>without Frescobaldi or Denemo, writing code on Lilypond's own text
>editor
>and compiling it in Lilypond as well. When I downloaded Lilipond for
>Linux
>and installed it, no icon for launch the software appears, no direct
>access
>to it, just by Frescobaldi. So, I cannot work only with Lilypond's
>software, I have to use others, like Denemo and Frescobaldi. Instead of
>the
>'pond' icon, like when I installed it on Mac, I have...nothing.
>Thanks
>Best Regards
>Marcelo
>
>Em segunda-feira, 4 de julho de 2016, Andrew Bernard <
>andrew.bern...@gmail.com> escreveu:
>
>> Hi Marcelo,
>>
>> There is no GUI for lilypond on Linux, only command line, as per any
>UNIX
>> tool. Frescobaldi is a fine GUI environment many find.
>>
>> Andrew
>>
>>
>>
>> On 5 July 2016 at 9:20:23 AM, Marcelo Carneiro de Lima (
>> marcelo.arc...@gmail.com
>> ) wrote:
>>
>> Hi,
>> Despite the fact that the installations seemed to be fine, I cannot
>access
>> Lilypond Gui (texts, menus, etc).
>>
>>
>
>-- 
>*Marcelo Carneiro*
>(21) 9382-3621
>(21) 3497-0193
>Skype: Carneiro3729
>
>
>
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Installing on Ubuntu Studio

[Marcelo Carneiro de Lima]

Thanks for the reply. When I say "Gui" I mean the same interface I have on
Mac OS, for instance. I mean the possibility to work directly on Lilipond
without Frescobaldi or Denemo, writing code on Lilypond's own text editor
and compiling it in Lilypond as well. When I downloaded Lilipond for Linux
and installed it, no icon for launch the software appears, no direct access
to it, just by Frescobaldi. So, I cannot work only with Lilypond's
software, I have to use others, like Denemo and Frescobaldi. Instead of the
'pond' icon, like when I installed it on Mac, I have...nothing.
Thanks
Best Regards
Marcelo

Em segunda-feira, 4 de julho de 2016, Andrew Bernard <
andrew.bern...@gmail.com> escreveu:

> Hi Marcelo,
>
> There is no GUI for lilypond on Linux, only command line, as per any UNIX
> tool. Frescobaldi is a fine GUI environment many find.
>
> Andrew
>
>
>
> On 5 July 2016 at 9:20:23 AM, Marcelo Carneiro de Lima (
> marcelo.arc...@gmail.com
> ) wrote:
>
> Hi,
> Despite the fact that the installations seemed to be fine, I cannot access
> Lilypond Gui (texts, menus, etc).
>
>

-- 
*Marcelo Carneiro*
(21) 9382-3621
(21) 3497-0193
Skype: Carneiro3729
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: NR 2.10.2 - arabic key signatures

[Blöchl Bernhard]

Am 05.07.2016 11:43, schrieb Federico Bruni:

Il giorno lun 4 lug 2016 alle 12:10, Carl Sorensen
 ha scritto:



On 7/1/16 5:08 AM, "Federico Bruni"  wrote:


Hi all

In the following paragraph, taken from
http://lilypond.org/doc/v2.19/Documentation/notation/arabic-music#arabic-k
ey-signatures


 Other maqams in the same bayati group, as shown in the table below:
 (bayati, hussaini, saba, and ushaq) can be indicated in the same 
way.

 These are all variations of the base and most common maqam in the
 group, which is bayati. They usually differ from the base maqam in
 their upper tetrachords, or certain flow details that don¹t change
 their fundamental nature, as siblings.


The last sentence seems quite obscure to me. What are "flow details"?
What are "siblings" in this context?


I think that "flow details" and "siblings" are arabic music terms, 
rather

than LilyPond internal terms.


ok



See https://en.wikipedia.org/wiki/Arabic_maqam

Although, I can't really understand that wikipedia page either.  It
appears that maqams are so different from traditional western music 
that

the terms are very difficult to relate.


In this page:
http://www.maqamworld.com/maqamat.html

it talks about "melodic flow":

Another peculiarity of maqamat is that the same note is not always 
played with the same exact pitch. The pitch may vary slightly, 
depending on the __melodic flow__ and what other notes are played 
before and after that note. The idea behind this effect is to round 
sharp corners in the melody by drawing the furthest notes nearer. This 
effect is sometimes called the law of attraction or gravity, and is 
common in other musical traditions (e.g. in Byzantine music).


Perhaps the doc is implicitely about "melodic flow details"?
Then what would "siblings" mean in that context?




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


That text of the manual is not a description of any real feature of 
lilypond, but describes the nature of arabic/turkish music in a very 
superficial form. Simply ignore it, it will not help you in any form - 
that is my personal opinion.


Arabic music/notation is different, as the arabic scale is 24-tet, 
whereas the Ottoman classical music uses a 53-tet scale. You easily find 
someone saying that is nonsense ... I simply agree, as it is 
oversimplified as well.


There had been some suggestions to extend lilypond for correct notation 
of arabic/turkish music. You might find mails about that attempts in the 
archive. But there was no real interest to add this feature to lilypond.


Regards

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: another slur problem

[David Kastrup]

Martin Tarenskeen  writes:

> On Tue, 5 Jul 2016, David Kastrup wrote:
>
 Probably GCC6.  What does ldd /usr/bin/lilypond state?
>>>
>>> See attachment.
>>
>> Huh.  The library version numbers (including C++ library as far as I can
>> tell) seem to match those of my system pretty closely.  Can you run this
>> under the debugger and get a traceback of the segfault?
>>
>> Basically
>>
>> gdb64 lilypond
>> run /tmp/bad-file.ly
>> backtrace
>>
>> It's gdb64 on my rather promiscous system.  Could be just gdb on yours.
>>
>
> See attached gdb.txt

Starting program: /usr/bin/lilypond slurtest2.ly
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x5561fa4f in Grob::get_offset (this=this@entry=0x0, 
a=a@entry=X_AXIS) at grob.cc:400
400   if (dim_cache_[a].offset_)
#0  0x5561fa4f in Grob::get_offset(Axis) const (this=this@entry=0x0, 
a=a@entry=X_AXIS) at grob.cc:400
#1  0x5561fb48 in Grob::relative_coordinate(Grob const*, Axis) const 
(this=0x0, refp=0x5619f290, a=X_AXIS) at grob.cc:341
#2  0x5561fb6e in Grob::relative_coordinate(Grob const*, Axis) const 
(this=0x5619eda0, refp=0x5619f290, a=X_AXIS) at grob.cc:345

Looks rather like

https://sourceforge.net/p/testlilyissues/issues/4814/

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: another slur problem

[Martin Tarenskeen]

On Tue, 5 Jul 2016, David Kastrup wrote:


Probably GCC6.  What does ldd /usr/bin/lilypond state?


See attachment.


Huh.  The library version numbers (including C++ library as far as I can
tell) seem to match those of my system pretty closely.  Can you run this
under the debugger and get a traceback of the segfault?

Basically

gdb64 lilypond
run /tmp/bad-file.ly
backtrace

It's gdb64 on my rather promiscous system.  Could be just gdb on yours.



See attached gdb.txt

--

MartinStarting program: /usr/bin/lilypond slurtest2.ly
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x5561fa4f in Grob::get_offset (this=this@entry=0x0, 
a=a@entry=X_AXIS) at grob.cc:400
400   if (dim_cache_[a].offset_)
#0  0x5561fa4f in Grob::get_offset(Axis) const (this=this@entry=0x0, 
a=a@entry=X_AXIS) at grob.cc:400
#1  0x5561fb48 in Grob::relative_coordinate(Grob const*, Axis) const 
(this=0x0, refp=0x5619f290, a=X_AXIS) at grob.cc:341
#2  0x5561fb6e in Grob::relative_coordinate(Grob const*, Axis) const 
(this=0x5619eda0, refp=0x5619f290, a=X_AXIS) at grob.cc:345
#3  0x5561fb6e in Grob::relative_coordinate(Grob const*, Axis) const 
(this=0x56046260, refp=0x5619f290, a=X_AXIS) at grob.cc:345
#4  0x5561fb6e in Grob::relative_coordinate(Grob const*, Axis) const 
(this=0x56046df0, refp=0x5619f290, a=X_AXIS) at grob.cc:345
#5  0x5561fb6e in Grob::relative_coordinate(Grob const*, Axis) const 
(this=0x560465f0, refp=0x5619f290, a=X_AXIS) at grob.cc:345
#6  0x5561fb6e in Grob::relative_coordinate(Grob const*, Axis) const 
(this=this@entry=0x56046f40, refp=0x5619f290, a=a@entry=X_AXIS) at 
grob.cc:345
#7  0x556547a4 in 
Slur_configuration::score_extra_encompass(Slur_score_state const&) 
(this=0x561a2640, state=...)
at slur-configuration.cc:341
#8  0x556550f5 in Slur_configuration::run_next_scorer(Slur_score_state 
const&) (this=0x561a2640, state=...)
at slur-configuration.cc:522
#9  0x5571b5ab in Slur_score_state::get_best_curve() const 
(this=this@entry=0x7fff8440) at slur-scoring.cc:427
#10 0x5571b80f in Slur::calc_control_points(scm_unused_struct*) 
(smob=) at slur-scoring.cc:363
#11 0x7791fcf5 in scm_dapply (proc=0x7fffecfc0180, arg1=0x7fffe99eaae0, 
args=0x404) at eval.c:4895
#12 0x557d94d1 in Grob::try_callback_on_alist(scm_unused_struct**, 
scm_unused_struct*, scm_unused_struct*) (this=0x56025db0, 
alist=0x56025e10, sym=0x7fffeb374a60, proc=0x7fffecfc0180)
at grob-property.cc:232
#13 0x555fcfcf in Slur::get_curve(Grob*) (me=me@entry=0x56025db0) 
at slur.cc:231
#14 0x555feb78 in Slur::vertical_skylines(scm_unused_struct*) 
(smob=) at slur.cc:375
#15 0x7791fcf5 in scm_dapply (proc=0x7fffeced8f80, arg1=0x7fffe99eaae0, 
args=0x404) at eval.c:4895
#16 0x557d94d1 in Grob::try_callback_on_alist(scm_unused_struct**, 
scm_unused_struct*, scm_unused_struct*) (this=this@entry=0x56025db0, 
alist=alist@entry=0x56025e10, sym=0x7fffec5f2860, proc=0x7fffeced8f80) at 
grob-property.cc:232
#17 0x557d961d in Grob::internal_get_property(scm_unused_struct*) const 
(this=this@entry=0x56025db0, sym=)
at grob-property.cc:184
#18 0x55834a42 in add_interior_skylines(Grob*, Grob*, Grob*, 
std::vector >*) 
(me=me@entry=0x56025db0, x_common=x_common@entry=0x5619eda0, 
y_common=y_common@entry=0x5619f290, skylines=skylines@entry=0x7fff8b80)
at axis-group-interface.cc:657
#19 0x55837040 in Axis_group_interface::skyline_spacing(Grob*) 
(me=0x5619f290) at axis-group-interface.cc:919
#20 0x558371a4 in 
Axis_group_interface::calc_skylines(scm_unused_struct*) (smob=) 
at axis-group-interface.cc:400
#21 0x7791fcf5 in scm_dapply (proc=0x7fffecec3040, arg1=0x7fffe93cc820, 
args=0x404) at eval.c:4895
#22 0x557d94d1 in Grob::try_callback_on_alist(scm_unused_struct**, 
scm_unused_struct*, scm_unused_struct*) (this=this@entry=0x5619f290, 
alist=alist@entry=0x5619f2f0, sym=0x7fffec5f2860, proc=0x7fffecec3040) at 
grob-property.cc:232
#23 0x557d961d in Grob::internal_get_property(scm_unused_struct*) const 
(this=this@entry=0x5619f290, sym=)
at grob-property.cc:184
#24 0x556f42cf in 
Align_interface::internal_get_minimum_translations(Grob*, std::vector > const&, Axis, bool, bool, int, int) (end=0, start=0, 
pure=false, other_common=0x560500f0, a=Y_AXIS, g=0x5619f290, 
this=) at align-interface.cc:79
#25 0x556f42cf in 
Align_interface::internal_get_minimum_translations(Grob*, std::vector > const&, Axis, bool, bool, int, int) 
(me=me@entry=0x5619f570, elems=std::vector of length 1, capacity 1 = {...}, 
a=a@entry=Y_AXIS, include_fixed_spacing=, 
include_fixed_spacing@entry=false, pure=pure@entry=

Re: another slur problem

[David Kastrup]

Martin Tarenskeen  writes:

> On Tue, 5 Jul 2016, David Kastrup wrote:
>
>> Martin Tarenskeen  writes:
>
>>> Linux Fedora 24
>
>> Probably GCC6.  What does ldd /usr/bin/lilypond state?
>
> See attachment.

Huh.  The library version numbers (including C++ library as far as I can
tell) seem to match those of my system pretty closely.  Can you run this
under the debugger and get a traceback of the segfault?

Basically

gdb64 lilypond
run /tmp/bad-file.ly
backtrace

It's gdb64 on my rather promiscous system.  Could be just gdb on yours.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: another slur problem

[Martin Tarenskeen]

On Tue, 5 Jul 2016, David Kastrup wrote:


Martin Tarenskeen  writes:



Linux Fedora 24



Probably GCC6.  What does ldd /usr/bin/lilypond state?


See attachment.

--

Martin
linux-vdso.so.1 (0x7ffe254be000)
libdl.so.2 => /lib64/libdl.so.2 (0x7f7e1ee53000)
libguile.so.17 => /lib64/libguile.so.17 (0x7f7e1eb57000)
libpangoft2-1.0.so.0 => /lib64/libpangoft2-1.0.so.0 (0x7f7e1e941000)
libpango-1.0.so.0 => /lib64/libpango-1.0.so.0 (0x7f7e1e6f6000)
libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x7f7e1e4a4000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x7f7e1e195000)
libfontconfig.so.1 => /lib64/libfontconfig.so.1 (0x7f7e1df51000)
libfreetype.so.6 => /lib64/libfreetype.so.6 (0x7f7e1dca2000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x7f7e1d91a000)
libm.so.6 => /lib64/libm.so.6 (0x7f7e1d61)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7f7e1d3f9000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7f7e1d1dc000)
libc.so.6 => /lib64/libc.so.6 (0x7f7e1ce1a000)
/lib64/ld-linux-x86-64.so.2 (0x556e41d75000)
libgmp.so.10 => /lib64/libgmp.so.10 (0x7f7e1cb87000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x7f7e1c95)
libltdl.so.7 => /lib64/libltdl.so.7 (0x7f7e1c746000)
libthai.so.0 => /lib64/libthai.so.0 (0x7f7e1c53d000)
libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x7f7e1c33a000)
libharfbuzz.so.0 => /lib64/libharfbuzz.so.0 (0x7f7e1c0ba000)
libffi.so.6 => /lib64/libffi.so.6 (0x7f7e1beb2000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x7f7e1bc3e000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x7f7e1ba12000)
libz.so.1 => /lib64/libz.so.1 (0x7f7e1b7fc000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x7f7e1b5eb000)
libpng16.so.16 => /lib64/libpng16.so.16 (0x7f7e1b3b8000)
libfreebl3.so => /lib64/libfreebl3.so (0x7f7e1b1b5000)
libdatrie.so.1 => /lib64/libdatrie.so.1 (0x7f7e1afac000)
libgraphite2.so.3 => /lib64/libgraphite2.so.3 (0x7f7e1ad8)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: slurs and repeats

[Martin Tarenskeen]

On Tue, 5 Jul 2016, Robert Blackstone wrote:


Hi Martin,

I think you forgot the ) after the e4 in the 3rd bar of \alternative.
Anyway, this works for me, but I'm not sure it is what you want.



music = \relative {
\partial 4
c'8( d | % this slur is OK
\repeat volta 2 {
  e4) g g4. a8 | g4 e c4. d8 |
}
\alternative {
  { e4 e d c | d2. c8( d | } % this slur is not allowed?
  { e4) e d d | c2. } % ) added after e4
}


Hi,

This draws a slur from the end of the first alternative ending to the 
beginning of the second alternative ending, which makes no sense (and you 
may even argue it's a bug that this does not give an error or warning 
message).


I need a (partial) slur at the end of the first ending to indicate it's 
slurred back to the first e' of the repeated segment. Just like the 
pickup bar (\partial 4) is slurred to that same note.


--

Martin



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: NR 2.10.2 - arabic key signatures

[Federico Bruni]

Il giorno lun 4 lug 2016 alle 12:10, Carl Sorensen  
ha scritto:



On 7/1/16 5:08 AM, "Federico Bruni"  wrote:


Hi all

In the following paragraph, taken from
http://lilypond.org/doc/v2.19/Documentation/notation/arabic-music#arabic-k
ey-signatures


 Other maqams in the same bayati group, as shown in the table below:
 (bayati, hussaini, saba, and ushaq) can be indicated in the same 
way.

 These are all variations of the base and most common maqam in the
 group, which is bayati. They usually differ from the base maqam in
 their upper tetrachords, or certain flow details that don¹t change
 their fundamental nature, as siblings.


The last sentence seems quite obscure to me. What are "flow details"?
What are "siblings" in this context?


I think that "flow details" and "siblings" are arabic music terms, 
rather

than LilyPond internal terms.


ok



See https://en.wikipedia.org/wiki/Arabic_maqam

Although, I can't really understand that wikipedia page either.  It
appears that maqams are so different from traditional western music 
that

the terms are very difficult to relate.


In this page:
http://www.maqamworld.com/maqamat.html

it talks about "melodic flow":

Another peculiarity of maqamat is that the same note is not always 
played with the same exact pitch. The pitch may vary slightly, 
depending on the __melodic flow__ and what other notes are played 
before and after that note. The idea behind this effect is to round 
sharp corners in the melody by drawing the furthest notes nearer. 
This effect is sometimes called the law of attraction or gravity, and 
is common in other musical traditions (e.g. in Byzantine music).


Perhaps the doc is implicitely about "melodic flow details"?
Then what would "siblings" mean in that context?




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: another slur problem

[David Kastrup]

Martin Tarenskeen  writes:

> On Tue, 5 Jul 2016, David Kastrup wrote:
>
>> Martin Tarenskeen  writes:
>
>>> But this gives me a "Segfault" error
>>>
>>> \version "2.19.44"
>>> \relative {
>>>   c''8( d e f~ f2~ | f8) f e d c2 |
>>> }
>>>
>>>
>>> What's wrong here ?
>>
>> You don't specify operating system, architecture, LilyPond binary
>> version, whether you took a prepackaged system or compiled yourself, and
>> if you did so, which compiler you used.
>>
>> I don't get a segfault on my system.
>
>
> Linux Fedora 24
>
> Linux localhost.localdomain 4.6.3-300.fc24.x86_64 #1 SMP Fri Jun 24
> 20:52:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> lilypond-2.19.44-1.fc24.x86_64 from Fedora repository

Probably GCC6.  What does ldd /usr/bin/lilypond state?

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: another slur problem

[Martin Tarenskeen]

On Tue, 5 Jul 2016, David Kastrup wrote:


Martin Tarenskeen  writes:



But this gives me a "Segfault" error

\version "2.19.44"
\relative {
  c''8( d e f~ f2~ | f8) f e d c2 |
}


What's wrong here ?


You don't specify operating system, architecture, LilyPond binary
version, whether you took a prepackaged system or compiled yourself, and
if you did so, which compiler you used.

I don't get a segfault on my system.



Linux Fedora 24

Linux localhost.localdomain 4.6.3-300.fc24.x86_64 #1 SMP Fri Jun 24 
20:52:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux


lilypond-2.19.44-1.fc24.x86_64 from Fedora repository


--

Martin

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: slurs and repeats

[Robert Blackstone]

On 5 Jul 2016, at 10:03 , Martin Tarenskeen  wrote:

> 
> Hi,
> 
> In the following example, how can I write a slur that starts at the end of 
> the first \alternative to repeat the corresponding slur from the pickup bar?
> 
> I hope my question/example is clear.
> 
> Martin
> 
> 
> 
> \version "2.19.44"
> 
> music = \relative {
>  \partial 4
>  c'8( d | % this slur is OK
>  \repeat volta 2 {
>e4) g g4. a8 | g4 e c4. d8 |
>  }
>  \alternative {
>{ e4 e d c | d2. c8( d | } % this slur is not allowed?
>{ e4 e d d | c2. }
>  }
>  \bar "|." }
> 
> \score {
>  \new Staff {
>\music
>  }
>  \layout {}
> }
> 
> 


 Hi Martin,

I think you forgot the ) after the e4 in the 3rd bar of \alternative.
Anyway, this works for me, but I'm not sure it is what you want.
BTW, I use TeXShop as the editor and it seems more forgiving than some other 
editors.

Best regards,
Robert Blackstone


\version "2.19.44"
\relative {
 c''8( d e f~ f2~ | f8) f e d c2 |
}


%What's wrong here ?

\version "2.19.44"

music = \relative {
 \partial 4
 c'8( d | % this slur is OK
 \repeat volta 2 {
   e4) g g4. a8 | g4 e c4. d8 |
 }
 \alternative {
   { e4 e d c | d2. c8( d | } % this slur is not allowed?
   { e4) e d d | c2. } % ) added after e4
 }
 \bar "|." }

\score {
 \new Staff {
   \music
 }
 \layout {}
}
% 


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: another slur problem

[Thomas Scharkowski]

 Original-Nachricht 


Hi,

This works fine:

\version "2.19.44"
\relative {
   c''8( d e) f~ f2~ | f8 f e d c2 |
}

But this gives me a "Segfault" error

\version "2.19.44"
\relative {
   c''8( d e f~ f2~ | f8) f e d c2 |
}


What's wrong here ?


Both are fine here (Mac OS X 10.11.5, LilyPond 2.19.44)
Thomas

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: another slur problem

[David Kastrup]

Martin Tarenskeen  writes:

> Hi,
>
> This works fine:
>
> \version "2.19.44"
> \relative {
>   c''8( d e) f~ f2~ | f8 f e d c2 | }
>
> But this gives me a "Segfault" error
>
> \version "2.19.44"
> \relative {
>   c''8( d e f~ f2~ | f8) f e d c2 |
> }
>
>
> What's wrong here ?

You don't specify operating system, architecture, LilyPond binary
version, whether you took a prepackaged system or compiled yourself, and
if you did so, which compiler you used.

I don't get a segfault on my system.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

another slur problem

[Martin Tarenskeen]

Hi,

This works fine:

\version "2.19.44"
\relative {
  c''8( d e) f~ f2~ | f8 f e d c2 | 
}


But this gives me a "Segfault" error

\version "2.19.44"
\relative {
  c''8( d e f~ f2~ | f8) f e d c2 |
}


What's wrong here ?

--

Martin

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

slurs and repeats

[Martin Tarenskeen]

Hi,

In the following example, how can I write a slur that starts at the end of 
the first \alternative to repeat the corresponding slur from the pickup 
bar?


I hope my question/example is clear.

Martin



\version "2.19.44"

music = \relative {
  \partial 4
  c'8( d | % this slur is OK
  \repeat volta 2 {
e4) g g4. a8 | g4 e c4. d8 |
  }
  \alternative {
{ e4 e d c | d2. c8( d | } % this slur is not allowed?
{ e4 e d d | c2. }
  }
  \bar "|." 
}


\score {
  \new Staff {
\music
  }
  \layout {}
}



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user