Re: Edition Engraver and staff changes
Hello Auke,
yes you are right, \change Staff cannot be used with the EE. Some time
ago I tried to make it possible, but it results in a fatal crash of
lilypond if the EE sends such an event. I add this to the issues.
Jan-Peter
Am 14.08.2018 um 21:51 schrieb Partitura Organum:
> Hello all,
>
> In organ music it is quite common that one of the hands plays a part
> that is either to high or to low for the 'common' clefs, but that can
> be perfectly rendered with the alto clef. Not many organists are still
> able to read the alto clef, so I usually make to versions, one with the
> alto clef, and one with the part distributed over two staves (see images
> for an example).
>
>
>
>
>
>
>
>
> Since the notes do not change, only the way they are rendered, I thought
> it would be a good use case for the edition engraver. Problem however
> is that the Edition Engraver references contexts and I cannot tell one
> context to become another. The command 'change Staff' cannot be used
> with the Edition Engraver. Below is my (not so minimal) not-working
> example. Is there a way to tell the Edition Engraver that a part should
> switch Staff? Or is the Edition Engraver not suitable for my use case
> (which means that I should continue to do it manually)?
>
>
> %==
> \include "/oll-core/package.ily"
> \loadPackage edition-engraver
> %\addEdition alto
> \addEdition nonalto
> \consistToContexts #edition-engraver Score.Staff.Voice
>
> righthand = \relative c''{
> a2 a |
> b1 |
> c4 b a2\trill
> }
>
> lefthand = \relative c'{
> f8 e d c d c b a |
> gis8 a b c d e fis gis |
> a8 a, b cis d d, e fis |
> }
>
> pedal = \relative c {
> b2 d |
> e1 |
> a,2 c
> }
>
> lefthandnonalto=\relative c'{
> \clef bass
> \change Staff="right" \voiceTwo f8 e d c d c \change Staff="left"
> \oneVoice b a |
> gis a b c \change Staff="right" \voiceTwo d e fis gis |
> a \change Staff="left" \oneVoice a, b cis d d, e fis |
> }
>
>
> \editionMod alto 1 0/4 left.Voice.A \clef alto
>
> \editionMod nonalto 1 0/4 right.Voice.A \voiceOne
> \editionMod nonalto 1 0/4 left.Voice.A \change Staff="right"
> \editionMod nonalto 1 0/4 left.Voice.A \voiceTwo
>
> \score {
> <<
> \new Staff = "right" \with {
> \editionID right
> }
> \new Voice { \righthand }
>
> \new Staff = "left" \with {
> \editionID left
> }
> %\new Voice { \lefthand}
> \new Voice { \lefthandnonalto}
>
> \new Staff {
> \clef bass \pedal
> }
> >>
> }
> %===
>
> Regards,
> Auke
>
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Include path syntax on Mac
On Wed 15 Aug 2018 at 00:58:51 (+0200), Urs Liska wrote: > Am 14.08.2018 um 22:21 schrieb David Wright: > >On Tue 14 Aug 2018 at 21:31:18 (+0200), Urs Liska wrote: > >>Hi all, > >> > >>it seems LilyPond on Windows requires paths passed to the -I command > >>line option to have a trailing slash while LilyPond on Linux doesn't > >>seem to care whether there is or not (see > >>https://github.com/wbsoft/frescobaldi/issues/1094). It seems a fix > >>to the issue in Frescobaldi is to ensure there's a trailing slash to > >>the paths, which makes it work on Windows and Linux. > >> > >>Before merging this code I'd need to know whether Mac also doesn't > >>care about the trailing slash. Obviously it accepts paths without > >>slashes, but if it should not accept them *with* slashes I'd need to > >>make the changed code aware of the OS. > >> > >>Could someone please test (or tell me directly) whether it makes a > >>difference if a path passed to -I has a trailing slash or not on > >>Mac? > >It's worth bearing in mind that AFAICT -I can take a relative path. > > Yes, it can. > Although it's not really relevant for my use case as Frescobaldi (at > least when used as intended) uses absolute paths. > > >In windows, D: and D:\ can be different directories depending on > >circumstances. No idea about the Mac, though. > > > >Is LP constructing filenames merely by concatenating part1, delimiter > >and part2? This usually works but isn't the Right Way, hence functions > >like Python's os.path.join(). > > I don't know what *LilyPond* does, but in Frescobaldi the path that > is stored by default is the result of a PyQt dialog's choice, so we > *can* expect it to be correct with regard to the actual OS. It's > just that this doesn't add a trailing slash to the path, and > LilyPond seems to choke on that on Windows. Then LP needs fixing. Sorry, but insisting that users specify directory names with a trailing (back)slash is plain wrong.¹ And, as shown above, mindlessly appending one is worse, as it can change the meaning of what the user wrote. Also, if someone writes -I D:foo and you want to convert it to an absolute path, it's necessary to find out what the current directory is on drive D: which may have no relationship to the current directory on the current drive (ie if D: is not the current drive). > (you can write *anything* in the line edit in Frescobaldi, so you > can also make it break, but I don't think we have to deal with wrong > input here.) AFAIK the rules for writing valid filenames and directory names in windows are well-defined and identical, ie the only way to distinguish a file from a directory by its name is to ask the OS. ¹Note that I'm not saying a user *can't* specify a trailing (back)slash on a directory name; the program can merely strip it (as long as it's not syntactically a root directory). Cheers, David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Include path syntax on Mac
Am 15.08.2018 um 00:34 schrieb Hans Åberg: On 14 Aug 2018, at 21:31, Urs Liska wrote: Could someone please test (or tell me directly) whether it makes a difference if a path passed to -I has a trailing slash or not on Mac? It seems to not matter, tried on MacOS 10.13.6. That was what I expected. Thank you for testing Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Include path syntax on Mac
Am 14.08.2018 um 22:21 schrieb David Wright: On Tue 14 Aug 2018 at 21:31:18 (+0200), Urs Liska wrote: Hi all, it seems LilyPond on Windows requires paths passed to the -I command line option to have a trailing slash while LilyPond on Linux doesn't seem to care whether there is or not (see https://github.com/wbsoft/frescobaldi/issues/1094). It seems a fix to the issue in Frescobaldi is to ensure there's a trailing slash to the paths, which makes it work on Windows and Linux. Before merging this code I'd need to know whether Mac also doesn't care about the trailing slash. Obviously it accepts paths without slashes, but if it should not accept them *with* slashes I'd need to make the changed code aware of the OS. Could someone please test (or tell me directly) whether it makes a difference if a path passed to -I has a trailing slash or not on Mac? It's worth bearing in mind that AFAICT -I can take a relative path. Yes, it can. Although it's not really relevant for my use case as Frescobaldi (at least when used as intended) uses absolute paths. In windows, D: and D:\ can be different directories depending on circumstances. No idea about the Mac, though. Is LP constructing filenames merely by concatenating part1, delimiter and part2? This usually works but isn't the Right Way, hence functions like Python's os.path.join(). I don't know what *LilyPond* does, but in Frescobaldi the path that is stored by default is the result of a PyQt dialog's choice, so we *can* expect it to be correct with regard to the actual OS. It's just that this doesn't add a trailing slash to the path, and LilyPond seems to choke on that on Windows. (you can write *anything* in the line edit in Frescobaldi, so you can also make it break, but I don't think we have to deal with wrong input here.) Urs Cheers, David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Include path syntax on Mac
> On 14 Aug 2018, at 21:31, Urs Liska wrote: > > Could someone please test (or tell me directly) whether it makes a difference > if a path passed to -I has a trailing slash or not on Mac? It seems to not matter, tried on MacOS 10.13.6. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Include path syntax on Mac
On Tue 14 Aug 2018 at 21:31:18 (+0200), Urs Liska wrote: > Hi all, > > it seems LilyPond on Windows requires paths passed to the -I command > line option to have a trailing slash while LilyPond on Linux doesn't > seem to care whether there is or not (see > https://github.com/wbsoft/frescobaldi/issues/1094). It seems a fix > to the issue in Frescobaldi is to ensure there's a trailing slash to > the paths, which makes it work on Windows and Linux. > > Before merging this code I'd need to know whether Mac also doesn't > care about the trailing slash. Obviously it accepts paths without > slashes, but if it should not accept them *with* slashes I'd need to > make the changed code aware of the OS. > > Could someone please test (or tell me directly) whether it makes a > difference if a path passed to -I has a trailing slash or not on > Mac? It's worth bearing in mind that AFAICT -I can take a relative path. In windows, D: and D:\ can be different directories depending on circumstances. No idea about the Mac, though. Is LP constructing filenames merely by concatenating part1, delimiter and part2? This usually works but isn't the Right Way, hence functions like Python's os.path.join(). Cheers, David. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Edition Engraver and staff changes
Hello Auke Am 14.08.2018 um 21:51 schrieb Partitura Organum: Hello all, In organ music it is quite common that one of the hands plays a part that is either to high or to low for the 'common' clefs, but that can be perfectly rendered with the alto clef. Not many organists are still able to read the alto clef, so I usually make to versions, one with the alto clef, and one with the part distributed over two staves (see images for an example). ... Since the notes do not change, only the way they are rendered, I thought it would be a good use case for the edition engraver. Problem however is that the Edition Engraver references contexts and I cannot tell one context to become another. The command 'change Staff' cannot be used with the Edition Engraver. Below is my (not so minimal) not-working example. Is there a way to tell the Edition Engraver that a part should switch Staff? Or is the Edition Engraver not suitable for my use case (which means that I should continue to do it manually)? I have not tested your example but believe you that it isn't working. I don't have insight in this kind of inner workings of the edition-engraver, but I hope it should be possible to make that work (which wouldn't be an input syntax thing but a task for the edition-engraver to explicitly support). I suggest you either wait for Jan-Peter to give his opinion on this or just go forward and add this as a feature request on https://github.com/openlilylib/edition-engraver/issues. Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Edition Engraver and staff changes
Hello all,
In organ music it is quite common that one of the hands plays a part
that is either to high or to low for the 'common' clefs, but that can
be perfectly rendered with the alto clef. Not many organists are still
able to read the alto clef, so I usually make to versions, one with the
alto clef, and one with the part distributed over two staves (see images
for an example).
Since the notes do not change, only the way they are rendered, I thought
it would be a good use case for the edition engraver. Problem however is
that the Edition Engraver references contexts and I cannot tell one
context to become another. The command 'change Staff' cannot be used
with the Edition Engraver. Below is my (not so minimal) not-working
example. Is there a way to tell the Edition Engraver that a part should
switch Staff? Or is the Edition Engraver not suitable for my use case
(which means that I should continue to do it manually)?
%==
\include "/oll-core/package.ily"
\loadPackage edition-engraver
%\addEdition alto
\addEdition nonalto
\consistToContexts #edition-engraver Score.Staff.Voice
righthand = \relative c''{
a2 a |
b1 |
c4 b a2\trill
}
lefthand = \relative c'{
f8 e d c d c b a |
gis8 a b c d e fis gis |
a8 a, b cis d d, e fis |
}
pedal = \relative c {
b2 d |
e1 |
a,2 c
}
lefthandnonalto=\relative c'{
\clef bass
\change Staff="right" \voiceTwo f8 e d c d c \change Staff="left"
\oneVoice b a |
gis a b c \change Staff="right" \voiceTwo d e fis gis |
a \change Staff="left" \oneVoice a, b cis d d, e fis |
}
\editionMod alto 1 0/4 left.Voice.A \clef alto
\editionMod nonalto 1 0/4 right.Voice.A \voiceOne
\editionMod nonalto 1 0/4 left.Voice.A \change Staff="right"
\editionMod nonalto 1 0/4 left.Voice.A \voiceTwo
\score {
<<
\new Staff = "right" \with {
\editionID right
}
\new Voice { \righthand }
\new Staff = "left" \with {
\editionID left
}
%\new Voice { \lefthand}
\new Voice { \lefthandnonalto}
\new Staff {
\clef bass \pedal
}
>>
}
%===
Regards,
Auke
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Include path syntax on Mac
Hi all, it seems LilyPond on Windows requires paths passed to the -I command line option to have a trailing slash while LilyPond on Linux doesn't seem to care whether there is or not (see https://github.com/wbsoft/frescobaldi/issues/1094). It seems a fix to the issue in Frescobaldi is to ensure there's a trailing slash to the paths, which makes it work on Windows and Linux. Before merging this code I'd need to know whether Mac also doesn't care about the trailing slash. Obviously it accepts paths without slashes, but if it should not accept them *with* slashes I'd need to make the changed code aware of the OS. Could someone please test (or tell me directly) whether it makes a difference if a path passed to -I has a trailing slash or not on Mac? Thanks Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center figured bass vertically
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 the difference between \new and \context: Using \context with the (existing) Staff's name will pass the musical expression to this Staff. That's why your attempts increasing vertical spacing variables failed - both notes and bass figures belong to the same Staff, so any inter-staff spacing will have no effect. \new, in contrast to that, will always create a new context (even if its name already exists). All the best, Torsten -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center figured bass vertically
Hi Torsten,
your answer did overlap with my last mail. It seems that your suggestion
solves my questions in a way as I imagined.
Many thanks to all!
Markus
On 14.08.2018 19:15, Torsten Hämmerle wrote:
> 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,
>
> Beyond the technical solution, it's quite challenging to have lyrics,
> dynamics, and bass figures associated with one stave in a clearly readable
> and aesthetic way.
>
> The problem with Phil's solution is that the bass figures get their "own
> line", so that the dynamics of the stave below will always stay below the
> bass figures. The "own separate line" is the reason for the nice vertical
> alignment.
> You might create a separate dynamics context and put it on top of the bass
> figures.
>
> In your original example (using the same Staff context for notes, dynamics,
> and bass figures) you didn't like the alignment, because the bass figures
> didn't share a common baseline.
> This, however, can be achieved as usual: by setting staff-padding large
> enough that all the figures' baselines are aligned at the same vertical
> position:
>
>
> %%%
> \version "2.19.82"
>
> violin = \relative c'' {
> e4 f4 g4 a4
> }
>
> cello = \relative c' {
> \dynamicUp
> c2. \p g4
> }
>
> figuredBass = \figuremode {
> \override Staff.BassFigureAlignmentPositioning.direction = #UP
> \override Staff.BassFigureAlignmentPositioning.staff-padding = #4
> <3>4 <4>2 <3>4
> }
>
> lyrtxt = \lyricmode { Please don’t! }
>
> \score {
> <<
> \new Staff = "violin" {
> \clef treble \violin
> }
> \new Staff = "cello" \new Voice = "melody" {
> \clef bass \cello
> }
> \context Staff = "cello" \figuredBass
> \new Lyrics \lyricsto "melody" \lyrtxt
> >>
> }
> %%%
>
>
>
>
> Drawback: that way, the bass figures will keep at least the vertical
> distance set by staff-padding, even if there are no notes above the stave.
> Stacking dynamics even on top, it is not clear what save the dynamics belong
> to if they come too close to the stave above. Increasing the stave distances
> might require a lot of space and one could think of even using separate
> saves for cello and vocals.
>
> But maybe this is of any help, at all…
>
> All the best,
> Torsten
>
>
>
> --
> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center figured bass vertically
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,
Beyond the technical solution, it's quite challenging to have lyrics,
dynamics, and bass figures associated with one stave in a clearly readable
and aesthetic way.
The problem with Phil's solution is that the bass figures get their "own
line", so that the dynamics of the stave below will always stay below the
bass figures. The the "own separate line" is the reason for the nice
vertical alignment.
You might create a separate dynamics context and put it on top of the bass
figures.
In your original example (using the same Staff context for notes, dynamics,
and bass figures) you didn't like the alignment, because the bass figures
didn't share a common baseline.
This, however, can be achieved as usual: by setting staff-padding large
enough that all the figures' baselines are aligned at the same vertical
position:
%%%
\version "2.19.82"
violin = \relative c'' {
e4 f4 g4 a4
}
cello = \relative c' {
\dynamicUp
c2. \p g4
}
figuredBass = \figuremode {
\override Staff.BassFigureAlignmentPositioning.direction = #UP
\override Staff.BassFigureAlignmentPositioning.staff-padding = #4
<3>4 <4>2 <3>4
}
lyrtxt = \lyricmode { Please don’t! }
\score {
<<
\new Staff = "violin" {
\clef treble \violin
}
\new Staff = "cello" \new Voice = "melody" {
\clef bass \cello
}
\context Staff = "cello" \figuredBass
\new Lyrics \lyricsto "melody" \lyrtxt
>>
}
%%%
Drawback: that way, the bass figures will keep at least the vertical
distance set by staff-padding, even if there are no notes above the stave.
Stacking dynamics even on top, it is not clear what save the dynamics belong
to if they come too close to the stave above. Increasing the stave distances
might require a lot of space and one could think of even using separate
saves for cello and vocals.
But maybe this is of any help, at all…
All the best,
Torsten
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center figured bass vertically
Hi,
I'm just trying another way: Coming from the very first example I try to
override some context properties increasing the minimum-distance to
stave so that the lowest <4> is rising up. Unfortunately it does not
work :-(
I'm somehow confused about the correct property names. Or am I
completely on the wrong track?
\version "2.19.82"
cello = \relative c' {
f2. f4
}
figuredBass = \figuremode {
<3>4 <4>2 <3>4
}
\score {
<<
\new Staff = continuo
{
\clef bass \cello
}
\context Staff = continuo
\with {
\override VerticalAxisGroup.staff-...-spacing.minimum-distance = #10.0
\override VerticalAxisGroup.nonstaff-...-spacing.minimum-distance
= #10.0
}
\figuredBass
>>
}
On 14.08.2018 16:22, mari+lilyp...@mailbox.org wrote:
> Hi Phil,
>
> On 14.08.2018 15:44, Phil Holmes wrote:
>> It would have been easier if you'd mentioned the violin originally!
>
> Sorry, that's a problem with trying to create a "minimal example". In
> fact I omitted other details which now seems to come relevant: 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?
>
> \version "2.19.82"
>
> violin = \relative c'' {
> e4 f4 g4 a4
> }
>
> cello = \relative c' {
> \dynamicUp
> g2. \p g4
> }
>
> figuredBass = \figuremode {
> <3>4 <4>2 <3>4
> }
>
> \score {
> <<
> \new Staff
> {
> \clef treble \violin
> }
> \new Staff = "cello"
> {
> \clef bass \cello
> }
> \new FiguredBass \with { alignAboveContext = "cello" } \figuredBass
> >>
> }
>
> Many thanks for your help
> Markus
>
>>
>> Try:
>>
>> \new Staff = "cello"
>> {
>> \clef bass \cello
>> }
>> \new FiguredBass \with { alignAboveContext = "cello" } \figuredBass
>>
>>
>>
>> --
>> Phil Holmes
>>
>>
>> - Original Message - From:
>> To: "lilypond-user"
>> Sent: Tuesday, August 14, 2018 2:26 PM
>> Subject: Re: center figured bass vertically
>>
>>
>>> 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' {
>>> g2. g4
>>> }
>>>
>>> figuredBass = \figuremode {
>>> <3>4 <4>2 <3>4
>>> }
>>>
>>> \score {
>>> <<
>>> \new Staff
>>> {
>>> \clef treble \violin
>>> }
>>> \new FiguredBass \figuredBass
>>> \new Staff
>>> {
>>> \clef bass \cello
>>> }
>>> >>
>>> }
>>>
>>> On 14.08.2018 14:47, Pierre Perol-Schneider wrote:
Hi Markus,
Does that help ?
\version "2.19.82"
cello = \relative c' {
f2. f4
}
figuredBass = \figuremode {
<3>4 <4>2 <3>4
}
\score {
<<
\new FiguredBass \figuredBass
\new Staff = continuo
{
\clef bass \cello
}
>>
}
Cheers,
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 done automatically, how can I do it manually?
>
> Any help is welcome
> Markus
>
>
> version "2.19.82"
>
> cello = \relative c' {
> f2. f4
> }
>
> figuredBass = \figuremode {
> <3>4 <4>2 <3>4
> }
>
> \score {
> <<
> \new Staff = continuo
> {
> \clef bass \cello
> }
> \context Staff = continuo
> \figuredBass
> >>
> }
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>>>
>>> ___
>>> lilypond-user mailing list
>>> lilypond-user@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>>
>>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center figured bass vertically
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,
Beyond the technical solution, it's quite challenging to have lyrics,
dynamics, and bass figures associated with one stave in a clearly readable
and aesthetic way.
The problem with Phil's solution is that the bass figures get their "own
line", so that the dynamics of the stave below will always stay below the
bass figures. The the "own separate line" is the reason for the nice
vertical alignment.
You might create a separate dynamics context and put it on top of the bass
figures.
In your original example (using the same Staff context for notes, dynamics,
and bass figures) you didn't like the alignment, because the bass figures
didn't share a common baseline.
This, however, can be achieved as usual: by setting staff-padding large
enough that all the figures' baselines are aligned at the same vertical
position:
%%%
\version "2.19.82"
violin = \relative c'' {
e4 f4 g4 a4
}
cello = \relative c' {
\dynamicUp
c2. \p g4
}
figuredBass = \figuremode {
\override Staff.BassFigureAlignmentPositioning.direction = #UP
\override Staff.BassFigureAlignmentPositioning.staff-padding = #4
<3>4 <4>2 <3>4
}
lyrtxt = \lyricmode { Please don’t! }
\score {
<<
\new Staff = "violin" {
\clef treble \violin
}
\new Staff = "cello" \new Voice = "melody" {
\clef bass \cello
}
\context Staff = "cello" \figuredBass
\new Lyrics \lyricsto "melody" \lyrtxt
>>
}
%%%
Drawback: that way, the bass figures will keep at least the vertical
distance set by staff-padding, even if there are no notes above the stave.
Stacking dynamics even on top, it is not clear what save the dynamics belong
to if they come too close to the stave above. Increasing the stave distances
might require a lot of space and one could think of even using separate
saves for cello and vocals.
But maybe this is of any help, at all…
All the best,
Torsten
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Question about GUB and source code update
Hello, About a month ago I succeeded in getting GUB running and compiling in VirtualBox on my Windows 10 machine. So I have now a working Windows version of Lilypond 2.21 from the source code as it was a month ago. What I'd like to know is: what happens if I run GUB again? Do I then build the same Lilypond version again? Or does GUB automatically refresh the source code and is the result a 'newer' Lilypond? I did run it again, but the version is number is the same, so that's a bit inconclusive. Regards, Auke ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center figured bass vertically
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,
Beyond the technical solution, it's quite challenging to have lyrics,
dynamics, and bass figures associated with one stave in a clearly readable
and aesthetic way.
The problem with Phil's solution is that the bass figures get their "own
line", so that the dynamics of the stave below will always stay below the
bass figures. The "own separate line" is the reason for the nice vertical
alignment.
You might create a separate dynamics context and put it on top of the bass
figures.
In your original example (using the same Staff context for notes, dynamics,
and bass figures) you didn't like the alignment, because the bass figures
didn't share a common baseline.
This, however, can be achieved as usual: by setting staff-padding large
enough that all the figures' baselines are aligned at the same vertical
position:
%%%
\version "2.19.82"
violin = \relative c'' {
e4 f4 g4 a4
}
cello = \relative c' {
\dynamicUp
c2. \p g4
}
figuredBass = \figuremode {
\override Staff.BassFigureAlignmentPositioning.direction = #UP
\override Staff.BassFigureAlignmentPositioning.staff-padding = #4
<3>4 <4>2 <3>4
}
lyrtxt = \lyricmode { Please don’t! }
\score {
<<
\new Staff = "violin" {
\clef treble \violin
}
\new Staff = "cello" \new Voice = "melody" {
\clef bass \cello
}
\context Staff = "cello" \figuredBass
\new Lyrics \lyricsto "melody" \lyrtxt
>>
}
%%%
Drawback: that way, the bass figures will keep at least the vertical
distance set by staff-padding, even if there are no notes above the stave.
Stacking dynamics even on top, it is not clear what save the dynamics belong
to if they come too close to the stave above. Increasing the stave distances
might require a lot of space and one could think of even using separate
saves for cello and vocals.
But maybe this is of any help, at all…
All the best,
Torsten
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center figured bass vertically
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,
Beyond the technical solution, it's quite challenging to have lyrics,
dynamics, and bass figures associated with one stave in a clearly readable
and aesthetic way.
The problem with Phil's solution is that the bass figures get their "own
line", so that the dynamics of the stave below will always stay below the
bass figures. The "own separate line" is the reason for the nice vertical
alignment.
You might create a separate dynamics context and put it on top of the bass
figures.
In your original example (using the same Staff context for notes, dynamics,
and bass figures) you didn't like the alignment, because the bass figures
didn't share a common baseline.
This, however, can be achieved as usual: by setting staff-padding large
enough that all the figures' baselines are aligned at the same vertical
position:
%%%
\version "2.19.82"
violin = \relative c'' {
e4 f4 g4 a4
}
cello = \relative c' {
\dynamicUp
c2. \p g4
}
figuredBass = \figuremode {
\override Staff.BassFigureAlignmentPositioning.direction = #UP
\override Staff.BassFigureAlignmentPositioning.staff-padding = #4
<3>4 <4>2 <3>4
}
lyrtxt = \lyricmode { Please don’t! }
\score {
<<
\new Staff = "violin" {
\clef treble \violin
}
\new Staff = "cello" \new Voice = "melody" {
\clef bass \cello
}
\context Staff = "cello" \figuredBass
\new Lyrics \lyricsto "melody" \lyrtxt
>>
}
%%%
Drawback: that way, the bass figures will keep at least the vertical
distance set by staff-padding, even if there are no notes above the stave.
Stacking dynamics even on top, it is not clear what save the dynamics belong
to if they come too close to the stave above. Increasing the stave distances
might require a lot of space and one could think of even using separate
saves for cello and vocals.
But maybe this is of any help, at all…
All the best,
Torsten
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center figured bass vertically
Hi Phil,
On 14.08.2018 15:44, Phil Holmes wrote:
> It would have been easier if you'd mentioned the violin originally!
Sorry, that's a problem with trying to create a "minimal example". In
fact I omitted other details which now seems to come relevant: 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?
\version "2.19.82"
violin = \relative c'' {
e4 f4 g4 a4
}
cello = \relative c' {
\dynamicUp
g2. \p g4
}
figuredBass = \figuremode {
<3>4 <4>2 <3>4
}
\score {
<<
\new Staff
{
\clef treble \violin
}
\new Staff = "cello"
{
\clef bass \cello
}
\new FiguredBass \with { alignAboveContext = "cello" } \figuredBass
>>
}
Many thanks for your help
Markus
>
> Try:
>
> \new Staff = "cello"
> {
> \clef bass \cello
> }
> \new FiguredBass \with { alignAboveContext = "cello" } \figuredBass
>
>
>
> --
> Phil Holmes
>
>
> - Original Message - From:
> To: "lilypond-user"
> Sent: Tuesday, August 14, 2018 2:26 PM
> Subject: Re: center figured bass vertically
>
>
>> 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' {
>> g2. g4
>> }
>>
>> figuredBass = \figuremode {
>> <3>4 <4>2 <3>4
>> }
>>
>> \score {
>> <<
>> \new Staff
>> {
>> \clef treble \violin
>> }
>> \new FiguredBass \figuredBass
>> \new Staff
>> {
>> \clef bass \cello
>> }
>> >>
>> }
>>
>> On 14.08.2018 14:47, Pierre Perol-Schneider wrote:
>>> Hi Markus,
>>> Does that help ?
>>>
>>> \version "2.19.82"
>>>
>>> cello = \relative c' {
>>> f2. f4
>>> }
>>>
>>> figuredBass = \figuremode {
>>> <3>4 <4>2 <3>4
>>> }
>>>
>>> \score {
>>> <<
>>> \new FiguredBass \figuredBass
>>> \new Staff = continuo
>>> {
>>> \clef bass \cello
>>> }
>>> >>
>>> }
>>>
>>> Cheers,
>>> 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 done automatically, how can I do it manually?
Any help is welcome
Markus
version "2.19.82"
cello = \relative c' {
f2. f4
}
figuredBass = \figuremode {
<3>4 <4>2 <3>4
}
\score {
<<
\new Staff = continuo
{
\clef bass \cello
}
\context Staff = continuo
\figuredBass
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
>>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Running Frescobaldi from Git on Windows
Am 13.08.2018 um 21:47 schrieb eBooks: On Aug 13, 2018, at 10:05 AM, Urs Liska wrote: I have written a Wiki page on how Frescobaldi can be run from its Git repository on Windows: https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-from-Git-on-Windows and I would like Windows users to test that and report any issues. I did it on Windows 7 and using all the default options the various installers suggested. The point in running Frescobaldi from the Git repository is the ability to test new features before release or to run a custom version provided for a project by someone ;-) Is there something similar for macOS users? I have no idea. There are a number of Mac installation instructions (including translations) on the Wiki, but I think they all cover the "release" installation. I *think* that the approach taken in the Windows guide should also work on Mac (pretend you use a released package and replace all the Python files in it - but from what I "know" about Apple's policies I wouldn't bet that they haven't done anything to prevent that kind of "abuse". Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center figured bass vertically
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' {
g2. g4
}
figuredBass = \figuremode {
<3>4 <4>2 <3>4
}
\score {
<<
\new Staff
{
\clef treble \violin
}
\new FiguredBass \figuredBass
\new Staff
{
\clef bass \cello
}
>>
}
You have to tell the FiguredBass that it "belongs to" the staff /below/.
This is either done by issuing
\layout {
\override FiguredBass.VerticalAxisGroup.staff-affinity = #DOWN
}
at the top level of the file, or just for the one FiguredBass context by
adjusting the command that creates it:
\new FiguredBass \with { \override VerticalAxisGroup.staff-affinity =
#DOWN } \figuredBass
instead of
\new FiguredBass \figuredBass
Best
Lukas
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center figured bass vertically
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' {
g2. g4
}
figuredBass = \figuremode {
<3>4 <4>2 <3>4
}
\score {
<<
\new Staff
{
\clef treble \violin
}
\new FiguredBass \figuredBass
\new Staff
{
\clef bass \cello
}
>>
}
On 14.08.2018 14:47, Pierre Perol-Schneider wrote:
> Hi Markus,
> Does that help ?
>
> \version "2.19.82"
>
> cello = \relative c' {
> f2. f4
> }
>
> figuredBass = \figuremode {
> <3>4 <4>2 <3>4
> }
>
> \score {
> <<
> \new FiguredBass \figuredBass
> \new Staff = continuo
> {
> \clef bass \cello
> }
> >>
> }
>
> Cheers,
> 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 done automatically, how can I do it manually?
>>
>> Any help is welcome
>> Markus
>>
>>
>> version "2.19.82"
>>
>> cello = \relative c' {
>> f2. f4
>> }
>>
>> figuredBass = \figuremode {
>> <3>4 <4>2 <3>4
>> }
>>
>> \score {
>> <<
>> \new Staff = continuo
>> {
>> \clef bass \cello
>> }
>> \context Staff = continuo
>> \figuredBass
>> >>
>> }
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: center figured bass vertically
Hi Markus,
Does that help ?
\version "2.19.82"
cello = \relative c' {
f2. f4
}
figuredBass = \figuremode {
<3>4 <4>2 <3>4
}
\score {
<<
\new FiguredBass \figuredBass
\new Staff = continuo
{
\clef bass \cello
}
>>
}
Cheers,
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 done automatically, how can I do it manually?
>
> Any help is welcome
> Markus
>
>
> version "2.19.82"
>
> cello = \relative c' {
> f2. f4
> }
>
> figuredBass = \figuremode {
> <3>4 <4>2 <3>4
> }
>
> \score {
> <<
> \new Staff = continuo
> {
> \clef bass \cello
> }
> \context Staff = continuo
> \figuredBass
> >>
> }
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
center figured bass vertically
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.19.82"
cello = \relative c' {
f2. f4
}
figuredBass = \figuremode {
<3>4 <4>2 <3>4
}
\score {
<<
\new Staff = continuo
{
\clef bass \cello
}
\context Staff = continuo
\figuredBass
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Running Frescobaldi from Git on Windows
On 13-8-2018 19:05, Urs Liska wrote: I have written a Wiki page on how Frescobaldi can be run from its Git repository on Windows: https://github.com/wbsoft/frescobaldi/wiki/Run-Frescobaldi-3-from-Git-on-Windows and I would like Windows users to test that and report any issues. I did it on Windows 7 and using all the default options the various installers suggested. The point in running Frescobaldi from the Git repository is the ability to test new features before release or to run a custom version provided for a project by someone ;-) Best Urs ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user Works like a charm. Tested on Windows 10. Regards, Auke ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
