LilyPond hangs on os x
Hey all, I'm running LilyPond on the command line from Mac OS X and it is hanging right after printing the version. I downloaded several versions (stable, unstable, previous unstable) and it happens with all of them. This is a recent-ish development (about 5 days ago or so). Is there a tool I could use to diagnose on what function call the hangup happens? Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond hangs on os x
m...@mikesolomon.org m...@mikesolomon.org writes: Hey all, I'm running LilyPond on the command line from Mac OS X and it is hanging right after printing the version. I downloaded several versions (stable, unstable, previous unstable) and it happens with all of them. This is a recent-ish development (about 5 days ago or so). So what changed in your setup? Is there a tool I could use to diagnose on what function call the hangup happens? Have you tried running LilyPond under gdb? In that case, just pressing C-c should get you back into the debugger, and bt should give you a backtrace. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Doc: document \on-the-fly (2579) (issue 6347062)
http://codereview.appspot.com/6347062/diff/1002/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6347062/diff/1002/Documentation/notation/input.itely#newcode1017 Documentation/notation/input.itely:1017: @item (on-page nmbr) @tab is page number = nmbr? whoops - should be 'does', not 'is'. I'll change before committing. http://codereview.appspot.com/6347062/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Doc: document \on-the-fly (2579) (issue 6347062)
http://codereview.appspot.com/6347062/diff/1002/Documentation/notation/input.itely File Documentation/notation/input.itely (right): http://codereview.appspot.com/6347062/diff/1002/Documentation/notation/input.itely#newcode1017 Documentation/notation/input.itely:1017: @item (on-page nmbr) @tab is page number = nmbr? On 2012/07/06 07:31:08, Trevor Daniels wrote: whoops - should be 'does', not 'is'. I'll change before committing. Uh what? It is more correct as it is. Even if you choose to interpret page number = nmbr not as a mathematical state and read it aloud symbol by symbol, Does page number equals nmbr? is not grammatical either. If you care about spoken grammar, you need to ditch any verb. Otherwise is is just fine. http://codereview.appspot.com/6347062/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Doc: document \on-the-fly (2579) (issue 6347062)
On 2012/07/06 07:38:05, dak wrote: Yes, it's best to drop the verb. That is more consistent with the rest of the table. But we are nitpicking here, aren't we :) Done. http://codereview.appspot.com/6347062/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hauptstimme Brackets?
At 11:38 on 04 Jul 2012, Nathan wrote:
Here's a solution using markup paths and text spanners:
%%%
\version 2.14.2
hauptstimmeStart = \markup {
\path #0.25 #'((moveto 0 0)
(lineto 0 -2)
(moveto 0 -1)
(lineto 1 -1)
(moveto 1 0)
(lineto 1 -2)
(moveto 1 0)
(lineto 1.8 0))
}
nebenstimmeStart = \markup {
\path #0.25 #'((moveto 0 -2)
(lineto 0 0)
(lineto 1 -2)
(lineto 1 0)
(lineto 1.8 0))
}
hauptstimmeEnd = \markup {
\path #0.25 #'((moveto 0 0)
(lineto 0.8 0)
(lineto 0.8 -0.8))
}
hauptstimme = {
\once \override TextSpanner #'style = #'none
\once \override TextSpanner #'(bound-details left text) = \hauptstimmeStart
\once \override TextSpanner #'(bound-details right text) = \hauptstimmeEnd
}
nebenstimme = {
\once \override TextSpanner #'style = #'none
\once \override TextSpanner #'(bound-details left text) = \nebenstimmeStart
\once \override TextSpanner #'(bound-details right text) = \hauptstimmeEnd
}
\relative c' {
\hauptstimme
| c4\startTextSpan c4 c4 c4
| c4 c4 c4 c4\stopTextSpan
| c4 c4 c4 c4
\nebenstimme
| c4\startTextSpan c4 c4 c4
| c4 c4 c4 c4\stopTextSpan
}
%%%
This is very nice, but unfortunately repeats the symbols at line
breaks, which is not ideal. To avoid this, you probably want to add:
\once \override TextSpanner #'(bound-details left-broken text) = ##f
\once \override TextSpanner #'(bound-details right-broken text) = ##f
--
Mark Knoop
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tunefl and other web services
On 05/07/12 22:03, David Kastrup wrote: It also means bad compatibility with GPL. And a license change. What's the bad compatibility you have in mind? AGPLv3 is compatible with any code licensed GPLv2 or later. LilyPond is already on GPLv3 or later, which has the same issues with GPLv2-only code. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tunefl and other web services
Joseph Rushton Wakeling joseph.wakel...@webdrake.net writes: On 05/07/12 22:03, David Kastrup wrote: It also means bad compatibility with GPL. And a license change. What's the bad compatibility you have in mind? AGPLv3 is compatible with any code licensed GPLv2 or later. I don't see that GPLv2 permits additional restrictions to be added to the work as a whole. The requirement to make the source available to anybody using a service supplied by the software is an additional restriction. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hauptstimme Brackets?
2012/7/6 Mark Knoop m...@opus11.net:
At 11:38 on 04 Jul 2012, Nathan wrote:
Here's a solution using markup paths and text spanners:
%%%
\version 2.14.2
hauptstimmeStart = \markup {
\path #0.25 #'((moveto 0 0)
(lineto 0 -2)
(moveto 0 -1)
(lineto 1 -1)
(moveto 1 0)
(lineto 1 -2)
(moveto 1 0)
(lineto 1.8 0))
}
nebenstimmeStart = \markup {
\path #0.25 #'((moveto 0 -2)
(lineto 0 0)
(lineto 1 -2)
(lineto 1 0)
(lineto 1.8 0))
}
hauptstimmeEnd = \markup {
\path #0.25 #'((moveto 0 0)
(lineto 0.8 0)
(lineto 0.8 -0.8))
}
hauptstimme = {
\once \override TextSpanner #'style = #'none
\once \override TextSpanner #'(bound-details left text) = \hauptstimmeStart
\once \override TextSpanner #'(bound-details right text) = \hauptstimmeEnd
}
nebenstimme = {
\once \override TextSpanner #'style = #'none
\once \override TextSpanner #'(bound-details left text) = \nebenstimmeStart
\once \override TextSpanner #'(bound-details right text) = \hauptstimmeEnd
}
\relative c' {
\hauptstimme
| c4\startTextSpan c4 c4 c4
| c4 c4 c4 c4\stopTextSpan
| c4 c4 c4 c4
\nebenstimme
| c4\startTextSpan c4 c4 c4
| c4 c4 c4 c4\stopTextSpan
}
%%%
This is very nice, but unfortunately repeats the symbols at line
breaks, which is not ideal. To avoid this, you probably want to add:
\once \override TextSpanner #'(bound-details left-broken text) = ##f
\once \override TextSpanner #'(bound-details right-broken text) = ##f
--
Mark Knoop
Hi,
I've put it into the LSR, adding Mark's suggestion and some own
trickery to make it work with customized staff-sizes.
(postscript scales with global-staff-size only)
http://lsr.dsi.unimi.it/LSR/Item?u=1id=843
Any suggestion to improve it (or my bad english)?
-Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Hauptstimme Brackets?
Am 04.07.2012 20:55, schrieb Nick Baskin: On Wed, Jul 4, 2012 at 2:40 PM, Thomas Morley thomasmorle...@googlemail.com mailto:thomasmorle...@googlemail.com wrote: 2012/7/4 Nick Baskin amphio...@gmail.com mailto:amphio...@gmail.com: Hey all, Is there any way to create Hauptstimme and Nebenstimme brackets in LilyPond? My searches of the manual, LSR, and recent list archives have not been fruitful. I am using version 2.14.2. Cheers, Nick Baskin What is Hauptstimme and Nebenstimme brackets? I'm a native german speaker, but I really don't understand what you're writing. Could you provide an example? -Harm @Nathan: Brilliant! This is just what I needed. Thanks! @Thomas/Harm: Hauptstimme and Nebenstimme brackets are used to show which voices in a thick texture are the most important ones. My understanding is that they were first invented by Schoenberg, but this could be incorrect. There is a little information on the English Wikipedia here: http://en.wikipedia.org/wiki/Hauptstimme , Quite correct, but Hauptstimme and Hauptsatz or Nebenstimme and Seitensatz really aren't equivalent. but the German Wikipedia article it links to appears to be about something rather different. (My German is not good enough to tell for certain, though, sorry!) No, this link is quite nonsensical. The German article isn't really related to the topic. Best Urs ~Nick Baskin -- And she forgot the stars, the moon, and sun, And she forgot the blue above the trees, And she forgot the dells where waters run, And she forgot the chilly autumn breeze... --- Keats, Isabella, or the Pot of Basil ___ 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: LSR snippet Controlling of the pitch range in a score broken at 2.15.40
Patrick or Cynthia Karl pck...@mac.com writes:
The LSR snippet Controlling of the pitch range in a score contains
the code for a function, colorizeOutOfRange. This function works at
2.14.2, but doesn't at 2.15.40.
This can be demonstrated by compiling the following:
\include ./colorize.ly
music = \relative c' { c d e f g a b }
\new Staff { \colorizeOutOfRange d' a' \music }
where the file colorize.ly contains the following code from the cited snippet:
colorizeOutOfRange = #(define-music-function (parser location
low-note high-note music )(ly:music? ly:music?
ly:music?)
Colorizes in red notes out of range `low-note `high-note
(let* (
(low-elts (ly:music-property low-note 'elements))
(high-elts (ly:music-property high-note 'elements))
(low-pitch (and (pair? low-elts)
(ly:music-property (car low-elts) 'pitch)))
(high-pitch (and (pair? high-elts)
(ly:music-property (car high-elts) 'pitch
(if (and (ly:pitch? low-pitch)
(ly:pitch? high-pitch)
(ly:pitch? low-pitch high-pitch))
(music-map
(lambda (evt)
(let ((p (ly:music-property evt 'pitch)))
(if (and (ly:pitch? p)
(or (ly:pitch? p low-pitch)
(ly:pitch? high-pitch p)))
(let ((tweaks (ly:music-property evt 'tweaks)))
(ly:music-set-property! evt 'tweaks
(acons 'color red tweaks
evt))
music)
music)))
When compiled with lilypond 2.14.2 the notes c and b are colored red.
When compiled with lilypond 2.15.40, all notes are black.
Does anyone know a fix for colorizeOutOfRange?
It relies on a complex structure of music internals to pick out pitches
from its arguments. This structure has changed. Fortunately, 2.15.40
makes it much much easier to get pitches from music function arguments,
so the following reduction of the complex original code will do the
trick:
colorizeOutOfRange =
#(define-music-function (parser location low-pitch high-pitch music)
(ly:pitch? ly:pitch? ly:music?)
Colorizes in red notes out of range `low-pitch `high-pitch
(if (ly:pitch? low-pitch high-pitch)
(music-map
(lambda (evt)
(let ((p (ly:music-property evt 'pitch)))
(if (and (ly:pitch? p)
(or (ly:pitch? p low-pitch)
(ly:pitch? high-pitch p)))
(let ((tweaks (ly:music-property evt 'tweaks)))
(ly:music-set-property! evt 'tweaks
(acons 'color red tweaks
evt))
music)
music))
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR snippet Controlling of the pitch range in a score broken at2.15.40
- Original Message -
From: Patrick or Cynthia Karl pck...@mac.com
To: lilypond-user@gnu.org
Sent: Friday, July 06, 2012 5:07 PM
Subject: LSR snippet Controlling of the pitch range in a score broken
at2.15.40
The LSR snippet Controlling of the pitch range in a score contains the
code for a function, colorizeOutOfRange. This function works at 2.14.2,
but doesn't at 2.15.40.
This can be demonstrated by compiling the following:
\include ./colorize.ly
music = \relative c' { c d e f g a b }
\new Staff { \colorizeOutOfRange d' a' \music }
where the file colorize.ly contains the following code from the cited
snippet:
colorizeOutOfRange = #(define-music-function (parser location
low-note high-note music )(ly:music? ly:music?
ly:music?)
Colorizes in red notes out of range `low-note `high-note
(let* (
(low-elts (ly:music-property low-note 'elements))
(high-elts (ly:music-property high-note 'elements))
(low-pitch (and (pair? low-elts)
(ly:music-property (car low-elts) 'pitch)))
(high-pitch (and (pair? high-elts)
(ly:music-property (car high-elts) 'pitch
(if (and (ly:pitch? low-pitch)
(ly:pitch? high-pitch)
(ly:pitch? low-pitch high-pitch))
(music-map
(lambda (evt)
(let ((p (ly:music-property evt 'pitch)))
(if (and (ly:pitch? p)
(or (ly:pitch? p low-pitch)
(ly:pitch? high-pitch p)))
(let ((tweaks (ly:music-property evt 'tweaks)))
(ly:music-set-property! evt 'tweaks
(acons 'color red tweaks
evt))
music)
music)))
When compiled with lilypond 2.14.2 the notes c and b are colored red.
When compiled with lilypond 2.15.40, all notes are black.
Does anyone know a fix for colorizeOutOfRange?
Have you tried updating it with convert-ly?
http://lilypond.org/doc/v2.15/Documentation/usage/invoking-convert_002dly
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LSR snippet Controlling of the pitch range in a score broken at2.15.40
Phil Holmes m...@philholmes.net writes:
colorizeOutOfRange = #(define-music-function (parser location
low-note high-note music )(ly:music?
ly:music? ly:music?)
Colorizes in red notes out of range `low-note `high-note
(let* (
(low-elts (ly:music-property low-note 'elements))
(high-elts (ly:music-property high-note 'elements))
(low-pitch (and (pair? low-elts)
(ly:music-property (car low-elts) 'pitch)))
(high-pitch (and (pair? high-elts)
(ly:music-property (car high-elts) 'pitch
When compiled with lilypond 2.14.2 the notes c and b are colored
red. When compiled with lilypond 2.15.40, all notes are black.
Does anyone know a fix for colorizeOutOfRange?
Have you tried updating it with convert-ly?
Would not help. It relies on single notes being wrapped inside of
EventChord which is no longer the case. It was a change to the
internals making a lot of things easier or possible to do in the first
place (fully functional music functions inside of chords, tweaks working
on single notes, q implemented in a reliably robust way, #{ ... #} being
useful inside of chords and other things).
Much more straightforward, but incompatible. One could have band-aid
patched the code by putting
(set! low-note (event-chord-wrap! low-note parser))
(set! high-note (event-chord-wrap! high-note parser))
in, but it was much easier to just create a working replacement (posted
separately) that does not even need to dig into the internals.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Document use of alignAboveContext and alignBelowContext (issue 6353079)
One suggestion, otherwise LGTM. Thanks. http://codereview.appspot.com/6353079/diff/1/Documentation/notation/vocal.itely File Documentation/notation/vocal.itely (right): http://codereview.appspot.com/6353079/diff/1/Documentation/notation/vocal.itely#newcode1327 Documentation/notation/vocal.itely:1327: One for Graham really, but it strikes me as wrong to add an example showing what is effectively incorrect output. I would have thought it better to simply say the lyrics go below the bottom staff unless you tell them explicitly where to go like this... http://codereview.appspot.com/6353079/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics in color
On Mon, 02 Jul 2012 21:03:46 +0400, Aleksandr Andreev aleksandr.andr...@gmail.com wrote: Why is this important? It would need to be possible to support Znamenny neumatic notation, as in the following example, done in Finale: http://ecmr.t5.fi/Transcripta/KalSamogl.pdf (except that Finale does not support this -- the modifier marks on the neumes, e.g., the н, р, etc) need to be in red, not black. Aleksandr Hi, Aleksandr! David Nalesnik did a great work helping me to deal with Znamenny notation, he already gave you the links, but you also can contact me, I can give you some working examples with more tricks (I have something like a file framework with includes to make things wery easy) and may be you have some too. My native language is Russian, so if you decide write me directly you can use it. Seems, we are doing the same work with Oktay, so just look on my results with Lilypond and LaTeX: https://www.dropbox.com/s/1x1oeom2jfe1i72/oktoih.pdf?m ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics in color
Hi David! I feel very sorry that I didn't manage to make a good example for LSR that days. Assembling the real scores was so exciting. If you will be so kind to help me to accomplish this work, I'll make files for LSR till this weekend. Hoping, that you'll excuse me, Svetlana. On Mon, 02 Jul 2012 21:16:54 +0400, David Nalesnik david.nales...@gmail.com wrote: Some time ago, I worked on functions to automate coloring of Znamenny chant. The thread is found here: http://www.mail-archive.com/lilypond-user@gnu.org/msg68263.html and the last version of the file is found here (the thread seems a little tangled): http://www.mail-archive.com/lilypond-user@gnu.org/msg68583.html Hopefully this will be of use to you! -David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tunefl and other web services
On 06/07/12 14:49, David Kastrup wrote: I don't see that GPLv2 permits additional restrictions to be added to the work as a whole. The requirement to make the source available to anybody using a service supplied by the software is an additional restriction. GPLv2 or later means that you can interpret the work as being covered instead by GPLv3, which _is_ compatible with AGPLv3. It's only if you have an explicit GPLv2-only licence that you have an issue here. For this latter case, is there a specific concern that you have here, or only a general one? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: tunefl and other web services
Joseph Rushton Wakeling joseph.wakel...@webdrake.net writes: On 06/07/12 14:49, David Kastrup wrote: I don't see that GPLv2 permits additional restrictions to be added to the work as a whole. The requirement to make the source available to anybody using a service supplied by the software is an additional restriction. GPLv2 or later means that you can interpret the work as being covered instead by GPLv3, This is not a question of reinterpretation or optional. You _can't_ license redistributed works under GPLv2 if the work as a whole contains AGPLv3 components. Once you made use of the relicensing and upstream did not, changes from you can't be contributed upstream by anybody else under GPLv2. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
