date:20140727

Re: thanks again for the editionEngraver

2014-07-27 Thread Kieren MacMillan

Hi Jan-Peter,

> I think the most complicated part is addressing multiple voices in one Staff.
[…]
> propably there are more things to modify to make it more intuitive.

I think the stated problem would be solved *AND* the whole machinery made more 
intuitive by allowing a context to be “direct addressed”, i.e., the context

\new Staff = “MyStaff” \someMusic

would be mod-ed using something like

\editionMod ThisEdition 1 0/4 APiece.MyStaff \override …

as opposed to

\editionMod ThisEdition 1 0/4 APiece.Staff.B \override …

It seems like a very small change — and might mess up your “templating” 
system(s) — but three obvious and immediate benefits are: the ability to move 
contexts within the score block without having to recode the edition; the 
ability to change the type of context without recoding the edition; and the 
ability to quickly cross-reference a mod with its context (i.e., no need to 
“count” contexts).

Consider it?

Thanks,
Kieren.
___

Kieren MacMillan, composer
www:  
email:  i...@kierenmacmillan.info
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: See the new music fonts in action

2014-07-27 Thread Werner LEMBERG


> Scorlatti?

:-)  I like it.


Werner

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

Re: Hairpin inside slur?

2014-07-27 Thread pls


On 27.07.2014, at 22:18, Phil Holmes  wrote:

> I don't know.  My guess: there is no reasonable slur that will miss the 
> hairpin if the hairpin is inside the slur, so Lily does the best compromise.

Thanks, Phil!  It’s actually an excerpt of a real-life example I’m trying to 
re-engrave.  There is probably no automated solution for this case so I might 
use the \shape function.

patrick
>  
> - Original Message -
> From: pls
> To: Abel Cheung
> Cc: lilypond-user
> Sent: Sunday, July 27, 2014 8:18 PM
> Subject: Re: Hairpin inside slur?
> 
> Hey all,
> 
> today I experimented with hairpins inside slurs and encountered a strange 
> phenomenon: 
> 
> \version "2.19.11"
> 
> exOne = { 
>   \override Slur.height-limit = 20
>   \override DynamicLineSpanner #'outside-staff-priority = ##f  
>   c'32 ( g'32 ^\< c''32 g''32\! a''32 ^\> g''32 e''32\! g'32 )   
> }
> 
> exTwo = { 
>   \override Slur.height-limit = 20
>   \override DynamicLineSpanner #'outside-staff-priority = ##f  
>   e32 (  g32_\< b32 c'32\! d'32_\> c'32  g32\! e32 )
> }
> 
> {
>   \exOne 
> }
> 
> {
>   \exTwo 
> }
> 
> 
> 
> The second example works as expected.  I’m running out of ideas why the 
> hairpins can’t be moved inside the slur in the first example.  Am I missing 
> something?
> 
> Thanks for your help!
> 
> patrick
> On 26.07.2014, at 22:29, Abel Cheung  wrote:
> 
>> On Sat, Jul 26, 2014 at 11:54 PM, Thomas Morley
>>  wrote:
 Currently hairpin is always placed outside slurs. What controls their
 vertial priority?
>>> 
>>>  \override DynamicLineSpanner #'outside-staff-priority = ##f
>> 
>> Silly me, I've been keep trying zero and negative values. Thanks a lot.
>> 
>> Abel
>> 
>> 
>> 
>>> 
  \music
  \break
  \override Hairpin.extra-offset = #'(0 . 3)
  \music
 }
 
 --
 Abel Cheung
>>> 
>>> HTH,
>>>  Harm
>> 
>> 
>> 
>> -- 
>> Abel Cheung
>> New GPG Key fingerprint: F43B 7F88 3D7B 4B58 928E  0151 EC2B E414 3B03 A8AC
>> Old GPG Key fingerprint: 671C C7AE EFB5 110C D6D1  41EE 4152 E1F1 C671 86FF
>> 
>> ___
>> 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: Hairpin inside slur?

2014-07-27 Thread pls


On 27.07.2014, at 22:11, Mike Solomon  wrote:

> 
> On Jul 27, 2014, at 10:18 PM, pls  wrote:
> 
>> Hey all,
>> 
>> today I experimented with hairpins inside slurs and encountered a strange 
>> phenomenon: 
>> 
>> \version "2.19.11"
>> 
>> exOne = { 
>>   \override Slur.height-limit = 20
>>   \override DynamicLineSpanner #'outside-staff-priority = ##f  
>>   c'32 ( g'32 ^\< c''32 g''32\! a''32 ^\> g''32 e''32\! g'32 )   
>> }
>> 
>> exTwo = { 
>>   \override Slur.height-limit = 20
>>   \override DynamicLineSpanner #'outside-staff-priority = ##f  
>>   e32 (  g32_\< b32 c'32\! d'32_\> c'32  g32\! e32 )
>> }
>> 
>> {
>>   \exOne 
>> }
>> 
>> {
>>   \exTwo 
>> }
>> 
>> 
>> 
>> The second example works as expected.  I’m running out of ideas why the 
>> hairpins can’t be moved inside the slur in the first example.  Am I missing 
>> something?
>> 
>> Thanks for your help!
>> 
>> patrick
> 
> 
> The slur is ignoring the hairpin and vice versa, so the lack of an 
> intersection in the second example is serendipitous and not the result of any 
> collision avoidance mechanism.
> 
> Currently, in addition to note-heads and stems, slurs avoid what are called 
> “extra-objects”.  These objects are hard-coded into the Slur engraver and are 
> things like tuplet numbers, scripts, and fingerings.  Hairpins and 
> DynamicLineSpanners are currently not in this category.
> 
> So unfortunately it is currently not possible in the way you’re aiming for.
> 
> But, there is one possibility worth studying:
> 
> exOne = {
>   \override Slur.height-limit = 20
>   \override DynamicLineSpanner #'outside-staff-priority = #20
>   \override Slur #'outside-staff-priority = #21
>   c'32 ( g'32 ^\< c''32 g''32\! a''32 ^\> g''32 e''32\! g'32 )   
> }
> 
> {
>   \exOne
> }
> 
> If you go with this, I'd recommend thinning out the girth of the hairpin, as 
> a slur that high is a bit of an eyesore IMO.

Thanks, Mike!

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

Re: How do I write Bm7b5

2014-07-27 Thread keith Luke

You can use { \small \flat \small5 } if you want to use the flat symbol
instead of a lowercase b.


On Fri, Jul 25, 2014 at 7:52 AM, Flaming Hakama by Elaine <
ela...@flaminghakama.com> wrote:

> Guptila,
>
> On Fri, Jul 25, 2014 at 6:01 AM,  wrote:
>
>> From: Guptila de Silva 
>> To: lilypond-user@gnu.org
>> Subject: Lilypond notation for Bm7b5
>>
>>
>> Hi, How do I write Bm7b5 in Lilypond notation? I can get the fretboard
>> diagram show up but cannot work out how to get the chord name in this
>> format.
>>
>> Many thanks.
>>
>> Guptila
>>
>
> Here is something that does that.  Also discussed at
> http://flaminghakama.com/flaming-lilypond-chords
>
>
> \version "2.18.0"
> \include "english.ly"
>
> myChordExceptions = {
>
>   % Half-diminished
>   1-\markup { m7b5 }
>
>   % If you want to fiddle with formatting of the symbols, here is one
> approach
>   %1-\markup { \raise #0.2 { \magnify #0.2 { " " }
> \small { m } } \raise #0.3 { \normalsize 7 } \raise #0.6 { \small b5 } }
>
> }
> chExceptions = #(append (sequential-music-to-chord-exceptions
> myChordExceptions #t) ignatzekExceptions)
>
> myChordSequence = \chordmode {
>   \set chordChanges = ##t
>   \set chordNameExceptions = #chExceptions
>   b1:m7.5-
> }
>
> myMelody = \relative c'' {
>   r4 f8 d b a4.
> }
>
> \score {
>   \new StaffGroup <<
> \new ChordNames \myChordSequence
> \new Staff {
>   \myMelody
> }
>   >>
> }
>
>
>
> HTH,
>
> David Elaine Alt
> 415 . 341 .4954   "*Confusion is
> highly underrated*"
> ela...@flaminghakama.com
> self-immolation.info
> skype: flaming_hakama
> Producer ~ Composer ~ Instrumentalist
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> ___
> 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: Hairpin inside slur?

2014-07-27 Thread Phil Holmes

I don't know.  My guess: there is no reasonable slur that will miss the hairpin 
if the hairpin is inside the slur, so Lily does the best compromise.

--
Phil Holmes


  - Original Message - 
  From: pls 
  To: Abel Cheung 
  Cc: lilypond-user 
  Sent: Sunday, July 27, 2014 8:18 PM
  Subject: Re: Hairpin inside slur?


  Hey all,


  today I experimented with hairpins inside slurs and encountered a strange 
phenomenon: 


  \version "2.19.11"


  exOne = { 
\override Slur.height-limit = 20
\override DynamicLineSpanner #'outside-staff-priority = ##f  
c'32 ( g'32 ^\< c''32 g''32\! a''32 ^\> g''32 e''32\! g'32 )   
  }


  exTwo = { 
\override Slur.height-limit = 20
\override DynamicLineSpanner #'outside-staff-priority = ##f  
e32 (  g32_\< b32 c'32\! d'32_\> c'32  g32\! e32 )
  }


  {
\exOne 
  }


  {
\exTwo 
  }





  The second example works as expected.  I’m running out of ideas why the 
hairpins can’t be moved inside the slur in the first example.  Am I missing 
something?


  Thanks for your help!


  patrick
  On 26.07.2014, at 22:29, Abel Cheung  wrote:


On Sat, Jul 26, 2014 at 11:54 PM, Thomas Morley
 wrote:

Currently hairpin is always placed outside slurs. What controls their
vertial priority?


   \override DynamicLineSpanner #'outside-staff-priority = ##f


Silly me, I've been keep trying zero and negative values. Thanks a lot.

Abel






 \music
 \break
 \override Hairpin.extra-offset = #'(0 . 3)
 \music
}

--
Abel Cheung


  HTH,
   Harm




-- 
Abel Cheung
New GPG Key fingerprint: F43B 7F88 3D7B 4B58 928E  0151 EC2B E414 3B03 A8AC
Old GPG Key fingerprint: 671C C7AE EFB5 110C D6D1  41EE 4152 E1F1 C671 86FF

___
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: Hairpin inside slur?

2014-07-27 Thread Mike Solomon


On Jul 27, 2014, at 10:18 PM, pls  wrote:

> Hey all,
> 
> today I experimented with hairpins inside slurs and encountered a strange 
> phenomenon: 
> 
> \version "2.19.11"
> 
> exOne = { 
>   \override Slur.height-limit = 20
>   \override DynamicLineSpanner #'outside-staff-priority = ##f  
>   c'32 ( g'32 ^\< c''32 g''32\! a''32 ^\> g''32 e''32\! g'32 )   
> }
> 
> exTwo = { 
>   \override Slur.height-limit = 20
>   \override DynamicLineSpanner #'outside-staff-priority = ##f  
>   e32 (  g32_\< b32 c'32\! d'32_\> c'32  g32\! e32 )
> }
> 
> {
>   \exOne 
> }
> 
> {
>   \exTwo 
> }
> 
> 
> 
> The second example works as expected.  I’m running out of ideas why the 
> hairpins can’t be moved inside the slur in the first example.  Am I missing 
> something?
> 
> Thanks for your help!
> 
> patrick
> On 26.07.2014, at 22:29, Abel Cheung  wrote:
> 
>> On Sat, Jul 26, 2014 at 11:54 PM, Thomas Morley
>>  wrote:
 Currently hairpin is always placed outside slurs. What controls their
 vertial priority?
>>> 
>>>  \override DynamicLineSpanner #'outside-staff-priority = ##f
>> 
>> Silly me, I've been keep trying zero and negative values. Thanks a lot.
>> 
>> Abel
>> 
>> 
>> 
>>> 
  \music
  \break
  \override Hairpin.extra-offset = #'(0 . 3)
  \music
 }
 
 --
 Abel Cheung
>>> 
>>> HTH,
>>>  Harm
>> 
>> 


The slur is ignoring the hairpin and vice versa, so the lack of an intersection 
in the second example is serendipitous and not the result of any collision 
avoidance mechanism.

Currently, in addition to note-heads and stems, slurs avoid what are called 
“extra-objects”.  These objects are hard-coded into the Slur engraver and are 
things like tuplet numbers, scripts, and fingerings.  Hairpins and 
DynamicLineSpanners are currently not in this category.

So unfortunately it is currently not possible in the way you’re aiming for.

But, there is one possibility worth studying:

exOne = {
  \override Slur.height-limit = 20
  \override DynamicLineSpanner #'outside-staff-priority = #20
  \override Slur #'outside-staff-priority = #21
  c'32 ( g'32 ^\< c''32 g''32\! a''32 ^\> g''32 e''32\! g'32 )   
}

{
  \exOne
}

If you go with this, I'd recommend thinning out the girth of the hairpin, as a 
slur that high is a bit of an eyesore IMO.

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

Re: Hairpin inside slur?

2014-07-27 Thread pls

Hey all,

today I experimented with hairpins inside slurs and encountered a strange 
phenomenon: 

\version "2.19.11"

exOne = { 
  \override Slur.height-limit = 20
  \override DynamicLineSpanner #'outside-staff-priority = ##f  
  c'32 ( g'32 ^\< c''32 g''32\! a''32 ^\> g''32 e''32\! g'32 )   
}

exTwo = { 
  \override Slur.height-limit = 20
  \override DynamicLineSpanner #'outside-staff-priority = ##f  
  e32 (  g32_\< b32 c'32\! d'32_\> c'32  g32\! e32 )
}

{
  \exOne 
}

{
  \exTwo 
}



The second example works as expected.  I’m running out of ideas why the 
hairpins can’t be moved inside the slur in the first example.  Am I missing 
something?

Thanks for your help!

patrick
On 26.07.2014, at 22:29, Abel Cheung  wrote:

> On Sat, Jul 26, 2014 at 11:54 PM, Thomas Morley
>  wrote:
>>> Currently hairpin is always placed outside slurs. What controls their
>>> vertial priority?
>> 
>>  \override DynamicLineSpanner #'outside-staff-priority = ##f
> 
> Silly me, I've been keep trying zero and negative values. Thanks a lot.
> 
> Abel
> 
> 
> 
>> 
>>>  \music
>>>  \break
>>>  \override Hairpin.extra-offset = #'(0 . 3)
>>>  \music
>>> }
>>> 
>>> --
>>> Abel Cheung
>> 
>> HTH,
>>  Harm
> 
> 
> 
> -- 
> Abel Cheung
> New GPG Key fingerprint: F43B 7F88 3D7B 4B58 928E  0151 EC2B E414 3B03 A8AC
> Old GPG Key fingerprint: 671C C7AE EFB5 110C D6D1  41EE 4152 E1F1 C671 86FF
> 
> ___
> 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: See the new music fonts in action

2014-07-27 Thread Conor Cook

> From: Abraham Lee 
> Subject: Re: See the new music fonts in action
> Date: July 27, 2014 at 11:09:00 AM EDT
> To: David Kastrup 
> Cc: Urs Liska , LilyPond Users 
> 
> 
> You may be joking, but that's not a bad idea. Scorlatti... Maybe so.
> 
> -Abraham
> 
> 
> On Sun, Jul 27, 2014 at 8:30 AM, David Kastrup  wrote:
> Abraham Lee  writes:
> 
> > P.P.S. You don't like "Amadeus"? I feel rejected :) I guess I'm okay with
> > that... What shall we call it? Maybe something to do with SCORE itself or
> > with Leland Smith (the author)? I'm open to suggestions.
> 
> Scorlatti?  Thanks, thanks, you are too kind.  I'll be here the whole
> week.
> 
> --
> David Kastrup

What about "Nannerl"?

~Conor Cook___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: tenorized treble clef

2014-07-27 Thread Conor Cook

> From: Janek Warchoł 
> Subject: tenorized treble clef
> Date: July 27, 2014 at 10:30:15 AM EDT
> To: LilyPond Users , Marc Hohl , 
> Werner Lemberg 
> 
> 
> Hi,
> 
> LilyPond has a treble clef with added C-clef-like stuff:
> 
> { \clef "tenorG" c' }
> 
> (http://lists.gnu.org/archive/html/lilypond-user/2013-11/msg00661.html)
> However, it seems to me that these added lines should be positioned
> half a staff-space lower.  After all, C clef indicates the position of
> middle C:
> 
> { \clef "tenor" c' }
> 
> The way we have it right now, the extra "claws" point to d instead of
> c.  I see that the engraved example provided in the thread linked
> above has this positioning, but I think that's a mistake on the
> clef-punch manufacturer's side.  What do you think?  Does anyone have
> more examples of such clef?
> 
> best,
> Janek

It seems like the claws are indicating octave displacement, and the best way to 
show it was by centering the switch on D.  I think the claw ends are the 
important part.

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

Re: tenorized treble clef

2014-07-27 Thread Simon Albrecht


Am 27.07.2014 16:30, schrieb Janek Warchoł:

Hi,

LilyPond has a treble clef with added C-clef-like stuff:

{ \clef "tenorG" c' }

(http://lists.gnu.org/archive/html/lilypond-user/2013-11/msg00661.html)
However, it seems to me that these added lines should be positioned
half a staff-space lower.  After all, C clef indicates the position of
middle C:

{ \clef "tenor" c' }

The way we have it right now, the extra "claws" point to d instead of
c.  I see that the engraved example provided in the thread linked
above has this positioning, but I think that's a mistake on the
clef-punch manufacturer's side.  What do you think?
I think there is a misunderstanding here which originates in a logical 
inconsistency of this design:
For all I know, this clef has only been in use in France in the first 
half of the twentieth century (examples I have seen are from the late 
1930’s), and quite exactly in the shape that Lily now reproduces, with 
the “claws” pointing to the fourth line (counted from the bottom), as 
they do with the tenor clef. However, the “claws” are not actually 
indicating the position of the middle (or any other) c, but rather serve 
as a mere reminiscence of the specific tenor clef and the reader is 
supposed to conclude that the following notes are in a tenor register, 
that is, an octave lower as with a normal g clef. And indeed it is 
confusing and, strictly speaking, wrong that the g and c clefs mixed in 
this shape contradict each other.
So, nothing wrong in Lily’s adaptation there, only I have my doubts if 
it’s really a good idea to reactivate this clef, except for nostalgia 
reasons ;-)


Best regards, Simon

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

Re: See the new music fonts in action

2014-07-27 Thread Abraham Lee

You may be joking, but that's not a bad idea. Scorlatti... Maybe so.

-Abraham


On Sun, Jul 27, 2014 at 8:30 AM, David Kastrup  wrote:

> Abraham Lee  writes:
>
> > P.P.S. You don't like "Amadeus"? I feel rejected :) I guess I'm okay with
> > that... What shall we call it? Maybe something to do with SCORE itself or
> > with Leland Smith (the author)? I'm open to suggestions.
>
> Scorlatti?  Thanks, thanks, you are too kind.  I'll be here the whole
> week.
>
> --
> David Kastrup
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

tenorized treble clef

2014-07-27 Thread Janek Warchoł

Hi,

LilyPond has a treble clef with added C-clef-like stuff:

{ \clef "tenorG" c' }

(http://lists.gnu.org/archive/html/lilypond-user/2013-11/msg00661.html)
However, it seems to me that these added lines should be positioned
half a staff-space lower.  After all, C clef indicates the position of
middle C:

{ \clef "tenor" c' }

The way we have it right now, the extra "claws" point to d instead of
c.  I see that the engraved example provided in the thread linked
above has this positioning, but I think that's a mistake on the
clef-punch manufacturer's side.  What do you think?  Does anyone have
more examples of such clef?

best,
Janek

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

Re: See the new music fonts in action

2014-07-27 Thread David Kastrup

Abraham Lee  writes:

> P.P.S. You don't like "Amadeus"? I feel rejected :) I guess I'm okay with
> that... What shall we call it? Maybe something to do with SCORE itself or
> with Leland Smith (the author)? I'm open to suggestions.

Scorlatti?  Thanks, thanks, you are too kind.  I'll be here the whole
week.

-- 
David Kastrup

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

Re: thanks again for the editionEngraver

Re: See the new music fonts in action

Re: Hairpin inside slur?

Re: Hairpin inside slur?

Re: How do I write Bm7b5

Re: Hairpin inside slur?

Re: Hairpin inside slur?

Re: Hairpin inside slur?

Re: See the new music fonts in action

Re: tenorized treble clef

Re: tenorized treble clef

Re: See the new music fonts in action

tenorized treble clef

Re: See the new music fonts in action

14 matches

Site Navigation

Mail list logo

Footer information