Re: Help with making new Context and Engraver
Carl Sorensen writes:
1. Copied ChordNames context in ly/engraver-init.ly
Modified as it seemed to make sense to me.
\context {
\type Engraver_group_engraver
\name FretDiagram
Interpreting music... warning: Cannot find or create `FretDiagram'
called `uniqueContext1'
Someone (probably Score) should accept the FretDiagram engraver.
What step have I missed?
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
[EMAIL PROTECTED] writes:
Carl Sorensen writes:
1. Copied ChordNames context in ly/engraver-init.ly
Modified as it seemed to make sense to me.
\context {
\type Engraver_group_engraver
\name FretDiagram
Interpreting music... warning: Cannot find or create `FretDiagram'
called `uniqueContext1'
Someone (probably Score) should accept the FretDiagram
engraver.
(context)
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Boxed bar numbers used as rehearsal marks
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. I
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 |.
}
}
--
Christian Hitz
Unterehrendingen, Switzerland
[EMAIL PROTECTED] or [EMAIL PROTECTED]
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Boxed bar numbers used as rehearsal marks
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. I
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 |.
}
}
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
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-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Boxed bar numbers used as rehearsal marks
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. I
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 |.
}
}
--
Christian Hitz
Unterehrendingen, Switzerland
[EMAIL PROTECTED] or [EMAIL PROTECTED]
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Help with making new Context and Engraver
On Wed, 2004-11-10 at 01:31, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Someone (probably Score) should accept the FretDiagram
engraver.
(context)
I changed the name of the context from FretDiagram to FretDiagrams, for
consistency with ChordNames.
Then I added a line to engraver-init.ly:
\context {
\type Score_engraver
\name Score
snip
\accepts FiguredBass
\accepts FretDiagrams
snip
}
I also added a line '\accepts FretDiagrams' to every context that
accepts ChordNames.
I still get this error:
Interpreting music... warning: Cannot find or create `FretDiagrams'
called `uniqueContext1'
Any further ideas?
Carl
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Help with making new Context and Engraver
I hope you have checked that LilyPond really reads the copy of
the engraver-init.ly file that you edit (run lilypond --verbose
to see the full path).
/Mats
Carl Sorensen wrote:
On Wed, 2004-11-10 at 01:31, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Someone (probably Score) should accept the FretDiagram
engraver.
(context)
I changed the name of the context from FretDiagram to FretDiagrams, for
consistency with ChordNames.
Then I added a line to engraver-init.ly:
\context {
\type Score_engraver
\name Score
snip
\accepts FiguredBass
\accepts FretDiagrams
snip
}
I also added a line '\accepts FretDiagrams' to every context that
accepts ChordNames.
I still get this error:
Interpreting music... warning: Cannot find or create `FretDiagrams'
called `uniqueContext1'
Any further ideas?
Carl
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
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-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: battle-plan for 2.5 development
On Friday 05 November 2004 13.49, Han-Wen Nienhuys wrote:
Hi there,
with 2.4 just released, it is time to share what each of us is up to.
In this post, I want to tell you about my plans for LilyPond for the
coming time.
I invite you all to follow this example, and post where you would like
to steer LilyPond to. To keep the discussion focused, please respond
with what you plan to contribute rather than what you want to have.
I will contribute with continuous work on bughunting and -administration, as
usual.
Against your orders, I am here posting some features requests. Some are just
my own ideas (i.e. pretty off-topic, it's better to see them as design ideas
than as feature requests). Some are based on user response bughunting, and
can thus be seen as more relevant.
INTRODUCTION
My target for LilyPond is that it becomes the tool of choice for
high-quality engraving, both for professionals and amateurs. More
concretely spoken: to take the leading position in this area from
SCORE, Finale and Sibelius.
This is just so cool. For the first time we have an open and clear
step-by-step World Domination Plan :)
I believe that in the end, if finale sibelius are to be beaten, someone
should also sell lilypond in some kind of nice boxed form. I believe that it
too often happens that a musician just goes to the music shop, and checks
which programs there are to buy. If lilypond doesn't exist there, then she
will buy some other program. But if there does exist a box with lilypond,
much cheaper than the other programs, then there is a chance that she will
have a look at it and actually see the difference in quality. We simply need
to target the big group that doesn't yet understand about Free Software and
still believe that software is something that you're supposed to buy.
Also, selling stuff like this might make it possible for our Gurus to spend
more time on improving lilypond.
Selling boxed lilypond is probably far-future. And it might not even be our
job, the sellable product might simply be a boxed lilypond-based music
typesetting suite, using e.g. rosegarden as its user interface.
TEX/ENCODING
The next stable release will probably be called LilyPond 3.0, and the
primary goal for that release is to be usable without requiring TeX.
Why?
* It simplifies installation
* reduces size of install (I hear windows users getting scared of the
install procedure, since It starts to download other things!)
* PostScript is a more robust solution, while the TeX solution is
rather complex, and takes relatively much developer time to support.
* Makes the GNOME backend possible... This might be pretty important for World
Domination.
TYPOGRAPHY
The worst outstanding typographical problems should be solved, among
others,
* Rewrite tie formatting
* Dynamics ?
* Cross-staff stems
Especially the first point should also be tackled for the 3.0 release.
OK - I didn't notice this myself, but I guess you know what you're talking
about.. c-tie-tie is the only active tie bug, which doesn't look too serious
to me.
Among bugs, I find that the following ones make more sense to me (though all
aren't layout problems):
- Grace notes is a problem. You mentioned yourself that the grace note code
currently is very hairy; and there do exist severe bugs (e.g. midi-grace).
Plus the problem with skip grace note padding as in {\key c \grace s c d e
f} {grace a g f e d}. I will write more about this in a separate mail (I
haven't gotten the time to continue our discussion on the thread with
subject: grace-timing; I have more to say there).
- [OT] \noBreak seems a bit unlogical to me. It would be nicer with something
like \startNoBreak and \endNoBreak, i.e. defining on which _intervals_
lines / pages shouldn't break. What you mostly want, is to keep e.g. a repeat
on one line or on one page. For me this is a minor issue (I don't use those
commands myself), I just observed that things could be done more logical from
a user's point of view. There have been a few postings on lilypond-user from
people trying things like \repeat unfold 44 {s1 \noBreak}
- [OT] Handle collision of text markup better (this is a future thing.. i just
hope that you'll develop the TeX replacements with this in mind.. one thing
I've been dreaming about is the use of polygonal convex hulls iso rectangular
bounding boxes, but I understand that this might also be quite a nightmare to
implement)
- Also, there are some issues about repeats, which however are far from
urgent. I might post them in a separate mail once I have made my thoughts a
bit more clear than they are now. Basically, I am thinking about the time
concept in lilypond; scores do not always have linear time, question is
whether this in the long run should be solved by extending the time concept,
or by adding enough hacks to make it work well for 99% of the cases.
COMMUNICATION
The development team should be
Re: Boxed bar numbers used as rehearsal marks
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.
/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. I
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 |.
}
}
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
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-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Essay on Free Software
Actually, project Gutenburg [...] Gutenberg, Graham, Gutenberg :-) Werner ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Help with making new Context and Engraver
On Wed, 2004-11-10 at 07:39, Mats Bengtsson wrote: I hope you have checked that LilyPond really reads the copy of the engraver-init.ly file that you edit (run lilypond --verbose to see the full path). /Mats Thanks, Mats. That helped me see what was going on. I was changing engraver-init.ly in sourcedir/ly/ LilyPond was using engraver-init.ly in sourcedir/share/lilypond/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? I copied the file by hand, and it worked (and took a lot less time than make clean, followed by make all). Am I setting up for trouble by just copying the file? Thanks, Carl ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Help on Item/Grob creation
I've (somewhat) successfully created a FretDiagrams context, with a Fret_diagram_engraver. I can sort of make things work. Now I'd like some clarification on Items. 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. 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? 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? 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? Thanks, Carl ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
