Kenneth,
The auto beaming can be overridden using [..]. Look up "manual beaming"
in the docs.
Stem direction can be changed with \stemUp and \stemDown.
Attached is a start.
Mark
-Original Message-
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On
Thanks Aaron.
The first suggestion seemed to do absolutely nothing to change the
appearance of the beaming (I'm bewildered), but the second suggestion
worked.
Ken
On Sun, Jul 31, 2022 at 7:45 PM Aaron Hill wrote:
>
> On 2022-07-31 7:10 pm, Kenneth Wolcott wrote:
> > However, the current
On 2022-07-31 7:10 pm, Kenneth Wolcott wrote:
However, the current incarnation of my Swan Lake harp part (one bar
so far), does not have a complete beam (only each triplet has a beam).
I thought that this would be automatic.
In 4/4 time, there is a default beam exception for "twelfth" notes.
Maybe I got it now :-)
Thanks to all of you who put up with me
Ken
On Sun, Jul 31, 2022 at 6:33 PM Kenneth Wolcott
wrote:
>
> Ah! I created more than one bar of notes, therefore I have to have
> more than one bar of spacer notes. Doh!
>
> On Sun, Jul 31, 2022 at 5:35 PM Kenneth Wolcott
>
Ah! I created more than one bar of notes, therefore I have to have
more than one bar of spacer notes. Doh!
On Sun, Jul 31, 2022 at 5:35 PM Kenneth Wolcott
wrote:
>
> Hi;
>
> Starting a new email thread regarding my difficulty in understanding
> how to use the Lilypond \change Staff feature...
Hi;
Starting a new email thread regarding my difficulty in understanding
how to use the Lilypond \change Staff feature...
I'm trying to create a two-octave ascending C Major scale using the
change Staff example in NR.
Thank you, Mark. I will start a new email thread on this topic
starting with a more basic \change Staff query.
On Sat, Jul 30, 2022 at 7:02 PM Mark Stephen Mrotek
wrote:
>
> Kenneth,
>
> If you want, send your code to me and I shall try to achieve what you want
> with an explanation.
>
> Mark
Aaron Hill writes:
> On 2022-07-31 2:11 pm, Jim Cline wrote:
>>> Can you provide a MWE? (https://lilypond.org/tiny-examples.html)
>>> --
>>> Knute Snortum
>> Sure, here is one. The vspace is ignored, no matter what value is
>> given.
>> %%%
>> \version "2.20.0"
>> \relative c {
>> \time 3/4
Hi Jim,
> I guess \vspace is not intended for use within markups?
Well… \vspace is not intended to be used within markups the way you were trying
to use it. :)
\markup \column {
"this"
\vspace #5
"works"
}
If you want to move something down, you can use \lower:
\markup { "this"
I am not certain negative \hspace or \vspace is supported. For \hspace, it
probably only works by fluke.
Hi Aaron, thanks for those examples!
To clarify, when I said that \vspace is disregarded no matter what the
value, that includes positive values. In fact, it is ignored regardless
of
On 2022-07-31 2:11 pm, Jim Cline wrote:
Can you provide a MWE? (https://lilypond.org/tiny-examples.html)
--
Knute Snortum
Sure, here is one. The vspace is ignored, no matter what value is
given.
%%%
\version "2.20.0"
\relative c {
\time 3/4
g'' e' d_\markup{\hspace #-4 \vspace #-7 x}
Can you provide a MWE? (https://lilypond.org/tiny-examples.html)
--
Knute Snortum
Sure, here is one. The vspace is ignored, no matter what value is given.
%%%
\version "2.20.0"
\relative c {
\time 3/4
g'' e' d_\markup{\hspace #-4 \vspace #-7 x}
}
--Jim
Hi Aaron,
>> Here is something I threw together quickly... Hope it offers some
>> inspiration:
> And here is a better and more readable version
Truly incredible and inspiring! Thanks!
I'll get back to you with any questions I have.
All the best,
Kieren.
On Sun, Jul 31, 2022 at 8:08 AM Jim Cline wrote:
>
> Hi Knute, thanks, that works. I am also trying to figure out how to do
> the analogous thing with the placement of a markup text. Putting the same
> tweaks within the markup does not compile. Putting
>
> \markup{\hspace #4 \vspace #-2 text}
On 2022-07-31 12:48 pm, Aaron Hill wrote:
On 2022-07-31 12:00 pm, Kieren MacMillan wrote:
Thanks for any help you can give!
Here is something I threw together quickly... Hope it offers some
inspiration:
And here is a better and more readable version:
(Why I had all those unnecessary
Hi! I am studying Byzantine singing, which uses neumes to record melodies. Have you ever met a player or a converter of this notation into a five-line one in the lilypond program? Are there any developments on this topic at all?Например посмотрите книгу по византийскому пению:Langue N. "A guide to
On 2022-07-31 12:00 pm, Kieren MacMillan wrote:
Thanks for any help you can give!
Here is something I threw together quickly... Hope it offers some
inspiration:
\version "2.22.0"
createExercise =
#(define-scheme-function
(clef key root)
(symbol? ly:pitch? ly:pitch?)
#{
Hi all!
I'm hoping someone can whip up a “simple” example of an exercise randomizer,
built in Scheme, for music theory. Let's say I want to generate something like
this:
I would love to be able to have a function do this, with parameters for:
— how many examples to generate
— which
Hello Hans,
> Le 31 juil. 2022 à 16:22, Hans Aikema a écrit :
>
> Loking at the spec
> https://w3c.github.io/musicxml/musicxml-reference/elements/note/
>
> I would say the proper behaviour is that the entire note, including the stem,
> is hidden for these cases (but taken into account for
Jim Cline writes:
>> You can always write something like
>>
>> %%%
>> \version "2.20.0"
>> \relative c {
>> \time 3/4
>> \mergeDifferentlyDottedOn
>> <<{4\arpeggio e' d}\\{ g,8._\tweak extra-offset #'(0.5 . 3) ->
>> dis16 a2}>>|
>> }
>>
>> but frankly, it quite evades me why you would
You can always write something like
%%%
\version "2.20.0"
\relative c {
\time 3/4
\mergeDifferentlyDottedOn
<<{4\arpeggio e' d}\\{ g,8._\tweak extra-offset #'(0.5 . 3) -> dis16
a2}>>|
}
but frankly, it quite evades me why you would consider this desirable
over the default output.
In the
Hi Knute, thanks, that works. I am also trying to figure out how to do
the analogous thing with the placement of a markup text. Putting the same
tweaks within the markup does not compile. Putting
\markup{\hspace #4 \vspace #-2 text}
applies the hspace but ignores the vspace. --Jim
I
On Sun, Jul 31, 2022 at 7:01 AM Jim Cline wrote:
>
> Apologies in advance; this seems like it must be simple, but I cannot find
> the answer. I would like to be able to move an accent closer to the note
> head, possibly using markup since it would also be nice to know how to get
> markups to
Jim Cline writes:
> Apologies in advance; this seems like it must be simple, but I cannot
> find the answer. I would like to be able to move an accent closer to
> the note head, possibly using markup since it would also be nice to
> know how to get markups to print over the staff lines. Here
> On 31 Jul 2022, at 15:16, Jacques Menu wrote:
>
> Hello Timothy,
>
> Thanks for the info. This version of Finale is old, and it does print the
> note heads, ignoring the print-object attribute.
>
> I’ll complement xml2ly to hide the note head in this case.
>
> A nice day!
>
> JM
>
>>
Apologies in advance; this seems like it must be simple, but I cannot find
the answer. I would like to be able to move an accent closer to the note
head, possibly using markup since it would also be nice to know how to get
markups to print over the staff lines. Here is an example:
%%%
Hello Timothy,
Thanks for the info. This version of Finale is old, and it does print the note
heads, ignoring the print-object attribute.
I’ll complement xml2ly to hide the note head in this case.
A nice day!
JM
> Le 31 juil. 2022 à 00:06, Timothy Lanfear a écrit :
>
> On 30/07/2022 17:18,
As a programmer in other languages, I like to think of arguments being
enclosed in some kind of brackets, like a function f(x,y(z)). That's why
I alway enclose what I'm marking up within {}; what's inside are the
arguments of the markup. Using your explanation then it looks like
Jim Cline writes:
> Hi Aaron, thanks for that. I thought I had tried all permutations of
> the order of specifications but I missed that one. It's hard to guess
> which one is correct.--Jim
It's not a matter of order or permutations. Things like \with-color
#red are not complete without the
> Hi Aaron, thanks for that. I thought I had tried all permutations
> of the order of specifications but I missed that one. It's hard to
> guess which one is correct.
Is it? I don't think so. Just bear in mind whether you have used up
all arguments of a markup command. In your case,
Hi Aaron, thanks for that. I thought I had tried all permutations of the
order of specifications but I missed that one. It's hard to guess which
one is correct.--Jim
What you have effectively done is this:
\markup {
\smaller { \with-color #blue { \hspace #-3 } }
text
}
You could
31 matches
Mail list logo
