taves but "on the same level" because of an ottava, the
> > accidental is repeated. This makes sense logically because they are
> > not the same note, but it doesn't look right to me, at least. Maybe
> > it's the intended behavior?
>
> FWIW, Gould writes:
At 10:38 on 10 Feb 2023, Knute Snortum wrote:
> I have run into something in LilyPond that's annoying -- it probably
> doesn't rise to the level of bug. When you have two notes in
> different octaves but "on the same level" because of an ottava, the
> accidenta
I have run into something in LilyPond that's annoying -- it probably
doesn't rise to the level of bug. When you have two notes in
different octaves but "on the same level" because of an ottava, the
accidental is repeated. This makes sense logically because they are
not t
> I actually looked, but found this page -
> https://lilypond.org/doc/v2.22/Documentation/notation/clef-styles
> there it's not mentioned :(
https://gitlab.com/lilypond/lilypond/-/merge_requests/1838
Werner
thx Xavier - I actually looked, but found this page -
https://lilypond.org/doc/v2.22/Documentation/notation/clef-styles
there it's not mentioned :( - sorry, embarrassing...
On Wed, 8 Feb 2023 at 15:26, Johannes Roeßler wrote:
>
> Hi Group,
>
> is it possible to create a clef like this:
>
> Like
On Wed, 8 Feb 2023 at 15:26, Johannes Roeßler wrote:
>
> Hi Group,
>
> is it possible to create a clef like this:
>
> Like \clef "violin_8" but with the 8 in parentheses?
Hello,
\clef "violin_(8)" or \clef "treble_(8)" works.
They are also mentioned in the documentation:
NR 1.1.3 Displaying pitc
> Le 8 févr. 2023 à 15:27, Johannes Roeßler a écrit :
>
>
> Hi Group,
>
> is it possible to create a clef like this:
>
>
>
> Like \clef "violin_8" but with the 8 in parentheses?
>
See the fourth example here:
https://lilypond.org/doc/v2.24/Documentation/notation/displaying-pitches#cle
Hi Group,
is it possible to create a clef like this:
Like \clef "violin_8" but with the 8 in parentheses?
Best regards
Johannes
On Fri, Dec 2, 2022 at 2:14 PM Jean Abou Samra wrote:
>
> Le 02/12/2022 à 02:27, Joel C. Salomon a écrit :
> > Piece of music I have in front of me puts the text "loco." above the
> > first note after an ottava. See also the attached example, from
> > <https:
Am Sa., 3. Dez. 2022 um 16:56 Uhr schrieb Jean Abou Samra :
>
> Le 03/12/2022 à 15:41, Thomas Morley a écrit :
> > Granted, if I use -dcheck-internal-types I mostly wear my developer
> > hat. But sometimes I use it even for huge custom codings as part of
> > debugging processes.
>
>
>
> Why? What d
Le 03/12/2022 à 15:41, Thomas Morley a écrit :
Granted, if I use -dcheck-internal-types I mostly wear my developer
hat. But sometimes I use it even for huge custom codings as part of
debugging processes.
Why? What does it catch?
In my view, warnings about a property being set on a grob
that
Am Sa., 3. Dez. 2022 um 15:06 Uhr schrieb Jean Abou Samra :
> -S only shows commits that changed the number of occurrences
> of the pattern, which is useful to find out when something
> was added or deleted. To find all the times a line containing
> the pattern was changed, use -G instead.
Thanks
Le 03/12/2022 à 14:46, Thomas Morley a écrit :
I didn't know about -S
Thanks.
Alas, this command extended as
$ git log -S "check-internal-types" --oneline --author="Han-Wen"
prints for me:
$ git log -S "check-internal-types" --oneline --author="Han-Wen"
264570e68e Documentation: remove documenta
Am Sa., 3. Dez. 2022 um 13:53 Uhr schrieb Jean Abou Samra :
> Le 03/12/2022 à 13:26, Thomas Morley a écrit :
> > \version "2.23.0"
>
>
> 2.23.80, I suppose? horizontal-line-spanner is new in 2.23.6.
Ofcourse, that 8 slipped away somehow...
> > Btw, I can't find -dcheck-internal-types in the 2.2
example we were to transpose the part up we would want to extend the
ottava indication so it also encompasses some notes marked as loco. If we were
to transpose it down we might not use the ottave indication at all (or only
for a shorter section), but we would still put the loco in the same place.
I
Am Fr., 2. Dez. 2022 um 02:28 Uhr schrieb Joel C. Salomon
:
>
> Piece of music I have in front of me puts the text "loco." above the
> first note after an ottava. See also the attached example, from
> <https://dictionary.onmusic.org/terms/17-8va>.
>
> The code b
Hi Joel,
The OttavaBracket looks like a line-spanner, but it isn’t! It doesn’t even
follow the spanner interface (between notes), but the bracket interface
(encompass notes).
But why would you in fact want this? As I read this the ottava indication and
the indication are mostly independent
Le 02/12/2022 à 02:27, Joel C. Salomon a écrit :
Piece of music I have in front of me puts the text "loco." above the
first note after an ottava. See also the attached example, from
<https://dictionary.onmusic.org/terms/17-8va>.
The code below does not work, which makes me sus
Piece of music I have in front of me puts the text "loco." above the
first note after an ottava. See also the attached example, from
<https://dictionary.onmusic.org/terms/17-8va>.
The code below does not work, which makes me suspect I do not in fact
understand the spanner interf
Thank you!
-Ahanu
On Fri, Jul 1, 2022, 04:00 Paul Hodges wrote:
> The ottava bracket needs both ends defined to appear, so the ottava
> command and its cancellation should be at the start and end of the music to
> be affected, like this:
>
> << { \ottava 1 \repeat u
The ottava bracket needs both ends defined to appear, so the ottava command and
its cancellation should be at the start and end of the music to be affected,
like this:
<< { \ottava 1 \repeat unfold 4 c'' \ottava 0 } \\ { \repeat unfold 4 d,, } >>
However, the comm
Dear Ahanu,
There is an example (
https://lilypond.org/doc/v2.22/Documentation/notation/displaying-pitches#ottava-brackets
) in the documentation which covers this subject. Is there anything else
about this that isn't working for you?
-William
---
{
\clef bass
<&
Hi,
Is it possible to have two voices in one measure, on one staff, with one
voice as "Ottava 1" and the other as "Ottava 0"? (I realise this notation
may seem unclear, but I have a specific use case.)
If I try the following, each ottava overrides the other:
\version &
> behaviour, as done by most Software, Editions and recommended by Gould. Thus
>> doing ottava markings like this should be considered uncommon notation.
>> Considering Tchaikovsky is not exactly modern music I think it is viable to
>> say that in this case it is your original s
your expertise.
Ken
On Sat, May 14, 2022 at 2:54 AM Valentin Petzel wrote:
>
> Hello Ken,
>
> As far as I know Lilypond's behaviour here is pretty much the standard
> behaviour, as done by most Software, Editions and recommended by Gould. Thus
> doing ottava markings li
Thank you, Aaron.
Interesting thoughts...
Ken
On Fri, May 13, 2022 at 9:21 PM Aaron Hill wrote:
>
> On 2022-05-13 8:28 pm, Kenneth Wolcott wrote:
> > The ottava spanner terminates at the end of the note, not at the end
> > of the bar.
> >
> > How to chan
Hello Ken,
As far as I know Lilypond's behaviour here is pretty much the standard
behaviour, as done by most Software, Editions and recommended by Gould. Thus
doing ottava markings like this should be considered uncommon notation.
Considering Tchaikovsky is not exactly modern music I thi
On 2022-05-13 8:28 pm, Kenneth Wolcott wrote:
The ottava spanner terminates at the end of the note, not at the end
of the bar.
How to change this?
Screenshots attached.
Consider the following:
\version "2.22.0"
\relative c'' {
% Be careful not to stop
what this function does is:
> >
> > If the ottava bracket is broken we check if the grob is a broken part.
> > This is done by getting all broken parts (the siblings) and checking if
> > grob is the first of these (implying that it is the first part which we
> > do not w
Am Mo., 29. Nov. 2021 um 22:49 Uhr schrieb Valentin Petzel :
>
> Basically grob.after-line-breaking is a function that get’s called on grob
> after line breaks are determined and allows us to do tweaks related to line-
> breaking. So what this function does is:
>
> If the ottava
Basically grob.after-line-breaking is a function that get’s called on grob
after line breaks are determined and allows us to do tweaks related to line-
breaking. So what this function does is:
If the ottava bracket is broken we check if the grob is a broken part. This is
done by getting all
t
> > continue it with a dashed line?
> >
> > \version "2.22.1"
> >
> > \score {
> >
> > \new Staff {
> > \set Staff.ottavationMarkups = #ottavation-ordinals
> > \ottava #1
> > c''' 4 d''' e'''' f''''
> > \break
> > d''' f'''' g'''' a''''
> >
> >}
> > }
> >
> > -Molly
t;
>
> \score {
>
> \new Staff {
> \set Staff.ottavationMarkups = #ottavation-ordinals
> \ottava #1
> c''' 4 d''' e'''' f''''
> \break
> d''' f'''' g'''
#ottavation-ordinals
\ottava #1
c''' 4 d''' e'''' f''''
\break
d''' f'''' g'''' a''''
}
}
-Molly
On Sat, Nov 6, 2021 at 2:08 PM Kieren MacMillan
wrote:
>
> p.s.
>
> > Does \afterBreak not work with OttavaBracket.padding?
>
> um… \alterBroken (as in the snippet).
> Sorry! — K
>
> > \relative {
> > \alterBroken #'padding #'(1 7) Staff.Ot
On 11/6/21, 3:24 PM, "lilypond-user on behalf of Lukas-Fabian Moser"
wrote:
> \relative {
>\alterBroken #'padding #'(1 7) Staff.OttavaBracket
>\ottava 1 c''''1 \break
> c2 2
> }
I continue my l
Hi Lukas,
> I continue my lonely crusade against the hash-tick-combinations
I generally remove them — I’m on the crusade with you! — tho’ on this
“fast-cut-and-paste job”, I didn’t. =(
That being said, there are certain circumstances in which I prefer keeping the
hashes, as they (IMO) help re
On 2021-11-06 2:45 pm, Lukas-Fabian Moser wrote:
Since #'(1 7) is a list of numbers, you could write it this way:
\relative {
\alterBroken padding 1,7 Staff.OttavaBracket
\ottava 1 c''''1 \break
c2 2
}
Right, thanks! I had a feeling there was a w
Since #'(1 7) is a list of numbers, you could write it this way:
\relative {
\alterBroken padding 1,7 Staff.OttavaBracket
\ottava 1 c''''1 \break
c2 2
}
Right, thanks! I had a feeling there was a way to do this using dak's
syntax enhancements
On 2021-11-06 2:23 pm, Lukas-Fabian Moser wrote:
\relative {
\alterBroken #'padding #'(1 7) Staff.OttavaBracket
\ottava 1 c''''1 \break
c2 2
}
I continue my lonely crusade against the hash-tick-combinations that I
found so daunting when I learned LilyPond
\relative {
\alterBroken #'padding #'(1 7) Staff.OttavaBracket
\ottava 1 c''''1 \break
c2 2
}
I continue my lonely crusade against the hash-tick-combinations that I
found so daunting when I learned LilyPond and which are needed much less
often today
Le 06/11/2021 à 22:01, Knute Snortum a écrit :
Hello again,
I have a situation where I need to adjust the padding of an ottava
bracket after a line break. That is, I want to affect the bracket on
the second line, but not the first.
I know you can do something like this with the \shape
p.s.
> Does \afterBreak not work with OttavaBracket.padding?
um… \alterBroken (as in the snippet).
Sorry! — K
> \relative {
> \alterBroken #'padding #'(1 7) Staff.OttavaBracket
> \ottava 1 c''''1 \break
> c2 2
> }
Hi Knute,
> I have a situation where I need to adjust the padding of an ottava
> bracket after a line break. That is, I want to affect the bracket on
> the second line, but not the first.
Does \afterBreak not work with OttavaBracket.padding?
\relative {
\alterBroken #'
Hello again,
I have a situation where I need to adjust the padding of an ottava
bracket after a line break. That is, I want to affect the bracket on
the second line, but not the first.
I know you can do something like this with the \shape function, but
what about brackets?
I tried this solution
isely what this arranger is doing, I
> > > could just enter the pitches as written and just place a note to
> > > instruct the performer to do the ottava manually, correct?
> >
> > Sure. And if you would prefer to enter
> > the pitches as souding, you could keep
> &
itten and just place a note to
> > instruct the performer to do the ottava manually, correct?
> >
> > Thanks,
> > Ken
>
> Sure. And if you would prefer to enter
> the pitches as souding, you could keep
> \ottava and add
>
>\omit Staff.OttavaBracket
>
> Best,
> Jean
Le 02/11/2021 à 00:08, Kenneth Wolcott a écrit :
That helps explain it! Thanks!
But if I wanted to reproduce precisely what this arranger is doing, I
could just enter the pitches as written and just place a note to
instruct the performer to do the ottava manually, correct?
Thanks,
Ken
Sure
t;I now have the attava bracket beneath the notes using " \override
> > Staff.OttavaBracket.direction = #DOWN"
> >
> >BTW, I'm looking at the NR for 2.22.1 and I see "ottava #X" where,
> > apparently the "#" is no longer needed.
>
That helps explain it! Thanks!
But if I wanted to reproduce precisely what this arranger is doing, I
could just enter the pitches as written and just place a note to
instruct the performer to do the ottava manually, correct?
Thanks,
Ken
On Mon, Nov 1, 2021 at 3:57 PM Jean Abou Samra wrote
Le 02/11/2021 à 00:00, Kenneth Wolcott a écrit :
Hi Jean;
Thanks for the tip.
I'm using Lilypond 2.22.1.
I now have the attava bracket beneath the notes using " \override
Staff.OttavaBracket.direction = #DOWN"
BTW, I'm looking at the NR for 2.22.1 and I s
Hi Jean;
Thanks for the tip.
I'm using Lilypond 2.22.1.
I now have the attava bracket beneath the notes using " \override
Staff.OttavaBracket.direction = #DOWN"
BTW, I'm looking at the NR for 2.22.1 and I see "ottava #X" where,
apparently the "#"
ival of
the Animals", by Saint-Saens. It is not long and it is simple.
Perhaps I'm doing something really stupid...
You're trying to enter the pitches as if the ottava were
not there, and add the ottava to make them sound and read
one octave lower. Just like with accidentals, LilyPo
by an octave. But when you entered
the pitches, you didn't lower them by an octave to the sounding pitch, you
entered them at the staff position pitch. Thus, when you lowered the staff by
an octave with \ottava, the pitches shifted up by an octave on the staff.
TLDR; Your pitches are an octave too high.
Carl
Le 01/11/2021 à 23:20, Kenneth Wolcott a écrit :
How to force the placement of the ottava bracket to be below the
notes? (or above?)
Below: just \override the direction. Above: prior
to version 2.23.3, you had to use the lesser known
\overrideProperty (see
https://gitlab.com/lilypond
Ken,
Please show an example.
I assume you are using it wrong.
Always enter the sounding pitch in lilypond. In the Notation Reference, they
are showing you that if you don't change the pitch, an add an ottava, the note
will displace in the opposite direction of the ottava bracket, becaus
Hi;
How to force the placement of the ottava bracket to be below the
notes? (or above?)
Thanks,
Ken Wolcott
Hi Ken,
> another question regarding ottava: why does Lilypond change the pitches?
>
> If the purpose of the ottava is to make it easier for the
> publisher/engraver/typesetter/performer to read the notes within the
> staff rather than lots of ledger lines above or below the st
Hi again;
another question regarding ottava: why does Lilypond change the pitches?
If the purpose of the ottava is to make it easier for the
publisher/engraver/typesetter/performer to read the notes within the
staff rather than lots of ledger lines above or below the staff, then
why does
Thanks, Jean; I'll continue to experiment.
On Wed, Aug 11, 2021 at 3:13 PM Jean Abou Samra wrote:
>
> Le 12/08/2021 à 00:11, Kenneth Wolcott a écrit :
> > Sorry, did not reply-all :-(
> >
> > No, I did not upgrade. I thought you stated that I had two choices:
> > one command that would work with
Le 12/08/2021 à 00:11, Kenneth Wolcott a écrit :
Sorry, did not reply-all :-(
No, I did not upgrade. I thought you stated that I had two choices:
one command that would work with 2.33 and the other one which will
work with 2.23.
Yes (but I think you meant 2.22, not 2.33).
\overrideProperty wil
Sorry, did not reply-all :-(
No, I did not upgrade. I thought you stated that I had two choices:
one command that would work with 2.33 and the other one which will
work with 2.23.
On Wed, Aug 11, 2021 at 3:10 PM Kenneth Wolcott
wrote:
>
> No, I did not upgrade. I thought you stated that I had tw
Le 11/08/2021 à 23:57, Kenneth Wolcott a écrit :
Thanks, Jean!
However, I see no change in the pdf output and I get no errors or warnings.
I saw this command in Notation reference, and had tried it already. I
thought perhaps I had not used the correct syntax.
So I tried copy&paste from your e
g 11, 2021 at 2:36 PM Jean Abou Samra wrote:
>
> Le 11/08/2021 à 23:30, Kenneth Wolcott a écrit :
> > Hi All;
> >
> >I'm using Lilypond 2.22 on a Mac.
> >
> >How to force the ottava bracket to go above the notes in a Piano piece?
> >
> >T
Le 11/08/2021 à 23:30, Kenneth Wolcott a écrit :
Hi All;
I'm using Lilypond 2.22 on a Mac.
How to force the ottava bracket to go above the notes in a Piano piece?
The ottava bracket is not clear when placed in between the clefs; I
suppose I could make it bold face...
The
Hi All;
I'm using Lilypond 2.22 on a Mac.
How to force the ottava bracket to go above the notes in a Piano piece?
The ottava bracket is not clear when placed in between the clefs; I
suppose I could make it bold face...
The notes are still within the treble staff.
Thanks,
Ken Wolcott
On 2021-02-19 5:48 pm, Andrew Bernard wrote:
Acceptable to Gould or not, there are valid use cases for this (in my
New Complexity stuff for one). There's a way to do it - I need to find
it in my library code later today. I seem to vaguely recall there is
an example in LSR? I may be wrong.
Maybe
02 AM:
Re: Partial ottava sign Just the one chord. I'll try that unless
anyone else here comes up with a better suggestion. I was really
asking whether there's an accepted way of doing it.
5:17 PM
>> From: "Kieren MacMillan"
>> To: "Peter Toye"
>> Cc: "Lilypond-User Mailing List"
>> Subject: Re: Partial ottava sign
>> Hi Peter,
>> > Is there an accepted way of notating an ottava sign for only part of a
>> &g
> Is there an accepted way of notating an ottava sign for only part of a
>> staff? I have a two-handed chord of which the LH part needs to be an octave
>> lower than notated, but the RH part is at pitch.
>> I realise that this isn't really a LilyPond question but a general
At 11:17 19/02/2021 -0500, Kieren MacMillan wrote:
At 15:35 19/02/2021 +, Peter Toye wrote:
Is there an accepted way of notating an ottava sign for only part
of a staff? I have a two-handed chord of which the LH part needs to
be an octave lower than notated, but the RH part is at pitch
t; To: "Peter Toye"
> Cc: "Lilypond-User Mailing List"
> Subject: Re: Partial ottava sign
>
> Hi Peter,
>
> > Is there an accepted way of notating an ottava sign for only part of a
> > staff? I have a two-handed chord of which the LH part needs to
Hi Peter,
> Is there an accepted way of notating an ottava sign for only part of a staff?
> I have a two-handed chord of which the LH part needs to be an octave lower
> than notated, but the RH part is at pitch.
>
> I realise that this isn't really a LilyPond question
Is there an accepted way of notating an ottava sign for only part of a staff? I
have a two-handed chord of which the LH part needs to be an octave lower than
notated, but the RH part is at pitch.
I realise that this isn't really a LilyPond question but a general music
engraving one (i
Am Do., 7. Jan. 2021 um 18:33 Uhr schrieb Davide Parisi :
>
> Goodmorning,
> I'm transcribing "Scarbo" from Gaspard de la Nuit with Lilypond.
> There is a method for create a cross-staff ottava bracket with breaked line
> like this example?
> https://ibb.co/rw
Goodmorning,
I'm transcribing "Scarbo" from Gaspard de la Nuit with Lilypond.
There is a method for create a cross-staff ottava bracket with breaked line
like this example?
https://ibb.co/rwLwd19
Thanks for your attention!
> I think that the problem with the bracket I just described is a bug
> or a feature that should be enhanced...
Vertical alignment of cross-staff material is partially broken, yes,
from the very beginning. Search for
cross AND staff AND status:Accepted
in the issue tracker.
Werner
between ottava bracket and stems in cross-staff systems
Hello Kieren,
unfortunately this method is trial and error as well. In fact, I can't use the
same shorten-pair value if the stem is up or down, and (maybe) if the notehead
has different sizes...
I think that the problem wit
Hi Paolo,
> unfortunately this method is trial and error as well.
Not if it’s a callback function. ;) You need to write code that determines how
much to shorten/extend (by referencing the width of noteheads, etc.), and
automatically applies the tweak. That’s how you make it not trial-and-error.
ult might
> be.
>
> Hope that helps!
> Kieren.
>
>
> > -- Original Message --
> > From: Paolo Pr
> > Date: December 8, 2019 at 6:40 PM
> >
> >
> > Hello,
> >
> > in cross-staff systems, I see that the ottava br
M
>
>
> Hello,
>
> in cross-staff systems, I see that the ottava bracket can produce an unwanted
> collision between the "8va" string and the stems. Please, look at:
>
> http://lilybin.com/vf4vaj/1
>
> Is there a way to automatically avoid that, without using t
On 2019-12-08 3:40 pm, Paolo Pr wrote:
Hello,
in cross-staff systems, I see that the ottava bracket can produce an
unwanted collision between the "8va" string and the stems. Please, look
at:
http://lilybin.com/vf4vaj/1
Is there a way to automatically avoid that, without using the
Hello,
in cross-staff systems, I see that the ottava bracket can produce an
unwanted collision between the "8va" string and the stems. Please, look at:
http://lilybin.com/vf4vaj/1
Is there a way to automatically avoid that, without using the
trial-and-error method for adjusting the
On 2019/11/30 18:56, Thomas Morley wrote:
Am Sa., 30. Nov. 2019 um 02:19 Uhr schrieb Jinsong Zhao
:
On 2019/11/30 2:23, Thomas Morley wrote:
\ottava works for Staff. You told LilyPond to write your entered
Staff-input one octave below. Thus the OttavaBracket _needs_ to span
the upper
Am Sa., 30. Nov. 2019 um 02:19 Uhr schrieb Jinsong Zhao
:
>
> On 2019/11/30 2:23, Thomas Morley wrote:
> >
> > \ottava works for Staff. You told LilyPond to write your entered
> > Staff-input one octave below. Thus the OttavaBracket _needs_ to span
> > the upper Vo
Hello Jinsong.
In the Notation Reference manual (NR). It's complete. But its not a
ordered alphabetical list of commands. It's arranged by topic, with
extensive explanatory material. There is also an alphabetical index.
http://lilypond.org/doc/v2.18/Documentation/notation/index.html
You can
On 2019/11/30 2:23, Thomas Morley wrote:
\ottava works for Staff. You told LilyPond to write your entered
Staff-input one octave below. Thus the OttavaBracket _needs_ to span
the upper Voice (although you tweaked it's direction down)
Though, I somehow doubt that's what you intended .
Am Fr., 29. Nov. 2019 um 18:20 Uhr schrieb Jinsong Zhao
:
>
> Hi there,
>
>
>
> In the following MWE, you may notice that the ottava spanner have different
> behavior. It may be my fault. However, I don’t know how to correct it.
>
>
>
> The first question is why t
Hi there,
In the following MWE, you may notice that the ottava spanner have different
behavior. It may be my fault. However, I don’t know how to correct it.
The first question is why the first ottava spanner extent to the second note?
The second question is how to prevent the ottava spanner
On 2019-02-07 3:01 am, N. Andrew Walsh wrote:
Problem now is, Lily isn't avoiding collisions between the markup
objects
and grobs on other staves. Neither the markup nor the Staff.ottavation
text
block are given place, instead overlapping the voice above. How can I
fix
this?
Do you have a MW
PS- also, I've made use of http://lsr.di.unimi.it/LSR/Item?id=875, which
gets the notes in the correct positions. My example now looks like this:
---
\version "2.19.82"
\relative c, {
\clef "bass_8"
\textLengthOn
\override Staff.NoteColumn.ignore-collision = ##t
\override No
Hi Andrew
On Thu, Feb 7, 2019 at 11:51 AM Andrew Bernard
wrote:
> Hello Andrew,
>
> Why are quartertones technically wrong?
>
Quartertones are wrong for harmonics (especially "natural" ones), because
neither the finger position nor the resultant pitch are equivalent to
equal-tempered quarterton
Hello Andrew,
Why are quartertones technically wrong?
My current string quartet is full of them. String players can do them just
fine.
Andrew
On Thu, 7 Feb 2019 at 21:46, N. Andrew Walsh
wrote:
>
> (And yes, I know quartertones are technically wrong.
>
__
h^\markup { \right-align "Sul D" }--\harmonic
}
\\
{
\oneVoice
\tiny
\override Stem.stencil = ##f
\override Flag.stencil = ##f
\override ParenthesesItem.font-size = #0
{ \ottava #1 < \parenthesize ceh'''>4 s }
}
>
Hi Ryan,
>> I simply want to increase the vertical space between the ottava in the other
>> elements. How do I accomplish this?
> \override Staff.OttavaBracket.extra-offset = #'(0 . 2)
I always reserve extra-offset for the very last resort, because it doesn’t
inter
On 9/28/2018 12:17 PM, Ryan Michael wrote:
Hello, So I know how to change the priority of the ottava such that it
appears on the outside of other elements of the system. However, in my
case, I simply want to increase the vertical space between the ottava
in the other elements. How do I
Hello, So I know how to change the priority of the ottava such that it
appears on the outside of other elements of the system. However, in my
case, I simply want to increase the vertical space between the ottava in
the other elements. How do I accomplish this? I have tried something like
2"
rD = { \change Staff = right \stemDown }
lU = { \change Staff = left \stemUp }
right = \relative b'''' {
\ottava 2 b8 \lU
\once\override Stem.layer = -1
\once\override Stem.whiteout = #1
a, \rD b' \lU g, \rD b' \lU f, \rD b' \lU e,,
}
left = {
\overr
Yes you can... probably.
Anyway, it's not the finest idea. Please consider the following code:
\version "2.18.2"
rD = { \change Staff = right \stemDown }
lU = { \change Staff = left \stemUp }
right = \relative b'''' {
\ottava 2 b8 \lU
\once\override Stem.la
Dear Pierre,
thanks for Your answer. Can I also achieve the opposite? Can the stem
whiteout the ottava-bracket?
Am Di., 21. Aug. 2018 um 18:31 Uhr schrieb Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:
> Hi Stefan,
>
> How about:
>
> \version "2.18.2"
1 - 100 of 415 matches
Mail list logo
