RE: lilypond: ps2pdf not found
No, actually pstools is not needed (and it is called psutil). ps2pdf is in the ghostscript package Harald, please run cygwin setup again and ensure that the ghostscript (and ghostscript-base) package is selected. (Ghostscript is in requires) > > install pstools > > Shouldn't this be added to requires:? ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: 2.1.25 Compile problems
Am 23.02.2004 um 04:52 schrieb Walter Hofmeister: Any ideas? I have upgraded the OS to 10.3.2 since my last build and suspect that this could be a problem but I have installed and re-installed all of the developers tools. Any other Mac users out there ever seen this before. I am not a programmer but I do recognize that malloc problems are funtions to allocate memory. Does this look like an incomplete installation or a problem with the source? I've tried to install lily in the same way and I got the same results. 2.1.21 was the last version that I could install. I attach the output of gdb. The problem seems to lie in a file called gc.c (garbage collector?). I think MacOS X is less forgiving with double free()'s than linux is. Christian System: macos x 10.3.2 G4:/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/out chhitz$ gdb /sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/lily/out/lilypond-bin GNU gdb 5.3-20030128 (Apple version gdb-309) (Thu Dec 4 15:41:30 GMT 2003) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "powerpc-apple-darwin". Reading symbols for shared libraries .. done (gdb) run --verbose /sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/ly/generate-documentation Starting program: /sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/lily/out/lilypond-bin --verbose /sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/ly/generate-documentation Reading symbols for shared libraries .. done lilypond_datadir: `/sw/share/lilypond' local_lilypond_datadir: `/sw/share/lilypond/2.1.25' localedir: `/sw/share/locale' LILYPONDPREFIX: `/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond' Reading symbols for shared libraries . done [/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/define-music-types.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/output-lib.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/c++.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/chord-ignatzek-names.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/chord-entry.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/chord-generic-names.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/stencil.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/new-markup.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/bass-figure.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/music-functions.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/part-combiner.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/define-music-properties.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/auto-beam.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/chord-name.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/define-context-properties.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/translation-functions.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/script.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/midi.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/beam.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/clef.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/slur.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/font.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/define-markup-commands.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/define-grob-properties.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/define-grobs.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/define-grob-interfaces.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/paper.scm] Bearbeite: `/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/ly/generate-documentation.ly' Analysiere...[/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/init.ly[/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/declarations-init.ly[/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/nederlands.ly][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/drumpitch-init.ly][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/chord-modifiers-init.ly][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/script-ini
Re: reduce spacing between chord names and staff?
Paul Scott wrote:
Mats Bengtsson wrote:
This is controlled by the |minimumVerticalExtent| property of the two
involved
contexts, namely ChordNames and Staff. However, by default the ChordNames
don't extend below zero, so you probably have to reduce the upper value
(= the second value) of the property for Staff. Note that this may
affect also
other spacings in the score.
See
http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond-internals/Staff.html#Staff
and
http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Vertical-spacing.html#Vertical%20spacing
That's what I thought.
Ok. With some experimentation I got it to work but from my experiments I
discovered that \set creates a new staff. The following creates the
staff above the chords:
\version "2.1.25"
\header { title= "Chord Space Test" }
\score {
<<
\set Staff.minimumVerticalExtent = #'(-0 . 1)
\context ChordNames \chords{ a b c d }
\context Staff \notes{ a'4 b' c' d' }
>>
}
Is this what is intended? Where is this feature of \set described?
Haven't you asked almost the same question before?
\set Staff.xxx = xxx sets a property value in the current
Staff context. If there is no such context, LilyPond has to
create one to be able to do the setting. Two lines later, you
create a new Staff context.
You have to do the setting within the context you want to affect:
\score {
<<
\context ChordNames \chords{ a b c d }
\context Staff \notes{
\set Staff.minimumVerticalExtent = #'(-0 . 1)
a'4 b' c' d' }
>>
}
In recent development versions, you also have the following convenient
syntax:
\score {
<<
\context ChordNames \chords{ a b c d }
\context Staff \notes \with { minimumVerticalExtent = #'(-0 . 1) }
{ a'4 b' c' d' }
>>
}
/Mats
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: 2.1.25 Compile problems
Hello Walter, [...] > -2.1.25/share/lilypond/scm/document-markup.scm]*** malloc[6369]: > Deallocation of a pointer not malloced: 0x2b8aa08; This could be a double > free(), or free() called with the middle of an allocated block; Try setting > environment variable MallocHelp to see tools to help debug [...] > -2.1.25/share/lilypond/scm/document-markup.scm]*** malloc[12770]: > Deallocation of a pointer not malloced: 0x2b8aa08; This could be a double > free(), or free() called with the middle of an allocated block; Try setting > environment variable MallocHelp to see tools to help debug [...] > ### execution of gnumake failed, exit code 2 > Failed: installing lilypond-unstable-2.1.25-1 failed > > Any ideas? I have upgraded the OS to 10.3.2 since my last build and suspect > that this could be a problem but I have installed and re-installed all of > the developers tools. Any other Mac users out there ever seen this before. > I am not a programmer but I do recognize that malloc problems are funtions > to allocate memory. Does this look like an incomplete installation or a > problem with the source? I think you may have a very good compiler and that it might be a problem with the source. From the release notes of 2.1.25: -- For the past few days, I've received reports about hard-to trace crashes in LilyPond 2.1.22 and 2.1.23. If you are affected by signal 11 faults, then can you try this release to see if it fixes these problems? If not, please send a full bugreport (including platform description and compilation options) to [EMAIL PROTECTED] -- I my own project I have seen similar symptoms (crashing at any random new statement) and there it was caused by a malloc/free mistake. So I guess it would be nice if you could tell which compiler (+version) you use, and then a Mac hacker (IANAMH) might follow up on the MallocHelp hint. Probably the readers of [EMAIL PROTECTED] would be interested in this as well. David Boersma ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
lilypond-user@gnu.org
Reuben Thomas wrote: Another basic question, but again, I can't find the answer in the docs: does LilyPond (2.1.25 in my case) have standard text styles for expression markings, tempo markings &c.? All I've found in the docs and from pieces on mutopia.org is ad-hoc font settings (using \bold, \italic, \large &c.) which seems rather unsatisfactory. You are not the only one, see http://mail.gnu.org/archive/html/lilypond-user/2004-02/msg00012.html /Mats ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: reduce spacing between chord names and staff?
Mats Bengtsson wrote:
Paul Scott wrote:
\score {
<<
\set Staff.minimumVerticalExtent = #'(-0 . 1)
\context ChordNames \chords{ a b c d }
\context Staff \notes{ a'4 b' c' d' }
>>
}
Is this what is intended? Where is this feature of \set described?
Haven't you asked almost the same question before?
Not intentionally. You may have actually answered it in one of our
recent threads but if so I didn't get the full meaning at that time. So
far I have found examples of the context syntax in the manual but not a
clear explanation of how it works. I probably should have done the
experimenting I just did before this.
\set Staff.xxx = xxx sets a property value in the current
Staff context.
Where those properties were stored was not clear until now.
If there is no such context, LilyPond has to
create one to be able to do the setting. Two lines later, you
create a new Staff context.
You have to do the setting within the context you want to affect:
\score {
<<
\context ChordNames \chords{ a b c d }
\context Staff \notes{
\set Staff.minimumVerticalExtent = #'(-0 . 1)
a'4 b' c' d' }
>>
}
In recent development versions, you also have the following convenient
syntax:
\score {
<<
\context ChordNames \chords{ a b c d }
\context Staff \notes \with { minimumVerticalExtent = #'(-0 . 1) }
{ a'4 b' c' d' }
>>
}
Thanks. It's a big manual and so far I hadn't seen a clear enough
example of the syntax for '\with'. Of course now when I search for
'\with' in the manual I find more.
Thanks for your patience,
Paul
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Piano markings question
In the definition of the Dynamics context, just add the line
\override TextScript #'padding = #0
or maybe
\override TextScript #'padding = #-1
/Mats
Reuben Thomas wrote:
I've used the hack in the Lilypond docs for getting dynamics centred
between the staves of a PianoStaff, but I would like to make it more
convenient to do other markings. At the moment, I can write something like
s1\f
to get a piano dynamic which is nicely centred, but if I write another
marking, e.g.
s1^\markup { espress. }
then it's too high (or I can try s1_\markup { ... }, but it's too low). I
can't use \markup without ^ or _ because then I'm not in Lyric mode, which
is how markings seem to be implemented. Basically I'd like another hack
that reverses the raising effect of ^, so that I can use ^ and the text
generated by markup will be level with the dynamics generated by the
dynamics commands. Of course, I don't want to have to put a \raise command
before every \markup.
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Again: \rest spacing
[EMAIL PROTECTED] writes: > Hello, > > maybe my last post was not clear enough, so I try again: > In polyphonic situations the vertical position of rests entered with > \rest is not as expected. thanks, fixed. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
lilypond-user@gnu.org
[EMAIL PROTECTED] writes: > Another basic question, but again, I can't find the answer in the docs: > does LilyPond (2.1.25 in my case) have standard text styles for expression > markings, tempo markings &c.? All I've found in the docs and from pieces > on mutopia.org is ad-hoc font settings (using \bold, \italic, \large &c.) > which seems rather unsatisfactory. No; you're welcome to add them as \markup commands, though. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Piano markings question
[EMAIL PROTECTED] writes: > In the definition of the Dynamics context, just add the line >\override TextScript #'padding = #0 > > or maybe > >\override TextScript #'padding = #-1 The hack in the templates section add extra-offset for the dynamics. Maybe you could add that for TextScripts too? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Again: \rest spacing
On Monday 23 February 2004 02:33, Thomas Scharkowski wrote: > Hello, > > maybe my last post was not clear enough, so I try again: > In polyphonic situations the vertical position of rests entered with > \rest is not as expected. > The attached code produces correct positions for bar 1 (which is > "monophonic" and wrong positions for bar 2, which is polyphonic. > I am quite sure this did not appear in previous versions. > > Thank you > Thomas > 2.1.25 on cygwin/xp I suggested long ago that since rests are basically cues for the following note in the voice, that they should take their default pitch from that note. When a rest is simultaneous with a stem in another voice, and there is necessary collision because there are 3 or more parts on the staff and the rest is an inside part, the rest is placed *before* the stem, even if the stem is down. That rule is not in any published book that I know of, but I have many examples from as early as 1810, and I have seen it on the web. -- It's not that hard to understand the lesson of Viet Nam. Never never never never defend one tyrant against another, because The worst thing that can happen is you might win. The *Gulf* war was worse than Nam. D. Raleigh Arnold dra@ (http://www.) openguitar.com [EMAIL PROTECTED] ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Piano markings question
The problem was to improve the example hack for piano dynamics being centred between the staves so that it works for other expression marks. Matts suggested: > In the definition of the Dynamics context, just add the line >\override TextScript #'padding = #0 > > or maybe > >\override TextScript #'padding = #-1 While Han-Wen said: > The hack in the templates section add extra-offset for the > dynamics. Maybe you could add that for TextScripts too? I can't get any of these to work exactly, though I could if I fiddled the numbers a bit. But rather than just fiddle I'd prefer to know what's going on. There are two issues: 1. I'd like to understand what the two alternative approaches are doing above, and why I should choose one rather than the other. In particular, I don't want to use magic numbers (which the existing hack already seems to do, e.g. \override DynamicText #'extra-offset = #'(0 . 2.5) \override Hairpin #'extra-offset = #'(0 . 2.5) where does the 2.5 come from? 2. Neither approach above, nor the existing stuff, seems to affect \cresc .. \endcresc, which still puts its text too low. It would be nice to sort this out so that it can be fed back to improve the manual example. -- http://www.mupsych.org/~rrt/ | The old cliches are the best ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
lilypond-user@gnu.org
> [EMAIL PROTECTED] writes: > > Another basic question, but again, I can't find the answer in the docs: > > does LilyPond (2.1.25 in my case) have standard text styles for expression > > markings, tempo markings &c.? All I've found in the docs and from pieces > > on mutopia.org is ad-hoc font settings (using \bold, \italic, \large &c.) > > which seems rather unsatisfactory. > > No; you're welcome to add them as \markup commands, though. Thanks, I'm doing that. When I have a bit of experience and a reasonable set of commands, I'll post them. -- http://www.mupsych.org/~rrt/ | fantasize, a. the largest you can imagine ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: 2.1.25 Compile problems
On Feb 22, 2004, at 9:52 PM, Walter Hofmeister wrote: Hello All, I have been trying to get 2.1.25 to install under Fink on OS X and have had some problems. The method is as follows: 1. Download the source tarball and and the lilypond-2.1.25-1.i386.rpm file and place them in the folder /sw/src (this is where Fink is going to look for source). 2. Locate the Lilypond-unstable.info and the lilypond-unstable.patch file and open them using a text editor. Change all instances of 2.1.x (2.1.17 in my case) to 2.1.25. 3. In Terminal run the command: fink index (This will rebuild the fink database so that it knows there is a new version). 4. Run: fink list (to verify that it now knows there is a new version.) 5. Run: fink install lilypond-unstable Away it goes for about 10 -12 minutes untill I get: A lot of stuff left out Now processing: `/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/ly/generate- documentatio n.ly' Parsing...[/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/ lilypond /ly/init.ly[/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/ lilypon d/ly/declarations-init.ly[/sw/src/lilypond-unstable-2.1.25-1/lilypond -2.1.25 /share/lilypond/ly/nederlands.ly][/sw/src/lilypond-unstable-2.1.25-1/ lilypon d-2.1.25/share/lilypond/ly/drumpitch-init.ly][/sw/src/lilypond- unstable-2.1. 25-1/lilypond-2.1.25/share/lilypond/ly/chord-modifiers-init.ly][/sw/ src/lily pond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/script- init.ly][/sw /src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/ scale-defi nitions-init.ly][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/ share/li lypond/ly/grace-init.ly][/sw/src/lilypond-unstable-2.1.25-1/lilypond -2.1.25/ share/lilypond/ly/midi-init.ly[/sw/src/lilypond-unstable-2.1.25-1/ lilypond-2 .1.25/share/lilypond/ly/performer-init.ly]][/sw/src/lilypond-unstable -2.1.25 -1/lilypond-2.1.25/share/lilypond/ly/engraver-init.ly][/sw/src/ lilypond-unst able-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/dynamic-scripts- init.ly][/sw /src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/ spanners-i nit.ly][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/ lilypond/ly /property-init.ly]][/sw/src/lilypond-unstable-2.1.25-1/lilypond -2.1.25/ly/ge nerate-documentation.ly[/sw/src/lilypond-unstable-2.1.25-1/lilypond -2.1.25/s hare/lilypond/scm/documentation-lib.scm][/sw/src/lilypond-unstable -2.1.25-1/ lilypond-2.1.25/share/lilypond/scm/document-functions.scm][/sw/src/ lilypond- unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/scm/document- translation.sc m][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ scm/doc ument-music.scm][/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/ share/li lypond/scm/document-backend.scm][/sw/src/lilypond-unstable-2.1.25-1/ lilypond -2.1.25/share/lilypond/scm/document-markup.scm]*** malloc[6369]: Deallocation of a pointer not malloced: 0x2b8aa08; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug *** malloc[6369]: Deallocation of a pointer not malloced: 0x2b8ab68; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug *** malloc[6369]: Deallocation of a pointer not malloced: 0x2b8aba8; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug *** malloc[6369]: Deallocation of a pointer not malloced: 0x2b8abf0; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug *** malloc[6369]: Deallocation of a pointer not malloced: 0x2b8abf8; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug gnumake[2]: *** [out/lilypond-internals.texi] Error 138 gnumake[1]: *** [all] Error 2 gnumake: *** [all] Error 2 Followed by more stuff left out, then: Now processing: `/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/ly/generate- documentatio n.ly' Parsing...[/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/ lilypond /ly/init.ly[/sw/src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/ lilypon d/ly/declarations-init.ly[/sw/src/lilypond-unstable-2.1.25-1/lilypond -2.1.25 /share/lilypond/ly/nederlands.ly][/sw/src/lilypond-unstable-2.1.25-1/ lilypon d-2.1.25/share/lilypond/ly/drumpitch-init.ly][/sw/src/lilypond- unstable-2.1. 25-1/lilypond-2.1.25/share/lilypond/ly/chord-modifiers-init.ly][/sw/ src/lily pond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/script- init.ly][/sw /src/lilypond-unstable-2.1.25-1/lilypond-2.1.25/share/lilypond/ly/ scale-defi nitions-init.ly][/sw/src/lilypond-unstable-2.1.25-1/lilypond-
Re: 2.1.25 Compile problems
I've had the same result with the same setup. I'm hoping the maintainer (Matthias Neeracher <[EMAIL PROTECTED]> ) will update the fink files soon! I sent a request to that effect. If you look at the mailing list archives for lilypond-user, lilypond-develop and bug-lilypond for the last week, you will see that this problem is not specific for Fink. Han-Wen hoped to have solved it in 1.2.26 but it seems there are still some problems. /Mats ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: 2.1.25 Compile problems
[EMAIL PROTECTED] writes: > > I've had the same result with the same setup. I'm hoping the > > maintainer (Matthias Neeracher <[EMAIL PROTECTED]> ) will update > > the fink files soon! I sent a request to that effect. > > If you look at the mailing list archives for lilypond-user, > lilypond-develop and bug-lilypond for the last week, you will > see that this problem is not specific for Fink. Han-Wen hoped > to have solved it in 1.2.26 but it seems there are still some > problems. The problem that Erik reported was unrelated to the memory corruption bugs. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: 2.1.25 Compile problems
I've had the same result with the same setup. I'm hoping the maintainer (Matthias Neeracher <[EMAIL PROTECTED]> ) will update the fink files soon! I sent a request to that effect. If you look at the mailing list archives for lilypond-user, lilypond-develop and bug-lilypond for the last week, you will see that this problem is not specific for Fink. Han-Wen hoped to have solved it in 1.2.26 but it seems there are still some problems. /Mats I installed 1.2.26 today via fink. The mentioned install problems do not appear in this version. Christian [System: macos x 10.3.2] ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: 2.1.25 Compile problems
Op ma 23-02-2004, om 17:53 schreef Mats Bengtsson: > If you look at the mailing list archives for lilypond-user, > lilypond-develop and bug-lilypond for the last week, you will > see that this problem is not specific for Fink. Do you mean it's a PowerPC problem, or even broader? > Han-Wen hoped > to have solved it in 1.2.26 but it seems there are still some > problems. Looking forward to it. Here's someone eager to test it. Mark Debian GNU/Linux Unstable & Mac Os X 10.3.x on PPC -- Mark Van den Borre Noormannenstraat 113 3000 Leuven, Belgià +32 486 961726 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: 2.1.25 Compile problems
On Feb 23, 2004, at 11:30 AM, Christian Hitz wrote: I've had the same result with the same setup. I'm hoping the maintainer (Matthias Neeracher <[EMAIL PROTECTED]> ) will update the fink files soon! I sent a request to that effect. If you look at the mailing list archives for lilypond-user, lilypond-develop and bug-lilypond for the last week, you will see that this problem is not specific for Fink. Han-Wen hoped to have solved it in 1.2.26 but it seems there are still some problems. /Mats I installed 1.2.26 today via fink. The mentioned install problems do not appear in this version. Christian [System: macos x 10.3.2] Christian- Thanks for posting.. I was also successful in updating to 1.2..26on to testing it!! Stan ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Mac OS X 10.3.2 bugs/compile errors
Greetings, I have been using lilypond 2.0.1-16 from fink for about 2 weeks now. I have been transcribing some orchestral music and have noticed a bug (either in my document or lilypond) with multi-measure rests. Basically, the first multi-measure rest is rendered beautifully, but subsequent ones aren't. I have attached my source and the pdf. Assuming this is a bug in lilypond, I attempted to build from CVS, but hit these compile errors: g++ -shared -o out/midi.so out/midi.lo -L/sw/lib -L/sw/lib -lguile -lguile-ltdl -lm g++: unrecognized option `-shared' ld: Undefined symbols: _main _PyArg_ParseTuple _PyDict_SetItemString _PyErr_SetString _PyInt_FromLong _PyList_Append _PyList_New _PyModule_GetDict _PyString_FromString _PyTuple_GetItem _Py_BuildValue _Py_InitModule4 make[1]: *** [out/midi.so] Error 1 make: *** [all] Error 2 I looked at the code but could not find any of these symbols in midi.c (I didn't look hard -- I figured it was some python thing... I don't do python). I last cvs up'ed on 2004.02.23 at 20:15 GMT. Any insights into the nature of these bugs/erros is greatly apperciated. --Matthew Peltzer 01-Power.ly Description: application/text 01-Power.pdf Description: Adobe PDF document ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Possibly OT Problems creating bounded pdf
Hi all, This may be off topic but I'm using lilypond to create figures to use in my thesis but am having problems creating bounded pdf files. The reason I require bounded pdf is that I am using context and not latex. Has any got any suggestions?? I can create eps fine but it is the conversion from eps to pdf which is not keeping the bounding box. Adam ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Possibly OT Problems creating bounded pdf
On Mon, 23 Feb 2004, Adam Tee wrote: > Hi all, > > This may be off topic but I'm using lilypond to create figures to use > in my thesis but am having problems creating bounded pdf files. > The reason I require bounded pdf is that I am using context and not > latex. Has any got any suggestions?? I can create eps fine but it is > the conversion from eps to pdf which is not keeping the bounding box. > How do you do the conversion? The 'epstopdf' script usually works fine for me. On my linux machine it is installed through the tetex package. Otherwise: please give more specs on what kind of platform (apple, linux, windows; plus version), which tex/context versions you have etc.. David Boersma > > Adam > > > ___ > Lilypond-user mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/lilypond-user > -- David Boersma /"\ ASCII ribbon campaign \ / - X against HTML mail / \ and postings ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Editoral vertical brackets
How can I draw editorial brackets [ ] around some notes? [I'd like to take this opportunity to thank everyone for putting up with a tsunami of email over the past couple of days; thanks to all your help I'm now starting to trundle along quite happily typesetting, and the remaining few problems I'm collecting together for later.] -- http://www.mupsych.org/~rrt/ Careful Cyclists Approaching From Right (Anon) ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Musica ficta again
I read the archives, and since there's no proper support for musica ficta, I'm quite happy with the 2002 solution: #(define fictaflat '(music "accidentals--1")) #(define fictanat '(music "accidentals-0")) #(define fictasharp '(music "accidentals-1")) #(define smallsharp '((font-relative-size . -2) (music "accidentals-1"))) However, I can't get these macros to work as documented in 2002 (definitions as above, usage something like c#flat). I'm using 2.1.26. What do I need to do? -- http://www.mupsych.org/~rrt/ | plagiarism, n. the mind burgles ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
simultaneous trouble
In this snippet below I have a mystery. If I run the code as it is
there is no problem. If I un-comment the commented out lines I get
strange results. What I want is to have full sized whole measure rests
beneath the cue notes. When I try to do this I end up with all of the
tremolo quarter notes all on the same stem and the beam on the 5-tuplet
disappears. Am I trying to do this wrong?
v2.1.25.hwn1
Thanks,
David
cue = \set fontSize = #-4
part = \set fontSize = #0
\score{
\notes \relative c'''
{ \repeat unfold 4 {
% <<
\cue
c4:8 bes: a: g: \times 4/5{fis16-( g a bes c} d8-)-[ d-]
% \\
% \part
% r1
% >>
}
}
}
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Getting there with musica ficta
OK, I'm nearly there, my remaining problems are Scheme problems I think (I know a bit of elisp, but no Scheme up to now). I have the following: #(def-markup-command (fictasharp) () "Foo" (#:musicglyph "accidentals-2")) which doesn't parse. I think the problem is my empty argument type list. ?? -- http://www.mupsych.org/~rrt/ resolute, a. obstinate in a good cause (Bierce) ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Mac OS X 10.3.2 bugs/compile errors
On Feb 23, 2004, at 3:50 PM, Stan Sanderson wrote: Matthew-- I believe Lilypond is doing exactly what you have told it to. See the example in the documentation for multiple rests (in the regression tests). If Score.skipBars is set, the signs for four, two, and one measure rest are combined to produce the graphical representation of rests for up to 10 bars. The number of bars will be written above the sign. The symbols shown in your example appear to agree with those in the sample.. Ok... then I guess the problem is that I've never seen those symbols before (which is no surprise). I expected the 5 and 9 measure rests to appear like the 20 measure rest, with the horizontal bar between two vertical lines, like this: |---|, rather than | - or | | -. Is there any way to specify this? Stan P.s.- I ran your code with uh... I think some thing got cut off here... ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Musica ficta done
By googling I eventually found some more code examples that enabled me to complete the code for LilyPond 2.1.26: % Musica ficta #(def-markup-command (fictasharp paper props) () (interpret-markup paper props (markup #:musicglyph "accidentals-2"))) #(def-markup-command (fictaflat paper props) () (interpret-markup paper props (markup #:musicglyph "accidentals--1"))) #(def-markup-command (fictanatural paper props) () (interpret-markup paper props (markup #:musicglyph "accidentals-0"))) This is just the basic version; you might want to make the accidentals smaller, &c. -- http://www.mupsych.org/~rrt/ | wisdom, n. knowing when to be foolish ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Debian (Woody) packages for Lilypond 2.1.26
Binary packages of LilyPond 2.1.26 for Debian Woody are available at http://afavant.elte.hu/~wferi/lilypond Further announcements will only be sent to [EMAIL PROTECTED] Enjoy! ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
LilyPond 2.1.26 packaged for Cygwin
Cygwin binary packages of LilyPond 2.1.26 are available from my homepage. The package can be installed by adding and selecting my homepage as mirror: http://www.inf.bme.hu/~berti/lilypond Greetings, Bert ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Degenerate Bow
When working on a single staff, I get this warning: programming error: Degenerate bow: infinite steepness reqd (Continuing; cross thumbs) Through lots of commenting out I have attributed the problem to this measure: < g' e' >-.[ a,!-. < csharp a' >-. e,-.] < csharp' bflat' >-.[ e,-. < e c' >-. a,-.] < e' csharp' >-.[ a,-. < e' g >( < f a >]) < g bflat >-.[ a,-. < b! d >-.( < csharp e >] It looks perfect on PDF, but I suspect it's causing my set \breaks to screw up. What did I miss? Will Oram spamguy ^^AT^^ foxchange.com // william.oram ^^AT^^ cwru.edu // AIM spamguy21 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
extender lines not showing up
I was experimenting with the example file 'lyric-combine-new.ly' and I
noticed something strange. If you add extender lines to the lyrics
under the melismata, the extender lines do not show up after the lyrics
on the stanzas where the "\set ignoreMelismata = ##t" is not used.
Here is what I changed:
\lyricsto "bla" \lyrics \new Lyrics { bla __ ab __ blob blob }
\lyricsto "bla" \lyrics \new Lyrics {
bla __
\set ignoreMelismata = ##t
blob
%% note: effect of ignoreMelismata delayed one time step.
\unset ignoreMelismata
blob __
blob
}
\lyricsto "bla" \lyrics \new Lyrics { nes __ ted __
lyrics voice with more words than no tes } >>
What is going on here? I am using 2.1.26.
--
Blake Garretson --- http://blakeg.freeshell.org
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: 2.1.25 Compile problems
Op ma 23-02-2004, om 17:53 schreef Mats Bengtsson: > If you look at the mailing list archives for lilypond-user, > lilypond-develop and bug-lilypond for the last week, you will > see that this problem is not specific for Fink. Do you mean it's a PowerPC problem, or even broader? > Han-Wen hoped > to have solved it in 1.2.26 but it seems there are still some > problems. I just got 2.1.26 to compile without problems. Thanks. Walter Hofmeister ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
