Re: \crescTextCresc... 2.10 vs 2.12

[Graham Percival]

On Sat, Jan 31, 2009 at 08:11:11PM -, Trevor Daniels wrote:
>
> The docs for 2.12 don't mention \cresc or \dim.  This could (should) be  
> fixed now.

Rather, \cresc and \dim should finally be removed.  See the
message in ly/spanner-init.ly

Cheers,
- Graham


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

Re: bar numbers at beginning of bar - partial solution

[Paul Scott]

Trevor Daniels wrote:


Paul Scott wrote Saturday, January 31, 2009 8:47 PM



Kieren MacMillan wrote:

The first property description on that page is:
 "X-extent (pair of numbers) Hard coded extent in X direction."


I had no trouble finding X-extent in the docs.  Reading that did not 
tell me what X-extent meant.




So the command I suggested simply convinces the spacing engine 
BarNumbers have no width.


That helps me make sense of what X-extent means.


A more extensive description is rather well hidden in
section 5.5.1 of the Notation Reference.  It says:

"All graphical objects have a reference point, a horizontal extent and 
a vertical extent. The horizontal extent is a pair of numbers giving 
the displacements from the reference point of the left and right 
edges, displacements to the left being negative. The vertical extent 
is a pair of numbers giving the displacement from the reference point 
to the bottom and top edges, displacements down being negative."


Thank you

Paul




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

phrasing slur continued through a repeat?

[Ed Ravin]

I'm using LilyPond Version 2.10.29-1 on a PPC MacOS 10.4 (Tiger).

I'm trying to typeset a piece that has phrasing slurs and repeats.

One of the phrasing slurs starts in the repeated section, and it ends
in the alternative section.

The attached file "slurme.ly.txt" shows the problem.  It compiles without
errors, and the phrasing slur is rendered properly in the first alternative,
but it is not drawn at all in the 2nd alternative (the final measure).

Any ideas?  Do I need to draw the phrasing slur in the 2nd alternative
"by hand"?

Thanks,

-- Ed


#(set-default-paper-size "letter")

\include "english.ly"

\header {
title = "slur and volta problem"
subtitle = "the 2nd repeat should also have a trailing slur"
}
\version "2.10.25"

\score {
\relative c' 
{
\clef treble
\key c \major
\time 3/8
\override Staff.TimeSignature #'style = #'() 

\repeat volta 2 {
e8 ( [ f g ] ) |
a8 \( [ g f ] | \break
} 
\alternative {
{ c8 e4 \) | }
{ c8 g8 c8 \) | }
}
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: bar numbers at beginning of bar - partial solution

[Trevor Daniels]

Paul Scott wrote Saturday, January 31, 2009 8:47 PM



Kieren MacMillan wrote:

The first property description on that page is:
 "X-extent (pair of numbers) Hard coded extent in X direction."


I had no trouble finding X-extent in the docs.  Reading that did not tell 
me what X-extent meant.




So the command I suggested simply convinces the spacing engine BarNumbers 
have no width.


That helps me make sense of what X-extent means.


A more extensive description is rather well hidden in
section 5.5.1 of the Notation Reference.  It says:

"All graphical objects have a reference point, a horizontal extent and a 
vertical extent. The horizontal extent is a pair of numbers giving the 
displacements from the reference point of the left and right edges, 
displacements to the left being negative. The vertical extent is a pair of 
numbers giving the displacement from the reference point to the bottom and 
top edges, displacements down being negative."


HTH
Trevor




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

Re: bar numbers at beginning of bar - partial solution

[Paul Scott]

Kieren MacMillan wrote:

Hi Paul,

I just searched through the docs and I don't find the meaning of 
X-extent.

What does it mean?  What does the above do?


Google
X-extent site:lilypond.org/doc/v2.12

[Hint to everyone: using the 'site' Google-keyword is a great method 
of searching the docs!]


The first hit is
   
 



The first property description on that page is:
 "X-extent (pair of numbers) Hard coded extent in X direction."


I had no trouble finding X-extent in the docs.  Reading that did not 
tell me what X-extent meant.




So the command I suggested simply convinces the spacing engine 
BarNumbers have no width. 


That helps me make sense of what X-extent means.

Thanks,

Paul




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

Re: bar numbers at beginning of bar - partial solution

[Kieren MacMillan]

Hi Paul,

I just searched through the docs and I don't find the meaning of X- 
extent.

What does it mean?  What does the above do?


Google
X-extent site:lilypond.org/doc/v2.12

[Hint to everyone: using the 'site' Google-keyword is a great method  
of searching the docs!]


The first hit is
   


The first property description on that page is:
 "X-extent (pair of numbers) Hard coded extent in X direction."

So the command I suggested simply convinces the spacing engine  
BarNumbers have no width. [n.b., There's probably a more 'kosher' way  
of doing this, but this works for me.]


Now just solve the collision appropriately (with padding or  
whatever).

Why doesn't outside-staff-priority alone solve this?


Don't know — I imagine that o-s-p simply decides the stacking  
*order*, but doesn't adjust the collision engine's algorithm w.r.t.  
horizontal positions/spacing.

Kieren.

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

Re: Persian accidentals

[Kees van den Doel]

> Kees van den Doel wrote:
> > Is there any way to print the koron (60cents flat) and sori 
> (40 cent sharp)?
> > I've defined these pitch alterations by modifying makam.ly but 
> they should really
> > be printed according to the Persian notation.
> >
> > koron = upside down flat, with a triangular body like |>
> > sori = like sharp but with the two horizontal lines angled to 
> form a '>' sign.

> Maybe design a custom glyph in Inkscape, save as a postscript, 
> then 
> connect it to the results of your hacking so far.
> 
> There are a few threads about this type of thing, such as the 
> one 
> starting here:
> http://lists.gnu.org/archive/html/lilypond-user/2008-02/msg00510.html

Can't I just modify the svg of, say accidentals.mirroredflat? I see the svg 
code for that in the
emmentaler-??.svg files, but not sure what I need to do to compile my changes.

Thanks,
Kees


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

Re: \crescTextCresc... 2.10 vs 2.12

[Trevor Daniels]

Frédéric

You are quite right.

I think what was finally done in 2.11 and 2.12 was to make \crescTextCresc 
set crescencii persistently to text and \cresc do a once-only text 
crescendo.   There is a similar symmetry between


dimTextDim (persists) and \dim (once only)

but not between

\dimTextDecresc  and \decresc
\dimTextDecr  and \decr

because \decr is a synonym for \> and \decresc seems not to have been 
implemented.  This seems a pity, as the symmetry is broken.  Perhaps this 
should be corrected in 2.13.


The docs for 2.12 don't mention \cresc or \dim.  This could (should) be 
fixed now.


Trevor


- Original Message - 
From: "Frédéric Bron" 

To: 
Sent: Saturday, January 31, 2009 6:53 PM
Subject: Re: \crescTextCresc... 2.10 vs 2.12


Actually, it's the other way round: \setTextCresc was documented (and 
meant)
to apply only to the next crescendo, although in reality it was never 
reset
and its effect continued for all following crescendi. This behavior was 
fixed

in 2.12 and the effect now really only applies to the next crescendo as
documented.


\setTextCresc worked very well for me in 2.10.33 on the next cresc only.
However with 2.12.2 (Windows), the following gives 2 times cresc:
{ \crescTextCresc c'2\< d'\! c'\< d'\! }

Frédéric


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



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

RE: Make eighth looks like quarter note

[Nick Payne]

You can use

 

\override Stem #'flag-style = #'no-flag 

c8 c

 

and so on to remove the flag on eighth or shorter notes.

 

Nick

 

From: lilypond-user-bounces+nick.payne=internode.on@gnu.org 
[mailto:lilypond-user-bounces+nick.payne=internode.on@gnu.org] On Behalf Of 
Manolo Padron Martinez
Sent: Saturday, 31 January 2009 11:34 PM
To: lilypond-user@gnu.org
Subject: Make eighth looks like quarter note

 

Hi:

I'm really newbie with lilypond. I've been looking in google about how to 
change the look of the eighth note to appear like a quarter note. 

I only want to change how the note is draw into the pdf but I don't want to 
make it a quarter note. In drum partiture looks like better in that way but I 
need that the note sounds (when I get the midi file) like a eighth note.

I attach a screenshot to ilustrate why I want to do that.

Thanks in advance

Manolo Padrón Martínez

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.233 / Virus Database: 270.10.16/1926 - Release Date: 01/30/09 
17:31:00

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

Re: \crescTextCresc... 2.10 vs 2.12

[Frédéric Bron]

> Actually, it's the other way round: \setTextCresc was documented (and meant)
> to apply only to the next crescendo, although in reality it was never reset
> and its effect continued for all following crescendi. This behavior was fixed
> in 2.12 and the effect now really only applies to the next crescendo as
> documented.

\setTextCresc worked very well for me in 2.10.33 on the next cresc only.
However with 2.12.2 (Windows), the following gives 2 times cresc:
{ \crescTextCresc c'2\< d'\! c'\< d'\! }

Frédéric


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

Re: Staves closer to one another

[Fibonacci Prower]

Tried that. Setting \override Staff.VerticalAxisGroup
#'minimum-Y-extent = #'(-3 . 3) to anything lower than -4 . 4 has
absolutely no effect. Something higher does have an effect, though -
which is exactly the opposite to what I want.

Also, what about the font size?

2009/1/31 Wilbert Berendsen 
>
> Op vrijdag 30 januari 2009, schreef Fibonacci Prower:
> > Is there a way to get the staves in lilypond to appear closer
> > together?
>
> See http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Vertical-spacing
>
> best regards,
> Wilbert Berendsen
>
> --
> Frescobaldi, LilyPond editor for KDE: http://www.frescobaldi.org/



--
$0='!/msfQ0yjoV!fe!sfldbi!psup!pmpT'x19xor print+map{("\e[7m \e[0m",
chr ord(chop$0)-1)[$_].("\n")[++$i%72]}split//,unpack'B*',pack'H*',(
$P='F'x18)."8186078739E1F0F0E19FCF19CCE6667383CF0733099E67E7F39"
."FCF218067E7F39FCF319E739F860787399E70F0E1$P"#Perl rulz


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

Re: bar numbers at beginning of bar - partial solution

[Paul Scott]

Kieren MacMillan wrote:

Hi Paul,


Thanks for answering, Mats.  With the following code the bar number
displaces the notes in each bar to the right.  If I remove the two
self-alignment-X overrides the bar number does not displace any music.


\layout
{
\context
{
\Score
\override BarNumber #'X-extent = #'(0 . 0)
}
}


Hi Kieren,

I just searched through the docs and I don't find the meaning of 
X-extent.  What does it mean?  What does the above do?


Now just solve the collision appropriately (with padding or whatever).


Why doesn't outside-staff-priority alone solve this?

Thanks,

Paul




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

vertical system spacing -adjusting only selected systems

[Tom Hall]

Hello List

I have a piece of music for a solo (single stave) instrument, with about 10
systems per page. Of those, I use \bar "||" \break for about two systems per
page, and wish to add additional space/padding before the next system in those
cases (these breaks separate subsections of the piece that still occur on the
same page). 

How best to do this? Notation  Ref. 4.4.2 Vertical spacing between systems
doesn't seem relevant, as applies to _all_ systems?

4.4.3 Explicit staff and system positioning seems to mean that I'll need to set
the explicit position for each of my (say) 10 staves, including working out line
breaks for each, and, I guess, page breaks too? 

Is there an easier way to overide default system break spacing for only selected
systems? Any other thoughts about how I could go about this? 

Regards

Tom






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

Re: \crescTextCresc... 2.10 vs 2.12

[Reinhold Kainhofer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Samstag, 31. Januar 2009 18:09:46 Graham Percival wrote:
> On Sat, Jan 31, 2009 at 04:58:16PM +0100, Frédéric Bron wrote:
> > I upgraded to 2.12 and dicovered that \crescTextCresc is not set for
> > ever instead of just for the next crescendo.
>
> Sounds like a bug.  In fact, I was fairly certain that it's
> already in the issue tracker, although I couldn't find it in 60
> seconds of searching.

Actually, it's the other way round: \setTextCresc was documented (and meant) 
to apply only to the next crescendo, although in reality it was never reset 
and its effect continued for all following crescendi. This behavior was fixed 
in 2.12 and the effect now really only applies to the next crescendo as 
documented.

However, you can easily replace \crescTextCresc by your own function, which 
uses \override instead of \once \override, to change the crescendo type once 
and for all.

IIRC, we also had a discussion a while ago to make \< create a hairpin and 
\cresc to create a text crescendo, which makes much more sense, as the 
pictorial commands already incidate the outcome. I don't know the result of 
that discussion, though.

Cheers,
Reinhold
- -- 
- --
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJhJByTqjEwhXvPN0RAlFrAJ9FoYcJv55nJWphZYwj9xsMtS2gcgCgs285
KKi+1jSSWqhDgfJv+4/khGA=
=bvS2
-END PGP SIGNATURE-


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

Re: grace notes cause extra bar to contain them

[Daniel Hulme]

On Sat, Jan 31, 2009 at 04:26:25PM +, Rob Canning wrote:
> hi,
> not sure whats going on here...
> if i isolate and render only one of the two staves then everything is  
> fine but if i parse the .ly that contains two staves an extra bar gets  
> created that contains the grace notes.
It's not the grace notes that are causing the extra bar, it's the fact
you have manual barlines in different places in each voice. If you
comment out all the \bar "dashed" from your voiceF the superfluous
barlines will disappear.

> any ideas why this is happening?
Although grace notes don't take up the 'regular' time of the bar, they
need to take up special 'grace time' so they can be correctly beamed and
spaced within each group of grace notes. This means that the \bar in
voiceE, which is after the grace notes, is at a different time to the
corresponding \bar in voiceF, which is before the grace notes.

-- 
Always crash crash crashWell come on and let me know
You're happy when I'm running bash   Should I play or should I code?
One test is fine, next is black(with apologies to The Clash)
So if you want a dodgy hack  worse at http://surreal.istic.org/songs


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

Re: \crescTextCresc... 2.10 vs 2.12

[Graham Percival]

On Sat, Jan 31, 2009 at 04:58:16PM +0100, Frédéric Bron wrote:
> I upgraded to 2.12 and dicovered that \crescTextCresc is not set for
> ever instead of just for the next crescendo.

Sounds like a bug.  In fact, I was fairly certain that it's
already in the issue tracker, although I couldn't find it in 60
seconds of searching.

Cheers,
- Graham


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

Re: scheme - notes as variables

[Andrew Wilson]

2009/1/31 Rob Canning :
> #!/usr/bin/perl
>
> sub InsertNotes {
>   my ($num, $form, @notes) = @_;
>
>   my ($output, @temp);
>   while (@notes) {
> (@temp[0..$num-1], @notes) = @notes;
> $output .= sprintf $form, (@temp);
>   }
>   return $output;
> }
>   my @list = qw"a b c d a b c d a f cis d aes b c d g b c d a bes c dis c c c 
> d a e c d a b c d";
>
> my $format = "%s''4\\pp r16 %s'4\\accent %s''1 %s'''4 r8 %s''4\\mf \\accent 
> %s8 \\staccato\n";
>
> print InsertNotes(6, $format, @list);


> what i would like would be numbered variables (%s[1-n]) so i can
> repeat/recall certain elements within the script like this:
>
> like this (quasi-code):
> my $format = "%s1''8 r16 %s1'4 %s2''1 %s3'''4 r8 %s3''4 %s4''8";

The code is using the sprintf function, you can see how this works
with the command perldoc -f sprintf.  What printf needs is a format
string and a list of variables to substitute into the string.  Your
quasi-code is close to being correct, you can follow any of the
format strings (in out case %s) with a format parameter index.
The format parameter index is 1$, 2$, etc.  i.e. %s1$, %s2$

my $format = "%s1$''8 r16 %s1$'4 %s2$''1 %s3$'''4 r8 %s3$''4 %s4$''8";

If you're going to do that then you'll need to alter the number that
you pass to the InsertNotes function or you'll be throwing
entries from the note array.

> also would it be possible to incorperate a second variable reading from a
> second list? %B
>
> my $format = "%sA1''%sB1 r16 %sA1'%sB2 %sA2''%sB1 %sA3'''%sB3 r8 %sA3'' %sB2
> %sA4''"%sB4;

No, not directly.  you would have to interleave the values from the
separate arrays yourself before you called the sprintf function.

I've attached a file with some ides rob3.pl

> also
> to read from a list
> my @list = qw"a b c d a"
>
> is something like this possible?
> my @list = qw"mynotelist.txt"

see rob4.pl

HTH

If you want to learn perl, I recommend learning perl by O'Reilly.

andrew


rob3.pl
Description: Binary data


rob4.pl
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fitting as many lines as possible on a page

[Jonathan Kulp]

Anthony W. Youngman wrote:


Yes, currently the vertical page layouting algorithm of lilypond is sub-
optimal. Lilypond reserves 10% of the total space to make sure it does 
not
overprint staves. This means that 10% of the page will always be 
wasted...
Unfortunately, there is no easy way around this for now, until someone 
starts

working on the vertical staff layouting seriously...


ARRGGG

This is a TERRIBLE feature!!!

Is there any way to disable this? To me, a page turn can easily be the 
difference between a piece of music that's playable, and one that isn't. 
To discover that lily is wasting 10% of the page is a nasty surprise.


A page turn can easily take 30 seconds when you're sitting on a 
bandstand, and if your music is in a lyre then turning pages just isn't 
on (especially when you stick out like a sore thumb because you're in 
the front rank!)


(Actually, this is probably my biggest complaint about lily. I know 
"beautiful" and "playable" tend to go together, but sometimes 
"beautiful" and "practical" don't play nicely together and lily 
overemphasises the beauty. I *need* music to fit either on A5, or one or 
two sides of A4. I'll accept a hefty hit in other areas to avoid that 
third page, and often do have to accept it in nasty tweaks to force the 
music to fit.)


Cheers,
Wol


I don't have this problem as long as I use

ragged-last-bottom = ##f

and (if necessary) specify the page-count I want in the paper block. It 
fills up the whole page of each page with no wasted space in exactly how 
many pages I want.  Give this a try before despairing too much! :)


Jon
--
Jonathan Kulp
http://www.jonathankulp.com


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

\crescTextCresc... 2.10 vs 2.12

[Frédéric Bron]

I upgraded to 2.12 and dicovered that \crescTextCresc is not set for
ever instead of just for the next crescendo.
Is is possible to come back to 2.10 behaviour?
I think it was better because:

2.10: type \crescTextCresc only for text crescendo (once before)
2.12: type \crescTextCresc before and \crescHairpin after (2 commands)
or type \crescHairpin only if needed but then you do not remember if
you need it or not, only when you build the pdf. Another possiblity is
to type \crescTextCresc or \crescHairpin in front of all crescendo so
twice commands compared to 2.10.

Also convert-ly does not do the full job as it just change the name of
the command, not the behaviour.

Frédéric Bron


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

Re: bar "||" kills start-repeat

[Robin Bannister]

Simon Bailey wrote:
so basically that paragraph is telling me to NOT use 
the manual repeat barlines and use \repeat volta instead. 


The documentation uses a lot of different names for repeats. 
When you say "manual repeat barlines" it sounds as though 
you may not be distinguishing 
- manual barlines (inserted using \bar) 
- manual repeats (inserted using \set Score.repeatCommands)


When BarLines says "various repeat commands" 
the partially-initiated might think this means using the command 
"\repeat" in its several variations such as "volta", "unfold", etc.

But I think it is referring to NR 1.4.1.[1]  Specifically, the two sections on
- Normal repeats [2], which are applied to { ... }
- Manual repeat marks, which are inserted inline where branching can occur. 


So instead of "manual barlines", have a look at "manual repeats".

[1] http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Long-repeats
[2] aka "standard", and maybe thought of as "automatic" because not "manual". 


Cheers,
Robin


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

Re: incorrect auto bar and auto beaming ?

[-Eluze]

could it be that the bar counting is not fully correct - try to make some bar
checks  - best is after each measure!
hdh
-- 
View this message in context: 
http://www.nabble.com/incorrect-auto-bar-and-auto-beaming---tp21764013p21764803.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.



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

grace notes cause extra bar to contain them

[Rob Canning]

hi,
not sure whats going on here...
if i isolate and render only one of the two staves then everything is 
fine but if i parse the .ly that contains two staves an extra bar gets 
created that contains the grace notes.

i cant figure out why...
here is the .ly
http://pastebin.com/m672b44fd
see first set of grace notes in the upper part.

any ideas why this is happening?
thanks
rob


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

Re: Fitting as many lines as possible on a page

[Anthony W. Youngman]

In message <200901310053.32352.reinh...@kainhofer.com>, Reinhold 
Kainhofer  writes

On Freitag, 30. Januar 2009 23:37:28 Tim Yang wrote:

It doesn't work. I set the page-count as 2 and Lilypond still uses 3
pages. I think it is because somehow Lilypond thinks these lines don't
fit in 2 pages but in fact there is a lot of space left.


Yes, currently the vertical page layouting algorithm of lilypond is sub-
optimal. Lilypond reserves 10% of the total space to make sure it does not
overprint staves. This means that 10% of the page will always be wasted...
Unfortunately, there is no easy way around this for now, until someone starts
working on the vertical staff layouting seriously...


ARRGGG

This is a TERRIBLE feature!!!

Is there any way to disable this? To me, a page turn can easily be the 
difference between a piece of music that's playable, and one that isn't. 
To discover that lily is wasting 10% of the page is a nasty surprise.


A page turn can easily take 30 seconds when you're sitting on a 
bandstand, and if your music is in a lyre then turning pages just isn't 
on (especially when you stick out like a sore thumb because you're in 
the front rank!)


(Actually, this is probably my biggest complaint about lily. I know 
"beautiful" and "playable" tend to go together, but sometimes 
"beautiful" and "practical" don't play nicely together and lily 
overemphasises the beauty. I *need* music to fit either on A5, or one or 
two sides of A4. I'll accept a hefty hit in other areas to avoid that 
third page, and often do have to accept it in nasty tweaks to force the 
music to fit.)


Cheers,
Wol
--
Anthony W. Youngman - anth...@thewolery.demon.co.uk



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

incorrect auto bar and auto beaming ?

[Rob Canning]

hello,

i have a score which specifies:

\time 4/4 {tomfl16-> toml16 tomml16 tommh16 tomh4.:32\laissezVibrer r8 
tomfl16 toml8:16 tomml16 tomh16 tommh8 tomfl16  toml8 tommh8 tomml16 
tomh16 r4 tomfl16-> toml16 tommh16 tomh16 tomml4.:32\laissezVibrer r8 
tomfl16 toml8:16 tomh16 tomml16 tommh8 tomfl16  toml8 tomh8 tommh16

etc.

full score here:
http://pastebin.com/m59cc4b7e

without any barlines defined

seems things dont add up right...

bars 1 and 14 should have same beaming and beats but here bar 14 is 
short a 16th note at the end and the first four 16th notes are grouped 
in two pairs rather than together.


any idea what i am doing wrong? (score is generated algrithmicaly so i 
cant tweek it to correct it)


thanks

rob


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

Re: Make eighth looks like quarter note

[James E. Bailey]

in this case, why don't you just use <> to show that it's two notes  
happening in the same voice simultaneously. hh8 hh  hh16 


Also, since you're really new to lilypond, you should probably read  
through the entire Learning Manual before attempting to make a score.  
You'll learn a lot about how to actually make a score, rather than  
just trying and searching the documentation when you need to know how  
to do something.


Am 31.01.2009 um 13:34 schrieb Manolo Padron Martinez:


Hi:

I'm really newbie with lilypond. I've been looking in google about  
how to change the look of the eighth note to appear like a quarter  
note.


I only want to change how the note is draw into the pdf but I don't  
want to make it a quarter note. In drum partiture looks like better  
in that way but I need that the note sounds (when I get the midi  
file) like a eighth note.


I attach a screenshot to ilustrate why I want to do that.

Thanks in advance

Manolo Padrón Martínez

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




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

Make eighth looks like quarter note

[Manolo Padron Martinez]

Hi:

I'm really newbie with lilypond. I've been looking in google about how to
change the look of the eighth note to appear like a quarter note.

I only want to change how the note is draw into the pdf but I don't want to
make it a quarter note. In drum partiture looks like better in that way but
I need that the note sounds (when I get the midi file) like a eighth note.

I attach a screenshot to ilustrate why I want to do that.

Thanks in advance

Manolo Padrón Martínez
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Breathe signs too narrow (slim) compared to barlines

[Jiri Zurek (Prague)]

> A property that does work is 'minimum-X-extent, so I changed all 
> 'extra-X-extent --> 'minimum-X-extent, and the attached image is the 
> resulting output.  I don't know if this is more optimal or not, but 
> there is certainly a problem here.  I'll raise this issue on 
> lilypond-devel.


Hallo,
thank you very much. With the setting:
  \once \override BreathingSign  #'minimum-X-extent = #'(-1.6 . 0)
  \once \override BreathingSign  #'thickness = #2.1

to every BreathingSign in the gregorian.ly, I finally got more or less what
I wanted (see the picture).

However, the only thing which a bit discourages me from using Lilypond in my
musicological work is the fact that the documentation is somewhat behind the
current state of the program! I am always refering to the documentation
which is described as the "latest stable" - i.e. 2.12 and the outdated
definition of extra-X-extent are found there (B.13 Layout properties)! 
On the other side, what encourages me to use Lilypond is this fantastic
forum, where one always gets hints how to solve the problems! Marvellous
support.

http://www.nabble.com/file/p21762763/div3.png 
-- 
View this message in context: 
http://www.nabble.com/Breathe-signs-too-narrow-%28slim%29-compared-to-barlines-tp21761121p21762763.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.



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

Re: Fitting as many lines as possible on a page

[Reinhold Kainhofer]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Samstag, 31. Januar 2009 02:06:38 Joe Neeman wrote:
> On Sat, 2009-01-31 at 00:53 +0100, Reinhold Kainhofer wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Freitag, 30. Januar 2009 23:37:28 Tim Yang wrote:
> > > It doesn't work. I set the page-count as 2 and Lilypond still uses 3
> > > pages. I think it is because somehow Lilypond thinks these lines don't
> > > fit in 2 pages but in fact there is a lot of space left.
> >
> > Yes, currently the vertical page layouting algorithm of lilypond is sub-
> > optimal. Lilypond reserves 10% of the total space to make sure it does
> > not overprint staves. This means that 10% of the page will always be
> > wasted... Unfortunately, there is no easy way around this for now, until
> > someone starts working on the vertical staff layouting seriously...
>
> This is only the case for the stretching of systems, AFAICR. It
> shouldn't affect single-staff music.

Isn't stretch-and-draw-page called for all pages, even for single-staff 
systems? At least, I couldn't find any if in Page_breaking::make_pages to 
condition on the number of staves in the systems. That function reserves 10% 
of the space and evenly distributes it to all the spaces between systems 
(which is hardly noticable if you have 10 systems or so, but leaves a lot of 
space at the bottom if you have only one system).

Cheers,
Reinhold
- -- 
- --
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJhDJrTqjEwhXvPN0RAgehAKDYjraqHMVvgCQaAnJGtbCX1sUL/ACeKgU2
if/0cNuhp/om8t3wFy6VOvE=
=55VD
-END PGP SIGNATURE-


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

Re: Breathe signs too narrow (slim) compared to barlines

[Patrick McCarty]

Hi Jiri,

On Sat, Jan 31, 2009 at 12:46 AM, Jiri Zurek (Prague)  wrote:
>
> Although I can control the thickness of barlines in lilypond, I did not find
> the same property in breath signs which are used in old chant instead of
> barlines (divisio minor, maior, maxima, finalis) - these are defined in the
> gregorian.ly which is included in the lilypond distribution, but when I use
> them in conjunction with normal barlines (what I have to do), I would be
> happy that these breath signs are also a bit thicker to be similar to
> barlines - I love the thickness of barlines and therefore I do not want to
> make them slimmer to match the thickness of both items to be the same.
> How can I controll the thickness of the breath sings, please?

As you can see in ly/gregorian.ly, these are defined as BreathingSign
grobs, so you have to use overrides for the 'thickness property of
BreathingSign.

> Another problem is that the 'extra-X-extent property of breath signs does
> not seem to work as the breath signs (and barlines after all too) appear too
> close to the note which is on the left of them even though there is a
> special 'extra-X-extent applied in the gregorian.ly definition. It seems
> that the property is ignored by lilypond in this case. Is it a bug?

It is.  Checking the source code history, it appears that the
'extra-X-extent and 'extra-Y-extent properties were removed from
LilyPond in 2005.  Unfortunately the grob property is still
documented, and the overrides in ly/gregorian.ly still exist.  These
overrides have no affect on the musical output.

A property that does work is 'minimum-X-extent, so I changed all
'extra-X-extent --> 'minimum-X-extent, and the attached image is the
resulting output.  I don't know if this is more optimal or not, but
there is certainly a problem here.  I'll raise this issue on
lilypond-devel.

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

Re: scheme - notes as variables

[Rob Canning]

#!/usr/bin/perl

sub InsertNotes {
   my ($num, $form, @notes) = @_;

   my ($output, @temp);
   while (@notes) {
 (@temp[0..$num-1], @notes) = @notes;
 $output .= sprintf $form, (@temp);
   }
   return $output;
}
   
my @list = qw"a b c d a b c d a f cis d aes b c d g b c d a bes c dis c c c d a e c d a b c d";


my $format = "%s''4\\pp r16 %s'4\\accent %s''1 %s'''4 r8 %s''4\\mf \\accent %s8 
\\staccato\n";

print InsertNotes(6, $format, @list);



You can probably do it with scheme, but why would you want to.

Both @list and $form (and the number of %s to replace) can all
be read from files insterad of hard coded.  This is also
trivial.


this is very usefull and does pretty much what i need - unfortunatly i 
dont really have the skill to extend and modify script as i dont know 
perl - i am going to learn perl as it looks very useful but this might 
take a while.
i have two questions about how to extend this script which maybe 
trivial to add and just a couple of lines, but i understand that it 
might be much more involved and not something i can expect help with here.


but here it goes anyway ;)

what i would like would be numbered variables (%s[1-n]) so i can 
repeat/recall certain elements within the script like this:


like this (quasi-code):
my $format = "%s1''8 r16 %s1'4 %s2''1 %s3'''4 r8 %s3''4 %s4''8";

also would it be possible to incorperate a second variable reading from 
a second list? %B


my $format = "%sA1''%sB1 r16 %sA1'%sB2 %sA2''%sB1 %sA3'''%sB3 r8 %sA3'' 
%sB2 %sA4''"%sB4;


also
to read from a list
my @list = qw"a b c d a"

is something like this possible?
my @list = qw"mynotelist.txt"

if anyone has any ideas how to do the above in perl / scheme or anything 
else i would be most interested


many thanks

rob


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

Re: once and shortcuts

[Mats Bengtsson]

Quoting M Watts :


Nick Payne wrote:

Why is it that I can use, for example:

\once \override Slur #'direction = #DOWN

or

\once \override Slur #'direction = #UP

but

\once \slurDown or \once \slurUp

Generates a syntax error. The same happens with stemUp and stemDown, tieUp
and tieDown, etc.

I'm using 2.12.2.

Nick


I've only seen \once used with \override or \set -- some digging in 
the scm folder would probably reveal why.


It's rather a matter of a limitation in the input syntax, which does not
allow for a macro to follow after \once.

  /Mats



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

Breathe signs too narrow (slim) compared to barlines

[Jiri Zurek (Prague)]

Although I can control the thickness of barlines in lilypond, I did not find
the same property in breath signs which are used in old chant instead of
barlines (divisio minor, maior, maxima, finalis) - these are defined in the
gregorian.ly which is included in the lilypond distribution, but when I use
them in conjunction with normal barlines (what I have to do), I would be
happy that these breath signs are also a bit thicker to be similar to
barlines - I love the thickness of barlines and therefore I do not want to
make them slimmer to match the thickness of both items to be the same.
How can I controll the thickness of the breath sings, please?



%The example here shows the thickness of barlines and breathsings side by
side

\version "2.12.2"

\paper{
  ragged-right=##t
  indent=0\cm
}

\include "gregorian.ly" 

\score {
\new Voice = "cantus" {
  \clef "G_8"
  a4 \divisioMinima
  g \virgula
  c \divisioMaior
  d \bar "|"
  g \divisioMaxima
  d \bar "||"
  e \finalis
}
}

%end of musical example

Another problem is that the 'extra-X-extent property of breath signs does
not seem to work as the breath signs (and barlines after all too) appear too
close to the note which is on the left of them even though there is a
special 'extra-X-extent applied in the gregorian.ly definition. It seems
that the property is ignored by lilypond in this case. Is it a bug?

http://www.nabble.com/file/p21761121/div2.png 
-- 
View this message in context: 
http://www.nabble.com/Breathe-signs-too-narrow-%28slim%29-compared-to-barlines-tp21761121p21761121.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.



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