e 30)
> { c' }
> }
> \book {
> \markup "10"
> #(set-global-staff-size 10)
> { c' }
> }
> \book {
> \markup "10"
> #(set-global-staff-size 10)
> { c' }
> }
> ```
I've always just used it at top-level - this works as expected.
```
#(set-global-staff-size 30)
\book {
\markup "30"
{ c' }
}
#(set-global-staff-size 10)
\book {
\markup "10"
{ c' }
}
#(set-global-staff-size 20)
\book {
\markup "20"
{ c' }
}
```
--
Mark Knoop
nd arrow)
What's missing is a way to align them to the same Y position - could an
engraver do this?
--
Mark Knoop
mpilation error, so I wondered if the
> merge request I created just now would help:
> https://gitlab.com/lilypond/lilypond/-/merge_requests/2070 . With that
> patch, it does compile successfully, but I get a very concerning error
> when invoking make test-baseline without any arguments:
--
Mark Knoop
Following up on this post from the user list:
At 11:24 on 10 Feb 2023, Knute Snortum wrote:
> On Fri, Feb 10, 2023 at 10:48 AM Mark Knoop wrote:
>> At 10:38 on 10 Feb 2023, Knute Snortum wrote:
>>> I have run into something in LilyPond that's annoying -- it probably
>&g
ing with
> `\` (except in a string). This might even include `\1` and friends.
>From these examples at least, it would seem to embolden stuff which
requires an argument (i.e. music functions and markup functions), not
articulations which don't require a subsequent argument. There'
At 23:43 on 23 Jul 2021, Owen Lamb wrote:
Hi all! A few updates from the SMuFL front.
You have mapped both noteheads.s1triangle and noteheads.s2triangle to
noteheadTriangleHalf. Perhaps s2triangle should be noteheadTriangleQuarter?
--
Mark Knoop
At 15:45 on 15 Nov 2020, Jonas Hahnfeld wrote:
> Am Sonntag, den 15.11.2020, 15:13 + schrieb Mark Knoop:
>> At 15:08 on 15 Nov 2020, Jonas Hahnfeld wrote:
>>> Am Sonntag, den 15.11.2020, 10:04 -0500 schrieb Kieren MacMillan:
>>>> Hi all,
>>>>
&g
as:
\override Score.BarNumber.self-alignment-X = #1
would be equivalent to
\override Score.BarNumber.self-alignment-X = #(1 1 1)
--
Mark Knoop
to have bar numbers centred within the
>> measure?
>
> I think that's a totally different topic and not actually related to
> positioning the usual bar numbers that are above the bar line in all
> scores that I ever played from.
Measure-centred bar numbers are fairly standard in film scores.
--
Mark Knoop
fecting snippets, I see that I
>should run the makelsr script and add the resulting files.
>
>This, however, was not done in the last patch adding a snippet:
>
>commit 5944d20489bb5b8e4c4907fa3b3bcae9ec275ccb
>Author: Mark Knoop
>Date: Thu Sep 8 18:56:16 2016 +0100
I s
est something before sending an email
asserting things with great confidence? Or RTFM?
--
Mark Knoop
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
is
>implementation should also allow additional flexibility with ossia
>and divisi staves.
>
>http://codereview.appspot.com/308910043
>
>
>---
>
>Sent from sourceforge.net because you indicated interest in
><https://sourceforge.net/p/testlilyissues/issues/4949/>
&g
At 13:56 on 19 Aug 2016, David Kastrup wrote:
>Mark Knoop writes:
>> Just trying out some more ideas for the keep-alive-together-engraver.
>> How do I use the Guile max/min functions on a scheme list in C++? I
>> have tried this:
>
>Well...
>
>
At 11:37 on 19 Aug 2016, Carl Sorensen wrote:
>>From: Mark Knoop
>>
>>Just trying out some more ideas for the keep-alive-together-engraver.
>>How do I use the Guile max/min functions on a scheme list in C++? I
>>have tried this:
>>
>>SCM this_layer =
= scm_apply_0 (scm_max, this_layer);
}
...but the compiler returns:
error: cannot convert 'scm_unused_struct* (*)(SCM, SCM) {aka
scm_unused_struct* (*)(scm_unused_struct*, scm_unused_struct*)}' to
'SCM {aka scm_unused_struct*}' for argument '1' to 'scm_
th git-cl - it seems to
have worked, but the script borked with an error:
IOError: [Errno socket error] [Errno -5] No address associated
with hostname
The sourceforge website has had some problems today, so it might be
related to that. Anyway, the issue is at:
https://sourceforge.net/p/testlil
At 14:21 on 01 Aug 2016, Phil Holmes wrote:
>If you create an account on SourceForge and let us have the details,
>I'll add you to the tracker users.
username: mkdev
email: m...@opus11.net
Thanks!
--
Mark Knoop
___
lilypond-devel m
At 13:22 on 01 Aug 2016, Simon Albrecht wrote:
>Am 01.08.2016 um 10:49 schrieb Mark Knoop:
> > James, could you test this patch for review please?
>
> Please create a tracker issue following the CG instructions, with
> yourself as owner and Patch:new, and upload the p
At 21:21 on 31 Jul 2016, David Kastrup wrote:
>Mark Knoop writes:
>> OK. Attached are two patches and a test case. The patches are two
>> alternate methods of approaching the problem.
>>
>> Keep a staff alive with multiple layers
>> -
On 29/07/16 18:09, Mark Knoop wrote:
> I still think the easiest and most logical way to do this is with
> the Keep_alive_together_engraver.
>
> Prior to the fix for issue 3518 (support for temporary divisi
> staves), the Keep_alive_together_engraver was useful only in
> French
At 11:06 on 30 Jul 2016, James Lowe wrote:
>On 29/07/16 18:09, Mark Knoop wrote:
>> At 16:41 on 29 Jul 2016, David Kastrup wrote:
>>> I remember that the decision to sort the remove-layers numerically
>>> was based on the desire not to have logical circles: with thi
the divisi-staves regtest.
So perhaps a new property could be useful for solving this problem?
Thoughts?
--
Mark Knoop
\version "2.19.13"
\header {
texidoc = "The @code{VerticalAxisGroup.remove-layer}
property can be used for typesetting temporary divisi staves where
the swi
At 14:11 on 29 Jul 2016, David Kastrup wrote:
>Mark Knoop writes:
>> At 11:26 on 29 Jul 2016, David Kastrup wrote:
>>>Mark Knoop writes:
>>>> At 22:09 on 28 Jul 2016, David Kastrup wrote:
>>>>>What you are looking for, however, is a
>>
At 11:26 on 29 Jul 2016, David Kastrup wrote:
>Mark Knoop writes:
>> At 22:09 on 28 Jul 2016, David Kastrup wrote:
>>>What you are looking for, however, is a
>>>class of simple omission problems. Maybe we can solve this
>>>completely differently? Like us
At 22:09 on 28 Jul 2016, David Kastrup wrote:
>Mark Knoop writes:
>> I'm sorry, I am trying to progress this and respond to your
>> suggestions, but it would be nice to receive some proper criticism of
>> my (working) code which amounts to more than just "I don
material at each remove-layer.
Attached is I think what you want.
Ideally we wouldn't be moving pitches to the violIandIItrickyness
and violIIIandIVtrickyness variables, you could try setting
keepAliveInterfaces to something else to trigger "interest" instead.
--
Mark Knoop
\version
At 21:03 on 28 Jul 2016, David Kastrup wrote:
>Mark Knoop writes:
>> I'm also unclear as to why you feel that this is unsuitable to be
>> done by the Keep_alive_together_engraver without further nesting.
>> After all, the documentation for this engraver states:
>>
At 19:49 on 28 Jul 2016, David Kastrup wrote:
>Mark Knoop writes:
>> At 17:43 on 28 Jul 2016, David Kastrup wrote:
>>>At any rate, I think the principal problem is that the
>>>Keep_alive_together_engraver is desired to keep the marks context
>>>alive with
At 17:43 on 28 Jul 2016, David Kastrup wrote:
>Mark Knoop writes:
>> OK, here's a patch using only the remove-layer property with these
>> values:
>>
>> - #f: ignored by Keep_alive_together_engraver
>> - -1: kept alive by any other layer
>
>Isn'
At 10:52 on 28 Jul 2016, Mark Knoop wrote:
>At 09:59 on 28 Jul 2016, David Kastrup wrote:
>>It seems like an ad-hoc band-aid with limited utility. I'd rather see
>>something covering more use cases.
>
>Regardless of the merits of this solution, I not sure about
At 09:59 on 28 Jul 2016, David Kastrup wrote:
>Mark Knoop writes:
>> At 06:21 on 28 Jul 2016, James Lowe wrote:
>>>On 27/07/16 17:39, Mark Knoop wrote:
>>>> Once again further to this thread (see below) I've attempted a
>>>> patch (attached)
Hi James,
At 06:21 on 28 Jul 2016, James Lowe wrote:
>Hello Mark,
>
>On 27/07/16 17:39, Mark Knoop wrote:
>> Once again further to this thread (see below) I've attempted a patch
>> (attached) to the Keep_alive_together_engraver which makes this
>> work, at least f
tring (or list)
instead of an integer.
I don't have an account on the issue tracker and so haven't used the
git-cl script.
Regards, Mark
At 11:43 on 26 Jul 2016, Mark Knoop wrote:
>Further to this thread from 2013
>(https://lists.gnu.org/archive/html/lilypond-user/2013-09/msg00857.
s }
>}
> }
>}
>
>I've tried to write a function that replaces all the tag ... stuff, so
>that all I need in the music is
>
>\MensFict fis4
MensFict =
#(define-music-function (note) (ly:music?)
#{
\tag #'mens {
<>^\markup { \musicglyph #"ac
ys returns an absolute, slashified path
Now is-absolute? is not used anymore by LilyPond itself.
--
Mark Knoop
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
nst [with T = double]: Assertion `!is_empty
()' failed. Aborted (core dumped)
%}
\music
}
--
Mark Knoop
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
At 14:41 on 30 Aug 2015, Phil Holmes wrote:
>There's lots of differences, presumably down to font changes,
Also sans \bold and \italic do not seem to work in font-family-override.ly
--
Mark Knoop
___
lilypond-devel mailing list
lilypond-devel
g piece here has no effect,
% even without a bookpart level header
\header { piece = "Movement 3" }
\repeat unfold 400 e'1
}
}
}
--
Mark Knoop
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
strina taken from an edition which tries
>transforming the original in sort of modern notation.
That is an interesting case. It would seem to me that ideally there
should be two properties (perhaps three?) to control this behaviour for
notes, rests and multimeasure rests
At 15:43 on 24 Mar 2015, Kevin Barry wrote:
>On Tue, Mar 24, 2015 at 2:38 PM, Mark Knoop wrote:
>
>> { \time 2/4 c'4 c'1 c'4 } % 3 bars, 2nd of which is empty
>>
>> { \time 2/4 c'4 c'2 c'4 } % 2 bars, neither of which is empty
>>
>
At 12:31 on 24 Mar 2015, Kevin Barry wrote:
>On Tue, Mar 24, 2015 at 9:01 AM, Mark Knoop wrote:
>>>>At 18:16 on 23 Mar 2015, Mark Knoop wrote:
>>>Barlines disappear when skipBars is true and a note duration
>>>continues over the bar. I don't think this
he part where the
>corresponding commands are actually explained. Arguably it would make
>sense to split this section into more parts but in any case it does not
>make sense to let index entries be off-mark by what amounts to several
>page
any existing
layout settings, but the alternative method suggested by David seems
reasonable.
--
Mark Knoop
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
At 13:08 on 16 Jul 2012, David Kastrup wrote:
>Mark Knoop writes:
>
>> At 11:55 on 16 Jul 2012, Mark Knoop wrote:
>>>This used to work... but has recently broken. See:
>>>
>>>https://bugzilla.gnome.org/show_bug.cgi?id=568209
>>
>> or maybe:
>
At 11:55 on 16 Jul 2012, Mark Knoop wrote:
>This used to work... but has recently broken. See:
>
>https://bugzilla.gnome.org/show_bug.cgi?id=568209
or maybe:
https://bugzilla.gnome.org/show_bug.cgi?id=660092
--
Mark Knoop
___
lilypond-deve
to finish loading. Great. So there is a
>use case for image-less info files after all. The default GNOME help
>browser (yelp?) breaks down with images.
This used to work... but has recently broken. See:
https://bugzilla.gnome.org/show_bug.cgi?id=568209
--
Mark Knoop
At 17:01 on 06 Mar 2012, janek.lilyp...@gmail.com wrote:
>Reviewers: Graham Percival, carl.d.sorensen_gmail.com, MikeSol,
>lemzwerg, Reinhold, joeneeman,
>
>Message:
>Please review asap, it's only a couple days left before application
>deadline.
line 912: s/counfusing/conf
tomization, but all of the customization is at
> the top of the script.
You are using $NAME in line 34 before assigning it to $2 which will
lead to unexpected results. Perhaps move line 34 after line 40.
--
Mark Knoop
___
lilypond-devel mailing lis
guration, then $VISUAL, then
$EDITOR, and then finally vi.
--
Mark Knoop
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
> > I strip all the trailing whitespace with sed after downloading the
> > LSR tarball.
>
> Ok. Could we get this added to makelsr.py ? I'd be surprised if
> it takes more than 1 line of python to strip all trailing
> whitespace.
line = line.rstrip()
--
Mark Kn
hing except the notes, q allows for
> >
> >8-. q-^ q-. q-^
> >
> > etc., right? Obviously, this would *not* be possible with something
> > like
> >
> >4*8
>
> OTOH, something like
> { 8-.
> 8-. q-^ q-. q-^
And indeed:
4 q8 q8
which looks extremely useful to me.
--
Mark Knoop
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
f keyboard shortcuts. That was a couple
> years ago, but I remember being impressed.
>
For the ultimate in keyboard browsing, try Vimperator. Like all the
best software (e.g. LilyPond, Vim, etc.) there's a steep learning
curve...
http://vimperator.org/
--
Mark Knoop
not actually American...
http://en.wikipedia.org/wiki/Oxford_spelling
--
Mark Knoop
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
swapping between the
two staves.
So it's actually the extremity of the chord in the direction of
potential staff change that is of primary importance.
--
Mark Knoop
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
At 13:32 on 05 Jul 2009, Francisco Vila wrote:
> 2009/7/5 Mark Knoop :
> > http://code.google.com/p/support/issues/detail?id=1163
>
> > Mark Knoop
>
> Thank you, here is comprehensively explained. Are you horndude77?
No. But I do wish they would fix
h a suitable application instead?
>
> Or, is it completely out of our reach?
http://code.google.com/p/support/issues/detail?id=1163
--
Mark Knoop
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
ilise 128th notes for the reasons you explain. This is a decision
that should not be take by the software you choose.
I don't know how many flags Finale and Sibelius support, but Lilypond
should at least equal those programs' capabilities.
(And I'm not arguing that this shoul
otes' is rather disturbing. Clearly, composers *do* use 128th (and
shorter) notes, both beamed and unbeamed: therefore lilypond *should*
support them.
The musical notation should be chosen by the composer, not the tool. It
is not the job of software writers to dictate what is or is not
'
.cgi?id=299
Ah, but they're beamed. What if anyone ever wants to typeset
Ferneyhough's Lemma Icon Epigram?
--
Mark Knoop
<>___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
kes one argument, which is a music expression (and cannot be a sequence
> of notes, just a single so-called EventChord), so Max's comment seems
> correct.
...in which case it would seem to be almost completely useless. (If it
needs to be restated after every use, then one may as well just end
61 matches
Mail list logo
