In my experience, having played a number of pieces with glissandi, "rips" to us horn players, the straight line notation is quite common. I've seen both.
I input some pieces with glissandi and tried the zigzag option but it didn't look right to me, as I'm not used to to seeing it done that way, so I went back to the default. If I had seen the trill option, and I had tried it and it worked, I might have left it in, but the straight line option is OK. Tim Reeves > Message: 4 > Date: Tue, 30 Jan 2007 21:39:10 -0800 > From: Robert Kennedy <[EMAIL PROTECTED]> > Subject: Glissando notation? > To: lilypond-user@gnu.org > Message-ID: <[EMAIL PROTECTED]> > > It seems in Lilypond (v2.10.14) the default notation for glissandos is > a straight line. I've never seen that notation used for glissando > before so I have no idea why it's the default, but that's OK because > everything can be changed, right? > > So I tried "\override Glissando #'style = #'zigzag", thinking it would > give me the right thing. But it gives me a very thin, light zig-zag > line -- yet another notation that I have never seen used for > glissando. > > The most common, correct notation for glissando looks like a trill > mark. It's a wavy line of varying thickness. > > A statement in the on-line reference documentation suggests that > "\override Glissando #'style = #'trill" might help: > > http://lilypond.org/doc/v2.10/Documentation/user/lilypond- > internals/line_002dspanner_002dinterface#line_002dspanner_002dinterface > > But unfortunately it doesn't work. I still get a light, straight > line. How do I get correct glissando notation? > > -- Robert > > P.S. I really *love* the output I get from Lilypond but even (dare I > say it?) Finale gets this particular piece of notation more or less > right. > > > > > ------------------------------ > > Message: 5 > Date: Tue, 30 Jan 2007 23:52:56 -0600 > From: "Daniel Tonda" <[EMAIL PROTECTED]> > Subject: Re: Guitar fingering and string numbers > To: [EMAIL PROTECTED] > Cc: lilypond-user@gnu.org > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi, from a fellow guitarist! > > > 2007/1/30, Martin Nopola <[EMAIL PROTECTED]>: > > > > \version "2.8.8" on Suse Linux 10 > > > > I have been making beautiful copies of classical guitar music for > > my 8 string guitar. Everything works fine as long as I can copy > > a template such as > > \set Score.skipTypesetting = ##t > > s4*8 > > > > And this works for string number spacing if I enter them as text > > \once \override TextScript #'staff-padding = #3.0 > > b4^"2" e a2-3 > > But the numbers are twice as large as default string numbers. > > > > However, when I try changing variables on my own nothing works. > > This is one of my numerous failures > > \once \override StringNumberOrientations #' Stringnumber = down > > <g\6>4-1 fis e <d\7> > For fingerings and such I always put them between brackets: > > <g\6-1>4 fis e <d\7> %... > > If the fingering is outside the brackets, the fingering orientations > may not work properly. > > > > How do I set > > fingeringOrientation (up,down,left.right) > > \set fingeringOrientations = #'(left) > > > StringNumberOrientations (up, down) > \set stringNumberOrientation = #'(up) > > StringNumber #'staff-padding = #2.0 > > \override StringNumber #'padding = #2.0 > > > fingerNumber #'staff-padding > > > > Someday this will all make sense. > > > > Marty > > > > This is an idea that may work for you. > > I have a settings file where I define certain items, such as fingering > positions, string number positions, etc, and I include it in every > guitar-oriented score I typeset. > > for example: > > rhu = { \set strokeFingerOrientation = #'(up) } > rhd = { \set strokeFingerOrientation = #'(down) } > rhuonce = { \once \set strokeFingerOrientation = #'(up) } > % ...etc > > I include it in the new ly score, such as: > > \version "2.11.14" > > \include "/home/danton67/lib/ly/mydefs.ly" > > % Whenever I need an upward stroke fingering overall I just put: > \rhu > > % If i only need it occassionally, I just put: > \rhuonce > > If you're interested in the "library", ask and I'll send it to your > mail. So as not to burden the list. > > > > > > _______________________________________________ > > lilypond-user mailing list > > lilypond-user@gnu.org > > http://lists.gnu.org/mailman/listinfo/lilypond-user > > > > > -- > Daniel Tonda C. > > > > > ------------------------------ > > Message: 6 > Date: Tue, 30 Jan 2007 21:55:04 -0800 > From: Robert Kennedy <[EMAIL PROTECTED]> > Subject: Documentation: Software architecture overview and details? > To: lilypond-user@gnu.org > Message-ID: <[EMAIL PROTECTED]> > > I am a beginner at Lilypond, and I like it very much, but I am > struggling to understand how to use it. In this e-mail I am going to > ask for pointers to some documentation. I realize that some of it > might not exist -- I am familiar with how open source projects go, > and I understand and accept that these things are always works in > progress. > > LP is a wonderful tool and I'm very happy with the output it's giving > me 99% of the time, but controlling the remaining 1% seems completely > beyond my reach because I haven't been able to find some important > pieces of documentation. I hope they already exist and I just haven't > been able to locate them. > > Anyway, I don't mean to be complaining, even though it might sound > that way. I would just like to know how people (users and developers) > recommend I learn the information required to use this seemingly > excellent program. > > I think most of my struggle is because I haven't found a document that > explains the flow of information through Lilypond. For example, I know > it's possible to embed TeX expressions, and I know it's possible to > embed scheme code. But nowhere have I found an explanation of the form > "First your Lilypond input file is translated into Scheme, and then > the resulting Scheme program is run to produce Tex output." I am left > to guess whether that's what happens, or if something completely > different happens. I am seeking a document that describes the overall > software architecture, first at a high level, and then with enough > detail to actually be useful. > > There is lots of reference material on the individual interfaces and > objects, but I haven't found any explanation of what those things > actually are. Are they basic constructs that any scheme programmer > would instantly recognize? I am an experienced LISP programmer and an > experienced object-oriented programmer (C++, Python, Perl), so Scheme > and object orientation are not completely foreign to me. But I don't > have any clue about these aspects of Lilypond. The documentation gives > an explanation of what a CONS cell is in the "Scheme tutorial" > section, but am I then expected to jump from there to an understanding > of interfaces, grobs, properties, contexts, and objects? If we assume > someone needs an explanation of CONS cells, where is the document that > can help that person use that information to understand what the heck > is going on? Even though I already know what CONS cells are, I think > such a document would help me a great deal. > > I have also not been able to find any systematic information about how > to debug Lilypond files. When I get output different from what I > expect, it seems the only thing I can do is write a message to this > list, and wait for a reply from a helpful wizard. I have been very > lucky that helpful wizards are plentiful and kind, but it would be > nice if there were a way for me to see the generated Scheme code (if > such a thing exists) so I could see, for example, why setting some > property will have no effect, and (hopefully) what different property > or object I should use instead. There must be a way better than > guessing. How can I learn about it? > > Thanks in advance for any help! > > -- Robert Kennedy > > > > > ------------------------------ > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user > > > End of lilypond-user Digest, Vol 50, Issue 100 > **********************************************
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
