adding fingering diagrams

2006-11-18 Thread Chris Capoccia
is it possible to place fingering diagrams in the score like this:
http://www.interopp.org/flute/htm/fu_fingerings.htm
the solid holes are closed finger holes. the open holes are not covered by the
finger. the cracked closed hole is the one used to make vibrato.

i don't need to reproduce the diagram clint gloss uses, i would be happy with
something much simpler:
three characters in a vertical line above or below the staff for each note. i
could come up with my own scheme for which characters represent whether the hole
should be covered or not. maybe x for covered, o for open and ~ for closed with
vibrato.

in case you're curious, the notation is for the fujara. it's a traditional three
hole overtone flute from central slovakia.



___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Any way to turn off "warning: ignoring too many clashing note columns"?

2006-11-18 Thread Trevor Bača

Hi,

Unlike certain other programs, I've found that the warnings that Lily
issues during parsing, interpretation and preprocessing usually matter
a great deal; warnings are usually a sign either that there's a bug
that needs to be reported or that I'm doing something wrong that will
eventually come to haunt me.

For that reason I like to run completely 'clean' lilypond files that
generate no warnings whatsoever. And, in fact, this has always been
possible to do, even in very complex cases.

But now I've run into the following case:

%%% BEGIN %%%

\version "2.10.0"

\new Staff <<
  \new Voice \with {
 \override Stem #'direction = #up
  } { c''4 c''4 c''4 c''4 }
  \new Voice \with {
 \override Stem #'transparent = ##t
 \override NoteHead #'duration-log = #1
  } { e'4 e'4 e'4 e'4 }
  \new Voice \with {
 \override Stem #'direction = #down
  } { c'4 c'4 c'4 c'4 }




%%% END %%%

GNU LilyPond 2.10.0
Processing `348.ly'
Parsing...
Interpreting music... [1]
Preprocessing graphical objects...
348.ly:6:27: warning: ignoring too many clashing note columns
   } { c''4 c''4 c''4
  c''4 }
348.ly:6:22: warning: ignoring too many clashing note columns
   } { c''4 c''4
 c''4 c''4 }
348.ly:6:17: warning: ignoring too many clashing note columns
   } { c''4
c''4 c''4 c''4 }
348.ly:6:12: warning: ignoring too many clashing note columns
   } {
   c''4 c''4 c''4 c''4 }
Layout output to `348.ps'...
Converting to `348.pdf'...


The resulting output is letter-prefect (see ex), but there are copious
warnings. What's going on here is that I've concocted a special
notation that renders the middle notes of each 'chord' stemless with
Stem #'transparent = ##t (rather than, say, \remove Stem_engraver).
The Stems in the middle Voice still exist, though, so that clashing
note column warnings result.

So my question is: is there any way to turn off the clashing note
column warnings? I think this is the one place where one of Lily's
warnings truly is completely harmless and I feel safe turning it off.
More importantly, I really need to see any *other* warnings that Lily
generates, which is quite hard given the original sourcefile (which
runs many thousands of lines).

(I could of course pass Lily's output through sed, but that doesn't
seem as clean as a commandline option to disregard this specific
warning, for example.)

Alternatively, is there some way I can doctor up my example to avoid
the clashing note column warnings in the first place (which would
actually be preferrable)?


--
Trevor Bača
[EMAIL PROTECTED]


clashing-note-columns.png
Description: PNG image
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Hiding empty staves

2006-11-18 Thread Erik Sandberg
On Friday 17 November 2006 22:28, Bob Kline wrote:
> Andrew Longland-Meech wrote:
> > Thank you. I've got it now, even though it seems a bit illogical to put
> > one bit of layout in \layout and the other in with the notes, when they
> > both do a similar job!!
> >
> > On Thu, 2006-11-16 at 10:53 -0800, Graham Percival wrote:
> >> Andrew Longland-Meech wrote:
> >>>   \override Score.VerticalAxisGroup #'remove-first = ##t   "
> >>>
> >>> I don't understand where this should go. Is it in the \score section?
> >>> Or in the \layout section? Or in with the notes? Please can someone
> >>> guide me in the right direction?
> >>
> >> Please see chapter 5 of the docs.
>
> Could one of you have pity on a poor clueless user and give an example
> showing where these two directives go?  My attempts always end up with
> the unwanted staff omitted on the second system of the music, but
> included for the first system.  Here's an example of what I'm trying:
>
> \score {
> \override Score.VerticalAxisGroup #'remove-first = ##t
> \context ChoirStaff <<
> \context Staff = women <<  >>
> \new Lyrics 
> \context Staff = men <<  >>
>
> \layout {
>  \context { \RemoveEmptyStaffContext }
> }
> }
>
> I have looked at chapter 5 of the docs (I assume we're talking about the
> chapter 5 in the latest released version of lp, rather than the versions
> currently shipped with most Linux distros), and my poor brain just isn't
> getting it, as I don't see the part that says *where* to put the
> \override command.

The problem above, is that { } have different meanings in different places: 
Usually {  } means sequential music, but the { } after \score are special: it 
starts with a _single_ music expression, followed by optional \layout (etc) 
blocks. So you must make \override part of the music expression, like:

\score {
  <<
 \override Score.VerticalAxisGroup #'remove-first = ##t
 \context ChoirStaff <<
 \context Staff = women <<  >>
 \new Lyrics 
 \context Staff = men <<  >>
  >>
 \layout{...}
}

-- 
Erik


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


hairpinToBarline (bug or feature?)

2006-11-18 Thread Thomas Frank
To me it seems like hairpinToBarline works correctly in 2.10 as long as the 
(de-)crescendo ends in '\!' and not in an absolute dynamic like '\f'.

Is this the way it is supposed to work? Is there any switch to make it work 
with absolute dynamics, too? '\!\f' doesn't work.

cheers
Thomas


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


hairpinToBarline (bug or feature?)

2006-11-18 Thread Thomas Frank

To me it seems like hairpinToBarline works correctly in 2.10 as long as the 
(de-)crescendo ends in '\!' and not in an absolute dynamic like '\f'.

Is this the way it is supposed to work? Is there any switch to make it work 
with absolute dynamics, too? '\!\f' doesn't work.

cheers
Thomas


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Crazy idea: point-and-click for PDF end-users?

2006-11-18 Thread Kieren MacMillan

Hey, y'all!

I don't know any PDF viewer with annotation capabilities (that can  
be saved to the PDF).


Preview (built into Mac OS X) allows you to do this.

Cheers,
Kieren.


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Crazy idea: point-and-click for PDF end-users?

2006-11-18 Thread Iain Archibald

Bertalan Fodor wrote:
That depends on the PDF viewer. I don't know any PDF viewer with 
annotation capabilities (that can be saved to the PDF).


Bert
I think you'd need to use a full version of Acrobat to enable you to 
change a PDF file?




___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Crazy idea: point-and-click for PDF end-users?

2006-11-18 Thread Johan Vromans
Eduardo Vieira <[EMAIL PROTECTED]> writes:

> Hi! Foxit Reader already gives the ability of annotating PDFs,
> drawing shapes, etc, even for free.

Gratis, not free.

http://www.gnu.org/

-- Johan


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user