Re: #(make-dynamic-script)

2006-06-01 Thread Graham Percival


On 31-May-06, at 4:01 AM, Kieren Richard MacMillan wrote:

subPTrans = #(make-dynamic-script (markup #:hspace 0 #:translate 
(cons 4 0) #:line(#:normal-text #:italic sub. #:hspace -0.3 
#:dynamic p )))


However, I find that the extra padding is irritating -- for example, 
with a leading hairpin:

...
The non-padded manually-realigned version (i.e., the last one) is the 
most satisfying to my eye. Since nobody (hint hint!) has gotten back 
to me on how to align the dynamic text within the Scheme construct 
*without* adding all that padding, this is the best I can do for you 
right now...


Hey, weren't you asking for suggestions for hacking lilypond?  ;)

Seriously, I don't know how to do this, but a set of tips on how to 
produce easily-used and beautiful sub p / f espr / etc  signs would 
be of great value to many people (including me).  Please consider 
figuring this out, and if necessary adding patches to lilypond to 
enable this.


Cheers,
- Graham



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


Re: including eps file

2006-06-01 Thread Orm Finnendahl
Hi Han-Wen,

Am 31. Mai 2006, 13:38 Uhr (+0200) schrieb Han-Wen Nienhuys:

 see http://lilypond.org/~hanwen/eps-demo.zip


I can't get the barlow.ly example to compile. the log file is
attached. gs version is 8.15.2 on my machine.

--
Orm





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


Re: including eps file

2006-06-01 Thread Orm Finnendahl
Hi Han-Wen,

sorry, forgot the attachment...

Am 31. Mai 2006, 13:38 Uhr (+0200) schrieb Han-Wen Nienhuys:

 see http://lilypond.org/~hanwen/eps-demo.zip


I can't get the barlow.ly example to compile. the log file is
attached. gs version is 8.15.2 on my machine.

--
Orm





___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
GPL Ghostscript 8.50 (2005-12-31)
Copyright (C) 2005 artofcode LLC, Benicia, CA.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
WARNING: /Unicode /Decoding resource is not accessible but it is useful for 
generating ToUnicode CMap.
Can't find (or can't open) font file n021003l.pfb.
Can't find (or can't open) font file 
/usr/local/lilypond/usr/share/ghostscript/8.50/Resource/Font/NimbusRomNo9L-Regu.
Can't find (or can't open) font file NimbusRomNo9L-Regu.
Can't find (or can't open) font file 
/usr/local/lilypond/usr/share/ghostscript/8.50/Resource/Font/NimbusRomNo9L-Regu.
Can't find (or can't open) font file NimbusRomNo9L-Regu.
Querying operating system for font files...
Didn't find this font on the system!
Substituting font Courier for NimbusRomNo9L-Regu.
Can't find (or can't open) font file n022003l.pfb.
Can't find (or can't open) font file 
/usr/local/lilypond/usr/share/ghostscript/8.50/Resource/Font/NimbusMonL-Regu.
Can't find (or can't open) font file NimbusMonL-Regu.
Can't find (or can't open) font file 
/usr/local/lilypond/usr/share/ghostscript/8.50/Resource/Font/NimbusMonL-Regu.
Can't find (or can't open) font file NimbusMonL-Regu.
Didn't find this font on the system!
Unable to substitute for font.
Error: /invalidfont in findfont
Operand stack:
   Times-Roman   Font   Times-Roman   739153   Times-Roman   --nostringval--   
Times-Roman   NimbusRomNo9L-Regu   Courier   NimbusMonL-Regu
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1   3   
%oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   .runexec2   
--nostringval--   --nostringval--   --nostringval--   2   %stopped_push   
--nostringval--   --nostringval--   1   5   %oparray_pop   2   5   %oparray_pop 
  --nostringval--   --nostringval--   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   5   6   %oparray_pop   
--nostringval--   --nostringval--   --nostringval--   1   -1   1   
--nostringval--   %for_neg_int_continue
Dictionary stack:
   --dict:1124/1686(ro)(G)--   --dict:0/20(G)--   --dict:133/200(L)--   
--dict:133/200(L)--   --dict:133/200(L)--   --dict:17/17(ro)(G)--   
--dict:1124/1686(ro)(G)--
Current allocation mode is local
Last OS error: 2
Current file position is 373825
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user


Re: #(make-dynamic-script)

2006-06-01 Thread Kieren MacMillan

Hi, Graham:


Hey, weren't you asking for suggestions for hacking lilypond?  ;)


In a sense, I already have a million ideas on how to hack Lilypond!  ;-)

The problem is figuring out the best way to start, from a learning- 
curve-plus-community-benefit perspective.


a set of tips on how to produce easily-used and beautiful sub p /  
f espr / etc  signs

would be of great value to many people (including me).


So that sounds like a pretty good place to start, then!?

Please consider figuring this out, and if necessary adding patches  
to lilypond to enable this.


In progress!  =)

Cheers,
Kieren.


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


single quotes in docs (esp. functions, variables, etc.)

2006-06-01 Thread Kieren MacMillan

Hello, all:

1. Just reminding people that cutting and pasting code from the (PDF)  
docs might not always work as expected. In particular, many of the  
examples contain single typographer's quotes (’), where Lilypond  
would be expecting single straight quotes (') -- be sure to  
substitute these out before attempting to typeset/compile your file!


2. Graham: is there any way that the code (or verbatim or  
whatever) sections in the docs could be stylesheeted so that all  
curly quotes are straightened automatically?


Thanks,
Kieren.

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


Re: single quotes in docs (esp. functions, variables, etc.)

2006-06-01 Thread Sven Axelsson

On 01/06/06, Kieren MacMillan [EMAIL PROTECTED] wrote:

Hello, all:

1. Just reminding people that cutting and pasting code from the (PDF)
docs might not always work as expected. In particular, many of the
examples contain single typographer's quotes ('), where Lilypond
would be expecting single straight quotes (') -- be sure to
substitute these out before attempting to typeset/compile your file!

2. Graham: is there any way that the code (or verbatim or
whatever) sections in the docs could be stylesheeted so that all
curly quotes are straightened automatically?


That has been fixed, at least in the 2.9 documentation as far as I can
see. Or are there any particular places in the documentation where
code samples still use the wrong single quotes?

--
Sven Axelsson


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


Re: single quotes in docs (esp. functions, variables, etc.)

2006-06-01 Thread Kieren MacMillan

Hi, Sven:


are there any particular places in the documentation where
code samples still use the wrong single quotes?


Curly quotes are all over Chapter 11 (Interfaces for Programmers),  
e.g. pg. 245.


Don't know for certain that they cause a problem in that context, but
a. I was (am) having difficulty defining a function, and  
remembered that curly single quotes have caused me problems in the  
past (in other situations); and,

b. The docs should be consistent.

Thanks,
Kieren.


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


Tip/Solution: formatting and alignming multi-line instrument names

2006-06-01 Thread Kieren MacMillan

Hello, all:

Robert Memering was having difficulty getting his multi-line  
instrument names to line up.


I've attached the solution I came up with, which I rather like... In  
addition to fixing the alignment insert insect-related euphemism  
here, there are a couple of tweaks that make this particular output  
'just right'.


Best wishes,
Kieren.
_

%% CODE SNIPPET BEGINS
\version 2.9.6

\paper
{
indent = 40\mm
}

\layout
{
\context
{
\Score
\override InstrumentName #'X-offset = #-9.5
\override InstrumentName #'baseline-skip = #2.1
}
}

\score
{

\new StaffGroup = wholestaff

\new Staff
\with
{
instrument = \markup { \center-align { Superius \fontsize #-2  
(Soprano/Alto) } }

}
 \relative c'' { \clef treble c } 
\new Staff
\with
{
instrument = \markup { \override #'(baseline-skip . 2.3 ) \center- 
align { Quinta Pars \fontsize #-2 (Soprano/Alto) } }

}
 \relative c' { \clef treble g' } 
\new Staff
\with
{
instrument = \markup { \center-align { Contratenor \fontsize  
#-2 (Tenore) } }

}
 \relative c' { \clef treble_8 e } 
\new Staff
\with
{
instrument = \markup { \center-align { Tenor \fontsize #-2  
(Tenore) } }

}
 \relative c' { \clef treble_8 c } 
\new Staff
\with
{
instrument = \markup { \center-align { Sexta Pars \fontsize #-2  
(Basso) } }

}
 \relative c' { \clef bass g } 
\new Staff
\with
{
instrument = \markup { \center-align { Bassus \fontsize #-2  
(Basso) } }

}
 \relative c { \clef bass c } 


}
%% CODE SNIPPET ENDS


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


rest positioning failure - please help

2006-06-01 Thread Martin Bergande
I would like to repeat my question how to position a normal rest in single 
staff polyphony since I didn't get any answer. I would be very grateful if 
anybody could help me. It is a while ago since I described the problem as 
follows:

Dear all,

why does b4/rest in the following file.ly position the rest - exactly like 
r4 - to f'', while a4/rest and c4/rest would work as expected? Is there a 
special command apart from tweaking to enforce the b' position?

martin

% start file.ly

\version 2.7.40

\score { 

  \context PianoStaff  

\new Staff  { \override Score.BarNumber #'break-visibility =
#all-invisible  

% Sopran

  { \key f \major \relative c'
{ \partial 4*1 f a g a bes c2 a4\fermata
  d c bes a g a2 \fermata
  b4\rest c d e f e d2 c4\fermata
  a bes a g g f2.\fermata \bar |. } } \\ 

% Alt

  { \relative c' { } } 
  
}

\new Staff {  

% Tenor

  { \clef F \key f \major \relative c 
{ } } \\ 

% Bass

  { \relative c 
{ \hideNotes 

  c4 c c c c c c c 
  c4 c c c c c c c 
  c4 c c c c c c c 
  c4 c c c c c c c \unHideNotes } }

 } 

  

  \layout { 

indent = 00
ragged-right = ##t
ragged-last = ##t

  \context { }
  }

  \midi { 

  \tempo 4 = 92 
  }

}

% end file.ly

p.s. bug-lilypond@gnu.org rejected my message.
-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
  Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer



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


Re: Multi-line instrument names

2006-06-01 Thread Nicolas Sceaux
Robert Memering [EMAIL PROTECTED] writes:

 Hi all,

 I'm very frustrated because I still can't get proper alignment
 of my multi-line instrument names. I wrote a lengthy
 message to this list, including example bitmaps of the
 output, but nobody responded.
 (see http://lists.gnu.org/archive/html/lilypond-user/2006-03/msg00302.html)

 Now, several versions later, and after a careful review
 of the relevant sections of the manual, I still don't see
 the error in my code.

 But it has to be my error, because if this was the intended
 output, someone using multi-line instrument names would have
 complained...

 Below is my source text, I'd be grateful for any hints.

I use the following commands:

#(define-markup-command (hcenter-pad layout props width arg)
  (number? markup?)
  (let* ((arg-stencil (interpret-markup layout props arg))
 (w (interval-length (ly:stencil-extent arg-stencil X)))
 (pad-stencil (ly:make-stencil  
   (cons 0 (if ( w width)
0
(/ (- width w) 2.0)))
   '(-0.1 . 0.1
   (stack-stencil-line 0 
(list pad-stencil arg-stencil pad-stencil

#(define-markup-command (right-pad layout props pad arg)
  (number? markup?)
  (interpret-markup layout props (markup arg #:hspace pad)))

#(define-markup-command (instruments layout props texts) (markup-list?)
  (interpret-markup layout props
   (make-column-markup
(map (lambda (m) (markup #:hcenter-pad 18 #:huge m))
 texts

#(define-markup-command (instrument-name layout props text) (markup?)
  (interpret-markup layout props
   (markup #:right-pad 1 #:instruments (text

instrumentName = 
#(define-music-function (parser location name) (markup?)
  #{ \set Staff . instrument = \markup \instrument-name $name #})

\layout {
  indent = 40 \mm
}

\new StaffGroup 
  \new Staff 
\instrumentName \markup \instruments { Oboe,
   Violino I. }
c''
  
  \new Staff 
\instrumentName \markup Violino II.
g'
  
  \new Staff 
\instrumentName \markup Viola.
\clef alto
e'
  
  \new Staff 
\instrumentName \markup \instruments { Tutti Bassi. }
\clef bass
c
  
 


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


Re: How to work with makefile?

2006-06-01 Thread Anthony W. Youngman
In message [EMAIL PROTECTED], Eduardo Vieira 
[EMAIL PROTECTED] writes

Hello list! Once in a while I see .ly examples posted in this list in a zip file
containing several pieces and a file called makefile. I suppose it is to put
all the parts together. Is it possible to work with it Windows?
 

If you're running it under Cygwin ...

'make' is part of the GNU development tools. I use it, but I'm currently 
using the ?mingw version of lilypond and don't know how to get make to 
work with that.


Cheers,
Wol
--
Anthony W. Youngman - wol at thewolery dot demon dot co dot uk
HEX wondered how much he should tell the Wizards. He felt it would not be a
good idea to burden them with too much input. Hex always thought of his reports
as Lies-to-People.
The Science of Discworld : (c) Terry Pratchett 1999


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


lilypond semitones

2006-06-01 Thread Uzu Maki

http://img293.imageshack.us/my.php?image=semitone7xg.jpg

I would like to know if it's possible to have lilypond do what you can
see on the picture above ?
it's a way to emphasize the place of the semitones.
it's makes it easier for beginners to place their fingers right.

thank you for your help, I can't seem to be able to find anything in
the manuel...
nor on the web...

if it's not possible yet... will il be in the future ?


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


RE: set Hairpin length as percentage of normal?

2006-06-01 Thread Colin Wilding

I use this sort of construction (note-shorter-than-it-looks + hidden note)
quite a lot for tweaks, it's very handy.

Colin
--
View this message in context: 
http://www.nabble.com/set+Hairpin+length+as+percentage+of+%22normal%22--t1652404.html#a4669479
Sent from the Gnu - Lilypond - User forum at Nabble.com.



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


Re: Glissando length

2006-06-01 Thread stmaxx

Hi Ben

I would like to suggest three (more or less sophisticated) solutions for  
your problem:


- you could insert additional line breaks to increase the distance between  
notes


- decrease the gap between note and glissando:
  \once \override Glissando#'gap = #0.1 (standard value is 0.5)

- (my favourite) use skips as spacers between the notes:
  c4 \glissando s8 d4*1/2
  you can even shift both notes symmetrically (see code bellow)


Stefan @Munich


% %%%
\version 2.8.3

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

upper = \relative c' {
c4 d4*3/4 c4  \glissando  s8 d4*3/4
c4 d c4 \glissando s8 d4*1/2
}


lower = \relative c' {
c4 c c c c c c c
}

\score {
\new PianoStaff 
\new Staff = upper  \upper
\new Staff = lower \lower
  
  \layout {
  }
}






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


Re: Glissando length

2006-06-01 Thread Benedict Singer
Thanks for your suggestions! I'd rather avoid doing manual line-breaks, 
as lilypond does the line-breaking well in general. At the scales that 
this is an issue, decreasing the gap wouldn't help either. Somebody else 
pointed me towards \once \override Score.SeparationItem #'padding = #1, 
and this works well. For now, I'm just overriding the padding for the 
entire section to be 1.5, and this does a nice job with the glissandi, 
although it spaces out the whole section way too much (as expected). At 
least this lets me and others see where the glissandi are, and when I 
clean up the score I'll look into using the skips like you suggest. 
Thanks again!


Ben

[EMAIL PROTECTED] wrote:

Hi Ben

I would like to suggest three (more or less sophisticated) solutions 
for your problem:


- you could insert additional line breaks to increase the distance 
between notes


- decrease the gap between note and glissando:
  \once \override Glissando#'gap = #0.1 (standard value is 0.5)

- (my favourite) use skips as spacers between the notes:
  c4 \glissando s8 d4*1/2
  you can even shift both notes symmetrically (see code bellow)


Stefan @Munich


% %%%
\version 2.8.3

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

upper = \relative c' {
c4 d4*3/4 c4  \glissando  s8 d4*3/4
c4 d c4 \glissando s8 d4*1/2
}


lower = \relative c' {
c4 c c c c c c c
}

\score {
\new PianoStaff 
\new Staff = upper  \upper
\new Staff = lower \lower
  
  \layout {
  }
}






___
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: rest positioning failure - please help

2006-06-01 Thread Trent Johnston
Hi Martin,

Mats gave me this help awhile ago which still works.

normalRests = {
  \revert Rest  #'direction
  \revert MultiMeasureRest #'staff-position
}

place this at the start of a file and use \normalRests before the rest you
want to change.

Trent


- Original Message - 
From: Martin Bergande [EMAIL PROTECTED]
To: lilypond-user@gnu.org
Sent: Friday, June 02, 2006 5:21 AM
Subject: rest positioning failure - please help


| I would like to repeat my question how to position a normal rest in
single staff polyphony since I didn't get any answer. I would be very
grateful if anybody could help me. It is a while ago since I described the
problem as follows:
|
| Dear all,
|
| why does b4/rest in the following file.ly position the rest - exactly
like r4 - to f'', while a4/rest and c4/rest would work as expected? Is
there a special command apart from tweaking to enforce the b' position?
|
| martin
|
| % start file.ly
|
| \version 2.7.40
|
| \score {
|
|   \context PianoStaff 
|
| \new Staff  { \override Score.BarNumber #'break-visibility =
| #all-invisible 
|
| % Sopran
|
|   { \key f \major \relative c'
| { \partial 4*1 f a g a bes c2 a4\fermata
|   d c bes a g a2 \fermata
|   b4\rest c d e f e d2 c4\fermata
|   a bes a g g f2.\fermata \bar |. } } \\
|
| % Alt
|
|   { \relative c' { } } 
|
| }
|
| \new Staff { 
|
| % Tenor
|
|   { \clef F \key f \major \relative c
| { } } \\
|
| % Bass
|
|   { \relative c
| { \hideNotes
|
|   c4 c c c c c c c
|   c4 c c c c c c c
|   c4 c c c c c c c
|   c4 c c c c c c c \unHideNotes } }
|
|  }
|
|   
|
|   \layout {
|
| indent = 00
| ragged-right = ##t
| ragged-last = ##t
|
|   \context { }
|   }
|
|   \midi {
|
|   \tempo 4 = 92
|   }
|
| }
|
| % end file.ly
|
| p.s. bug-lilypond@gnu.org rejected my message.
| -- 
|
|
| Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
|   Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
|
|
|
| ___
| 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: single quotes in docs (esp. functions, variables, etc.)

2006-06-01 Thread Graham Percival


On 1-Jun-06, at 7:39 AM, Kieren MacMillan wrote:


Hi, Sven:


are there any particular places in the documentation where
code samples still use the wrong single quotes?


Curly quotes are all over Chapter 11 (Interfaces for Programmers), 
e.g. pg. 245.


Ah, I see.  Lilypond code is fine, but examples are not.

Han-Wen, could you modify  tex/texinfo.tex  so quotes inside an
@example
c'
@end example

remain as ascii?  (I can't understand texinfo.tex)

Cheers,
- Graham



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


Re: lilypond semitones

2006-06-01 Thread Han-Wen Nienhuys

Uzu Maki schreef:

http://img293.imageshack.us/my.php?image=semitone7xg.jpg

I would like to know if it's possible to have lilypond do what you can
see on the picture above ?
it's a way to emphasize the place of the semitones.
it's makes it easier for beginners to place their fingers right.

thank you for your help, I can't seem to be able to find anything in
the manuel...
nor on the web...

if it's not possible yet... will il be in the future ?


It's not possible, but I can add it as a sponsored feature.

Cheers!


--

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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


Re: including eps file

2006-06-01 Thread Han-Wen Nienhuys

Orm Finnendahl schreef:

Hi Han-Wen,

sorry, forgot the attachment...

Am 31. Mai 2006, 13:38 Uhr (+0200) schrieb Han-Wen Nienhuys:

see http://lilypond.org/~hanwen/eps-demo.zip



I can't get the barlow.ly example to compile. the log file is
attached. gs version is 8.15.2 on my machine.



Can you view the PS file with your regular GS ?

The GS error you get is from our bundled GS, which doesn't have a 
Times-Roman font.


--

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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


Re: single quotes in docs (esp. functions, variables, etc.)

2006-06-01 Thread Han-Wen Nienhuys

Graham Percival schreef:


On 1-Jun-06, at 7:39 AM, Kieren MacMillan wrote:


Hi, Sven:


are there any particular places in the documentation where
code samples still use the wrong single quotes?


Curly quotes are all over Chapter 11 (Interfaces for Programmers), 
e.g. pg. 245.


Ah, I see.  Lilypond code is fine, but examples are not.

Han-Wen, could you modify  tex/texinfo.tex  so quotes inside an
@example
c'
@end example

remain as ascii?  (I can't understand texinfo.tex)


should be fixed in CVS.


--

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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


Re: Re: rest positioning failure - please help

2006-06-01 Thread Martin Bergande
Hi Trent,

wonderful, thank you very much! That's what I needed.

Yours,

Martin



  Original-Nachricht 
 Datum: Fri, 2 Jun 2006 08:46:11 +1000
 Von: Trent Johnston [EMAIL PROTECTED]
 An: Martin Bergande [EMAIL PROTECTED],  lilypond-user@gnu.org
 Betreff: Re: rest positioning failure - please help
 
 Hi Martin,
 
 Mats gave me this help awhile ago which still works.
 
 normalRests = {
   \revert Rest  #'direction
   \revert MultiMeasureRest #'staff-position
 }
 
 place this at the start of a file and use \normalRests before the rest you
 want to change.
 
 Trent
 
 - Original Message - 
 From: Martin Bergande [EMAIL PROTECTED]
 To: lilypond-user@gnu.org
 Sent: Friday, June 02, 2006 5:21 AM
 Subject: rest positioning failure - please help
 
 | I would like to repeat my question how to position a normal rest in
 single staff polyphony since I didn't get any answer. I would be very
 grateful if anybody could help me. It is a while ago since I described the
 problem as follows:
 |
 | Dear all,
 |
 | why does b4/rest in the following file.ly position the rest - exactly
 like r4 - to f'', while a4/rest and c4/rest would work as expected?
 Is
 there a special command apart from tweaking to enforce the b' position?
 |
 | martin
 |
 | % start file.ly
 |
 | \version 2.7.40
 |
 | \score {
 |
 |   \context PianoStaff 
 |
 | \new Staff  { \override Score.BarNumber #'break-visibility =
 | #all-invisible 
 |
 | % Sopran
 |
 |   { \key f \major \relative c'
 | { \partial 4*1 f a g a bes c2 a4\fermata
 |   d c bes a g a2 \fermata
 |   b4\rest c d e f e d2 c4\fermata
 |   a bes a g g f2.\fermata \bar |. } } \\
 |
 | % Alt
 |
 |   { \relative c' { } } 
 |
 | }
 |
 | \new Staff { 
 |
 | % Tenor
 |
 |   { \clef F \key f \major \relative c
 | { } } \\
 |
 | % Bass
 |
 |   { \relative c
 | { \hideNotes
 |
 |   c4 c c c c c c c
 |   c4 c c c c c c c
 |   c4 c c c c c c c
 |   c4 c c c c c c c \unHideNotes } }
 |
 |  }
 |
 |   
 |
 |   \layout {
 |
 | indent = 00
 | ragged-right = ##t
 | ragged-last = ##t
 |
 |   \context { }
 |   }
 |
 |   \midi {
 |
 |   \tempo 4 = 92
 |   }
 |
 | }
 |
 | % end file.ly
 |
 | p.s. bug-lilypond@gnu.org rejected my message.
 | -- 
 |
 |
 | Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
 |   Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
 |
 |
 |
 | ___
 | lilypond-user mailing list
 | lilypond-user@gnu.org
 | http://lists.gnu.org/mailman/listinfo/lilypond-user
 |
 

-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
  Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer


-- 


Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
  Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer



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


Glissando fall/rises with no termination

2006-06-01 Thread Benedict Singer

Hi again, another Glissando related question,

This issue was brought up a while ago with the feature request dealing 
with falls, but I'm revisiting it for a piece I'm working on; the 
section in question is for pizz. cello, and I need a way to indicate the 
pitch rising or falling after plucking the note. If there's a better way 
than using \glissando then I'd love to hear about it, but until then 
this is what I have:


glissFall =
   #(define-music-function (parser location note) (ly:music?)
   #{ $note \once \override NoteHead #'transparent = ##t \once 
\override Stem #'transparent = ##t \relative c { f,8 } #})


varVI = \relative c' {
   \clef bass
   \time 3/4
   \override Glissando #'style = #'zigzag

   \glissFall f,4*1/2\glissando r2
   \glissFall c'4*1/2\glissando r2
   \bar ||
}

I'm looking for tips from the Scheme/LilyPond pros to make this a bit 
better. In particular, the ending note is currently hard-coded, so the 
gliss down from the F is much shorter than the one down from the C. Is 
there a way to use the note that \glissFall takes as input and modify it 
to construct the invisible note somehow? So that whatever note you 
\glissFall from, the glissando goes to an invisible note an octave, or 
two octaves, or some fixed interval, below the original note? The other 
thing is that this requires the input to have the duration scaled 
appropriately already so that the invisible eighth note can fit in - can 
this be done in the function too? The second issue is less of a concern 
than the first, since I anticipate using \glissFall on a wide variety of 
starting pitches, and having the falls be uniform in length would be 
excellent.


Thanks so much!

Benedict


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


Re: Glissando fall/rises with no termination

2006-06-01 Thread Graham Percival


On 1-Jun-06, at 8:12 PM, Benedict Singer wrote:


glissFall =
   #(define-music-function (parser location note) (ly:music?)
   #{ $note \once \override NoteHead #'transparent = ##t \once 
\override Stem #'transparent = ##t \relative c { f,8 } #})


varVI = \relative c' {
   \override Glissando #'style = #'zigzag

   \glissFall f,4*1/2\glissando r2
}

I'm looking for tips from the Scheme/LilyPond pros to make this a bit 
better.


1)  If you always want zigzag gliss, I would move that line (with a 
\once) inside the glissFall function.
2)  Only have one command per line inside the music function.  This is 
good advice for lilypond in general, but particularly inside music 
functions!


 In particular, the ending note is currently hard-coded, so the gliss 
down from the F is much shorter than the one down from the C. Is there 
a way to use the note that \glissFall takes as input and modify it to 
construct the invisible note somehow?


Yes, but I don't know how to do it offhand.  See 11.3 Building 
complicated functions for tips.  The basic idea is to use scheme to 
take the initial note, subtract 9 semitones (or whatever you want), and 
create a new (invisible) note.


Cheers,
- Graham



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


Re: Glissando fall/rises with no termination

2006-06-01 Thread Benedict Singer
Thanks to your input I looked in the 2.9 manual rather than the 2.8 
manual and found the excellent examples there; I then came up with the 
functions at the end of this mail; my Scheme training is useful for 
once! Almost everything is perfect, however, I can't seem to suppress 
the ledger lines with the method included below. LedgerLineEngraver is 
all I've been able to find relating to ledger lines. If I have to turn 
them off for the duration of the piece I could probably live with that, 
and just use pitches within the staff, but it would be easier (and more 
portable) to be able to suppress them for a single note. Thanks!


Ben

%%

fallAdjust =
   #(define-music-function (parser location oct note) (number? ly:music?)
   (let ((pitch (ly:music-property (first (ly:music-property note 
'elements)) 'pitch)))

   (make-music
'EventChord
'elements (list (make-music
'NoteEvent
'duration
(ly:make-duration 3 0)
'pitch
(ly:make-pitch (+ (ly:pitch-octave pitch) oct) 
(ly:pitch-notename pitch) 0))
  
glissFall =

   #(define-music-function (parser location note) (ly:music?)
   #{ $note
  \once \override NoteHead #'transparent = ##t
  \once \override Stem #'transparent = ##t
  \once \override Staff.LedgerLineSpanner #'transparent = ##t
  \fallAdjust #-1 $note
   #})
  
glissRise =

   #(define-music-function (parser location note) (ly:music?)
   #{ $note
  \once \override NoteHead #'transparent = ##t
  \once \override Stem #'transparent = ##t
  \once \override Staff.LedgerLineSpanner #'transparent = ##t
  \fallAdjust #1 $note
   #})

varVI = {
   \clef bass
   \time 3/4
   \override Glissando #'style = #'zigzag
   \override Score.SeparationItem #'padding = #1.5

   f4-.^sempre pizz. \glissFall f4*1/2-.\glissando r4
   \glissFall f4*1/2-.\glissando \glissFall c4*1/2-.\glissando r4
   \glissFall f4*1/2-.\glissando \glissFall d4*1/2-.\glissando r4
   f4 c d
   \glissFall g4*1/2-.\glissando r2
  
   f4-. \glissRise f4*1/2-.\glissando r4

   \glissRise f4*1/2-.\glissando \glissRise c4*1/2-.\glissando r4
   \glissRise f4*1/2-.\glissando \glissRise d4*1/2-.\glissando r4
   f4 c d
   \glissRise g4*1/2-.\glissando r2

   \bar ||
}

Graham Percival wrote:


On 1-Jun-06, at 8:12 PM, Benedict Singer wrote:


glissFall =
   #(define-music-function (parser location note) (ly:music?)
   #{ $note \once \override NoteHead #'transparent = ##t \once 
\override Stem #'transparent = ##t \relative c { f,8 } #})


varVI = \relative c' {
   \override Glissando #'style = #'zigzag

   \glissFall f,4*1/2\glissando r2
}

I'm looking for tips from the Scheme/LilyPond pros to make this a bit 
better.


1)  If you always want zigzag gliss, I would move that line (with a 
\once) inside the glissFall function.
2)  Only have one command per line inside the music function.  This is 
good advice for lilypond in general, but particularly inside music 
functions!


 In particular, the ending note is currently hard-coded, so the gliss 
down from the F is much shorter than the one down from the C. Is 
there a way to use the note that \glissFall takes as input and modify 
it to construct the invisible note somehow?


Yes, but I don't know how to do it offhand.  See 11.3 Building 
complicated functions for tips.  The basic idea is to use scheme to 
take the initial note, subtract 9 semitones (or whatever you want), 
and create a new (invisible) note.


Cheers,
- Graham





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


Re: How to work with makefile?

2006-06-01 Thread Simon Dahlbacka
On 6/1/06, Anthony W. Youngman [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Eduardo Vieira[EMAIL PROTECTED] writesHello list! Once in a while I see .ly examples posted in this list in a zip file
containing several pieces and a file called makefile. I suppose it is to putall the parts together. Is it possible to work with it Windows?If you're running it under Cygwin ...
'make' is part of the GNU development tools. I use it, but I'm currentlyusing the ?mingw version of lilypond and don't know how to get make towork with that.at least on 
http://www.mingw.org/download.shtml there is a mingw version of make, so it seems it might be possible, I haven't yet had the time to try, but I'll see during the weekend../Simon 
Cheers,Wol--Anthony W. Youngman - wol at thewolery dot demon dot co dot ukHEX wondered how much he should tell the Wizards. He felt it would not be agood idea to burden them with too much input. Hex always thought of his reports
as Lies-to-People.The Science of Discworld : (c) Terry Pratchett 1999___lilypond-user mailing listlilypond-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