Re: "bitonal" key signatures

[Pierre Perol-Schneider]

I just tried it.
Strangely, you still have to slightly extra-offset the LH key to get a
proper alignment.
~Pierre

2016-02-10 14:42 GMT+01:00 Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:

> Yep, much smarter Phil.
>
> 2016-02-10 14:40 GMT+01:00 Phil Holmes :
>
>> Better would be to add \tweak X-extent #'(0 . 0) just before the C major
>> key sig in the right hand?
>>
>>
>> --
>> Phil Holmes
>>
>>
>> - Original Message - From: Pierre Perol-Schneider
>> To: N. Andrew Walsh
>> Cc: lilypond-user
>> Sent: Wednesday, February 10, 2016 1:19 PM
>> Subject: Re: "bitonal" key signatures
>>
>>
>>
>> ... but is probably not the "better" way!
>>
>>
>>
>> 2016-02-10 14:18 GMT+01:00 Pierre Perol-Schneider <
>> pierre.schneider.pa...@gmail.com>:
>>
>> Hi Andrew,
>>
>>
>> In lhMusic mes.2 try :
>> ...
>> \tweak X-extent #'(0 . 0)
>> \tweak extra-offset #'(-3 . 0)
>> \key es \major
>> 
>>
>>
>> Cheers,
>>
>> Pierre
>>
>>
>>
>>
>> 2016-02-10 13:36 GMT+01:00 N. Andrew Walsh :
>>
>> Hi List (again),
>>
>> here's another question, more general: I have a piano part in which the
>> upper voice is to have one key signature, the lower to retain another one
>> (namely, the right hand has \key c \major, while the left hand has \key es
>> \major, which was also declared at the start of the piece). Something like
>> this:
>>
>>
>> \version "2.19.36"
>>
>>
>>
>>
>> beambreakOn = {
>>  \set subdivideBeams = ##t
>>  \set baseMoment = #(ly:make-moment 1/8)
>>  \set beatStructure = #'(2 2 2 2)
>> }
>>
>>
>> beambreakOff = {
>>  \set subdivideBeams = ##f
>>  \set baseMoment = #(ly:make-moment 1/8)
>>  \set beatStructure = #'(2 2 2 2)
>> }
>>
>>
>> rhMusic = \relative c'' {
>>\key es \major
>>  \time 4/8
>>  r16 bes d bes d bes d bes |
>>  \key c \major
>>  \beambreakOn \tuplet 3/2 { es,\( f g } \tuplet 3/2 { a b cis } dis4\) |
>> }
>>
>>
>> lhMusic = \relative c {
>>  \clef bass
>>  \key es \major
>>  \time 4/8
>>  <<
>>  { r16 d f d f d f d | }
>>  \\
>>  { bes2 | }
>>>>
>>  \key es \major
>>  <<
>>{ es,16 bes' es bes g' d g d | }
>>\\
>>{ es,2 | }
>>  >>
>> }
>>
>>
>> \score {
>>
>>
>>  \new PianoStaff <<
>>\new Staff = "RH"  <<
>>  \rhMusic
>>>>
>>\new Staff = "LH" <<
>> \lhMusic
>>>>
>>  >>
>> }
>> 
>>
>> My issue is as follows: the engraver in charge of key signatures is
>> displacing that second "\key es \major" expression in the left hand,
>> presumably because there was already one in place from the beginning (or
>> perhaps because it's assuming a possible collision with the "\key c \major"
>> expression in the right hand). In either case, what I would prefer is that
>> both new key signatures are not displaced horizontally, so that the second
>> "\key es \major" is, in effect, merely a cautionary repetition of the one
>> from the start and aligned underneath the naturals of the "\key c \major"
>> expression in the right hand.
>>
>>
>>
>> Is there a better way to do this?
>>
>>
>> Cheers,
>>
>>
>> A
>>
>>
>> ___
>> 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

Re: "bitonal" key signatures

[N. Andrew Walsh]

Also, another matter that's somewhat related: the key change in the right
hand goes back to "\key es \major" at the end of a system, right before
which is a note with a phrasing slur extending into the next system.
Something like this:

\version "2.19.36"

rhMusic = \relative c'' {
\key c \major
\time 4/8
\phrasingSlurUp
r8 r r g\( | \bar "||"\break
\key es \major
\mark \default g8. f16 es8 g | as4 es8 as | g4 es8 es | f2\)
}

\score {
\rhMusic
}

NB: "\phrasingSlurUp" is there because this is a voice part and I didn't
want to crowd the lyrics.

I also see a bunch of the message:
programming error: no solution found for Bezier intersection
continuing, cross fingers

in the log when this is in a larger piece, but not in this MWE. Regardless:
is there a way to change the placement of that curve? It seems the ideal
solution would be either 1) keep the slope and raise it vertically, or 2)
change the slope (likely to something pretty steep) to avoid the collision.
However, this is also a grob that's connected to the phrasing slur on the
next line, and I don't want to affect that placement (it looks fine to
me?).

What's the best way to go about this?

Cheers,

A

On Wed, Feb 10, 2016 at 3:51 PM, N. Andrew Walsh 
wrote:

> Thanks for the tips. Another question: how can I force a display of the
> "natural" time signature, so that it's clear the right hand is in a
> different tonality than the left? Right now there's just blank space.
>
> Cheers,
>
> A
>
> On Wed, Feb 10, 2016 at 2:54 PM, Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com> wrote:
>
>> I just tried it.
>> Strangely, you still have to slightly extra-offset the LH key to get a
>> proper alignment.
>> ~Pierre
>>
>> 2016-02-10 14:42 GMT+01:00 Pierre Perol-Schneider <
>> pierre.schneider.pa...@gmail.com>:
>>
>>> Yep, much smarter Phil.
>>>
>>> 2016-02-10 14:40 GMT+01:00 Phil Holmes :
>>>
 Better would be to add \tweak X-extent #'(0 . 0) just before the C
 major key sig in the right hand?


 --
 Phil Holmes


 - Original Message - From: Pierre Perol-Schneider
 To: N. Andrew Walsh
 Cc: lilypond-user
 Sent: Wednesday, February 10, 2016 1:19 PM
 Subject: Re: "bitonal" key signatures



 ... but is probably not the "better" way!



 2016-02-10 14:18 GMT+01:00 Pierre Perol-Schneider <
 pierre.schneider.pa...@gmail.com>:

 Hi Andrew,


 In lhMusic mes.2 try :
 ...
 \tweak X-extent #'(0 . 0)
 \tweak extra-offset #'(-3 . 0)
 \key es \major
 


 Cheers,

 Pierre




 2016-02-10 13:36 GMT+01:00 N. Andrew Walsh :

 Hi List (again),

 here's another question, more general: I have a piano part in which the
 upper voice is to have one key signature, the lower to retain another one
 (namely, the right hand has \key c \major, while the left hand has \key es
 \major, which was also declared at the start of the piece). Something like
 this:


 \version "2.19.36"




 beambreakOn = {
  \set subdivideBeams = ##t
  \set baseMoment = #(ly:make-moment 1/8)
  \set beatStructure = #'(2 2 2 2)
 }


 beambreakOff = {
  \set subdivideBeams = ##f
  \set baseMoment = #(ly:make-moment 1/8)
  \set beatStructure = #'(2 2 2 2)
 }


 rhMusic = \relative c'' {
\key es \major
  \time 4/8
  r16 bes d bes d bes d bes |
  \key c \major
  \beambreakOn \tuplet 3/2 { es,\( f g } \tuplet 3/2 { a b cis } dis4\) |
 }


 lhMusic = \relative c {
  \clef bass
  \key es \major
  \time 4/8
  <<
  { r16 d f d f d f d | }
  \\
  { bes2 | }
>>
  \key es \major
  <<
{ es,16 bes' es bes g' d g d | }
\\
{ es,2 | }
  >>
 }


 \score {


  \new PianoStaff <<
\new Staff = "RH"  <<
  \rhMusic
>>
\new Staff = "LH" <<
 \lhMusic
>>
  >>
 }
 

 My issue is as follows: the engraver in charge of key signatures is
 displacing that second "\key es \major" expression in the left hand,
 presumably because there was already one in place from the beginning (or
 perhaps because it's assuming a possible collision with the "\key c \major"
 expression in the right hand). In either case, what I would prefer is that
 both new key signatures are not displaced horizontally, so that the second
 "\key es \major" is, in effect, merely a cautionary repetition of the one
 from the start and aligned underneath the naturals of the "\key c \major"
 expression in the right hand.



 Is there a better way to do this?


 Cheers,


 A

Re: "bitonal" key signatures

[N. Andrew Walsh]

Thanks for the tips. Another question: how can I force a display of the
"natural" time signature, so that it's clear the right hand is in a
different tonality than the left? Right now there's just blank space.

Cheers,

A

On Wed, Feb 10, 2016 at 2:54 PM, Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com> wrote:

> I just tried it.
> Strangely, you still have to slightly extra-offset the LH key to get a
> proper alignment.
> ~Pierre
>
> 2016-02-10 14:42 GMT+01:00 Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com>:
>
>> Yep, much smarter Phil.
>>
>> 2016-02-10 14:40 GMT+01:00 Phil Holmes :
>>
>>> Better would be to add \tweak X-extent #'(0 . 0) just before the C major
>>> key sig in the right hand?
>>>
>>>
>>> --
>>> Phil Holmes
>>>
>>>
>>> - Original Message - From: Pierre Perol-Schneider
>>> To: N. Andrew Walsh
>>> Cc: lilypond-user
>>> Sent: Wednesday, February 10, 2016 1:19 PM
>>> Subject: Re: "bitonal" key signatures
>>>
>>>
>>>
>>> ... but is probably not the "better" way!
>>>
>>>
>>>
>>> 2016-02-10 14:18 GMT+01:00 Pierre Perol-Schneider <
>>> pierre.schneider.pa...@gmail.com>:
>>>
>>> Hi Andrew,
>>>
>>>
>>> In lhMusic mes.2 try :
>>> ...
>>> \tweak X-extent #'(0 . 0)
>>> \tweak extra-offset #'(-3 . 0)
>>> \key es \major
>>> 
>>>
>>>
>>> Cheers,
>>>
>>> Pierre
>>>
>>>
>>>
>>>
>>> 2016-02-10 13:36 GMT+01:00 N. Andrew Walsh :
>>>
>>> Hi List (again),
>>>
>>> here's another question, more general: I have a piano part in which the
>>> upper voice is to have one key signature, the lower to retain another one
>>> (namely, the right hand has \key c \major, while the left hand has \key es
>>> \major, which was also declared at the start of the piece). Something like
>>> this:
>>>
>>>
>>> \version "2.19.36"
>>>
>>>
>>>
>>>
>>> beambreakOn = {
>>>  \set subdivideBeams = ##t
>>>  \set baseMoment = #(ly:make-moment 1/8)
>>>  \set beatStructure = #'(2 2 2 2)
>>> }
>>>
>>>
>>> beambreakOff = {
>>>  \set subdivideBeams = ##f
>>>  \set baseMoment = #(ly:make-moment 1/8)
>>>  \set beatStructure = #'(2 2 2 2)
>>> }
>>>
>>>
>>> rhMusic = \relative c'' {
>>>\key es \major
>>>  \time 4/8
>>>  r16 bes d bes d bes d bes |
>>>  \key c \major
>>>  \beambreakOn \tuplet 3/2 { es,\( f g } \tuplet 3/2 { a b cis } dis4\) |
>>> }
>>>
>>>
>>> lhMusic = \relative c {
>>>  \clef bass
>>>  \key es \major
>>>  \time 4/8
>>>  <<
>>>  { r16 d f d f d f d | }
>>>  \\
>>>  { bes2 | }
>>>>>
>>>  \key es \major
>>>  <<
>>>{ es,16 bes' es bes g' d g d | }
>>>\\
>>>{ es,2 | }
>>>  >>
>>> }
>>>
>>>
>>> \score {
>>>
>>>
>>>  \new PianoStaff <<
>>>\new Staff = "RH"  <<
>>>  \rhMusic
>>>>>
>>>\new Staff = "LH" <<
>>> \lhMusic
>>>>>
>>>  >>
>>> }
>>> 
>>>
>>> My issue is as follows: the engraver in charge of key signatures is
>>> displacing that second "\key es \major" expression in the left hand,
>>> presumably because there was already one in place from the beginning (or
>>> perhaps because it's assuming a possible collision with the "\key c \major"
>>> expression in the right hand). In either case, what I would prefer is that
>>> both new key signatures are not displaced horizontally, so that the second
>>> "\key es \major" is, in effect, merely a cautionary repetition of the one
>>> from the start and aligned underneath the naturals of the "\key c \major"
>>> expression in the right hand.
>>>
>>>
>>>
>>> Is there a better way to do this?
>>>
>>>
>>> Cheers,
>>>
>>>
>>> A
>>>
>>>
>>> ___
>>> 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

Re: "bitonal" key signatures

[Phil Holmes]

Better would be to add \tweak X-extent #'(0 . 0) just before the C major key 
sig in the right hand?



--
Phil Holmes


- Original Message - 
From: Pierre Perol-Schneider

To: N. Andrew Walsh
Cc: lilypond-user
Sent: Wednesday, February 10, 2016 1:19 PM
Subject: Re: "bitonal" key signatures


... but is probably not the "better" way!



2016-02-10 14:18 GMT+01:00 Pierre Perol-Schneider 
:


Hi Andrew,


In lhMusic mes.2 try :
...
\tweak X-extent #'(0 . 0)
\tweak extra-offset #'(-3 . 0)
\key es \major



Cheers,

Pierre




2016-02-10 13:36 GMT+01:00 N. Andrew Walsh :

Hi List (again),

here's another question, more general: I have a piano part in which the 
upper voice is to have one key signature, the lower to retain another one 
(namely, the right hand has \key c \major, while the left hand has \key es 
\major, which was also declared at the start of the piece). Something like 
this:



\version "2.19.36"




beambreakOn = {
 \set subdivideBeams = ##t
 \set baseMoment = #(ly:make-moment 1/8)
 \set beatStructure = #'(2 2 2 2)
}


beambreakOff = {
 \set subdivideBeams = ##f
 \set baseMoment = #(ly:make-moment 1/8)
 \set beatStructure = #'(2 2 2 2)
}


rhMusic = \relative c'' {
   \key es \major
 \time 4/8
 r16 bes d bes d bes d bes |
 \key c \major
 \beambreakOn \tuplet 3/2 { es,\( f g } \tuplet 3/2 { a b cis } dis4\) |
}


lhMusic = \relative c {
 \clef bass
 \key es \major
 \time 4/8
 <<
 { r16 d f d f d f d | }
 \\
 { bes2 | }
   >>
 \key es \major
 <<
   { es,16 bes' es bes g' d g d | }
   \\
   { es,2 | }
 >>
}


\score {


 \new PianoStaff <<
   \new Staff = "RH"  <<
 \rhMusic
   >>
   \new Staff = "LH" <<
\lhMusic
   >>
 >>
}


My issue is as follows: the engraver in charge of key signatures is 
displacing that second "\key es \major" expression in the left hand, 
presumably because there was already one in place from the beginning (or 
perhaps because it's assuming a possible collision with the "\key c \major" 
expression in the right hand). In either case, what I would prefer is that 
both new key signatures are not displaced horizontally, so that the second 
"\key es \major" is, in effect, merely a cautionary repetition of the one 
from the start and aligned underneath the naturals of the "\key c \major" 
expression in the right hand.




Is there a better way to do this?


Cheers,


A


___
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

Re: OS X Emacs Point and Click

[Kevin Barry]

Hi Daniel,

I tried to get this working some years ago. I even went as far as
installing X11 and xpdf, but still couldn't overcome some guile
problems (my memory is hazy). The discussion begins with this message:
https://lists.gnu.org/archive/html/lilypond-user/2013-12/msg00902.html

hth,
Kevin

On 10 February 2016 at 07:37, Dr. Daniel Hensel  wrote:
> Hello there,
>
> I really feel like an idiot by asking this, but who managed to get point and
> click on OS X working, especially in emacs? I figured out that the
> lilypond-invoke-editor is not able to compile on OS X. So I installed
> „guile" via homebrew and changed the directory in the lilypond-invoke-editor
> itself, so it can find guile: I changed it to
> #!/usr/local/Cellar/guile/2.0.11_2/bin/guile -s
>
> I also installed  "scm-manager" and "scm-buff", because I got scm-errors,
> but that didn’t help either:
>
> lilypond-invoke-editor
> [textedit://]/Users/*/Documents/Lilypond-Dateien/7.Modus.ly:14:84:84
> lilypond-invoke-editor (GNU LilyPond) 2.18.2
> Backtrace:
> In ice-9/boot-9.scm:
>  157: 16 [catch #t # ...]
> In unknown file:
>?: 15 [apply-smob/1 #]
> In ice-9/boot-9.scm:
>   63: 14 [call-with-prompt prompt0 ...]
> In ice-9/eval.scm:
>  432: 13 [eval # #]
> In ice-9/boot-9.scm:
> 2401: 12 [save-module-excursion # ice-9/boot-9.scm:4045:3 ()>]
> 4050: 11 [#]
> In unknown file:
>?: 10 [load-compiled/vm
> "/Users/*/.cache/guile/ccache/2.0-LE-8-2.0/Applications/LilyPond.app/Contents/Resources/bin/lilypond-invoke-editor.go"]
> In /Applications/LilyPond.app/Contents/Resources/bin/lilypond-invoke-editor:
>  164: 9 [main #]
> In ice-9/eval.scm:
>  505: 8 [# (use-modules
> #)]
> In ice-9/psyntax.scm:
> 1106: 7 [expand-top-sequence ((use-modules (scm editor))) () ...]
>  989: 6 [scan ((use-modules (scm editor))) () ...]
>  279: 5 [scan ((# #) #(syntax-object *unspecified* # #)) () (()) ...]
> In ice-9/boot-9.scm:
> 3597: 4 [process-use-modules (((scm editor)))]
>  702: 3 [map #
> ((#))]
> 3598: 2 [# (#)]
> 2867: 1 [resolve-interface (scm editor) #:select ...]
> In unknown file:
>?: 0 [scm-error misc-error #f "~A ~S" ("no code for module" (scm editor))
> #f]
>
> ERROR: In procedure scm-error:
> ERROR: no code for module (scm editor)
>
> Is there a chance to get point and click working on a Mac with emacs? I
> recently have been able to setup lilypond with emacs on my mac, thanks to
> Orm Finnendahl. Without that workaround
> http://www.danielhensel.de/www.danielhensel.de_en/styled-19/styled-22/styled-23/
> lilypond could not compile in emacs on my Mac, now it works, but it still
> lacks the point and click function. With my URL-Handler I was only able to
> open the emacs.app, but it didn’t open the file itself.
>
> Sincerely,
> Daniel Hensel
>
> ___
> 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: "bitonal" key signatures

[Pierre Perol-Schneider]

Yep, much smarter Phil.

2016-02-10 14:40 GMT+01:00 Phil Holmes :

> Better would be to add \tweak X-extent #'(0 . 0) just before the C major
> key sig in the right hand?
>
>
> --
> Phil Holmes
>
>
> - Original Message - From: Pierre Perol-Schneider
> To: N. Andrew Walsh
> Cc: lilypond-user
> Sent: Wednesday, February 10, 2016 1:19 PM
> Subject: Re: "bitonal" key signatures
>
>
>
> ... but is probably not the "better" way!
>
>
>
> 2016-02-10 14:18 GMT+01:00 Pierre Perol-Schneider <
> pierre.schneider.pa...@gmail.com>:
>
> Hi Andrew,
>
>
> In lhMusic mes.2 try :
> ...
> \tweak X-extent #'(0 . 0)
> \tweak extra-offset #'(-3 . 0)
> \key es \major
> 
>
>
> Cheers,
>
> Pierre
>
>
>
>
> 2016-02-10 13:36 GMT+01:00 N. Andrew Walsh :
>
> Hi List (again),
>
> here's another question, more general: I have a piano part in which the
> upper voice is to have one key signature, the lower to retain another one
> (namely, the right hand has \key c \major, while the left hand has \key es
> \major, which was also declared at the start of the piece). Something like
> this:
>
>
> \version "2.19.36"
>
>
>
>
> beambreakOn = {
>  \set subdivideBeams = ##t
>  \set baseMoment = #(ly:make-moment 1/8)
>  \set beatStructure = #'(2 2 2 2)
> }
>
>
> beambreakOff = {
>  \set subdivideBeams = ##f
>  \set baseMoment = #(ly:make-moment 1/8)
>  \set beatStructure = #'(2 2 2 2)
> }
>
>
> rhMusic = \relative c'' {
>\key es \major
>  \time 4/8
>  r16 bes d bes d bes d bes |
>  \key c \major
>  \beambreakOn \tuplet 3/2 { es,\( f g } \tuplet 3/2 { a b cis } dis4\) |
> }
>
>
> lhMusic = \relative c {
>  \clef bass
>  \key es \major
>  \time 4/8
>  <<
>  { r16 d f d f d f d | }
>  \\
>  { bes2 | }
>>>
>  \key es \major
>  <<
>{ es,16 bes' es bes g' d g d | }
>\\
>{ es,2 | }
>  >>
> }
>
>
> \score {
>
>
>  \new PianoStaff <<
>\new Staff = "RH"  <<
>  \rhMusic
>>>
>\new Staff = "LH" <<
> \lhMusic
>>>
>  >>
> }
> 
>
> My issue is as follows: the engraver in charge of key signatures is
> displacing that second "\key es \major" expression in the left hand,
> presumably because there was already one in place from the beginning (or
> perhaps because it's assuming a possible collision with the "\key c \major"
> expression in the right hand). In either case, what I would prefer is that
> both new key signatures are not displaced horizontally, so that the second
> "\key es \major" is, in effect, merely a cautionary repetition of the one
> from the start and aligned underneath the naturals of the "\key c \major"
> expression in the right hand.
>
>
>
> Is there a better way to do this?
>
>
> Cheers,
>
>
> A
>
>
> ___
> 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

Re: Lilypond doesn't respond anymore MacOSX 10.8

[Alberto Simões]

Hi

Not easy to help.

But, do you have disk space available?

On 10/02/16 16:43, Darrémont Jean-Michel wrote:

Hi everybody,

Lilypond was working fine until today where it stopped working with message: " 
Application not responding".
I just have to force quit.

Thanks for any help.

MacOSX 10.8.5
Lilypond 2.18.2-1
___
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 doesn't respond anymore MacOSX 10.8

[Darrémont Jean-Michel]

Hi everybody,

Lilypond was working fine until today where it stopped working with message: " 
Application not responding".
I just have to force quit.

Thanks for any help.

MacOSX 10.8.5 
Lilypond 2.18.2-1
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Writing notes for explaining rhythm

[tisimst]

Luca,

On Wed, Feb 10, 2016 at 12:22 PM, Luca Danieli [via Lilypond] <
ml-node+s1069038n187085...@n5.nabble.com> wrote:

> how can I write a note above the system without displaying the pitch of
> those notes in order to explain just the rhythm of a specific passage?
>

That's what the RhythmicStaff context is for! By default, it prints a
single staff line, but you can hide that.

HTH,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Writing-notes-for-explaining-rhythm-tp187085p187086.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

Writing notes for explaining rhythm

[Luca Danieli]

Hello all,

how can I write a note above the system without displaying the pitch of those 
notes in order to explain just the rhythm of a specific passage?

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

Re: Writing notes for explaining rhythm

[Pierre Perol-Schneider]

Hi Abraham,
you were faster.
Anyway, Luca, you said "above", so here's "above":

\version "2.18.2"

theMusic = \relative c' {
  c8. d16 e4 f8. g16 a4 a
}

\score {
  <<
\new RhythmicStaff
  \with {
\remove "Staff_symbol_engraver"
\omit TimeSignature
\omit BarLine
\override VerticalAxisGroup.staff-staff-spacing = #'(
(basic-distance . 0)
(padding . 1))
  }
  \theMusic
  \new Staff \theMusic
  >>
  \layout { }
}

Cheers,
Pierre

2016-02-10 20:35 GMT+01:00 Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:

> Hi Luca,
>
> How about:
>
> \version "2.18.2"
>
> theMusic = \relative c' {
>   c8. d16 e4 f8. g16 a4 a a a
> }
>
> \score {
>   <<
> \new Staff \theMusic
> \new RhythmicStaff
>   \with {
> \remove "Staff_symbol_engraver"
> \omit TimeSignature
> \omit BarLine
>   }
>   \theMusic
>   >>
>   \layout { }
> }
>
> HTH,
> Pierre
>
> 2016-02-10 20:21 GMT+01:00 Luca Danieli :
>
>> Hello all,
>>
>> how can I write a note above the system without displaying the pitch of
>> those notes in order to explain just the rhythm of a specific passage?
>>
>> Best,
>> Luca
>>
>> ___
>> 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: Writing notes for explaining rhythm

[Pierre Perol-Schneider]

Hi Luca,

How about:

\version "2.18.2"

theMusic = \relative c' {
  c8. d16 e4 f8. g16 a4 a a a
}

\score {
  <<
\new Staff \theMusic
\new RhythmicStaff
  \with {
\remove "Staff_symbol_engraver"
\omit TimeSignature
\omit BarLine
  }
  \theMusic
  >>
  \layout { }
}

HTH,
Pierre

2016-02-10 20:21 GMT+01:00 Luca Danieli :

> Hello all,
>
> how can I write a note above the system without displaying the pitch of
> those notes in order to explain just the rhythm of a specific passage?
>
> Best,
> Luca
>
> ___
> 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: Writing notes for explaining rhythm

[tisimst]

Pierre,

On Wed, Feb 10, 2016 at 12:43 PM, Schneidy [via Lilypond] <
ml-node+s1069038n187088...@n5.nabble.com> wrote:

> Hi Abraham,
> you were faster.
> Anyway, Luca, you said "above", so here's "above":
>
> \version "2.18.2"
>
> theMusic = \relative c' {
>   c8. d16 e4 f8. g16 a4 a
> }
>
> \score {
>   <<
> \new RhythmicStaff
>   \with {
> \remove "Staff_symbol_engraver"
> \omit TimeSignature
> \omit BarLine
> \override VerticalAxisGroup.staff-staff-spacing = #'(
> (basic-distance . 0)
> (padding . 1))
>   }
>   \theMusic
>   \new Staff \theMusic
>   >>
>   \layout { }
> }
>

That is super funny! This was the exact snippet I was going to send back
after I saw yours. Nicely done!

- Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Writing-notes-for-explaining-rhythm-tp187085p187089.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

warning: already have a volta spanner, ending that one prematurely

[Federico Bruni]

Hi all

Do you know why the following input causes this warning?
There's anything I can do to avoid it?

\version "2.19.35"
\relative {
 c'1
 \set Score.repeatCommands = #'((volta "1"))
 d'1
 \set Score.repeatCommands = #'((volta #f))

 \set Score.repeatCommands = #'((volta "2"))
 f1
 \set Score.repeatCommands = #'((volta #f))
}


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

Re: warning: already have a volta spanner, ending that one prematurely

[Thomas Morley]

2016-02-10 22:54 GMT+01:00 Federico Bruni :
> Hi all
>
> Do you know why the following input causes this warning?
> There's anything I can do to avoid it?
>
> \version "2.19.35"
> \relative {
>  c'1
>  \set Score.repeatCommands = #'((volta "1"))
>  d'1

Here you try to end the volta-spanner:
>  \set Score.repeatCommands = #'((volta #f))
>
Here you try to begin a new volta-spanner:
>  \set Score.repeatCommands = #'((volta "2"))
Both commands are set at the same musical moment, conflict! So Lily
tries to makes any sense of your input and throws a warning.
>  f1
>  \set Score.repeatCommands = #'((volta #f))
> }

`repeatCommands' expects a list. So put all stuff in _one_ list:

\relative {
 c'1
 \set Score.repeatCommands = #'((volta "1"))
 d'1
 \set Score.repeatCommands = #'((volta #f) (volta "2") end-repeat)
 f1
 \set Score.repeatCommands = #'((volta #f))
}

As shown in the NR ;)
http://www.lilypond.org/doc/v2.19/Documentation/notation/long-repeats#manual-repeat-marks

Cheers,
  Harm

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

Re: beam breaking with tuplets

[Urs Liska]

Hi Andrew,

I can't compile your example on the mobile,  but you are most certainly 
experiencing an issue where LilyPond doesn't behave according to its declared 
intention. (Assuming that with "broken" you mean subdivided).

The proper handling of subdivisions under tuplets is on my agenda in rewriting 
the beaming pattern code, and this should be fixed in one of the next devel 
releases.

Urs


Am 10. Februar 2016 12:35:53 MEZ, schrieb "N. Andrew Walsh" 
:
>Hi List,
>
>I have the following expression:
>
>\version "2.19.36"
>
>\relative c'' {
>  \set subdivideBeams = ##t
>  \set baseMoment = #(ly:make-moment 1/8)
>  \set beatStructure = #'(2 2 2 2)
>  \time 4/8
>\tuplet 3/2 { es,16\( f g } \tuplet 3/2 { a b cis\) } \tuplet 3/2 {
>dis\(
>eis g } a32 b16.->\) |
>}
>
>
>If I read the NR correctly, that should have broken every beam below
>the
>8th-note level, but the second group retains the 16th-note beam between
>the
>g in the last triplet and the a32 of the next group. It is correct in
>the
>first beat, breaking the 16th-note beams between the two triplets.
>
>Am I formatting this incorrectly? (spoiler: the answer is most
>certainly
>"yes," so I guess my question is thus more properly formulated "how am
>I
>formatting this incorrectly, and what is the correct syntax?")
>
>Cheers,
>
>A
>
>
>
>
>___
>lilypond-user mailing list
>lilypond-user@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

beam breaking with tuplets

[N. Andrew Walsh]

Hi List,

I have the following expression:

\version "2.19.36"

\relative c'' {
  \set subdivideBeams = ##t
  \set baseMoment = #(ly:make-moment 1/8)
  \set beatStructure = #'(2 2 2 2)
  \time 4/8
  \tuplet 3/2 { es,16\( f g } \tuplet 3/2 { a b cis\) } \tuplet 3/2 { dis\(
eis g } a32 b16.->\) |
}


If I read the NR correctly, that should have broken every beam below the
8th-note level, but the second group retains the 16th-note beam between the
g in the last triplet and the a32 of the next group. It is correct in the
first beat, breaking the 16th-note beams between the two triplets.

Am I formatting this incorrectly? (spoiler: the answer is most certainly
"yes," so I guess my question is thus more properly formulated "how am I
formatting this incorrectly, and what is the correct syntax?")

Cheers,

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

"bitonal" key signatures

[N. Andrew Walsh]

Hi List (again),

here's another question, more general: I have a piano part in which the
upper voice is to have one key signature, the lower to retain another one
(namely, the right hand has \key c \major, while the left hand has \key es
\major, which was also declared at the start of the piece). Something like
this:

\version "2.19.36"


beambreakOn = {
  \set subdivideBeams = ##t
  \set baseMoment = #(ly:make-moment 1/8)
  \set beatStructure = #'(2 2 2 2)
}

beambreakOff = {
  \set subdivideBeams = ##f
  \set baseMoment = #(ly:make-moment 1/8)
  \set beatStructure = #'(2 2 2 2)
}

rhMusic = \relative c'' {
\key es \major
  \time 4/8
  r16 bes d bes d bes d bes |
  \key c \major
  \beambreakOn \tuplet 3/2 { es,\( f g } \tuplet 3/2 { a b cis } dis4\) |
}

lhMusic = \relative c {
  \clef bass
  \key es \major
  \time 4/8
  <<
  { r16 d f d f d f d | }
  \\
  { bes2 | }
>>
  \key es \major
  <<
{ es,16 bes' es bes g' d g d | }
\\
{ es,2 | }
  >>
}

\score {

  \new PianoStaff <<
\new Staff = "RH"  <<
  \rhMusic
>>
\new Staff = "LH" <<
 \lhMusic
>>
  >>
}

My issue is as follows: the engraver in charge of key signatures is
displacing that second "\key es \major" expression in the left hand,
presumably because there was already one in place from the beginning (or
perhaps because it's assuming a possible collision with the "\key c \major"
expression in the right hand). In either case, what I would prefer is that
both new key signatures are not displaced horizontally, so that the second
"\key es \major" is, in effect, merely a cautionary repetition of the one
from the start and aligned underneath the naturals of the "\key c \major"
expression in the right hand.

Is there a better way to do this?

Cheers,

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

Re: "bitonal" key signatures

[Pierre Perol-Schneider]

Hi Andrew,

In lhMusic mes.2 try :
...
\tweak X-extent #'(0 . 0)
\tweak extra-offset #'(-3 . 0)
\key es \major


Cheers,
Pierre


2016-02-10 13:36 GMT+01:00 N. Andrew Walsh :

> Hi List (again),
>
> here's another question, more general: I have a piano part in which the
> upper voice is to have one key signature, the lower to retain another one
> (namely, the right hand has \key c \major, while the left hand has \key es
> \major, which was also declared at the start of the piece). Something like
> this:
>
> \version "2.19.36"
>
>
> beambreakOn = {
>   \set subdivideBeams = ##t
>   \set baseMoment = #(ly:make-moment 1/8)
>   \set beatStructure = #'(2 2 2 2)
> }
>
> beambreakOff = {
>   \set subdivideBeams = ##f
>   \set baseMoment = #(ly:make-moment 1/8)
>   \set beatStructure = #'(2 2 2 2)
> }
>
> rhMusic = \relative c'' {
> \key es \major
>   \time 4/8
>   r16 bes d bes d bes d bes |
>   \key c \major
>   \beambreakOn \tuplet 3/2 { es,\( f g } \tuplet 3/2 { a b cis } dis4\) |
> }
>
> lhMusic = \relative c {
>   \clef bass
>   \key es \major
>   \time 4/8
>   <<
>   { r16 d f d f d f d | }
>   \\
>   { bes2 | }
> >>
>   \key es \major
>   <<
> { es,16 bes' es bes g' d g d | }
> \\
> { es,2 | }
>   >>
> }
>
> \score {
>
>   \new PianoStaff <<
> \new Staff = "RH"  <<
>   \rhMusic
> >>
> \new Staff = "LH" <<
>  \lhMusic
> >>
>   >>
> }
> 
> My issue is as follows: the engraver in charge of key signatures is
> displacing that second "\key es \major" expression in the left hand,
> presumably because there was already one in place from the beginning (or
> perhaps because it's assuming a possible collision with the "\key c \major"
> expression in the right hand). In either case, what I would prefer is that
> both new key signatures are not displaced horizontally, so that the second
> "\key es \major" is, in effect, merely a cautionary repetition of the one
> from the start and aligned underneath the naturals of the "\key c \major"
> expression in the right hand.
>
> Is there a better way to do this?
>
> Cheers,
>
> A
>
> ___
> 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: "bitonal" key signatures

[Pierre Perol-Schneider]

... but is probably not the "better" way!

2016-02-10 14:18 GMT+01:00 Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:

> Hi Andrew,
>
> In lhMusic mes.2 try :
> ...
> \tweak X-extent #'(0 . 0)
> \tweak extra-offset #'(-3 . 0)
> \key es \major
> 
>
> Cheers,
> Pierre
>
>
> 2016-02-10 13:36 GMT+01:00 N. Andrew Walsh :
>
>> Hi List (again),
>>
>> here's another question, more general: I have a piano part in which the
>> upper voice is to have one key signature, the lower to retain another one
>> (namely, the right hand has \key c \major, while the left hand has \key es
>> \major, which was also declared at the start of the piece). Something like
>> this:
>>
>> \version "2.19.36"
>>
>>
>> beambreakOn = {
>>   \set subdivideBeams = ##t
>>   \set baseMoment = #(ly:make-moment 1/8)
>>   \set beatStructure = #'(2 2 2 2)
>> }
>>
>> beambreakOff = {
>>   \set subdivideBeams = ##f
>>   \set baseMoment = #(ly:make-moment 1/8)
>>   \set beatStructure = #'(2 2 2 2)
>> }
>>
>> rhMusic = \relative c'' {
>> \key es \major
>>   \time 4/8
>>   r16 bes d bes d bes d bes |
>>   \key c \major
>>   \beambreakOn \tuplet 3/2 { es,\( f g } \tuplet 3/2 { a b cis } dis4\) |
>> }
>>
>> lhMusic = \relative c {
>>   \clef bass
>>   \key es \major
>>   \time 4/8
>>   <<
>>   { r16 d f d f d f d | }
>>   \\
>>   { bes2 | }
>> >>
>>   \key es \major
>>   <<
>> { es,16 bes' es bes g' d g d | }
>> \\
>> { es,2 | }
>>   >>
>> }
>>
>> \score {
>>
>>   \new PianoStaff <<
>> \new Staff = "RH"  <<
>>   \rhMusic
>> >>
>> \new Staff = "LH" <<
>>  \lhMusic
>> >>
>>   >>
>> }
>> 
>> My issue is as follows: the engraver in charge of key signatures is
>> displacing that second "\key es \major" expression in the left hand,
>> presumably because there was already one in place from the beginning (or
>> perhaps because it's assuming a possible collision with the "\key c \major"
>> expression in the right hand). In either case, what I would prefer is that
>> both new key signatures are not displaced horizontally, so that the second
>> "\key es \major" is, in effect, merely a cautionary repetition of the one
>> from the start and aligned underneath the naturals of the "\key c \major"
>> expression in the right hand.
>>
>> Is there a better way to do this?
>>
>> Cheers,
>>
>> A
>>
>> ___
>> 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

OS X Emacs Point and Click

[Dr. Daniel Hensel]

Hello there,

I really feel like an idiot by asking this, but who managed to get point and 
click on OS X working, especially in emacs? I figured out that the 
lilypond-invoke-editor is not able to compile on OS X. So I installed „guile" 
via homebrew and changed the directory in the lilypond-invoke-editor itself, so 
it can find guile: I changed it to
#!/usr/local/Cellar/guile/2.0.11_2/bin/guile -s

I also installed  "scm-manager" and "scm-buff", because I got scm-errors, but 
that didn’t help either:

lilypond-invoke-editor 
[textedit://]/Users/*/Documents/Lilypond-Dateien/7.Modus.ly:14:84:84
lilypond-invoke-editor (GNU LilyPond) 2.18.2
Backtrace:
In ice-9/boot-9.scm:
 157: 16 [catch #t # ...]
In unknown file:
   ?: 15 [apply-smob/1 #]
In ice-9/boot-9.scm:
  63: 14 [call-with-prompt prompt0 ...]
In ice-9/eval.scm:
 432: 13 [eval # #]
In ice-9/boot-9.scm:
2401: 12 [save-module-excursion #]
4050: 11 [#]
In unknown file:
   ?: 10 [load-compiled/vm 
"/Users/*/.cache/guile/ccache/2.0-LE-8-2.0/Applications/LilyPond.app/Contents/Resources/bin/lilypond-invoke-editor.go"]
In /Applications/LilyPond.app/Contents/Resources/bin/lilypond-invoke-editor:
 164: 9 [main #]
In ice-9/eval.scm:
 505: 8 [# (use-modules #)]
In ice-9/psyntax.scm:
1106: 7 [expand-top-sequence ((use-modules (scm editor))) () ...]
 989: 6 [scan ((use-modules (scm editor))) () ...]
 279: 5 [scan ((# #) #(syntax-object *unspecified* # #)) () (()) ...]
In ice-9/boot-9.scm:
3597: 4 [process-use-modules (((scm editor)))]
 702: 3 [map # 
((#))]
3598: 2 [# (#)]
2867: 1 [resolve-interface (scm editor) #:select ...]
In unknown file:
   ?: 0 [scm-error misc-error #f "~A ~S" ("no code for module" (scm editor)) #f]

ERROR: In procedure scm-error:
ERROR: no code for module (scm editor)

Is there a chance to get point and click working on a Mac with emacs? I 
recently have been able to setup lilypond with emacs on my mac, thanks to Orm 
Finnendahl. Without that workaround 
http://www.danielhensel.de/www.danielhensel.de_en/styled-19/styled-22/styled-23/
 

  lilypond could not compile in emacs on my Mac, now it works, but it still 
lacks the point and click function. With my URL-Handler I was only able to open 
the emacs.app, but it didn’t open the file itself. 

Sincerely,
Daniel Hensel___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user