Re: clef change in 1st ending
Le 26/10/2021 à 01:21, David Zelinsky a écrit :
I have a repeated section that starts in tenor clef, then changes to
bass clef (before the repeat). I want to show a tenor clef at the end
of the 1st ending, just before the repeat sign, as a reminder that the
repeat starts in that clef. But when I put '\clef "tenor"' in the first
\alternative, the 2nd ending then also gets engraved in tenor clef,
which is not right. Adding '\clef "bass" at the beginning of the 2nd
\alternative makes the tenor clef in the 1st ending disappear.
What is the correct way to deal with this situation?
(I'm sure I've seen a way to force a clef to be visible in situations
like this, but try as I might I can't find it.)
-David
David,
I'd do it like this:
\version "2.22.1"
{
\clef tenor
\repeat volta 2 {
c'1
\clef bass
c'1
}
\alternative {
{
c'1
\set Staff.clefGlyph = "clefs.C"
}
{ c'1 }
}
c'1
}
Best,
Jean
clef change in 1st ending
I have a repeated section that starts in tenor clef, then changes to bass clef (before the repeat). I want to show a tenor clef at the end of the 1st ending, just before the repeat sign, as a reminder that the repeat starts in that clef. But when I put '\clef "tenor"' in the first \alternative, the 2nd ending then also gets engraved in tenor clef, which is not right. Adding '\clef "bass" at the beginning of the 2nd \alternative makes the tenor clef in the 1st ending disappear. What is the correct way to deal with this situation? (I'm sure I've seen a way to force a clef to be visible in situations like this, but try as I might I can't find it.) -David
Re: Tweaking glissando timing stems
Am Mo., 25. Okt. 2021 um 12:00 Uhr schrieb Leo Correia de Verdier : > > Don’t worry, you’re doing far more on this than anyone could reasonably > expect. > > The final result should be something along these lines, but what I was asking > about is just the chord possibility. I have looked a little more into the > code and it’s far far above my level, but I’ve found som places I could > possibly act on… > If you don’t have time for it I would be grateful for hints about what I > could mess around with where in the code. > > > Thanks! > /Leo Hi Leo, thanks for the image, I think I understood. Though, I will first improve the current coding to make it working with all usual basic cases (and cure some bugs), before I try to implement other features. Got already some great hints from Jean and Aaron. Maybe next weekend ... Cheers, Harm
LilyPond 2.23.3 installer on MacOS 11
This is a LilyPond 2.23.3 installer, latest unstable release, for use on MacOS 11, made from MacPorts lilypond-devel, available on the link below [1]. Does not work on earlier MacOS versions. Might possibly work on MacOS 12 if installed on MacOS 11 before updating. It installs in /opt/lilypond/, with the program in /opt/lilypond/bin/lilypond, and /opt/lilypond/bin/ contains other LilyPond programs. If you have already something installed in this directory, it may be prudent to remove it first. This can be done by the command sudo rm -rf /opt/lilypond 1. https://web2.storegate.com/share/nI5ql1K It may be the case that 'lilypond' is best to be run from a script that sets LC_CTYPE=en_US.UTF-8 (which otherwise on MacOS is LC_CTYPE=UTF-8). It can be created and installed as follows: In Terminal write (^D is D): % cat > lilypond export LC_CTYPE=en_US.UTF-8 export LANG=en_US.UTF-8 exec /opt/lilypond/bin/lilypond "$@“ ^D % chmod a+x lilypond % sudo -s cp lilypond /usr/local/bin/lilypond The program can then be called by 'lilypond' in Terminal, as /usr/local/bin/ is in the system searchpath. And do 'rm lilypond' if you do not want to keep the local copy of the script.
Re: Markup with long notes spacing
What Aaron suggested seemed to work with the passage similar to the previous
rit-a tempo example, but the stretching 8-notes problem arises elsewhere, like
in the example below.
\version "2.18.2"
pocoaccel = \markup { \italic "poco accel." }
common = {
\override TextScript.extra-spacing-width = #'(0 . 1.5)
\override TextScript.extra-spacing-height = #'(1 . 1)
\override TextScript.staff-padding = #1
s1 ^\pocoaccel
}
oboe = \relative c''{
g8 (a b c d) g, (b c) a1
}
\score {
\new Staff <<\common \oboe>>
}
Re: Tweaking glissando timing stems
Don’t worry, you’re doing far more on this than anyone could reasonably expect. The final result should be something along these lines, but what I was asking about is just the chord possibility. I have looked a little more into the code and it’s far far above my level, but I’ve found som places I could possibly act on… If you don’t have time for it I would be grateful for hints about what I could mess around with where in the code. gliss-notehead-example.pdf Description: Adobe PDF document Thanks! /Leo > 25 okt. 2021 kl. 09:42 skrev Thomas Morley : > > Am Mo., 25. Okt. 2021 um 00:02 Uhr schrieb Leo Correia de Verdier > : > >> One feature I would find useful would be the ability to make chords with one >> ”gliss-note” and one regular notehead. I implemented this (not entirely >> successfully) on top of an earlier version of your code by making it work >> only on transparent noteheads and leave untransparent ones where they were >> from start. > > I've no good idea what you'ree after. > Could you post an image? > >> I haven’t had time to read into this version and try to understand >> everything it does yet. Do you have an idea of how readily that could be >> done to this version? > > Well, as said, my autumn break had ended, meaning I'll have far less > time to work on or with LilyPond. > Thus I can't say yet... > > Cheers, > Harm
Re: Tweaking glissando timing stems
Am Mo., 25. Okt. 2021 um 00:02 Uhr schrieb Leo Correia de Verdier : > One feature I would find useful would be the ability to make chords with one > ”gliss-note” and one regular notehead. I implemented this (not entirely > successfully) on top of an earlier version of your code by making it work > only on transparent noteheads and leave untransparent ones where they were > from start. I've no good idea what you'ree after. Could you post an image? > I haven’t had time to read into this version and try to understand everything > it does yet. Do you have an idea of how readily that could be done to this > version? Well, as said, my autumn break had ended, meaning I'll have far less time to work on or with LilyPond. Thus I can't say yet... Cheers, Harm
