Simon, David and Thorsten,
Thanks for your replies!
I just finished my score with the workaround, but of course Thorsten's
would have been the easier way. However, if I understand this correctly,
this will only work if one doesn't customise the notehead itself, right?
So, maybe this could be i
Menu Jacques,
Trying to compile your code.
Not successful for the moment.
Shall try later tonight.
Mark
From: Menu Jacques [mailto:imj-...@bluewin.ch]
Sent: Tuesday, July 10, 2018 2:17 PM
To: Mark Stephen Mrotek
Cc: Menu Jacques ; Lilypond-User Mailing List
Subject: Re: Chord \cro
Robert Schmaus wrote
> The improvisation switch works well if one comments out the \set ... line.
Hi Robert,
You won't believe it, but everything works "as expected":
\improvisationOn actually does set the NoteHead.style to #'slash, but in
your custom case, this #'slash will be overwritten again
Robert Schmaus writes:
> Hi David,
>
> you are right, of course - here it is:
>
> \version "2.19.35"
>
> #(define mydrums '(
> (bassdrumdefault #f -3)
> (snare default #f 1)
> (hihat cross #f
On 10.07.2018 23:16, Menu Jacques wrote:
But in the image from Finale 2014, all pitched notes occur in the
second staff, and I tried to achieve the same.
What do you mean? They are cross-staff chords, so some of the note heads
are on the upper staff.
LilyPond doesn’t currently have any notion
On 10.07.2018 23:33, Robert Schmaus wrote:
\set DrumStaff.drumStyleTable = #(alist->hash-table mydrums)
It makes lots of sense to set this variable in a \with or layout block,
since it’s supposed to affect the context right from the beginning; I
seem to recall that it sometimes makes a di
On 10.07.2018 21:02, Robert Schmaus wrote:
I'm setting up a custom drumStyleTable as described in the
documentation here:
http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion#custom-percussion-staves
So far, so good, but I've noticed that \improvisationOn/Off
Hi David,
you are right, of course - here it is:
\version "2.19.35"
#(define mydrums '(
(bassdrum default #f -3)
(snare default #f 1)
(hihat cross #f 1)
))
\score {
\new DrumStaff
Hello Mark,
That’s the example I was mentioning.
But in the image from Finale 2014, all pitched notes occur in the second staff,
and I tried to achieve the same.
JM
> Le 10 juil. 2018 à 21:59, Mark Stephen Mrotek a écrit :
>
> Menu Jackues
>
> Perhaps this can direct you
> http://lilypond
Robert Schmaus writes:
> Dear Ponderers,
>
> I'm setting up a custom drumStyleTable as described in the
> documentation here:
> http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion#custom-percussion-staves
>
> So far, so good, but I've noticed that \improvisationOn/
Dear Ponderers,
I'm setting up a custom drumStyleTable as described in the documentation
here:
http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion#custom-percussion-staves
So far, so good, but I've noticed that \improvisationOn/Off seems to
stop working with th
>
> -- Forwarded message --
> From: Reilly Farrell
> To: lilypond-user
> Date: Fri, 29 Jun 2018 23:37:20 -0700
> Subject: chord names - C Delta 7 chord?
> Hi All,
>
> I'm looking for a solution for printing a C Delta 7 chord name (so that 7
> prints clearly after the delta symbol)
Dear Ponderers,
I'm setting up a custom drumStyleTable as described in the documentation
here:
http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-percussion#custom-percussion-staves
So far, so good, but I've noticed that \improvisationOn/Off seems to
stop working with th
Am 10.07.2018 um 16:56 schrieb Urs Liska:
Am 10.07.2018 um 16:48 schrieb David Kastrup:
Urs Liska writes:
Hi all,
after completing most of the work of reviewing the scholarly.annotate
module I realize that it (presumably one small change) is a total
performance killer, and I need some hel
Am 10.07.2018 um 16:48 schrieb David Kastrup:
Urs Liska writes:
Hi all,
after completing most of the work of reviewing the scholarly.annotate
module I realize that it (presumably one small change) is a total
performance killer, and I need some help tracking it down.
Well, one thing just j
Am 10.07.2018 um 12:22 schrieb David Kastrup:
Urs Liska writes:
after completing most of the work of reviewing the scholarly.annotate
module I realize that it (presumably one small change) is a total
performance killer, and I need some help tracking it down.
Quadratic behavior or worse.
Th
Urs Liska writes:
> Hi all,
>
> after completing most of the work of reviewing the scholarly.annotate
> module I realize that it (presumably one small change) is a total
> performance killer, and I need some help tracking it down.
Well, one thing just jumping out at me is
((process-acknowl
On 2018-07-10 02:56, Urs Liska wrote:
The situation is that a three-page score that takes ~ 2.1 seconds
without the engraver and with the old state of the engraver now needs
5.8 seconds. And a >20 page score that I recall using around 20-25
seconds now needs 57 - so that's obviously nothing to ig
Urs Liska writes:
> after completing most of the work of reviewing the scholarly.annotate
> module I realize that it (presumably one small change) is a total
> performance killer, and I need some help tracking it down.
Quadratic behavior or worse.
> Observations:
>
> * The obvious stage of slo
Hi all,
after completing most of the work of reviewing the scholarly.annotate
module I realize that it (presumably one small change) is a total
performance killer, and I need some help tracking it down.
There are a few things I have changed (had to), and one in particular
seemed suspicious t
Typo: \fixed c' should be \fixed $amb1, plus I forgot to remove the flags:
\version "2.19.82"
amb = #(define-music-function (parser location arg mus) (integer? ly:music?)
(let ((amb1 (ly:make-pitch 0 0 0))
(amb2 (ly:make-pitch 0 (abs arg) 0)))
#{
\fixed $amb1
<<
21 matches
Mail list logo
