"Library not loaded" error on MacOS version

g the same problem, and if so, what was your workaround? --- Christopher Heckman ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Polychord Support

> Message: 2 > Date: Sat, 29 Jan 2022 21:30:36 +0100 > From: skoop...@web.de > To: bug-lilypond@gnu.org > Subject: Polychord support > Message-ID: > > > > Content-Type: text/plain; charset=UTF-8 > > Hello, > > is there meanwhile an easy way to write polychords as a chord name? I found a

Re: polyphony and TabStaff: don’t put two voices on the same string (Malte Meyn)

> Malte Even worse, Lilypond can slide from one note to a note on another string, with something like c \\glissando c'. (The octaves might need adjusting.) A few years ago, I worked on an improved tablature algorithm, but could never get github (or something like it) to work so that other people cou

Request: Print actual number of pages after compiling

Obviously, in this situation, I want to know the exact number of pages without re-opening the .pdf file. Could someone add a one-line statement to print out the actual number of pages, near the "Success: compilation successfully completed" message? ---

Re: bug-lilypond Digest, Vol 197, Issue 11

On Thu, Apr 25, 2019 at 9:05 AM wrote: > > Am Mi., 24. Apr. 2019 um 23:24 Uhr schrieb Christopher Heckman > : > > > > I searched for this at the archives, but maybe I didn't look in the right > > place. > > > > The title is pretty self-expanatory. If the pi

Bug: q doesn't keep fingerings in TabStaff context

, even if you put a tie after . (This is Lilypond version 2.18.) --- Christopher Carl Heckman ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: bug-lilypond Digest, Vol 189, Issue 17

On Sun, Aug 26, 2018 at 7:04 AM, wrote: > > Message: 3 > Date: Sun, 26 Aug 2018 11:43:44 +0200 > From: Thomas Morley > To: Pierre Perol-Schneider > Cc: bug-lilypond > Subject: Re: Doc 2.4.2: Indicating harmonics and dampened notes > Message-ID: > > Content-Type: text/plain;

[no subject]

> From: Dan Eble > Subject: Default repeat type > > It would be convenient if both of these did the same thing: > > A. \lyricmode { Ah __ \repeat unfold 7 _ } > B. \lyricmode { Ah __ \repeat 7 _ } Maybe the user should be able to set the default repeat type? After all,

Re: bug-lilypond Digest, Vol 173, Issue 17

On Mon, Apr 17, 2017 at 9:00 AM, <bug-lilypond-requ...@gnu.org> wrote: > > On Sun, Apr 16, 2017 at 9:00 AM, Martin Tarenskeen > <m.tarensk...@zonnet.nl> wrote: > > On Sun, 16 Apr 2017, Christopher Heckman wrote: > >>> I like the idea and really apprecia

midi2ly: Fraction Reduction + 2 minor issues

a cryptic comment # urg, this will barf at meter changes Is there a brief explanation of the problem available? ====== Christopher Carl Heckman Honors Faculty Lecturer 33° 25' 7'' N, 111° 55' 55'' W ECA 212 School of Mathematical & Statistical Sciences Arizona State University

Re: Issue 2214 in lilypond: "fatal error" reported when version is too old but correct output is still generated

As Gus Baird once said, when something goes wrong in a program, you should inform a user in the least surprising way. --- Christopher Heckman -- View this message in context: http://lilypond.1069038.n5.nabble.com/Issue-2214-in-lilypond-fatal-error-reported-when-version-is-too-old-but-correct

Re: Mark / Barcheck Bug (#1626) Appearing Again

After playing around with Lilypond for a while, I found out that \mark appears to "gobble up" the next token in the list. For example, \new Staff { c \mark | c c c | } and \new Staff { c c c c | c c c \mark | c | c c c c | } should give barcheck errors but don't. That's because

Mark / Barcheck Bug (#1626) Appearing Again

This was mentioned about five years ago, but I re-discovered it. Does the so-called patch fix this? The bug is as follows: Placing the \mark can have an effect on the bar check. If you run Lilypond with the following code, the barcheck will fail exactly once. --- CCH \new Staff { \mark | c4 c c

Behavior on Errors; Separate Run Output

. Some sort of a separator (even if it's just hyphens) should be put between compilings. --- Christopher Heckman ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

tie placement bug

I'm not top posting. % It is hard to tell from looking which note a tie goes with. % Tie on E is placed as though it is a tie on G or C when the C below it is % preceded by an accidental. sharp or flat sign \version 2.18.0 \relative g' { | g e ~ c2 ^\markup \column { tie E can't tell C or E

Re: Composer header field with large staff size

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/06/2012 07:57 PM, Nick Payne wrote: With a large staff size and a longish composer field, the composer name runs off the right-hand edge of the page, even though there is plenty of room for it to be accommodated within the left and right

Dokumentation- Links to snippets in Translations

Hi! I often read the german translation of the manual. When follow a link to the snippets list, the URL is wrong, because it is translated too. Wrong: http://www.lilypond.org/doc/v2.14/Documentation/snippets/tonhohen Right: http://www.lilypond.org/doc/v2.14/Documentation/snippets/pitches I do

LilyPond ignores copyright assertions for scores in a book.

As posted to lilypond-user, assertion of copyright in a score header has no discernible effect on the output. I don’t much care where it ends up, but it ought to do something. The attached tiny example was made with 2.12, but apparently the problem persists in 2.14 and up. [Er... I don’t seem

Collision of hyphen and barline

I'm not top posting. %This is e.g. a problem for engraving a choral piece with barlines in mensural style. Maybe this is a special case of bug #2061, but I wasn't sure. \version 2.14.2 \new StaffGroup \new Staff { r1 r} %Collision of hyphen and barline \new

Bug in Piano Pedal instructions

-position = 1 ( or 0,-1) \override Staff.PianoPedalBracket #'direction = #CENTER ( or #LEFT,#RIGHT) but this did not help. Maybe I did something wrong ? Maybe it is a bug ? I don't know. Kind regards, Christopher ___ bug-lilypond mailing list bug-lilypond

Re: Failure to run midi2ly successfully

Mats Bengtsson mats.bengtsson at ee.kth.se writes: Please always tell exactly what LilyPond version you use. /Mats Sorry for the oversight. This is Lilypond version 2.8.5-1, downloaded from lilypond.org's site under its Stable Branch listings. Additionally, it is being run under the

Failure to run midi2ly successfully

The following error is the result of attempting to convert a MIDI file to Lilypond format: C:\Lilypond\Projectsmidi2ly dulcimerreel.mid Traceback (most recent call last): File C:\Lilypond\usr\bin\midi2ly.py, line 1004, in ? main() File C:\Lilypond\usr\bin\midi2ly.py, line 1002, in main

This message must change your life history!

Formulated for: Increase sexual life ride Boost intimate operation Copious & solid erections Increase stamina & endurance Characteristic: Ameliorate mixture Effects in less than 15 minutes Best price on the Net My web representation ___

ottava bug?

Is this a bug? Sorry is this is a repeat. \version 2.2.0 #(ly:set-point-and-click 'line-column) #(set-default-paper-size letter) #(set-global-staff-size 18) vlnI = \notes \relative c' { \clef violin \key e \major \time 2/2 r16 g\ff a g c e g c e2 | \times 2/3 { fis8 g a } b4 r4 e8.

Re: ottava bug?

, 2004-08-15 at 19:12, Erik Sandberg wrote: Sorry, I don't understand. The output with lilypond 2.2.5 looks normal to me, please specify what the unexpected behaviour is. Erik On Sunday 15 August 2004 12.09, Christopher Ellis wrote: Is this a bug? Sorry is this is a repeat. \version

bug/tag at beginning?

Not sure if this is a bug. I quickly viewed the subject lines of the last two months. With the tag stuff commented out, it produces the desired result. There is an extra line, clef, and time signature as is. A solution is easy. Just put the tagged stuff after the first measure. Sorry if this