Re: problems with learning lilypond
Citeren John Sellers <[EMAIL PROTECTED]>: confronted with multiple choice, none of which are distinguished from each other in regard as to the best one to pick. If I understood what was said, the 2.11 and later documentation is better than 2.10 and earlier. Why would I look at 2.11 I suggest to add only one small word to the link on the webpage to the 2.11 docs: "( Recommended ! )" That should be enough to make an end to the confusion ? Martin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: dissonant chords
I had a play around with the code from the snippets repository. Both that
and Jon's change to have both stems sloping fail to cope with the example
given in the original message of . Depending on the order in which
the notes in the chord are given, one either gets a collision of the natural
or accidental with a notehead, or the natural and accidental overlay each
other. With a bit more tweaking that can be avoided, though with the wrong
order of notes the natural and sharp symbols still collide:
%=
\version "2.11.64"
fixA = {
\once \override Stem #'length = #9
}
fixB = {
\once \override NoteHead #'extra-offset = #'(2.7 . 0)
\once \override Stem #'rotation = #'(45 0 0)
\once \override Stem #'extra-offset = #'(0.2 . -0.6)
\once \override Stem #'flag-style = #'no-flag
\once \override Stem #'length = #9.4
\once \override Accidental #'extra-offset = #'(4.3 . 0)
}
\relative c''
{
<< { \fixA 2 } \\ { \voiceThree \fixB cis } >> s
<< { \fixA } \\ { \voiceThree \fixB c! } >> s
<< { \fixA } \\ { \voiceThree \fixB d } >> s
}
%=
One other thing I note - see 2nd png, is that gets engraved with
only one of the two notes touching the stem. Is it possible to vary the
position of an individual notehead in a chord?
Nick
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Jonathan Kulp
> Sent: Friday, 28 November 2008 04:40
> To: Mats Bengtsson
> Cc: lilypond-user mailinglist
> Subject: Re: dissonant chords
>
> Mats Bengtsson wrote:
> > See http://lsr.dsi.unimi.it/LSR/Item?id=505 for a solution.
> >
> > /Mats
> >
>
> Thanks for this direction, Mats. I tweaked it a bit to look more like
> the ones Samuel Barber uses but haven't had time to figure out how to
> make the split stem converge on a single stem that is then able to
> attach to other notes with beams. Here's the code and an image is
> attached.
>
> Jon
> --
> Jonathan Kulp
> http://www.jonathankulp.com
>
> %
>
> fixB = {
>\once \override NoteHead #'extra-offset = #'(0.5 . 0)
>\once \override Stem #'rotation = #'(25 0 0)
>\once \override Stem #'extra-offset = #'(-0.2 . -0.2)
>\once \override Stem #'flag-style = #'no-flag
>\once \override Accidental #'extra-offset = #'(2.2 . 0) }
>
> fixC = {
>\once \override NoteHead #'extra-offset = #'(-0.5 . 0)
>\once \override Stem #'rotation = #'(-25 0 0)
>\once \override Stem #'extra-offset = #'(-0.2 . -0.2)
>\once \override Stem #'flag-style = #'no-flag
>\once \override Accidental #'extra-offset = #'(0.2 . 0) }
>
>
> \relative c' {
><< { \fixC d!8 } \\ { \voiceThree \fixB dis } >> s }
<><>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problems with learning lilypond
I just have to say that, having been a newbie at one point, with absolutely no background in script programs, I found LilyPond quite a simple affair to learn well enough to accomplish something. After that, it was all about exploring docs. Now I have a handful of students who have learned it very quickly and know how to get solutions. My real-world experience (I have met other Lilyponders face to face!!!) is that the program is well-documented and rather simple to learn. It's not perfect, but at least it has docs! I must say that, unless you are willing to dig into the program, do something useful with/to it, and contribute to the community, then just let the community be. Ranting to change people's opinions will accomplish nothing. Spend some of your time learning the workings of the program and less time ranting, and maybe you could contribute something. My two cents. I love LilyPond! Go LilyPond! I don't contribute much on the coding/dialoguing side, but I make beautiful scores with it, and, in a way, that is a contribution! Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Just chords.
On Fri, Nov 28, 2008 at 05:24:39PM +, Keith Weintraub wrote: > I have been trying to follow the docs (2.10.33) for making just chord symbol > sheets for guitar. Don't. 2.11 has vastly improved chord symbols and documentation. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: jpedal slowness
On my system, using jEdit on Vista, the PDF gets reloaded when I click on the jPedal window to make it topmost. Nick > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Bertalan Fodor (LilyPondTool) > Sent: Saturday, 29 November 2008 11:36 > To: Francisco Vila > Cc: lilypond-user > Subject: Re: jpedal slowness > > Does it realize at all? My experience was that I needed to close the > document and reopen. This closing and reopening is done automatically > when you run lilypond with the toolbar button (or menu item). > > Bert > > Francisco Vila wrote: > > Hello, > > the PDF viewer that comes with jedit (jPedal) seems to wait a long > > time before realizing that the file has changed, is it a known issue? > > I am using the very latest versions of sun jre, jedit and > lilypondtool. > > > > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user > No virus found in this incoming message. > Checked by AVG - http://www.avg.com > Version: 8.0.176 / Virus Database: 270.9.11/1816 - Release Date: > 27/11/2008 19:53 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: jpedal slowness
2008/11/29 Bertalan Fodor (LilyPondTool) <[EMAIL PROTECTED]>: > Does it realize at all? My experience was that I needed to close the > document and reopen. This closing and reopening is done automatically when > you run lilypond with the toolbar button (or menu item). In my experience, doing that the window stays open, only its contents are cleared (not immediately but after a variable wait), and then (again after a variable wait sometimes rather long) finally shows the output. The feel is otherwise quick, I usually work with gedit+evince under Linux+Gnome and the response for small files is absolutely instantaneous, less than 1 second. Only jpedal seems not to finish thinking for ages. -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: jpedal slowness
Does it realize at all? My experience was that I needed to close the document and reopen. This closing and reopening is done automatically when you run lilypond with the toolbar button (or menu item). Bert Francisco Vila wrote: Hello, the PDF viewer that comes with jedit (jPedal) seems to wait a long time before realizing that the file has changed, is it a known issue? I am using the very latest versions of sun jre, jedit and lilypondtool. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problems with learning lilypond
2008/11/29 John Sellers <[EMAIL PROTECTED]>: If you want your documentation to > really be useful, then put in enough qualification that all other > possibilities are eliminated. This is the exact nature of putting something > like "Choose this link to find the best documentation for getting a handle > on Lilypond"... Something I can extract from this all is, yes, if we have a very important thing to say to everybody, eg "so-called unstable docs are way better than old stable docs", then maybe we should put it in the web page in a prominent place. I mean, not waiting for people to subscribe to -user and convince them from there that "stable" does not mean "perfect" and that unstable version is not as bad as its name suggests. Rather the opposite, at least right now, do you agree? -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problems with learning lilypond
Graham Percival wrote: ... umm, WHAT?! Are you seriously claiming that you couldn't find the "Learning Manual" link? Top-left on the Documentation page? 1) go to lilypond.org 2) click on "documentation" 3) click on "documentation for 2.11" 4) click on "Learning manual" 5) click on "1.2 About the documentation" or "2. Tutorial" If you can find the documentation, you can find the tutorial. And if you can't find the documentation... well, some programs can be used without reading the docs; lilypond is not one of them. You misunderstand me. I am not concerned about myself. It is the umpteen other newbies who come to the front page of lilypond and are confronted with multiple choice, none of which are distinguished from each other in regard as to the best one to pick. If I understood what was said, the 2.11 and later documentation is better than 2.10 and earlier. Why would I look at 2.11 when the most recent stable version is 2.10 unless something up front says. "The 2.11 tutorial is important and you should look at it if you want to understand lilypond." Is it important? You bet. If you have a blatantly obvious link that in effect says "here is where to go to get a handle on Lilypond" then 99 out of a 100 who want to get a handle on Lillypond will follow that path and most of them will get a handle on Lilypond. If there is no such link, but instead you say something like "2.11 documentation". Then many newbies may well say. H...2.10 is the newest stable release. I'm not going to waste my time on 2.11 because it is not stable yet, and thus will never know they missed a tutorial that will save them a lot of time. It is true that if one has enough time, one will look around and eventually find that there is a tutorial that one should look at. But this isn't like to happen if one doesn't have a lot of time, which happens to be most of those who are technologically involved. Your comment about "are you seriously claiming..." comment. Of course I can find it, if I know it is there, if I know there something important I should see, if I know that it is better than looking somewhere else. You described a drill down to get there. I suggest you count the number of end points for all the drill down paths for the depth of the preferred documentation and then calculate the time it would take to explore them compared to a doing a single click on an front link that says: "Learning manual that every person wanting understand Lilypond should look at". You have to remember that the world over, people have different experiences and different ways of understanding, and that these are not unique or even similar in spite of using the exact same words to describe whatever it is. Let me explain it in another way. Consider "learning manual" and "dog". You understand both of these perfectly, right? But wait, then what is "dogged", "dog gone it", "dog days", "hot dog stand", "hot dog!", "hot dogging"? These are all very different and if you only knew the word dog and didn't know these idioms you would have a hard time making heads or tails of what they mean. Here is a news flash. Whatever a "learning manual" is, turns out to be as widely varied as all the dog expressions. A good way to solve this problem is to be specific enough that only the right meaning is likely. This is illustrated by doing a google search on, "You ain't nothing but a hound dog". You will find that there are few if any false positives in the 12,000+ hits. If you want your documentation to really be useful, then put in enough qualification that all other possibilities are eliminated. This is the exact nature of putting something like "Choose this link to find the best documentation for getting a handle on Lilypond" which doesn't leave any room for doubt regardless of which part of the world you might be from or what your previous experience might have been. It is the universal tendency of all technical documentation to fail to be this unambiguous simply because of the nature of the context that documentation is developed. Assumptions are made based on what is known or seen, and unfortunately none of us has the opportunity grow up and experience any of the 99.% of the rest of the world, so it is very hard for us to take this into account so we do what we already know to do instead. --end of tirade-- ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Re: Re: Centered Textspan for Piano music
2008/11/25 stefankaegi <[EMAIL PROTECTED]>:
> Thank you very much. This has already helped a lot. Yes, I'm using
> lilypond 2.11.64. There's still a small problem. I marked it red in the
> picture. There's a line too far left in bar 14. Don't quite know what's
> the problem of this.
This is part of the problem I mentioned about TextSpanner alignment
when using the centred dynamics template. Normally, using
'end-on-note would align the start point with the first note after the
break, but this is ignored when the spanner is attached to skips.
You'll have to add some 'left-broken 'padding to shift the line the
the right.
> And btw: do you have an idea how I could maybe make the bar lines like
> half transparent? The text and the bar lines sometimes collide in the
> piece.
The simplest way is to use \whiteout:
\override TextSpanner #'bound-details #'right #'text = \markup
\whiteout { rit. }
You might find that there's not enough whitespace around the text; in
this case, you're better off combining the text with a white box,
setting the box dimensions manually.
Regards,
Neil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Dynamics collision in 2.11.64
Hi Dmytro, 2008/11/28 Dmytro O. Redchuk <[EMAIL PROTECTED]>: > Hello, > > i've run into some problem with 2.11.64: > DynamicsText collide with Hairpins if #'to-barline = ##t. > > As you can see (attached), there is everything ok with 2.11.42. The comparison is invalid since 2.11.42 uses the context property hairpinToBarline, and it defaults to false. If you run the snippet with \set hairpinToBarline = ##t, it's identical to 2.11.64. The Bar_engraver is responsible for aligning the end points of line spanners with a barline when 'to-barline = ##t; it pays no attention to scripts which directly follow a spanner. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Color one accidental in a chord? Also, improved docs ... again!
Trevor Bača wrote:
Hi Jon, hi Trevor (D),
Thanks for the suggestion. The layered voices are kinda hacky but they work
successfully in my case.
There is, btw, a switch to suppress collisions in cases like this,
implemented on NoteColumn ...
\new Staff <<
\override Staff.NoteColumn #'ignore-collision = ##t
\new Voice { \voiceOne 1 }
\new Voice { \voiceOne \override Accidental #'color = #blue des'1 }
... which makes the solution interpret completely cleanly.
Awesome! That's very slick. Glad it worked for you,
Jon
--
Jonathan Kulp
http://www.jonathankulp.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Color one accidental in a chord? Also, improved docs ... again!
On Fri, Nov 28, 2008 at 1:18 PM, Jonathan Kulp <[EMAIL PROTECTED]>wrote:
> Trevor Bača wrote:
>
>> Hi,
>>
>> First off, I am once again amazed at the incremental improvement in the
>> docs. For example: 5.3.4 "The \tweak command". I've been working this
>> morning on coloring one (and only one) accidental in a chord. It seemed
>> like
>> \tweak would be the way to do it. The \tweak command works, for example,
>> in
>> constructions like 4 to adjust the color of
>> individual noteheads within a chord. However, I ran into the problem that
>> \tweak decides which grob to apply to *lexically* (ie, by the bit of input
>> syntax immediately following) which works great for noteheads, slurs and
>> the
>> like but doesn't work for accidentals because accidentals get created
>> implicitly during interpretation.
>>
>> So, after fiddling with \tweak for a while to color just one accidental in
>> a
>> chord, I'm pretty sure that \tweak won't work but I'm still not completely
>> sure. "Am I thinking of things correctly? Or is there something easier
>> that
>> I'm missing?" So I click over to 5.3.4 . Not only has the section been
>> expanded from the last time I read over it (probably more than a year ago)
>> and not only does it read great, there is now the following language on
>> explicit limitations of the command:
>>
>> "Notably the \tweak command cannot be used to modify stems, beams or
>> accidentals, since these are generated later by note heads, rather than by
>> music elements in the input stream."
>>
>> This is excellent. Not because I can't color a single accidental. But
>> instead because *the docs are explicit enough to stop me spending any
>> further time going down the wrong path*.
>>
>> I know this seems like small point. But, to me, it is only the most
>> professional docs that list not only what something does do ... but also
>> what something *does not do*. (I'm reminded of "limitation of scope"
>> sections that appear in some of the best-written software specification
>> docs: all software requirements docs list pages and pages of what the
>> system
>> shall do, but it takes someone to go the extra mile to include writing
>> that
>> points out limitations about what the system need not do.) Of course
>> there's
>> something of a tradition of this in the docs in general because of the
>> 'known limitations and bugs' sections, which are also quite useful.
>>
>> So thank you to whoever edited 5.3.4. And thanks again to the entire GDP
>> team for the dramatic improvements in the docs generally over the last
>> months.
>>
>> Now on to my original question.
>>
>> * * *
>>
>> QUESTION: is it possible to reach inside of a chord and color just one
>> accidental red?
>>
>> \tweak isn't going to work, as is quite clear from the docs, and Trevor
>> (D)'s post to this thread earlier this year in April ...
>>
>> http://lists.gnu.org/archive/html/lilypond-user/2008-04/msg00067.html
>>
>> ... makes me think that the task may not be possible at all.
>>
>> Does anyone have a work-around?
>>
>>
> I just made up a workaround for a simple example. Maybe you can use it in
> more complicated situations, too. I put the inner note of the chord in a
> separate voice. To keep the notes all lined up as if they were in one
> voice, I put \voiceOne commands in both voices. Just ignore the warnings
> about too many clashing note columns. HTH,
>
> Jon
>
>
> \version "2.11.64"
>
>
> \relative c' {
>
> << { \voiceOne 1 } \\ { \voiceOne \override Accidental #'color =
> #blue des1 } >>
> }
Hi Jon, hi Trevor (D),
Thanks for the suggestion. The layered voices are kinda hacky but they work
successfully in my case.
There is, btw, a switch to suppress collisions in cases like this,
implemented on NoteColumn ...
\new Staff <<
\override Staff.NoteColumn #'ignore-collision = ##t
\new Voice { \voiceOne 1 }
\new Voice { \voiceOne \override Accidental #'color = #blue des'1 }
>>
... which makes the solution interpret completely cleanly.
Thank you both!
Trevor (B).
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: pianist's needs
Am 28.11.2008 um 20:28 schrieb Tim MacEachern: I like the thrust of your notation software. As a pianist, I'd like to make a comment on what I would like to see. Although the traditional method of marking accidentals works, it can be time-consuming to figure out whether a note is to be played as an accidental and this is often time a pianist does not have. I'd like to have my music all colour coded: naturals should be in black, sharps in some other colour, perhaps red, and flats in maybe green (double sharps and flats are rare and could be done in black or a different colour). Then I would not have to figure things out. This colour coding could be added to normal notation without changing the traditional aspects. As an alternative to colour coding, it might be possible for the note heads to be different shapes for accidentals. These differences might be too small to notice at pace though. in contrast with other notation programs I've used, that's quite simple with lilypond. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
jpedal slowness
Hello, the PDF viewer that comes with jedit (jPedal) seems to wait a long time before realizing that the file has changed, is it a known issue? I am using the very latest versions of sun jre, jedit and lilypondtool. -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: your Software
2008/11/28 ketung hsiao <[EMAIL PROTECTED]>: > Like to see how our software works. Read carefully one of the following pages, then ask again if anything is not clear enough: http://lilypond.org/web/switch/howto http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Compiling-a-file http://lilypondwiki.tuxfamily.org/index.php?title=Main_Page Please, use the bug list only for bug reporting. I'm forwarding to lilypond-user. -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Quick-insert mode for vim -- work in progress
If You are interested: I made short-cuts for jedit by myself. I type, q qi wi ei and I get c'', dis'', dis'' und eis'' for example and I can input chords quicker. I type asd (shift enter) and then I get . I You are interested, I can send it to You. But now I use most of the time lilykde, which I prefer because of the RUMOR implementation. 2008/11/21 Bertalan Fodor <[EMAIL PROTECTED]> > Also there is a quick insert mode work in progress for jEdit / > LilyPondTool. However, I could not make enough progress yet, but the > foundations are there, so in the after-the-next release it will be > available. > > However, my quick insert mode will be really a virtual piano made from the > keyboard. I found that approach much better. It will sport automatic > accidental handling. For example if you want to write > > c es c bes, b c > > in quick lily you type: > d g e d l , e d > > In LilyPondTool you'll be able to type: > > c g c s x c (try it!) > > Much more natural. However, it makes it complicated, because the software > must know the key. So for example is c minor it will be rendered as > c es c bes, b c > but in h major, it will be rendered as > c dis c ais, b c > > But will make it the fastest possible way to enter notes on a computer > keyboard. > > Bert > > > Great work. However, I find there is only one thing wrong with it: > > it's for vim. :-) > > > > 2008/11/21 Eyolf Řstrem <[EMAIL PROTECTED]>: > >> The most useful and simple tool I've had the pleasure to work on > >> lilypond > >> files with, is Nicolas Sceaux's lyqi mode (lilypond quick insert). There > >> is > >> only one thing wrong with it: it's for emacs. I therefore decided to > >> make > >> my own version of it for vim. > > -- > > Francisco Vila. Badajoz (Spain) > > http://www.paconet.org > > > > > > ___ > > 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 > ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: segno above rehearsal mark
Hi Tao, 2008/11/28 Tao Cumplido <[EMAIL PROTECTED]>: > I need to put a segno mark on top of one rehearsal mark but lily doesn't > allow two marks at the same spot so I searched LSR and came across this > http://lsr.dsi.unimi.it/LSR/Item?id=202 > > unfortunately it doesn't work with 2.11.62 and I am not really good at scheme > so I can't figure out why. Replace #:center-align with #:center-column. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: two-pass line breaking
Hi Basil,
On Fri, Nov 28, 2008 at 11:37 AM, Basil Crow <[EMAIL PROTECTED]> wrote:
>
> Suppose I have a .ly file with Score.timing set to false and no line breaks
> (that is, everything is typeset on one line):
>
> \relative c'
> {
> \set Score.timing = ##f
> f4 g a b
> f4 g a b
> f4 g a b
> f4 g a b
> f4 g a b
> f4 g a b
> f4 g a b
> f4 g a b
> f4 g a b
> f4 g a b
> f4 g a b
> f4 g a b
> }
>
> Now suppose I have the following preprocessed line breaks:
>
> tweaks = {
> \break
> \skip 1*4/1
> \break
> \skip 1*4/1
> \break
> \skip 1*4/1
> \break
> }
>
> How can I integrated these breaks into the score?
One method is to add "invisible" bars at the points where you need a \break:
%%% BEGIN %%%
\version "2.11.64"
tweaks = {
\break
\skip 1*4/1
\break
\skip 1*4/1
\break
\skip 1*4/1
\break
}
\relative c' {
\set Score.timing = ##f
<<
{
\repeat unfold 12 { f4 g a b \bar "" }
}
\\
{
\tweaks
}
>>
}
%%% END %%%
HTH,
Patrick
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: two-pass line breaking
Basil,
I've massaged your input file a bit. I think this produces what you want.
Notice I commented out the Score.timing line.
%
melody = \relative c'
{
%\set Score.timing = ##f
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
}
tweaks = {
\break
\skip 1*4/1 % why the /1 ? It's not necessary
\break
\skip 1*4/1
\break
\skip 1*4/1
\break
}
\score {
\context Staff
<<
\melody
\tweaks
>>
}
%
Basil Crow wrote:
Dear list,
Suppose I have a .ly file with Score.timing set to false and no line
breaks (that is, everything is typeset on one line):
\relative c'
{
\set Score.timing = ##f
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
}
Now suppose I have the following preprocessed line breaks:
tweaks = {
\break
\skip 1*4/1
\break
\skip 1*4/1
\break
\skip 1*4/1
\break
}
How can I integrated these breaks into the score?
Basil
___
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
two-pass line breaking
Dear list,
Suppose I have a .ly file with Score.timing set to false and no line
breaks (that is, everything is typeset on one line):
\relative c'
{
\set Score.timing = ##f
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
f4 g a b
}
Now suppose I have the following preprocessed line breaks:
tweaks = {
\break
\skip 1*4/1
\break
\skip 1*4/1
\break
\skip 1*4/1
\break
}
How can I integrated these breaks into the score?
Basil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
pianist's needs
I like the thrust of your notation software. As a pianist, I'd like to make a comment on what I would like to see. Although the traditional method of marking accidentals works, it can be time-consuming to figure out whether a note is to be played as an accidental and this is often time a pianist does not have. I'd like to have my music all colour coded: naturals should be in black, sharps in some other colour, perhaps red, and flats in maybe green (double sharps and flats are rare and could be done in black or a different colour). Then I would not have to figure things out. This colour coding could be added to normal notation without changing the traditional aspects. As an alternative to colour coding, it might be possible for the note heads to be different shapes for accidentals. These differences might be too small to notice at pace though. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Color one accidental in a chord? Also, improved docs ... again!
Trevor Bača wrote:
Hi,
First off, I am once again amazed at the incremental improvement in the
docs. For example: 5.3.4 "The \tweak command". I've been working this
morning on coloring one (and only one) accidental in a chord. It seemed like
\tweak would be the way to do it. The \tweak command works, for example, in
constructions like 4 to adjust the color of
individual noteheads within a chord. However, I ran into the problem that
\tweak decides which grob to apply to *lexically* (ie, by the bit of input
syntax immediately following) which works great for noteheads, slurs and the
like but doesn't work for accidentals because accidentals get created
implicitly during interpretation.
So, after fiddling with \tweak for a while to color just one accidental in a
chord, I'm pretty sure that \tweak won't work but I'm still not completely
sure. "Am I thinking of things correctly? Or is there something easier that
I'm missing?" So I click over to 5.3.4 . Not only has the section been
expanded from the last time I read over it (probably more than a year ago)
and not only does it read great, there is now the following language on
explicit limitations of the command:
"Notably the \tweak command cannot be used to modify stems, beams or
accidentals, since these are generated later by note heads, rather than by
music elements in the input stream."
This is excellent. Not because I can't color a single accidental. But
instead because *the docs are explicit enough to stop me spending any
further time going down the wrong path*.
I know this seems like small point. But, to me, it is only the most
professional docs that list not only what something does do ... but also
what something *does not do*. (I'm reminded of "limitation of scope"
sections that appear in some of the best-written software specification
docs: all software requirements docs list pages and pages of what the system
shall do, but it takes someone to go the extra mile to include writing that
points out limitations about what the system need not do.) Of course there's
something of a tradition of this in the docs in general because of the
'known limitations and bugs' sections, which are also quite useful.
So thank you to whoever edited 5.3.4. And thanks again to the entire GDP
team for the dramatic improvements in the docs generally over the last
months.
Now on to my original question.
* * *
QUESTION: is it possible to reach inside of a chord and color just one
accidental red?
\tweak isn't going to work, as is quite clear from the docs, and Trevor
(D)'s post to this thread earlier this year in April ...
http://lists.gnu.org/archive/html/lilypond-user/2008-04/msg00067.html
... makes me think that the task may not be possible at all.
Does anyone have a work-around?
I just made up a workaround for a simple example. Maybe you can use it
in more complicated situations, too. I put the inner note of the chord
in a separate voice. To keep the notes all lined up as if they were in
one voice, I put \voiceOne commands in both voices. Just ignore the
warnings about too many clashing note columns. HTH,
Jon
\version "2.11.64"
\relative c' {
<< { \voiceOne 1 } \\ { \voiceOne \override Accidental #'color =
#blue des1 } >>
}
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Color one accidental in a chord? Also, improved docs ... again!
Thanks for the nice comments about the docs. Makes it all worthwhile :) One horrible frig you might consider if you only need to do this once is to change the note in the chord to one with no accidental, then add the note with the accidental in a second voice, making the notehead and stem transparent and the accidental coloured. Each case might need further tweaking to look right, though. Trevor - Original Message - From: "Trevor Bača" <[EMAIL PROTECTED]> To: "lilypond-user" Sent: Friday, November 28, 2008 6:41 PM Subject: Color one accidental in a chord? Also, improved docs ... again! Hi, First off, I am once again amazed at the incremental improvement in the docs. For example: 5.3.4 "The \tweak command". I've been working this morning on coloring one (and only one) accidental in a chord. It seemed like \tweak would be the way to do it. The \tweak command works, for example, in constructions like 4 to adjust the color of individual noteheads within a chord. However, I ran into the problem that \tweak decides which grob to apply to *lexically* (ie, by the bit of input syntax immediately following) which works great for noteheads, slurs and the like but doesn't work for accidentals because accidentals get created implicitly during interpretation. So, after fiddling with \tweak for a while to color just one accidental in a chord, I'm pretty sure that \tweak won't work but I'm still not completely sure. "Am I thinking of things correctly? Or is there something easier that I'm missing?" So I click over to 5.3.4 . Not only has the section been expanded from the last time I read over it (probably more than a year ago) and not only does it read great, there is now the following language on explicit limitations of the command: "Notably the \tweak command cannot be used to modify stems, beams or accidentals, since these are generated later by note heads, rather than by music elements in the input stream." This is excellent. Not because I can't color a single accidental. But instead because *the docs are explicit enough to stop me spending any further time going down the wrong path*. I know this seems like small point. But, to me, it is only the most professional docs that list not only what something does do ... but also what something *does not do*. (I'm reminded of "limitation of scope" sections that appear in some of the best-written software specification docs: all software requirements docs list pages and pages of what the system shall do, but it takes someone to go the extra mile to include writing that points out limitations about what the system need not do.) Of course there's something of a tradition of this in the docs in general because of the 'known limitations and bugs' sections, which are also quite useful. So thank you to whoever edited 5.3.4. And thanks again to the entire GDP team for the dramatic improvements in the docs generally over the last months. Now on to my original question. * * * QUESTION: is it possible to reach inside of a chord and color just one accidental red? \tweak isn't going to work, as is quite clear from the docs, and Trevor (D)'s post to this thread earlier this year in April ... http://lists.gnu.org/archive/html/lilypond-user/2008-04/msg00067.html ... makes me think that the task may not be possible at all. Does anyone have a work-around? Trevor. -- Trevor Bača [EMAIL PROTECTED] ___ 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: nested staffgroups broken in 2.11.64
Hi Simon, On Fri, Nov 28, 2008 at 2:11 AM, Simon Bailey <[EMAIL PROTECTED]> wrote: > > btw, is there a possibility to see the documentation w/out frames? i tried > browsing it this morning on the way to work on a mobile device, and the > browser there doesn't support frames. would be nice if there was a version > without frames. from another point of view, i could imagine that the frame > setup would be problematic for visually-impaired users (such as hai-peng) > using screen readers. is this the case? The documentation does not use frames; the layout is achieved with CSS only. The accessibility issue you mention is one primary motivation behind this. The problem of getting the layout working well with various screen resolutions is a known issue (it's under `CSS Issues'): http://wiki.kainhofer.com/lilypond/texi2html_issues Do you have any ideas for a documentation layout for small resolution displays (e.g. mobile devices)? Thanks, Patrick ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing before and after barlines
On Nov 28, 2008, at 12:49 PM, Neil Puttock wrote: Take a look at Issue #462 in the bug tracker: http://code.google.com/p/lilypond/issues/detail?id=462&q=barline Until this enhancement is dealt with, I'm afraid you're stuck with the extra space. Thank you for your reply. I am disappointed, but I will check back again during 2.13 development to see if this enhancement is dealt with. Basil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Color one accidental in a chord? Also, improved docs ... again!
Hi, First off, I am once again amazed at the incremental improvement in the docs. For example: 5.3.4 "The \tweak command". I've been working this morning on coloring one (and only one) accidental in a chord. It seemed like \tweak would be the way to do it. The \tweak command works, for example, in constructions like 4 to adjust the color of individual noteheads within a chord. However, I ran into the problem that \tweak decides which grob to apply to *lexically* (ie, by the bit of input syntax immediately following) which works great for noteheads, slurs and the like but doesn't work for accidentals because accidentals get created implicitly during interpretation. So, after fiddling with \tweak for a while to color just one accidental in a chord, I'm pretty sure that \tweak won't work but I'm still not completely sure. "Am I thinking of things correctly? Or is there something easier that I'm missing?" So I click over to 5.3.4 . Not only has the section been expanded from the last time I read over it (probably more than a year ago) and not only does it read great, there is now the following language on explicit limitations of the command: "Notably the \tweak command cannot be used to modify stems, beams or accidentals, since these are generated later by note heads, rather than by music elements in the input stream." This is excellent. Not because I can't color a single accidental. But instead because *the docs are explicit enough to stop me spending any further time going down the wrong path*. I know this seems like small point. But, to me, it is only the most professional docs that list not only what something does do ... but also what something *does not do*. (I'm reminded of "limitation of scope" sections that appear in some of the best-written software specification docs: all software requirements docs list pages and pages of what the system shall do, but it takes someone to go the extra mile to include writing that points out limitations about what the system need not do.) Of course there's something of a tradition of this in the docs in general because of the 'known limitations and bugs' sections, which are also quite useful. So thank you to whoever edited 5.3.4. And thanks again to the entire GDP team for the dramatic improvements in the docs generally over the last months. Now on to my original question. * * * QUESTION: is it possible to reach inside of a chord and color just one accidental red? \tweak isn't going to work, as is quite clear from the docs, and Trevor (D)'s post to this thread earlier this year in April ... http://lists.gnu.org/archive/html/lilypond-user/2008-04/msg00067.html ... makes me think that the task may not be possible at all. Does anyone have a work-around? Trevor. -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: manipulating .ly with bash
On Wed, Nov 26, 2008 at 06:41:24PM +, Rob Canning wrote: > Jonathan Kulp wrote: > i really need to learn sed properly I scratched around for a good number of years using bash, sed, awk and friends, but now I really prefer perl. It is designed specifically for processing text, like Lilypond source. It is also more fun :-) -- Thanks Joe Mc Cool Snark, currently LEYC 028 37548074, 07802572441 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing before and after barlines
Hi Basil, 2008/11/28 Basil Crow <[EMAIL PROTECTED]>: > In this case, the rivers of white space where barlines would be drawn still > appear. I would appreciate some advice regarding what is creating this white > space. Take a look at Issue #462 in the bug tracker: http://code.google.com/p/lilypond/issues/detail?id=462&q=barline Until this enhancement is dealt with, I'm afraid you're stuck with the extra space. Regards, Neil ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Just chords.
Keith Weintraub <[EMAIL PROTECTED]> writes: > I would like the measures to be 4 per line. And I would like them to line up > from one line to the next. For this purpose I'd suggest you take a look at http://johan.vromans.org/software/sw_playtab.html . (The most recent version also accepts chords in LilyPond notation). -- Johan Chord is alive! http://chordii.sourceforge.net ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing before and after barlines
On Nov 28, 2008, at 12:19 PM, Kieren MacMillan wrote:
Is this not what you want?
\relative c'
{
\set Score.timing = ##f
\override Staff.BarLine #'break-visibility = #'#(#f #f #f)
f4 g a b
f4 g a b
f4 g a b
f4 g a b
}
Dear Kieren,
Thank you again, but it is not. Since you have set Score.timing to
false, no barlines are automatically drawn. While this has the
advantage of circumventing this entire issue, it has the disadvantage
of causing LilyPond not to break lines automatically. The problem I am
describing is when invisible barlines are in the middle of a line.
\relative c'
{
\set Score.timing = ##f
\override Staff.BarLine #'break-visibility = #'#(#f #f #f)
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
}
In this case, the rivers of white space where barlines would be drawn
still appear. I would appreciate some advice regarding what is
creating this white space.
Thank you,
Basil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Just chords.
Folks,
I have been trying to follow the docs (2.10.33) for making just chord symbol
sheets for guitar.
I would like the measures to be 4 per line. And I would like them to line up
from one line to the next.
In addition I would like my first notation (markup) to start right at the
beginning of line 1 but even with the score.
I can't seem to get it to do this.
Hope you can help like you have in the past.
Thanks,
KW
Begin cut and paste
\version "2.10.33"
\paper {
indent = #0
%interscoreline = 2.\mm
%between-system-space = 15\mm
ragged-bottom = ##f
%horizontal-shift = 0.5\in
left-margin = 2\in
line-width = 7.75\in
}
\header {
title = "Rikki Don't Lose That Number"
instrument = "Guitar"
composer = "Steely Dan"
opus = "Pretzel Logic"
}
\new ChordNames \with {
\override BarLine #'bar-size = #4
voltaOnThisStaff = ##t
\consists Bar_engraver
\consists "Volta_engraver"
}
\chordmode {
\repeat volta 2 {
\mark \markup {\small {Intro (chords implicit...)}} e1:m7 e1:m7 e1:m7
e1:m7 \break
d1 a1:sus2 e1 e1 \break
d1 a1:sus2 e1 cis2:5 b2:5 \break
} \alternative {
es e
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing before and after barlines
Hi Basil,
Is this not what you want?
\relative c'
{
\set Score.timing = ##f
\override Staff.BarLine #'break-visibility = #'#(#f #f #f)
f4 g a b
f4 g a b
f4 g a b
f4 g a b
}
HTH,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: dissonant chords
On Thursday 27 November 2008, Jonathan Kulp wrote:
> Martin Tarenskeen wrote:
> > Hi,
> >
> > Did anyone ever try to typeset dissonant chords like { < c cis d
> } ? I
> > can remember having seen chords like this frequently in Bela
Bartok's
> > Mikrokosmos book V or VI , edition Boosey & Hawkes.
> >
> > I don't have a scan or a scanner, but it would approximately look
> > something like this:
> >
> >
> >
> > 0
> > 0|#0
> > |/
> > |
This is better than the "Y" way because it can be used in many more
situations. It is not as good IMO as using a zero tuplet bracket,
which could be used to assemble *any* combination of stems, voices,
and notes. daveA
--
Free download of technical exercises worth a lifetime of practice:
http://www.openguitar.com/dynamic.html You can play the cards
you're dealt, or improve your hand with DGT. Very easy guitar
music, solos, duets, exercises, etc. [EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-invoke-editor
Dear Craig, A quick Google searched yielded the following blog post, which may provide you with some useful information regarding custom URL handlers in Java. http://www.unicon.net/node/776 Basil On Nov 28, 2008, at 10:57 AM, Craig Bakalian wrote: Hi, I have just finished making my own java TextEditor for Lilypond files. It has lots of nice macros, LINE NUMBERS! , it even has a nice midi input, my midi keyboards events are hooked into the editor's JTextArea, and it typesets. But the one thing I cannot figure out is how to get lilypond-invoke-editor to work? I know when lilypond is typesetting a file it is sending url to the postscript file, and clicking on the note head calls the uri. But, I just don't get the paradigm. How do I get my happy little java TextEditor project to become the head of the url? Craig Bakalian ___ 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
lilypond-invoke-editor
Hi, I have just finished making my own java TextEditor for Lilypond files. It has lots of nice macros, LINE NUMBERS! , it even has a nice midi input, my midi keyboards events are hooked into the editor's JTextArea, and it typesets. But the one thing I cannot figure out is how to get lilypond-invoke-editor to work? I know when lilypond is typesetting a file it is sending url to the postscript file, and clicking on the note head calls the uri. But, I just don't get the paradigm. How do I get my happy little java TextEditor project to become the head of the url? Craig Bakalian ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Just chords and lyrics.
Carl D. Sorensen wrote: On 11/28/08 4:47 AM, "Mats Bengtsson" <[EMAIL PROTECTED]> wrote: There's major problem with your proposed \hideAll (or whatever you want to call it), namely that the hidden voice will influence the placement of the other voices, since LilyPond will try to avoid collisions with the hidden note heads. Therefore, this solution is not really working if you want to use it to align lyrics to a hidden Voice in a Staff that also contains other voices. When I used it to align lyrics to partcombined music, I simply transposed the voice I used with lyricsto up an octave, and everything seemed to work fine. Yes, that's one possible trick, but as long as you only have set the objects as transparent, they will still influence spacing, for example the spacing to other objects that appear above the staff. Trying to instead to \override NoteHead #'stencil = ##f doesn't help either, since then the lyrics alignment won't work anymore. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing before and after barlines
On Nov 28, 2008, at 4:23 AM, Trevor Daniels wrote:
You should find your answer in the docs. Section "5.4.6 Visibility
of objects" in the 2.11 docs gives several different approaches to
making objects vanish. I'm sure one of these will be right for you,
but I can't say which one without knowing more of your intentions.
I suggest you read through this whole section first before deciding
- it's not very long.
I have read through Sections 5.4.6. I set Score.BarLine #'stencil to
false and Staff.BarLine #'break-visibility = #'#(#f #f #f). Despite
this, I still see extra space. I am not sure where this space is
coming from, but it is not the BarLine object. Notice the rivers of
white every four beats in these examples:
\relative c'
{
f4 g a b
f4 g a b
\override Score.BarLine #'stencil = ##f
f4 g a b
\revert Score.BarLine #'stencil
f4 g a b
f4 g a b
}
\relative c'
{
\override Staff.BarLine #'break-visibility = #'#(#f #f #f)
f4 g a b
f4 g a b
f4 g a b
f4 g a b
}
\relative c'
{
\set Score.timing = ##f
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
f4 g a b \bar ""
}
Could someone please point me in the right direction regarding where
this extra space is coming from?
Thank you,
Basil
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Just chords and lyrics.
Mats Bengtsson wrote: There's major problem with your proposed \hideAll (or whatever you want to call it), namely that the hidden voice will influence the placement of the other voices, since LilyPond will try to avoid collisions with the hidden note heads. Therefore, this solution is not really working if you want to use it to align lyrics to a hidden Voice in a Staff that also contains other voices. /Mats Trevor Daniels wrote: Graham Percival wrote Friday, November 28, 2008 10:42 AM On Fri, Nov 28, 2008 at 10:04:50AM -, Trevor Daniels wrote: ok, let's make a \hideNotation or \hideAll or something like that for printing lyrics + chords. \hideNotation is a bit too close to \hideNotes. \hideAll, \unHideAll looks good. The documentation can say it applies to the Voice, not the Staff. Trevor Given the problem Mats points out, my inclination is to keep the example using all the overrides as a snippet. People who want to use a \hideAllVoiceNotation sort of command can create one themselves using \hideNotes and my snippet as a starting point, and store their definition either in the file they're working on or in a definitions.ly file as described in the Learning Manual 5.1.5 "Style Sheets." The examples using "\new Devnull" can go in the main text of the docs since they have no overrides. Best, Jon -- Jonathan Kulp http://www.jonathankulp.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Just chords and lyrics.
On 11/28/08 4:47 AM, "Mats Bengtsson" <[EMAIL PROTECTED]> wrote: > There's major problem with your proposed \hideAll (or whatever you want > to call it), namely > that the hidden voice will influence the placement of the other voices, > since LilyPond will > try to avoid collisions with the hidden note heads. Therefore, this > solution is not really working > if you want to use it to align lyrics to a hidden Voice in a Staff that > also contains other voices. When I used it to align lyrics to partcombined music, I simply transposed the voice I used with lyricsto up an octave, and everything seemed to work fine. Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Dynamics collision in 2.11.64
Hello,
i've run into some problem with 2.11.64:
DynamicsText collide with Hairpins if #'to-barline = ##t.
As you can see (attached), there is everything ok with 2.11.42.
% \version "2.11.64"
\score {
\new Staff \with {
\remove "Time_signature_engraver"
} {
\new Voice \relative c'' {
% \override Hairpin #'to-barline = ##f
c4 c \< c c
c4 \! \mf c c c
\break
%
c4 c \< c c
\once \override DynamicText #'self-alignment-X = #RIGHT
c4 \! \mf c c c
\break
%
c4 c \< c c
\once \override DynamicText #'X-offset = #-5
c4 \! \mf c c c
}
}
}
\paper {
indent = 0
line-width = 7\cm
}
--
Dmytro O. Redchuk
<><>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
custom noteheads
hi list, I came across ths snippet from the lsr: http://lsr.dsi.unimi.it/LSR/Item?id=516 Now I was thinking if it is possible to assign such custom heads to different duratiosn, e.g. that half notes look different than quarter and eigths, etc. Also if it is possible to use them in a custom drum table but I think I can find this out easily, just if someone already knows. regards, Tao -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Just chords and lyrics.
There's major problem with your proposed \hideAll (or whatever you want to call it), namely that the hidden voice will influence the placement of the other voices, since LilyPond will try to avoid collisions with the hidden note heads. Therefore, this solution is not really working if you want to use it to align lyrics to a hidden Voice in a Staff that also contains other voices. /Mats Trevor Daniels wrote: Graham Percival wrote Friday, November 28, 2008 10:42 AM On Fri, Nov 28, 2008 at 10:04:50AM -, Trevor Daniels wrote: ok, let's make a \hideNotation or \hideAll or something like that for printing lyrics + chords. \hideNotation is a bit too close to \hideNotes. \hideAll, \unHideAll looks good. The documentation can say it applies to the Voice, not the Staff. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing School of Electrical Engineering Royal Institute of Technology (KTH) 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 lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Just chords and lyrics.
Graham Percival wrote Friday, November 28, 2008 10:42 AM On Fri, Nov 28, 2008 at 10:04:50AM -, Trevor Daniels wrote: ok, let's make a \hideNotation or \hideAll or something like that for printing lyrics + chords. \hideNotation is a bit too close to \hideNotes. \hideAll, \unHideAll looks good. The documentation can say it applies to the Voice, not the Staff. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Just chords and lyrics.
On Fri, Nov 28, 2008 at 10:04:50AM -, Trevor Daniels wrote: > > Graham Percival wrote Friday, November 28, 2008 7:49 AM > >> Let me put it this way: should \hideNotes *only* hide the noteheads >> and steams, or should \hideNotes hide everything? My first > > By using a second voice with \hideNotes it is possible to have > overlapping printed slurs (slurs can't be attached to spacer rests). > Not sure if this is a good-enough reason though. That's an *excellent* reason -- the original reason for \hideNotes was to fake slurs between voices (for Bach string parts). ok, let's make a \hideNotation or \hideAll or something like that for printing lyrics + chords. Cheers, - Graham PS err, on second reason, this isn't quite the same as "overlapping printed slurs"... but it reminded me of /my/ reason. :) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: nested staffgroups broken in 2.11.64
graham, On Nov 28, 2008, at 9:29 AM, Graham Percival wrote: <...SNIP...> reinhold's site is the official documentation... At least it's the one that everyone links to... The official documentation is at lilypond.org. thanks graham for the info. Guys, please stop pointing to kainhofer. Use it internally for doc work, but don't send the URLs to -user. this has been confusing me for a while. good to see it clarified. btw, is there a possibility to see the documentation w/out frames? i tried browsing it this morning on the way to work on a mobile device, and the browser there doesn't support frames. would be nice if there was a version without frames. from another point of view, i could imagine that the frame setup would be problematic for visually- impaired users (such as hai-peng) using screen readers. is this the case? just to clarify, i'm not complaining about the "new" form of the documentation. i find the list of contents in a navigation frame really handy when using a full fledged browser. i'm just pondering the problems that frames may pose to alternate forms of browsing. regards, sb -- Simon Bailey Oompa Loompa of Science +43 699 190 631 25 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Just chords and lyrics.
Graham Percival wrote Friday, November 28, 2008 7:49 AM
On Thu, Nov 27, 2008 at 08:15:39PM -0700, Carl D. Sorensen wrote:
On 11/27/08 8:06 PM, "Jonathan Kulp" <[EMAIL PROTECTED]> wrote:
> Graham Percival wrote:
>> On Thu, Nov 27, 2008 at 08:22:51PM -0600, Jonathan Kulp wrote:
>>> makeTransparent = {
>>> \override NoteHead #'transparent = ##t
>>> \override Stem #'transparent = ##t
>>> \override TupletBracket #'bracket-visibility = ##f
>>
>> This could be added to ly/property-init.ly. Oh, and indentation.
>
Let me put it this way: should \hideNotes *only* hide the noteheads
and steams, or should \hideNotes hide everything? My first
instinct as that it should hide everything, but maybe somebody can
think of a reason why not. -- I mean, a reason that isn't highly
tweaked out, like making Schenkerian graphs with lilypond. People
doing that kind of stuff should be able to figure out the
\overrides on their own.
If we *can't* think of a reason why \hideNodes should leave the
slurs and tuplet brackets visible, then I would rather that you
dump your overrides into the existing \hideNotes macro.
By using a second voice with \hideNotes it is possible to have
overlapping printed slurs (slurs can't be attached to spacer rests).
Not sure if this is a good-enough reason though.
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spacing before and after barlines
Basil You should find your answer in the docs. Section "5.4.6 Visibility of objects" in the 2.11 docs gives several different approaches to making objects vanish. I'm sure one of these will be right for you, but I can't say which one without knowing more of your intentions. I suggest you read through this whole section first before deciding - it's not very long. Trevor - Original Message - From: "Basil Crow" <[EMAIL PROTECTED]> To: Sent: Friday, November 28, 2008 4:50 AM Subject: Re: Spacing before and after barlines On Nov 27, 2008, at 11:40 PM, Kieren MacMillan wrote: Have you tried \override BarLine #'X-extent = #'(0 . 0) [or even negative numbers]? Hi Kieren, Thank you for the suggestion. Unfortunately, it doesn't resolve my issue. I also tried zeroing "kern" to no effect. Also, in case it wasn't obvious from my original email, I am working in an environment with Score.timing set to false. Thank you, Basil ___ 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
segno above rehearsal mark
Hi list, I need to put a segno mark on top of one rehearsal mark but lily doesn't allow two marks at the same spot so I searched LSR and came across this http://lsr.dsi.unimi.it/LSR/Item?id=202 unfortunately it doesn't work with 2.11.62 and I am not really good at scheme so I can't figure out why. It'd be great if somone more skilled at scheme could fix this. regards, Tao -- Sensationsangebot nur bis 30.11: GMX FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: nested staffgroups broken in 2.11.64
On Fri, Nov 28, 2008 at 09:19:23AM +0100, Simon Bailey wrote: > Where's the documentation for the current unstable (i.e. 2.11.64) > release? I was under the impression that the documentation at > reinhold's site is the official documentation... At least it's the one > that everyone links to... The official documentation is at lilypond.org. Guys, please stop pointing to kainhofer. Use it internally for doc work, but don't send the URLs to -user. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: nested staffgroups broken in 2.11.64
On 11/28/08, Neil Puttock <[EMAIL PROTECTED]> wrote: > Hi Simon, > > The documentation at kainhofer.com reflects the latest build from the > git repository; the new syntax won't be available until the next > development release (which is most likely imminent). > Where's the documentation for the current unstable (i.e. 2.11.64) release? I was under the impression that the documentation at reinhold's site is the official documentation... At least it's the one that everyone links to... Thanks for the info though. Regards, Sb > Regards, > Neil > -- Do not meddle in the affairs of trombonists, for they are subtle and quick to anger. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
