Werner LEMBERG | 23 Jul 07:31 2016
Picon

Problems with `\repeat percent'


[445bf3bb2fbd1f259fe43ade204fb34d68bdd581]

Folks,

have a look at NR section `Percent Repeats', `Known Issues and
Warnings'.  There is code like

  \relative c'' {
    \repeat percent 3 { \time 5/4 c2. 2 \time 4/4 2 2 }
  }

which generates the attached image.  The generation of a second staff
can't be right...  A bug?

Additionally, the `improved' version

  \relative c''
    <<
      \repeat percent 3 { c2. 2 2 2 }
      \repeat unfold 3 { \time 5/4 s4*5 \time 4/4 s1 }
    >>

also generates an empty staff, which looks definitely wrong to me.

BTW, both snippets generate

  programming error:
    No spacing entry from DoublePercentRepeat to `right-edge'

(Continue reading)

Pierre Perol-Schneider | 22 Jul 13:46 2016
Picon

DOC: Essay, 1.4 Building software

> I'm not top posting.

Hi Bug Squad,

See:
http://lilypond.org/doc/v2.19/Documentation/essay/building-software.html#music-representation

I think that this part, especially the chords ('Simultaneous notes'),
should be re-written, e.g.:

\version "2.19"

<<c4 d4 e4>>

Cheers,

Pierre
Karim Haddad | 21 Jul 15:05 2016
Picon

old style arguments in overrides using #' generate errors

Hi

I am not sure it is a bug, but with  LilyPond 2.19.45 version

we have this error :

error: syntax error, unexpected SCM_TOKEN, expecting '='
 \override Staff.LaissezVibrerTie  #'details
                                               #'note-head-gap = #(/ 1.5 -2)
					       
get also an error here :

 \override TextSpanner #'bound-details #'left #'text = \markup { \italic "m.d" }
 \override TextSpanner #'bound-details #'right #'text = \markup { \draw-line #'(0 . 1) }

with this verssion 2.19.36 everything works fine.
I don't know if the #'arguments aren't no more supported with the latest version (?).

best

--

-- 
Karim Haddad
Mojca Miklavec | 20 Jul 16:14 2016
Picon

Junk string in ly -> midi -> ly conversion

Hi,

I wanted to test the conversion from midi to Lilypond. I took a midi
file generated with LilyPond, converted it to LilyPond with

arch -32 /System/Library/Frameworks/Python.framework/Versions/2.7/bin/python
/Applications/LilyPond.app/Contents/Resources/bin/midi2ly test.midi

(I didn't find any more intuitive way to do the conversion)

But then lilypond failed to process the generated ly file:

> lilypond test-midi.ly
GNU LilyPond 2.19.44
Processing `test-midi.ly'
Parsing...
test-midi.ly:16:32: warning: non-UTF-8 input
  \set Staff.instrumentName = "
                               ??a
test-midi.ly:16:33: warning: non-UTF-8 input
  \set Staff.instrumentName = "?
                                ?a
test-midi.ly:16:32: error: EOF found inside string
  \set Staff.instrumentName = "
                               ??a
test-midi.ly:16:32: error: syntax error, unexpected end of input
  \set Staff.instrumentName = "
                               ??a
fatal error: failed files: "test-midi.ly"

(Continue reading)

Federico Bruni | 17 Jul 12:11 2016

Re: LM 2.4.1: errors in variable definitions

Il giorno dom 17 lug 2016 alle 11:44, David Kastrup <dak <at> gnu.org> ha 
scritto:
>>  Of course, but this is the standard \paper property and the whole
>>  point of the example in the documentation is defining variables.
>> 
>>  We may omit the unit and use the default one (millimeters). But I
>>  wonder if this is a bug or there's a better way to define such a
>>  variable.
> 
> I thought the default unit was staff spaces?  Don't quote me on that 
> but
> I thought that the main mess was that the definition of \cm changed 
> when
> one changed the default staff size.

Perhaps the default unit of \paper properties is millimeters? That 
would make sense. While staff spaces make sense for elements of the 
notation.

I just made a test. A 208 line-width spans almost all the 210x210 
document:

\version "2.19.45"

width = 208
stringName = "Wendy"
aFivePaper = \paper { paper-height = 210 }

\paper {
  \aFivePaper
(Continue reading)

Federico Bruni | 17 Jul 09:16 2016

LM 2.4.1: errors in variable definitions

I found a bug in the Learning Manual:
http://lilypond.org/doc/v2.19/Documentation/learning/organizing-pieces-with-variables.html

The example suggested at the end of that page doesn't work:

1. paperheight should be renamed to paper-height

2. name variable should be renamed to something else (myName), as it 
triggers this error:
warning: identifier name is a keyword: `name'

3. width variable triggers this error:
error: unknown escaped string: `\cm'

I don't know how to fix this,

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\version "2.19.45"

%width = 4.5\cm
%name = "Wendy"
aFivePaper = \paper { paper-height = 21.0 \cm }

\paper {
  \aFivePaper
  %line-width = \width
}

{
(Continue reading)

David Kastrup | 17 Jul 00:47 2016
Picon
Picon

Re: Compiling lilypond


[For the record: compiling LilyPond with Clang++ currently fails]

Mojca Miklavec <mojca.miklavec.lists <at> gmail.com> writes:

> Hi,
>
> It seems that this is also a problem on the latest OS X, not just on
> my ancient box. We'll probably drop an email on the bug mailing list.

Here is an example you can report to the Clang++ mailing list.  This
overloading resolution seems to be what essentially fails with the
current LilyPond source.

Attachment (ugh.cc): text/x-c++src, 279 bytes

Unfortunately, I don't see much of a way to circumvent this one in the
current code base without completely throwing large reorganizations and
simplifications away.

Sorry, you'll need to use GCC for now.

--

-- 
David Kastrup
_______________________________________________
bug-lilypond mailing list
(Continue reading)

Federico Bruni | 15 Jul 11:55 2016

Re: PDF metadata missing if \header is within a \bookpart block

Il giorno ven 15 lug 2016 alle 10:47, David Kastrup <dak <at> gnu.org> ha 
scritto:
> Federico Bruni <fede <at> inventati.org> writes:
> 
>>  Il giorno dom 3 lug 2016 alle 14:57, Simon Albrecht
>>  <simon.albrecht <at> mail.de> ha scritto:
>>>>  Let me explain better.
>>>>  In a directory I have single files for each song. I want to 
>>>> compile
>>>>  each of them as a standalone PDF. But I also want to include them
>>>>  in a master file which acts as an anthology book.
>>>>  So the master file already works fine, because the \header is in
>>>>  the top level.
>>>>  The problem is with each single song, because the songs use
>>>>  \bookpart.
>>> 
>>>  Well, I suppose you need to find a clever way of setting pdftitle 
>>> in
>>>  the wrapper files for the single songs. This kind of things can be
>>>  really annoying and convoluted…
>> 
>>  This is going to cause me headaches. I've always fought with this 
>> sort
>>  of things in LilyPond.
>>  The problem is that I cannot include music variables within a
>>  \bookpart block.
> 
> Come again?  Why wouldn't you be able to do that?

If you try to compile the file John-Doe-Anthology.ly in the _first_ set 
(Continue reading)

Tobias Kretschmar | 14 Jul 22:41 2016
Picon
Picon

musicxml2ly writes UTF16 BE in header texts

musicxml2ly 2.19.45 writes any header text (and some more) as UTF16 BE in
the ly file. 

This will lead to errors when running lilypond with this file.  

error: EOF found inside string
error: syntax error, unexpected end of input, ...

Regards, Tobias
Federico Bruni | 14 Jul 17:51 2016

Re: PDF metadata missing if \header is within a \bookpart block


Il giorno gio 14 lug 2016 alle 10:58, Federico Bruni 
<fede <at> inventati.org> ha scritto:
> Il giorno dom 3 lug 2016 alle 14:57, Simon Albrecht 
> <simon.albrecht <at> mail.de> ha scritto:
>>> Let me explain better.
>>> In a directory I have single files for each song. I want to compile 
>>> each of them as a standalone PDF. But I also want to include them 
>>> in a master file which acts as an anthology book.
>>> So the master file already works fine, because the \header is in 
>>> the top level.
>>> The problem is with each single song, because the songs use 
>>> \bookpart.
>> 
>> Well, I suppose you need to find a clever way of setting pdftitle in 
>> the wrapper files for the single songs. This kind of things can be 
>> really annoying and convoluted…
> 
> This is going to cause me headaches. I've always fought with this 
> sort of things in LilyPond.
> The problem is that I cannot include music variables within a 
> \bookpart block.
> I suspect that what I want to achieve is not possible.
> 
> See attached examples.
> The -part.ly files compile fine, but the Anthology will fail. I see 
> why it's failing but I cannot find other ways.
> _______________________________________________

Ok, I found a solution:
(Continue reading)

Federico Bruni | 14 Jul 10:58 2016

Re: PDF metadata missing if \header is within a \bookpart block

Il giorno dom 3 lug 2016 alle 14:57, Simon Albrecht 
<simon.albrecht <at> mail.de> ha scritto:
>> Let me explain better.
>> In a directory I have single files for each song. I want to compile 
>> each of them as a standalone PDF. But I also want to include them in 
>> a master file which acts as an anthology book.
>> So the master file already works fine, because the \header is in the 
>> top level.
>> The problem is with each single song, because the songs use 
>> \bookpart.
> 
> Well, I suppose you need to find a clever way of setting pdftitle in 
> the wrapper files for the single songs. This kind of things can be 
> really annoying and convoluted…

This is going to cause me headaches. I've always fought with this sort 
of things in LilyPond.
The problem is that I cannot include music variables within a \bookpart 
block.
I suspect that what I want to achieve is not possible.

See attached examples.
The -part.ly files compile fine, but the Anthology will fail. I see why 
it's failing but I cannot find other ways.
Attachment (composition-2-part.ly): text/x-lilypond, 137 bytes
\version "2.19.45"
myMusic = \relative {
  d'4 e g2 |
(Continue reading)


Gmane