Re: For a Weird Key Signature (Retry)

2011-05-02 Thread Trevor Daniels 


"PMA" 


Again, the question is, How can I apply horizontal shift to one
element of a key *signature*?


Not sure if this is helpful, but one (only?) property which
affects the placement of elements of a key signature is
'padding.  It affects all elements except the first.

Try playing with 


 \override Staff.KeySignature #'padding =#-1

BTW, more people might respond if you post a small example
which is immediately compilable.

Trevor



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

Non-standard tuning in 2 or more voices

2011-05-02 Thread Richard Sabey 

How come LilyPond can't output the correct MIDI for 2 or more simultaneous 
notes in a non-standard tuning? After all, it does output the correct MIDI for 
individual notes in a non-standard tuning.

Investigating LilyPond's limits in this area, I find that LilyPond outputs the 
correct MIDI for simultaneous notes in a non-standard tuning, /provided that/ 
they are in separate MIDI channels to which are assigned /different/ MIDI 
instruments (e.g. violin notes at the same time as piano notes). However, it 
outputs incorrect pitches for simultaneous notes to be played by identical MIDI 
instruments (e.g. all notes to be played by violin), even if I get LilyPond to 
get MIDI to assign these notes to separate channels. How come?

Is LilyPond actually assigning the notes to the same channel despite my efforts 
to get it to get MIDI to assign these notes to separate channels? If so, how do 
I get these notes assigned to separate channels, and would that produce the 
correct pitches anyway?

In the example below, the upper and lower voices should hold constant pitches 
but in the MIDI they don't.

%%%
\version "2.13.55"

% For syntax, see \usr\share\lilypond\current\ly\makam.ly
% The unit here is the tone.

xixPitchNames = #`(
(c . ,(ly:make-pitch -1 0 0/38))
(cs . ,(ly:make-pitch -1 0 12/38))
(df . ,(ly:make-pitch -1 1 -14/38))
(d . ,(ly:make-pitch -1 1 -2/38))
(ds . ,(ly:make-pitch -1 1 10/38))
(ef . ,(ly:make-pitch -1 2 -16/38))
(e . ,(ly:make-pitch -1 2 -4/38))
(es . ,(ly:make-pitch -1 2 8/38))
(ff . ,(ly:make-pitch -1 3 -11/38))
(f . ,(ly:make-pitch -1 3 1/38))
(fs . ,(ly:make-pitch -1 3 13/38))
(gf . ,(ly:make-pitch -1 4 -13/38))
(g . ,(ly:make-pitch -1 4 -1/38))
(gs . ,(ly:make-pitch -1 4 11/38))
(af . ,(ly:make-pitch -1 5 -15/38))
(a . ,(ly:make-pitch -1 5 -3/38))
(as . ,(ly:make-pitch -1 5 9/38))
(bf . ,(ly:make-pitch -1 6 -17/38))
(b . ,(ly:make-pitch -1 6 -5/38))
(bs . ,(ly:make-pitch -1 6 7/38))
)
pitchnames = \xixPitchNames
#(ly:parser-set-note-names parser xixPitchNames)

xixGlyphs = #`(
(0/38 . "accidentals.natural")
(12/38 . "accidentals.sharp")
(-14/38 . "accidentals.flat")
(-2/38 . "accidentals.natural")
(10/38 . "accidentals.sharp")
(-16/38 . "accidentals.flat")
(-4/38 . "accidentals.natural")
(8/38 . "accidentals.sharp")
(-11/38 . "accidentals.flat")
(1/38 . "accidentals.natural")
(13/38 . "accidentals.sharp")
(-13/38 . "accidentals.flat")
(-1/38 . "accidentals.natural")
(11/38 . "accidentals.sharp")
(-15/38 . "accidentals.flat")
(-3/38 . "accidentals.natural")
(9/38 . "accidentals.sharp")
(-17/38 . "accidentals.flat")
(-5/38 . "accidentals.natural")
(7/38 . "accidentals.sharp")
)
\layout
{
\context
{
\Score
\override KeySignature #'glyph-name-alist = \xixGlyphs
\override Accidental #'glyph-name-alist = \xixGlyphs
\override AccidentalCautionary #'glyph-name-alist = \xixGlyphs
\override TrillPitchAccidental #'glyph-name-alist = \xixGlyphs
\override AmbitusAccidental #'glyph-name-alist = \xixGlyphs
}
}

xixNullKeySig = #`(
(1 . -2/38); d
(2 . -4/38); e
(3 .  1/38); f
(4 . -1/38); g
(5 . -3/38); a
(6 . -5/38); b
)

xixSetNullKeySig =
{
\override Staff.KeySignature #'stencil = ##f
\set Staff.keySignature = \xixNullKeySig
}

xixHacks =
{
\set Staff.extraNatural = ##f
\xixSetNullKeySig
}

global =
{
\xixHacks
}

vna =
{
g'1
}

vnb =
{
ff'4 e' ef'4 ds'
}

vnc =
{
c'1
}

\score
{
<<
\new Staff \with { midiInstrument = #"violin"} { << \global \vna >> }
\new Staff \with { midiInstrument = #"violin"} { << \global \vnb >> }
\new Staff \with { midiInstrument = #"violin"} { << \global \vnc >> }
>>

\layout { }
\midi
{
\context
{\Staff
\remove "Staff_performer"
}
\context
{\Voice
\consists "Staff_performer"
}
}
} % score
%%%

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

RE: Compound time signature

2011-05-02 Thread James Lowe 
Paul,

)-Original Message-
)From: lilypond-user-bounces+james.lowe=datacore@gnu.org
)[mailto:lilypond-user-bounces+james.lowe=datacore@gnu.org] On
)Behalf Of Paul Scott
)Sent: 01 May 2011 20:15
)To: lilypond-user@gnu.org
)Subject: Re: Compound time signature
)
)On 04/30/2011 10:24 AM, Thomas Scharkowski wrote:
)> Hi,
)>
)>   I try to print a compound time signature using this construction:
)
)Is there a way to generate a (complex?) time signature that indicates bars
)alternating between two different time signatures?  I have seen this in
)several band pieces as well as the score for "Man of La Mancha."  A
)common one is 3/4 6/8 but I an example of 3/4 4/4.
)


http://lsr.dsi.unimi.it/LSR/Item?id=261

Does that do what you want?

or

http://lsr.dsi.unimi.it/LSR/Item?id=743

for another option.

also this

http://lsr.dsi.unimi.it/LSR/Item?id=395


James

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

define line break

2011-05-02 Thread MING TSANG 
According to lilypond usage 5.2

* Define mBreak = { \break } and insert \mBreak in the input file 
whenever the 
manuscript has a line break.  This makes it much easier to compare the LilyPond 
music to the original music.  When you are finished proofreading your score, 
you 
may define mBreak = { } to remove all those line breaks.  This will allow 
LilyPond to place line breaks wherever it feels are best. I coded:
\version 2.13.61
define mBreak = {\break}   
\relative c, { c d e f g a b \mBreak b b a a }

I got the following error:
C:/Documents and Settings/Administrator/Desktop/LILY_POND/little-dream.ly:16:7: 
error: syntax error, unexpected STRING, expecting SCM_IDENTIFIER or SCM_TOKEN 
or 
'='
define 
   mBreak = {\break} 


Question:  what is the correct syntax?  
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: define line break

2011-05-02 Thread Phil Holmes 
You don't need the word "define".  It's just an instruction in the manual.  
Just use

mBreak = { \break }

--
Phil Holmes


  - Original Message - 
  From: MING TSANG 
  To: lilypond-user@gnu.org ; lilypond-user-requ...@gnu.org 
  Sent: Monday, May 02, 2011 2:41 PM
  Subject: define line break


  According to lilypond usage 5.2

a.. Define mBreak = { \break } and insert \mBreak in the input file 
whenever the manuscript has a line break. This makes it much easier to compare 
the LilyPond music to the original music. When you are finished proofreading 
your score, you may define mBreak = { } to remove all those line breaks. This 
will allow LilyPond to place line breaks wherever it feels are best. 
  I coded:
  \version 2.13.61
  define mBreak = {\break}   
  \relative c, { c d e f g a b \mBreak b b a a }

  I got the following error:
  C:/Documents and 
Settings/Administrator/Desktop/LILY_POND/little-dream.ly:16:7: error: syntax 
error, unexpected STRING, expecting SCM_IDENTIFIER or SCM_TOKEN or '='
  define 
 mBreak = {\break} 


  Question:  what is the correct syntax?  



--


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

Fw: midi arpeggio

2011-05-02 Thread MING TSANG 
Re posting the following. Need help!



- Forwarded Message 
From: MING TSANG 
To: lilypond-user@gnu.org
Sent: Mon, April 11, 2011 5:31:39 PM
Subject: midi arpeggio


The midi output does not produce arpeggio midi sound.  

<><><>
snippet

\version "2.13.59"
\include "english.ly"
TimeKey = { \time 4/4  \key ef  \major  } 
PianoRHand = \relative c' {
8 ef4 8 8 ef'4 8 |%bar 01
8 ef4 8 8 4 8 |%bar 02
8 g4 8 4 8 8~ \break%bar 03
2 2\arpeggio |%bar 04
8 ef4 8 8 ef'4 8 |%bar 05
8 ef4 8 8 4 8 |%bar 06
8 4 8 4 8 8~ \break%bar 07
2 2\arpeggio |%bar 08
  }
PianoLHand = \relative c {
<< {bf2 c2} \\ {ef,1} >> |%bar 01
<< {df'2 cf2} \\ {ef,1} >> |%bar 02
2 4. 8~ \break %bar 03
1 | %bar 04
<< {bf'2 c2} \\ {ef,1} >> |%bar  05
<< {df'2 c2} \\ {ef,1} >> |%bar 06
2 4. 8~ \break %bar 07
1 |%bar 08
 }
 

  
  
\score {
  \new GrandStaff = "GrandStaff_score"  <<
\new ChoirStaff <<
>>
\new PianoStaff <<
  \new Staff = "RH" { \TimeKey  \PianoRHand  }
  \new Staff = "LH" { \TimeKey \clef bass \PianoLHand }
>>
  >>
   \layout {   }
  \midi {}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: mup2ly.py

2011-05-02 Thread MING TSANG 
I am re-posting the following email.  I have not received any reply yet.





From: MING TSANG 
To: lilypond-user@gnu.org
Sent: Mon, April 11, 2011 10:40:17 PM
Subject: mup2ly.py


I download lilypond v2.6.5 and try to use mup2ly.py to convert a .mup file to 
.ly

questions:
1.  mup2ly.py sample2.mup did not produce a .ly file.
2.  is any one know how this mup2ly works?
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: define line break

2011-05-02 Thread MING TSANG 
It works now. Thanks.






From: Phil Holmes 
To: MING TSANG ; lilypond-user@gnu.org; 
lilypond-user-requ...@gnu.org
Sent: Mon, May 2, 2011 9:47:49 AM
Subject: Re: define line break

  
You don't need the word "define".  It's just  an instruction in the manual.  
Just use
 
mBreak = { \break }

--
Phil Holmes
 
 
- Original Message - 
>From: MING TSANG 
>To: lilypond-user@gnu.org ; lilypond-user-requ...@gnu.org 
>Sent: Monday, May 02, 2011 2:41 PM
>Subject: define line break
>
>
>Accordingto lilypond usage 5.2
>
>   * Define mBreak = { \break } and insert \mBreak in the input file 
> whenever the 
>manuscript has a line break. This makes it  much easier to compare the 
>LilyPond music to the original music. When you  are finished proofreading 
>your score, you may define mBreak = {  } to remove all those line breaks. 
>This will allow LilyPond to place  line breaks wherever it feels are best. 
>I 
>coded:
>\version2.13.61
>define mBreak = {\break}   
>\relative c, { c d e f g ab \mBreak b b a a }
>
>I got the following error:
>C:/Documents and
>Settings/Administrator/Desktop/LILY_POND/little-dream.ly:16:7: error: syntax   
> 
>error, unexpected STRING, expecting SCM_IDENTIFIER or SCM_TOKEN or'='
>define 
>   mBreak = {\break} 
>
>
>Question:  what is thecorrect syntax?  
>

 ___
>lilypond-usermailinglist
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user
>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: define line break

2011-05-02 Thread Éditions IN NOMINE 
This is alkso VERY usefull to compile seperate scores without messing up 
the main orchestral score.


Great idea !

JMarc

MING TSANG a écrit :

It works now. Thanks.



*From:* Phil Holmes 
*To:* MING TSANG ; lilypond-user@gnu.org; 
lilypond-user-requ...@gnu.org

*Sent:* Mon, May 2, 2011 9:47:49 AM
*Subject:* Re: define line break

You don't need the word "define".  It's just an instruction in the 
manual.  Just use
 
mBreak = { \break }


--
Phil Holmes
 
 


- Original Message -
*From:* MING TSANG 
*To:* lilypond-user@gnu.org  ;
lilypond-user-requ...@gnu.org 
*Sent:* Monday, May 02, 2011 2:41 PM
*Subject:* define line break

According to lilypond usage 5.2

* Define |mBreak = { \break }| and insert |\mBreak| in the
  input file whenever the manuscript has a line break. This
  makes it much easier to compare the LilyPond music to the
  original music. When you are finished proofreading your
  score, you may define |mBreak = { }| to remove all those
  line breaks. This will allow LilyPond to place line breaks
  wherever it feels are best.

I coded:
\version 2.13.61
define mBreak = {\break}  
\relative c, { c d e f g a b \mBreak b b a a }


I got the following error:
C:/Documents and
Settings/Administrator/Desktop/LILY_POND/little-dream.ly:16:7:
error: syntax error, unexpected STRING, expecting SCM_IDENTIFIER
or SCM_TOKEN or '='
define
   mBreak = {\break}


Question:  what is the correct syntax? 



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



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


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

tuplet brackets force print

2011-05-02 Thread Peter O'Doherty 
re. my previous post concerning tuplet brackets not bing printed. 
Apparently this is a known bug for which a patch has been made.


http://code.google.com/p/lilypond/issues/detail?id=405

Can anyone advise how I can implement this patch?

Thanks,
Peter

--
//=
->  Peter O'Doherty
->  http://www.peterodoherty.net
->  m...@peterodoherty.net
//=


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

Re: tuplet brackets force print

2011-05-02 Thread Nick Payne 

On 03/05/11 15:13, Peter O'Doherty wrote:
re. my previous post concerning tuplet brackets not bing printed. 
Apparently this is a known bug for which a patch has been made.


http://code.google.com/p/lilypond/issues/detail?id=405

Can anyone advise how I can implement this patch?


According to the link above, the fix was implemented in 2.13.14, so run 
the current development version to get it.


Nick

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

Re: tuplet brackets force print

2011-05-02 Thread Peter O'Doherty 

On 05/03/2011 07:46 AM, Nick Payne wrote:

On 03/05/11 15:13, Peter O'Doherty wrote:
re. my previous post concerning tuplet brackets not bing printed. 
Apparently this is a known bug for which a patch has been made.


http://code.google.com/p/lilypond/issues/detail?id=405

Can anyone advise how I can implement this patch?


According to the link above, the fix was implemented in 2.13.14, so 
run the current development version to get it.


Nick


Thanks. Is it possible to have two versions alongside each other?


--
//=
->  Peter O'Doherty
->  http://www.peterodoherty.net
->  m...@peterodoherty.net
//=


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