Kieren MacMillan writes:
> Hi all,
>
> The error turned out to be caused by the fact that the lower staff
> already contained a rest at the moment where I was [accidentally, via
> my \pfUTwo function] trying to also have a sixteenth note g.
>
> Unless this quick mention/report turns out to be int
Hi David,
> With regard to "have not caused problems before": after version 2.19.22,
> assertions were enabled for the default compilations. The given
> assertion triggers when a definite direction is required but 0 or
> #CENTER given. "changing staves/voices" sounds like something where one
> c
Hi all,
The error turned out to be caused by the fact that the lower staff already
contained a rest at the moment where I was [accidentally, via my \pfUTwo
function] trying to also have a sixteenth note g.
Unless this quick mention/report turns out to be interesting to the developers
in terms
Kieren MacMillan writes:
> Hello all,
>
> Until a few minutes ago, my score was compiling fine (2.19,46). Now I
> am getting the following error:
>
>> /home/gub/NewGub/gub/target/darwin-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/drul-array.hh:35:
>> failed asser
Hello all,
Until a few minutes ago, my score was compiling fine (2.19,46). Now I am
getting the following error:
> /home/gub/NewGub/gub/target/darwin-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/drul-array.hh:35:
> failed assertion `d == 1 || d == -1’
> Exited w
