Re: Hide time signature in final partial measure

[Thomas Liggett]

On Sat, 13 Apr 2019 at 18:40, Michael Gerdau  wrote:
>
> Hi Thomas,
>
> just realized, I did not answer your original question.
>
> If you want the TimeSignature change and just not show it, you need to \omit 
> it in the Voice instead of the NullVoice.
>
> Kind regards,
> Michael
> --
> Michael Gerdau email: m...@qata.de
> GPG-keys available on request or at public keyserver

Hi Michael,

Thanks for your help – it pointed me in the direction of the manual in
which I discovered that NullVoice isn’t intended to be used for a
global-type voice (with time signatures, baronies etc.) but rather
just for aligning lyrics. So, as you say, replacing NullVoice with
Voice produces the expected behaviour.

Kind regards,
Thomas

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

Re: warning message - missing slur

[MING TSANG]

 Lukas-Fabian, Ralph, Budanov and Ben:
Thank you all for the solution.
Ming.On Sunday, April 14, 2019, 8:18:42 a.m. EDT, Ralph Palmer 
 wrote:  
 
 On Sun, Apr 14, 2019 at 4:33 AM Lukas-Fabian Moser  wrote:

  

That's not true anymore: In recent versions (starting at some point in the 
2.19.xx series), slurs can be assigned a "name" allowing them to be referenced, 
and in particular, nested (cf. 
http://lilypond.org/doc/v2.19/Documentation/changes/index.html):

Thanks so much for this link, Lukas! Somehow, I had missed that documentation.
All the best, 
Ralph

-- 
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com  ___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Adding a new accidental style

[Thomas Morley]

Am So., 14. Apr. 2019 um 17:22 Uhr schrieb Edward Lilley :
>
> Dear all,
>
> I am trying extend Lilypond in Scheme to add a new accidental
> style. What I am currently stuck on is how to add a new item to the
> "accidental-styles" alist in such a way that it is visible to the
> \accidentalStyle command.
>
> I have a file called "hist-accidentals.scm" that contains the following:
>
> > (define-public (hist-accidental-rule context pitch barnum measurepos)
> >   "An accidental rule that only typesets sharps and flats, indicating
> >   relative alteration compared to the key signature."
> >   (let* ((keysig (ly:context-property context 'localAlterations))
> >   (entry (find-pitch-entry keysig pitch #t #t)))
> >   (if (not entry)
> >   (cons #f #f)
> >   (let* ((global-entry (find-pitch-entry keysig pitch #f #f))
> >   (key-acc (key-entry-alteration global-entry))
> >   (acc (ly:pitch-alteration pitch))
> >   (entrymp (key-entry-measure-position entry))
> >   (entrybn (key-entry-bar-number entry)))
> >   (cons #f (not (or (equal? acc key-acc)
> >   (and (equal? entrybn barnum) (equal?
> >   entrymp measurepos)
> >
> > (set! accidental-styles
> > (cons hist #f
> > (Staff ,(make-accidental-rule 'same-octave 0))
> > (Staff ,(make-accidental-rule 'same-octave 1)
> > hist-accidental-rule)))
> > accidental-styles))
>
> (currently the contents of "hist-accidental-rule" is just a copy of the
> "teaching" accidental style)
>
> At the top of the relevant lilypond file, I load the scheme file with
>
> > #(load "hist-accidentals.scm")
>
> But when I come to write
>
> > \accidentalStyle hist
>
> later on, lilypond complains with "warning: unknown accidental style:
> hist". How do I modify variables defined using "define-public"? Or, what
> should I be doing instead?
>
> Thanks,
> Edward

Hi,

please attach the file in future: From here it looks like the syntax
is messed up for brackets/semiquotes and unquotes.
It's not unheard some email-client done such things, though ...

Anyway, below should do:

(set! accidental-styles
  (cons
`(hist #f
   (Staff ,(make-accidental-rule 'same-octave 0))
   (Staff ,(make-accidental-rule 'same-octave 1)
  ,hist-accidental-rule))
accidental-styles))

Cheers,
  Harm

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

Adding a new accidental style

[Edward Lilley]

Dear all,

I am trying extend Lilypond in Scheme to add a new accidental
style. What I am currently stuck on is how to add a new item to the
"accidental-styles" alist in such a way that it is visible to the
\accidentalStyle command.

I have a file called "hist-accidentals.scm" that contains the following:

> (define-public (hist-accidental-rule context pitch barnum measurepos)
>   "An accidental rule that only typesets sharps and flats, indicating
>   relative alteration compared to the key signature."
>   (let* ((keysig (ly:context-property context 'localAlterations))
>   (entry (find-pitch-entry keysig pitch #t #t)))
>   (if (not entry)
>   (cons #f #f)
>   (let* ((global-entry (find-pitch-entry keysig pitch #f #f))
>   (key-acc (key-entry-alteration global-entry))
>   (acc (ly:pitch-alteration pitch))
>   (entrymp (key-entry-measure-position entry))
>   (entrybn (key-entry-bar-number entry)))
>   (cons #f (not (or (equal? acc key-acc)
>   (and (equal? entrybn barnum) (equal?
>   entrymp measurepos)
> 
> (set! accidental-styles
> (cons hist #f
> (Staff ,(make-accidental-rule 'same-octave 0))
> (Staff ,(make-accidental-rule 'same-octave 1)
> hist-accidental-rule)))
> accidental-styles))

(currently the contents of "hist-accidental-rule" is just a copy of the
"teaching" accidental style)

At the top of the relevant lilypond file, I load the scheme file with

> #(load "hist-accidentals.scm")

But when I come to write

> \accidentalStyle hist

later on, lilypond complains with "warning: unknown accidental style:
hist". How do I modify variables defined using "define-public"? Or, what
should I be doing instead?

Thanks,
Edward



-- 

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

Re: rest + fermata

[Martin Tarenskeen]

On Sun, 14 Apr 2019, Malte Meyn wrote:


 r1\fermata works fine, R1\fermata doesn't. No fermata sign is printed.
 Is this a bug?

That’s the third time in a few weeks that someone asks why that doesn’t work 
at a list/forum/… that I read.


Looks like I should continue my work on issue 5486 
(https://sourceforge.net/p/testlilyissues/issues/5486/) and maybe find a way 
that \fermataMarkup isn’t needed anymore and R1\fermata works instead …



Everyone thanks for the easy solution.

Easy but ugly. Would be nice if R1\fermata would simply work. No big deal 
though, no need to hurry to make this possible,


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

Re: rest + fermata

[Malte Meyn]

Am 14.04.19 um 13:38 schrieb Martin Tarenskeen:


Hi,

This is strange:

%%% start of tiny example

\version "2.19.83"
{
   r1\fermata
   R1\fermata
}

%%% end of tiny example

r1\fermata works fine, R1\fermata doesn't. No fermata sign is printed.
Is this a bug?

That’s the third time in a few weeks that someone asks why that doesn’t 
work at a list/forum/… that I read.


Looks like I should continue my work on issue 5486 
(https://sourceforge.net/p/testlilyissues/issues/5486/) and maybe find a 
way that \fermataMarkup isn’t needed anymore and R1\fermata works instead …


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

Re: warning message - missing slur

[Ralph Palmer]

On Sun, Apr 14, 2019 at 4:33 AM Lukas-Fabian Moser  wrote:

> That's not true anymore: In recent versions (starting at some point in the
> 2.19.xx series), slurs can be assigned a "name" allowing them to be
> referenced, and in particular, nested (cf.
> http://lilypond.org/doc/v2.19/Documentation/changes/index.html):
>

Thanks so much for this link, Lukas! Somehow, I had missed that
documentation.

All the best,

Ralph


-- 
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: rest + fermata

[Andrew Bernard]

Hi Martin,

Three identical answers - that's fascinating, It must be due to global
distribution delays on the list.

cheerio!

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

Re: rest + fermata

[Phil Holmes]

- Original Message - 
From: "Martin Tarenskeen" 
To: "lilypond-user mailinglist" ; "bug-lilypond 
mailinglist" 

Sent: Sunday, April 14, 2019 12:38 PM
Subject: rest + fermata




Hi,

This is strange:

%%% start of tiny example

\version "2.19.83"
{
  r1\fermata
  R1\fermata
}

%%% end of tiny example

r1\fermata works fine, R1\fermata doesn't. No fermata sign is printed.
Is this a bug?

--

MT


See 
http://lilypond.org/doc/v2.19/Documentation/notation/expressive-marks-attached-to-notes


\fermataMarkup

--
Phil Holmes 



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

Re: warning message - missing slur

[Ben]

On 4/14/2019 4:33 AM, Lukas-Fabian Moser wrote:


I've done two things. First, I've rewritten your code in a way that's 
easier for me to read.
Second, and more to the point, I've changed the "outside" set of 
slurs to phrasing slurs. AFAIK, you can't nest regular slurs. Please 
take a look at 
 .


That's not true anymore: In recent versions (starting at some point in 
the 2.19.xx series), slurs can be assigned a "name" allowing them to 
be referenced, and in particular, nested (cf. 
http://lilypond.org/doc/v2.19/Documentation/changes/index.html):



\version "2.19.83"
\language "english"

\fixed c'
{ <<
  {
    f4 e8 c8~( c4 e8\=inner( f8\inner) ) | % the \( and \) are 
phrasing slurs.

  }
  \\
  {
    f4 e8 c~ 4~ 4 ||
  }
  >>
  }

Though I admit that the layout engine handles the phrasing slur better 
in this specific situation.


By the way, it's even possible to do

\version "2.19.82"

\fixed c' {
  c\=1( d e^\=2( f\=1) g a\=2)
}

IMHO this feature alone is worth the (negligible) trouble of switching 
to recent development versions.


Best
Lukas


Absolutely agree. The whole name/ID slur config is a huge game changer. 
So happy that we have it! :)



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

Re: rest + fermata

[Thomas Morley]

Am So., 14. Apr. 2019 um 13:38 Uhr schrieb Martin Tarenskeen
:
>
>
> Hi,
>
> This is strange:
>
> %%% start of tiny example
>
> \version "2.19.83"
> {
>r1\fermata
>R1\fermata
> }
>
> %%% end of tiny example
>
> r1\fermata works fine, R1\fermata doesn't. No fermata sign is printed.
> Is this a bug?

Hi,

see
http://lilypond.org/doc/v2.19/Documentation/notation/writing-rests#index-_005cfermataMarkup-1
leading to:
{
   r1\fermata
   R1\fermataMarkup
}

No bug ;)

Cheers,
  Harm

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

Re: rest + fermata

[Andrew Bernard]

Hi Martin,

   R1^\fermataMarkup

It's special. Refer to the NR.

Andrew


On Sun, 14 Apr 2019 at 21:38, Martin Tarenskeen 
wrote:

>
> Hi,
>
> This is strange:
>
> %%% start of tiny example
>
> \version "2.19.83"
> {
>r1\fermata
>R1\fermata
> }
>
> %%% end of tiny example
>
> r1\fermata works fine, R1\fermata doesn't. No fermata sign is printed.
> Is this a bug?
>
> --
>
> MT
>
> ___
> bug-lilypond mailing list
> bug-lilyp...@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

rest + fermata

[Martin Tarenskeen]

Hi,

This is strange:

%%% start of tiny example

\version "2.19.83"
{
  r1\fermata
  R1\fermata
}

%%% end of tiny example

r1\fermata works fine, R1\fermata doesn't. No fermata sign is printed.
Is this a bug?

--

MT

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

Re: warning message - missing slur

[Lukas-Fabian Moser]

I've done two things. First, I've rewritten your code in a way that's 
easier for me to read.
Second, and more to the point, I've changed the "outside" set of slurs 
to phrasing slurs. AFAIK, you can't nest regular slurs. Please take a 
look at 
 .


That's not true anymore: In recent versions (starting at some point in 
the 2.19.xx series), slurs can be assigned a "name" allowing them to be 
referenced, and in particular, nested (cf. 
http://lilypond.org/doc/v2.19/Documentation/changes/index.html):



\version "2.19.83"
\language "english"

\fixed c'
{ <<
  {
    f4 e8 c8~( c4 e8\=inner( f8\inner) ) | % the \( and \) are 
phrasing slurs.

  }
  \\
  {
    f4 e8 c~ 4~ 4 ||
  }
  >>
  }

Though I admit that the layout engine handles the phrasing slur better 
in this specific situation.


By the way, it's even possible to do

\version "2.19.82"

\fixed c' {
  c\=1( d e^\=2( f\=1) g a\=2)
}

IMHO this feature alone is worth the (negligible) trouble of switching 
to recent development versions.


Best
Lukas

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