Am 13.04.2015 um 04:11 schrieb Urs Liska:
Am 13. April 2015 04:05:56 MESZ, schrieb Urs Liska :
Hi David,
thank you for your head start.
See my attached results. I'd be grateful for any comments to improve
the
coding.
In particular I am quite sure that the nesting of
(list (list
is quite c
Am 13. April 2015 04:05:56 MESZ, schrieb Urs Liska :
>Hi David,
>
>thank you for your head start.
>See my attached results. I'd be grateful for any comments to improve
>the
>coding.
In particular I am quite sure that the nesting of
(list (list
is quite clumsy and maybe even "wrong".
>One bas
Hi David,
thank you for your head start.
See my attached results. I'd be grateful for any comments to improve the
coding.
One basic question is if it will be possible to extend it with other
types (dynamic text spanners etc.) without having to write another
engraver with duplicating code.
And
Am 13.04.2015 um 01:42 schrieb Thomas Morley:
2015-04-13 1:04 GMT+02:00 Pierre Perol-Schneider
:
Hi List,
If I wright:
\version "2.18.2"
{
r256
}
I get a warning: rest `rests.8' not found
How could I define rests.8 in order to put it in a function?
Cheers,
Pierre
We have no glyph f
David,
Thank you for this. This is exactly what I'm after.
It seems like you're a Scheme guy. Is there a learning resource you
would recommend to a very green beginner?
Thanks again,
David
On 04/09/2015 01:22 PM, lilypond-user-requ...@gnu.org wrote:
You can find a function here which I bel
Hi Pierre,
sorry to come back to you that late :(
2015-04-11 13:50 GMT+02:00 Pierre Perol-Schneider
:
> Hi List, Hi Harm,
>
> Harm, do you remember this disussion?
> http://lilypond.1069038.n5.nabble.com/How-to-catch-the-current-height-of-a-StaffGroup-td46889.html#a46893
>
> Did you finally find
2015-04-13 1:04 GMT+02:00 Pierre Perol-Schneider
:
> Hi List,
>
> If I wright:
>
> \version "2.18.2"
>
> {
> r256
> }
>
> I get a warning: rest `rests.8' not found
>
> How could I define rests.8 in order to put it in a function?
>
> Cheers,
> Pierre
We have no glyph for it.
Have a look at:
htt
Hi List,
If I wright:
\version "2.18.2"
{
r256
}
I get a warning: rest `rests.8' not found
How could I define rests.8 in order to put it in a function?
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailm
Ok, thanks for the explanation Andrew.
But I'm afraid you can't do that here since 'elipse' draws a single line
with a specific thickness. A note head with a counter would need at least
two lines/elipses, one filled 'inside' and the other filled 'outside' (but
I don't know how to do that).
So I'm a
Hi Harm,
> Well, you could do:
Thanks! I’ll check this out and report back.
> Though why?
> \once \set Score.timeSigVisibility = ##t is even more typing than
> inserting \time
Because I’m trying to separate content from presentation — typing \time
forces presentation layer information into m
2015-04-12 21:28 GMT+02:00 Kieren MacMillan :
> Hi all,
>
>>> But forcing the grob to appear presupposes that there is a TimeSignature
>>> grob, and these are created in response to \time. What you are suggesting
>>> would mean that each measure needs its own time signature object, which is
>>> no
Hi Calixte (which, by the way, is a wonderful name!),
> Using \RemoveEmptyStaves, is there a way to print the shortInstrumentName
> only when a Staff reappears.
+1
> To go further, is there a way to know when a Staff reappears, and then add a
> markup with the InstrumentName instead of shortIn
Hi everyone,
Using \RemoveEmptyStaves, is there a way to print the shortInstrumentName
only when a Staff reappears.
To go further, is there a way to know when a Staff reappears, and then add
a markup with the InstrumentName instead of shortInstrumentName?
I’d like to automate what it used to be in
Hi all,
>> But forcing the grob to appear presupposes that there is a TimeSignature
>> grob, and these are created in response to \time. What you are suggesting
>> would mean that each measure needs its own time signature object, which is
>> not the case.
Fair enough.
> Can the edition engraver
2015-04-12 20:40 GMT+02:00 Eljakim Schrijvers :
> Super, that is great to see! Thank you so much.
>
> I prefer this over Python (which I normally program in) since this can
> easily be posted in lilybin.com.
>
> Thanks again,
>
> Eljakim
Hi,
sorry for dropping in that late.
Here my own highly a
Super, that is great to see! Thank you so much.
I prefer this over Python (which I normally program in) since this can
easily be posted in lilybin.com.
Thanks again,
Eljakim
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Repeating-a-section-with-different-transpose-tp
David Nalesnik-2 wrote
> But forcing the grob to appear presupposes that there is a TimeSignature
> grob, and these are created in response to \time. What you are suggesting
> would mean that each measure needs its own time signature object, which is
> not the case.
Can the edition engraver just
On Sun, Apr 12, 2015 at 9:58 AM, Kieren MacMillan <
kieren_macmil...@sympatico.ca> wrote:
> Hi Simon,
>
> > I couldn’t carry it out, but what about the following approach: Create a
> music function to add \times before /every/ bar, add that function to
> toplevel-music-functions, \omit them except
Something I noticed: commands like figuredBassAlterationDirection do not work
when placed in the staff context (unlike Figured bass context)
Any idea to solve that?
Philippe
> Le 11 avr. 2015 à 10:10, Pierre Perol-Schneider
> a écrit :
>
> Hi Richard,
>
> Your option is more elegant than m
Hi Simon,
> I couldn’t carry it out, but what about the following approach: Create a
> music function to add \times before /every/ bar, add that function to
> toplevel-music-functions, \omit them except for the first, and use
> \once\override TimeSignature.stencil = #ly:time-signature::print fo
Am 12.04.2015 um 02:32 schrieb Kieren MacMillan:
Hi David,
No promises, just something hacked together. This only moves time signatures belonging
to the same paper column as a criteron of vertical "relatedness." Can't say if
that's a valid assumption.
Outstanding! Works great on all the ex
Paul Morris wrote
> Well, here's where the climb gets steep in trying to make this more
> robust. See below where I added a "music-filter" step that filters out
> the bar checks.
On second thought, forget the music-filter version and the ones before that.
The one below has the better approach,
In typography, the hole in characters such as ‘o’ and ‘a’ is called the
counter. Most notes are engraved with an ellipse as the empty space, with
‘italic pen’ style thick and thin.
The standard lilypond noteheads do this.
Andrew
On 12 April 2015 at 23:35:58, Pierre Perol-Schneider
(pierre.sc
Hi Andrew,
2015-04-12 13:45 GMT+02:00 Andrew Bernard :
> Here is my very first attempt at making custom noteheads. The shape is
> what we desire, but there are two questions that I have.
>
> 1. How does one achieve an elliptical counter in unfilled notes? I know
> how to do this in Postscript, bu
Hi Peter,
On Sun, Apr 12, 2015 at 7:08 AM, Peter Toye wrote:
> Sorry for the late reply - been rather busy.
>
> This is the LP that gives the error - I don't think I can cut it down any
> more.
>
> I got round it by accident - changed quite a few details and it worked OK,
> but I'm not 100% sur
Sorry for the late reply - been rather busy.
This is the LP that gives the error - I don't think I can cut it down any more.
I got round it by accident - changed quite a few details and it worked OK, but
I'm not 100% sure exactly which combination of changes solved the problem. But
I can't see
Here is my very first attempt at making custom noteheads. The shape is what we
desire, but there are two questions that I have.
1. How does one achieve an elliptical counter in unfilled notes? I know how to
do this in Postscript, but not here.
2. How can the stem alignment be corrected in the ch
27 matches
Mail list logo
