How to hide footnote annotation line

Hello everyone, In a score I'm preparing I'm using footnotes for some explanations. In those cases it is clear from context which notes they refer to, rendering the lines to the note heads they are attached to both unnecessary and – to my eye – visually unpleasing. The documentation led me to try

Re: How to hide footnote annotation line

Hi David, \override Score.FootnoteItem #'annotation-line = ##f That's it. I had also tried FootnoteItem, but was missing the Score qualifier. Thanks a lot, Martin -- homme, ni présence ___ lilypond-user mailing list lilypond-user@gnu.org

Re: beam-problem

Hi, You can always use explicit beaming: \version 2.16.1 \new Staff \relative c' { \time 2/4 %1 a32[ a a a] a a a a a8 a16. a32 | %2 a8 a16. a32 a32[ a a a] a a a a | } Regards, Martin (Sent to the list this time) On 26 November 2012 12:53, Thomas Morley

Re: AutoBeam Behaving Properly?

On 6 April 2016 at 09:10, Thomas Scharkowski wrote: > From the Notation Reference: > "In engraving from the Romantic and Classical periods, beams often begin > midway through the measure in 3/4 time, but modern practice is to avoid the > false impression of 6/8 time

Re: AutoBeam Behaving Properly?

On 6 April 2016 at 13:23, Kieren MacMillan wrote: > Hi Martin, > > > when I explored the effect of that setting, I wasn't sure the outcome is > really that desirable > > Wait… is your example **actually** what happens with > Timing.beamHalfMeasure = ##f? > At least

Re: AutoBeam Behaving Properly?

Hi Karen, > When working in 3/4, Lilypond is autobeaming 8th notes in groups of 3 8th > notes per pulse (as if it were 6/8) rather than in groups of 2 8th notes > per pulse. > That's not entirely accurate, in 3/4 time the autobeaming by default creates a single beam for the whole measure. In

Re: AutoBeam Behaving Properly?

On 6 April 2016 at 01:51, Simon Albrecht wrote: > That would be unnecessary. Better use the beamHalfMeasure context > property, which is also explained on that docs page. > Interesting. In my defence I can only say that this wasn't available back when I started out with

Re: AutoBeam Behaving Properly?

On 6 April 2016 at 04:16, Kieren MacMillan <kieren_macmil...@sympatico.ca> wrote: > Hi Martin, > > On Apr 5, 2016, at 9:58 PM, Martin Neubauer <mrtn...@gmail.com> wrote: > > I was wondering how often the odd half measure beam really leads to > ambiguity betwee

lilypond fonts

Hi all, Because I did no (serious) music typesetting for quite some time, I got a bit out of touch with what was going on in the lilypond world. Because I have some upcoming projects ahead of me, I took the opportunity to try and catch up a little. So I became now aware of the mechanism for

Re: Start of the first row of a staff

Hello, Try putting %%% \paper { indent = 0\mm } %%% in your lilypond source. Regards, Martin On 21/09/2016 08:19, Marco Bagolin wrote: > Hello all, > please, I need a help because I don't find a solution in the snippet > repository. > I need that the first line of the staff is aligned

Re: \omit TupletNumber reversal

\once \undo \omit TupletNumber ? On 19/10/2016 15:39, Bernhard Kleine wrote: > For a long sequence of trioles I have shown the tupletNumber once and > omitted thereafter. Now a next triole sequence starts and would show > again the tupletNumber only once. But it is no longer there. How to > bring

Re: separating notes and fingerings

I did something like this recently: \relative c''{ <>\flageolet a4 <>^\markup { \finger "↓2" } c etc... } (with the markups getting tags for the different renderings.) What I wanted was to create differently marked parts for a single instrument though, so this might get a bit unwieldy

Re: convert-ly usage question

In addition to that, try running: % /home/simon/lilypond/2.19.47/bin/convert-ly -e *.ly If that's working, you might want to read up on aliases in the bash man page, and then use a shell function instead. On 24/10/2016 23:31, Karol Majewski wrote: > Hi Simon, > > does convert-ly work for you

Re: #4975 [Windows] Grace notes cause staff to protrude into the margin

I just tried it with 2.19.50 (on FreeBSD, though), and noticed no problem. (Neither error message, nor unexpected output.) So maybe you should try a newer version as well. Regards, Martin On 19/11/2016 02:51, Ralph Palmer wrote: > Greetings - > > I'm running LY 2.19.40 under Windows 7 SP1. > >

Re: Tricky tweak

What about something like: nonsf = #(make-dynamic-script (markup #:normal-text #:italic "(non " #:dynamic "sf" #:normal-text #:italic ")")) On 03/11/2016 23:37, David Sumbler wrote: > Well, it's proving tricky to me, anyway. > > I

Re: compound time signature with non duple denominator

On 04/11/2016 01:13, mclaren wrote: > This seems like an entirely valid question. 1/3 would be a single triplet > note, right? That is, if we're dealing with (4 + 1/3)/4, then what we want > is 4 quarter notes + 1 triplet quarter note, correct? Wouldn't that be rather (4 + 2/3)/4? -- Not the

Re: Understanding how \tag works in \relative pitched music

Maybe someone more well-versed with the inner workings of lilypond might correct me here, but as I understand it, the pitches depend on the sequence of notes in the input, regardless of any tags that might be attached to some of them. Conversely, when \keepWithTag (or any of the related commands)

Re: Vertical alignment of custom dynamics

On 06/08/2017 00:19, Gregor Smith wrote: > \version "2.16.0" > > \include "common.ly" > > upper = \relative c'' { > \clef treble > \key c \major > \time 2/4 > c2 > \repeat volta 2 { > d | e > } > } > > > lower = \relative c' { > \clef bass > \key c \major > \time 2/4 >

Re: Large set of parts

For me it depends primarily on the length and complexity of the score. For (larger) orchestral works I usually prefer having separate output files for each part. That way it's easy to just print out a single part and to distribute the parts electronically to the players. (\bookOutputName and

Re: spacer rest *

On 27/04/2018 10:53, Gianmaria Lari wrote: > And why spacer rests and rests don't "propagate" like note? I'm not sure what you mean by that, but »regular« notes behave just the same way: << {f'4 g' a' b'} \\ {d'4\< d'4*3\! } >> -- I am my own reality check. signature.asc

Re: Cross staff stems for beamed notes

On 26/04/2018 07:28, Helge Kruse wrote: > I need to add cross staff stems and used the approach found in > http://lilypond.org/doc/v2.19/Documentation/snippets/staff-notation.html#staff-notation-cross-staff-stems > > Unfortunately this doesn't give the expected result for eighth notes. > - If

Re: More than one tempo mark in a score

On 12/02/2018 16:42, Peter Toye wrote: > Monday, February 12, 2018, 3:22:27 PM, you wrote: > > *> Hi Peter, > >>> The nuisance is that you have to count all the silent bars where there >>> aren't any tempo changes, which is far less convenient than simply adding a >>> \tempo "Allegro" at the

Re: usage of OLL notation-fonts

Possibly there might even be a pull request for that already... On 15/02/2018 13:03, Urs Liska wrote: > Hi Johannes, > > please add this to the issue tracker of the notation-fonts package on > Github. > > I know what it is and will be able to fix it later, maybe this evening. > > Best > Urs >

Re: usage of OLL notation-fonts

You could try making the che changes in my pull request to your local copy and see if it fixes your problem. I think I got exactly that error message, but hey, that's more than a week ago, so what do I know... Good luck, Martin On 15/02/2018 16:00, Johannes Roeßler wrote: > added this issue...

Re: Aleatoric Elements with barlines

On 07/01/2019 17:29, Reggie wrote: > Aaron you are a great teacher thank you. Just a couple few more questions > please. First how did you know that it had to equal 2 full measures? I did > not see how you arrived. Second please tell me is there any negative effect > of moving the barline from

Re: Aleatoric Elements with barlines

On 09/01/2019 14:06, Ben wrote: > On 1/8/2019 10:43 PM, Martin Neubauer wrote: >> On 07/01/2019 17:29, Reggie wrote: >>> Aaron you are a great teacher thank you. Just a couple few more >>> questions >>> please. First how did you know that it had to equal 2 full

Re: set-global-staff-size undoes define fonts

On 27/01/2019 04:52, David F. wrote: > I can specify the font for my score to use with #(define fonts … ), but > calling #(set-global-staff-size) undoes the font definition. > > In the snippet below, Times New Roman will be used as the font for the whole > document. But if line 6 is

Re: Convert-ly adds line breaks

Hi, I suspect this is a Unix vs. Windows line ending issue. Maybe you can either run some utility like dos2unix (or whatever is available for windows these days) prior to running convert-ly, or confirm which line terminators are used before and after running convert-ly via some hexdump utility.

Re: Lilypond requires Python2

On 26/04/2020 16:30, Jonas Hahnfeld wrote: > Yes, 2.20.0 "requires" Python2 for building and scripts like lilypond- > book (not for running lilypond itself though). Will there be python3 based release of the 2.20 branch in the foreseeable future then (i.e this year?) As the current maintainer of

Re: Lilypond requires Python2

On 02/05/2020 09:53, Jonas Hahnfeld wrote: > The scripts and build system in 2.20 just don't work with Python 2. I > was against applying the port in the past, and I stand by that opinion. > I simply don't think it's feasible to apply the ~50 patches that were > developed against master long

Re: grace notes spacing

On 11/10/2020 21:26, Kieren MacMillan wrote: Note that I had to unfold the \repeat in the lower staff, in order to easily apply the tweak to the correct moment. This is one of the [many!] reasons I use the edition-engraver: you can inject the tweak at an exact moment, regardless of how the

Re: Acciaccatura giving errors

On 16/06/2020 17:30, Peter Toye wrote: > Thanks both. I've found the same now. I'd assumed that 2.21.0 would be later > than 2.20, but it seems not to be the case. > > Now sorted. Technically it is, but that might be less relevant than one would expect, as the split between the 2.20 release

Re: PDF not shown in Frescobaldi

Hello, Are you using \bookOutputName / \bookOutputSuffix for controlling the names of the pdf files? In my experience this can throw frescobaldi off if the resulting file name doesn't end with some digit. (As far as I remember there already exists an issue, but I'm not aware of any more detailed

Re: Odd \time bar check behaviour

On 10/06/2020 13:41, Michael Käppler wrote: > Am 10.06.2020 um 13:27 schrieb ebenezer: >> >> Hi all, >> >> The 1st code snippett generates warnings, but the 2nd does not. >> >> I'd like to keep the bar symbols in place as it helps me to keep track >> in the music. >> >> This is my first piece so

Re: How to align text in a whole-bar rest?

For cases like this the edition engraver might be of use to keep the entered music cleaner. On 13/06/2020 13:48, Peter Toye wrote: > Xavier, > > D'oh!!! Silly me. My brain isn't working today. Thanks. > > Best regards, > > Peter > mailto:lilyp...@ptoye.com > www.ptoye.com > >

Re: openLilyLib and text fonts

There are two different issues here: Firstly, the oll package defaults to "serif"/"sans-serif"/"monospace" which are the lilypond defaults onlky for the svg backend. Stealing from scm/fonts.scm (in the lilypond distribution) suggest the following changes that indeed seem to use the proper fonts:

Re: Hairpin which ends at the beginning of a measure

Try: \override Hairpin.to-barline = ##f (http://lilypond.org/doc/v2.21/Documentation/notation/expressive-marks-attached-to-notes) On 07/06/2020 16:00, Paolo Prete wrote: > Hello, > > As you can see in the following example, a hairpin is not connected to its > final dynamic if this dynamic is

Re: edition-engraver mod on first note

Hi Damian, During the summer I spent some time diving into the edition engraver myself and also noticed that some classes of mods didn't work on the first downbeat while others did. (I don't remember exactly which ones were problematic, but I can look it up later.) My workaround was to insert

Re: Markup in scheme

Maybe this is a starting point: \version "2.20.0" \new Staff{ <>-\markup{"First markup"} <>-#(markup #:line (#:simple "Second markup")) } On 31/10/2020 16:29, John Schlomann wrote: In the following snippet, the first markup works fine. The second gives no errors, but outputs

Re: error :GUILE signaled an error for the expression

On 13/07/2021 20:34, David Olson wrote: (poetry unworthy of this talented group, to be sure) (but then, the text of ANY song operates at a level at least 30 IQ points below the median of the singers) (why is that?) There exists some classic research in this field:

Re: Guile V1 vs. V2?

On Tue, 21 Dec 2021, Valentin Petzel wrote: Hello, Hello Mike, Guile 1 to Guile 2 did change some syntax and some mechanics, which means that guile code must be reworked for guile 2 and using guile 2 makes the program much slower. There is ongoing long time effort to port Lilypond to guile 2

Re: [large/complex projects] where should transpositions go?

Hi Kieren, I'm somewhat late to the party, and hadn't looked to thoroughly at your example code, either, but I'd like to nevertheless share my take on one specific point: 3. Compare the voicing of m3 in the SATB and SA voicings: mm1-2 are different, but m3 is the same. How can I do this kind