Re: tie and slur problem

2014-10-30 Thread Rutger Hofman 

On 10/28/2014 09:42 AM, Dr. Bernhard Kleine wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

There should be a tie between the two c and a slur from e to f.  and a slur
from g  over b(bes) to a in the right hand. The upper g and b and a are in a 
separate voice and no problem.
But how to code the tie and the slur in voiceTwo? Between  to < c f>

Schnipsel from Missa in C from Anton Bruckner

Bernhard


The following code works for me. It depends on two voices having the 
same predicate \voiceTwo. Note that you will probably want to tune the 
shape of the voiceTwo slur, it is wider than in your original.


\new Score {
\new Staff <<
\new Voice \relative c' {
\voiceOne
g'2.( bes4 |
a4)
}
\new Voice \relative c' {
\voiceTwo
c1~ |
c4
}
\new Voice \relative c' {
\voiceTwo
e1( |
f4)
}
>>
}




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

Re: thanks again for the editionEngraver

2014-10-30 Thread Urs Liska 


Am 30. Oktober 2014 02:51:16 MEZ, schrieb Paul Morris :
>I was thinking the edition engraver would be a good way to handle Urs'
>"original breaks" functionality.  
>
>Instead of entering the original breaks (tagged or with a special break
>command) in the score in the middle of the music, mixing content and
>presentation...  I can imagine a way to simply enter a list of measure
>numbers where the original breaks should be placed, as part of the
>"editing
>edition" of the score.  
>
>Then it would be easy to turn this "editing edition" on or off (from
>the
>command line or however).
>
>Just thinking out loud,

That sounds reasonable.
However, original breaks *are* part of the content so that's not a mixture.

Urs

>-Paul
>
>
>
>--
>View this message in context:
>http://lilypond.1069038.n5.nabble.com/thanks-again-for-the-editionEngraver-tp164625p168103.html
>Sent from the User mailing list archive at Nabble.com.
>
>___
>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

Re: Clef change at the beginning of a staff

2014-10-30 Thread Joram 
Hi Abraham,

thanks for looking at it.

> I get a bar-check warning before the c1 using 2.18.2. You not seeing that?

I did not calculate the numbers well (1/128+1/4*31/32 = 1/4).
This works without warning:

\relative c' {
  %%  Start with a bass clef
  \clef bass
  %%  Use a skip (has the least effect on Score timing)
  s128
  %%  Put in the tenor clef and continue...
  \clef treble c4*31/32
  c4 c c | c1
}

Cheers,
Joram

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

Re: midi2ly

2014-10-30 Thread Hans Aberg 

> On 30 Oct 2014, at 01:07, ole  wrote:
> 
> Am 29.10.2014 um 23:10 schrieb Hans Aberg :
> 
>> On 29 Oct 2014, at 21:53, ole  wrote:

>>> Sorry for the noise! 
>>> Just discovered that a .ly file has been made despite of the error warning..
>> 
>> Strictly speaking, it is a warning as it passes the compile, not an error 
>> which would abort. So it is a relevant issue, though it seems to work.
>> 
> So- as I understand it right- I can install python 2.4 into /opt/local/bin 
> via macports
> 
> and then change the line to
> 
> exec /usr/bin/arch -i386 /opt/local/bin/python2.4 
> /Applications/LilyPond.app/Contents/Resources/bin/midi2ly "$@"
> 
> Would that work?

If you don’t like that pesky warning, you can always try. But the MIDI file I 
used it on seemed to work with Python 2.7.



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

Re: Clef change at the beginning of a staff

2014-10-30 Thread Pierre Perol-Schneider 
Hi Joram, Hi Abraham,

2014-10-30 10:11 GMT+01:00 Joram :


> I did not calculate the numbers well (1/128+1/4*31/32 = 1/4).
> This works without warning:
>
> \relative c' {
>   %%  Start with a bass clef
>   \clef bass
>   %%  Use a skip (has the least effect on Score timing)
>   s128
>   %%  Put in the tenor clef and continue...
>   \clef treble c4*31/32
>   c4 c c | c1
> }
>
>
How about :

\version "2.18.2"

\relative c' {
  %%  Start with a bass clef :
  \clef bass
  %%  Use a hidden grace note (avoid any wrong calculation):
  \once\hideNotes\grace c64
  %%  Adjust the clef spacing:
  \once\override Staff.Clef.X-extent = #'(1 . 2)
  %%  Put in the treble clef:
  \clef treble
  c4 c c c | c1
}

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