Re: first-page-number silently ignored sometimes

2022-09-07 Thread Nikolai Hedler
Putting the function inside a bookpart's paper block causes it to have no effect. - Nikolai On Wed, Sep 7, 2022, 19:34 Jean Abou Samra wrote: > Le 08/09/2022 à 01:31, Nikolai Hedler a écrit : > > Hello, > > > > When attempting to determine the correct usage of

first-page-number silently ignored sometimes

2022-09-07 Thread Nikolai Hedler
Hello, When attempting to determine the correct usage of "first-page-number" in a (fairly complex) project, I first found that it did nothing at all - even with absurd inputs (e.g. first-page-number = asdf) it changed nothing and the compiler carried on silently - no errors, warnings, or other ind

warning/note in 2.23.12 about source file mismatch

2022-09-01 Thread Nikolai Hedler
Hello, When moving to 2.23.12 to check it out, I encountered the following warning at the end of compilation: ;;; note: source file C:/Program Files/lilypond-2.23.12/share/lilypond/2.23.12/scm/lily/font-encodings.scm ;;; newer than compiled C:/Program Files/lilypond-2.23.12/lib/lilypond/2.23.12/

Re: v2.23.8: \fine seems to break \midi

2022-08-29 Thread Nikolai Hedler
it plays a bit with unfolding, but not by redefining the default > implementation, as far as I can see. Do you remember what you changed in > articulate.ly? > >/Mats > On 2022-07-01 16:42, Nikolai Hedler wrote: > > For what it's worth, I deleted the implementation of \u

Re: v2.23.8: \fine seems to break \midi

2022-07-01 Thread Nikolai Hedler
amra [1] wrote: > > Le 28/06/2022 à 01:33, Nikolai Hedler a écrit : > > MIDI ends late if |\fine| followed by a pitch. > > [2]https://gitlab.com/lilypond/lilypond/-/issues/6368 > > > Beaming and |\fine| > > [3]https://gitlab.com/lilypond/lilypond/-/issues/6

Re: v2.23.8: \fine seems to break \midi

2022-06-27 Thread Nikolai Hedler
nding the ideal number of pages...Fitting music on 1 page...Drawing systems...Converting to `document.pdf'...This object should be a markup: ()Success: compilation successfully completed - Nikolai On Tue, May 17, 2022 at 4:38 AM Jean Abou Samra wrote: > > > Le 09/05/2022 à 20:11, N

v2.23.8: \fine seems to break \midi

2022-05-09 Thread Nikolai Hedler
Windows 10, 64-bit I discovered the new \fine feature and looked to implement it in a project of mine, and I believe I've discovered a bug in its interaction with \midi blocks. The following appears to be a minimal example which produces the error for me: \version "2.23.8" \score { \unfoldRepea

Re: isolated durations after isolated pitches - intended behavior?

2022-03-23 Thread Nikolai Hedler
wrote: > Le 23/03/2022 à 22:59, Nikolai Hedler a écrit : > > Hello! > > > > First of all, thanks to all the developers for their continued efforts! > > > > I am coming back to LIlypond after a couple years away, and found the > > addition of unpitched dur

isolated durations after isolated pitches - intended behavior?

2022-03-23 Thread Nikolai Hedler
Hello! First of all, thanks to all the developers for their continued efforts! I am coming back to LIlypond after a couple years away, and found the addition of unpitched durations an interesting shorthand feature, but encountered a behavior I didn't expect. It seems that a pitch without explicit

Re: Midi block gives errors with bar number checks

2019-11-27 Thread Nikolai Hedler
For what it's worth, I'm one of those users who makes use of the MIDI output from LilyPond frequently, and while I have not needed to mess with bar numbers on the MIDI side, I have found it's repeat support serviceable aside from D.C./D.S. being unsupported. Unfortunately, in my current project, I'

Re: \parenthesize is not affected by \tweak

2019-01-29 Thread Nikolai Hedler
I'm an outside party here, but I think you would find some answers by investigating LilyPond's definition of "music object" further; it sounds like you're being tripped up by that. - Nikolai On Tue, Jan 29, 2019, 15:07 Pierre Perol-Schneider < pierre.schneider.pa...@gmail.com wrote: > What I mea