On 2024-12-30 01:25, Werner LEMBERG wrote:
So yes, please improve the documentation. The example
I'll work on it.
--
Dan
On 2024-12-29 17:06, Werner LEMBERG wrote:
Your test code omits the `\set` command, which is slightly different.
Yes, thank you for clarifying that.
Anyway, both situations don't work; I would call it a bug.
I would rather call it a doc issue. It doesn't make sense to me that
\with { x =
On 2024-12-27 17:06, Knute Snortum wrote:
Interesting. this doesn't work with Voice, as you point out, but it
does work with Staff:
I thought that might have been what the author had in mind, but it's
hard to tell from what is actually written.
--
Dan
https://lilypond.org/doc/v2.24/Documentation/learning/modifying-context-properties
Under the heading "Setting context properties with \with", there are
these statements:
Properties set in this way may still be changed
dynamically using \set and returned to the default
value set in
On 2024-12-22 16:55, Werner LEMBERG wrote:
In this example, \popContextProperty appears not to restore the
property to the state it was in (unset) before \pushContextProperty.
This is a bug, right?
[...]
[I'm extremely busy the next week without a chance looking at this
issue.]
I expect
In this example, \popContextProperty appears not to restore the property
to the state it was in (unset) before \pushContextProperty. This is a
bug, right?
\new Staff <<
{
\time 2/4
\set Score.autoBeaming = ##f
\skip 8*6
\set Score.autoBeaming = ##t
}
\new Voice \with \voi
On 2024-12-17 00:48, Werner LEMBERG wrote:
Distributing the file with LilyPond was not intended. I don't
think it would make sense either.
I agree with Trevor, and I also think it would make sense.
[...] For my part, looking at the music of the psalm (lovely, btw) I
certainly think it woul
On 2024-12-16 17:57, Trevor Bača wrote:
On Mon, Dec 16, 2024 at 5:32 PM Dan Eble <mailto:nine.fierce.ball...@gmail.com>> wrote:
I am the author of this example. I used inclusion to cut out material
that I thought was not essential to make my point. I question whether
On 2024-12-16 15:28, Trevor Bača wrote:
dit 23: NR 2.1.7: Phrase bar lines in hymn tunes: notation example 1
* Example contains \include "old-hundredth-example.ly",
which can not be found under 2.25.19
In your attachment, your suggested action is "Update location of
included file, or r
On Mar 29, 2023, at 18:04, Grant Diffey wrote:
>
> I do wonder if there's a way to make the horizontal spacing.. 'nicer' but
> it's certainly functional for all my purposes as is.
My biggest questions about this use case surround the layout changes that are
baked into gregorian.ly, for example
On Mar 28, 2023, at 16:36, Grant Diffey wrote:
>
> Sure,
>
> However none of the staff types dan suggested will do what I could previously
> do. Gregorian divisiones not supported on modern staffs is a reasonable
> closure for this as a bug however I've previously been able to use the
> gre
On Mar 28, 2023, at 03:02, Jean Abou Samra wrote:
> Le mardi 28 mars 2023 à 12:54 +1100, Grant Diffey a écrit :
>> The following example:
>> \include "gregorian.ly"
>> { c' \divisioMaior d' \finalis }
>> Renders 'correctly' in 2.22 (using hacklily)
>> and incorrectly on my debian machine with Li
On Oct 7, 2022, at 16:45, Jean Abou Samra wrote:
> Thus I wrote to the general GNU list server admins and proposed
> to step up for being an admin on these lists, just like I am
> already an admin on lilypond-user-fr (the French-speaking equivalent
> of lilypond-user, in case you didn't know).
>
On Sep 5, 2022, at 10:02, Dan Eble wrote:
>
> I think that the commands that configure single-staff polyphony should set
> Voice.BreathingSign.direction. Does anyone know of a reason not to change
> the current behavior?
https://gitlab.com/lilypond/lilypond/-/issues
I think that the commands that configure single-staff polyphony should set
Voice.BreathingSign.direction. Does anyone know of a reason not to change the
current behavior?
```
\version "2.23.13"
upper = \fixed c'' { c2.-. \breathe d4-. | c2.-. \breathe d4-. }
lower = \fixed c' { a2.-. \breathe
On Jun 29, 2022, at 16:14, Jean Abou Samra wrote:
>
> Le 28/06/2022 à 01:33, Nikolai Hedler a écrit :
>>
>> MIDI ends late if |\fine| followed by a pitch.
https://gitlab.com/lilypond/lilypond/-/issues/6368
>> Beaming and |\fine|
https://gitlab.com/lilypond/lilypond/-/issues/6369
>>
On May 27, 2022, at 10:28, Jean Abou Samra wrote:
>
> Le 27/05/2022 à 14:34, Dan Eble a écrit :
>> I would at least like to understand whether the error message is reasonable
>> first.
>
> Do you mean whether it is reasonable for \bar "" during a
> no
On May 26, 2022, at 11:36, Jean Abou Samra wrote:
> I can't tell why the commit "Refactor BarLine engraving" had that
> effect (and I'm not investigating). Dan, any thoughts? Should
> MensuralStaff simply be changed to have measureBarType = ##f
> (instead of "")?
I think that measureBarType = #'
On Apr 30, 2022, at 13:34, Thomas Morley wrote:
>
> I'd offer to change it in LSR to use
> \repeat volta 2 ...
> Would be available after next LSR-import.
That makes sense. Thanks.
—
Dan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://li
On Oct 16, 2021, at 10:58, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
>
> in my opinion we want to
> send users to the mailing list by default.
I don't devote much time to handling bugs (until I'm tagged), but the reports
that have come directly through the GitLab UI have be
Timothy,
I'm looking into the issue. Does adding
\tagGroup #'($partCombine)
early in your score work around the problem?
—
Dan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On Feb 28, 2021, at 08:50, Jean-Charles Malahieude wrote:
>
> Revising the French translation of repeats.itely, I notice that the volta
> bracket doesn't appear in the third staff of the snippet with the master
> branch.
>
> Just compare the two versions of the online documentation of NR-1.41.
On Feb 15, 2021, at 04:44, Thomas Morley wrote:
>
> Here the ".|:"-bar-line is split into "|" at line-end and ".|:" at
> line-begin, but the volta-hook is not allowed for "|".
>
> This is the situation, as far as I can tell.
> The printed outcome is always the same since 2.12.3, although the
> i
On Feb 14, 2021, at 23:26, Jürgen Reuter wrote:
>
> Hi Dan and all others,
>
> yes, the second, more compact / dense version definitely looks _much_ better!
> I would be happy if you could commit your change!
https://gitlab.com/lilypond/lilypond/-/issues/6098
_
As I read Behind Bars, p.237, the bracket for volta 2 should not turn down at
the end in this case. Either way, it's strange that the outcome depends on
line breaking. If someone is willing to second this, I am willing to
investigate it.
—
Dan
\version "2.20.0"
\layout {
ragged-right = ##
Jürgen and all,
I've attached two images of the first system produced for regression test
input/breathing-sign-ancient.ly and included the relevant portion of the input
below.
The current version of master adds some horizontal space after every fourth
note. It happens because there are transp
On Dec 26, 2020, at 13:29, Thomas Morley wrote:
>
> Hi,
>
> the following code gives bad output.
>
> %% Start
> \version "2.20.0"
>
> one = { e''2 \tag #'score f'' \tag #'part fis'' g''1 }
> two = { e''2 d'' g'1 }
>
> \removeWithTag #'score \partCombine \one \two
> %% end
>
> it looks like t
> On Dec 22, 2020, at 14:59, Dan Eble wrote:
>
> I guess that it is undesirable for these bends to cross the barlines. If
> someone validates my judgment, I'll create a ticket and try to improve it.
> —
> Dan
https://gitlab.com/lilypond/lilypo
I guess that it is undesirable for these bends to cross the barlines. If
someone validates my judgment, I'll create a ticket and try to improve it.
—
Dan
\version "2.20.0"
quarters = \fixed c'' {
c4\bendAfter -4
c4\bendAfter -4
\repeat volta 2 {
c2\bendAfter -4
|
c2\bendAfter
On Dec 6, 2020, at 06:39, Jonas Hahnfeld wrote:
>
> (https://gitlab.com/lilypond/lilypond/-/merge_requests/540), but I
> think this means we should not release the stable version 2.22.0
> without the fix and an additional 2.21.82. A bit unfortunate, but
> better now than discovered by users.
+1
> > Absolutely no idea which is correct. Sorry. :/
>
> Dan? I think this issue started occuring after a change of yours, so do you
> have an idea about the meaning of raw-voice becoming #f here?
I'll take a look.
I don't subscribe to bug-lilypond, so I just now saw this because I happened to
b
\version "2.20.0"
{
\set Score.barNumberVisibility = #(every-nth-bar-number-visible 2)
\override Score.BarNumber.break-visibility = #end-of-line-invisible
\repeat volta 2 R1 \alternative { R1 R1 }
}
With master, the bar number is placed up against the volta bracket. With
2.20.0, the bracke
```
\version "2.20.0"
{ \grace c8 \grace d8 e4 }
```
That crashes. The oldest version I tried was 2.20, but I suspect the problem
is ancient. Does anyone disagree that the above would ideally be treated as if
it were this?
```
{ \grace { c8 d8 } e4 }
```
Regards,
—
Dan
__
On Feb 6, 2020, at 18:35, Paolo Prete wrote:
>
> (I re-post this here, because it's a bug and maybe you have an easy fix for
> it)
Paolo,
I'm not sure where you're re-posting from, but the expected forum for bug
reports is https://lists.gnu.org/mailman/listinfo/bug-lilypond . The audience
is
I’ve convinced myself that this is a bug, so I will spend some time trying to
change it and see what happens. I will probably use something like the
following as regression tests.
Regards,
—
Dan
\version "2.19.80"
\layout {
indent = 0
line-width = 2 \cm
}
%% Find the nearest enclosing c
See comment. I am currently working in the guts of the context code, so I
could try to improve this while I’m there, but I would like to hear
confirmation that it is a bug first. Thanks.
\version "2.19.80" % the version I tested
\score {
\new StaffGroup = "A" \with { shortInstrumentName = "X
%% The MIDI output should have key signature of C major, but instead
%% has the key signature of D major.
\version "2.19.80" % the version I'm using
\language "english"
soundingPitch = bf
\score {
\new Staff \with {
instrumentTransposition = \soundingPitch
} <<
\transpose \soundingPi
%% This file is processed without error.
%% Please see my feature request below.
\version "2.19.80"
INSTRUMENT = "Drum Sander"
\bookpart {
%% Instead of defining INSTRUMENT above, I would like to define it
%% here, which is not currently allowed, ...
%{
INSTRUMENT = "Drum Sander"
%}
\head
So difficult to do anything about that it’s not worth tracking.
Very well.
—
Dan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On Sep 3, 2017, at 08:42, Thomas Morley wrote:
> still not sure I really understood what you are after...
> Though, how about below?
> Admittedly, it's only the sketch of an idea, but seems to work
>
> music =
> \new Voice = "m" \repeat volta 2 \relative c'' { c4 c8 c c4 c }
>
> lyrI = \lyricmod
Simon wrote:
> On 02.09.2017 23:11, Dan Eble wrote:
>> David wrote:
>>> Putting different lyrics in sequence to each other does not make a lot of
>>> sense,
>> Isn’t it fundamental to performing a multi-stanza song?
>
> Different lyrics _contexts_ in s
I hope this example makes clear what I’m trying to do. Below is the input, and
attached is what a MIDI editor shows of the output. (I hope it comes through.)
In the output, \unfoldRepeats has unfolded the notes into two measures, but
the lyrics are still concurrent in the first measure (natur
[copying the bug list this time—sorry]
David wrote:
> Putting different lyrics in sequence to each other does not make a lot of
> sense,
Isn’t it fundamental to performing a multi-stanza song?
> and a \lyricsto-governed context in
> particular has no well-defined ending where another context co
%% It is puzzling that none of cases 2-4 produces the same output as
%% case 1. I could not find any known issue in the NR that would
%% explain this.
%%
%% Case 2 is extra puzzling because Lilypond warns that the syllables
%% in { Cc2 Dd } are simultaneous.
\version "2.18.0"
music = \relative c'
On Sep 1, 2017, at 16:27, Dan Eble wrote:
>
> On Aug 30, 2017, at 21:48, Dan Eble wrote:
>
> %% This is probably a bug because even at the quietest
> %% possible dynamic, a note is still a note, so it should be
> %% in the output at the lowest level suppo
On Aug 30, 2017, at 21:48, Dan Eble wrote:
>
> %% Bug: The second word of the lyrics is placed on the second beat, as
> %% if there were no tie.
%% Idea: use another bug to work around the first. =:o
\version "2.19.65"
music = \relative c'' { c4~ c r c }
st
Simon wrote:
> IIUC, Dan’s point was that in \lyricmode, almost all instances of \repeat are
> \repeat unfold. I didn’t read it as concerning any other modes.
I did have an immutable global default in mind. I would expect anything less
to lead to hair-pulling.
—
Dan
_
I don’t know who might care about this, but when Lilypond processes an empty
file, it prints a warning about not finding a \version statement, yet when it
processes a file containing only \include “english.ly”, it does not mention
that there is no \version statement.
—
Dan
___
%% Bug: The second word of the lyrics is placed on the second beat, as
%% if there were no tie.
\version "2.19.65"
music = \relative c'' { c4~ c r c }
stanza = \lyricmode { Good! Not. }
\score {
<<
\new Voice = "V" { \music }
\new NullVoice = "N" { \music }
\new Lyrics { \lyricsto "
It would be convenient if both of these did the same thing:
A. \lyricmode { Ah __ \repeat unfold 7 _ }
B. \lyricmode { Ah __ \repeat 7 _ }
Thanks,
Dan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-li
%% Semantically, the melisma ends at the skip.
%% In the output, the extender continues to the next syllable.
\version "2.19.65"
<<
\context Voice = "V" { c''2 2 2 2 }
\context Lyrics \lyricsto "V" { Ah __ _ \skip 1 buh. }
>>
Regards,
Dan
___
bug-l
\version "2.19.58"
%% engrave dynamics in Staff context
\layout {
\context {
\Staff
\consists "Dynamic_engraver"
\consists "Dynamic_align_engraver"
}
\context {
\Voice
\remove "Dynamic_engraver"
\remove "Dynamic_align_engraver"
}
}
%% This causes a warning, yet the
> On Apr 7, 2017, at 03:58, David Kastrup wrote:
>
>> Please try this. I haven’t tested your patch.
>
> I'm sort of annoyed at the somewhat roundabout \RemoveEmptyStaves bit
> but I guess that's likely a pretty direct way to figure out where the
> NullVoice went. One doesn't get to see a lot
> Tracker issue:
> 5116 (https://sourceforge.net/p/testlilyissues/issues/5116/)
> Rietveld issue:
> 322820043 (https://codereview.appspot.com/322820043)
Thank you.
> Could you rework your almost minimal example into a regtest?
> Those give me much more of a headache than most code changes
> since
David Kastrup writes:
> For something like
>
> \change StaffGroup = "what"
>
> the change iterator looks at the current context hierarchy upwards until
> it finds a "StaffGroup" as a parent. The layer below that is the
> context to move, and if it is significantly similar in specification to
>
On Apr 4, 2017, at 22:57, Colin Campbell wrote:
>
>
> Staff "S" doesn't have a NullVoice defined. I modified your code as follows,
> and it seems to do what you want, although you still get a warning because
> the \changeStaff event happens in both a regular Voice and a NullVoice.b
Thank you
On Mar 25, 2017, at 14:34, Dan Eble wrote:
>
> NullVoice is unlike a Voice in this respect: trying to move it to a
> different Staff with \change fails with this warning:
>
>Change_iterator::process (): NullVoice = `soprano':
>cannot change `Staff' to `S&#x
David wrote:
> It would seem more sensible to change overrides to have
> tweak syntax and forego the gratuitous equals sign.
That would be an improvement.
—
Dan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/b
On Mar 27, 2017, at 22:20 , Simon Albrecht wrote:
>
>> This command can produce either an \override or a \tweak of
>> a spanner property.
>
> But that’s exactly the point: \alterBroken (and \shape and \offset) can act
> _both_ as an override _and_ a tweak, so its syntax must be differen
> Am 27.03.2017 um 23:32 schrieb Dan Eble:
>>
>> This is the current syntax:
>> \alterBroken property-name #’(before after) GrobName
>> This would be more consistent with other things:
>> \alterBroken GrobName.property-name #’(before after)
>>
&
> On Mar 27, 2017, at 17:32 , Dan Eble wrote:
>
> This is the current syntax:
>
>\alterBroken property-name #’(before after) GrobName
>
> This would be more consistent with other things:
>
>\alterBroken GrobName.property-name #’(before after)
>
Notatio
This is the current syntax:
\alterBroken property-name #’(before after) GrobName
This would be more consistent with other things:
\alterBroken GrobName.property-name #’(before after)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://
%{
NullVoice is unlike a Voice in this respect: trying to move it to a
different Staff with \change fails with this warning:
Change_iterator::process (): NullVoice = `soprano':
cannot change `Staff' to `S': not changing to same context type: Staff
Apart from the warning, this is inconven
The NR has this:
> harmonicNote [music] - note (music)
> Print note with a diamond-shaped note head.
Does \harmonicNote c4 do more than c4\harmonic? If so, it would be nice to
document what. If not, perhaps convert-ly could replace it out of existence.
If a documentation update is undertaken
> > %% Harmonic does not carry through a tie.
> > \version "2.19.42"
> > { ~ 4 }
>
> As documented and intended.
>
> Durations occuring on their own within a music
> sequence will take their pitches from the preceding
> note or chord.
>
> Nothing but the pitch is taken.
1. Adding “
%% Harmonic does not carry through a tie.
\version "2.19.42"
{ ~ 4 }
—
Dan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
> On Feb 7, 2016, at 09:59 , Dan Eble wrote:
>
>
>> On Feb 7, 2016, at 09:57 , Thomas Morley wrote:
>>
>> 2016-02-07 15:43 GMT+01:00 Dan Eble :
>>> % Lilypond does not apply staccato to chords in the MIDI output.
>>> % A shot of opening LP output
> On Feb 7, 2016, at 09:57 , Thomas Morley wrote:
>
> 2016-02-07 15:43 GMT+01:00 Dan Eble :
>> % Lilypond does not apply staccato to chords in the MIDI output.
>> % A shot of opening LP output in another program is attached.
>
> Hi Dan,
>
> can't find
% Lilypond does not apply staccato to chords in the MIDI output.
% A shot of opening LP output in another program is attached.
% Tested with 2.19.36.
\version "2.19.0"
\score {
\new Staff { c-. -. -. }
\midi {}
}
Regards,
—
Dan
___
bug-lilypond
On Jan 17, 2016, at 06:15 , Simon Albrecht wrote:
>
> Please give a minimal example. Seems sensible, though.
%% The uneven spacing of the notes would be helped by removing the
%% space after "tuh—“.
\version "2.19.0"
\layout {
ragged-right = ##t
}
aNotes = \relative c'' { c8 d e f c4 }
stanz
Lilypond seems to want to keep a minimum amount of space between all lyric
words. It would be nice if it understood without being told that space can be
reduced after an em dash. I’m getting "message— now” where “message—now” would
look better.
(No need to offer tweaks; I’m not dedicated enou
In issue #2458 (Remove small gaps between lyric syllables), Janek says:
>
> I agree that sometimes a hyphen is necessary, "call-ed" being a good example.
>
In a tight place this could be rendered "callèd” but it shouldn't be "call-èd"
when there is room for the hyphen. It would be nice if there
Feature request:
* ability to configure a line-break penalty applied automatically at hyphens in
the lyrics
* ability to configure a greater penalty for the first hyphen in the word than
for the rest
* maybe ditto for the last hyphen (not sure how useful it is)
Regards,
—
Dan
> On Oct 23, 2015, at 19:37 , Simon Albrecht wrote:
>
> Perhaps it’s immediately understandable by someone more technically apt than
> me, but I can’t see what you actually did here, when the error occurred. Did
> you compile an .ly file? Could you share a minimal example?
I don’t have time.
Simon Albrecht mail.de> writes:
> On 18.10.2015 13:25, Gilberto Agostinho wrote:
> > Hi Simon,
> >
> > Thanks for the reply. I am not sure I understand your answer, do you
> > mean that in the tiny example I created I should simply have used a
> > "Solo I" indication in the fourth bar instead o
Forgive me for being brief, but I thought I should at least mention this in
case someone would like to approach it with code review:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 lilypond0x001f35ff
Slur_proto_engraver::derived_mark() const + 79
1 lily
On Aug 13, 2015, at 09:36 , Simon Albrecht wrote:
> Am 01.08.2015 um 19:35 schrieb Dan Eble:
>> add a variant of \include which does nothing if the file does not exist
>> (eliminating one reason to have empty files in the first place)
[…]
> surely we would want \include to com
I have a couple of related suggestions. These would be minor conveniences—so
minor that I don’t care enough at the moment to implement them myself.
let convert-ly remain silent about files which contain only whitespace (or
which are empty) rather than issuing an error that there is no \version
Percent repeats are omitted from cues. I suggest that the percents should
appear by default.
Using \addQuote … \unfoldRepeats … is a work around if there are no repeats
that the user does not want expanded (e.g. voltas). If there were a way to
unfold percent repeats selectively, that might be
On Jun 30, 2015, at 08:47 , Dan Eble wrote:
> On Jun 30, 2015, at 04:41 , Federico Bruni wrote:
>> Il giorno mar 30 giu 2015 alle 1:12, Dan Eble ha scritto:
>>> %% This tie is nearly invisible before the line break.
>>> \score {{ r2 f'8 f' f' f'~
On Jun 30, 2015, at 04:41 , Federico Bruni wrote:
>
> Il giorno mar 30 giu 2015 alle 1:12, Dan Eble ha scritto:
>> %% This tie is nearly invisible before the line break.
>> \score {{ r2 f'8 f' f' f'~ \break | f'2 r }}
>
> I believe that this
\version “2.14.0”
\layout { indent = 0 }
\paper { paper-width = 6 \cm }
%% The first and second ties look different. Is there a good reason?
%% IMHO, the first is not conspicuous enough because it is too close
%% to the staff line.
\score {{ f'4 f'~ f'8 f'~ f'4 }}
%% This tie is nearly invisible
% slur collides with stem and flag of starting note
\version "2.16.0"
\layout { indent = 0 }
\paper { paper-width = 6 \cm }
{ \clef "bass" \key d \major d4 r r r8 a,8( \break | d4) r }
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gn
The Notation Reference says that \autochange "looks ahead skipping over rests
to switch in advance” and provides an example with a single rest. When there
are multiple rests, it doesn’t move them all, which seems like a bug based on
the NR.
I’ve prepared a patch to change this, but I haven’t cr
% 2.19.20 does not engrave the lyrics and stops engraving the vocal
% staff before the end. (Compare to 2.18.2.) I haven’t tested MIDI.
\version "2.18.0"
\include "english.ly"
vocal = \relative c'' { R1 | f2 c }
% adding the skip makes 2.19.20 work
accomp = \relative c'' { c1 %{ s1 %} }
\scor
Dan Eble faithful.be> writes:
>
> Dan Eble faithful.be> writes:
>
> > \context Lyrics = "lyricsI" <<
> > % The lyrics do not appear when this "alignBelowContext" is set.
> > \set alignBelowContext = "upper&qu
https://code.google.com/p/lilypond/issues/detail?id=4402
Patch: Part combiner: Ignore skips coinciding with rests within a part
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
James Lowe gnu.org> writes:
> On 15/05/15 22:38, H. S. Teoh wrote:
> > % The triplet in the first argument to \partcombine is wrongly
> > % formatted in the output; the tuplet bracket only spans the two quarter
> > % rests, whereas it should span both rests and the single note.
> > %
> > % - Note:
After this commit
commit 386c1fb71fef99d9ac865ccd1449412c26cef5cc
Author: Dan Eble
Date: Sun Nov 23 23:55:03 2014 -0500
The rests in this example are not merged when \global is present in
the individual voices. If \global is removed, the rests are merged.
It is tempting to say that
H. S. Teoh quickfur.ath.cx> writes:
> % Arguably, using \tag with \partcombine is a bad idea, since it can
> % easily result in constructs that are probably not representable in a
> % way that would make a subsequent \removeWithTag work correctly, but
> % Lilypond should at least give a warning an
Dan Eble faithful.be> writes:
> % When these are added, the voice settings below are
> % ignored and the resulting warning is cryptic.
I just realized this is useful behavior. What's missing is to document
how \with{} works in section 5.1.2 of the Notation Reference
H. S. Teoh quickfur.ath.cx> writes:
> \score {
> \removeWithTag #'midi {
> \partcombine \fluteIPart \fluteIIPart
> }
> }
Have you tried filtering before combining?
\partcombine \removeWithTag #'midi \fluteIPart \removeWithTag #'midi
\fluteIIPart
--
Dan
__
Dan Eble faithful.be> writes:
> \context Lyrics = "lyricsI" <<
> % The lyrics do not appear when this "alignBelowContext" is set.
> \set alignBelowContext = "upper"
It also happens with \set stanza.
--
Dan
\version "2.19.16"
aNotes = \relative c'' { c4 d e f }
stanzaI = \lyricmode { La la la la }
\score {
<<
\context Staff = "upper" <<
\new Voice = "melody" \aNotes
>>
\context Lyrics = "lyricsI" <<
% The lyrics do not appear when this "alignBelowContext" is set.
\version "2.19.15"
\score {
\new Staff <<
%{
% When these are added, the voice settings below are
% ignored and the resulting warning is cryptic.
\context Voice = "one" \with { \override NoteHead.color = #red }
\context Voice = "two" \with { \override NoteHead.color = #blue }
%}
David Kastrup gnu.org> writes:
> Dan Eble faithful.be> writes:
> So what do you expect for
>
> { <\hide c'' e''>4 }
>
> Stem or no stem?
Good question. In that context, hiding just the head would not surprise me.
But then what about {\hide 4
On Apr 7, 2015, at 00:23 , Pierre Perol-Schneider
wrote:
>
> 2015-04-07 3:35 GMT+02:00 Dan Eble <mailto:d...@faithful.be>>:
> % Is this supposed to leave a stem showing?
> \version "2.19.17"
> \hide c''4
>
> Yes, because equivalent to:
>
% Is this supposed to leave a stem showing?
\version "2.19.17"
\hide c''4
—
Dan
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Dan Eble faithful.be> writes:
> Does anyone else think that the automatic placement of the second
> rest in this example is distractingly low in the “z” style?
A few examples have all the rests on the bottom staff line, and this
one places the first rest even higher:
http://www.hymnary
Does anyone else think that the automatic placement of the second rest in this
example is distractingly low in the “z” style? (If you have enough experience
to suggest a solution, please do. I haven’t looked at the rest collision code
yet.) Thanks.
—
Dan
\version "2.19.16"
\language "englis
1 - 100 of 149 matches
Mail list logo
