\\ constructs and things that cross measures

2007-08-25 Thread Ed Ravin
In the LilyPond docs, it says:

   
http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Basic-polyphony#Basic-polyphony

   These voices are all separate from the voice that contains the notes just
   outside the  \\  construct. This should be noted when making changes at
   the voice level. This also means that slurs and ties cannot go into or out
   of a  \\  construct.

And this is my problem - I've got a measure like this, where I'm trying to
draw a crescendo hairpin from the 3rd beat of this measure to the 2nd beat
of the next measure:

 { d8. cs16 } \\ { f,8 g f d' \ g b f' g c ef2 \! }  \\ {
s4 s4 s4 s4 \ }  |

Obviously this doesn't work - I get warning: unterminated (de)crescendo
on this measure and warning: can't find start of (de)crescendo on the \!
in the next measure.

What's the right way to deal with this kind of problem?  It happens
elsewhere where I'm trying to put pedal marks or slurs across measures.  Do
I need to make the  {} \\ {}  sections wider to cover multiple
measures, and take out my bar checks for those measures?

In this particular case, the excerpt above is from the upper staff and I'm
actually trying to line the hairpin up with something on the lower staff.
I suppose I could put the hairpin on the lower staff, but then I'd get
the problem in the next measure, because the voice moves to the upper
staff there and the notes on the lower staff don't line up with where the
hairpin is supposed to end.


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


Re: LilyPond - dynamics and MIDI output

2007-08-25 Thread Philippe Raynaud
 I am not top posting

You have your problem (partly) resolved in the documentation
 D.2.4 Piano centered dynamics.
I am also interested in a good MIDI output.
At he beginning, I was hiding some dynamics, particularly
after a (de)crescendo, but now I prefer writing the dynamics
separately from the notes.
So I write tthe dynamics twice:
1. for the score, as they have to appear on it
2. for the Midi Output, so I can control their effect.
If your are particularly interested in a good Midi output,
I'll give you an example of the way I manage it (Voice +
piano staves).
Cheers. Philippe

Ed Ravin eravin at panix.com writes:

 
 In piano music, the dynamics written between the upper and lower
 staves seem to apply to both staves.  But in LilyPond's MIDI output,
 the dynamics are understandably only placed in the staff where they
 were entered.  When the MIDI plays, one staff gets louder and softer
 in the right places, while the other plays at the same volume throughout.
 
 I know that LilyPond's main purpose is music typesetting, with the MIDI
 output a secondary function, but is there any way to deal with this?
 Maybe write the dynamics in a second time on the lower staff and make
 them all invisible somehow?
 






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


Re: lilypond book error

2007-08-25 Thread Graham Percival
Please send a complete example, not just the lilypond portion.  The only 
other thing I can think of is to remove the fragment, and add {} around 
the notes.


HTH,
- Graham


mojocojo2000 wrote:

I am using lilypond version 2.10.29.  I'm trying to integrate music
into a paper I have for a class.  When I input the following into my 
tex file:


\begin[quote,fragment,staffsize=26]{lilypond}
c' d' e' f' g'2 g'2
\end{lilypond}

(I got this from the tutorial)

I invoke lilypond book with the following command and receive an error:

C:\Python25\python.exe 
C:\Program Files\Lilypond\usr\bin\lilypond-book.py

--pdf --output=C:\lilypondtest C:\test.tex


snippet-map.ly:3:1: error: GUILE signaled an error for the 
expression beginning

here
#
 (ly:add-file-name-alist '(
snippet-map.ly:4:30: illegal character in escape sequence: #\D
snippet-map.ly:3:4: error: syntax error, unexpected ':', expecting '='
#(ly
:add-file-name-alist '(
Processing `lily-a9db7ba2f3.ly'
Parsing...
lily-a9db7ba2f3.ly:97:5: error: unknown escaped string: `\notes'

 \notes \relative c' {
lily-a9db7ba2f3.ly:97:5: error: syntax error, unexpected STRING

 \notes \relative c' {
lily-a9db7ba2f3.ly:98:8: error: unknown escaped string: `\property'

\property Voice.autoBeaming = ##f
lily-a9db7ba2f3.ly:98:8: error: syntax error, unexpected STRING

\property Voice.autoBeaming = ##f
lily-a9db7ba2f3.ly:97:12: error: errors found, ignoring music 
expression

 \notes
\relative c' {
lily-a9db7ba2f3.ly:103:8: error: syntax error, unexpected '}'

}
error: failed files: lily-a9db7ba2f3 snippet-map.ly
command failed: lilypond -b eps -I  C:\\test 
--formats=eps  -deps-box-padding=3.0

0  -dread-file-list  snippet-names
Child returned 1

Thanks for your help.



___
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: \\ constructs and things that cross measures

2007-08-25 Thread Kieren MacMillan

Hi Ed:

   These voices are all separate from the voice that contains the  
notes just
   outside the  \\  construct. This should be noted when making  
changes at
   the voice level. This also means that slurs and ties cannot go  
into or out

   of a  \\  construct.


That's because of the \\ only -- that creates two new Voice contexts,  
each different from the main one that existed before the .


What you *can* do is

a b c\ d  { a b\! c d } \new Voice { g g g g } 

and things will behave as desired -- the first {} is a continuation  
of the main Voice context, and only the \new {} is different/new. See  
Instantiating new voices in the docs for more info.


Do I need to make the  {} \\ {}  sections wider to cover  
multiple

measures, and take out my bar checks for those measures?


That would also work, but you don't have to remove the bar checks.

Hope this helps!
Kieren.


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


Re: change Staff hara-kiri-ability on the fly?

2007-08-25 Thread Neil Puttock
Hi Kieren,

On 8/24/07, Kieren MacMillan [EMAIL PROTECTED] wrote:


 Just wondering if anyone has solved the problem of turning the hara-
 kiri-ability of a Staff on the fly?


I haven't had much success, unfortunately.

The closest I've got is in creating a new staff context with the properties
of \RemoveEmptyStaffContext, but it only allows you to choose whether a
particular stave can be hidden or not.

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


Re: change Staff hara-kiri-ability on the fly? SPONSORSHIP?

2007-08-25 Thread Kieren MacMillan

Hi Neil:

The closest I've got is in creating a new staff context with the  
properties of \RemoveEmptyStaffContext,
but it only allows you to choose whether a particular stave can be  
hidden or not.


If you read the Hara_kiri_engraver docs, it says
__

Like Axis_group_engraver, but make a hara-kiri spanner, and add  
interesting items (ie. note heads, lyric syllables and normal rests)


Properties (read)

keepAliveInterfaces (list)
A list of symbols, signifying grob interfaces that are worth  
keeping a staff with remove-empty set around for.

__

If that property were settable (on the fly), we could add  
MultiMeasureRest to (or remove it from) the keepAliveInterfaces as  
desired -- that would solve the problem!


Developers: any chance you can do this (or something similar, with an  
equivalent result)?

I've still got a few Euros burning a hole in my PayPal account...  =)

Thanks,
Kieren.


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


Re: change Staff hara-kiri-ability on the fly? SPONSORSHIP?

2007-08-25 Thread Kieren MacMillan

Hi Neil,

I've tried messing around with keepAliveInterfaces, and this is  
quite pleasing:


Nicely done -- I hereby retract my offer of sponsorship...  =)

Best regards,
Kieren.

p.s. This is *definitely* an LSR-worthy tip/trick!


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


Re: \rest in \drummode

2007-08-25 Thread pascal lawrynowicz

Hi,

Maybe this will help :
\once \override Rest #'extra-offset = #'( 0.0 . 5.0) r4

PL
www.percunivers.com

Message: 1
Date: Sat, 25 Aug 2007 03:39:18 +0200
From: Ole Schmidt [EMAIL PROTECTED]
Subject: \rest in \drummode?
To: lilypond-user@gnu.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

Dear all,

is there a way to place a rest (higher)  in \drummode? (like with  
\rest command in normal staffs)




\version 2.10.15
up = \drummode
{  s1 }

down = \drummode
{ sn4 sn2.\rest }

\new DrumStaff 
\new DrumVoice { \voiceOne \up }
\new DrumVoice { \voiceTwo \down }
 

\layout { ragged-right = ##t }



best

ole

  



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


Re: change Staff hara-kiri-ability on the fly? SPONSORSHIP?

2007-08-25 Thread Neil Puttock
Hi Kieren,

On 8/25/07, Kieren MacMillan [EMAIL PROTECTED] wrote:


 If you read the Hara_kiri_engraver docs, it says
 __

 Like Axis_group_engraver, but make a hara-kiri spanner, and add
 interesting items (ie. note heads, lyric syllables and normal rests)

 Properties (read)

  keepAliveInterfaces (list)
  A list of symbols, signifying grob interfaces that are worth
 keeping a staff with remove-empty set around for.
 __

 If that property were settable (on the fly), we could add
 MultiMeasureRest to (or remove it from) the keepAliveInterfaces as
 desired -- that would solve the problem!


I've tried messing around with keepAliveInterfaces, and this is quite
pleasing:

\version 2.11.30
show = { \set Staff.keepAliveInterfaces = #'(
rhythmic-grob-interface
multi-measure-rest-interface
lyric-interface
stanza-number-interface
percent-repeat-interface)
}
hide = \unset Staff.keepAliveInterfaces
one = { \repeat unfold 4 { a1 b c' d' \break }
R1 \show R1 R1 \hide R1 \break
R1*4
}
two = { \override MultiMeasureRest #'color = #red
R1*4
R1 \show R1 R1 \hide R1
R1*4
R
R1 \show R1 R1 R1
R1*4
}
three = { \override MultiMeasureRest #'color = #blue
R1*4
R
R1 \show R1 R1 \hide R1
R1*4
R1 \show R1 R1 \hide R1
R1*4
}
\score {
\new StaffGroup 
\context Staff = one \one
\context Staff = two \two
\context Staff = three \three

\layout {
\context { \RemoveEmptyStaffContext }
}
}

The positioning of the overrides is critical (inside each system), otherwise
they tend to interfere with the other staves.

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


Re: \\ constructs and things that cross measures

2007-08-25 Thread Kieren MacMillan

Hi Trevor (et al.):


Yup, this is indeed very useful. Here's me discovering this construct
just a couple of days ago for double-voiced noteheads and stems that
cross over in piano music:


The other really helpful (at least for me) situation this handles is  
lyrics: the lyrics automatically follow the principal Voice if you  
don't use \\.


If you use the \\ construct, you then need to explicitly name the  
context to maintain the Lyric attachment:

 \context Voice = mainVoice { a b c d } \\  { f f f g } 

Cheers,
Kieren.


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


Request for comments: LilyPond 2.12

2007-08-25 Thread Han-Wen Nienhuys


Hello everyone,

Since most of the horizontal and vertical spacing hacks of Joe have
stabilized, I think it is time now to start considering a new stable
release.  With the current release process, it should be possible to
build a new stable release in a matter of days, so the real question, 
are we in a state for release 2.12?

Historically, the criterion for a new stable release is

1. No regressions

Currently, the bug tracker does not show any regressions.

2. Significant features.  We have plenty:

  - Completely rewritten page breaking/vertical spacing combo, with
skylining spacing and better vertical collision detection

  - Table of contents, multi paragraph text, page references

  - Generic microtone support

  - Doc updates (graham?)

  - Manual translations: french, spanish, german

  - More flexible line spanners.

  - Several performance and resource speedups.

3. no glaring bugs in the new features.

I seem to recall that we have a nasty bug in reverting nested
properties, but except for that I can't recall anything notable.


Comments, ideas?



-- 

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



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


Re: How to deal with Time Signatures horizontal alignment?

2007-08-25 Thread Han-Wen Nienhuys
Joe Neeman escreveu:
 On Tuesday 21 August 2007 20:34, Valentin Villenave wrote:
 That being said, do you think it would be a good idea to make
 TimeSignature accept the break-alignable-interface?
 
 No, because TimeSignature already accepts an interface 
 (break-aligned-interface) that determines its horizontal position; it 
 wouldn't make sense for it to accept another one. The cleanest way of getting 
 this functionality into the lilypond core, in my opinion, would be to create 
 a whole new grob class.

I think you are all thinking in too complicated directions.

layout{
  \context { 
\type Engraver_group
\consists Time_signature_engraver
\consists Axis_group_engraver
\name TimeSig
\override TimeSignature #'font-size = #3
\override TimeSignature #'break-align-symbol = ##f
\override TimeSignature #'X-offset
= #ly:self-alignment-interface::x-aligned-on-self
\override TimeSignature #'self-alignment-X = #0
  }
  \context {
\Score \accepts TimeSig
  }

  \context {
\Staff
\remove Time_signature_engraver
  }
}

timeSignatures = { \time 2/4 s2 \time 3/4 s2. \time 4/4 s1 }
\score {

  \new TimeSig \timeSignatures
\new Staff \relative { c'2  c2.  c1 }
\new Staff { a2 a2. a1}
 
}

-- 

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



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


Re: \rest in \drummode?

2007-08-25 Thread Han-Wen Nienhuys
Ole Schmidt escreveu:
 Dear all,
 
 is there a way to place a rest (higher)  in \drummode? (like with \rest
 command in normal staffs)

\override the staff-position of the Rest, or perhaps using tweak. 
Untested code follows:


\tweak #'staff-position #5 r 

-- 

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



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


Re: \rest in \drummode

2007-08-25 Thread Ole Schmidt

does not work with dotted rests...

ole


Am 25.08.2007 um 21:40 schrieb pascal lawrynowicz:


Hi,

Maybe this will help :
\once \override Rest #'extra-offset = #'( 0.0 . 5.0) r4

PL
www.percunivers.com

Message: 1
Date: Sat, 25 Aug 2007 03:39:18 +0200
From: Ole Schmidt [EMAIL PROTECTED]
Subject: \rest in \drummode?
To: lilypond-user@gnu.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

Dear all,

is there a way to place a rest (higher)  in \drummode? (like with   
\rest command in normal staffs)




\version 2.10.15
up = \drummode
{  s1 }

down = \drummode
{ sn4 sn2.\rest }

\new DrumStaff 
\new DrumVoice { \voiceOne \up }
\new DrumVoice { \voiceTwo \down }
 

\layout { ragged-right = ##t }



best

ole





___
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