Accordion notation
I noticed part of the source code for the accordion example is missing, hiding the information that the use-modules statement has been changed from #(use-modules (scm accreg)) to #(use-modules (lily accreg)). http://lilypond.org/doc/v2.23/Documentation/notation/accordion -- Timothy Lanfear, Bristol, UK. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Change staff with horizontal bracket engraver
Since 2.23.3, this example produces several error messages of the type
programming error: cyclic dependency: calculation-in-progress
encountered for #'adjacent-pure-heights (VerticalAxisGroup)
continuing, cross fingers
\version "2.23.3"
\layout {
\context { \Voice \consists "Horizontal_bracket_engraver" }
}
\new StaffGroup <<
\new Staff="A" {
s1*2
}
\new Staff="B" {
c'1\startGroup \change Staff="A" c'1\stopGroup
}
>>
--
Timothy Lanfear, Bristol, UK.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Changed behaviour of tag and partCombine
On 12/10/2021 22:55, Dan Eble wrote: Timothy, I'm looking into the issue. Does adding \tagGroup #'($partCombine) early in your score work around the problem? — Dan Yes, adding the \tagGroup does bring back the missing music. -- Timothy Lanfear, Bristol, UK. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Changed behaviour of tag and partCombine
From at least 2.18 to 2.23.3, it was possible to place \tag and
\keepWithTag outside of \partCombine. Version 2.23.4 requires the
tagging inside \partCombine. I do have a lot of files expecting the old
behaviour.
\version "2.22.1"
{
\keepWithTag #'t \tag #'t \partCombine c''1 c'1
}
{
\partCombine \keepWithTag #'t \tag #'t c''1 \keepWithTag #'t \tag #'t c'1
}
--
Timothy Lanfear, Bristol, UK.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Bad slur shape at line break with change of clef
The part of the slur before the line break is badly shaped when another
staff has a clef change.
\version "2.20.0"
<<
\new Staff {
R1*2
r2 r4 r8 r16 r32 e''32( |
\break
d''8) r r4 r2 |
R1*3
}
\new Staff {
R1*3
\clef "bass"
R1*4
}
>>
--
Timothy Lanfear, Bristol, UK.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
convert-ly rule for tocItem
Applying convert-ly (2.21.5) to this file produces illegal output with
the first double quote escaped by a backslash
\version "2.20.0"
\tocItem "Score A"
score { { a'1 } }
Output
\version "2.21.2"
\tocItem \markup \"Score A"
\score { { a'1 } }
--
Timothy Lanfear, Bristol, UK.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Small bugs in "Changes" document
The descriptions of changes to \powerChords, \partcombine and \autochange have acquired an extra backslash. -- Timothy Lanfear, Bristol, UK. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: musicxml2ly Pitch Changing Potential Bug
Alex Hansen wrote > I think I have found a bug. The following musicXML, when run through > musicxml2ly, produces lilypond which has entirely different pitches. I've > cut out as much of the XML as possible to ensure it is a minimal example. > Note that the musicXML specifies a single D whole note, but when it goes > through to lilypond, it comes out as an A. > > > > > > > > d > > > > 4 > > > > > > 4 > > > > whole > > > In MusicXML, the contents of the step element must be in uppercase. Change d to D and it should work. - Timothy Lanfear, Bristol, UK. -- Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Setting rehearsal mark value in non=default context
On 22/10/16 11:37, Phil Holmes wrote: Please see http://lilypond.1069038.n5.nabble.com/Mark-numbering-incorrect-at-staff-level-td195296.html for exactly the same situation. Thanks for the pointer to the solution. -- Timothy Lanfear, Bristol, UK. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Setting rehearsal mark value in non=default context
An integer argument to \mark is not respected if the mark engraver is
moved from the Score context. The example creates rehearsal marks "A",
"B", not "A", "C".
\version "2.19.49"
\layout {
\context {
\Score
\remove "Mark_engraver"
\remove "Staff_collecting_engraver"
}
\context {
\Staff
\consists "Mark_engraver"
\consists "Staff_collecting_engraver"
}
}
<<
\new Staff { R1 R1 R1 }
\new Staff { R1 \mark \default R1 \mark #3 R1 }
>>
--
Timothy Lanfear, Bristol, UK.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Core dump with combination of tie, fermata and some pitches
On 02/09/16 17:31, David Kastrup wrote:
Timothy Lanfear <timo...@lanfear.me> writes:
Bug appears in 2.19.46 and .47. Ubuntu 16.04, 64-bit.
The first line provokes a core dump. The second line is perhaps the
right syntax for this construction and works fine, but I'm reporting
in case there is something here that needs investigating.
\version "2.19.46"
{
<b' gis'>2\fermata ~ b'2 % core dump
<b'~ gis'>2\fermata b'2 % move tie inside chord, OK
<b' g'>2\fermata ~ b'2% gis => g, OK
<b' gis'>2 ~ b'2 % delete fermata, OK
<b' gis'>2\fermata b'2% delete tie, OK
}
Not here. Which compilations are you using? I suspect some compiler
bug or overoptimization.
I'm using the pre-built package.
lanfear@D20$ /usr/local/lilypond-2.19.46/bin/lilypond tmp.ly
GNU LilyPond 2.19.46
Processing `tmp.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...Segmentation fault (core dumped)
--
Timothy Lanfear, Bristol, UK.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Core dump with combination of tie, fermata and some pitches
Bug appears in 2.19.46 and .47. Ubuntu 16.04, 64-bit.
The first line provokes a core dump. The second line is perhaps the
right syntax for this construction and works fine, but I'm reporting in
case there is something here that needs investigating.
\version "2.19.46"
{
<b' gis'>2\fermata ~ b'2 % core dump
<b'~ gis'>2\fermata b'2 % move tie inside chord, OK
<b' g'>2\fermata ~ b'2% gis => g, OK
<b' gis'>2 ~ b'2 % delete fermata, OK
<b' gis'>2\fermata b'2% delete tie, OK
}
--
Timothy Lanfear, Bristol, UK.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Simultaneous notes yield "programming error"
See the similar report by me to this list on 6 August and Harm's reply.
Timothy Lanfear
> On 2 Sep 2016, at 08:38, Simon Albrecht <simon.albre...@mail.de> wrote:
>
> Hi Joel,
>
> thanks for the report.
>
> On the user list, I may have exaggerated my zeal for minimal examples. Here
> on the bug list, however, they are more strictly required, so the bass clef
> and bar checks (which I believe are certainly unrelated with the bug – can’t
> test on Linux) could’ve been left out. Also it will be very much appreciated
> if you revise your code formatting. Privately, you may do whatever you like,
> but sharing code requires complying to some conventions such as indenting by
> two spaces, giving closing brackets or braces their own line if the opening
> struct also has one See attached.
>
> And don’t misunderstand me: This is not about my personal preferences, but
> badly formatted code is an obstacle in understanding it.
>
> I’ll wait submitting an issue tracker and see if somebody can say some more
> on what the actual problem is.
>
> Best, Simon
>
>
>> On 02.09.2016 05:57, Joel C. Salomon wrote:
>> Compiling the attached file with LilyPond 2.19.46 on Windows 10 64-bit
>> via Frescobaldi yields:
>>
>> Starting lilypond-windows.exe 2.19.46 [programming_error.ly]...
>> Processing
>> `c:/users/chesky/appdata/local/temp/frescobaldi-irr7t1/tmpc362im/programming_error.ly'
>> Parsing...
>> Interpreting music...
>> Preprocessing graphical objects...
>> Interpreting music...
>> MIDI output to `programming_error.mid'...
>> programming error: asked to compute volume at +1.00 for dynamic
>> span of duration 1.00 starting at 1
>> continuing, cross fingers
>> programming error: asked to compute volume at +1.00 for dynamic
>> span of duration 1.00 starting at 1
>> continuing, cross fingers
>> Finding the ideal number of pages...
>> Fitting music on 1 page...
>> Drawing systems...
>> Layout output to `./tmp-lilypond-XEJJlg'...
>> Converting to `programming_error.pdf'...
>> Deleting `./tmp-lilypond-XEJJlg'...
>> Success: compilation successfully completed
>> Completed successfully in 1.3".
>>
>> Replacing the << {} \new Voice {} >> structure with << {} \\ {} >>
>> makes this go away; interestingly, simply writing << \new Voice {}
>> \new Voice {} >> still yields the error.
>>
>> Giving the note immediately following the << >> structure an explicit
>> dynamic (\f, for example) also makes the error disappear.
>>
>> —Joel C. Salomon
>>
>>
>> ___
>> bug-lilypond mailing list
>> bug-lilypond@gnu.org
>> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
MIDI programming error with polyphony
Bug first appears in 2.19.46.
\version "2.19.46"
\score {
{ a'4 << \new Voice a'4 \new Voice f'4 >> a'2 }
\midi{}
}
generates
GNU LilyPond 2.19.46
Processing `tmp.ly'
Parsing...
Interpreting music...
MIDI output to `tmp.midi'...
programming error: asked to compute volume at +0.25 for dynamic span
of duration 0.25 starting at 1/4 continuing, cross fingers
programming error: asked to compute volume at +0.25 for dynamic span
of duration 0.25 starting at 1/4 continuing, cross fingers
Success: compilation successfully completed
--
Timothy Lanfear, Bristol, UK.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Header fonts
Fonts for the header fields are not set correctly for the second and
subsequent books in a file.
Pre-built version 2.19.45, 64-bit Linux.
\version "2.19.45"
\header { title = "Title" composer = "Composer" }
\book { \score { a'1 } }
\book { \score { a'1 } }
--
Timothy Lanfear, Bristol, UK.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Mistake in addInstrument example
I'm not top posting.
Notation reference section 2.1.6. The example illustrating the use of
addInstrumentDefinition sets instrumentTransposition context properties
incorrectly. The midi output for Kaspar is an octave too low. The
transposition for Melchior is harmless but unnecessary.
\addInstrumentDefinition #kaspar
#`((instrumentTransposition . ,(ly:make-pitch -1 0 0))
(shortInstrumentName . Kas.)
(clefGlyph . clefs.G)
(clefTransposition . -7)
(middleCPosition . 1)
(clefPosition . -2)
(instrumentCueName . ,(markup #:fontsize 1 #:smallCaps Kaspar))
(midiInstrument . voice oohs))
\addInstrumentDefinition #melchior
#`((instrumentTransposition . ,(ly:make-pitch 0 0 0))
(shortInstrumentName . Mel.)
(clefGlyph . clefs.F)
(clefTransposition . 0)
(middleCPosition . 6)
(clefPosition . 2)
(instrumentCueName . ,(markup #:fontsize 1 #:smallCaps Melchior))
(midiInstrument . choir aahs))
\score {
\relative c' {
\instrumentSwitch kaspar
c4 c c c
\instrumentSwitch melchior
a4 a a a
\instrumentSwitch kaspar
c4 c c c
}
\midi{}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: InstrumentSwitch in CueVoice
Keith OHara k-ohara5a5a at oco.net writes: Would markup work just as well in your case ? labelTreble = ^\markup\boldtreb. This automatically conforms to the size of the Voice or CueVoice in which it is used. Or, do you do other things with the addInstrumentDefinition ? I mostly use Lilypond for setting recorder consort music. Changing instrument during a piece is not uncommon, so I've set up instrument definitions for all sizes of recorder. I was hoping to reuse what I already had for cues -- after all, the docs suggested it would work. Automatically printing cue clefs is a handy feature that is used the score that lead to this discussion. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: InstrumentSwitch in CueVoice
Keith OHara k-ohara5a5a at oco.net writes:
Oops. The docs say
The placement and style of the instrumentCueName is controlled by
the \instrumentSwitch object,
but that should be the InstrumentSwitch object, as in
\once\override InstrumentSwitch #'font-series = #'bold
\set instrumentCueName = ten.
The double printing from an \instrumentSwitch is issue 2835.
\instrumentSwitch has been called into service for two jobs
Thanks. you gave me enough hints to construct my preferred solution.
\version 2.17.97
\addInstrumentDefinition #Treble
#`((instrumentCueName . ,(make-bold-markup treb.)))
\addInstrumentDefinition #Tenor
#`((instrumentCueName . ,(make-bold-markup ten.)))
\layout { \context { \CueVoice \remove Instrument_switch_engraver } }
{
g'1
\once \override InstrumentSwitch.font-size = #-4
\new CueVoice {
\instrumentSwitch Treble
g'1
}
\instrumentSwitch Tenor
g'1
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Pitched trill layout
I'm not top posting
Layout of pitched trills with an interval greater than a third became worse
in 2.17.10.
\version 2.17.10
\relative c' {
\pitchedTrill f2 \startTrillSpan g r2 \stopTrillSpan
\pitchedTrill f2 \startTrillSpan a r2 \stopTrillSpan
\pitchedTrill f2 \startTrillSpan b r2 \stopTrillSpan
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Marks right-aligned in unstable
Marks are aligned to the right edge of objects in unstable release, whereas they are centred in the stable release in agreement with the documentation. Compare, for example, the arrow above the treble clef in the example near the end of http://www.lilypond.org/doc/v2.16/Documentation/notation/writing-text#text-marks with http://www.lilypond.org/doc/v2.17/Documentation/notation/writing-text#text-marks ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 3363: Scripts misplaced with cross-staff slurs
I'm not top posting.
Issue 3363 has reappeared in 2.17.20; 2.17.19 was fine. I'm using Windows
32-bit.
\version 2.17.20
\new Staff = R { s2 }
\new Staff = L {
\new Voice {
\voiceTwo
f'8 \change Staff=R f'( \change Staff=L f'_. f')
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Bad vertical spacing with instantiated staves
I'm not top posting.
I tried 2.17.16 and found vertical spacing was much looser than 2.16.2 when
instantiating ossia staves. 2.17.14 was the first release to exhibit this
behaviour. The effect is only seen when the music extends over more than one
page, hence the large repeat unfold in the example.
\version 2.17.14
{
c''1
c''1
\new Staff c''1
\repeat unfold 120 c''1
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
