Re: midiPanPosition in midi context block

Hi Matt, I had a hard time to compile your code, because your email-client inserts not common spacers at line-begin, but something else. I didn't bother to identify... Please: Use plain text !!! Here your _compilable_ example: sopStaff = \new Staff = "sop" { \relative c' { e4 f g a } } altoSt

Re: m7.5- transposed to sus#4 b3 ??

Am Mo., 11. Nov. 2019 um 21:38 Uhr schrieb Sandro Santilli : > > I transcribed an A major song with this chords snippet: > > ees:m7.5- | aes:7 | aes:m7.5- | des:7 | > > When transposing it to Eb major it is rendered as: > > Bbbø | Ebb7 | Ebb7sus#4 b3 | Abb7 > > I don't understand why the third

Re: harmonyli.ly beta 0.91 released

Am So., 10. Nov. 2019 um 14:32 Uhr schrieb Karsten Reincke : > I expanded the traditional System by two elements Ok, I wasn't sure whether it's your extension or I missed some newer developments. (The latter may have been true, I don't follow this topic closely.) Thanks, Harm

Re: harmonyli.ly beta 0.91 released

Am So., 10. Nov. 2019 um 13:14 Uhr schrieb Karsten Reincke : > > Dear friends; > > I've just published the release no 0.91 ( > https://github.com/kreincke/harmonyli.ly > ) of the library for integrating > Functional Harmony Analyse Symbols into a music score as it is used by > musicologists. > >

Re: Notating Rhythms

Am Fr., 8. Nov. 2019 um 20:59 Uhr schrieb Karsten Reincke : > > > Dear Friends; > > due to a special requirement, I have to insert a staff into a score which only > contains one line instead of five (as it is offered by percussion-style in > DrumStaff drummode), but which then takes normal notes wi

Re: midiPanPosition in midi context block

Am Fr., 8. Nov. 2019 um 15:35 Uhr schrieb David Kastrup : > > Matt Wallis writes: > > > But it doesn't work if I try to set the midiPanPosition inside a midi > > context block like this: > > > > \version "2.19.83" > > > > \include "english.ly" > > sopStaff = \new Staff = "sop" { > > \relative c'

Re: How to use optional arguments / parameters in a define-markup-command

Am Di., 5. Nov. 2019 um 09:14 Uhr schrieb Karsten Reincke : > > On Mon, 2019-11-04 at 23:06 +0100, Thomas Morley wrote: > > Am Mo., 4. Nov. 2019 um 18:00 Uhr schrieb Karsten Reincke > > : > > [...] > > Let me quote another part of my reply: > > > > Am Fr.

Re: scheme-question: matrix-operation

Am Mo., 4. Nov. 2019 um 01:05 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Hi, > > > > lets say I've a list of sublists like '((1 2 3)(4 5 6)) > > I want to modify it, the result should be '((1 3 5)(2 4 6)) > > > > This i

Re: How to use optional arguments / parameters in a define-markup-command

portunity does not exist (Thomas Morley) Let me quote another part of my reply: Am Fr., 1. Nov. 2019 um 16:01 Uhr schrieb Thomas Morley : > For variable amount of args I'd go for list? (or the like) and let the > body of your code sort it out. And that's basically what you d

scheme-question: matrix-operation

Hi, lets say I've a list of sublists like '((1 2 3)(4 5 6)) I want to modify it, the result should be '((1 3 5)(2 4 6)) This is a matrix-operation (not sure whether matrix is the correct english term), on could write it graphically: 1 2 3 4 5 6 -> 1 3 5 2 4 6 What's the best scheme-way to get it

Re: \woodwind-diagram shift problem

Am So., 3. Nov. 2019 um 11:39 Uhr schrieb Jacques Menu : > > Hello folks, > > In the attached sample, the diagrams in the second measure are shifted right, > and the second one is much above the others. > > Any hint is welcome! > > JM Hi Jacques, I'd delete all occurrencies of \center-column, ma

Re: TabStaff.keepAliveInterfaces

Am Sa., 2. Nov. 2019 um 12:59 Uhr schrieb Thomas Morley : > > Am Sa., 2. Nov. 2019 um 09:41 Uhr schrieb Malte Meyn : > > > > Hi list, > > > > what am I (or what is LilyPond) doing wrong here? > > > > %%% > > > >

Re: TabStaff.keepAliveInterfaces

Am Sa., 2. Nov. 2019 um 09:41 Uhr schrieb Malte Meyn : > > Hi list, > > what am I (or what is LilyPond) doing wrong here? > > %%% > > \version "2.19.83" > > bla = { \repeat unfold 100 e'4 } > git = { >\set TabStaff.keepAliveInterfaces = #'() >R1*10 >\repe

Re: define-markup-command with variable number of arguments

Am Fr., 1. Nov. 2019 um 15:34 Uhr schrieb Karsten Reincke : > does anyone has / know about an example of a define-markup-command > implementation > using a variable number of arguments / parameters? Nope, optional arguments are not possible using define-markup-command. > Unfortunately, in my sy

Re: Hairpin.minimum-length gives wrong output

ptoye wrote > What I want is the first quaver sf and the hairpin to finish before the > next quaver, so that the 3rd quaver is at the same dynamic as the 2nd > one. > > Here's a better MWV > > \version "2.19.52" > \language "english" > { > << > \new Staff { > \time 2/4 > \clef

Re: Tight spacing in mensural notation (was: Re: Cadenza Senza Tempo Problem)

Am Mi., 30. Okt. 2019 um 19:44 Uhr schrieb Graham King : > Harm, I'm afraid I'm struggling with "#(ly:make-moment -3)" > > The NR[2] shows four arguments to ly:make-moment, describes two of them, and > then speaks a little obtusely of the _second_ argument to ly:make-moment > being possibly nega

Re: Tight spacing in mensural notation (was: Re: Cadenza Senza Tempo Problem)

Am Di., 29. Okt. 2019 um 16:28 Uhr schrieb Graham King : > > "...and most important you want tight space between all notes as > though it's not allowing the space for barlines and more." > > This unanswered part of Reggie's question in [1] lead me to re-scratch an old > itch. In manuscripts and o

Re: Cadenza Senza Tempo Problem

Am Mo., 28. Okt. 2019 um 11:22 Uhr schrieb Reggie : > > Hello list. I am struggling with this. Please don't laugh I just feel like > crying I cannot see what is right in front of me I must be. I am attempting > to learn more deeper in lilypond and try a cadenza sort of passage. I see > two problems

Re: Musicology with Lilypond (and now correct attachments ;-)

Am Mo., 28. Okt. 2019 um 00:22 Uhr schrieb Karsten Reincke : > BUT THERE IS A LICENSE QUESTION (very important in the area of free > software!) The example shown if you click on the graphik of > http://lsr.di.unimi.it/LSR/Item?id=967 does not contain any license > information. Does anyone know the

Re: Crossstaff position tolerance

Am Fr., 25. Okt. 2019 um 12:27 Uhr schrieb Andrew Bernard : > > What is the position tolerance distance for cross staff stems to work? Zero? > Or is there some wriggle room? > > I ask because I have a complex (as always) bit of free form music with > different overlapping tuplet ratios in differe

Re: Tweaking glissando timing stems

Am Fr., 25. Okt. 2019 um 22:41 Uhr schrieb Leo Correia de Verdier : > I realized that defining the glissando gradient taking the stencil as point > of departure, rather than the grob properties, makes it work for broken > glissandi too. It was a quite minimal change. > > (gliss-gradient (/ (+ (-

Re: Arpeggio misbehaviour?

Am Sa., 26. Okt. 2019 um 04:45 Uhr schrieb Federico Sarudiansky : > > Hello, > > I'm typesetting a work which includes this single measure (here as a MWE) in > a PianoStaff. > > \version "2.19.83" > > \score { > \new PianoStaff { >\set PianoStaff.connectArpeggios = ##t ><< > \new Sta

Re: Tweaking glissando timing stems

Am Sa., 19. Okt. 2019 um 12:36 Uhr schrieb Thomas Morley : > Meanwhile I've probably found a method to affect Beams from inside a > Glissando.after-line-breaking, but currently it's not mature to say > more. > Anyway, my goal will be to make Beams parallel to the glissando

Re: midi instrument for ChordNames

Am Mo., 21. Okt. 2019 um 11:12 Uhr schrieb Sandro Santilli : > > I can't get anything but a piano rendering of ChordNames staff, > can other instruments be used ? If so, how ? > > This is my sheet snippet: > > << > \new ChordNames { > \set midiInstrument = "flute" % does not work here >

Re: Double-underline markup

Am So., 20. Okt. 2019 um 12:58 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am Sa., 19. Okt. 2019 um 14:45 Uhr schrieb David Kastrup : > >> b) change a property (akin to offset but probably unique to \underline > >> to avoid unexpected interac

Re: Double-underline markup

Am Sa., 19. Okt. 2019 um 14:45 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am Sa., 19. Okt. 2019 um 13:35 Uhr schrieb David Kastrup : > >> > >> Thomas Morley writes: > > > >> > Iiuc, you recommend to fix \underline

Re: Double-underline markup

Am So., 20. Okt. 2019 um 05:38 Uhr schrieb Carl Sorensen : > > > > On 10/19/19, 3:13 AM, "Thomas Morley" wrote: > > Am Fr., 18. Okt. 2019 um 19:21 Uhr schrieb Carl Sorensen > : > > > > Why not add it to lilypond proper? I think that we

Re: Double-underline markup

Am Sa., 19. Okt. 2019 um 19:24 Uhr schrieb David Kastrup : > By the way, it's "an under...", not "a under...". That's not at all > relevant to the problem, merely a distraction for focusing on the > images. Ooops, sorry for that, Harm ___ lilypond-u

Re: Double-underline markup

Am Sa., 19. Okt. 2019 um 14:45 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am Sa., 19. Okt. 2019 um 13:35 Uhr schrieb David Kastrup : > >> > >> Thomas Morley writes: > > > >> > Iiuc, you recommend to fix \underline

Re: Double-underline markup

Am Sa., 19. Okt. 2019 um 13:35 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > Iiuc, you recommend to fix \underline to make it work with most simple > > input like: > > > > \markup { > > \override #'(offset . 12) \underline > > \over

Re: Double-underline markup

Am Sa., 19. Okt. 2019 um 12:42 Uhr schrieb David Kastrup : > > David Kastrup writes: > > > Thomas Morley writes: > > > >> Am Fr., 18. Okt. 2019 um 19:21 Uhr schrieb Carl Sorensen > >> : > >>> > >>> Why not add it to lilypond proper?

Re: Tweaking glissando timing stems

Am Sa., 19. Okt. 2019 um 00:01 Uhr schrieb Leo Correia de Verdier : > > Thanks a lot for your help! > > Quite to my surprise I found the following snippet does work. > > > > \version "2.19.82" > > #(define changebeam (lambda (grob) > (let* ((stem (ly:grob-object grob '

Re: Double-underline markup

Am Sa., 19. Okt. 2019 um 06:58 Uhr schrieb Andrew Bernard : > > That's funny - it's the argument I always use for my new complexity work, but > it usually gets shouted down quite vocally (refer for example to my > requirement for equal width bars!). Nah, it's not shouted down. ;) Though, there a

Re: Double-underline markup

Am Sa., 19. Okt. 2019 um 05:22 Uhr schrieb Andrew Bernard : > > I have not seen anything get added to lilypond proper for a long time. > I may be wrong, but it's immensely difficult to get changes to core it would > seem. Fair enough too. That's why openlilylib exists. Nothing against openlilyib

Re: Double-underline markup

Am Fr., 18. Okt. 2019 um 19:21 Uhr schrieb Carl Sorensen : > > Why not add it to lilypond proper? I think that we would want to be careful > about property names (perhaps with an underline-details property to minimize > namespace pollution), but I think it would make a great addition to Lilypond

Re: Double-underline markup

Am Di., 15. Okt. 2019 um 13:19 Uhr schrieb Pierre Perol-Schneider : > > Hi Urs a,d Aaron, > > Simply: > > \markup { > \underline > \override #'(offset . 6)\underline > "Lorem ipsum" > \override #'(offset . 5)\underline > \override #'(offset . 10)\underline > "dolor sit amet" > } > > Wor

Re: Tweaking glissando timing stems

Am Mo., 14. Okt. 2019 um 12:22 Uhr schrieb Leo Correia de Verdier : > When you write that "inner beams positions can’t be affected from > Glissando.after-line-breaking", do you mean it’s impossible, that they would > need to be recreated rather than repositioned or just that the actual code > c

Re: Tweaking glissando timing stems

Am Do., 10. Okt. 2019 um 14:51 Uhr schrieb Leo Correia de Verdier : > > Dear list! > > I'm soon going to start engraving a piece that contains very many glissandi > with timing marks (or actually, glissandi with broken bowing and > articulations during the way). The snippet in > http://lilypond.

Re: LSR-snippet 1071 "Percussion example" incomplete

Am Do., 3. Okt. 2019 um 11:43 Uhr schrieb Thomas Morley : > > To the author of LSR-snippet 1071 "Percussion example", > > this snippet > lsr.di.unimi.it/LSR/Item?u=1&id=1071 > is obviously not complete (probably a copy/paste-error), please add > the missing parts

LSR-snippet 1071 "Percussion example" incomplete

To the author of LSR-snippet 1071 "Percussion example", this snippet lsr.di.unimi.it/LSR/Item?u=1&id=1071 is obviously not complete (probably a copy/paste-error), please add the missing parts. Otherwise I'll delete it soon. Cheers, Harm ___ lilypond

Re: Input syntax question

Am So., 29. Sept. 2019 um 18:57 Uhr schrieb : > > What characters are allowed in variable names? > > -- > Matthew Skala > msk...@ansuz.sooke.bc.ca People before tribes. > https://ansuz.sooke.bc.ca/ From NR: "The name of a [LilyPond-]variable should have alphabetic characters only;

Re: Translating stencils

Am Di., 24. Sept. 2019 um 12:06 Uhr schrieb Michael Käppler : > > Hi Harm, > many thanks for your advice! > The \table command was completely new to me. > Here is my current state of work: > > #(define (mm->staff-spaces mm) > (let ((ss (ly:output-def-lookup $defaultpaper 'staff-space))) >

Re: Installing missing Guile modules in order to

Am Mo., 23. Sept. 2019 um 22:48 Uhr schrieb Werner LEMBERG : > > > >> no code for module (ice-9 readline) > >> > >> [...] > >> > >> This seems to mean I should install Guile modules that Lilypond > >> doesn't install by default, but I haven't been able to work out > >> from the doc where to install

Re: Translating stencils

Am Mo., 23. Sept. 2019 um 18:04 Uhr schrieb Michael Käppler : > > Hi all, > I'm trying to understand the way one can translate / stack stencils in > LilyPond. > Consider the following code: > > #(define-markup-command (draw-line-mod layout props startpos endpos) > (number-pair? number-pair?) >

Re: old school style of parenthesised ties or slurs possible ?.

Am Mo., 23. Sept. 2019 um 18:56 Uhr schrieb Eby Mani via lilypond-user : > > > examples, the ties float within the parenthesis, slightly above the notes. > Lillypond ties almost touch both notes. > > eby > On Monday, 23 September, 2019, 9:03:58 AM IST, Andrew Bernard > wrote: > > > Provide an ex

Re: Installing missing Guile modules in order to

Am Mo., 23. Sept. 2019 um 18:45 Uhr schrieb Leah Velleman : > > Attempting to follow the instructions here for setting a breakpoint > > > http://lilypond.org/doc/v2.19/Documentation/contributor/debugging-scheme-code > > > gets me several errors: > > /Applications/LilyPond.app/Contents/Resources/sha

Re: Nested tuplet across tuplets

Am So., 22. Sept. 2019 um 01:22 Uhr schrieb Andrew Bernard : > > I have come to an impasse in a score I am setting. Is it even remotely > possible to have a tuplet nested _across_ two tuplets with lilypond? See > attached image. > > [Don't blame me for the musical aspect of this - it's not my music

Re: Links in PDF-Files

Am Fr., 20. Sept. 2019 um 18:53 Uhr schrieb Richard Shann : > > On Fri, 2019-09-20 at 12:26 -0400, msk...@ansuz.sooke.bc.ca wrote: > > On Fri, 20 Sep 2019, sir.teddy.the.fi...@gmail.com wrote: > > > Why does lilypond add these links and is there a way to prevent it > > > from > > > doing so? > > >

Re: \bookpart question

Am Mi., 18. Sept. 2019 um 08:22 Uhr schrieb Jacques Menu : > > Hello folks, > > I naturally tend to specify a number of pages in a bookpart this way: > > \bookpart { > \layout { > page-count = 1 > } [...] > } > > What is the logic behind that being rejected, and the need to use

Re: improving Janek's \dynamic function (for combo dynamics)

Hi Kieren, sorry for the late reply. Am So., 8. Sept. 2019 um 21:29 Uhr schrieb Kieren MacMillan : > > Hi Harm, > > Three questions on this [seemingly-ancient!] thread about your (wonderful) > "dynamics on the fly" function: You likely mean this thread: http://lilypond.1069038.n5.nabble.com/imp

Re: Detecting first and last pages of a score

Am Sa., 7. Sept. 2019 um 01:42 Uhr schrieb Thomas Morley : > > Am Fr., 6. Sept. 2019 um 23:55 Uhr schrieb David Kastrup : > > > > On 06/09/19 17:00, David Kastrup wrote: > > (short of some > > multi-pass algorithm writing out table-of-content like information on &

Re: Detecting first and last pages of a score

Am Fr., 6. Sept. 2019 um 23:55 Uhr schrieb David Kastrup : > > On 06/09/19 17:00, David Kastrup wrote: > (short of some > multi-pass algorithm writing out table-of-content like information on > each run) David, we have a prob-property 'last-in-score, iiuc it's set far too late to be of any use h

Re: Guitar string bends

Am Di., 3. Sept. 2019 um 16:08 Uhr schrieb Federico Bruni : > > > > Il giorno mar 3 set 2019 alle 15:36, Randy Josleyn > ha scritto: > > Hi all, > > > > (Sorry for the duplicate, I didn't know how I replied created issues > > for others.) > > > > What's the state of Lilypond's support for notating

Re: Note spacing with a polyphonic grace notes

Am Sa., 17. Aug. 2019 um 11:44 Uhr schrieb Pierre Perol-Schneider : > > Hi Andrew, > The wanted spacing is shown in the 2nd snippet. > The workaround reaches almost it. > Cheers, > Pierre > > Le sam. 17 août 2019 à 11:20, Andrew Bernard a > écrit : >> >> What is the wanted spacing? >> >> Andrew >

Re: NullVoice lyrics overlap

Am Mi., 7. Aug. 2019 um 22:02 Uhr schrieb Kenny Stephens via lilypond-user : > > The lyrics DO NOT format correctly if NullVoice is used for the Tenor. > The lyrics format correctly if Voice is used for the Tenor. > The lyrics format correctly using NullVoice if the Soprano and Tenor if "\new > St

Re: Overriding a global declaration

compiled together with… > A so called reduced tune also with 13 lines which now fits onto one page > after following suggestions from Thomas Morley. > The final tune is normal and should perform as number 1 and spill over onto > the next page – it doesn’t. > > Simply stated, I w

Re: Overriding a global declaration

Am Mo., 5. Aug. 2019 um 14:21 Uhr schrieb Thomas Morley : > > Am Mo., 5. Aug. 2019 um 12:46 Uhr schrieb John McWilliam > : > > > > > > > <http://lsr.di.unimi.it/LSR/Item?id=862 or the builtin `magnifyStaff´. > > > > > > &

Re: Specifying piece titles in Score context

Am Mo., 5. Aug. 2019 um 00:28 Uhr schrieb Michael Seifert : > > I’m trying to compile some parts and a full score from a set of > included files. I’m running into a problem that I’m sure must be solvable; > I just can’t figure out where it is in the documentation. > > Specifica

Re: Mysterious behavior in music function

Am So., 4. Aug. 2019 um 22:49 Uhr schrieb Marc Evanstein : > > Hi all, > > I'm trying to define a music function that adds a gliss after a note down to > a second parenthesized grace note. I've tried the following, but the gliss > doesn't show up: > > \version "2.19.83" > \language "english" > >

Re: Overriding a global declaration

Am So., 4. Aug. 2019 um 20:09 Uhr schrieb John McWilliam : > > I’m compiling a book of bagpipe tunes and have used a global declaration > which suits my Music: > > #(set-global-staff-size 16) > > I now fine I have one tune which still does not fit onto the page and one > line of music spills over

Re: allowVoltaHook

Am Sa., 3. Aug. 2019 um 10:39 Uhr schrieb John McWilliam : > > Windows 10, Lilypond 2.18.2, Friscobaldi 3.0.1 > > > > I have some old Music which I am updating to Lilypond 2.18.2 and have come > across this command which doesn’t seem to have any affect on the Music: > > > > #(allow-volta-hook "|")

Re: Accidentals from note grob

Am Do., 1. Aug. 2019 um 15:23 Uhr schrieb Nils Nommensen : > > Sorry to bother you with this, but I'm really new to Lilypond and Scheme. I > need a String representation of the name. If I use display on the return > value, I get something like: "accidentals.natural"#". > How can I extract the "na

Re: Accidentals from note grob

Am Do., 1. Aug. 2019 um 13:13 Uhr schrieb Nils Nommensen : > > While I'm at it: How would I get the correct glyph name from the > accidental-grob object as a string? #(define get-accidental (lambda (note) (let* ((acc (ly:grob-object note 'accidental-grob))) (write (ly:grob-property a

Re: Accidentals from note grob

Am Do., 1. Aug. 2019 um 12:42 Uhr schrieb Nils Nommensen : > > Thank you very much! That does the trick Glad I could help. Cheers, Harm P.S. Please alway reply to all, even if merely confirming the proposed sollution works. cc-ing list ___ lilypond-

Re: Accidentals from note grob

Am Do., 1. Aug. 2019 um 12:03 Uhr schrieb Nils Nommensen : > > Hello everyone, > > Is there any way to get the accidentals that belong to a specific notehead > grob? > When calling ly:grob-basic-properties on the notehead grob, you get a list > with an attribute "parenthesis-friens", which has th

Re: Strange results from simultaneous RehearsalMarks

Am Sa., 27. Juli 2019 um 18:29 Uhr schrieb Patrick Karl : > I'm running LIlyPond 2.19.81 on a Mac desktop running OSX 10.11.6. > > I'm confused about the warnings generated by the following snippet: > > \version "2.19.81" \score { \new GrandStaff << \new Staff { > c'1\bar

Re: Alternating text and music

Am Fr., 26. Juli 2019 um 14:16 Uhr schrieb Urs Liska : > Hm, at least according to Frescobaldi's auto-completion LaissezVibrerTie > does *not* have a minimum-length property, which is confirmed by that > result ... > Also, \shape does have no effect on the \LaissezVibrer, sorry. > LaissezVibrerT

Re: accessing broken part of frameextender

Am Di., 23. Juli 2019 um 15:57 Uhr schrieb Neil Thornock : > > Hello all, I'm trying to modify the broken part of FrameExtender in the > frameEngraver-bars-and-boxes.ily code. \alterBroken fails with an error > stating that it is not a spanner. > > So, how to access and modify the broken part, af

Re: How to increase the distance between staves?

Am Mi., 24. Juli 2019 um 17:52 Uhr schrieb Richard Shann : > > On Wed, 2019-07-24 at 12:54 +0100, Peter Toye wrote: > > I want to increase the distance between the staves > > I've just been asked a similar question of denemo-d...@gnu.org and > looking into it I came up with the following example wh

Re: How to increase the distance between staves?

Am Mi., 24. Juli 2019 um 14:26 Uhr schrieb Jean ABOU SAMRA : > > Hi Peter, > Any overrides you can do in StaffGrouper are related to the space between > staves > of the _same_ system when they are grouped in StaffGroup-s or such. Nope. StaffGrouper.staffgroup-staff-spacing will affect spacing bet

Re: I don't understand this output

Am Sa., 20. Juli 2019 um 08:29 Uhr schrieb james via lilypond-user : > > Hello, I don't understand why this results in the output it does. > I wanted to have the second voice instantiated in the beginning because it is > used later and I would like to have the lyrics align vertically. > Alternativ

Re: Arrowed quartertones notes snippet compilation problem

Am Do., 18. Juli 2019 um 21:15 Uhr schrieb Jacques Menu : > > Hello folks, > > The snippet at http://lsr.di.unimi.it/LSR/Snippet?id=784 leads to the error > messages below with LP 2.19.83. > > Didn’t find eiseh nor feh in Lily's source code. > I don’t know which version it was written for. Does an

Re: LilyPond 2.20 or 2.21 on Ubuntu 18.04

Am Do., 18. Juli 2019 um 15:36 Uhr schrieb Aaron Hill : > > On 2019-07-18 6:13 am, Thomas Morley wrote: > > Am Do., 18. Juli 2019 um 14:37 Uhr schrieb Ralph Palmer > > : > >> > >> Greetings - > >> > >> I'm running LilyPond 2.19.81 with Fre

Re: LilyPond 2.20 or 2.21 on Ubuntu 18.04

Am Do., 18. Juli 2019 um 14:37 Uhr schrieb Ralph Palmer : > > Greetings - > > I'm running LilyPond 2.19.81 with Frescobaldi 3.0.0 under Ubuntu 18.04.2. > > Has any progress been made in making a process available to install LilyPond > 2.20 or 2.21 on Ubuntu 18.04? Back in March of this year (2019)

Re: slurs and ties to end of bar

Am Do., 18. Juli 2019 um 07:38 Uhr schrieb Werner LEMBERG : > > > Folks, > > > I have to typeset a bunch of snippets that contain ties and slurs > either from a (not typeset) bar at the left or to a bar to the right > (see attached example). What is the recommended way to do that > gracefully? > >

Re: Incorrect letter spacing in header

Am Do., 18. Juli 2019 um 13:04 Uhr schrieb David Kastrup : > > Steven Smith writes: > > > I am working on an arrangement for band, and would like the header > > information to be the same size on the conductor's score and the > > instrumental parts. I put the scores in different \book block so I >

Re: inter-letter spacing?

Am Mo., 15. Juli 2019 um 21:37 Uhr schrieb David Kastrup : > > Werner LEMBERG writes: > > >> any idea how to realize inter-letter spacing? Has someone already > >> written a macro like > >> > >> \markup { \letter-spacing #0.1 "foobar" } > >> > >> which should be equivalent to > >> > >> \marku

Re: Jazz chords layout question

Hi Jacques, Am So., 14. Juli 2019 um 01:30 Uhr schrieb Jacques Menu : > > Hello Robin, > > Thanks, the result is already better, with the seconda volta at the right > place after adjusting the parameter of \pseudoIndent. > > Didn’t find a way to hide the empty part of the staff to the left of it

Re: Two Hands "Snake"

Am Mo., 8. Juli 2019 um 23:35 Uhr schrieb tdy lists : > With the template of the vibrato: > > %% > https://raw.githubusercontent.com/mwitmer/LyUtil/master/ly/expressive_markings/vibrato.ly > %% Original author: Mark Witmer > %% Rewritten version by Harm > > I tweak the thiknes of the curve and I

Re: Modification of Flam, Drag, Ruff snippet

Am Sa., 29. Juni 2019 um 11:06 Uhr schrieb Craig Dabelstein : > > Hi all, > > Is there a way to modify the Flams, Drags and Ruff snippet from the LSR > (http://lsr.di.unimi.it/LSR/Item?id=566) so that there can be open versions > of the drag and ruff (that's what exists now), and also a closed ve

Re: Inserting alternative endings from a music function

Am Mi., 26. Juni 2019 um 17:41 Uhr schrieb Leah Velleman : > > I'm writing a music function to insert a specific pattern of alternative > endings with partial measures. Lilypond gives an error suggesting the > \alternative block is in the wrong place, even though writing it in the same > place b

Re: Strange space between beam and slur

Am So., 23. Juni 2019 um 11:59 Uhr schrieb Thomas Morley : [...] Just reported in the german forum https://lilypondforum.de/index.php/topic,501.0.html \version "2.19.82" % problem occurs at staff-size 19, but does not occur at staff-size 18 or 20 #(set-global-staff-size 19) \new TabS

Re: Strange space between beam and slur

Am So., 23. Juni 2019 um 10:54 Uhr schrieb Andrew Bernard : > > Hi Lukas, > > May be a bug, but I always use explicit voices, not '//' constructs. I > find it is just better but. > > You play with the rests, but this works: > > > \new Staff > << >{ > \voiceOne > R1 > a''8( b'' b'

Re: [192]ERROR: In procedure ly:trampoline: | Adding any more code throws error!

Am Do., 20. Juni 2019 um 19:50 Uhr schrieb Karlin High : > > On 6/20/2019 12:26 PM, Samuel Burt wrote: > > Does that help anyone in figuring out what my problem is? > > A few weeks ago, there was a similar error report. > > >

Re: Volta font

Am Do., 20. Juni 2019 um 18:21 Uhr schrieb Leah Velleman : > > Is it possible to change the font used for volta numbers? > > In the list archives I've seen options for customizing the volta text, some > of which could be used with \text or \markup to change the font in addition. > But I don't wan

Re: glissando over break

Am Mo., 10. Juni 2019 um 20:54 Uhr schrieb Aaron Hill : > > On 2019-06-10 11:04 am, Paul Scott wrote: > > Can LilyPond make a glissando across a line break? > > > > [ . . . ] > > > > Is there an equivalent of > > \override Beam.breakable = ##t for glissandos ? > > >\override Glissando.brea

Re: custom dynamics with midi output

Am Sa., 8. Juni 2019 um 18:03 Uhr schrieb Karim Haddad : > > Dear All, > > In the following documentation's snippet : > > doctitle = "Creating custom dynamics in MIDI output" > } % begin verbatim > > #(define (myDynamics dynamic) > (if (equal? dynamic "rfz") > 0.9 > (default-dynam

Re: Insipit variation

Am So., 2. Juni 2019 um 20:51 Uhr schrieb Thomas Morley : > > Am So., 2. Juni 2019 um 18:30 Uhr schrieb Lutenist : > > I did try to use \incipit but there are no barlines! > > Well, \incipit uses MensuralStaff. But usually there are no BarLines > MensuralStaff, they

Re: Insipit variation

Am So., 2. Juni 2019 um 18:30 Uhr schrieb Lutenist : > > Dear Simon, > > thank you for your reply! I tried a bit longer and came quite close to what > I wanted, but lack the know-how. > I have attached my test file. > > What I try to replicate is the incipit from > http://lilypond.org/doc/v2.19/Doc

Re: How to calculate visible vertical beam-height

Am So., 2. Juni 2019 um 17:26 Uhr schrieb : > > ---- > Thomas Morley: > ... > > I'm interested in a formula how the length of the red line changes > > with different blot-diameters. > ... > > \version "2.19.82" > > > > #(de

How to calculate visible vertical beam-height

Hi, here a problem which should be solveable, but the math escapes me, although all values are known, afaict. Please look at the attached image, the black polygons are created by the beam-markup-command (slightly changed to make blot-diameter settable with an override). The red lines represent th

Re: bug in lyric syllable magnetic snap

Am Di., 28. Mai 2019 um 18:52 Uhr schrieb Alexander Kobel : > > Hi, > > On 28.05.19 18:12, Thomas Morley wrote: > > Am Di., 28. Mai 2019 um 15:48 Uhr schrieb Thomas Morley > > : > > > >> I then switched to brute-force, i.e. always throw away all > >&g

Re: bug in lyric syllable magnetic snap

Am Di., 28. Mai 2019 um 15:48 Uhr schrieb Thomas Morley : > I then switched to brute-force, i.e. always throw away all > line-starting LyricHyphens > > Seems to work, see attached revised file. G, it does not. Please try to replace `remove-line-starting-hyphens´ with belo

Re: bug in lyric syllable magnetic snap

Am Mo., 27. Mai 2019 um 22:34 Uhr schrieb Thomas Morley : > > Am Mo., 27. Mai 2019 um 10:40 Uhr schrieb Alexander Kobel > : > > > unless I additionally engage > >http://lsr.di.unimi.it/LSR/Item?id=1090 > > to replace Lily's built-in hyphens by the "p

Re: Stem in double division

Am Di., 28. Mai 2019 um 14:38 Uhr schrieb Niels : > > Dear users, > > For a pianoscore I want to use three voices for the lower staff. > First I divide into two parts, then the upper voice again in two. > However, I am getting a warning" > > ly:10:26: warning: adding note head to incompatible stem

Re: bug in lyric syllable magnetic snap

Am Mo., 27. Mai 2019 um 10:40 Uhr schrieb Alexander Kobel : > unless I additionally engage >http://lsr.di.unimi.it/LSR/Item?id=1090 > to replace Lily's built-in hyphens by the "proper" Lyric's font hyphens; > then it breaks again. > > I did not have a very close look yet; I thought replacing l

Re: bug in lyric syllable magnetic snap

Am Fr., 17. Mai 2019 um 16:35 Uhr schrieb Kieren MacMillan : > I *so* wish I could use it… but I keep running into bugs that I never have > time to MWE-ize, and so I end up bailing on it. > > The one you point out here is one of the issues that I’ve been hit by. > Another is somehow related to us

Re: bug in lyric syllable magnetic snap

Am Mi., 22. Mai 2019 um 08:17 Uhr schrieb Alexander Kobel : > > Hi Harm, hi all, > > On 22.05.19 01:20, Thomas Morley wrote: > > Am Do., 16. Mai 2019 um 13:25 Uhr schrieb Alexander Kobel > > : > >> > >> Hi David, hi Mike, hi all, > >> >

Re: bug in lyric syllable magnetic snap

Am Do., 16. Mai 2019 um 13:25 Uhr schrieb Alexander Kobel : > > Hi David, hi Mike, hi all, > > I sometimes (still use Lilypond, and when I do, I typically use) your > wonderful snippet for snapping "close" syllables into a single token. > > (For those who don't know this contribution: it's meant to

Re: Unconventional score and unwanted stray staff lines

Am Di., 21. Mai 2019 um 22:46 Uhr schrieb Leo Correia de Verdier : > > A quite minimal could look like: > > \version "2.19.82" > > \score { > << \new Staff {e'2.} > \new Staff {g'4. f'4} > \new Staff {a'1} >> > > \layout { > \context { > \Voice > \remove "Note_heads_en

<    2   3   4   5   6   7   8   9   10   11   >