Frederic Dannen wrote:
Is there also a way to supress the first page number,
and move the numbers to the outer edge?
For that you have to get involved with
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Custom-titles
and how the source code in titling-init.ly does these things.
Frederic Dannen wrote:
It works, but as I said, not very elegant.
Would it be more elegant without the blank pages?
You could make lily *seem* to count pages twice as fast by
doubling what \fromproperty #'page:page-number-string delivers.
Kieren MacMillan wrote:
I've also tried to override the BarLine #'stencil, to no avail.
Maybe you weren't using ly:stencil-combine-at-edge
as demonstrated in
http://lsr.dsi.unimi.it/LSR/Item?id=650
Cheers,
Robin
___
lilypond-user mailing list
Stan Mulder wrote:
Is it possible to put a different set of chords
above the main line of chords
...
And what about the parenthesis around the chord name.
For parenthesizing see the thread with
http://lists.gnu.org/archive/html/lilypond-user/2009-03/msg00016.html
which also links to
**lost**
Only lower case because a very peripheral concern.
But this reminder has had NO RESPONSE.
(Should I have done something differently?)
http://lists.gnu.org/archive/html/bug-lilypond/2011-01/msg00480.html
Cheers,
Robin
___
bug-lilypond
Hu Haipeng wrote:
this doesn't work at all.
The hidden breathe sign strangely leaves an apostrophe like sign
This apostrophe is the breathe glyph; so I suppose the #'transparent
override wasn't being effective. My workaround did work for your snippet
(as my attachment for sighted
Hu Haipeng wrote:
this doesn't work at all.
The hidden breathe sign strangely leaves an apostrophe like sign
This apostrophe is the breathe glyph; so I suppose the #'transparent
override wasn't being effective. My workaround did work for your snippet
(as my attachment for sighted
Hu Haipeng wrote:
the arpeggio sign collides with the a'4 natural of the treble
It is as if the arpeggio code doesn't notice the staff change.
Here is a workaround which doesn't prevent a collision but disguises it.
Insert a transparent breathing sign after s2 in the right hand:
Hu Haipeng wrote:
the arpeggio sign collides with the a'4 natural of the treble
It is as if the arpeggio code doesn't notice the staff change.
Here is a workaround which doesn't prevent a collision but disguises it.
Insert a transparent breathing sign after s2 in the right hand:
Javier Ruiz wrote:
just adding [\bar |.] doesn't reset lilypond's automatic bar generator.
You can use \cadenzaOn to turn off the bar generator.
a set of alternate fingering digits stacked vertically.
Lilypond doen't object to you asking for two fingers on one note.
If that is too
Marek Klein wrote:
how can I get the staff-lines vertically aligned?
Here's another padding hack:
\layout { line-width = 6.2\cm ragged-right = ##f }
centeredVAG = \with { \override VerticalAxisGroup #'Y-extent = #'(-8 . 8) }
\markup \fill-line \vcenter {
\column{
\score
Tim Sheasby wrote:
how do I apply it to a specific note in a \set shapeNoteStyles context
Well, I'm not sure what you're aiming for, but try this:
miNarrow = #(lambda (grob)
(if (eqv? (ly:grob-property grob 'style) 'miMirror)
(ly:stencil-scale (ly:note-head::print grob)
Gabriel Espelleta wrote:
I have tried to generate a PDF out of this here below file,
but it does not work.
The Lilypond code you supplied says what the lead violin should play.
This, by itself, is not enough for what you are expecting.
You must also have code which asks Lilypond to
Helga Kruse wrote:
... avoiding the clash with the last e note?
A fairly reliable method would be to reference the whole markup to
this last note instead of the rest following it.
... so that they have the same base line ... ?
There is a \vcenter but there seem to be no \vbottom;
but
Carl Testa wrote:
Is there a way to define how big a stencil is
In your case, using ly:make-stencil, the parameters xext and yext
are for saying how big, and you have done this OK.
The problem is that these values don't get to affect the layout,
because the overridden rest is still
This is hardcoded. See
http://lists.gnu.org/archive/html/lilypond-user/2009-04/msg00691.html
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Tim McNamara wrote:
I am not sure how to actually use this in a file.
The multimeasure.ly has four sections;
the first two are needed to define inlineMMRN,
the last two give an example of using \inlineMMRN.
The example I used is a rough skeleton of Blessed Relief,
whose last part
Tao wrote:
I have a global frame with rehearsal marks etc., which I wanted
to use for all parts but I guess I'll just have to make an
alternative one for the rhythm section in this case.
The next time try doing it like this:
\set Score.skipTypesetting = ##t
[ ... empty section ...
Tim McNamara wrote:
There is a number in the middle of the bar
which indicates how many bars to repeat,
with a heavy horizontal bar on either side of the number.
Would this do the sort of thing you're looking for?
You ask for a multi-measure rest (big R)
and let \inlineMMRN move its
Neil Puttock commented on issue 1543:
If we really need to control the line breaks printed in drafts made with
skipTypesetting, we can insert a \grace s8 to define the timing.
A simpler method would be to unset forbidBreak.
I can't get this to work.
I would be interested in a
Neil Puttock wrote:
Works fine here
Thanks a lot! This is very easy to apply.
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Without skipTypesetting the following snippet delivers three lines.
With skipTypesetting it used to deliver two,
skipping the forced break at the dashed barline.
Since 2.13.43 it delivers only one line, skipping *both* forced breaks.
See
Tao wrote:
I tried overriding the #'text property of BarNumber but nothing happens.
Maybe this is because the bar counter sets up the #'text property at
a late stage and so overwrites what you had put there;
ChordName does that too.
You can bypass the #'text property with
Tao wrote:
maybe this is a bug?
It is an issue:
http://lists.gnu.org/archive/html/bug-lilypond/2009-03/msg00019.html
Try turning skipTypesetting on and off:
\set Score.skipTypesetting = ##t
[ ... empty section ... ]
\set Score.skipTypesetting = ##f
Cheers,
Robin
Tao wrote:
Unfortunately this seems to neutralize all \break commands.
This is probably due to the new vertical spacing.
Something relevant must have changed between 2.13.40 and 2.13.46.
Cheers,
Robin
___
lilypond-user mailing list
Robin Bannister wrote:
Something relevant must have changed between 2.13.40 and 2.13.46.
I've narrowed this down to between 2.13.42 and 2.13.43,
so it's probably the commit to fix issue 1336
http://code.google.com/p/lilypond/issues/detail?id=1336
Don't make paper columns
Tim Sheasby wrote:
Can a notehead be scaled by different factors in the x and y directions?
In the recent development versions (starting with 2.13.38) you can.
The following snippet uses an X-factor of 2:
wideNH = #(lambda (grob) (ly:stencil-scale (ly:note-head::print grob) 2 1))
Frank Weichert wrote:
I'm looking for special symbols used for harp-notation
You could try following up Mario's TabSymbols font
http://www.lilypondforum.de/index.php?topic=252.0
And for a possible markup approach and some discussion, see
Matthias Hüsken wrote:
What I'd like to achieve:
When ending a bar with the repetition sign :|,
I need double lines (||) at the beginning of the next bar.
It looks as though you actually mean ending/beginning lines, not bars.
[...]
(:|| . (:| . ||))
[...]
Unfortunately, this does not work:
Neil Puttock wrote quite some time ago
http://lists.gnu.org/archive/html/bug-lilypond/2009-09/msg00039.html
Thanks, I'll sort this out.
I have just noticed that LSR 377 is still suffering from the
convert problem (re issue 97) described in
ornello wrote:
My solution is not working because it affects all line breaks
(not just the beginning of the piece
Having to affect all line breaks was what made was-empty.ly so cumbersome.
You can make LSR 500 work by adding:
\once \override Staff.BarLine #'glyph-name = ||
Xavier Scheuer wrote:
[...] James Bailey wrote:
I haven't checked it, but they're probably in different voice contexts.
Possible explicity doing a \new Voice = first and \context Voice = first
where appropriate may solve the problem.
Yes, or simply putting all in a \new Voice works:
Disc Magnet wrote:
the MIDI output misses the second note in the last bar
This looks like issue 676, so you are probably using a 2.12 version.
See
http://code.google.com/p/lilypond/issues/detail?id=676
The MIDI behaviour was corrected in version 2.13.8.
Warnings for this situation
David Kastrup wrote:
the vertical extent should fit in the circles
necessitated by the horizontal extent.
The 4 is big enough to ensure that all the vertical extents do fit,
but (because of this) they all fit loosely.
This looseness means that to decide where to position a circle
Peter Buhr wrote:
the arpeggio symbol appears [...] about 1cm from the chord,
and the finger number is to the left of the arpeggio symbol,
while I want the finger number to be on the right of the arpeggio symbol.
Suggestions?
Check out my hack at
Dominic Neumann wrote:
[...] Gilles, said that using a |. bar the bracket has an end line.
You can make the |. merely look like || by saying
\once \override Score.BarLine #'thick-thickness = #1.9
That way you don't need the s4 and the extra-(X-)offsets:
\set Score.repeatCommands =
Rodolfo Zitellini wrote:
and I can't use \tweak (the notation manual states quite
clearly that accidentals can not be modified with \tweak)
You mean at the end of Notation Reference 5.3.4.
Well, it used to be quite categorical on this, e.g in the 2.12.1 docs.
Last year Mark Polesky found
Jiri Zurek wrote:
put into the brackets not the normal key signature
but only the cautionary cancellation key signature?
Say 'Staff.KeyCancellation' instead of 'Staff.KeySignature'.
Cheers,
Robin
___
lilypond-user mailing list
carbon14 wrote:
Is there a way to make the bar span a dashed or dotted line,
but leave the bar lines themselves solid?
This works with 2.12.3 (I can't test it with 2.12.4!) :
\override Score.SpanBar #'glyph-name = #dashed
Cheers,
Robin
Sam Domonkos wrote:
I would like to explicitly separate parts of music by having
these bar lines always at the beginning and end of parts
...
\bar .| a4 b c d \bar |. \break
\bar .| a b c d \bar |.
I'm not sure what you mean by a part.
Xavier Scheuer wrote:
Robin (or somebody else), could you provide me a version of your
put-mm but using \hspace instead of \vspace ?
...
in order to make a _horizontal_ space with a value in millimeters
Well, I've had Lilypond on the back burner for a while, so I'm a bit rusty.
By swapping
Kieren MacMillan wrote:
Any tips/suggestions on best practice(s) would be appreciated.
I don't presume to know about best practice,
but I suspect it doesn't include negative spacing.
It's too easy to ask for nonsensical intervals and then
Lilypond quietly discards the whole markup,
Tom Cloyd wrote:
One more small problem: the measure 20 arpeggio across all three voices
(line 174) is wiping out the bar line. Ouch! Is that fixable?
This is issue 880, fixed in 2.13.12.
But my constrain-hidden-positions workaround fixes it on 2.12.3
Paul Scott wrote:
If anyone has an acceptable solution for this
I would appreciate hearing about it.
Inserting a grace spacer is fairly painless (unless it triggers issue 34).
Cheers,
Robin
{
\compressFullBarRests
R1
\tempo rall
\grace s1
R1*20
R1
\tempo a tempo
David Stocker wrote:
center the entire chord symbol (root and suffix) on its rhythmic axis?
#(define (centerCN grob)
(ly:stencil-aligned-to (ly:text-interface::print grob) X CENTER ))
and then apply as
\override ChordNames.ChordName #'stencil = #centerCN
Cheers,
Robin
Leland Kusmer wrote:
Is there a way to do this?
Lilypond does this according to bar-glyph-alist,
by calling calc-glyph-name from within the barline print routine.
But when you override the BarLine stencil like this,
you are bypassing the barline print routine.
So try something (which calls
Werner wrote:
I tried to get a left-aligned (or offset) RehearselMark.
This could be above a dashed bar-line
Does this do what you wanted?
\once \override Score.RehearsalMark #'self-alignment-X = #LEFT
\bar dashed
Cheers,
Robin
___
Helge Kruse wrote:
I made some further experiments.
Well, I messed around a bit.
I certainly wasn't doing experiments; that makes it sound systematic.
My slurs often silently ignored the staff change; no idea why.
Two offerings, FWIW:
A: no cross-staff in right hand.
B: cross-staff in
Jay Hamilton wrote:
not exactly sure what that means in this case
There is an example at
http://lsr.dsi.unimi.it/LSR/Item?id=258
This sidesteps the question of horizontal space by setting ragged-right.
Do you already have enough horizontal space for the text?
Or do you expect Lilypond to
Here is an example of the arpeggio approach (not dashed).
Cheers,
Robin
\version 2.12.3
#(define (thin-line grob)
(let* (
(pos (ly:grob-property grob 'positions))
(lo-hi (interval-widen pos -1.2))
(thin 0.05))
(make-line-stencil thin 0 (interval-start lo-hi) 0 (interval-end
Neil Puttock wrote:
\override ChoirStaff.Arpeggio #'stencil = #ly:arpeggio::brew-chord-bracket
I wanted to do pretty much the same last week
and ran into a familiar bug which I haven't reported yet.
To get the closing bracket right (sic), try
\context { \ChoirStaff
\consists
You're welcome.
Richard Wattenbarger wrote:
If I could [ ... ] , I would!
I would prefer your response to
It would help in this regard if you could explain why you need the
bracket to be closed like this, e.g. does it involve a coda?
Cheers,
Robin
Richard Wattenbarger wrote:
Is there a way to force LilyPond to draw a standard single bar
instead of the .| glyph?
As I said, this flexibility is not provided.
Which bar lines have this side-effect is currently hardcoded in C++.
A likely enhancement would make this selection overrideable,
Patrick McCarty wrote:
I will try to see what's going on.
See here for an overview
http://lists.gnu.org/archive/html/bug-lilypond/2010-02/msg00124.html
Cheers,
Robin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Athanasius Pelletier wrote
at certain parts where the lyrics are supposed to continue until another note.
This is discussed in Notation Reference 2.8.5.
Helge Kruse wrote:
Why talks Lilypond German and
how can I set the language to English?
Probably because of your regional settings.
Application Usage 3.2.3 tells you about LANG, but not enough.
You need to set it to en (an ISO 639-1 code).
I don't know about Windows7,
but the attachment
Richard Wattenbarger wrote:
I would like the bracket for the second ending to conclude with a vertical line
That would imply something which your example doesn't have:
that the second ending is not always followed by the neigboring measure
and/or
that the neigboring measure is not always
Gerry Prosser wrote:
Capo settings really should be with the chords.
You could do this with (the simple version of) besideCN:
http://lists.gnu.org/archive/html/lilypond-user/2009-03/msg00052.html
(mangled by the archives as usual)
Cheers,
Robin
Gerry Prosser wrote:
the dreaded N/C. But I can tipex that
Or say
\once \set noChordSymbol =
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
I wrote:
\once \set noChordSymbol =
Sorry, that typo makes it end up like skip.
You need at least one blank in the string:
\once \set noChordSymbol =
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
Chord names entered in note mode are annotated in the pdf with a link
leading to the corresponding position in the ly source file.
But chord names entered in chord mode get either
a link with an invalid position (versions = 2.13.7 say line0 column0).
or no link at all.
This seems to be
Patrick McCarty wrote:
Do you think it's worth opening a separate issue,
given that fixing #975 might also fix this issue?
No, please don't bother. I just thought this info might help #975.
I can probably get by with just the 2.12.3 stable.
Although I did leave a vertically tight single
Patrick McCarty wrote:
The cache is located in $HOME/.lilypond-fonts.cache-2
(or the equivalent on Windows)
Well, I didn't understand what the equivalent was referring to, but
this got me doing the same searches again, and some more, and even more.
And then I found the cache in an unrelated
I wrote:
And now I have also installed 2.12.3.
Both it and 2.13.9 run OK, but the others crash.
Maybe a long shot, but could my problem be related to issue 975?
http://code.google.com/p/lilypond/issues/detail?id=975
I am wary of doing something which makes _all_ the versions crash.
But
Following Trevor's hint
http://lists.gnu.org/archive/html/bug-lilypond/2008-05/msg00137.html
I have had no problems switching between Lilypond versions by renaming,
mainly between 2.8.8, 2.10.33 and 2.12.1 (but also 2.13.1).
Two days ago I also installed 2.13.9.
It runs OK, but now the
Hu Haipeng wrote:
Why this compilation gets only two pages?
Mmm, that's my fault.
I commented out the midi generation to save time,
and I may have needed global-staff-size 6 in the initial stage
while I had done this incorrectly.
This size squeezes much more than you need, the second
I suppose I'd like a filler that does *not* take up duration
You can use a breath mark for this
http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Curves#Breath-marks
and then make it blank by overriding #'text or #'transparent.
gap = {
\once \override BreathingSign #'text =
%
Hu Haipeng wrote:
only a few pages [...] and some of these with staves missing
I ran this through 2.13.9. The most obvious problems are:
A:
The first page has music running off the bottom.
I suppose so many staves can't be fitted in vertically.
One of the following makes things fit on
David Nalesnik wrote:
I want [...] a dashed barline between the staves, while
retaining a solid barline within the individual lines.
Add the following to your \layout{\context{\Score block:
\override SpanBar #'glyph-name = #dashed
Cheers,
Robin
Jay Anderson wrote:
I've attached a picture of the particular chord I was working on
(for viola, alto clef, in 3/4). In this case
I want to keep it explicitly notated and all in the same voice.
I suppose that this is notionally c g e'2.
Something which sounds like that but looks like
c4*3 g e'2.
Mmm, that was where you started.
Sorry for the noise.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Stefan Kaegi wrote:
It actually should be under the f (in the left hand) and not before.
Then you shouldn't say \sustainOn until the cadenza has been and gone,
i.e. s1\sustainOn is all you need - because the s1 starts when the f starts.
See the bracket example in NR 2.2.2 -
Hu Haipeng wrote:
This unterminated tie may sound odd,
and will therefore give warning to the user
Maybe, but in my case it was masked by another voice.
What brought it to my attention was the subsequent note not sounding.
See my original report (before it got garbled in 676).
Aaron Dalton wrote:
I want to be able to hide the accidental.
There is Mark Polesky's suppress-accidental
http://lists.gnu.org/archive/html/lilypond-devel/2009-07/msg00384.html
but that is probably overkill in your case.
You can do it by switching the style in a music function
\paper { ragged-right = ##t }
teeny = \set fontSize = #-3
% seen with versions 2.12.1, 2.10.33, 2.8.8
a'2
\\
% \once \override NoteHead #'X-extent = #'(0 . 1.3) % crude workaround to avoid
\teeny a'4 % voice2 colliding with larger voice1
It looks like the collision avoidance is
\paper { ragged-right = ##t }
{% seen with versions 2.12.1, 2.10.33, 2.8.8
b'1 \\ s1 \\ f' e''1 \arpeggio % arpeggio collides with voice1
}% unless there is an accidental (in any voice)
Cheers,
Robin
___
bug-lilypond mailing list
Robin Bannister wrote:
This of course also applies to the issue(s) I referenced in my followup
http://lists.gnu.org/archive/html/bug-lilypond/2009-10/msg00294.html
I am unsuccessful again. I will just spell out the main point:
The collision snippet which is registered as issue 821
http
Seeing the issues in the priority/type table format made me realise
how important it is to get these categories right.
This thread (span arpeggio and single notes)
supplied the collision snippet which is registered as issue 880
http://code.google.com/p/lilypond/issues/detail?id=880
No
MonAmiPierrot wrote:
I also would like to be given the possibility to put the blank space
between different examples from the same musical context
For big gaps you can use \stopStaff and \startStaff and put
suitable spacer rests in between.
For small gaps you could try misusing the
MonAmiPierrot wrote:
But for \stopStaff and \startStaff it won't work at the beginning
with a s invisible pause.
It seems OK to me (with 2.12.1) but maybe you want it effective even earlier.
For that (and the \partial question) you could try using
| \grace s1
to get the music
Václav Šmilauer wrote:
other than using \markup{...} in lyrics context for every single chord
If your needs are met by (a possibly modifed) ChordNames most of the time,
you can use replaceCN to deal with the impossible cases.
Jiri Zurek wrote:
What is wrong with my syntax, please?
ly:bar-line::calc-bar-size needs a parameter.
If you get used to writing things like
\override Staff.BarLine #'bar-size = #ly:bar-line::calc-bar-size
you think that is all you ever need to say.
But the functions for grob
David Sumbler wrote:
I thought that using the slashSeparator between items
would make things clearer, but I only want it
after each complete item, not after every line.
It sounds as though each of your exercises is a \score block.
You can put (stand-alone) markup between these blocks;
Valentin Villenave wrote:
While waiting for acknowledgement,
I have come across several online examples of this.
Yes, I suspect these issues have the same underlying cause (though I
opened multiple issues since I'm not sure what that cause might be).
Well, that was my point
ze patavinas wrote:
I don't understand why it does not print the stem and the notehead
It as if it doesn't like the notehead style being undefined. Just add
#:override '(style . 'default)
Cheers,
Robin
___
lilypond-user
Going by the list of Scheme functions (2.12 NR B.15, 2.13 NR A.16)
it seems that there are two basic graphical transformations available:
- translation, e.g ly:stencil-translate
- rotation, e.g. ly:stencil-rotate
I feel that these two should be complemented by a third
bradford powell wrote:
This doesn't work, any suggestions?
#(define* (draw hole #:optional (bends 0))
(markup (make-line-markup (make-list bends #:flat )) #:circle hole))
The make-list result is not itself a markup;
for that, it must be passed to something like #:line.
And then
Kim Shrier wrote:
there is something I need
#'outside-staff-priority ##f
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Kim Shrier wrote:
I am trying to place a right comma just to the right and a little above a note.
This alternative may do the spacing better:
c4 \once \override BreathingSign #'Y-offset = #0 \breathe
Cheers,
Robin
___
lilypond-user
It looks fine here too, with 2.12.1.
But I noticed my editor was garbling some IPA.
It is set to use DejaVu Sans Mono.
If I change your lyrics font override to DejaVu Sans Mono,
then Lilpond garbles my output too.
Cheers,
Robin
___
While waiting for acknowledgement,
I have come across several online examples of this.
Their severity depends on how dense the local layout is.
Neighboring things may push the faulty arpeggio that bit too far.
And less severe cases may go unnoticed, e.g. the Ravel;
the tight layout may look
\version 2.12.1 % regression: 2.10.33 and 2.8.8 are ok
dense = #(define-music-function (parser location mus) (ly:music?)
#{ s2 $mus $mus $mus $mus d g' 4 \noBreak #})
\score { \transpose c c' {
\stemDown
\dense e'16
\dense d'16
\dense c'16 % collision
\dense b 16 % collision
\dense a 16
And this is my attempt (see droeyende.ly).
For the alignment I used 2 force-hshift overrides (in voices 3 and 4).
You can certainly use arpeggioBracket here, but it is so inconvenient:
- put the Span_arpeggio_engraver in the right place
- turn on
Frédéric Bron wrote:
Any idea?
Well, there is LSR 428.
http://lsr.dsi.unimi.it/LSR/Item?id=428
From this you would expect
\set Score.voltaSpannerDuration = #(ly:make-moment 7 8)
to work, but it doesn't.
It seems the bracket is hung between barlines
(something this snippet doesn't
\version 2.12.1 % regression: 2.10.33 and 2.8.8 are ok
{
f'\laissezVibrer f a' \arpeggio
f'\laissezVibrer g a' \arpeggio \mark never
f'\laissezVibrer a a' \arpeggio
f'\laissezVibrer b a' \arpeggio
\bar ||
f'\laissezVibrer f g' \arpeggio
f'\laissezVibrer g g' \arpeggio
Graham Percival wrote:
in addition to the webpage, the documentation has been slightly reorganized
As regards inurl searching, I assume
- the Kainhofer demo doesn't show me what the urls will be like;
specifically
- the breadcrumb .../Documentation/... will not be right at the top
Valerio Pelliccioni wrote:
highlighted with a line with square ends lying above the bar
and the word Bis in the middle of the line.
You could use an analysis bracket (see NR 1.7.2) with added text.
Combine
fiëé visuëlle wrote:
I need the alternate voice only in some places.
This may be implying that you don't want to set the main voice as
\voiceOne, but rather keep it as (the implicit) \oneVoice.
If this rest collision behaviour is the only thing that is bothering you,
try the following
fiëé visuëlle wrote:
and since fermata is a TextScript element, I thought this would work
It is a Script element and doesn't use #'text.
You would have to do something like fermataLong
in the code for the initial example (the headword) in NR 2.2
fiëé visuëlle wrote:
The parentheses are a bit too small in comparison to the fermata
You can apply an override for this. See
http://lsr.dsi.unimi.it/LSR/Item?id=421
Cheers,
Robin
___
lilypond-user mailing list
lilypond-user@gnu.org
301 - 400 of 570 matches
Mail list logo
