GDP has a new home, which should be much more reliable:
http://web.uvic.ca/~gperciva/
(follow the link to GDP output)
This is the first draft of Expressive marks. Planned work:
REWRITE
- articulations. clean up first example, rewrite with appendix
list of articulations in mind.
- renam
GDP has a new home, which should be much more reliable:
http://web.uvic.ca/~gperciva/
(follow the link to GDP output)
This is the second draft of Pitches. Please have a look; it's been
significantly updated. Remaining items are
Misc formatting:
- add more links to glossary
- maybe more lin
Rene, thank you for that example. It works nicely, except on lines
where the refrain is by itself. On those lines, the extra space is
inserted even though it isn't needed. Here is the output PDF:
http://hymns.reactor-core.org/lilypond/refrain-rene.pdf
I changed the value 7.4 to 8 to get the r
Hi Risto,
I think this is, in fact, a bug. So I've entered as issue #493:
http://code.google.com/p/lilypond/issues/detail?id=493
Trevor.
On 10/16/07, Risto Vääräniemi <[EMAIL PROTECTED]> wrote:
>
> Dear Trevor and All,
>
> I wrote a small clip to demonstrate the possibly buggy TrillSpanner
Sorry - probably didn't explain very clearly. I couldn't get your code
snippet to work - the slurs don't seem to print at all. When I was
playing around with it, however, I found something in the reference and
managed to get what I wanted with:
% Scottish Bowing - use for straight slurs, hack b
The extra-offset solves the problem of closeness between the arpeggio itself
and the notes. if the fingering is oriented right, the fingering numbers are
still far away. and even with extra-offset on the fingering, there will
still be a visible gap between everything (fingers arpeggio and notes) a
Sorry, my fault!
When I compile the example on its own than everything works perfectly (version
2.11.34). (I compiled it several times with a couple of other fragments. The
error must be in one of the fragments that are compiled before this one.
Strange enough the error seems to influence only
Hello,
has anyone created a comparison between Lilypond source file format and
Braille notation? The Braille notation is described at
http://www.brl.org/music/.
For blind people, Lilypond input file syntax is much moor natural than
for other users.
Tomas Valusek
Hi Tomas,
A Music Braill
Hi Ted,
yesterday I had some time to look at your issue again,
here is a snippet, which works fine, the only caveat is that the refrain
also takes up the same amount of space in e new line.
\version "2.11.19"
\header {
title = "Wir feiern heut ein Fest"
}
\include "italiano.ly"
verseun
2007/10/16, Tomas Valusek <[EMAIL PROTECTED]>:
> For blind people, Lilypond input file syntax is much moor natural than
> for other users.
Yes, very good point!
Ralph Little is working on native Braille output support, as you can see here:
http://lists.gnu.org/archive/html/lilypond-devel/2007-09
What LilyPond version do you use? When I try your example
with version 2.10 and 2.11, it compiles without any problems.
/Mats
Patrick Schmidt wrote:
Dear all,
could anybody please help me with the following problem:
I'm trying to typeset a fragment with 3 repeats and 1 alternative ending b
Dear all,
could anybody please help me with the following problem:
I'm trying to typeset a fragment with 3 repeats and 1 alternative ending but I
get syntax errors.
What's wrong with this syntax?
frag = {
\key d \minor%
\set TabStaff.stringTunings = #'(+2 -3 -7 -12 -17 -24)%Dropped C-Tuning
Dear Trevor and All,
I wrote a small clip to demonstrate the possibly buggy TrillSpanner
behaviour at barline.
If you think it's of any help, feel free to use it.
-Risto
Start %
\version "2.11.32"
{
\override TrillSpanner #'to-barline = ##t
f'1\startTrillSpan | f'1\stopTrillS
13 matches
Mail list logo
