Re: Place objects by hand
Hi Joram,
2014-11-02 1:46 GMT+01:00 Noeck noeck.marb...@gmx.de:
That would be nice, but your example puts the f on the left of the upper
note and not centralized between the staves (I am using 2.19.15).
Try :
\version 2.19.15
\new PianoStaff
\new Staff { g-_ }
\new Dynamics {
s
-\tweak X-offset #-4
-\tweak Y-offset #-6
\f
}
\new Staff { \clef bass g'-_ }
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Draw a box spanning multiple staves
Hi All, I've slightly changed this snippet. Syntax has been simplyfied : \myBox #width #heigth http://lsr.di.unimi.it/LSR/Item?id=953 Cheers, Pierre ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Mark not visible at the beginning of a line
Hello folks,
In the following sample, how can I have the second mark displayed at the
beginning of the second line?
Adding the hidden measure and bar line trick prevents the new time indication
to be printed at the end of the first line, unfortunately.
Thanks for your help!
JM
—
%%%
\version 2.18.2
{
%%% BASIC ATTEMPT
\time 4/4
\clef bass
\mark\default
c1 | d1 | e1 |
\once \override Score.RehearsalMark.self-alignment-X = #CENTER
\override Score.RehearsalMark.break-visibility = #begin-of-line-invisible
\mark \markup {\musicglyph #scripts.ufermata}
\bar ||
\break | % 65
\mark\default
\tempo \markup{Subito tempo vite} 2 = 120
\time 6/8
b2. |
g2. |
\bar |.
}
{
%%% WITH HIDDEN MEASURE AND BAR LINE
\time 4/4
\clef bass
\mark\default
c1 | d1 | e1 |
\once \override Score.RehearsalMark.self-alignment-X = #CENTER
\override Score.RehearsalMark.break-visibility = #begin-of-line-invisible
\mark \markup {\musicglyph #scripts.ufermata}
\bar ||
\break | % 65
% the hidden measure and bar line
% \cadenzaOn turns off automatic calculation of bar numbers
\cadenzaOn
\once \omit Score.TimeSignature
\once \omit Score.BarNumber
\time 1/64
s64 \bar
\cadenzaOff
\mark\default
\tempo \markup{Subito tempo vite} 2 = 120
\time 6/8
b2. |
g2. |
\bar |.
}
%%%
smime.p7s
Description: S/MIME cryptographic signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unicode Font Issues
Yes, you are right. The unicode fonts failed on 2.19.5. I even tried the new windows 10 and it failed. Now that I know it works on linux (thanks to Bric), I will try to get access to linux using virtual box and try it out. On Sat, Nov 1, 2014 at 2:08 PM, Werner LEMBERG w...@gnu.org wrote: If it works on Linux, I may have a way to get Linux on the windows PC using Virtual Box. On the other hand I am using version 2.18.2 - perhaps I should try 2.19.5 first. I fear that 2.19.5 will fail on Windows as 2.18.2 does. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Where to Download the New Music Fonts?
Very interesting developements here. I love Lilypond! I am fine with the default font at the moment, just wondering if any of these fonts has specific improvements for ancient notation engraving. Thank you, A -- View this message in context: http://lilypond.1069038.n5.nabble.com/Where-to-Download-the-New-Music-Fonts-tp165035p168293.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Where to Download the New Music Fonts?
On 2 Nov 2014, at 11:31, Jayaratna jayara...@gmail.com wrote: Very interesting developements here. I love Lilypond! I am fine with the default font at the moment, just wondering if any of these fonts has specific improvements for ancient notation engraving. Check here: http://www.smufl.org/version/latest/ ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Where to Download the New Music Fonts?
No, I haven't attempted anything related to ancient notation. What kind of improvements are you thinking of? -Abraham Sent from my iPhone On Nov 2, 2014, at 4:31 AM, Jayaratna [via Lilypond] ml-node+s1069038n168293...@n5.nabble.com wrote: Very interesting developements here. I love Lilypond! I am fine with the default font at the moment, just wondering if any of these fonts has specific improvements for ancient notation engraving. Thank you, A If you reply to this email, your message will be added to the discussion below: http://lilypond.1069038.n5.nabble.com/Where-to-Download-the-New-Music-Fonts-tp165035p168293.html To start a new topic under User, email ml-node+s1069038n...@n5.nabble.com To unsubscribe from Lilypond, click here. NAML -- View this message in context: http://lilypond.1069038.n5.nabble.com/Where-to-Download-the-New-Music-Fonts-tp165035p168296.html Sent from the User mailing list archive at Nabble.com.___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Text above the staff
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When I try to move the tenor text above the staff I fail. I have read the
manual pages, but it does not work. What to change?
I have tested the following piece and it compiles, however, not with the result
I want.
Thank you
Bernhard
version 2.19.15
\language deutsch
global = {
\key c \major
\time 3/4
}
tenorTwo = \relative c' {
\global \dynamicUp
s2.| c2 c4|
}
bassTwo = \relative c' {
\global
a2 a4| a g f | e cis e | a ( g) f| e fis d4\rest
}
verseTenor = \lyricmode {
A -- gnus De -- i qui tol -- lis pec -- ca -- ta mun -- di
}
verseBasso = \lyricmode {
A -- gnus De -- i qui tol -- lis pec -- ca -- ta mun -- di
A -- gnus De -- i qui tol -- lis pec -- ca -- ta mun-- di
}
choirPart = \new ChoirStaff
\new Staff \with {
midiInstrument = choir aahs
instrumentName = \markup \center-column { Tenor Bass }
}
\clef bass
\new Voice = tenorTwo { \voiceThree \tenorTwo }
\new Voice = bassTwo { \voiceFour \bassTwo }
\new Lyrics \with {
\override VerticalAxisGroup.staff-affinity = #DOWN
} \lyricsto tenorTwo \verseTenor
\new Lyrics \with { }
\lyricsto bassTwo \verseBasso
\score {
\choirPart
\layout { }
\midi {
\tempo 4=100
}
}
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (MingW32)
Comment: Using gpg4o v3.3.26.5094 - http://www.gpg4o.de/
Charset: utf-8
iQIcBAEBAgAGBQJUVh1LAAoJENCoWyDsDBkPd3wP/RxF7p6ysCFxVmdkpQI6hSx/
etXAEwvkCQHH55wKzRJHAn1tT/cm3tUkRhU3zlxQMXNX1e7kiSB7Yoevh/XQs1Iv
vKk70kwIpXgih6iis5dYy2UYalUKel35zDMmswYZ6hsU70iQeEC5dZkddTLfGX6C
dsNJUflFa5MEwtm89vl9koOZ4ydxzFM1H2s5vkncqCeFKqMF7cf8Zos0WROKisyj
hVcjld5xDmhYVQkf6fgfs9dHwSxHh776AhjtQ+G4HIlOL/HnOvwVTv5TNftw519Q
MTVXSS5oapKWQzI9iWkPTMGDbFyS1hRUJ/jfe5pXPXjRBmrILQf8eGUZ+W7bjKgI
wlC4OTP5Sb1UgFNSm3QvO7nT253bdQnlC1uLb6+Iq08KUbKFWW9McsX81h4FTsoB
d6eqzxbn9dH+2OCZXx9j1zymVf0Qie9rOLOZgqUoTUaqGRjPZetWpONGj6FUEX+J
Pka8/QoXfNuMfbKMfmCG20QAvCeIWqRxO/Pn0lArcQYQTmr4SZXTzowJ3aKfxAb/
EdJ21Sk2gQUhUCSq7WVWy0Y31W+ypcd0g7Tu+MzubBVq0tPpAr4CrhFuiD3oEYQ1
NP0uxU94Akfc3dvAnLyEzGQ7O+/y/vPuCj2pX+ITBCyMvt8r4FzitiR7MkXlqv1d
bY8vKc86dTAPbe5yV6BH
=ylf4
-END PGP SIGNATURE-
When I try to move the tenor text above the staff I fail. I have read the manual pages, but it does not work. What to change?I have tested the following piece and it compiles, however, not with the result I want.Thank youBernhardversion 2.19.15\language deutschglobal = {\key c \major\time 3/4}tenorTwo = \relative c' {\global \dynamicUps2.| c2 c4|}bassTwo = \relative c' {\global a2 a4| a g f | e cis e | a ( g) f| e fis d4\rest}verseTenor = \lyricmode {A -- gnus De -- i qui tol -- lis pec -- ca -- ta mun -- di}verseBasso = \lyricmode {A -- gnus De -- i qui tol -- lis pec -- ca -- ta mun -- diA -- gnus De -- i qui tol -- lis pec -- ca -- ta mun-- di }choirPart = \new ChoirStaff \new Staff \with {midiInstrument = choir aahsinstrumentName = \markup \center-column { Tenor Bass }} \clef bass\new Voice = tenorTwo { \voiceThree \tenorTwo }\new Voice = bassTwo { \voiceFour \bassTwo }\new Lyrics \with {\override VerticalAxisGroup.staff-affinity = #DOWN} \lyricsto tenorTwo \verseTenor\new Lyrics \with { }\lyricsto bassTwo \verseBasso\score {\choirPart\layout { }\midi {\tempo 4=100}}
PGPexch.htm.sig
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Place objects by hand
Noeck wrote Sunday, November 02, 2014 12:46 AM
That would be nice, but your example puts the f on the left of the upper
note and not centralized between the staves (I am using 2.19.15).
You're right, Joram, \offset is not a solution. In fact, it seems to point to
another problem with \offset. In this example it prevents the dynamic
text being centered between the staves. I don't understand why it should
have this effect.
\version 2.18.2
\new PianoStaff
\new Staff { g-_ g c' }
\new Dynamics {
\once \offset X-offset -3 DynamicText
s\f s s\p
}
\new Staff { \clef bass g'-_ g' g' }
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Text above the staff
Bernhard Kleine wrote Sunday, November 02, 2014 12:02 PM
When I try to move the tenor text above the staff I fail. I have read the
manual pages, but it does not work. What to change?
I have tested the following piece and it compiles, however, not with the
result I want.
Almost right, but you have confused two possible ways, using part of one and
part of the other. I'd name the men's staff and use alignAboveContext = Men,
like this:
\version 2.19.15
\language deutsch
global = {
\key c \major
\time 3/4
}
tenorTwo = \relative c' {
\global \dynamicUp
s2.| c2 c4|
}
bassTwo = \relative c' {
\global
a2 a4| a g f | e cis e | a ( g) f| e fis d4\rest
}
verseTenor = \lyricmode {
A -- gnus De -- i qui tol -- lis pec -- ca -- ta mun -- di
}
verseBasso = \lyricmode {
A -- gnus De -- i qui tol -- lis pec -- ca -- ta mun -- di
A -- gnus De -- i qui tol -- lis pec -- ca -- ta mun-- di
}
choirPart = \new ChoirStaff
\new Staff = Men \with {
midiInstrument = choir aahs
instrumentName = \markup \center-column { Tenor Bass }
}
\clef bass
\new Voice = tenorTwo { \voiceThree \tenorTwo }
\new Voice = bassTwo { \voiceFour \bassTwo }
\new Lyrics \with {
alignAboveContext = Men
} \lyricsto tenorTwo \verseTenor
\new Lyrics \with { }
\lyricsto bassTwo \verseBasso
\score {
\choirPart
\layout { }
\midi {
\tempo 4=100
}
}
This is the first option in
http://www.lilypond.org/doc/v2.19/Documentation/notation/techniques-specific-to-lyrics#placing-lyrics-vertically
Trevor
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Place objects by hand
Hi,
On Sun, Nov 2, 2014 at 6:23 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Noeck wrote Sunday, November 02, 2014 12:46 AM
That would be nice, but your example puts the f on the left of the upper
note and not centralized between the staves (I am using 2.19.15).
You're right, Joram, \offset is not a solution. In fact, it seems to
point to
another problem with \offset. In this example it prevents the dynamic
text being centered between the staves. I don't understand why it should
have this effect.
\version 2.18.2
\new PianoStaff
\new Staff { g-_ g c' }
\new Dynamics {
\once \offset X-offset -3 DynamicText
s\f s s\p
}
\new Staff { \clef bass g'-_ g' g' }
Trevor
No, it's not a problem with \offset.
Substitute this for the call to \offset, and you'll see that it's actually
an issue with X-offset here:
\once \override DynamicText.X-offset = #-3
--David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Where to Download the New Music Fonts?
Let alone the music spacing, I think the diamond note heads are fare too small, in general. This is taken on a 12pt score magnified at 180%, default lilypond engraving: http://lilypond.1069038.n5.nabble.com/file/n168304/2014-11-02-180946_1024x600_scrot.png Look at the quavers flags, and compare the diamond noteheads and the breves.The latter colour is much heavier. See the tempo mark on the bottom staff too. The dots are too big. I don't know if it's an unbalanced font or if some work has to be done on the mensural staffvoice contexts. For mensural music parts (which are the most common case) there should be a way to turn off the lilypond proportional music spacing too (which again is not related to the font itself, I think). -- View this message in context: http://lilypond.1069038.n5.nabble.com/Where-to-Download-the-New-Music-Fonts-tp165035p168304.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Where to Download the New Music Fonts?
Interesting stuff, I should try it. I guess I'll wait for the 2.19 version to become stable and try some different fonts. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Where-to-Download-the-New-Music-Fonts-tp165035p168305.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Place objects by hand
David, you wrote Sunday, November 02, 2014 12:44 PM No, it's not a problem with \offset. Substitute this for the call to \offset, and you'll see that it's actually an issue with X-offset here: \once \override DynamicText.X-offset = #-3 Ah, sorry to cast invalid aspersions on \offset, David. Still looks like a bug though. Another example bites the dust. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Place objects by hand
On Sun, Nov 2, 2014 at 6:55 AM, Trevor Daniels t.dani...@treda.co.uk wrote: David, you wrote Sunday, November 02, 2014 12:44 PM No, it's not a problem with \offset. Substitute this for the call to \offset, and you'll see that it's actually an issue with X-offset here: \once \override DynamicText.X-offset = #-3 Ah, sorry to cast invalid aspersions on \offset, David. Still looks like a bug though. Yes, I would say it's definitely a bug. This is a bit of misuse of self-alignment-X, but the same happens with this line: \once \override DynamicText.self-alignment-X = #5 So, possibly it's a problem with the Dynamics context? Another example bites the dust. Yeah, sorry. It's not hard to come up with vivid demonstrations; the difficult part of course is to find the real-world example where just that command is what you need! (It can be used to create the same effects as \shape, but then...there's \shape for that.) Offsetting arpeggio.positions is nice, I think. (Though not precise; there is quantization which unavoidably kicks in, I think. It's still nice for arpeggios across tiny intervals, where you don't want to figure out staff positions yourself.) --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mark not visible at the beginning of a line
This may help you, although it is fairly complex:
http://lsr.di.unimi.it/LSR/Item?id=892
Knute Snortum
(via Gmail)
On Sun, Nov 2, 2014 at 2:12 AM, Jacques Menu imj-...@bluewin.ch wrote:
Hello folks,
In the following sample, how can I have the second mark displayed at the
beginning of the second line?
Adding the hidden measure and bar line trick prevents the new time
indication to be printed at the end of the first line, unfortunately.
Thanks for your help!
JM
—
%%%
\version 2.18.2
{
%%% BASIC ATTEMPT
\time 4/4
\clef bass
\mark\default
c1 | d1 | e1 |
\once \override Score.RehearsalMark.self-alignment-X = #CENTER
\override Score.RehearsalMark.break-visibility = #begin-of-line-invisible
\mark \markup {\musicglyph #scripts.ufermata}
\bar ||
\break | % 65
\mark\default
\tempo \markup{Subito tempo vite} 2 = 120
\time 6/8
b2. |
g2. |
\bar |.
}
{
%%% WITH HIDDEN MEASURE AND BAR LINE
\time 4/4
\clef bass
\mark\default
c1 | d1 | e1 |
\once \override Score.RehearsalMark.self-alignment-X = #CENTER
\override Score.RehearsalMark.break-visibility = #begin-of-line-invisible
\mark \markup {\musicglyph #scripts.ufermata}
\bar ||
\break | % 65
% the hidden measure and bar line
% \cadenzaOn turns off automatic calculation of bar numbers
\cadenzaOn
\once \omit Score.TimeSignature
\once \omit Score.BarNumber
\time 1/64
s64 \bar
\cadenzaOff
\mark\default
\tempo \markup{Subito tempo vite} 2 = 120
\time 6/8
b2. |
g2. |
\bar |.
}
%%%
___
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: Place objects by hand
Hi again, On Sun, Nov 2, 2014 at 7:08 AM, David Nalesnik david.nales...@gmail.com wrote: Offsetting arpeggio.positions is nice, I think. (Though not precise; there is quantization which unavoidably kicks in, I think. It's still nice for arpeggios across tiny intervals, where you don't want to figure out staff positions yourself.) Sorry, I should say that such arpeggios are always drawn too short, hence the need to override (or offset) the endpoints. --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Ties across voices
Hello,
As far as I know, which is certainly minimal, ties cannot be input across
voices as in
\new Voice \relative c' { \voiceOne }
\new Voice \relative c' { \voiceTwo }
.
How could I achieve ties as in the attached example?
Thank you for your kind attention.
Mark
Ties.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ties across voices
On Nov 2, 2014, at 4:24 PM, Mark Stephen Mrotek carsonm...@ca.rr.com wrote:
Hello,
As far as I know, which is certainly minimal, ties cannot be input across
voices as in
\new Voice \relative c' { \voiceOne }
\new Voice \relative c' { \voiceTwo }
.
How could I achieve ties as in the attached example?
Thank you for your kind attention.
Mark
Try:
\layout {
\context { \Voice \remove Tie_engraver }
\context { \Staff \consists Tie_engraver }
}
Doesn’t always work perfectly…
Cheers,
MS___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Ties across voices
Mike,
Thank you for your reply and the suggestion. I shall try it.
“Never let the perfect be the enemy of the good!”
Mark
From: Mike Solomon [mailto:m...@mikesolomon.org]
Sent: Sunday, November 02, 2014 6:43 AM
To: Mark Stephen Mrotek
Cc: lilypond-user@gnu.org
Subject: Re: Ties across voices
On Nov 2, 2014, at 4:24 PM, Mark Stephen Mrotek carsonm...@ca.rr.com wrote:
Hello,
As far as I know, which is certainly minimal, ties cannot be input across
voices as in
\new Voice \relative c' { \voiceOne }
\new Voice \relative c' { \voiceTwo }
.
How could I achieve ties as in the attached example?
Thank you for your kind attention.
Mark
Try:
\layout {
\context { \Voice \remove Tie_engraver }
\context { \Staff \consists Tie_engraver }
}
Doesn’t always work perfectly…
Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
possible bug: \change Staff and beam collision
Hello all,
Please have a look on the following code:
\version 2.19.15
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
a,
}
\new Staff = down {
\clef bass
s2
}
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
\change Staff = down a,
}
\new Staff = down {
\clef bass
s2
}
Which produces:
http://lilypond.1069038.n5.nabble.com/file/n168324/11.png
As you can see, without changing staff the ottava position is high enough
not to collide with the beam, but when changing staff the ottava position
gets lower (!) and collides with the beam. Anyone know any workaround for
this problem?
Best,
Gilberto
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/possible-bug-change-Staff-and-beam-collision-tp168324.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: possible bug: \change Staff and beam collision
On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho gilbertohasn...@gmail.com
wrote:
Hello all,
Please have a look on the following code:
\version 2.19.15
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
a,
}
\new Staff = down {
\clef bass
s2
}
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
\change Staff = down a,
}
\new Staff = down {
\clef bass
s2
}
Which produces:
http://lilypond.1069038.n5.nabble.com/file/n168324/11.png
As you can see, without changing staff the ottava position is high enough
not to collide with the beam, but when changing staff the ottava position
gets lower (!) and collides with the beam. Anyone know any workaround for
this problem?
Best,
Gilberto
This is a persistent issue in LilyPond development - there was some work on it
in course a couple years ago that has since been put on hold but I hope to pick
it back up one day.
The gist of the problem (and others like it) is that, because the beam is cross
staff, the layout engine does not know where it will be placed because it does
not know how far apart vertically the notes are until final page spacing is
done. That means that all objects that depend on the beam for placement (such
as the ottava) ignore it when being placed and, as a result, you get collisions.
I know that Keith has several cross-staff-related workarounds in his piano
scores. Sorry I can’t be of more help, but it is not an easy issue.
Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: possible bug: \change Staff and beam collision
On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho gilbertohasn...@gmail.com
wrote:
Hello all,
Please have a look on the following code:
\version 2.19.15
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
a,
}
\new Staff = down {
\clef bass
s2
}
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
\change Staff = down a,
}
\new Staff = down {
\clef bass
s2
}
Which produces:
http://lilypond.1069038.n5.nabble.com/file/n168324/11.png
As you can see, without changing staff the ottava position is high enough
not to collide with the beam, but when changing staff the ottava position
gets lower (!) and collides with the beam. Anyone know any workaround for
this problem?
Best,
Gilberto
This is a persistent issue in LilyPond development - there was some work on it
in course a couple years ago that has since been put on hold but I hope to pick
it back up one day.
The gist of the problem (and others like it) is that, because the beam is cross
staff, the layout engine does not know where it will be placed because it does
not know how far apart vertically the notes are until final page spacing is
done. That means that all objects that depend on the beam for placement (such
as the ottava) ignore it when being placed and, as a result, you get collisions.
I know that Keith has several cross-staff-related workarounds in his piano
scores. Sorry I can’t be of more help, but it is not an easy issue.
Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: possible bug: \change Staff and beam collision
On Nov 2, 2014, at 8:40 PM, Gilberto Agostinho gilbertohasn...@gmail.com
wrote:
Hello all,
Please have a look on the following code:
\version 2.19.15
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
a,
}
\new Staff = down {
\clef bass
s2
}
\new PianoStaff
\new Staff = up {
\override Score.Beam.damping = 3
\stemUp a'8
\ottava #1 a'''
\ottava #0 a'
\change Staff = down a,
}
\new Staff = down {
\clef bass
s2
}
Which produces:
http://lilypond.1069038.n5.nabble.com/file/n168324/11.png
As you can see, without changing staff the ottava position is high enough
not to collide with the beam, but when changing staff the ottava position
gets lower (!) and collides with the beam. Anyone know any workaround for
this problem?
Best,
Gilberto
This is a persistent issue in LilyPond development - there was some work on it
in course a couple years ago that has since been put on hold but I hope to pick
it back up one day.
The gist of the problem (and others like it) is that, because the beam is cross
staff, the layout engine does not know where it will be placed because it does
not know how far apart vertically the notes are until final page spacing is
done. That means that all objects that depend on the beam for placement (such
as the ottava) ignore it when being placed and, as a result, you get collisions.
I know that Keith has several cross-staff-related workarounds in his piano
scores. Sorry I can’t be of more help, but it is not an easy issue.
Cheers,
MS
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: possible bug: \change Staff and beam collision
Hi Mike, Thanks for your reply. Mike Solomon wrote This is a persistent issue in LilyPond development - there was some work on it in course a couple years ago that has since been put on hold but I hope to pick it back up one day. I totally understand it. Mike Solomon wrote I know that Keith has several cross-staff-related workarounds in his piano scores. Sorry I can’t be of more help, but it is not an easy issue. Thanks anyway, I will see if I find some interesting snippet by Keith then. My case is always complicated though, my main work is with algorithmically generated music and so I always need to either automatize a solution or completely forget about it and approach the problem of notation from a different point of view (manual tweaking isn't an option for what I do). Best, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/possible-bug-change-Staff-and-beam-collision-tp168324p168329.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \autochange and \ottava
Gilberto Agostinho gilbertohasnofb at gmail.com writes:
[in the context of music generated by an algorithm]
I am having trouble dealing with ottava changes while using autochange.
The example showed \ottava changing the ottavation of staves by hand,
but the music moving between staves automatically with \autochange.
You or your algorithm must have some idea on which staff to place the
notes, before determining whether the staff needs an ottava change.
The general solution seems to be to apply whatever algorithm you use
to choose ottavation after applying the \autochange routine
\autoOctave \autoChange {...}
or maybe easier to merge them into one.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: possible bug: \change Staff and beam collision
Gilberto Agostinho gilbertohasnofb at gmail.com writes:
but when changing staff the ottava position
gets lower (!) and collides with the beam.
LilyPond allows you to beam to any other staff, so in general that
beam might have to go up and cross the ottava bracket, while the
bracket must stay with the staff. This is not likely with ottava
brackets but cross-staff beams and their stems sometimes need to cross
similar spanning structures.
The code is so far not sophisticated enough to look ahead to staff layout
when placing the ottava on its home staff, so assumes the cross-staff
beam might have to cross it.
Logically we should have a setting
\override Staff.OttavaBracket.cross-staff =
#ly:side-position-interface::calc-cross-staf
to tell Lilypond she may move the OttavaBracket along with the beam
but when I give LilyPond permission this way, she does not move the beam.
My case is always complicated though, my main work is with algorithmically
generated music and so I always need to either automatize a solution or
completely forget about it and approach the problem of notation from a
different point of view (manual tweaking isn't an option for what I do).
I have no better suggestion. The manual tweak is simple, though,
\once\override Staff.OttavaBracket.staff-padding = #6
and Lilypond makes it easy to put overrides in a separate expression
{ s1*54 \overrideThis}
{ s1*32 s2 \overrideThat}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with \autochange and \ottava
Hi Keith,
Keith OHara wrote
The general solution seems to be to apply whatever algorithm you use
to choose ottavation after applying the \autochange routine
\autoOctave \autoChange {...}
or maybe easier to merge them into one.
Oh, I see! So now I will probably aim to produce something like the code
below:
\score {
\new PianoStaff {
\autochange { c'4 d' c' b }
\autochange { \ottava #1 c''' e''' g''' }
\autochange { \ottava #0 c' b a }
}
}
I always applied \autochange to the whole PianoStaff, and for some reason it
didn't cross my mind I could do \autochange { musicA } \autochange { musicB
} etc. Thanks a lot, now things will be much easier!
Take care,
Gilberto
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/problem-with-autochange-and-ottava-tp168278p168336.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: possible bug: \change Staff and beam collision
Hi Keith, Thanks for the detailed explanation, I think I understand the situation well now. Keith OHara wrote I have no better suggestion. The manual tweak is simple, though, \once\override Staff.OttavaBracket.staff-padding = #6 Thanks anyway. Unfortunately my case of avoiding manual tweaks is not simple laziness: I work with generative music, which means that I will give the performers a computer program rather than a score, and I will let them generate a new version of a work by themselves. This means that I have absolutely no chances of ever tweaking that .ly file. Nevertheless, I am trying to play around with staff-padding but the results are not very good. Sometimes the ottavas are way too high, sometimes the collision problem appears again. Thanks a lot for your reply, I really appreciate it. Best, Gilberto -- View this message in context: http://lilypond.1069038.n5.nabble.com/possible-bug-change-Staff-and-beam-collision-tp168324p168337.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
