Re: error message

[Colin Campbell]

On 15-10-09 05:20 PM, Mark Stephen Mrotek wrote:


Hello,

Using Lilypond2.18.0, Frescobaldi 2.18.1.

When clicking the Lilypond icon in Frescobaldi the following appears:

Starting lilypond-windows.exe 2.18.2 [Nocturne Ab.ly]...Aborting 
lilypond-windows.exe 2.18.2 [Nocturne Ab.ly]...


Exited with return code 62097.

Please provide advice.

Thank you for your kind attention.




The test code runs without error under 2.19.29 and Linux. The problem 
may be platform-specific, it seems.


Cheers,
Colin
--
There have been times I've considered getting the arbalest mounted on 
the right front fender of my car in working order.

 - denaldo, in alt.callahans
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

code \acciaccatura e'8 broke the manual \break

[MING TSANG]

It didn't show up at lilypond-user Mailinglist.   Try again
- Forwarded Message -
  From: MING TSANG 
 To: Lilypond-user Mailinglist  
 Sent: Thursday, October 8, 2015 7:10 PM
 Subject: code \acciaccatura e'8 broke the manual \break
   
Dear lilyponders,
Please refer to .png.Is this a bug? How can I resolve it.


Attach is the lily file
Immanuel,Ming

  \version "2.19.28"
\language "english"



global = {
  \key d \major
  \numericTimeSignature
  \time 3/4
  \tempo "喜樂地,讚美地" 4=127
}

x = b'8\rest
z = b'4\rest
zi = d4\rest
ss➎➊   = { b'4 cs''4 d''4 |}
ss➎➋   = { a'2. |}
ss➎➌   = { b'4 a'4 fs'4 |}
ss➎➍   = { e'4 d'4 e'4 |}
sa➎➎   = { d'2. |}
sa➎➏   = R2.
sa➎➐   = R2.
sa➎➑   = R2.
sa➎➒   = R2.
sa➏➓   = R2.


soprano =   {
  \global
 r2.
  \ss➎➊   \ss➎➋   \ss➎➌   \ss➎➍   \sa➎➎   \break
  \sa➎➏   \sa➎➐   \sa➎➑   \sa➎➒   \sa➏➓   \break

}


r➄➀ = { <<{b'8( cs''8 d''8[ cs''8] d''8 e''8)}\\{fs'2.}>> |}
r➄➁ = { <<{fs''4 d''4 a'4}\\{a'4 fs'2}>> |}
r➄➂ = { \z 2 |}
r➄➃ = { \z 2 |}
r➄➄ = { \z d'8([ e'8] g'8 a'8) |}

r➄➅  = { 2. |}
r➄➅i = { \acciaccatura e'8  2. |}

r➄➆ = { 4( 4 4) |}
r➄➇ = { 2. |}
r➄➈ = \r➄➆
r➅➉ = { <<{e''4 d''8([ cs''8] a'8 e'8)}\\{g'2.}>> |}


right =   {
  
  \global
  r2.^\markup"no \grace or \acciaccatura with manual \break"
\r➄➀   \r➄➁   \r➄➂   \r➄➃   \r➄➄
\r➄➅   \r➄➆   \r➄➇   \r➄➈   \r➅➉
}



righti =   {
  
  \global
  r2.^\markup"Use \grace or \acciaccatura with manual \break - break no longer work "
\r➄➀   \r➄➁   \r➄➂   \r➄➃   \r➄➄
\r➄➅i   \r➄➆   \r➄➇   \r➄➈   \r➅➉
}

<<
\new Staff \soprano
\new Staff \right
>>

<<
\new Staff \soprano
\new Staff \righti
>>

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

Re: New Music-Engraving Forum

[Pierre Perol-Schneider]

Interesting, thanks for the link Abraham.
Cheers,
~Pierre

2015-10-08 22:49 GMT+02:00 Abraham Lee :

> All,
>
> Prompted by some discussions on the Finale user forums, a new
> software-agnostic forum has been created to discuss general practice music
> notation/engraving issues and questions. As far as I'm aware, all users are
> welcome, regardless of what their software of choice is for music
> engraving.
>
> Here's the link for anyone interested in registering: http://notat.io
>
> Happy Engraving!
> - Abraham
>
> ___
> 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: How to get X/Y-extent of a bezier-curve?

[David Kastrup]

Thomas Morley  writes:

> 2015-10-07 14:08 GMT+02:00 Thomas Morley :
>
>> The code in my initial mail uses coord-rotate (not
>> ly:stencil-rotate-absolute as in Jans suggestion)
>> What do you think about this method?
>>
>> Ofcourse it was heavily simplified, maybe best to put up a patch to
>> have the full code for more detailed discussion.
>
> I have to postpone uploading the patch, there are some glitches ...
>
> And one thing which has driven me crazy, before I found the culprit:
> `coord-rotate' has a problem which can be demonstrated with:
>
> (display (coord-rotate '(10 . 0) (/ PI 2)))
>
> Expected:   (0 . 10)
> Actually:  (6.12323399573677e-16 . 10.0)
>
> What's the best method to get the zero?

coord-translate is written awfully (almost any intermediate use of atan
is an indicator of unnecessary contortions) but that's not the problem
here.  The problem is that GUILE stores floating point number as double
numbers (64 bits), and the MPU does its calculations, including
trigonometry, using long double arithmetic (80 bits on x86).
Consequently, there is no representation of PI in GUILE that would lead
to the expected results.

When angles are represented un GUILE, you are probably indeed best off
using degrees rather than radians since small multiples of 45 are
exactly representable at any number resolution available to GUILE.

The code used in ly:stencil-rotate-absolute looks like it might work
(though I'd write (a * (M_PI / 180.0)) rather than (a * M_PI / 180.0)).

-- 
David Kastrup

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

RE: error message

[Mark Stephen Mrotek]

Abraham,

 

Thank you for your response. The file is attached.

 

Mark

 

From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of
tisimst
Sent: Friday, October 09, 2015 4:45 PM
To: lilypond-user@gnu.org
Subject: Re: error message

 

Mind sharing the source (file) that is being used when you get this error?

 

Thanks,

Abraham

On Friday, October 9, 2015, Mark Stephen Mrotek [via Lilypond] <[hidden
email]> wrote:

Hello,

 

Using Lilypond2.18.0, Frescobaldi 2.18.1.

When clicking the Lilypond icon in Frescobaldi the following appears:

 

Starting lilypond-windows.exe 2.18.2 [Nocturne Ab.ly]...Aborting
lilypond-windows.exe 2.18.2 [Nocturne Ab.ly]...

Exited with return code 62097.

 

Please provide advice.

Thank you for your kind attention.

 

Mark Stephen Mrotek


___ 
lilypond-user mailing list 
[hidden email]   
https://lists.gnu.org/mailman/listinfo/lilypond-user



  _  

If you reply to this email, your message will be added to the discussion
below:

http://lilypond.1069038.n5.nabble.com/error-message-tp182215.html 

To start a new topic under User, email ml-node+s1069038n3h2@... 
To unsubscribe from Lilypond, click here.
 
 NAML


 

  _  

View this message in context: Re: error message
 
Sent from the User mailing list archive
  at Nabble.com.

\version "2.18.0"

\header {
  title = "Nocturne 5"
  composer = "J. Leybach"
  opus = "Op. 52 No. 5"
}

\score {
  \new PianoStaff <<
\new Staff = "upper"
\relative c'' {
  \clef treble
  \key aes \major
  \time 6/8
  
  r4 8\p-. q-. -. -. |
  \tieDown
  4. (4-.) r8 |
  r4 8-.\p -. -. -. |
  4. (< ees g>4-.) r8 |
  
  %5
  
  r4 8\p q   |

 |
  4. (4-.) r8 |
  4. (4-.) r8 |
  4. (4-.) r8 |
  ees\f^^^.-2 ees'^^^.-2 ees'^^^.-2
  \ottava 1
  f'16 ees des bes g ees-4 |
  \ottava 0
  des bes g ees-4 des bes
  g_\markup {\italic "diminuendoe ritardando"}
  ees-2 d ees f ees |
  d ees f ees d ees f-1 g aes a-1 bes-2 b-1 \bar "||"
  c4.\p (ees4 f8 | ees4.~) ees4 ees8-3 |
  f4.-1 (aes4 bes8 \appoggiatura {c,8} c'4.~) c4 8 |
  
  
}

\new Staff = "lower"
\relative c {
  \clef bass
  \key aes \major
  \time 6/8
  
  4_^-.^\f \clef treble
  8-. << { bes'-. aes-. g-. |
aes4. (g4-.) } \\
  { ees4.~ | ees~ ees4 } >> r8 \clef bass |
  4_^-.^\f \clef treble
  8-. << { des'-. c-. bes-. | c4. (bes4) } \\
   { ees,4.~ | ees~ ees4 } >> r8 \clef bass |
  
  %5
  
  4_^-.^\f \clef treble
  << { r8 r ees des | c bes aes g aes g | aes4. (g4) } \\
 { ees8 ees4.~ | ees2.~ | ees4.~ ees4 } >> r8 \clef bass |
  e4. (f4) r8 | d4. (ees4) r8 |
  4_^-. r8 4^^^.\arpeggio r8 |
  R2. | R | aes,16 ees'^3 aes^2 c ees^4 aes c8^. r r |
  
  
}

\new Dynamics {
 
 s8 s8\sustainOn s2 | s4. s4 s8\sustainOff |
 s8 s8\sustainOn s2 | s4. s4 s8\sustainOff |
 s8 s8\sustainOn s2 | s4. s4 s16 s16\sustainOff |
 s2. | s | s |
 s8 s8\sustainOn s2 | s4. s4.\sustainOff |
}

  >>
  
  \layout {
indent = #0
  }
  
  }


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

Re: error message

[tisimst]

Mind sharing the source (file) that is being used when you get this error?

Thanks,
Abraham

On Friday, October 9, 2015, Mark Stephen Mrotek [via Lilypond] <
ml-node+s1069038n182215...@n5.nabble.com> wrote:

> Hello,
>
>
>
> Using Lilypond2.18.0, Frescobaldi 2.18.1.
>
> When clicking the Lilypond icon in Frescobaldi the following appears:
>
>
>
> Starting lilypond-windows.exe 2.18.2 [Nocturne Ab.ly]...Aborting
> lilypond-windows.exe 2.18.2 [Nocturne Ab.ly]...
>
> Exited with return code 62097.
>
>
>
> Please provide advice.
>
> Thank you for your kind attention.
>
>
>
> Mark Stephen Mrotek
>
> ___
> lilypond-user mailing list
> [hidden email] 
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://lilypond.1069038.n5.nabble.com/error-message-tp182215.html
> To start a new topic under User, email ml-node+s1069038n...@n5.nabble.com
> 
> To unsubscribe from Lilypond, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/error-message-tp182215p182216.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: How to get X/Y-extent of a bezier-curve?

[Ed Gordijn]

>
>
> Expected:   (0 . 10)
> Actually:  (6.12323399573677e-16 . 10.0)
>
> What's the best method to get the zero?
> Using simple `round' will not work, because I don't want to get
> integers for other fractions of PI.
>

in pseudo code:

if abs(x) < 0.001 then x=0

or
round(x, 3) if 3 decimals is your accuracy

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

error message

[Mark Stephen Mrotek]

Hello,

 

Using Lilypond2.18.0, Frescobaldi 2.18.1.

When clicking the Lilypond icon in Frescobaldi the following appears:

 

Starting lilypond-windows.exe 2.18.2 [Nocturne Ab.ly]...Aborting
lilypond-windows.exe 2.18.2 [Nocturne Ab.ly]...

Exited with return code 62097.

 

Please provide advice.

Thank you for your kind attention.

 

Mark Stephen Mrotek

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

Re: compress full bar rests

[Flaming Hakama by Elaine]

Thanks for the help, everyone who replied.  Looks like a simple solution.

The purpose of the globals treatment is to consolidate any score-wide
content,  like double barlines, repeats, signatures, rehearsal marks, coda
and D.S. markings, tempi, etc.

Admiyyedly, in this minimal example, that utility is not at all obvious.
But that's the framework in which I was having the problem.

On Oct 9, 2015 3:41 PM, "Thomas Morley" 
> A sequence of single SkipEvents like { s1 s1 } will not be compressed.
> You need to write { s1*2 }.
> See the following tiny examples:
>
> \new Staff <<
>   {  s1 s1 }
>   {  \compressFullBarRests R1*2 }
> >>
>
> \new Staff <<
>   \displayMusic {  s1*2 }
>   {  \compressFullBarRests R1*2 }
> >>
>
>
> Your example cold read:
>
> \version "2.19.28"
>
> structure = \relative c {
> \compressFullBarRests
> \override MultiMeasureRest.expand-limit = #2
> \override Score.RehearsalMark.self-alignment-X = #LEFT
> \mark "Globally compressed"
> s1*5 \bar "||"
> }
>
> globals = #(define-music-function (parser location mus) (ly:music?)
>   #{ << \structure \relative { $mus } >> #})
>
> melody = \relative c'' {
> c1 | R1*4 ||
> }
>
> melodyGlobal = \globals { \melody }
>
> <<
> \new Staff {
> \melodyGlobal
> }
> >>
>
> HTH,
>   Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: compress full bar rests

[Kieren MacMillan]

Hi Thomas (et al.),

On Oct 9, 2015, at 6:41 PM, Thomas Morley  wrote:
> A sequence of single SkipEvents like { s1 s1 } will not be compressed.

Check the archives for “mergeSkips”, especially 
.
(And, yes, I think this — or something similar — should be in the standard 
distro.)

Hope this helps!
Kieren.



Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

Re: compress full bar rests

[Simon Albrecht]

Hello David,

On 09.10.2015 22:31, Flaming Hakama by Elaine wrote:
Somehow, through this framework, I cannot get full bar rests to 
compress when I use a globals treatment.


Minimal examples are highly useful: You should follow the instructions 
on  if you encounter such a problem.
There is _much_ redundancy in the example you posted: You use \relative 
three times for only one music expression. Many overrides are also 
applied multiple times, which does not help at all in debugging. Also 
there are many superfluous <<>> and {}: If you have only one expression, 
you needn’t wrap it in any kind of braces. For example ‘##{ \relative 
$mus #}’ or ‘\new Staff \foo’ on top level or ‘\globals \melody’.


But all of this has nothing to do with the problem, which now has 
already been resolved by Harm and Trevor.


Yours, Simon

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

Re: compress full bar rests

[Thomas Morley]

2015-10-09 22:31 GMT+02:00 Flaming Hakama by Elaine :
> Somehow, through this framework, I cannot get full bar rests to compress
> when I use a globals treatment.
>
> Does anyone have a clue as to how to get them to compress?
>
> Thanks.
>
>
>
> \version "2.19.15"
>
> structure = \relative c {
> \compressFullBarRests
> \override MultiMeasureRest.expand-limit = #2
> \override Score.RehearsalMark.self-alignment-X = #LEFT
> \mark "Globally Uncompressed"
> s1 |
> s1 | s | s | s \bar "||"
> }
>
> globals = #(define-music-function (parser location mus) (ly:music?) #{ <<
> \structure \relative { $mus } >> #})
>
> melody = \relative c'' {
> \compressFullBarRests
> \override MultiMeasureRest.expand-limit = #2
> c1 | R1*4 ||
> }
>
> melodyGlobal = \globals { \melody }
>
>
> <<
> \new Staff {
> \compressFullBarRests
> \override MultiMeasureRest.expand-limit = #2
> \override Score.RehearsalMark.self-alignment-X = #LEFT
> \mark "Simple and Compressed"
> \melody
> }
>>>
>
> <<
> \new Staff {
> \compressFullBarRests
> \override MultiMeasureRest.expand-limit = #2
> \melodyGlobal
> }
>>>
>
>
> David Elaine Alt


A sequence of single SkipEvents like { s1 s1 } will not be compressed.
You need to write { s1*2 }.
See the following tiny examples:

\new Staff <<
  {  s1 s1 }
  {  \compressFullBarRests R1*2 }
>>

\new Staff <<
  \displayMusic {  s1*2 }
  {  \compressFullBarRests R1*2 }
>>


Your example cold read:

\version "2.19.28"

structure = \relative c {
\compressFullBarRests
\override MultiMeasureRest.expand-limit = #2
\override Score.RehearsalMark.self-alignment-X = #LEFT
\mark "Globally compressed"
s1*5 \bar "||"
}

globals = #(define-music-function (parser location mus) (ly:music?)
  #{ << \structure \relative { $mus } >> #})

melody = \relative c'' {
c1 | R1*4 ||
}

melodyGlobal = \globals { \melody }

<<
\new Staff {
\melodyGlobal
}
>>

HTH,
  Harm

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

Re: compress full bar rests

[Trevor Daniels]

Try s1*5

Trevor


  - Original Message - 
  From: Flaming Hakama by Elaine 
  To: Lilypond-User Mailing List 
  Sent: Friday, October 09, 2015 9:31 PM
  Subject: compress full bar rests


  Somehow, through this framework, I cannot get full bar rests to compress when 
I use a globals treatment.


  Does anyone have a clue as to how to get them to compress?


  Thanks.






  \version "2.19.15" 


  structure = \relative c { 
  \compressFullBarRests
  \override MultiMeasureRest.expand-limit = #2   
  \override Score.RehearsalMark.self-alignment-X = #LEFT
  \mark "Globally Uncompressed"
  s1 | 
  s1 | s | s | s \bar "||" 
  }


  globals = #(define-music-function (parser location mus) (ly:music?) #{ << 
\structure \relative { $mus } >> #})


  melody = \relative c'' {
  \compressFullBarRests
  \override MultiMeasureRest.expand-limit = #2
  c1 | R1*4 || 
  }


  melodyGlobal = \globals { \melody }




  <<
  \new Staff { 
  \compressFullBarRests
  \override MultiMeasureRest.expand-limit = #2
  \override Score.RehearsalMark.self-alignment-X = #LEFT
  \mark "Simple and Compressed"
  \melody
  }
  >>


  <<
  \new Staff { 
  \compressFullBarRests
  \override MultiMeasureRest.expand-limit = #2
  \melodyGlobal
  }
  >>




  David Elaine Alt

  415 . 341 .4954   "Confusion is 
highly underrated"

  ela...@flaminghakama.com

  self-immolation.info
  skype: flaming_hakama
  Producer ~ Composer ~ Instrumentalist
  
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


--


  ___
  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: compress full bar rests

[Jacques Menu]

Hello David,

Played around with your example, but to no avail.

What is this « globals » function supposed to bring?

JM

> Le 9 oct. 2015 à 22:31, Flaming Hakama by Elaine  a 
> écrit :
> 
> Somehow, through this framework, I cannot get full bar rests to compress when 
> I use a globals treatment.
> 
> Does anyone have a clue as to how to get them to compress?
> 
> Thanks.
> 
> 
> 
> \version "2.19.15" 
> 
> structure = \relative c { 
> \compressFullBarRests
> \override MultiMeasureRest.expand-limit = #2   
> \override Score.RehearsalMark.self-alignment-X = #LEFT
> \mark "Globally Uncompressed"
> s1 | 
> s1 | s | s | s \bar "||" 
> }
> 
> globals = #(define-music-function (parser location mus) (ly:music?) #{ << 
> \structure \relative { $mus } >> #})
> 
> melody = \relative c'' {
> \compressFullBarRests
> \override MultiMeasureRest.expand-limit = #2
> c1 | R1*4 || 
> }
> 
> melodyGlobal = \globals { \melody }
> 
> 
> <<
> \new Staff { 
> \compressFullBarRests
> \override MultiMeasureRest.expand-limit = #2
> \override Score.RehearsalMark.self-alignment-X = #LEFT
> \mark "Simple and Compressed"
> \melody
> }
> >>
> 
> <<
> \new Staff { 
> \compressFullBarRests
> \override MultiMeasureRest.expand-limit = #2
> \melodyGlobal
> }
> >>
> 
> 
> David Elaine Alt
> 415 . 341 .4954   "Confusion is 
> highly underrated"
> ela...@flaminghakama.com 
> self-immolation.info 
> skype: flaming_hakama
> Producer ~ Composer ~ Instrumentalist
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> ___
> 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: opus and piece fields in top level header.

[Simon Albrecht]

On 09.10.2015 22:25, Richard Shann wrote:

In the 2.18 it does not seem to mention that the opus and piece fields
are not output anywhere if they are set in a \header{} block *outside*
any \score{} block, but this seems to be the case.


I can’t access the 2.18 docs ATM, since lilypond.org is down. But in the 
current development version, this is documented in NR 3.2.1, with an 
example for the default placement. 3.2.2 has an explanation how to 
redefine the \paper variable bookHeaderMarkup, and the default value can 
be found in ‘ly/titling-init.ly’.


HTH, Simon

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

Re: New to Lilypond - including score in LaTeX

[Светлана Лобанова]

I had some unwanted issues with lilypond-book and TeX (I don't remember which 
ones), so I've chosen "manual method", enhanced with .bat file (on Windows). I 
have a .bat file which compilles all my .ly files (plenty of lines like this 
"lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts -dno-aux-files  
filename.ly"). Then I include all of them as pdf images in .tex. The drawback 
is when you have multi-page score you will need to include them page-by-page.

-- 
С уважением,
 Светлана Лобанова
+79036683074


09.10.2015, 03:40, "Felix Yeung" :
> Dear All,
>
> I’m very new to Lilypond, currently typesetting a document with plainsong 
> notation (with gregorio) and with occasional modern music. I am wondering if 
> you there’s any way to incorporate lilypond scores into my document?
>
> Many thanks for your help!
>
> Felix Yeung
>
> ___
> 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

compress full bar rests

[Flaming Hakama by Elaine]

Somehow, through this framework, I cannot get full bar rests to compress
when I use a globals treatment.

Does anyone have a clue as to how to get them to compress?

Thanks.



\version "2.19.15"

structure = \relative c {
\compressFullBarRests
\override MultiMeasureRest.expand-limit = #2
\override Score.RehearsalMark.self-alignment-X = #LEFT
\mark "Globally Uncompressed"
s1 |
s1 | s | s | s \bar "||"
}

globals = #(define-music-function (parser location mus) (ly:music?) #{ <<
\structure \relative { $mus } >> #})

melody = \relative c'' {
\compressFullBarRests
\override MultiMeasureRest.expand-limit = #2
c1 | R1*4 ||
}

melodyGlobal = \globals { \melody }


<<
\new Staff {
\compressFullBarRests
\override MultiMeasureRest.expand-limit = #2
\override Score.RehearsalMark.self-alignment-X = #LEFT
\mark "Simple and Compressed"
\melody
}
>>

<<
\new Staff {
\compressFullBarRests
\override MultiMeasureRest.expand-limit = #2
\melodyGlobal
}
>>


David Elaine Alt
415 . 341 .4954   "*Confusion is
highly underrated*"
ela...@flaminghakama.com
self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

opus and piece fields in top level header.

[Richard Shann]

In the 2.18 it does not seem to mention that the opus and piece fields
are not output anywhere if they are set in a \header{} block *outside*
any \score{} block, but this seems to be the case.
It is not a problem, but I would like to be sure this is intended to be
the case as I have finally got round to creating a sane interface to the
titles from Denemo and I see that they should be available for setting
at the top level as they don't (?) do anything there.
If there is someone knowledgeable that can confirm this I'd be grateful

Richard



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

Re: Tweaking a footnote

[Vaughan McAlley]

On 9 October 2015 at 10:35, Simon Albrecht  wrote:
>> ...
> Don’t worry. The footnote engine is not well documented.
>
>> ...
> There’s much room for improvement in the footnote implementation.

True, and true. On the upside, Lilypond actually *has* footnotes that move
when the music moves. I typeset a 120-page mass with tens of footnotes.
That would have been really annoying in Finale 2012.

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

Re: Using \partial with TACET

[Pierre Perol-Schneider]

Hi Andrew,

How about:

\version "2.19.28"

tacet =
#(define-scheme-function (parser location str) (string?)
   #{
  \compressFullBarRests
  \once\override MultiMeasureRest.expand-limit = #1
  \once\override MultiMeasureRestNumber.font-name = "Vera Bold"
  \once\override MultiMeasureRestNumber.stencil =
#(lambda (grob)(grob-interpret-markup grob
   (markup #:whiteout #:pad-markup .8 str)))
  \once\override MultiMeasureRest.layer = #-2
  \once\override MultiMeasureRestNumber.layer = #-1
  \once\override MultiMeasureRestNumber.Y-offset = #-.5
   #})

tympanoMusic = {
  \time 2/4
  \clef bass
  \partial 8
  r8 |
  \tacet "Tacet" R2*54
  \bar "||" \break
  \time 3/4
  \tacet "Tacet bis Ende" R2.*29
  \bar "|."
}

theMusic = {
  \time 2/4
  \partial 8
  c'8 |
  \repeat unfold 32 c'2
  c'4 c'8
  \tempo\markup\sans\medium\fontsize #4 "Adagio" c'8 |
  \repeat unfold 21 c'2
  \bar "||" \break
  \time 3/4
  \repeat unfold 29 c'2.
  \tweak break-visibility #begin-of-line-invisible
  \mark\markup\musicglyph #"scripts.ufermata"
  \bar "||"
}

%% Part:
\score {
  \tympanoMusic
  \header { piece = "Part" }
}

%% Full score:
\score {
  <<
\new StaffGroup <<
  \new Staff \theMusic
  \new Staff \theMusic
>>
\new Staff \tympanoMusic
  >>
  \header { piece = "Full Score" }
  \layout {
\context {
  \Staff
  \RemoveEmptyStaves
}
  }
}

Cheers,
~Pierre

2015-10-08 21:46 GMT+02:00 N. Andrew Walsh :

> correct. Each movement has its own \score block, in which the starting
> meter is set with a single \time command at the top. Subsequent meter
> changes are handled by the \systembreaks variable.
>
> On Thu, Oct 8, 2015 at 9:32 PM, David Kastrup  wrote:
>
>> "N. Andrew Walsh"  writes:
>>
>> > duh, I am A Idiot, sorry. That needed some extra code to work. Here's a
>> > more comprehensive version:
>> >
>> > \version "2.19.28"
>> > \time 2/4
>> [...]
>>
>> Uh, this will set one score containing nothing but the time signature
>> change.  But this change will not propagate in any way to other scores.
>>
>> --
>> David Kastrup
>>
>
>
> ___
> 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: How to get X/Y-extent of a bezier-curve?

[David Kastrup]

Thomas Morley  writes:

> 2015-10-09 8:20 GMT+02:00 David Kastrup :
>> Thomas Morley  writes:
>>
>>> 2015-10-07 14:08 GMT+02:00 Thomas Morley :
>>>
 The code in my initial mail uses coord-rotate (not
 ly:stencil-rotate-absolute as in Jans suggestion)
 What do you think about this method?

 Ofcourse it was heavily simplified, maybe best to put up a patch to
 have the full code for more detailed discussion.
>>>
>>> I have to postpone uploading the patch, there are some glitches ...
>>>
>>> And one thing which has driven me crazy, before I found the culprit:
>>> `coord-rotate' has a problem which can be demonstrated with:
>>>
>>> (display (coord-rotate '(10 . 0) (/ PI 2)))
>>>
>>> Expected:   (0 . 10)
>>> Actually:  (6.12323399573677e-16 . 10.0)
>>>
>>> What's the best method to get the zero?
>>
>> coord-translate is written awfully (almost any intermediate use of atan
>> is an indicator of unnecessary contortions) but that's not the problem
>> here.  The problem is that GUILE stores floating point number as double
>> numbers (64 bits), and the MPU does its calculations, including
>> trigonometry, using long double arithmetic (80 bits on x86).
>> Consequently, there is no representation of PI in GUILE that would lead
>> to the expected results.
>
> Ok, thanks for the explanation.
>
>> When angles are represented un GUILE, you are probably indeed best off
>> using degrees rather than radians since small multiples of 45 are
>> exactly representable at any number resolution available to GUILE.
>
> Well, coord-rotate uses sin and cos for the final result. They both
> expect their argument as radians. Converting them with
> `degrees->radians' involves PI again.
> So far the obvious ...
>
> Consequently I tried to redefine coord-rotate without depending on PI
> or at least without trigonometric functions.
> Up to now without result.
> Actually, I have no clue how to.

Oh, that won't work.  But sin(0) and cos(0) are exact.  What one can do
is to divide the given number by PI/4, and truncate to get the octant in
question.

Then you do something like

cos (x), sin (x) for octants 0, 7
-sin (x-PI/2), -cos (x-PI/2) for octants 1, 2
-cos (x-PI), -sin (x-PI) for octants 3, 4
sin (x-3PI/2), cos (x-3PI/2) for octants 5, 6

and get the proper 0 and 1 for GUILE's ideas of PI, PI/2 and 3PI/2.  Or,
probably saner, for GUILE's ideas of 180, 90, and 270.  Namely work with
degrees even when dividing into octants and only convert to radians at
the very last moment.  When you do this stuff separately for every
octant, you get exact results where you really need them.

Probably the best you can do without reverting to C altogether.

>> The code used in ly:stencil-rotate-absolute looks like it might work
>> (though I'd write (a * (M_PI / 180.0)) rather than (a * M_PI /
>> 180.0)).
>
> If I understand this correctly (and I probably don't), I don't see how
> it would help.

stencil-rotate-absolute takes its angle in degrees and converts into
radians in a manner that seems more likely not to lose the necessary
precision.

-- 
David Kastrup

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

Re: How to get X/Y-extent of a bezier-curve?

[Thomas Morley]

2015-10-09 8:20 GMT+02:00 David Kastrup :
> Thomas Morley  writes:
>
>> 2015-10-07 14:08 GMT+02:00 Thomas Morley :
>>
>>> The code in my initial mail uses coord-rotate (not
>>> ly:stencil-rotate-absolute as in Jans suggestion)
>>> What do you think about this method?
>>>
>>> Ofcourse it was heavily simplified, maybe best to put up a patch to
>>> have the full code for more detailed discussion.
>>
>> I have to postpone uploading the patch, there are some glitches ...
>>
>> And one thing which has driven me crazy, before I found the culprit:
>> `coord-rotate' has a problem which can be demonstrated with:
>>
>> (display (coord-rotate '(10 . 0) (/ PI 2)))
>>
>> Expected:   (0 . 10)
>> Actually:  (6.12323399573677e-16 . 10.0)
>>
>> What's the best method to get the zero?
>
> coord-translate is written awfully (almost any intermediate use of atan
> is an indicator of unnecessary contortions) but that's not the problem
> here.  The problem is that GUILE stores floating point number as double
> numbers (64 bits), and the MPU does its calculations, including
> trigonometry, using long double arithmetic (80 bits on x86).
> Consequently, there is no representation of PI in GUILE that would lead
> to the expected results.

Ok, thanks for the explanation.

>
> When angles are represented un GUILE, you are probably indeed best off
> using degrees rather than radians since small multiples of 45 are
> exactly representable at any number resolution available to GUILE.

Well, coord-rotate uses sin and cos for the final result. They both
expect their argument as radians. Converting them with
`degrees->radians' involves PI again.
So far the obvious ...

Consequently I tried to redefine coord-rotate without depending on PI
or at least without trigonometric functions.
Up to now without result.
Actually, I have no clue how to.

Maybe I fallback to some rounding like Ed suggested (thanks for that)
Something at the lines of `close-enough?' from music-functions.scm

>
> The code used in ly:stencil-rotate-absolute looks like it might work
> (though I'd write (a * (M_PI / 180.0)) rather than (a * M_PI / 180.0)).

If I understand this correctly (and I probably don't), I don't see how
it would help.


Thanks,
  Harm

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

Re: Using \partial with TACET

[Pierre Perol-Schneider]

Fine, here it goes:

tacet =
#(define-music-function
(str)
(string?)
   #{
  \compressFullBarRests
  \once\override MultiMeasureRest.expand-limit = #1
  \once\override MultiMeasureRestNumber.font-name = "Vera Bold"
  \once\override MultiMeasureRestNumber.stencil =
#(lambda (grob)(grob-interpret-markup grob
   (markup #:whiteout #:pad-markup .8 str)))
  \once\override MultiMeasureRest.layer = #-2
  \once\override MultiMeasureRestNumber.layer = #-1
  \once\override MultiMeasureRestNumber.Y-offset = #-.5
   #})

2015-10-09 10:03 GMT+02:00 David Kastrup :

> Pierre Perol-Schneider  writes:
>
> > Hi Andrew,
> >
> > How about:
> >
> > \version "2.19.28"
> >
> > tacet =
> > #(define-scheme-function (parser location str) (string?)
> >#{
> >   \compressFullBarRests
>
> You mean define-music-function here, and in version 2.19.28 the
> "parser location" arguments are just unnecessary baggage.
>
> --
> David Kastrup
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Using \partial with TACET

[David Kastrup]

Pierre Perol-Schneider  writes:

> Hi Andrew,
>
> How about:
>
> \version "2.19.28"
>
> tacet =
> #(define-scheme-function (parser location str) (string?)
>#{
>   \compressFullBarRests

You mean define-music-function here, and in version 2.19.28 the
"parser location" arguments are just unnecessary baggage.

-- 
David Kastrup

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

Re: lyrics placement change from 2.18 to 2.19 ?

[David Kastrup]

Johannes Waldmann  writes:

> Hi.
>
> The following snippet is interpreted
> differently by 2.18.* and 2.19.* :
>
> \score {
> <<
> \new Staff { \key a \minor \relative c'' {
>   a1   \new Voice { c2 d2 } e1
> }}
> \addlyrics  { foo bar }
>>>
> }
>
> notes are displayed identically,
> but lyrics placement is changed:
>
> with 2.18.2,  foo -> a1, bar -> e1,
> with 2.19.27, foo -> a1, bar -> c2.
>
> This breaks a bunch of my scores (so I don't like it).
> Is this a bug? Or a bug-fix?

If you put \addlyrics to a staff, how can you expect one voice in the
staff to be relevant for the lyrics and another not?  LilyPond did not
do anything sensible here.  Try

\score {
  \new Staff { \key a \minor
	   \relative c'' {
		 a1   \new Voice { c2 d2 } e1
	   }
	   \addlyrics { foo bar }
	 }
}

> What is the relevant section of documentation?

What is the relevant section of documentation that would have promised
your version to work?

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