Re: improving docs (was: Break_Align_Order-3)
Graham Percival wrote: On Fri, 14 Mar 2003 17:00:18 -0700 Paul Scott <[EMAIL PROTECTED]> wrote: Han-Wen Nienhuys wrote: How about some diagrams showing the relationships between the various dimensions and what they apply to? Please make some! :-) I wish I knew enough about these to do that. You don't really need to know a lot to improve docs (this isn't just directed at you, Paul; as Han-Wen says, many people have asked for better documentation). If you (or anybody else) is a good proofreader, then simply proofread the documents -- that's what I did until I agreed to finish my cello suite before I graduate (in a few weeks). While you're proofreading, you can add in a bit of rephrasing, extra explanations, or better examples. I can certainly do some of that. My next concern/question would be concerning versions. I use whatever is packaged for Debian unstable - currently 1.6.6. Is there much point improving that documentation when the development is done on a later version? I see the online manual is actually 1.6.0. When you're having trouble understanding something, make a note of it. Once you _do_ understand it, rewrite or create a new piece of documentation that makes it easier to understand. I will see what I can do. Thanks, Paul ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
multiple \scores in a lily-book included file?
scales.ly:
scale= \notes{ blah blah}
\score{ \transpose c'{ \scale }}
\score{ \transpose g'{ \scale }}
\score{ \transpose d'{ \scale }}
\score{ \transpose a'{ \scale }}
-
book1.tex:
\documentclass[]{article}
\usepackage[margin=1cm,nohead,nofoot]{geometry}
\begin{document}
\lilypondfile[26pt]{book1/1scales.ly}
\end{document}
-
Only the first \score is printed once I run it through lilypond-book. I
_could_ split up each scale into its own file, but that would be messy.
This this a bug? (I can't see any reason for this to be a deliberate
feature). Can I pass some option to \lilypondfile[] to make it include
the whole file, not just the first \score setting?
This is still on lily 1.6.6, so I could be missing some recent bug fixes.
Cheers,
- Graham
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-book margins yet again
On Mon, 03 Mar 2003 13:16:22 +0100
Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> The default in ly2dvi is to use 1cm margins both to the left and the
> right, which is much smaller than the default margins for ordinary
> documents in LaTeX. If you want the same, just say
> \usepackage[margin=1cm]{geometry}
While writing my resume, I stumbled across what I was missing: the
nohead and nofoot command (trying to make it all fit onto one page).
When I use this:
\usepackage[margin=1cm,nohead,nofoot]{geometry}
my ly2dvi two-page score remains two pages when I use lilypond-book.
When I used only [margin=1cm], it was three pages.
> somewhere before \begin{document}. I don't see what's so complicated
> about this use of the geometry package.
My previous experience with LaTeX involved things like this:
\geometry{textwidth=296.900mm,textheight=210.00mm}
\oddsidemargin=0in
\textheight=9in
\topmargin=0in
\voffset=0in
\topmargin=0in
That's why I thought that the margins were complicated to set. The two
LaTeX guides I downloaded didn't mention the geometry package. :)
Cheers,
- Graham
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
improving docs (was: Break_Align_Order-3)
On Fri, 14 Mar 2003 17:00:18 -0700 Paul Scott <[EMAIL PROTECTED]> wrote: > Han-Wen Nienhuys wrote: > >>How about some diagrams showing the relationships between the > >>various dimensions and what they apply to? > >Please make some! :-) > > > I wish I knew enough about these to do that. You don't really need to know a lot to improve docs (this isn't just directed at you, Paul; as Han-Wen says, many people have asked for better documentation). If you (or anybody else) is a good proofreader, then simply proofread the documents -- that's what I did until I agreed to finish my cello suite before I graduate (in a few weeks). While you're proofreading, you can add in a bit of rephrasing, extra explanations, or better examples. When you're having trouble understanding something, make a note of it. Once you _do_ understand it, rewrite or create a new piece of documentation that makes it easier to understand. Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: StaffGroup troubles
On Fri, 14 Mar 2003 18:18:29 -0600
>< \context StaffGroup <
> \context Staff = up { e'4 d'
>\bar "||"
>f' e' }
> \context Staff = down { \clef bass c4 g e g } >
> \context Staff = pedal { \clef bass c2 c2 } >
This fragment is missing things like \score{ ... } . I tried playing with
it briefly, but I couldn't easily figure out what was missing.
Try looking at this:
http://lilypond.org/stable/input/template/out-www/template.html
Some of the exmples use StaffGroup.
Cheers,
- Graham
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Problematic TeX
[EMAIL PROTECTED] writes:
> The attached file gives an error when ly2dvi is running the TeX
> produced by lilypond 1.6.8, but ly2dvi seems to cope with it ok.
> However, if I use it in a lilypond-book input file, lilypond-book
> crashes.
Try this patch:
*** scm-hash.cc.~1.22.~ 2003-01-12 23:01:30.0 +0100
--- scm-hash.cc 2003-03-15 00:36:33.0 +0100
***
*** 11,24
#include "scm-hash.hh"
#include "ly-smobs.icc"
! void
copy_scm_hashes (SCM dest, SCM src)
{
! for (int i = SCM_SYMBOL_LENGTH (src); i--;)
for (SCM s = scm_vector_ref (src, SCM_MAKINUM (i)); ly_pair_p(s); s = ly_cdr (s))
{
scm_hashq_set_x (dest, ly_caar (s), ly_cdar (s));
}
}
--- 11,30
#include "scm-hash.hh"
#include "ly-smobs.icc"
! /*
! Return: number of objects.
! */
! int
copy_scm_hashes (SCM dest, SCM src)
{
! int k = 0;
! for (int i = SCM_VECTOR_LENGTH (src); i--;)
for (SCM s = scm_vector_ref (src, SCM_MAKINUM (i)); ly_pair_p(s); s = ly_cdr (s))
{
scm_hashq_set_x (dest, ly_caar (s), ly_cdar (s));
+ k++;
}
+ return k ;
}
***
*** 35,45
{
hash_tab_ = SCM_EOL;
! elt_count_ = src.elt_count_;
smobify_self ();
hash_tab_ = scm_make_vector (gh_int2scm (src.elt_count_ >? 11 ), SCM_EOL);
! copy_scm_hashes (hash_tab_, src.hash_tab_);
}
void
--- 41,51
{
hash_tab_ = SCM_EOL;
! elt_count_ = 0;
smobify_self ();
hash_tab_ = scm_make_vector (gh_int2scm (src.elt_count_ >? 11 ), SCM_EOL);
! elt_count_ = copy_scm_hashes (hash_tab_, src.hash_tab_);
}
void
***
*** 48,56
if (&src == this)
return;
- elt_count_ = src.elt_count_;
hash_tab_ = scm_make_vector (gh_int2scm (src.elt_count_ >? 11), SCM_EOL);
! copy_scm_hashes (hash_tab_, src.hash_tab_);
}
SCM
--- 54,61
if (&src == this)
return;
hash_tab_ = scm_make_vector (gh_int2scm (src.elt_count_ >? 11), SCM_EOL);
! elt_count_ = copy_scm_hashes (hash_tab_, src.hash_tab_);
}
SCM
***
*** 108,120
/*
resize if getting too large.
*/
! if (elt_count_ > 2 * SCM_SYMBOL_LENGTH (hash_tab_))
{
SCM nh = scm_make_vector (gh_int2scm (3* elt_count_+1), SCM_EOL);
! copy_scm_hashes (nh, hash_tab_);
hash_tab_ = nh;
}
-
}
// UGH.
--- 113,124
/*
resize if getting too large.
*/
! if (elt_count_ > 2 * SCM_VECTOR_LENGTH (hash_tab_))
{
SCM nh = scm_make_vector (gh_int2scm (3* elt_count_+1), SCM_EOL);
! elt_count_ = copy_scm_hashes (nh, hash_tab_);
hash_tab_ = nh;
}
}
// UGH.
***
*** 131,137
Scheme_hash_table::remove (SCM k)
{
scm_hashq_remove_x (hash_tab_, k);
! elt_count_ --;
}
Scheme_hash_table::~Scheme_hash_table ()
--- 135,144
Scheme_hash_table::remove (SCM k)
{
scm_hashq_remove_x (hash_tab_, k);
! /*
! don't decrease elt_count_ , as this may cause underflow. The exact
! value of elt_count_ is not important.
!*/
}
Scheme_hash_table::~Scheme_hash_table ()
***
*** 142,148
Scheme_hash_table::to_alist () const
{
SCM l = SCM_EOL;
! for (int i = SCM_SYMBOL_LENGTH (hash_tab_); i--;)
for (SCM s = scm_vector_ref (hash_tab_, gh_int2scm (i)); ly_pair_p(s); s =
ly_cdr (s))
{
l = scm_acons (ly_caar (s), ly_cdar (s), l);
--- 149,155
Scheme_hash_table::to_alist () const
{
SCM l = SCM_EOL;
! for (int i = SCM_VECTOR_LENGTH (hash_tab_); i--;)
for (SCM s = scm_vector_ref (hash_tab_, gh_int2scm (i)); ly_pair_p(s); s =
ly_cdr (s))
{
l = scm_acons (ly_caar (s), ly_cdar (s), l);
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Break_Align_Order-3
Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: How about some diagrams showing the relationships between the various dimensions and what they apply to? Yes! Please make some! :-) I wish I knew enough about these to do that. Seriously -- I've tried explaining this a lot of times: it is very hard for me to write adequate "newbie" documentation, and see where the current doc is lacking, because I know lily so well. If you people want to have better docs, than the best way to ensure that is by helping to write them. I completely understand and appreciate what you have been able to do. I hope to know enough in the near future to be able to help more. I used to hand copy parts professionally for orchestral works and know most of that side of things. I also develop software but still don't know enough about Lily to help more yet. Paul ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Break_Align_Order-3
[EMAIL PROTECTED] writes: > How about some diagrams showing the relationships between the various > dimensions and what they apply to? Yes! Please make some! :-) Seriously -- I've tried explaining this a lot of times: it is very hard for me to write adequate "newbie" documentation, and see where the current doc is lacking, because I know lily so well. If you people want to have better docs, than the best way to ensure that is by helping to write them. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
StaffGroup troubles
I'm a new Lilypond user coming from an ABC background, and I'm having
problems with StaffGroup. It's my understanding that if I want the two
staves in a duet to be connected (other than at the left edge), I need
to enclose the two staves in a StaffGroup. I found an example or two
which I tried emulating, but got error messages. So I tried pasting in
a sample from the Lilypond user manual:
< \context StaffGroup <
\context Staff = up { e'4 d'
\bar "||"
f' e' }
\context Staff = down { \clef bass c4 g e g } >
\context Staff = pedal { \clef bass c2 c2 } >
I saved this in a file (test.ly) by itself and ran it through ly2dvi,
and still got error messages:
Running LilyPond...
GNU LilyPond 1.6.6
Now processing: `test.ly'
Parsing...
/home/wilsonjb/test.ly:0:3: error: parse error, unexpected '<':
<
\context StaffGroup <
/home/wilsonjb/test.ly:0:21: error: parse error, unexpected '{':
\context Staff = up {
e'4 d'
/home/wilsonjb/test.ly:3:30: error: parse error, unexpected '{':
\context Staff = down {
\clef bass c4 g e g } >
/home/wilsonjb/test.ly:4:24: error: parse error, unexpected '{':
\context Staff = pedal {
\clef bass c2 c2 } >
/home/wilsonjb/test.ly:4:41: warning: Braces don't match:
\context Staff = pedal { \clef bass c2 c2
} >
LilyPond failed on an input file (exit status 1).
Trying to salvage the rest.
warning: no LilyPond output found for `test'
Running LaTeX...
Thanks for any help!
Joyce Wilson
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Break_Align_Order-3
Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: The documentation should be updated. If I may, I'd like to say something about the documentation in general. From an end-user standpoint I'd have to say that the docs are the weakest part of Lilypond. I don't mean to say that they're bad. I'm sure it is all very well documented. What I find problematic is that the docs go from a fairly simple example of HOW THINGS WORK straight to a gory-details nuts-and-bolts description of the minute workings of the program. I don't have a problem with that, either. What I find lacking is much of anything in-between. For example: \property Score.MultiMeasureRest \override #'expand-limit = #9 ...was exactly what I needed to adjust the block rest behavior. I didn't need several paragraphs of dense description of how this mechanism works. That I can save for later. As Mats points out, one of the major problems is that there are hundreds of ways (literally: 1.7.14 has 276 different backend properties) in which output can be tuned. The real question is how we make all this information accessible in a sensible way. The current internals documentation is a try, but I'm sure it can be improved. This problem is not unique to Lilypond. Other packages, for example SCORE, also have tons and tons of formatting options that take a long time to learn. How about some diagrams showing the relationships between the various dimensions and what they apply to? Paul Scott ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Break_Align_Order-3
[EMAIL PROTECTED] writes:
> >The documentation should be updated.
>
> If I may, I'd like to say something about the documentation in general.
> >From an end-user standpoint I'd have to say that the docs are the weakest
> part of Lilypond. I don't mean to say that they're bad. I'm sure it is
> all very well documented. What I find problematic is that the docs go from
> a fairly simple example of HOW THINGS WORK straight to a gory-details
> nuts-and-bolts description of the minute workings of the program. I don't
> have a problem with that, either. What I find lacking is much of anything
> in-between. For example:
>
> \property Score.MultiMeasureRest \override #'expand-limit = #9
>
> ...was exactly what I needed to adjust the block rest behavior. I didn't
> need several paragraphs of dense description of how this mechanism works.
> That I can save for later.
As Mats points out, one of the major problems is that there are
hundreds of ways (literally: 1.7.14 has 276 different backend
properties) in which output can be tuned. The real question is how we
make all this information accessible in a sensible way. The current
internals documentation is a try, but I'm sure it can be improved.
This problem is not unique to Lilypond. Other packages, for example
SCORE, also have tons and tons of formatting options that take a long
time to learn.
> about (I *have* found the occasional "fix" on the wiki) . If I manage
> that, the next step would be to post them on the web. I don't know if that
> will happen any time soon but I can wish.
A more direct way would be to add appropriate documentation to test
files in input/ . For example, I've added the following to
input/regression/multi-measure-rest.ly texidoc field.
Rests over measures during longer than 2 wholes use breve rests. When
more than 10 or more measures (tunable through @code{expand-limit})
are used then a different symbol is used.
Patches are always appreciated.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Can Lilypond do dotted time signatures
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: >> > > http://www.arbat.com/erik/screendump.gif >> > > I think it is confusing notation, and should be avoided. This is commonly used in ancient music. I believe we had several requests before for this feature. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Can Lilypond do dotted time signatures
[EMAIL PROTECTED] writes: > On Fri, Mar 14, 2003 at 10:40:27AM +0100, David Boersma wrote: > > On Fri, 14 Mar 2003, Erik Corry wrote: > > > > > Like this one: > > > > > > http://www.arbat.com/erik/screendump.gif > > > > Looks a bit exotic to me... Why wouldn't you use 12/8 in this case? > > I don't know, I didn't invent it. I guess it makes it explict that > there are 4 beats in a bar. I think it is confusing notation, and should be avoided. At first glance, the first measure looks as if it contains five notes. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Problematic TeX
On Friday 14 March 2003 09:55 am, Laura Conrad wrote:
> The attached file gives an error when ly2dvi is running the TeX
> produced by lilypond 1.6.8, but ly2dvi seems to cope with it ok.
> However, if I use it in a lilypond-book input file, lilypond-book
> crashes.
\usepackage[tmargin=0.5in,lmargin=0.5in,rmargin=0.75in,bmargin=0.75in]{geometry}
\title{Sonata Sesta}
\author{Francesco Maria Veracini Florentino (1690-1768)\\
\ <--**and Transcribed by Laura Conrad}
\date{}
\begin{document}
\and maybe? DaveA
--
Lies are the first casualty of peace.
dra@ or http://www.openguitar.com
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Break_Align_Order-3
David Bobroff wrote:
If I may, I'd like to say something about the documentation in general.
From an end-user standpoint I'd have to say that the docs are the weakest
part of Lilypond. I don't mean to say that they're bad. I'm sure it is
all very well documented. What I find problematic is that the docs go from
a fairly simple example of HOW THINGS WORK straight to a gory-details
nuts-and-bolts description of the minute workings of the program. I don't
have a problem with that, either. What I find lacking is much of anything
in-between. For example:
\property Score.MultiMeasureRest \override #'expand-limit = #9
...was exactly what I needed to adjust the block rest behavior. I didn't
need several paragraphs of dense description of how this mechanism works.
That I can save for later.
Now please, I'm not "complaining". I think Lilypond is great. It appeals
to me for many reasons. I just think a "middle ground" level of docs would
be of great value to the new users as well as the "sometimes" users. I
fall into this category. I'll have a project, learn a bunch of Lilypond
tricksand then forget them all before I have another project. Should I
read the docs more? Sure. But knowing a bunch of specific operations
beforehand make it easier to generalize and make use of the nuts-and-bolts
docs.
I kind of agree, but my first priority (I've probably said for over a
year that I will do this as soon as I get some time) is to rewrite the
"fine tuning" sections of the manual. The point is that it would take
too large space to include an example of every possible application of
every property. Remember that most of the properties are common to a
number of different graphical objects, whereas the documentation of each
property currently is only written once (and then duplicated in the
autogenerated part of the manual).
Also, there are typically several ways to apply the same setting.
Consider the setting shown above as an example. If you want the
same setting in the full score or even in a "global.ly" file that you
include in several scores, it would be better to put it within the
paper section:
\paper{
...
MultiMeasureRest \override #'expand-limit = #9
}
whereas the version given above is more appropriate if you want to
have different settings in different bars or in different staves,
for example. My conclusion is that it's essential for most users
to have an idea of the general principles of how to set a property.
However, I agree that the current manual does not manage completely
to describe these fairly simple principles in a clear way.
/Mats
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Break_Align_Order-3
David Bobroff wrote: No spacing entry from BarLine/TimeSignature/KeySignature to `left-edge'/`key-signature'/`left-edge The example is not really complete. You should start from the current default setting and just move the objects that you want to move. Ah, so I was on the right track. I included all of the elements: \property Score.breakAlignOrder = #'( instrument-name left-edge ambitus span-bar breathing-sign clef staff-bar key-signature time-signature custos) And it seems to work. I *still* got lots of error messages in the console. programming error: No spacing entry from BarLine to `' or `key-signature' These are only warnings, Lilypond mostly does something sensible anyway, as you have noticed. If you want to get rid of the warnings or if you are not happy about the default spacing, you should set the space-alist property of the BarLine object to include a value of the spacing also to key-signature. Something like (again untested): \property Score.BarLine \override #'space-alist = #'( (time-signature . (extra-space . 0.75)) (custos . (minimum-space . 2.0)) (clef . (minimum-space . 1.0)) (first-note . (extra-space . 1.3)) (key-signature . (minimum-space . 1.0)) ) You may want to use some other spacing value. /Mats ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Break_Align_Order-3
>> No spacing entry from BarLine/TimeSignature/KeySignature to >> `left-edge'/`key-signature'/`left-edge > >The example is not really complete. You should start from the current >default setting and just move the objects that you want to move. Ah, so I was on the right track. I included all of the elements: \property Score.breakAlignOrder = #'( instrument-name left-edge ambitus span-bar breathing-sign clef staff-bar key-signature time-signature custos) And it seems to work. I *still* got lots of error messages in the console. programming error: No spacing entry from BarLine to `' or `key-signature' >The documentation should be updated. If I may, I'd like to say something about the documentation in general. >From an end-user standpoint I'd have to say that the docs are the weakest part of Lilypond. I don't mean to say that they're bad. I'm sure it is all very well documented. What I find problematic is that the docs go from a fairly simple example of HOW THINGS WORK straight to a gory-details nuts-and-bolts description of the minute workings of the program. I don't have a problem with that, either. What I find lacking is much of anything in-between. For example: \property Score.MultiMeasureRest \override #'expand-limit = #9 ...was exactly what I needed to adjust the block rest behavior. I didn't need several paragraphs of dense description of how this mechanism works. That I can save for later. Now please, I'm not "complaining". I think Lilypond is great. It appeals to me for many reasons. I just think a "middle ground" level of docs would be of great value to the new users as well as the "sometimes" users. I fall into this category. I'll have a project, learn a bunch of Lilypond tricksand then forget them all before I have another project. Should I read the docs more? Sure. But knowing a bunch of specific operations beforehand make it easier to generalize and make use of the nuts-and-bolts docs. One thing I want to do for myself is make a list of all the tricks etc. that I've learned that (like the multimeasure rest adjustment above) and organize them so that they will form the "middle level" docs I'm talking about (I *have* found the occasional "fix" on the wiki) . If I manage that, the next step would be to post them on the web. I don't know if that will happen any time soon but I can wish. Thanks, David Bobroff The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Break_Align_Order
David Bobroff wrote: Mats, Following your advice I checked the internals page and found this: breakAlignOrder (list): Defines the order in which prefatory matter (clefs, key signatures) appears, eg. this puts the key signatures after the bar lines: \property Score.breakAlignOrder = #'( span-bar breathing-sign clef staff-bar key time-signature ) This appeared to be what I needed, ready-made. I pasted it into my Lily source and it did put the key changes after the barlines. Some other things happened, too. The clefs and key signatures at the beginnings of lines don't have staff lines running through them. They appear to be pushed to the left. Also, at the right ends of the lines the staff lines extend to the right of the barline. This also produced a lot of errors: No spacing entry from BarLine/TimeSignature/KeySignature to `left-edge'/`key-signature'/`left-edge The example is not really complete. You should start from the current default setting and just move the objects that you want to move. According to the documentation, the default is (instrument-name left-edge ambitus span-bar breathing-sign clef key-signature staff-bar time-signature custos) If you want to move the key signature after the bar line, you should use (untested): (instrument-name left-edge ambitus span-bar breathing-sign clef staff-bar key-signature time-signature custos) The documentation should be updated. As for changing the multimeasure behavior; I have read the page linked me to but I don't know what the syntax is. Is there a set of instructions for how this is to be used? Certainly, read the "Fine tuning a piece" section in the Tutorial and the "Tuning output" section in the Reference Manual. For your example, something like \property Score.MultiMeasureRest \override #'expand-limit = #9 should work. Another oddity. I was using: \mark 1 \mark \default etc. to put in rehearsal marks. When it got to "10" it did not print a "10" but rather a ":", for "11" I got ";" and for "12" I got an inverted "!". It is actually a little quicker to type in the numbers but this seemed to be a bug. Indeed! /Mats ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Break_Align_Order-2
By adding "left-edge" as here: \property Score.breakAlignOrder = #'( left-edge span-bar breathing-sign clef staff-bar key time-signature ) The clefs all moved back into the staff and the staff no longer pokes out the right side. I still get a lot of error messages, though. David Bobroff The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Break_Align_Order
Mats, Following your advice I checked the internals page and found this: breakAlignOrder (list): Defines the order in which prefatory matter (clefs, key signatures) appears, eg. this puts the key signatures after the bar lines: \property Score.breakAlignOrder = #'( span-bar breathing-sign clef staff-bar key time-signature ) This appeared to be what I needed, ready-made. I pasted it into my Lily source and it did put the key changes after the barlines. Some other things happened, too. The clefs and key signatures at the beginnings of lines don't have staff lines running through them. They appear to be pushed to the left. Also, at the right ends of the lines the staff lines extend to the right of the barline. This also produced a lot of errors: No spacing entry from BarLine/TimeSignature/KeySignature to `left-edge'/`key-signature'/`left-edge As for changing the multimeasure behavior; I have read the page linked me to but I don't know what the syntax is. Is there a set of instructions for how this is to be used? Another oddity. I was using: \mark 1 \mark \default etc. to put in rehearsal marks. When it got to "10" it did not print a "10" but rather a ":", for "11" I got ";" and for "12" I got an inverted "!". It is actually a little quicker to type in the numbers but this seemed to be a bug. Thanks, David Bobroff ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Problematic TeX
The attached file gives an error when ly2dvi is running the TeX
produced by lilypond 1.6.8, but ly2dvi seems to cope with it ok.
However, if I use it in a lilypond-book input file, lilypond-book
crashes.
Here's the lilypond-book error:
Interpreting music...warning: can't find or create `FiguredBass' called `'
warning: FIXME: key change merge
warning: FIXME: key change merge
ERROR: In procedure make-vector:
ERROR: Argument out of range: -2
Error command exited with value 512
Exiting ...
Traceback (most recent call last):
File "/usr/bin/lilypond-book", line 1547, in ?
do_file(input_filename)
File "/usr/bin/lilypond-book", line 1444, in do_file
compile_all_files (chunks)
File "/usr/bin/lilypond-book", line 1222, in compile_all_files
system (cmd)
File "/usr/bin/lilypond-book", line 1128, in system
error ('Error command exited with value %d\n' % st)
File "/usr/bin/lilypond-book", line 638, in error
raise 'Exiting.'
Exiting.
Here's the lilypond file:
\header {
crossRefNumber = "1"
footnotes = ""
subtitle = "II"
tagline = "Lily was here 1.6.8 -- automatically converted from ABC"
title = ""
}
voiceB = \notes {
\property Score.defaultBarType="empty"
\property Staff.instrument = treble
\partial 8
% %LY voices \partial 8
\repeat volta 2 { e''8 ^"Allegro" \bar "|" a''8gis''8a''8
e''8\bar "|" b''4b''8.a''32b''32\bar "|" c'''8a''16
b''16c'''8a''8\bar "|" b''8e''8r8 e''8\bar "|"
a''8gis''8a''8e''8\bar "|" b''4b''8.a''32b''32
\bar "|" c'''8a''16b''16c'''8a''8\bar "|" b''4r8
e''8\bar "|" % 9
a''8gis''8a''8e''8\bar "|" f''8f''4g''!16a''16
\bar "|" g''8fis''8g''8d''8\bar "|" e''8e''4
f''16g''16\bar "|" f''8e''8f''8c''8\bar "|" d''8
d''4e''16f''16\bar "|" e''8d''8e''8b'8\bar "|"
c''4r8 e''8\bar "|" cis''8cis''4d''16e''16\bar "|"
% 18
d''8f''4c''!8\bar "|" b'8b'4c''16d''16\bar "|"
c''8e''4bes'8\bar "|" a'8d''4f''8\bar "|" b'8
e''4g''8\bar "|" c''8f''4a''8\bar "|" g''16a''16
g''16e''16f''16g''16f''16d''16\bar "|" e''16c''16
e''16f''16g''8a''8\bar "|" % 26
b'4.c''8\bar "|" c''4r8 g'8\bar "|" a'8d''4
f''8\bar "|" b'8e''4g''8\bar "|" c''8f''4a''8
\bar "|" g''16a''16g''16e''16f''16g''16f''16d''16
\bar "|" e''16c''16e''16f''16g''8a'8\bar "|"
b'4.c''8\bar "|" c''4.} % 35
\repeat volta 2 { g'8\bar "|" c''8e''8g''8bes''8
\bar "|" cis''8bes''4a''8\bar "|" f''8e''16d''16
e''8d''16cis''16\bar "|" d''8d''8ees''8d''16
cis''16\bar "|" d''8d''8ees''8d''16cis''16\bar "|"
d''4r8 a'8\bar "|" % 41
d''8fis''8a''8c'''8\bar "|" dis''8c'''4b''8
\bar "|" g''8fis''16e''16fis''8e''16dis''16\bar "|"
e''8e''8f''!8e''16dis''16\bar "|" e''8e''8f''!8
e''16dis''16\bar "|" e''4r8 b'8\bar "|" e''8dis''8
e''8b'8\bar "|" % 48
fis''4fis''8.e''32fis''32\bar "|" g''8e''16fis''16
g''8e''8\bar "|" fis''8b''8r8 b'8\bar "|" e''8
dis''8e''8b'8\bar "|" fis''4fis''8.e''32fis''32
\bar "|" g''8e''16fis''16g''8e''8\bar "|" fis''4r8
b''8\bar "|" % 55
gis''8gis''4a''16b''16\bar "|" a''8c'''4g''!8
\bar "|" fis''8fis''4g''16a''16\bar "|" g''4r8 f''!8
\bar "|" e''8e''4f''16g''16\bar "|" f''8a''4e''8
\bar "|" dis''8dis''4e''16fis''16\bar "|" % 62
e''4.b'8\bar "|" \grace {g''8 } fis''4.b'8\bar "|"
\grace {a''8 } g''4.b'8\bar "|" \grace {a''8 } gis''4.
b'8\bar "|" \grace {b''8 } a''4.e''8\bar "|" \grace {
c'''8 } b''4.e''8\bar "|" \grace {d'''8 } c'''4.c'''8
\bar "|" % 69
bes''16c'''16bes''16gis''16a''16b''!16a''16
fis''16\bar "|" gis''8e''8r8 b''8\bar "|" b''16
gis''16a''16fis''16e''8b''8\bar "|" dis''8b''8
d''!8b''8\bar "|" b''16gis''16a''16fis''16e''8
b''8\bar "|" cis''8b''8c''!8b''8\bar "|" b''16
gis''16a''16fis''16e''8a''8\bar "|"
Re: how2
You are correct that #1 and #3 are supported nicely in the latest
1.7.x versions but unfortunately not in the stable versions.
One possible workaround is to attach the text/script to a spacing
note in a parallel line of music:
but it can be tricky to get the horizontal alignment correct.
For #4, take a look at the documentation of the breakAlignOrder
property of the Score context, see
http://lilypond.org/stable/Documentation/user/out-www/lilypond-internals/Score.html
The default settings can be found close to the top of the page and an
example of the syntax is found further down in the paragraph on
Break_align_engraver.
For #2, take a look at the documentation of the MultiMeasureRest
object at
http://lilypond.org/stable/Documentation/user/out-www/lilypond-internals/MultiMeasureRest.html
In particular, you will find a property called expand-limit which is
exactly what you're looking for.
/Mats
David Bobroff wrote:
I posted four problems two days ago. I think I have found an answer to two
of them:
1) Place text markup (tempos) over block rests.
2) Make block rests change style at 10 measures. I want a 10-measure rest
to be a single beam rather than two quads and a double.
3) Place a fermata over a single, centered, measure rest (likely related to
#1).
4) Print key changes *after* the barline rather than before. I normally
see a key change printed following a barline rather than before, but Lily
wants to place it before the barline.
#1 and #3 appear to be addressed in the regression tests. I tried to run
the test on my setup:
\score { \notes {
\time 3/4
R2._\markup { \center << \musicglyph #"scripts-dfermata" \roman "Ad lib"
>> }
R2.^\fermataMarkup
R2.^"4"
c2.
}}
But got an "unexpected NUMBER_IDENTIFIER" error. Then I saw that the
regression tests were for v1.7.x and I'm using 1.6.8. I suppose this is a
version issue. Correct?
I'm still at a loss as to the fix for #2 (change block rest style for 10
bars rest) and #4 (place key changes after the barline).
Thanks,
David Bobroff
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
--
=
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-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
how2
I posted four problems two days ago. I think I have found an answer to two
of them:
>1) Place text markup (tempos) over block rests.
>
>2) Make block rests change style at 10 measures. I want a 10-measure rest
>to be a single beam rather than two quads and a double.
>
>3) Place a fermata over a single, centered, measure rest (likely related to
>#1).
>
>4) Print key changes *after* the barline rather than before. I normally
>see a key change printed following a barline rather than before, but Lily
>wants to place it before the barline.
#1 and #3 appear to be addressed in the regression tests. I tried to run
the test on my setup:
\score { \notes {
\time 3/4
R2._\markup { \center << \musicglyph #"scripts-dfermata" \roman "Ad lib"
>> }
R2.^\fermataMarkup
R2.^"4"
c2.
}}
But got an "unexpected NUMBER_IDENTIFIER" error. Then I saw that the
regression tests were for v1.7.x and I'm using 1.6.8. I suppose this is a
version issue. Correct?
I'm still at a loss as to the fix for #2 (change block rest style for 10
bars rest) and #4 (place key changes after the barline).
Thanks,
David Bobroff
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: altering the tempo of a MIDI file
Mostly, MIDI is interpreted by your soundcard (unless you use a
software MIDI interpreter like Timidity) and the MIDI "standard"
has probably as many interpretations as there are chip manufacturers.
One thing to try is to insert the \tempo directives directly within
the music of each stave. Try both with and without including it also
in the \midi{...} section.
/Mats
Milan M. Horák wrote:
clive CATTERALL scripsit:
I have tried altering
\midi { \tempo 4=120}
up to
\midi { \tempo 4=240}
with no noticeable effect.
I had the same problem under Linux (RedHat) / KDE. A friend of mine having the
same configuration had no problems. MIDI files built by him und by me were
the same, but in his computer they had various tempos, in my computer they
had only the tempo 120 - that is why I think it was no LilyPond bug. Nobody
could understand, what the problem was. Now, after updating LilyPond,
OS-version and sound card, I have no problems more.
Regards
Milan Horak
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
--
=
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-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Can Lilypond do dotted time signatures
On Fri, Mar 14, 2003 at 10:40:27AM +0100, David Boersma wrote: > On Fri, 14 Mar 2003, Erik Corry wrote: > > > Like this one: > > > > http://www.arbat.com/erik/screendump.gif > > Looks a bit exotic to me... Why wouldn't you use 12/8 in this case? I don't know, I didn't invent it. I guess it makes it explict that there are 4 beats in a bar. -- Erik Corry [EMAIL PROTECTED] ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Can Lilypond do dotted time signatures
On Fri, 14 Mar 2003, Erik Corry wrote: > Like this one: > > http://www.arbat.com/erik/screendump.gif Looks a bit exotic to me... Why wouldn't you use 12/8 in this case? But you can do almost everything with with Lily (though it doesn't and probably won't include a kitchen sink, like mozilla) so I don't doubt that it is actually possible. -- David Boersma /"\ ASCII ribbon campaign \ / - X against HTML mail / \ and postings ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
300 Modelos de Cartas comerciais, avisos, convites, propostas, etc.
COMUNICADO IMPORTANTE!! Estamos lançando o KIT DE CARTAS COMERCIAIS, que sana suas dúvidas na elaboração de: agradecimentos, atestados e declarações, avisos, cartas de cobrança, cartas em inglês, comunicados, convites, contratos, propostas, empregos, solicitações e pedidos, telegramas, cartas por e-mail, etc. Composto de 02 (dois) disquetes com 150 modelos de documentos cada um, mais livreto 20 páginas, com técnicas de redação comercial. Indicado para: secretárias em geral, gerências, Rh, executivos, estudantes e empresas de toda ordem. Este kit possui um preço ínfimo em relação ao que poderá gerar no aperfeiçoamento da comunicação de sua empresa. Acesse nossa Home Page para mais detalhes: http://www.redacaocartas.ihp.com.br Ps: Caso não queira receber novas mensagens e novidades sobre esse assunto, acesse: http://www.remova-me.ihp.com.br ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Can Lilypond do dotted time signatures
Like this one: http://www.arbat.com/erik/screendump.gif -- Erik Corry [EMAIL PROTECTED] ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
