Re: 2.9.2 octavation dashes not cancelled and more but not in 2.8.1-4
On 25-Apr-06, at 6:36 PM, Paul Scott wrote: Paul Scott wrote: Just the addition of #(set-octavation 1) causes the rest of the staff lines to be dashed. (commenting that line restores the solid staff lines.) Example later if necessary. I'm trying to get some parts out right away. This problem goes away with 2.8.1-4 as well as an unexplained conflict with my transpositions. (After the octavation change I get an unspecified whole step transposition). I recommend using 2.8 (the stable version) for real work. If you want to use 2.9 (the unstable development version), issues like this will crop up from time to time. When they do, please report them in the bugs list or lilypond-devel; these problems are not relevant to lilypond-user. We're aware of this problem; it will hopefully be fixed in the next version of 2.9. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: 2.9.2 octavation dashes not cancelled and more but not in 2.8.1-4
Graham Percival wrote: On 25-Apr-06, at 6:36 PM, Paul Scott wrote: Paul Scott wrote: Just the addition of #(set-octavation 1) causes the rest of the staff lines to be dashed. (commenting that line restores the solid staff lines.) Example later if necessary. I'm trying to get some parts out right away. This problem goes away with 2.8.1-4 as well as an unexplained conflict with my transpositions. (After the octavation change I get an unspecified whole step transposition). I recommend using 2.8 (the stable version) for real work. Understood. If you want to use 2.9 (the unstable development version), issues like this will crop up from time to time. Understood. I also use Debian sid. I would like to be able to contribute more to the project but this is all I have time to do right now. When they do, please report them in the bugs list or lilypond-devel; Ok. I thought I would post it here first since I didn't have a small example to prove it with, these problems are not relevant to lilypond-user. Ok. We're aware of this problem; I'm subscribed to the devel. list and must have missed that discussion. it will hopefully be fixed in the next version of 2.9. Great! Thanks, Paul ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pitched trill?
Quoting Panteck [EMAIL PROTECTED]:
Is there a way to do this in Lilypond (2.8)? I've looked at the
\pitchedTrill command, but that specifies a note to trill to, and I'd
rather just specify sharp, flat, or natural in the trill line.
--Steven
You can redefine what is printed at the beginning of the wavy line,
like in this example:
\version 2.8.0
trillflat = \markup{ \musicglyph #scripts.trill \flat }
\relative{
\once \override TrillSpanner #'edge-text = #(cons trillflat ) c1
\startTrillSpan
b \stopTrillSpan
}
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: uncertain about MIDI dynamic scaling
On 25-Apr-06, at 4:36 AM, Sean Reed wrote: Is there documentation somewhere on how the .midiMinimumVolume and .midiMaximum values specifically effect the velocity scaling? I expected it to scale #0.0=0 to #1.0=127, but I discovered that you can go above 1.0 and below 0.0 into negative values. For now I used a hit or miss approach to gradually tweak the scaling to my taste, opening the MIDI files in Digital Performer and looking at the values in the event lists. From the most recent docs, 10.7.1 Creating MIDI files. I think I added this info in the last few weeks, so it might not appear in the online docs. Ties, dynamics, and tempo changes are interpreted. Dynamic marks, crescendi and decrescendi translate into MIDI volume levels. Dynamic marks translate to a fixed fraction of the available MIDI volume range, crescendi and decrescendi make the volume vary linearly between their two extremes. The fractions can be adjusted by dynamicAbsoluteVolumeFunction in Voice context. For each type of MIDI instrument, a volume range can be defined. This gives a basic equalizer control, which can enhance the quality of the MIDI output remarkably. The equalizer can be controlled by setting instrumentEqualizer, or by setting \set Staff.midiMinimumVolume = #0.2 \set Staff.midiMaximumVolume = #0.8 Through experimenting I also discovered that the dynamic range in LilyPond is \p to \. The current downloadable PDF version of the manual still states this range as \ppp to \fff (with a typo as well, I think, since \fff is listed twice). \ also works; the typo is that the second \fff should be \. Fixed, thanks. - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Markup text to the left of first chord on ChordNames staff
Rick Hansen (aka RickH) wrote: This should be simple but I cant find an answer after exhaustive tries. How can I attach a bit of markup text immediately to the left of the first chord in a ChordNames context staff? Did anyone reply to this? I have a similar requirement as well, i.e. if I put markup text above the staff, then lilypond will shift the chords higher up to get out of its way, which is usually a good thing. But there are a few times when I would prefer that the chords just remained as they are. Thanks! Jennifer ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
LilyPond-book WinXP again...
Hi, I am using the LilyPond 2.8.1 on WinXP Home Edition. I have installed it running the lilypond-2.8.1-4.mingw.exe file, downloaded from the LilyPond website. I have not intalled anything more, like Cygwin, for instance. TeX was already installed on my system. The program works well, but when I try to make a musicological document, mixing LaTeX and LilyPond code, I'm always in trouble. Applying the LilyPond-book on a *.lytex file (from the Windows prompt) results in the same error as reported many times here, see for example http://lists.gnu.org/archive/html/lilypond-user/2006-03/msg00435.html Although this topic has been discussed before, I'm really despaired I have not found any complex instructions on how to solve this problem. Is it enough to reinstall Python? Where to get it? How to install and what to do next? Or is it necessary to install Cygwin? Or is there some patch for LilyPond-book.py? Excuse me, but I'm totally confused about that already... I think, as this is apparently a common problem of WinXP users (although might be beginners), it would be very useful to place some hints to the LilyPond page. Would there be somebody to help me? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Boxes and bars
Hello all, I sent a message to the list a couple of days ago and never heard anything back, I'm just wondering if the message actually went through, because it seems like people here are good at responding :) So here it is again, my apologies if I'm double-posting... --- If anyone can help with these 2 questions regarding a score I'm working on, I would be very grateful. I'm using 2.4.5. 1) I need to draw boxes notes on the staff, in order to designate improvisation. Is this possible? (I would be surprised if it wasn't, but I seem unable to find anything in the docs.) 2) Is there a way to draw manual barlines in one staff that won't affect anything in other staves? For instance: c8 c8 \bar c8 c8 overtop of: c2 I'm sorry if either of those questions are covered in the docs, a link would be sufficient. Thanks in advance, - Chris ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Markup text to the left of first chord on ChordNames staff
Jennifer Clark wrote: Rick Hansen (aka RickH) wrote: This should be simple but I cant find an answer after exhaustive tries. How can I attach a bit of markup text immediately to the left of the first chord in a ChordNames context staff? Did anyone reply to this? I have a similar requirement as well, i.e. if I put markup text above the staff, then lilypond will shift the chords higher up to get out of its way, which is usually a good thing. But there are a few times when I would prefer that the chords just remained as they are. Sorry for answering my own post, but I have found something that may be relevant; in the manual, it says you can move about items through use of the extra-offset, e.g. for markup text, which seems quite effective; \once \override TextScript #'extra-offset = #'(-1.3 . 1.3) Is it possible to apply the same thing to chords? Jennifer ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Boxes and bars
I, a beginner too, and maybe others don't really understand your need, but here are my guesses (I hope someone else will help too). My first advice is to upgrade your version of Lilypond. :) About item 2: You might find answers in 8.4.1 Polymetric notation. Also if you use \set Score.defaultBarType = empty. No bar line will be drawn unless you specify, for example, c8 c8 \bar | c8 c8. About item 1: Do you need what is described in section 8.5.1? Or you may find something in the Regression Tests or Tips and Tricks. It is worth consulting these html files. Good luck, Eduardo - Original Message - From: c.m.bryan [EMAIL PROTECTED] To: lilypond-user@gnu.org Sent: Wednesday, April 26, 2006 11:05 AM Subject: Re: Boxes and bars Hello all, I sent a message to the list a couple of days ago and never heard anything back, I'm just wondering if the message actually went through, because it seems like people here are good at responding :) So here it is again, my apologies if I'm double-posting... --- If anyone can help with these 2 questions regarding a score I'm working on, I would be very grateful. I'm using 2.4.5. 1) I need to draw boxes notes on the staff, in order to designate improvisation. Is this possible? (I would be surprised if it wasn't, but I seem unable to find anything in the docs.) 2) Is there a way to draw manual barlines in one staff that won't affect anything in other staves? For instance: c8 c8 \bar c8 c8 overtop of: c2 I'm sorry if either of those questions are covered in the docs, a link would be sufficient. Thanks in advance, - Chris ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Markup text to the left of first chord on ChordNames staff
- Original Message - From: Jennifer Clark [EMAIL PROTECTED] To: lilypond-user@gnu.org Sent: Wednesday, April 26, 2006 11:30 AM Subject: Re: Markup text to the left of first chord on ChordNames staff Sorry for answering my own post, but I have found something that may be relevant; in the manual, it says you can move about items through use of the extra-offset, e.g. for markup text, which seems quite effective; \once \override TextScript #'extra-offset = #'(-1.3 . 1.3) Is it possible to apply the same thing to chords? Jennifer Sure, according to the Program Reference - I never verified it, though. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Markup text to the left of first chord on ChordNames staff
On 26-Apr-06, at 7:30 AM, Jennifer Clark wrote: Sorry for answering my own post, but I have found something that may be relevant; in the manual, it says you can move about items through use of the extra-offset, e.g. for markup text, which seems quite effective; \once \override TextScript #'extra-offset = #'(-1.3 . 1.3) Is it possible to apply the same thing to chords? Yes, of course. See chapter 10 for hints about how to do this. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Set vs. Override - I'm confused
On Tuesday 11 April 2006 23:56, Werner LEMBERG wrote: \set: set the value of a context property \override: set the value of a layout object property I've always wondered why it isn't possible to unify them... In 2.8 there's an essential difference between grob and context properties, which is visible for end-users: the \tweak command only makes sense on layout object properties, not on context properties. This difference might make it easier for new users to understand grob properties. -- Erik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Macro pre-processing?
On Friday 07 April 2006 00:50, Geoff Horton wrote:
Just read sections 11.1.3 and 11.1.6 in the manual.
That's far more complicated than I want, and even further more
complicated than a musician who's not a computer programmer is going
to want to deal with--please note that those sections are in the
chapter on Interfaces for Programmers. Why should I have to know
Scheme and the details of LilyPond implementation if all I want to do
is save a little typing and come up with a less busy-looking input
file?
I agree with you that this would be nice.
LilyPond is powerful, and I'd like to see more of that power made more
easily accessible. I'm not asking for changes to the basic syntax at
all--anything I'd come up with would be a totally optional pre-pass
system.
I have plans to make some improvent to the parser, in order to make \relative
soft-codable. A side-effect of this will probably be that custom high-order
music functions can be written; for example, you could add a function
\define-function, to easily define a simple music function. It could work
something like this:
\define-music-function {\foo \x \y} { c8 \x d8 \y }
...
{ \foo e16 {f g} }
=
{ c8 e16 d8 {f16 g16} }
The usefulness of this kind of function is disputed among developers, so it
might not become part of the official lilypond distribution.
--
Erik
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Macro pre-processing?
\define-music-function {\foo \x \y} { c8 \x d8 \y }
...
{ \foo e16 {f g} }
=
{ c8 e16 d8 {f16 g16} }
The usefulness of this kind of function is disputed among developers, so it
might not become part of the official lilypond distribution.
I am not a developer (though I do read the dev list), but I would
certainly use such a thing if it existed, and it would do most of the
things (and maybe all of them) for which I wanted a pre-processor.
Geoff
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Markup text to the left of first chord on ChordNames staff
In contrast to the previous people who answered the questions, I would say that you cannot directly apply the same idea to move a whole line of chords. See http://lists.gnu.org/archive/html/lilypond-user/2006-03/msg00411.html for a hint on how to solve the problem. /Mats Quoting Jennifer Clark [EMAIL PROTECTED]: Jennifer Clark wrote: Rick Hansen (aka RickH) wrote: This should be simple but I cant find an answer after exhaustive tries. How can I attach a bit of markup text immediately to the left of the first chord in a ChordNames context staff? Did anyone reply to this? I have a similar requirement as well, i.e. if I put markup text above the staff, then lilypond will shift the chords higher up to get out of its way, which is usually a good thing. But there are a few times when I would prefer that the chords just remained as they are. Sorry for answering my own post, but I have found something that may be relevant; in the manual, it says you can move about items through use of the extra-offset, e.g. for markup text, which seems quite effective; \once \override TextScript #'extra-offset = #'(-1.3 . 1.3) Is it possible to apply the same thing to chords? Jennifer ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: LilyPond-book WinXP again...
See http://lists.gnu.org/archive/html/lilypond-user/2006-04/msg00363.html /Mats Quoting Michal Vopalensky [EMAIL PROTECTED]: Hi, I am using the LilyPond 2.8.1 on WinXP Home Edition. I have installed it running the lilypond-2.8.1-4.mingw.exe file, downloaded from the LilyPond website. I have not intalled anything more, like Cygwin, for instance. TeX was already installed on my system. The program works well, but when I try to make a musicological document, mixing LaTeX and LilyPond code, I'm always in trouble. Applying the LilyPond-book on a *.lytex file (from the Windows prompt) results in the same error as reported many times here, see for example http://lists.gnu.org/archive/html/lilypond-user/2006-03/msg00435.html Although this topic has been discussed before, I'm really despaired I have not found any complex instructions on how to solve this problem. Is it enough to reinstall Python? Where to get it? How to install and what to do next? Or is it necessary to install Cygwin? Or is there some patch for LilyPond-book.py? Excuse me, but I'm totally confused about that already... I think, as this is apparently a common problem of WinXP users (although might be beginners), it would be very useful to place some hints to the LilyPond page. Would there be somebody to help me? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Markup text to the left of first chord on ChordNames staff
Mats Bengtsson wrote: In contrast to the previous people who answered the questions, I would say that you cannot directly apply the same idea to move a whole line of chords. See http://lists.gnu.org/archive/html/lilypond-user/2006-03/msg00411.html for a hint on how to solve the problem. Thanks for the reply Mats, I've checked the post and followups, and had a look at the manual page and reference, but to be honest I don't really understand how to approach this, even with that information. Is there a specific command I can use to enable this? Jennifer ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Set vs. Override - I'm confused
On 4/19/06, Erik Sandberg [EMAIL PROTECTED] wrote: In 2.8 there's an essential difference between grob and context properties, which is visible for end-users: the \tweak command only makes sense on layout object properties, not on context properties. This difference might make it easier for new users to understand grob properties. Might, but doesn't. David ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Set vs. Override - I'm confused
In 2.8 there's an essential difference between grob and context properties, which is visible for end-users: the \tweak command only makes sense on layout object properties, not on context properties. This difference might make it easier for new users to understand grob properties. Might, but doesn't. Hehe, I second this. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Set vs. Override - I'm confused
In 2.8 there's an essential difference between grob and context properties, which is visible for end-users: the \tweak command only makes sense on layout object properties, not on context properties. This difference might make it easier for new users to understand grob properties. Might, but doesn't. I have to agree. It seems an arbitrary distinction. Geoff ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
accordion dissCant
I want to put in the symbol voor the disscant for the accordion. In the installed .ly example file's I found the text for it.If I do \mark \markup { \musicglyph #accDiscantEEE } it runs without errors but the sign isn't there. Also --^\markup {musicglypyh ,, ,,, ,, ,}.
What must I do to get it in the score?regards Marcel.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Set vs. Override - I'm confused
David Feuer wrote: On 4/19/06, Erik Sandberg [EMAIL PROTECTED] wrote: In 2.8 there's an essential difference between grob and context properties, which is visible for end-users: the \tweak command only makes sense on layout object properties, not on context properties. This difference might make it easier for new users to understand grob properties. Might, but doesn't. David Actually it helps me, as a new user. When I first read the manual I didn't see any clear explanation of the difference, the docs could be more clear on that point. But when I realized that one was for grobs and the other for context, it became much clearer, for me it helps separating and understanding grobs and contexts. /Michael ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Set vs. Override - I'm confused
[...] when I realized that one was for grobs and the other for context, it became much clearer, for me it helps separating and understanding grobs and contexts. A big help would be a simple means to distinguish grobs and context properties. For example, context property names could always start with `c-', whereas grob properties don't have this prefix. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Contexts (Was Re: Set vs. Override - I'm confused)
Hello, When I first read the manual I didn't see any clear explanation of the difference, the docs could be more clear on that point. But when I realized that one was for grobs and the other for context, it became much clearer, for me it helps separating and understanding grobs and contexts. Context - another topic of my interest. It seems to me I haven't understood them fully yet. I generally know what they are for, but the role of them is not fully clear to me. Tomas Valusek ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
