Hi Lukas,
Thank you. I found \bassFigureExtendersOn a bit odd, and now you've clearly
explained why.
Cheers,
Jun
> 2025/01/05 2:51、Lukas-Fabian Moser のメール:
>
> Hi Jun,
>
> Am 04.01.25 um 18:07 schrieb Jun Tamura:
>> Yes. Thank you.
>> I now understand that the following are equivalent.
>>
>
Hi Jun,
Am 04.01.25 um 18:07 schrieb Jun Tamura:
Yes. Thank you.
I now understand that the following are equivalent.
<_>8 \once\bassFigureExtendersOn <_>8
<_>8 \once\bassFigureExtendersOn <_>
<_>8 \once\bassFigureExtendersOn 8
<_>8 \once\bassFigureExtendersOn q
In effect, yes.
On a related n
Yes. Thank you.
I now understand that the following are equivalent.
<_>8 \once\bassFigureExtendersOn <_>8
<_>8 \once\bassFigureExtendersOn <_>
<_>8 \once\bassFigureExtendersOn 8
<_>8 \once\bassFigureExtendersOn q
Jun.
> 2025/01/05 0:32、Lukas-Fabian Moser のメール:
>
>
>
> Am 04.01.25 um 16:18 sch
Am 04.01.25 um 16:18 schrieb Knute Snortum:
On Sat, Jan 4, 2025 at 6:02 AM Jun Tamura wrote:
Hi Lukas,
Thank you!
Would you kindly let me know where I can find the trick of “q” in
the documentation?
https://lilypond.org/doc/v2.24/Documentation/notation/single-voice#chord-rep
On Sat, Jan 4, 2025 at 6:02 AM Jun Tamura wrote:
> Hi Lukas,
>
> Thank you!
> Would you kindly let me know where I can find the trick of “q” in the
> documentation?
>
https://lilypond.org/doc/v2.24/Documentation/notation/single-voice#chord-repetition
--
Knute Snortum
No. 2 and come across
>> the attached figured bass. Is there a good way to achieve this in LilyPond?
>> Bach often uses a short horizontal line, like a minus sign, instead of “3”
>> to indicate the third. I can typeset that with:
>> < \markup “-“ >
>> but I canno
Hi Jun,
Am 04.01.25 um 14:01 schrieb Jun Tamura:
I’m trying to typeset J. S. Bach’s Orchestral Suite No. 2 and come across the
attached figured bass. Is there a good way to achieve this in LilyPond? Bach
often uses a short horizontal line, like a minus sign, instead of “3” to
indicate the
Hello,
I’m trying to typeset J. S. Bach’s Orchestral Suite No. 2 and come across the
attached figured bass. Is there a good way to achieve this in LilyPond? Bach
often uses a short horizontal line, like a minus sign, instead of “3” to
indicate the third. I can typeset that with:
< \mar
+ _+> < 5- _-> <6 _+> <_+> <5- _-
> >}
> accidentals are placed at the left side of the number.
>
> > On 25 Apr 2024, at 1:10 AM, Jakob Pedersen
> > wrote:
> >
> >
> > Hi Dimitri
> >
> > Isn't that the standa
You forgot the lilypond list email, Dimitri.
Forwarded Message
Subject:Re: Figured bass
Date: Thu, 25 Apr 2024 01:37:09 +0300
From: Dimitri Sykias
To: Jakob Pedersen
OK. I found it: \set figuredBassAlterationDirection = #RIGHT
On 25 Apr 2024, at 1:32 AM
; <6- 4> <6> <6- 4-> <_-> <5-> <5+ _+> < 5- _-> <6 _+> <_+> <5- _->}
>> accidentals are placed at the left side of the number.
>>
>>> On 25 Apr 2024, at 1:10 AM, Jakob Pedersen
>>> <mailto:jak...@
rsen wrote:
Hi Dimitri
Isn't that the standard as shown in the example?
http://lilypond.org/doc/v2.24/Documentation/notation/figured-bass
Best wishes,
Jakob
On 25.04.2024 00.03, Dimitri Sykias wrote:
In Figured bass is it possible to place accidentals at the right side of the
number? (Ex. 6b, 5#)
Thanks!
he left side of the number.
> On 25 Apr 2024, at 1:10 AM, Jakob Pedersen wrote:
>
> Hi Dimitri
>
> Isn't that the standard as shown in the example?
> http://lilypond.org/doc/v2.24/Documentation/notation/figured-bass
>
> Best wishes,
> Jakob
>
> On 25.04.202
Hi Dimitri
Isn't that the standard as shown in the example?
http://lilypond.org/doc/v2.24/Documentation/notation/figured-bass
Best wishes,
Jakob
On 25.04.2024 00.03, Dimitri Sykias wrote:
In Figured bass is it possible to place accidentals at the right side of the
number? (Ex.
In Figured bass is it possible to place accidentals at the right side of the
number? (Ex. 6b, 5#)
Thanks!
Am 17.08.23 um 13:05 schrieb Jean Abou Samra:
Le jeudi 17 août 2023 à 12:28 +0200, Lukas-Fabian Moser a écrit :
(The even friendlier syntax variant would require changing the
lexer/parser, I think.)
Why don't you just do
<"/">
?
Two reasons:
- I wasn't aware that figures support " "
The slash is pronounced the best of several possibilites by
C. Ph. E. Bach [...]
Thanks. Please open an issue for SMuFL at
https://github.com/w3c/smufl/issues
so that this slash symbol gets added to the figured bass glyphs.
https://github.com/w3c/smufl/issues/279
open an issue for SMuFL at
https://github.com/w3c/smufl/issues
so that this slash symbol gets added to the figured bass glyphs.
Werner
Le jeudi 17 août 2023 à 12:28 +0200, Lukas-Fabian Moser a écrit :
> (The even friendlier syntax variant would require changing the
> lexer/parser, I think.)
Why don't you just do
<"/">
?
Obviously, you can customize it with
\version "2.25.7"
slashMarkup =
\markup
\beam #0.5 #2.0 #0.3
> From Förster's book:
> https://www.digitale-sammlungen.de/view/bsb10527178?page=64 ex. 141
> I also attach an example from his "Practische Beyspiele", in which a
> slightly different layout is being used in which the slash and the
> figure are put separately over their respective notes.
>
> Of
Folks (& especially: Dear Werner),
in his "Anleitung zum Generalbasse" (and the accompanying "Practische
Beyspiele") from the early 1800s, E. A. Förster uses a "slash" symbol in
figured bass to denote a chord that is being described relative not to
the
issues.
>>
>> If a tool like that already exists? would be great :-)
>>
>> Eef
>>
>>
>>
>>
>>
>> Op 16 jul. 2023, om 10:33 heeft Vaughan McAlley
>> mailto:vaug...@mcalley.net.au>> het volgende
>> geschreven:
>>
a tool like that already exists? would be great :-)
>
> Eef
>
>
>
>
>
> Op 16 jul. 2023, om 10:33 heeft Vaughan McAlley
> mailto:vaug...@mcalley.net.au>> het volgende
> geschreven:
>
> I wrote a script in Lua to check MIDI files for consecutives. It as
ecutives. It assumes one
voice per track, so may not suit your needs for figured bass. I need to make it
more user-friendly, but would be happy to do so if anyone is interested.
Congratulations to Thomas Tallis for having no consecutive fifths at all in
Spem in alium!
Vaughan
On Sat, 15 Jul 2023 a
Op 16 jul. 2023, om 10:33 heeft Vaughan McAlley
mailto:vaug...@mcalley.net.au>> het volgende geschreven:
I wrote a script in Lua to check MIDI files for consecutives. It assumes one
voice per track, so may not suit your needs for figured bass. I need to make it
more user-friendly, but
I wrote a script in Lua to check MIDI files for consecutives. It assumes
one voice per track, so may not suit your needs for figured bass. I need to
make it more user-friendly, but would be happy to do so if anyone is
interested.
Congratulations to Thomas Tallis for having no consecutive fifths
Hi all,
On Fri, Jul 14, 2023 at 6:36 PM Jean Abou Samra wrote:
> Le vendredi 14 juillet 2023 à 21:08 +, Eef Weenink a écrit :
>
> Maybe somebody already made a script for this:
>
> In figured bass there are two fundamental rules: Avoid parallell octaves
> and or fifhts
On Sat, Jul 15, 2023 at 1:26 AM Richard Shann
wrote:
> On Fri, 2023-07-14 at 21:08 +, Eef Weenink wrote:
> > Maybe somebody already made a script for this:
> >
> > In figured bass there are two fundamental rules: Avoid parallell
> > octaves and or fifhts.
> >
On Fri, 2023-07-14 at 21:08 +, Eef Weenink wrote:
> Maybe somebody already made a script for this:
>
> In figured bass there are two fundamental rules: Avoid parallell
> octaves and or fifhts.
> So it would be nice to have some scipts what checks for this.
FWIW
There is a s
Le vendredi 14 juillet 2023 à 21:08 +, Eef Weenink a écrit :
> Maybe somebody already made a script for this:
>
> In figured bass there are two fundamental rules: Avoid parallell octaves and
> or fifhts.
> So it would be nice to have some scipts what checks for this. So if tw
Maybe somebody already made a script for this:
In figured bass there are two fundamental rules: Avoid parallell octaves and or
fifhts.
So it would be nice to have some scipts what checks for this. So if two voices
have a distance of a fifth or octave, the next chord is checked if the same two
On Sat, 2023-01-14 at 18:50 +0100, Jean Abou Samra wrote:
> Le 14/01/2023 à 18:27, Richard Shann a écrit :
> > I didn't get a response to this email,
>
> ?? You got a reponse from Werner last Monday. While there can be
> distribution delays on this list, you were in the direct recipients
> of
>
Le 14/01/2023 à 18:27, Richard Shann a écrit :
I didn't get a response to this email,
?? You got a reponse from Werner last Monday. While there can be
distribution delays on this list, you were in the direct recipients of
the email so it is a mystery if it didn't reach you.
You can always r
I didn't get a response to this email, but I stumbled across this the
presence of these glyphs
fattened.four
fattened.four.alt
at
https://lilypond.org/doc/v2.24/Documentation/notation/the-emmentaler-font#figured-bass-symbol-glyphs
and it would seem that the change to figured bass goi
> The figure "4" in figured bass is coming out with a stunted upright in
> the new release
>
> 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
The figure "4" in figured bass is coming out with a stunted upright in
the new release
8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
%
Le 13/06/2022 à 07:31, Werner LEMBERG a écrit :
I see that the function also listens to `basic-distance` (probably
from `VerticalAxisGroup`), but I wasn't able to trigger it – most
probably, this code part is not specific to figured bass.
I think this should do (I can elaborate when I
>> I see that the function also listens to `basic-distance` (probably
>> from `VerticalAxisGroup`), but I wasn't able to trigger it – most
>> probably, this code part is not specific to figured bass.
>
> I think this should do (I can elaborate when I have more
Jean Abou Samra writes:
[...]
> staff-padding also works for this purpose. However, it may be trumped by
> other settings if they lead to larger offset values. You likely need
> to reduce padding and outside-staff-padding. This changes the spacing
> in situations where there are collisions. Inde
Hi Jean,
Thanks for this really in-depth explanation! Despite having used Lilypond for
twenty years, and RTFineM[s] multiple times, in great depth, your
analysis/presentation contained new information/insights for me.
> If a letter protrudes on the bottom like "g"
> (not sure how this would be
OK, trying to correct myself and articulate a little more coherent
thoughts this time. Sorry, I was hearing about election results in
France at the same time and was distracted.
I wrote:
Le 12/06/2022 à 21:32, Jean Abou Samra a écrit :
Le 12/06/2022 à 21:08, Kieren MacMillan a écrit :
Hi Davi
Hi Jean,
Sorry I didn’t respond to this:
> For a start, this can be useful:
> {
> \override Score.RehearsalMark.Y-offset = 4
> \mark \markup { agt } g'1
> \mark \markup { aht } g'1
> \mark \markup { agt } g'1
> }
Well, yes… and I’ve used that mechanism in my scores. My frustration is tha
Hi Jean,
> I don't understand how staff-padding relates to this discussion.
It relates to the discussion as follows:
— when one wants to align TextScripts above the staff to their baseline(s), one
apparently uses staff-padding;
— when one wants to align RehearsalMarks (or, probably, MetronomeMar
p.s. To be clear, \override-ing Score.RehearsalMark.staff-padding does nothing,
which is a related but separate point of inconsistency.
— Kieren
> On Jun 12, 2022, at 3:37 PM, Kieren MacMillan
> wrote:
>
> Hi all,
>
> Sorry for the typo in the last email… Here’s a “correct incantation”:
>
>
Hi all,
Sorry for the typo in the last email… Here’s a “correct incantation”:
\version "2.23.4"
{
\override Score.RehearsalMark.padding = #2
\mark \markup { agt } g'1
\mark \markup { aht } g'1
\mark \markup { agt } g'1
}
I put “correct incantation” in quotes because it moves the RehearsalMar
Le 12/06/2022 à 21:32, Jean Abou Samra a écrit :
Le 12/06/2022 à 21:08, Kieren MacMillan a écrit :
Hi David,
I have problems believing we did not have this particular discussion
already since there is a documented setting for it.
I don't understand how staff-padding relates to this discu
Le 12/06/2022 à 21:08, Kieren MacMillan a écrit :
Hi David,
I have problems believing we did not have this particular discussion
already since there is a documented setting for it.
I don't understand how staff-padding relates to this discussion.
It counts from the reference point of the mark
Hi David,
> I have problems believing we did not have this particular discussion
> already since there is a documented setting for it.
The problem isn’t really whether there’s a documented setting or not… It’s
whether that documented setting is consistently applied and behaves in the way
most u
Kieren MacMillan writes:
> Hi Jean,
>
>> Then I don't understand the problem. What characteristic
>> of baseline-skip do you wish? Is it that it counts from
>> the origin of each markup and somehow this distance is
>> more convenient for you to provide? Is it that it ignores
>> the extents of the
mechanism exists and
isn’t sufficiently well exposed/documented/promoted.
It looks superficially similar, but I think it is a completely
different mechanism behind the scenes. AFAICS, the vertical spacing
of vertically stacked figured bass elements uses a special routine
`ly:align-interface::align-to
fficiently well exposed/documented/promoted.
It looks superficially similar, but I think it is a completely
different mechanism behind the scenes. AFAICS, the vertical spacing
of vertically stacked figured bass elements uses a special routine
`ly:align-interface::align-to-minimum-dis
> Then I don't understand the problem. What characteristic of
> baseline-skip do you wish? Is it that it counts from the origin of
> each markup and somehow this distance is more convenient for you to
> provide? Is it that it ignores the extents of the markups?
I want equal vertical spacing of li
Hi Jean,
> Then I don't understand the problem. What characteristic
> of baseline-skip do you wish? Is it that it counts from
> the origin of each markup and somehow this distance is
> more convenient for you to provide? Is it that it ignores
> the extents of the markups?
>
> Could you explain th
Le 12/06/2022 à 17:55, Werner LEMBERG a écrit :
Nope, this only changes the padding (i.e., the whitespace between the
bottom of the upper and the top of the lower element). What I want is
vertical stacking as if it were done with the `\column` markup command
– which respects `baseline-skip`.
>> Consider the following example:
>>
>> ```
>> \figures {
>>
>> }
>> ```
>>
>> As can be seen in the attached image, the elements are separated by
>> padding only; they are not vertically spaced using `baseline-skip`
>> or something similar.
>>
>> How can I change that?
>
> Like this?
>
> \v
Le 12/06/2022 à 17:36, Werner LEMBERG a écrit :
Consider the following example:
```
\figures {
}
```
As can be seen in the attached image, the elements are separated by
padding only; they are not vertically spaced using `baseline-skip` or
something similar.
How can I change that?
Like
Consider the following example:
```
\figures {
}
```
As can be seen in the attached image, the elements are separated by
padding only; they are not vertically spaced using `baseline-skip` or
something similar.
How can I change that?
Werner
From: Jon Arnold
Date: Friday, October 15, 2021 at 7:39 PM
To: Carl Sorensen
Cc: Lukas-Fabian Moser , lilypond-user
Subject: Re: Override start of figured bass continuation line
Ah, I think I might have removed the \once command by mistake.
That would explain it.
Carl
ypond-user@gnu.org>
> *Subject: *Re: Override start of figured bass continuation line
>
>
>
> Thank you both. Carl's solution seems to shorten the right side as well,
> so I think I will use Lukas's.
>
>
>
> I’m not trying to argue for my solution, but I
From: Jon Arnold
Date: Friday, October 15, 2021 at 4:43 PM
To: Carl Sorensen
Cc: Lukas-Fabian Moser , lilypond-user
Subject: Re: Override start of figured bass continuation line
Thank you both. Carl's solution seems to shorten the right side as well, so I
think I will use Lukas's
ct 15, 2021 at 2:43 PM Carl Sorensen wrote:
>
>>
>>
>>
>>
>> *From: *lilypond-user > gmail@gnu.org> on behalf of Jon Arnold
>> *Date: *Friday, October 15, 2021 at 1:14 PM
>> *To: *Lukas-Fabian Moser
>> *Cc: *lilypond-user
>>
, 2021 at 1:14 PM
> *To: *Lukas-Fabian Moser
> *Cc: *lilypond-user
> *Subject: *Re: Override start of figured bass continuation line
>
>
>
> Here's an example:
>
> \version "2.22.1"
>
> \score {
> \new Staff {
> {
> <<
From: lilypond-user
on behalf of Jon Arnold
Date: Friday, October 15, 2021 at 1:14 PM
To: Lukas-Fabian Moser
Cc: lilypond-user
Subject: Re: Override start of figured bass continuation line
Here's an example:
\version "2.22.1"
\score {
\new Staff {
{
<<
Hi Jon,
Am 15.10.21 um 21:10 schrieb Jon Arnold:
Here's an example:
\version "2.22.1"
\score {
\new Staff {
{
<<
{f''8 e'' d'' c'' b'2 |
f''8 e'' d'' c'' b'2 }
\new FiguredBass {
\figuremode {
\bassFigureExtendersOn
<[_!]>8 <_!>
something in between). I do not
want the note spacing of the second measure.
On Fri, Oct 15, 2021 at 1:59 PM Lukas-Fabian Moser wrote:
> Hi Jon,
> Am 15.10.21 um 20:29 schrieb Jon Arnold:
>
> Hi folks-
>
> I have some figured bass continuation lines like this:
>
> \set St
Hi Jon,
Am 15.10.21 um 20:29 schrieb Jon Arnold:
Hi folks-
I have some figured bass continuation lines like this:
\set Staff.implicitBassFigures = #'(99)
\bassFigureExtendersOn
<99> q8
My teacher is asking me to move the start of it over to the right (but
not move th
Hi folks-
I have some figured bass continuation lines like this:
\set Staff.implicitBassFigures = #'(99)
\bassFigureExtendersOn
<99> q8
My teacher is asking me to move the start of it over to the right (but not
move the end of it). How can I do this with an override? I know I can d
have the figures above the staff now. I
looked at the list of parameters I can set for the figured bass engraver,
http://lilypond.org/doc/v2.19/Documentation/internals/figured_005fbass_005fengraver
, and the position of alterations is there, but the position of the figures
itself relative to the st
On Sun, Aug 30, 2020 at 8:57 AM Leszek Wroński wrote:
> Hello Experts,
>
> if there's a c2 in the bc voice and the figures are "<7>4 <6>", the '7'
> ends up higher than the '6':
> https://www.dropbox.com/s/f45idpgtnd1jjch/figured_bass.png
>
> (I'm using 2.20.)
>
> Is there a method of telling Lil
Hello Experts,
if there's a c2 in the bc voice and the figures are "<7>4 <6>", the '7'
ends up higher than the '6':
https://www.dropbox.com/s/f45idpgtnd1jjch/figured_bass.png
(I'm using 2.20.)
Is there a method of telling Lilypond to align the figures horizontally in
the space of, say, a measure
rested in getting
more ideas. What exactly does that text expander do for you, and what
do you have to do to prepare it doing so?
BestUrs
> If you’re interested I can send you privately my score of
> Telemann-SSGb-13-Die_vergessene_Phyllis.
>
> Best regards,
>
> Robert Blackstone
&
Mar 2020, at 14:43, Derek Remeš wrote:
>
> Hello,
>
> I’m a new user as of today. I’ve input my first score in LilyPond today (a
> Telemann song) and I can’t figure out how to enter the figured bass directly
> into the staff context, as described here
> <http://lily
abble.com/Another-Figured-Bass-problem-tp212469p212514.html
Best
Lukas
Sonntag, den 08.03.2020, 14:43 +0100 schrieb Derek Remeš:
> Hello,
>
> I’m a new user as of today. I’ve input my first score in LilyPond
> today (a Telemann song) and I can’t figure out how to enter the
> figured bass directly into the staff context, as
> described here becau
(a
> Telemann song) and I can’t figure out how to enter the figured bass
> directly into the staff context, as described here
> <http://lilypond.org/doc/v2.19/Documentation/notation/figured-bass> because
> I’ve
> used Frescobaldi’s template, which has a different setup. The pro
Hi Derek,
I’m a new user as of today.
This is great news - and I'm quite happy that my (and my colleagues')
introductions seem not to have been too deterrent. :-)
I’ve input my first score in LilyPond today (a Telemann song) and I
can’t figure out how to enter the figured bass dir
Hello,I’m a new user as of today. I’ve input my first score in LilyPond today (a Telemann song) and I can’t figure out how to enter the figured bass directly into the staff context, as described here because I’ve used Frescobaldi’s template, which has a different setup. The problem is that the
Carl wrote:
>
> I'm not sure exactly what you want, but I decided to try this.
> Is this what you want?
>
Yes, exactly. As a lilypond newbie I am still coming to terms with
some of the syntactical feeatures of the program, like the << >>
pairings.
.. mark.
Kieren wrote:
>
> Attached, below, is the way I would code your example. You’ll see
> that I’ve separated the definition of the notes (etc.) from the
> score ― I find it much easier to parse that way.
>
Wow! I didn't know you could do that. Thanks for the tip.
.. mark.
__
On 1/8/19, 6:47 PM, "Mark Probert" wrote:
Which produces the attached. Any ideas on how I can get the figures (or
the notes) all coming together nicely?
I'm not sure exactly what you want, but I decided to try this.
Is this what you want?
\score {
\new StaffGroup <<
s_lower >>
\new FiguredBass \theFigures
>>
}
%%% SNIPPET ENDS
> On Jan 8, 2019, at 8:47 PM, Mark Probert wrote:
>
> Hi, everyone.
>
> I'm having a problem getting LilyPond to do a figured bass. I've read
> the manual, and followed the examples,
Hi, everyone.
I'm having a problem getting LilyPond to do a figured bass. I've read
the manual, and followed the examples, but I have clearly missed
something out.
Here is the code I am currently using
---< cut >---
\score {
\new StaffGroup <<
\new Sta
How do I place text next to the Figured Bass part? I can get one on top of
the other but can't figure out how to get them next to each other. For an
analysis I'm try to put the bass's solfege syllable under the bass clef
immediately followed by figured bass numbers so it would basi
mari+lilypond wrote
> Hi Torsten,
>
> your answer did overlap with my last mail. It seems that your suggestion
> solves my questions in a way as I imagined.
Hi Markus,
I had some difficulties submitting my answer and, in the end, it appeared
four times - sorry for that.
Just a remark regarding
also a singing voice
>> with
>> lyrics) and in the very first example (\context Staff =) dynamic was
>> drawn above figured bass and now below. How can I swap both in the
>> example below?
>
> Hi Markus,
>
> Beyond the technical solution, it's quite challenging
mari+lilypond wrote
> I use \dynamicUp (because it's not only cello but also a singing voice
> with
> lyrics) and in the very first example (\context Staff =) dynamic was
> drawn above figured bass and now below. How can I swap both in the
> example below?
Hi Markus,
s not only cello but also a singing voice with
> lyrics) and in the very first example (\context Staff =) dynamic was
> drawn above figured bass and now below. How can I swap both in the
> example below?
>
> \version "2.19.82"
>
> violin = \relative c'
mari+lilypond wrote
> I use \dynamicUp (because it's not only cello but also a singing voice
> with
> lyrics) and in the very first example (\context Staff =) dynamic was
> drawn above figured bass and now below. How can I swap both in the
> example below?
Hi Markus,
mari+lilypond wrote
> I use \dynamicUp (because it's not only cello but also a singing voice
> with
> lyrics) and in the very first example (\context Staff =) dynamic was
> drawn above figured bass and now below. How can I swap both in the
> example below?
Hi Markus,
mari+lilypond wrote
> I use \dynamicUp (because it's not only cello but also a singing voice
> with
> lyrics) and in the very first example (\context Staff =) dynamic was
> drawn above figured bass and now below. How can I swap both in the
> example below?
Hi Markus,
(because it's not only cello but also a singing voice with
lyrics) and in the very first example (\context Staff =) dynamic was
drawn above figured bass and now below. How can I swap both in the
example below?
\version "2.19.82"
violin = \relative c'' {
e4 f4 g4 a4
}
Hi Markus,
thank you for your help. Your suggestion is a step in the right
direction, but now I do have the problem that the figured bass is more
nearby violin voice than cello voice:
\version "2.19.82"
violin = \relative c'' {
e4 f4 g4 a4
}
cello = \relative c' {
Hi Pierre,
thank you for your help. Your suggestion is a step in the right
direction, but now I do have the problem that the figured bass is more
nearby violin voice than cello voice:
\version "2.19.82"
violin = \relative c'' {
e4 f4 g4 a4
}
cello = \relative c'
ers,
Pierre
Le mar. 14 août 2018 à 14:33, a écrit :
> Hi all,
>
> if figured bass is drawn below a system it is automatically centered
> vertically in one line. How can I achieve the same if figured bass is
> above a system (see example below)?
>
> If it can not be don
Hi all,
if figured bass is drawn below a system it is automatically centered
vertically in one line. How can I achieve the same if figured bass is
above a system (see example below)?
If it can not be done automatically, how can I do it manually?
Any help is welcome
Markus
version "2.
-11 00:40, Brian Barker wrote:
At 00:09 11/08/2018 -0400, Nobody Noname wrote:
From the Lilypond manual,
"http://lilypond.org/doc/v2.19/Documentation/notation/figured-bass";
I use the following code for figured bass.
(The code is 3-steps above "Predefined commands" at th
,
"http://lilypond.org/doc/v2.19/Documentation/notation/figured-bass";
I use the following code for figured bass.
(The code is 3-steps above "Predefined commands" at the end)
\new Staff = "myStaff"
\figuremode {
<4>4 <10 6>8 s8
<6 4>4 &
tp://lilypond.org/doc/v2.19/Documentation/notation/figured-bass";
I use the following code for figured bass.
(The code is 3-steps above "Predefined commands" at the end)
\new Staff = "myStaff"
\figuremode {
<4>4 <10 6>
At 00:09 11/08/2018 -0400, Nobody Noname wrote:
From the Lilypond manual,
"http://lilypond.org/doc/v2.19/Documentation/notation/figured-bass";
I use the following code for figured bass.
(The code is 3-steps above "Predefined commands" at the end)
\new Staff = &qu
From the Lilypond manual,
"http://lilypond.org/doc/v2.19/Documentation/notation/figured-bass";
I use the following code for figured bass.
(The code is 3-steps above "Predefined commands" at the end)
\new Staff = "myStaff"
\figuremode {
<4>4 <
1 - 100 of 487 matches
Mail list logo