Adjusting intersystem spacing with FretDiagrams context
I've succeeded in getting a fret diagram out of a FretDiagrams context.
(The Fret_diagram_engraver is hard-coded to only produce a single
diagram for now, but it still lets me test out contexts).
Here's the .ly file:
\score{
<<
\chords{d}
\new FretDiagrams {d}
\chordmode{d}
>>
}
I've got the output two different sizes (I changed size by adding a size
property to FretDiagram in scm/define-grobs.scm).
The problem I'm seeing right now is that the ChordName is running into
the FretDiagram. It seems that the inter-system spacing isn't
appropriate. But it changes with the size of the FretDiagram, so
perhaps I just don't have some padding right.
Any thoughts on what I would tweak to increase the spacing between the
ChordName and the FretDiagram?
Thanks,
Carl
<><>___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Help with making new Context and Engraver
On Thu, 2004-11-11 at 01:44, Jan Nieuwenhuizen wrote: > This should be a symlink: > > 09:42:47 [EMAIL PROTECTED]:~/lily > $ ls -l share/lilypond/ly > lrwxrwxrwx 1 janneke janneke 21 2004-10-17 14:05 share/lilypond/ly -> > /home/janneke/lily/ly/ > > No, but you may want to find out why the symlink didn't work. > > Jan. I'm working with routines that have not been installed, (never ran make install) because I want to keep the debugging information. When I look at the stuff in share/lilypond/*, none of it is symlinked. [EMAIL PROTECTED] lilypond]$ ls -l share/lilypond/scm/* -rw-rw-r-- 1 carl carl 4070 Mar 22 2004 share/lilypond/scm/auto-beam.scm -rw-rw-r-- 1 carl carl 1286 May 7 2004 share/lilypond/scm/bass-figure.scm -rw-rw-r-- 1 carl carl 3770 Oct 10 05:42 share/lilypond/scm/beam.scm -rw-rw-r-- 1 carl carl 8091 Feb 28 2004 share/lilypond/scm/chord-entry.scm -rw-rw-r-- 1 carl carl 8883 Mar 13 2004 share/lilypond/scm/chord-generic-names.scm -rw-rw-r-- 1 carl carl 8155 Mar 13 2004 share/lilypond/scm/chord-ignatzek-names.scm ... [EMAIL PROTECTED] lilypond]$ ls -l share/lilypond/ly/* -rw-r--r-- 1 carl carl 2320 Nov 5 22:45 share/lilypond/ly/accordion-defs-init.ly -rw-r--r-- 1 carl carl 2733 Nov 5 22:45 share/lilypond/ly/catalan.ly -rw-r--r-- 1 carl carl 1171 Nov 5 22:45 share/lilypond/ly/chord-modifiers-init.ly -rw-r--r-- 1 carl carl 3011 Nov 5 22:45 share/lilypond/ly/declarations-init.ly etc. I assume this is because I haven't run make install. Carl ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Internals URLs in individual web pages vs. one big page
Graham Percival writes: > When looking at the "one big page", we have the following (not correct) > links: > http://lilypond.org/doc/v2.4/Documentation/user/out-www/lilypond/ > lilypond-internals.html#NoteEvent Why is this not correct? Oh, I see, the extra /lilypond/ dir. > Why does the build process give them different URLs? Makinfo generates the urls, and for urls that refer to external documents, it assumes that the external document is generated using the same --split/--no-split options. > Or a better question, how can we fix this? :) With a text substitution afterwards. There's already some perl (yuk) stuff in user/GNUmakefile. I'd have a go myself, but I don't feel like testing it right now. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Internals URLs in individual web pages vs. one big page
When looking at the web docs in individual pages, we have the following (correct) links to the internals: http://lilypond.org/doc/v2.4/Documentation/user/out-www/lilypond- internals/NoteEvent.html#NoteEvent When looking at the "one big page", we have the following (not correct) links: http://lilypond.org/doc/v2.4/Documentation/user/out-www/lilypond/ lilypond-internals.html#NoteEvent Why does the build process give them different URLs? Or a better question, how can we fix this? :) Cheers, - Graham ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Boxed bar numbers used as rehearsal marks
Anthony W. Youngman wrote: In message <[EMAIL PROTECTED]>, Mats Bengtsson <[EMAIL PROTECTED]> writes Sorry, I'll learn to read some time. However, if you want boxed bar numbers, then I propose to take a look at the example bar-number-regular-interval.ly in the Tips and Tricks document, which automatically gives boxed bar numbers at regular intervals without any \mark commands in the code. Except that's NOT what is wanted. What is wanted is a rehearsal mark, which is normally used at the start of a segue or new melody - ie at random not regular intervals. For example, the piece I've just been doing (admittedly I've been using letters) has marks at various intervals - sometimes 4, often 8, sometimes 12 bars. And just this evening I've been playing pieces marked up exactly as the OP referred to - using bar numbers as rehearsal marks at random intervals. This is *typical* of medley-style Concert Band pieces. Since you have to manually place the \mark commands anyway it might not be that much more trouble to just put the bar numbers in manually. You can just put this at the beginning to avoid having to use \markup and \box and \mark \override Score.RehearsalMark #'print-function = #(make-stencil-boxer 0.15 0.3 0.3 Text_interface::print) OTOH if you don't know ahead of time what the bar numbers will be (maybe you want to move things around) it would be great to know how to build an expression which will get the current bar number and put it into the \mark. It looks like Christian might be close. It would be great to have an answer to Christian's original question. Paul Scott ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Boxed bar numbers used as rehearsal marks
In message <[EMAIL PROTECTED]>, Mats Bengtsson
<[EMAIL PROTECTED]> writes
Sorry, I'll learn to read some time. However, if you want boxed
bar numbers, then I propose to take a look at the example
bar-number-regular-interval.ly in the Tips and Tricks document,
which automatically gives boxed bar numbers at regular intervals
without any \mark commands in the code.
Except that's NOT what is wanted. What is wanted is a rehearsal mark,
which is normally used at the start of a segue or new melody - ie at
random not regular intervals.
For example, the piece I've just been doing (admittedly I've been using
letters) has marks at various intervals - sometimes 4, often 8,
sometimes 12 bars.
And just this evening I've been playing pieces marked up exactly as the
OP referred to - using bar numbers as rehearsal marks at random
intervals. This is *typical* of medley-style Concert Band pieces.
Cheers,
Wol
/Mats
Christian Hitz wrote:
The main point of my example is that the rehearsal mark is not a
consecutive number but the current bar number.
Christian
Am 10.11.2004 um 12:51 schrieb Mats Bengtsson:
A simplified version of what you wrote can be found in
http://lists.gnu.org/archive/html/lilypond-user/2004-09/msg00160.html
/Mats
Christian Hitz wrote:
Hi list,
in wind band music I have encountered four types of rehearsal
marks: consecutive letters, consecutive numbers, bar numbers at
regular intervals and bar numbers at special places. The first
three types are explained in the manual.
With the help of the manual I could piece together the fourth type.
think the following example would make a good addition to the
Rehearsal mark (5.15.3) or Bar number (5.15.4) section.
Christian
\header {
texidoc = "Boxed bar numbers used as rehearsal marks"
}
\version "2.4.0"
\score {
\context Staff \transpose c c' {
\set Score.markFormatter
= #(lambda (mark context)
(make-bold-markup
(make-box-markup (number->string
(ly:context-property context 'currentBarNumber)
c1 \bar "||" \mark \default c1 c1 \mark \default c1 \bar "|."
}
}
--
Anthony W. Youngman - wol at thewolery dot demon dot co dot uk
HEX wondered how much he should tell the Wizards. He felt it would not be a
good idea to burden them with too much input. Hex always thought of his reports
as Lies-to-People.
The Science of Discworld : (c) Terry Pratchett 1999
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ec-fonts-mftraced cygwin postinstall
Bertalan Fodor writes: > Would you apply this? Applied slightly modified version. Thanks. > (Note: I changed @SHELL@ to /bin/sh because I don't know how to set > this in the makefiles.) That was a LilyPond/stepmake artifact. Jan. BTW, the patch was malformed; your email reader is broken, it wraps lines. > +rm -f $(find /var/lib/texmf /var/spool/texmf /var/cache/fonts -name > ec*pk' -or -name 'ec*tfm') -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Patch for ec-fonts-mftraced cygwin postinstall
Would you apply this? (Note: I changed @SHELL@ to /bin/sh because I don't know how to set this in the makefiles.) Index: cygwin/postinstall-ec-fonts-mftraced.sh === RCS file: /cvsroot/lilypond/sauter-fonts-mftraced/cygwin/postinstall-ec-fonts-mftraced.sh,v retrieving revision 1.1 diff -u -r1.1 postinstall-ec-fonts-mftraced.sh --- cygwin/postinstall-ec-fonts-mftraced.sh19 Oct 2004 16:54:13 -1.1 +++ cygwin/postinstall-ec-fonts-mftraced.sh11 Nov 2004 09:44:26 - @@ -1,10 +1,10 @@ [EMAIL PROTECTED]@ +#!/bin/sh # /etc/postinstall/ec-fonts-mftraced.sh # cleanup old fonts touch /tmp/.ec-fonts-mftraced -rm $(find /var/lib/texmf /var/spool/texmf /var/cache/fonts -name 'ec*pk' -or -name 'ec*tfm') +rm -f $(find /var/lib/texmf /var/spool/texmf /var/cache/fonts -name 'ec*pk' -or -name 'ec*tfm') rm -f /tmp/.ec-fonts-mftraced # update tex installation -mktexlsr +if [ -e /bin/mktexlsr ]; then mktexlsr; fi ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Help on Item/Grob creation
Carl Sorensen writes:
> I've (somewhat) successfully created a FretDiagrams context, with a
> Fret_diagram_engraver.
Great.
> As part of the engraver, I have the code
>
> fret_diagram_ = make_item ("FretDiagram",SCM_EOL); //WHAT GOES HERE?
>
> It appears to me that the "name" of the Item, FretDiagram, is in fact a
> pointer into scm/define-grobs.scm.
Yes.
> Since I want to make a FretDiagram
> Item, I believe I need to make an alist entry for FretDiagram in
> scm/define-grobs.scm. Is there any documentation for what goes in the
> alist entry?
In the alist entry go the immutable properties that describe a Grob.
Look at other Grob definitions for inspiration.
> Also, as part of making the item, I need to have a "cause", which is
> SCM_EOL in this particular example. It appears from some of the
> internal documentation that the cause is a music expression, generally
> the one responsible for creating the Item/Grob. What is the cause used
> for?
Cause is used for constructing error and warning messages to the user.
You use the music request form try_music () that caused the engraver
to create the Item.
> Also, what is the difference between an Item and a Grob? From some
> earlier descriptions, I think that an Item is one type of Grob; that is,
> all Items are Grobs, but not all Grobs are Items (i.e. some Grobs can be
> Spanners, etc.). Is this correct?
Yes, that's correct.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Help with making new Context and Engraver
Carl Sorensen writes: > I was changing engraver-init.ly in sourcedir/ly/ > LilyPond was using engraver-init.ly in sourcedir/share/lilypond/ly/. This should be a symlink: 09:42:47 [EMAIL PROTECTED]:~/lily $ ls -l share/lilypond/ly lrwxrwxrwx 1 janneke janneke 21 2004-10-17 14:05 share/lilypond/ly -> /home/janneke/lily/ly/ > I expected that make would copy the file, but apparently it wasn't. Do > I need to do make clean in order to get the file copied? No, but you may want to find out why the symlink didn't work. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
