Re: Repeat volta not at beginning of piece doesn't get initial repeat bar line

[Jay Anderson]

On Thu, Jun 26, 2014 at 2:05 PM, James  wrote:
> On 26/06/14 16:53, Jay Anderson wrote:
>> You're right that the \bar "||" is overriding the repeat bar. I assume
>> you're wanting a double bar before the break. Use \bar ".|:-||"
>> instead. You can lookup valid bar strings in bar-line.scm.
>>
>> -Jay
>>
> So does the documentation need changing as it is not clear here; and if
> so can you let me know what it should be?

To me the bar line situation is pretty clear here:
http://www.lilypond.org/doc/v2.19/Documentation/notation/bars

and here:
http://www.lilypond.org/doc/v2.19/Documentation/notation/long-repeats

When I'm looking for a specific bar line I tend to look directly in
bar-line.scm.

-Jay

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

Variable length bars

[Patrick or Cynthia Karl]

I'm trying to set a John Dowland piece (Come Ye Heavy States of Night) which 
has a single initial time signature of "4/2 2/2" followed by measures that are 
either 4 half-note beats or 2 half-note beats long, in quasi-random fashion.

It's clear that if I can get that time signature printed, I can set the piece 
by appropriate use of \set Timing.measureLength.

Can anyone point me to a way to do that?

Thanks

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

Re: Repeat volta not at beginning of piece doesn't get initial repeat bar line

[James]

On 26/06/14 16:53, Jay Anderson wrote:
> On Thu, Jun 26, 2014 at 8:37 AM, Patrick or Cynthia Karl  
> wrote:
>> Section 1.4 of the Notation Manual says about volta repeats:
>>
>> volta   The repeated music is not written out but enclosed between 
>> repeat bar lines. If the repeat is at the 
>> beginning of a piece, a repeat bar line is only printed at the end of the
>>   repeat.
>>
>> But the following snippet does not generate the initial repeat bar line, 
>> apparently because of the "||" bar line.  But the "||" bar line does not 
>> indicate the end of a piece.
>>
>> I have tried several things to get the inital repeat bar line to appear 
>> without success.  I suspect it's not very difficult.  Can anyone please tell 
>> me how to do it?  And if I'm correct about the problem being caused by the 
>> "||" bar line, the documentation should probably be changed.
>>
>> \version "2.18.2"
>>
>> music = \relative b' {
>> a1 a a a
>> \bar "||"
>>
>> \break
>>
>> \repeat volta 2 { a4 b c d }
>> }
> You're right that the \bar "||" is overriding the repeat bar. I assume
> you're wanting a double bar before the break. Use \bar ".|:-||"
> instead. You can lookup valid bar strings in bar-line.scm.
>
> -Jay
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
So does the documentation need changing as it is not clear here; and if
so can you let me know what it should be?

James

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

Re: Sloped/Angled ottava spanner

[James]

Javier,

On 26/06/14 20:49, Pierre Perol-Schneider wrote:
> 2014-06-26 19:13 GMT+02:00 Javier Ruiz-Alma  >:
>
> Pierre,
> Thank you for taking the time to craft this mod.  Works great.
> This should definitely be added to LSR.
> Let me know if you want me to take it there.  Javier
>
>
> Please do so :)
> Cheers,
> Pierre
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
Actually I am already adding a new (different) snippet to a section of
the Notation Reference where some other ottava snippets are referenced,
so let me do this for you with a doc patch.

I don't know how long it takes for LSR to get into Git and most people
will hit the Notation Reference first so perhaps it would be as good in
the doc and then get imported into the LSR.

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

Re: Sloped/Angled ottava spanner

[Pierre Perol-Schneider]

2014-06-26 19:13 GMT+02:00 Javier Ruiz-Alma :

> Pierre,
> Thank you for taking the time to craft this mod.  Works great. This should
> definitely be added to LSR.
> Let me know if you want me to take it there.  Javier
>

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

Re: Repeat volta not at beginning of piece doesn't get initial repeat bar line

[Marc Hohl]

[...]

Sorry, that doesn't work for me, result is the same.  I assume you're saying to replace the \bar 
"||" with \bar ".|:-||".


Typo?

\version "2.18.2"

music = \relative b' {
   a1 a a a
   \bar ".|:-||"

   \break

   \repeat volta 2 { a4 b c d }
}

\score  {
  \new Staff { \music }
}

compiles for me and yields in a || at the end of the first and a .|: at
the beginning of the next line.


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

Re: Repeat volta not at beginning of piece doesn't get initial repeat bar line

[Marc Hohl]

[sorry, forgot to reply to list]
Am 26.06.2014 18:22, schrieb Patrick or Cynthia Karl:

In lilypond-user Digest, Vol 139, Issue 98 Message: 6, Jay Anderson wrote:



Date: Thu, 26 Jun 2014 08:53:23 -0700
From: Jay Anderson 
To: Patrick or Cynthia Karl 
Subject: Re: Repeat volta not at beginning of piece doesn't get
initial repeat  bar line

On Thu, Jun 26, 2014 at 8:37 AM, Patrick or Cynthia Karl  wrote:

Section 1.4 of the Notation Manual says about volta repeats:

volta   The repeated music is not written out but enclosed between 
repeat bar lines. If the repeat is at the beginning 
of a piece, a repeat bar line is only printed at the end of the 
 repeat.

But the following snippet does not generate the initial repeat bar line, apparently because of the 
"||" bar line.  But the "||" bar line does not indicate the end of a piece.

I have tried several things to get the inital repeat bar line to appear without success.  
I suspect it's not very difficult.  Can anyone please tell me how to do it?  And if I'm 
correct about the problem being caused by the "||" bar line, the documentation 
should probably be changed.

\version "2.18.2"

music = \relative b' {
a1 a a a
\bar "||"

\break

\repeat volta 2 { a4 b c d }
}


You're right that the \bar "||" is overriding the repeat bar. I assume
you're wanting a double bar before the break. Use \bar ".|:-||"
instead. You can lookup valid bar strings in bar-line.scm.


Sorry, that doesn't work for me, result is the same.  I assume you're saying to replace the \bar 
"||" with \bar ".|:-||".


It should work with \bar ".|:-||" instead of \bar "||", though.


I still don't understand why the "||" bar is overriding the repeat bar, as "||" 
doesn't signify end-of-piece so the \repeat volta is not at the beginning of a piece so the initial 
repeat bar line should be printed.


Lilypond's bar lines have four values: the unbroken bar line, the parts
that are used if the bar line is at a line break, and a corresponding 
span bar line.


If you manually set \bar "||", then lilypond sets the corresponding
bar line types for the end of the line and the beginning of the
new line, which overrides the \repeat settings.

I must admit that the workaround above is in no way an ideal solution,
but it is not that simple to convince Lilypond to do the right thing
out of the box ...

HTH,

Marc


___
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: outside-staff-priority for markups attached to <>

[Richard Shann]

Oh, thank you - that is much neater syntax anyway.

Richard

On Thu, 2014-06-26 at 17:42 +0100, Mark Knoop wrote:
> At 17:26 on 26 Jun 2014, Richard Shann wrote:
> >When I generate text to appear above some music using the <>^\markup
> >"mytext" syntax, I don't seem to be able to control the
> >outside-staff-priority. In this example despite the second bit of
> >markup having a lower outside-staff-priority it appears above the
> >first bit.
> >
> >\version "2.18.0"
> >\score {
> > {  \once \override TextScript.outside-staff-priority = #1000  <>
> > ^\markup "Above the next text please" \once \override
> > TextScript.outside-staff-priority = #0  a'4^"below please" }
> >}
> >
> >
> >Can anyone suggest why this is happening and if there is a solution
> >that doesn't involve using a different sort of syntax for the markup,
> >(i.e. not involving the <> trick)? (The final target of all this is
> >scores with markup containing encapsulated postscript to create old
> >French clavecin ornaments which have to have a low
> >outside-staff-priority despite being textScript).
> 
> Since both events happen at the same moment in time, you have to use
> tweak.
> 
> \version "2.18.0"
> \score {
>  {
> <>-\tweak outside-staff-priority #1000
> ^\markup "Above the next text please"
> a'4-\tweak outside-staff-priority #0 ^"below please"
>  }
> }
> 
> --
> Mark Knoop



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

Re: outside-staff-priority for markups attached to <>

[Mark Knoop]

At 17:26 on 26 Jun 2014, Richard Shann wrote:
>When I generate text to appear above some music using the <>^\markup
>"mytext" syntax, I don't seem to be able to control the
>outside-staff-priority. In this example despite the second bit of
>markup having a lower outside-staff-priority it appears above the
>first bit.
>
>\version "2.18.0"
>\score {
> {  \once \override TextScript.outside-staff-priority = #1000  <>
> ^\markup "Above the next text please" \once \override
> TextScript.outside-staff-priority = #0  a'4^"below please" }
>}
>
>
>Can anyone suggest why this is happening and if there is a solution
>that doesn't involve using a different sort of syntax for the markup,
>(i.e. not involving the <> trick)? (The final target of all this is
>scores with markup containing encapsulated postscript to create old
>French clavecin ornaments which have to have a low
>outside-staff-priority despite being textScript).

Since both events happen at the same moment in time, you have to use
tweak.

\version "2.18.0"
\score {
 {
<>-\tweak outside-staff-priority #1000
^\markup "Above the next text please"
a'4-\tweak outside-staff-priority #0 ^"below please"
 }
}

--
Mark Knoop

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

outside-staff-priority for markups attached to <>

[Richard Shann]

When I generate text to appear above some music using the <>^\markup
"mytext" syntax, I don't seem to be able to control the
outside-staff-priority. In this example despite the second bit of markup
having a lower outside-staff-priority it appears above the first bit.

\version "2.18.0"
\score {
 {  \once \override TextScript.outside-staff-priority = #1000  <> ^\markup 
"Above the next text please" 
 \once \override TextScript.outside-staff-priority = #0  a'4^"below please"
 }
}


Can anyone suggest why this is happening and if there is a solution that
doesn't involve using a different sort of syntax for the markup, (i.e.
not involving the <> trick)? (The final target of all this is scores
with markup containing encapsulated postscript to create old French
clavecin ornaments which have to have a low outside-staff-priority
despite being textScript).

Richard Shann




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

Re: Repeat volta not at beginning of piece doesn't get initial repeat bar line

[Patrick or Cynthia Karl]

> In lilypond-user Digest, Vol 139, Issue 98 Message: 6, Jay Anderson wrote:

> Date: Thu, 26 Jun 2014 08:53:23 -0700
> From: Jay Anderson 
> To: Patrick or Cynthia Karl 
> Subject: Re: Repeat volta not at beginning of piece doesn't get
>   initial repeat  bar line
> 
> On Thu, Jun 26, 2014 at 8:37 AM, Patrick or Cynthia Karl  
> wrote:
>> Section 1.4 of the Notation Manual says about volta repeats:
>> 
>> volta   The repeated music is not written out but enclosed between 
>> repeat bar lines. If the repeat is at the 
>> beginning of a piece, a repeat bar line is only printed at the end of the
>>   repeat.
>> 
>> But the following snippet does not generate the initial repeat bar line, 
>> apparently because of the "||" bar line.  But the "||" bar line does not 
>> indicate the end of a piece.
>> 
>> I have tried several things to get the inital repeat bar line to appear 
>> without success.  I suspect it's not very difficult.  Can anyone please tell 
>> me how to do it?  And if I'm correct about the problem being caused by the 
>> "||" bar line, the documentation should probably be changed.
>> 
>> \version "2.18.2"
>> 
>> music = \relative b' {
>>a1 a a a
>>\bar "||"
>> 
>>\break
>> 
>>\repeat volta 2 { a4 b c d }
>> }
> 
> You're right that the \bar "||" is overriding the repeat bar. I assume
> you're wanting a double bar before the break. Use \bar ".|:-||"
> instead. You can lookup valid bar strings in bar-line.scm.

Sorry, that doesn't work for me, result is the same.  I assume you're saying to 
replace the \bar "||" with \bar ".|:-||".

I still don't understand why the "||" bar is overriding the repeat bar, as "||" 
doesn't signify end-of-piece so the \repeat volta is not at the beginning of a 
piece so the initial repeat bar line should be printed.


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

Re: Repeat volta not at beginning of piece doesn't get initial repeat bar line

[Jay Anderson]

On Thu, Jun 26, 2014 at 8:37 AM, Patrick or Cynthia Karl  wrote:
> Section 1.4 of the Notation Manual says about volta repeats:
>
> volta   The repeated music is not written out but enclosed between 
> repeat bar lines. If the repeat is at the 
> beginning of a piece, a repeat bar line is only printed at the end of the 
>  repeat.
>
> But the following snippet does not generate the initial repeat bar line, 
> apparently because of the "||" bar line.  But the "||" bar line does not 
> indicate the end of a piece.
>
> I have tried several things to get the inital repeat bar line to appear 
> without success.  I suspect it's not very difficult.  Can anyone please tell 
> me how to do it?  And if I'm correct about the problem being caused by the 
> "||" bar line, the documentation should probably be changed.
>
> \version "2.18.2"
>
> music = \relative b' {
> a1 a a a
> \bar "||"
>
> \break
>
> \repeat volta 2 { a4 b c d }
> }

You're right that the \bar "||" is overriding the repeat bar. I assume
you're wanting a double bar before the break. Use \bar ".|:-||"
instead. You can lookup valid bar strings in bar-line.scm.

-Jay

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

Repeat volta not at beginning of piece doesn't get initial repeat bar line

[Patrick or Cynthia Karl]

Section 1.4 of the Notation Manual says about volta repeats:

volta   The repeated music is not written out but enclosed between 
repeat bar lines. If the repeat is at the beginning 
of a piece, a repeat bar line is only printed at the end of the 
 repeat.

But the following snippet does not generate the initial repeat bar line, 
apparently because of the "||" bar line.  But the "||" bar line does not 
indicate the end of a piece.

I have tried several things to get the inital repeat bar line to appear without 
success.  I suspect it's not very difficult.  Can anyone please tell me how to 
do it?  And if I'm correct about the problem being caused by the "||" bar line, 
the documentation should probably be changed.

\version "2.18.2"

music = \relative b' {
a1 a a a
\bar "||"

\break

\repeat volta 2 { a4 b c d }
}


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

Re: [DOC] 1.3.1 Expressive marks attached to notes, has v.2.16 format

[David Kastrup]

Simon Albrecht  writes:

> Am 26.06.2014 13:33, schrieb David Kastrup:
>> And he's right with that as well...  Have you actually tried it?
>>
> My mistake again. Sorry for being pert and not checking first. I
> wasn’t aware that your parser improvements had gone so far…

Version 2.17.26:

commit c7320b8c6dd5ef813602526c340a3e30c2cc91f7
Author: David Kastrup 
Date:   Sat Aug 31 18:57:09 2013 +0200

Issue 3527: parser.yy: allow "scalar" to be a negative literal number

This makes the syntax of the value for \override (a hardwired syntax
construct which accepts a "scalar") and \tweak (which is a music
function accepting an expression of type "scheme?" possibly ending up
as a negative number) more comparable.


-- 
David Kastrup

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

Re: OT? Error importing Organ xml files made in Musescore

[Son_V]

Here it is ... I can't see no more to do than a copy and paste; in Denemo, or
in Frescocaldi choosing "insert from file" I can get the score, but without
the text and without the brackets.

%% File LilyPond generato da Denemo versione 1.1.4

%%http://www.gnu.org/software/denemo/

\version "2.18.0"

AutoBarline = {}
AutoEndMovementBarline = \bar "|."

% The music follows

MvmntIVoiceI = {
 a'2 c''4 a'\AutoBarline
 g'4. f'8 f'2\AutoBarline
 bes' d''4 bes'\AutoBarline
 a'4. g'8 g'2\AutoBarline
%5
 a'4 bes' c'' ees''\AutoBarline
 d''( c'') bes' a'\AutoBarline
 c''4. c''8 c''2~ \AutoBarline
 c''4 a' bes' g'\AutoBarline
 a'4. a'8 a'2\AutoBarline
%10
 a' bes'4( g')\AutoBarline
 c''2 a'\AutoBarline
 bes' a'4( c'')\AutoBarline
 g'2.( a'4)\AutoBarline
 a'1\AutoBarline
%15
 r\AutoBarline
 r\AutoBarline
 r\AutoBarline
 r\AutoBarline
 c''2 a'~ \AutoBarline
%20
 a'4 a' bes' c''\AutoBarline
 d''4. d''8 d''2\AutoBarline
 ees'' d''~ \AutoBarline
 d''4 d'' c'' bes'\AutoBarline
 bes'4. a'8 a'2\AutoBarline
%25
 a'4 a' a' a'\AutoBarline
 a'2 g'\AutoBarline
 a' a'\AutoBarline
 g'4 g' g' g'\AutoBarline
 bes'2 bes'\AutoBarline
%30
 a'1\AutoBarline
 a' \bar "|."}


MvmntIVoiceII = {
 f'2 e'4 e'\AutoBarline
 d'4. d'8 f'2\AutoBarline
 g' f'4 f'\AutoBarline
 f'4. e'8 e'2\AutoBarline
%5
 f'4 g' a' a'\AutoBarline
 bes'( a') g' f'\AutoBarline
 a'4. a'8 a'2~ \AutoBarline
 a'4 fis' g' d'\AutoBarline
 e'4. e'8 e'2\AutoBarline
%10
 fis' g'\AutoBarline
 a'4( g'2) fis'4\AutoBarline
 g'2 f'\AutoBarline
 f'( e')\AutoBarline
 f'1\AutoBarline
%15
 r\AutoBarline
 r\AutoBarline
 r\AutoBarline
 r\AutoBarline
 a'2 f'~ \AutoBarline
%20
 f'4 f' g' a'\AutoBarline
 bes'4. bes'8 bes'2\AutoBarline
 a' bes'~ \AutoBarline
 bes'4 bes' a' g'\AutoBarline
 g' f' e'2\AutoBarline
%25
 f'4 f' f' f'\AutoBarline
 f'2 e'\AutoBarline
 e' f'\AutoBarline
 f'4 f' ees' ees'\AutoBarline
 d'2 f'\AutoBarline
%30
 f'( e'4 d')\AutoBarline
 e'1 \bar "|."}


MvmntIVoiceIII = {
 c'2 c'4 c'\AutoBarline
 a4. a8 d'2\AutoBarline
 d' bes4 d'\AutoBarline
 c'4. c'8 c'2\AutoBarline
%5
 c'4 d' ees' g'\AutoBarline
 f'( ees') d' f'\AutoBarline
 e'4. e'8 e'2~ \AutoBarline
 e'4 d' d' d'\AutoBarline
 d'4. d'8 dis'2\AutoBarline
%10
 d' d'\AutoBarline
 g a4( d')\AutoBarline
 d'2 d'\AutoBarline
 d'( c')\AutoBarline
 c'1\AutoBarline
%15
 r\AutoBarline
 r\AutoBarline
 r\AutoBarline
 r\AutoBarline
 f'2 f'~ \AutoBarline
%20
 f'4 ees' d' c'\AutoBarline
 bes4. bes8 d'2\AutoBarline
 g' f'~ \AutoBarline
 f'4 f' e' d'\AutoBarline
 d'4. d'8 cis'2\AutoBarline
%25
 d'4 d' c' c'\AutoBarline
 bes2 bes\AutoBarline
 a d'\AutoBarline
 bes4 bes c' c'\AutoBarline
 d'2 d'\AutoBarline
%30
 d'( e'4 f')\AutoBarline
 e'1 \bar "|."}


MvmntIVoiceIV = {
 f2 a4 a\AutoBarline
 d4. d8 d2\AutoBarline
 g g4 g\AutoBarline
 c4. c8 c2\AutoBarline
%5
 f4 f f f\AutoBarline
 bes2 bes4 d'\AutoBarline
 a4. a8 a2~ \AutoBarline
 a4 d g bes\AutoBarline
 a4. a8 a2\AutoBarline
%10
 d g4( f)\AutoBarline
 ees2 d\AutoBarline
 g d4( a,)\AutoBarline
 bes,2( c)\AutoBarline
 f1\AutoBarline
%15
 r\AutoBarline
 r\AutoBarline
 r\AutoBarline
 r\AutoBarline
 f2 f~ \AutoBarline
%20
 f4 f f f\AutoBarline
 bes,4. bes,8 bes,2~ \AutoBarline
 bes, bes4( a)\AutoBarline
 g g g g\AutoBarline
 a a a2\AutoBarline
%25
 d4 d d d\AutoBarline
 d2 d\AutoBarline
 d d\AutoBarline
 ees4 ees ees ees\AutoBarline
 g2 g\AutoBarline
%30
 a1\AutoBarline
 a \bar "|."}


MvmntIVoiceV = {
 a'2( c''4 a'\AutoBarline
 d''2 f''4 d''\AutoBarline
 c'') a'( c'' ees''\AutoBarline
\AutoBarline
%5
 g'2) a'4( c''\AutoBarline
 f'2 g'4 a'\AutoBarline
 bes' a' g' f'\AutoBarline
 f' d' e' g')\AutoBarline
 a'2 c''4 a'\AutoBarline
%10
 g'4. f'8 f'2\AutoBarline
 bes' d''4 bes'\AutoBarline
 4. 8 2\AutoBarline
 a'4 bes' c'' ees''\AutoBarline
\AutoBarline
%15
 r1\AutoBarline
 r\AutoBarline
 r\AutoBarline
 r\AutoBarline
 r\AutoBarline
%20
 r\AutoBarline
 r

Re: [DOC] 1.3.1 Expressive marks attached to notes, has v.2.16 format

[Simon Albrecht]

Am 26.06.2014 13:33, schrieb David Kastrup:

And he's right with that as well...  Have you actually tried it?

My mistake again. Sorry for being pert and not checking first. I wasn’t 
aware that your parser improvements had gone so far…


Best regards,
Simon

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

Re: [DOC] 1.3.1 Expressive marks attached to notes, has v.2.16 format

[David Kastrup]

Simon Albrecht  writes:

> Am 26.06.2014 09:39, schrieb Pierre Perol-Schneider:
>> Hi James,
>> Sorry, I should have written "syntax" instead of "format"
>>
>> 2014-06-26 9:27 GMT+02:00 James :
>>
>>
>>> Can you be a bit more specific as I don't understand what you are stating?
>>>
>> 'Creating a delayed turn'
>> ...
>> \once \override AccidentalSuggestion #'outside-staff-priority = ##f
>> \once \override AccidentalSuggestion #'avoid-slur = #'inside
>> \once \override AccidentalSuggestion #'font-size = #-3
>> \once \override AccidentalSuggestion #'script-priority = #-1
>> ...
>>
>> should be :
>> ...
>> \once \override AccidentalSuggestion.outside-staff-priority = ##f
>> \once \override AccidentalSuggestion.avoid-slur = #'inside
>> \once \override AccidentalSuggestion.font-size = #-3
>> \once \override AccidentalSuggestion.script-priority = #-1
>> ...
>>
>> or even :
>> ...
>> \once \override AccidentalSuggestion.font-size = -3
>> \once \override AccidentalSuggestion.script-priority = -1
> Attention: this only works with non-negative numbers as the - is
> parsed as a post event identifier, not as a minus. So it’s still
> necessary to spell out the hash sign for negative numbers.
> Else you’re certainly right.

And he's right with that as well...  Have you actually tried it?

-- 
David Kastrup

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

Re: [DOC] 1.3.1 Expressive marks attached to notes, has v.2.16 format

[Simon Albrecht]

So sorry, wrong list…

Am 26.06.2014 12:53, schrieb Simon Albrecht:


Am 26.06.2014 09:39, schrieb Pierre Perol-Schneider:


\once \override AccidentalSuggestion #'outside-staff-priority = ##f
\once \override AccidentalSuggestion #'avoid-slur = #'inside
\once \override AccidentalSuggestion #'font-size = #-3
\once \override AccidentalSuggestion #'script-priority = #-1
...

should be :
...
\once \override AccidentalSuggestion.outside-staff-priority = ##f
\once \override AccidentalSuggestion.avoid-slur = #'inside
\once \override AccidentalSuggestion.font-size = #-3
\once \override AccidentalSuggestion.script-priority = #-1
...

or even :
...
\once \override AccidentalSuggestion.font-size = -3
\once \override AccidentalSuggestion.script-priority = -1
Attention: this only works with non-negative numbers as the - is 
parsed as a post event identifier, not as a minus. So it’s still 
necessary to spell out the hash sign for negative numbers.

Else you’re certainly right.

Best, Simon

(I added this as a comment in the issue tracker, also)

___
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: [DOC] 1.3.1 Expressive marks attached to notes, has v.2.16 format

[Simon Albrecht]

Am 26.06.2014 09:39, schrieb Pierre Perol-Schneider:

Hi James,
Sorry, I should have written "syntax" instead of "format"

2014-06-26 9:27 GMT+02:00 James :



Can you be a bit more specific as I don't understand what you are stating?


'Creating a delayed turn'
...
\once \override AccidentalSuggestion #'outside-staff-priority = ##f
\once \override AccidentalSuggestion #'avoid-slur = #'inside
\once \override AccidentalSuggestion #'font-size = #-3
\once \override AccidentalSuggestion #'script-priority = #-1
...

should be :
...
\once \override AccidentalSuggestion.outside-staff-priority = ##f
\once \override AccidentalSuggestion.avoid-slur = #'inside
\once \override AccidentalSuggestion.font-size = #-3
\once \override AccidentalSuggestion.script-priority = #-1
...

or even :
...
\once \override AccidentalSuggestion.font-size = -3
\once \override AccidentalSuggestion.script-priority = -1
Attention: this only works with non-negative numbers as the - is parsed 
as a post event identifier, not as a minus. So it’s still necessary to 
spell out the hash sign for negative numbers.

Else you’re certainly right.

Best, Simon

(I added this as a comment in the issue tracker, also)l

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

Weird spacing related to barlines

[Phil Holmes]

> I'm not top posting.

Using the gmane interface again, to ensure this gets through.

I'm currently typesetting quite a lot of music from the late 1500's, using 
mensural notation.  With this, it's normal to use

\remove "Default_bar_line_engraver"

to get the closest spacing possible.  However, the down-side is that lines 
don't break.  I discovered that this can be overcome with a simple \bar"" 
early in the music.  Today, I tried to find out how this affected the 
spacing.  It seems quite odd.

With the music below, we see the first block of notes tightly spaced.  
However, without the \bar these run off the side of the page.  Using 
\bar "" to break them, we see the next set of notes grouped into sections 
of 8 notes: it appears that where the end of a measure is mid note, extra 
space is added.  Don't understand.  If I change the pattern of notes so 
that measures always end between notes, the effect disappears.  If I then 
use a wider bar glyph, all the notes are spaced more widely and we still 
see slight evidence of the eight-note grouping.

Can anyone explain what's going on here?

\score {
  \new MensuralStaff {
\repeat unfold 30 { c''4 c''2 c''4 } c''1 ^"\bar" \bar"" 
\repeat unfold 40 { c''4 c''2 } 
c''1 ^"Pattern" \repeat unfold 40 { c''4 c''2 c''4 } c''1 ^"\bar || " 
\bar"||" 
\repeat unfold 40 { c''4 c''2 } 
c''1 ^"Pattern" \repeat unfold 40 { c''4 c''2 c''4 } 
  }
  \layout {
ragged-right-last = ##t
indent = 0.0
  \context {
\Score
  \override SpacingSpanner #'spacing-increment = #0
\remove "Default_bar_line_engraver"
  }
  }
}



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

Re: Sloped/Angled ottava spanner

[Pierre Perol-Schneider]

2014-06-26 4:15 GMT+02:00 Javier Ruiz-Alma :


> How does one angle an ottava (see attached)
>

See attached,
HTH
Pierre
\version "2.18.0"
\relative c'' {
  \override Staff.OttavaBracket.stencil = #ly:line-spanner::print
  \override Staff.OttavaBracket.bound-details =
#`((left . ((Y . 0)
(attach-dir . ,LEFT)
(padding . 0)
(stencil-align-dir-y . ,CENTER)))
   (right . ((Y . 5)
 (padding . 0)
 (attach-dir . ,RIGHT)
 (text . ,(make-draw-dashed-line-markup (cons 0 -1.2))
  \override Staff.OttavaBracket.left-bound-info =
 #ly:line-spanner::calc-left-bound-info-and-text
  \override Staff.OttavaBracket.right-bound-info =
 #ly:line-spanner::calc-right-bound-info
  \ottava #1
  c1
  c1
}___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user