Re: move chords closer to notes

Le mardi 21 février 2023 à 13:03 +0100, Jean Abou Samra a écrit : > Le mardi 21 février 2023 à 12:41 +0100, mi...@orbelanet.com a écrit : > > > Thanks a lot for your response! > > It looks good in the image you sent, but for some reason it doesn't work > > for me.The nex

Re: move chords closer to notes

Le mardi 21 février 2023 à 03:55 +0100, mi...@orbelanet.com a écrit : > Hi everyone, > when I write the chords together with one or several melodies, the > chords form a horizontal line, in such a way that if the range of the > melody is very wide, some chords end up being very far from the >

Re: Lilypond zip file doesn't include the lilypond app?

Hello Benjamin, Welcome to this list. So you know, your message was manually approved because you are not a list subscriber. Please subscribe on [https://lists.gnu.org/mailman/listinfo/lilypond-user](https://lists.gnu.org/mailman/listinfo/lilypond-user) in order to fix this (you can choose not

Re: I did not previously realize that Lilypond would automatically update pre-existing scores

Le samedi 18 février 2023 à 22:19 +0100, Jean Abou Samra a écrit : > Le samedi 18 février 2023 à 22:09 +0100, Valentin Petzel a écrit : > > > I do think that even in this case Lilypond should > > issue a warning. > > https://www.mail-archive.com/lilypond-devel@gnu.o

Re: Determining requested output files

(Adding back the list) Le dimanche 19 février 2023 à 12:46 -0500, R. Padraic Springuel a écrit : > It’s part of my system for having make automatically figure out dependencies > when running LilyPond:  >

Re: Workaround for issue on tuplet of skips

Le dimanche 19 février 2023 à 02:09 +0100, Paolo Prete a écrit : > Hello LilyPonders, > > Currently, I checked that Spontini-Editor has an incompatibility with LP > 2.25.x (it works well with 2.24.x branch) due to this bug: > >

Re: organizing pieces with variables - lyrics not aligned

Le dimanche 19 février 2023 à 08:57 +0800, Darren Ng a écrit : > In the following sheet, > "Dave" and "Ed" are not on the same line. > > How to properly group melodies and their matching lyrics into variables, > while keeping lyrics on the same line? > >     \version "2.24.1" >    

Re: unable to use convert.ly

Hello, For your information, your posts to the list had to be manually approved because you are not a subscriber. Please subscribe from [https://lists.gnu.org/mailman/listinfo/lilypond-user](https://lists.gnu.org/mailman/listinfo/lilypond-user) to fix this. Thank you. Le vendredi 17 février

Re: Wondering if there's a way to not just hide N.C symbols, but have them not erase "current" chord.

Le vendredi 17 février 2023 à 19:03 -0600, Matthew Probst a écrit : > This is indeed the first time I'm really understanding adding properties to > notes with music functions, and it makes much more sense to me now that I'm > deeper in this than it did in the past. Good to hear. For what it's

Re: Determining requested output files

Le samedi 18 février 2023 à 11:55 -0500, Fr. Samuel Springuel a écrit : > I have the following scheme function which I used on versions 2.22 and > earlier which determined the requested output files for a lilypond run: > > #(define target-extensions (cond ((equal? (ly:get-option 'backend) 'svg)

Re: I did not previously realize that Lilypond would automatically update pre-existing scores

Le samedi 18 février 2023 à 22:09 +0100, Valentin Petzel a écrit : > I do think that even in this case Lilypond should > issue a warning. https://www.mail-archive.com/lilypond-devel@gnu.org/msg78847.html signature.asc Description: This is a digitally signed message part

Re: bad grace note spacing

Le samedi 18 février 2023 à 08:01 +, Werner LEMBERG a écrit : > ``` > > >> The issue I filed is not related to `strict-grace-spacing` at all. > > > > It’s quite related.  [...] > > With 'related' I meant that there are two separate bugs.  I didn't > talk about what the best fix for the

Re: bad grace note spacing

> Le 18 févr. 2023 à 09:01, Werner LEMBERG a écrit : > >  >>> The issue I filed is not related to `strict-grace-spacing` at all. >> >> It’s quite related. [...] > > With 'related' I meant that there are two separate bugs. I didn't > talk about what the best fix for the whole problem

Re: I did not previously realize that Lilypond would automatically update pre-existing scores

 > Le 18 févr. 2023 à 08:31, Werner LEMBERG a écrit : >  >>> It prints a thick fat warning that the LilyPond version is too old >>> to handle this score. It proceeds, but it returns an non-zero >>> error code as a sign of protest :-) >> >> Ahem, no? There is only an additional warning in

Re: bad grace note spacing

> Le 18 févr. 2023 à 00:10, Werner LEMBERG a écrit : > > The issue I filed is not related to `strict-grace-spacing` at all. It’s quite related. In strict-grace-spacing mode, grace columns are not part of the main chain of springs that goes through the whole system from column to columns

Re: I did not previously realize that Lilypond would automatically update pre-existing scores

> Le 18 févr. 2023 à 08:02, Kenneth Wolcott a écrit : > > Hi Werner; > > Then as usual, I'm very confused. > > I'm not using Frescobaldi; the user interface is using a much too > small a font for me to use and I saw no way to enlarge it. Do you mean the font size? It can be changed in

Re: Wondering if there's a way to not just hide N.C symbols, but have them not erase "current" chord.

Le vendredi 17 février 2023 à 16:58 -0600, Matthew Probst a écrit : > One last question regarding this: > * Given that now I have a way to not have to set the N.C. symbol to the empty > string, is there a way to preserve a method of using the N.C symbol when I > _want_ it?  In other words, can

Re: Wondering if there's a way to not just hide N.C symbols, but have them not erase "current" chord.

Le vendredi 17 février 2023 à 16:39 -0600, Matthew Probst a écrit : > I'm working on charts/scores for a full rock/funk band performance, and I am > wondering whether there's an easy way to do what I'm looking for. > I understand chordmode and nodemode, and I understand how to set up separate

Re: Moving breath mark horizontally

Le vendredi 17 février 2023 à 11:03 +0100, Johannes Roeßler a écrit : > Hi Michael, > > > I tried to tweak what you sent - I need it in the opposite way, moving > the sign to the left - in the internal reference it might be > "direction"? > > But I have no clue how to use it.

Re: bad grace note spacing

Le vendredi 17 février 2023 à 18:42 +, Werner LEMBERG a écrit : > ``` > > > Try playing around with spacing parameters. As a starting point: > > > > \override Score.SpacingSpanner.strict-grace-spacing = ##t > > I tried that, but as soon as a group of grace notes has some > accidentals it

Re: Landscape output displays sideways

Le vendredi 17 février 2023 à 12:54 -0500, t...@risingdove.com a écrit : > On 17 Feb 2023 at 18:03, Jean Abou Samra wrote: > > > > > Le vendredi 17 février 2023 à 11:47 -0500, t...@risingdove.com a écrit : > > After some more investigation,

Re: Landscape output displays sideways

Le vendredi 17 février 2023 à 11:47 -0500, t...@risingdove.com a écrit : > After some more investigation, it seems that my problem is not with > Frescobaldi, but with Lilypond 2.24.1. The way you start your message, it sounds like you have already told the list about a problem, but I didn't

Re: bad grace note spacing

> Le 17 févr. 2023 à 12:08, Werner LEMBERG a écrit : > >  > Please have a look at this example. > > ``` > { > \omit Staff.TimeSignature > \repeat unfold 16 { \grace e'8 d'4 } \break > \repeat unfold 8 { \grace e'8 d'4 } > } > > \paper { indent = 0 } > ``` > > As can be seen, the spacing

Re: Key and time change at end of piece

> Le 17 févr. 2023 à 10:37, Aberforth D - Instrumentals > a écrit : > >  > Hello, > > I am working on a complete piano vocal score for an opera. To keep things > manageable I work on individual pieces one at a time, one file per piece. I > intend to combine them later with a superseding

Re: Custom dynamic text with spanner

Le vendredi 17 février 2023 à 00:45 -0600, Evan Driscoll a écrit : > On Fri, Feb 17, 2023 at 12:40 AM Jean Abou Samra > <[j...@abou-samra.fr](mailto:j...@abou-samra.fr)> wrote:It works like this > too: ``` > \version "2.24.0" > > > > { > > \once

Re: Double bar notation in middle of measure

Le vendredi 17 février 2023 à 07:31 +0100, Jean-Julien Fleck a écrit : > Have you tried ? > It seems to me that \bar doesn't perform any bar-check as to be able to break > a line inside a mesure, you just insert an invisible bar with \bar "" `\bar ""` is actually not necessary or recommended

Re: Custom dynamic text with spanner

Le vendredi 17 février 2023 à 00:31 -0600, Evan Driscoll a écrit : > > On Fri, Feb 17, 2023 at 12:17 AM Michael Werner > <[reznae...@gmail.com](mailto:reznae...@gmail.com)> wrote: > > > Short version:\set crescendoText = \markup { \italic { molto cresc } } > > \set crescendoSpanner = #'text >

Re: LilyPond has been updated on BytesIn

Le jeudi 16 février 2023 à 08:53 +, BytesIn a écrit : > We've sent this email because we have updated > LilyPond and this was the contact email supplied for the application. > > **Your application update status** >

Re: Problem with `\acciaccatura` and `\cueDuring`

Le jeudi 16 février 2023 à 06:30 +, Werner LEMBERG a écrit : > ``` > > >> As can be seen, the acciaccatura neither has a slash nor a slur if > >> quoted.  [...] > > > > This looks like a real bug, please file an issue. > >

Re: Problem with `\acciaccatura` and `\cueDuring`

Le mercredi 15 février 2023 à 19:34 +, Werner LEMBERG a écrit : > ``` > > Consider this example. > > ``` > fluteNotes = \relative { >   r2. c''4 | >   d8 \acciaccatura e c d e fis2 | >   g2 d | > } > > oboeNotes = \relative c'' { >   R1 | >   \cueDuring "flute" #UP { R1 } | >   g2 d | > } >

Re: Centering footnote for analysis

Le mercredi 15 février 2023 à 22:12 +0100, Valentin Petzel a écrit : > and is the default behaviour with > 2.24. The default is to use `X-attachment = LEFT` if the X offset of the small footnote line (the car of the number pair passed to `\footnote`) is negative, `CENTER` if it's zero, and

Re: Conditional Definitions

> Le 15 févr. 2023 à 20:55, Fr. Samuel Springuel a > écrit : > > I recently upgraded from 2.22 to 2.24 and have run into some problems with > one of my tools. The tool is set up to define some some stuff (in the > example attached below I’ve narrowed it down to be just a color), but only

Re: Centering footnote for analysis

> Le 15 févr. 2023 à 20:31, Calvin Ransom a écrit : > >  > Hello everyone, > > I am trying to attach a footnote to the center of a glissando as pictured > below. Does anyone know how to do this? I have tried following the directions > for attaching it to a grob (NR 3.3.4) > > Here is my

Re: vertical spacing of footnotes

Le mardi 14 février 2023 à 15:13 +, Werner LEMBERG a écrit : > Excellent, thanks!  I slowly arrive at some nice results, see attached > code and image.  However, there is one problem that I don't > understand: Why is the space between footnotes 3 and 4 (and 4 and 5) > larger than between 1 and

Re: accidental query

Le mardi 14 février 2023 à 19:49 +0100, Karim Haddad a écrit : > Thank you Hans, Gregory and Jean, > > Your help is precious. > > Just another beginner's question: > I found amazingly that Lily plays the 1/8th tones correctly as it does for > 1/4th tones. > If i need to use other weird

Re: accidental query

Le mardi 14 février 2023 à 19:11 +0100, Jean Abou Samra a écrit : > Le mardi 14 février 2023 à 15:27 +0100, Karim Haddad a écrit : > > > Dear All, > > Maybe this was already submitted. I am looking for this particular symbol > > to use as alteration for 1/8th tones.

Re: accidental query

Le mardi 14 février 2023 à 15:27 +0100, Karim Haddad a écrit : > Dear All, > > Maybe this was already submitted. I am looking for this particular symbol to > use as alteration for 1/8th tones. (cf. screenshot attached) > However it seems missing in the Emmentaler font. Is it possible to

Re: vertical spacing of footnotes

Le mardi 14 février 2023 à 15:02 +0100, Valentin Petzel a écrit : > But \column does have exactly that issue. Column will hickup on "lines" > spanning multiple lines. Precisely. That's why it should receive the lines individually rather than already combined in a stencil. ``` \version

Re: vertical spacing of footnotes

Le mardi 14 février 2023 à 13:02 +0100, Valentin Petzel a écrit : > As far as I see this is not the problem. Footnotes appear to be simply > stacked > by extent, not by baseline. This already creates issues with footnotes > extending over multiple lines, as the spacing between different

Re: vertical spacing of footnotes

Le mardi 14 février 2023 à 07:28 +, Werner LEMBERG a écrit : > * In what context are footnote texts handled?  I want to globally >   adjust `baseline-skip` for my (redefined) `\strut` function, but I'm >   not able to do it. Like all sticky grobs, footnotes are created in the same context

Re: vertical spacing of footnotes

Le lundi 13 février 2023 à 19:37 -0500, kie...@kierenmacmillan.info a écrit : > Am I the only one who thinks users shouldn’t have to add transparent > letters with ascenders and descenders in order to have a consistent line > height?! Working with text should not require such efforts…

Re: Documentation: Should we possibly have aliases for current stable and current devel?

Le lundi 13 février 2023 à 12:02 -0500, Kevin Cole a écrit : > That's okay too... as long as, when I ask a question, the answer isn't > always "upgrade". To speak for myself: If you say in your post “I know that this feature is in the latest stable version but I can't/don't want to upgrade

Re: `\afterGrace` and clef problem

Le lundi 13 février 2023 à 18:08 +0100, David Kastrup a écrit : > That begs the question whether it would make sense to restrict > afterGrace scales to values below 1.  But I think that making syntactic > decisions based on values rather than types is really icky.  It is > probably a bad

Re: Documentation: Should we possibly have aliases for current stable and current devel?

Le lundi 13 février 2023 à 11:40 -0500, Kevin Cole a écrit : > The point I was trying to make was "Does there REALLY need to be > documentation for versions 2.13 to 2.25?  Maybe 2.20 to 2.25 would > suffice." I'm not sure it would help with Qwant/DuckDuckGo/Google searches since we are

Re: Documentation: Should we possibly have aliases for current stable and current devel?

Le lundi 13 février 2023 à 17:37 +0100, Lukas-Fabian Moser a écrit : > Hi, > > > From [https://lilypond.org/help-us.html](https://lilypond.org/help-us.html) > > > > > > “Mailing list support: answer questions from fellow users. (This > > may entail helping them navigate the

Re: Documentation: Should we possibly have aliases for current stable and current devel?

Le lundi 13 février 2023 à 09:42 -0600, David Wright a écrit : > Very tangential to this, a URL like: > >   > [https://lists.gnu.org/archive/html/lilypond-user/recent](https://lists.gnu.org/archive/html/lilypond-user/recent) > > that would redirect to: > >   >

Re: Documentation: Should we possibly have aliases for current stable and current devel?

Le 13 févr. 2023 à 15:51, Valentin Petzel a écrit :Hello Pondmates!I’ve been wondering recently: When acessing the documentation we are usually acessing a specific version, we have something likelilypond.org/doc/v2.xy/whateverThis seems to mess with Google’s page scoring quite a bit. Now if I

Re: `StaffGroup` influences spacing of `DynamicText`

Le lundi 13 février 2023 à 10:48 +, Werner LEMBERG a écrit : > ``` > > Can someone please explain to me why the 'p sub.' in the first system > is badly spaced compared to the second one?  How can I avoid this? > Actually, this smells like a bug... You can read your own answer to this

Re: 2 Voices | 1 Staff | Mensuration Lines | Lyrics

Le samedi 11 février 2023 à 22:14 +0100, Valentin Petzel a écrit : > 2) Instead of using such a parallel global thing with \hide BarLine we can > achieve the same effect by doing > > \version "2.24.0" > > \layout { >   \override Staff.BarLine.stencil = >   #(grob-transformer 'stencil >  

Re: 2 Voices | 1 Staff | Mensuration Lines | Lyrics

Le samedi 11 février 2023 à 21:39 +0100, Johannes Roeßler a écrit : >   \new Staff { >     \voices 1,2<< \global \sopI \sopII >> >   } >   \lyricsto "2" { \words } Make that ``` \new Staff { << \global \voices 1,2 << \sopI \\ \sopII >> >> } \lyricsto

Re: `\offsetPosition` fails

Le samedi 11 février 2023 à 15:01 +, Werner LEMBERG a écrit : > ``` > > I'm using the `\offsetPosition` command > ([https://lsr.di.unimi.it/LSR/Item?id=748](https://lsr.di.unimi.it/LSR/Item?id=748)). >   Unfortunately, it fails in > a multi-staff, real-world piece: it has zero effect, and I

Re: Fun with Python...

    Le 10 févr. 2023 à 04:11, Jeff Kopmanis a écrit : What version of Lilypond will that appear in?     "That" refers to Guile 3, right? There are no plans yet. It is currently

Fun with Python...

Hi, I just want to share a little adventure. For context: I was not very satisfied with the snippet [https://lsr.di.unimi.it/LSR/Item?id=1153](https://lsr.di.unimi.it/LSR/Item?id=1153) because its interface is ``` \markup \qr-code "" ``` rather than ``` \markup \qr-code "https://my-url.com;

Re: Vertical arrows next to note

> Hello, > > It should be possible to use an Argpeggio with a custom stencil using > elements of arpeggioArrowDown and arpeggioBracket without protrusion. > This is beyond my current capabilities unfortunately. Something like this? ``` \version "2.24.0" arrow = #(define-event-function

Re: Voice for Lyrics

Le jeudi 09 février 2023 à 14:04 +0100, Johannes Roeßler a écrit : > Hi, > > I'm looking how to assign the lyrics two one of two voices in one staff > in the simplest way with my "normal" source code: > bassVoicePart = \new Staff \with { >   midiInstrument = "oboe" >   

Re: music function playing well with context

On 08/02/2023 20:00, Alberto Simões wrote: > I get a >   Unbound variable: when > may it be the lilypond version? running 2.22 here. > THanks when was added in Guile 2, which LilyPond 2.24 uses while LilyPond 2.22 is on Guile 1. But I really recommend upgrading to 2.24. OpenPGP_signature

Re: music function playing well with context

On 08/02/2023 19:45, Alberto Simões wrote: > I just noticed this does not support chords: \myT f > While I can do that manually (just a couple of cases) it would be nice to > learn how to handle these cases. > Would it be possible? Chords are distinguished by having the music class

Re: writing score in absolute time

On 08/02/2023 09:05, Cordelia wrote: > Yes, I see. Now the warning is gone. > > What I mean is this: > Now I’m start tweaking all the parameters and creating a nice score, but you > can see that each duration line if there’s a note that “superpose” on his > duration, it breaks. > I think it’s

Re: Installation of Lilypond 2.24.0 on a Windows 11 computer

On 08/02/2023 13:35, tommy_strandb...@web.de wrote: > Hi Jean, > > As I said yesterday, it's working now but I've run the FC_DEBUG you asked for > yesterday, see attachment > "Lilypond2240_isRunningOK_programInHomeDirectory.txt". If it for some reason > will start generating the errors I had

Re: Visible Barline in ChoirStaff

> Le 8 févr. 2023 à 16:13, Johannes Roeßler a écrit : > >  > Hi Group, > > how can I add a visible (in the sense of connecting all staffs) barline in a > choirstaff? > > I tried \once \override Staff.BarLine.transparent = ##f \bar "|" > > but o course it doesn't work, for its just in a

Re: Clef with Ottava in parenthese

> Le 8 févr. 2023 à 15:27, Johannes Roeßler a écrit : > >  > Hi Group, > > is it possible to create a clef like this: > > > > Like \clef "violin_8" but with the 8 in parentheses? > See the fourth example here:

Re: music function playing well with context

On 07/02/2023 22:17, Alberto Simões wrote: > Understood. Thank you . > After looking to the example, it makes sense, but it wasn't easy to get there > :-)> Always great to learn! Perhaps you will have an easier time building custom functions after reading pages like these:

Re: music function playing well with context

On 07/02/2023 21:57, Alberto Simões wrote: > Hello > > I am transcribing a piece that has a lot of tuplets: >   >    \tuplet 3/2 { a4 b8 } > > The duration of the notes is always this, just the pitch changes. > I tried to create a music function with this code > > myT = #(define-music-function

Re: Installation of Lilypond 2.24.0 on a Windows 11 computer

On 07/02/2023 19:25, tommy_strandb...@web.de wrote: > 2. The handbook is very misleading as it states ( > https://lilypond.org/doc/v2.23/Documentation/learning/graphical-setup-under-windows > > ) > “Place

Re: writing score in absolute time

On 07/02/2023 16:57, Cordelia wrote: > Totally, now it begins the game. But at least I’ve a starting point! > > I’ve to understand better the tempo and rhythmic values in lilypond. > I’ve already added the possibility to write cents for exemple for > microtonality (a simple way). > > There’s 2

Re: writing score in absolute time

On 07/02/2023 17:57, Aaron Hill wrote: > On 2023-02-07 8:22 am, Knute Snortum wrote: >> Setting the paper size to A4 should be as simple as: >> >> \paper { >>   #(set-paper-size "letter") >> } > > Well, that produces US letter size: 8.5" x 11".  For A4, you would naturally > use "a4". > > The

Re: Installation of Lilypond 2.24.0 on a Windows 11 computer

On 07/02/2023 17:00, tommy_strandb...@web.de wrote: > Hi, > > I’m a little annoyed over problems in getting Lilypond 2.24.0 properly > running on my computer.  My previous installation was Lilypond 2.22.2 > together with Frescobaldi 3.2.  Everything worked fine and the main reason > for

Re: writing score in absolute time

On 07/02/2023 14:58, Cordelia wrote: > Amazing, really. > I lastly just wonder now, if it’s possible to write the duration in seconds.. > But I understood that’s not the way of working of lilypond. > Thank you! This can be done too. \version "2.24.0" \paper { page-breaking =

Re: writing score in absolute time

On 07/02/2023 14:12, Cordelia wrote: > Oh, yeah. Thank you very very much. It gives me a lot of ideas!! It’s what I > was looking for. > > Do you have just an idea if it could be possible to write just a line (with a > lil’ bar at the end maybe) that could represent the duration of the note? >

Re: chord placement in Scores

On 07/02/2023 12:51, Jean Abou Samra wrote: > On 07/02/2023 05:44, Jeff Kopmanis wrote: >> I've found that when I put chords in my score, it's printing them /below/  >> the staff rather than above, as usual.  Things are normal if I'm not >> building a score,

Re: writing score in absolute time

On 04/02/2023 18:28, Jacopo Greco d'Alceo wrote: > Thank you Gregory for your complete answer. > And you’ve seen it right. I’m not yet an Abjad user, but I looked at it with > interest - but never drown inside. > I’m just another composer still dreaming about writing music easily with a >

Re: Command Alises

On 07/02/2023 12:59, Jean Abou Samra wrote: > On 07/02/2023 12:45, p...@ocmatos.com wrote: > >> Right, I confused the names, thanks for the help. One further question, why >> the need to prefix the commands with a - ? Does it start some sort of >> command mode? > &

Re: Command Alises

On 07/02/2023 12:45, p...@ocmatos.com wrote: > Right, I confused the names, thanks for the help. One further question, why > the need to prefix the commands with a - ? Does it start some sort of command > mode? You don't have to. It's just a neutral direction indicator. It is implicit if you

Re: chord placement in Scores

On 07/02/2023 05:44, Jeff Kopmanis wrote: > I've found that when I put chords in my score, it's printing them /below/ the > staff rather than above, as usual.  Things are normal if I'm not building a > score, but I'm wondering why this is happening.  I've included my (big) .ly > document and

Re: Dynamics for both staves

On 07/02/2023 12:44, p...@ocmatos.com wrote: > On 2023-02-03 17:41, Knute Snortum wrote: >> >> What I do is have a separate dynamics variable, then include that >> variable in both staves of the piano staff in the midi block.  Then I >> switch the dynamic performer to the staff level.  It looks

Re: Translating “Extending LilyPond” — any takers?

On 07/02/2023 10:52, Kenneth Flak wrote: > > Hi Jean, > > Thanks so much for continuing to develop this invaluable resource! I have one > small issue with the site in dark mode (which seems to be the default on my > linux system and android phone): some of the writing is barely legible, with

Re: Translating “Extending LilyPond” — any takers?

Just a small note: for various reasons, the guide has moved from ReadTheDocs to GitLab pages. The new URL is https://extending-lilypond.gitlab.io (old URLs have been turned into redirects). Best, Jean OpenPGP_signature Description: OpenPGP digital signature

Re: single system output in 2.24

Klaus, > Le 5 févr. 2023 à 16:56, Klaus Blum a écrit : You are not subscribed to this list. Can you please subscribe (https://lists.gnu.org/mailman/listinfo/lilypond-user) so that list admins don’t have to approve each of your messages manually? Thanks, Jean

Re: how to avoid double sharps in \transpose?

On 04/02/2023 21:07, Kenneth Flak wrote: > > This comes out correctly: > > patright = { > 2 | > } > > right = { > #@(map (lambda (p) #{ \transpose c #p \patright #}) > (event-chord-pitches #{ #})) > } > > This, however, transposes the g c sequence to b e instead on the first

Re: writing score in absolute time

On 04/02/2023 10:26, Jacopo Greco d'Alceo wrote: > Hello everybody, > > I’ve always wondered if it’s possible to write a lilypond score in *absolute > time*, just giving almost 2 parameters: note and absolute time in seconds, > without the measure boundaries. > If yes, can you give some

Re: Image width issue

On 31/01/2023 20:23, Rajesh Baskar wrote: > Hi Jean, > > The solution you gave me works very good for whole notes. But if the notes > have stems then the stems are not removed. Please look at the LilyPond like > below. Is this what you want? \version "2.24.0" \language english boxify =

Re: Command Alises

> Le 3 févr. 2023 à 16:32, Paulo Matos a écrit : > > Hi, > > I would like to define command aliases for \SustainOn, \SustainOff and > the combination \SustainOn\SustainOff and tried the obvious: > > pup = \SustainOn > pdown = \SustainOff It’s \sustainOn and \sustainOff. Jean

Re: Barline glyph in markup

On 03/02/2023 10:50, Rip _Mus wrote: > Hi, > is it possible to use a repeat barline glyph(opened or closed) in a markup? > I'm trying to print it centered between two staves within a Dynamics context. > Thank you in advance! The two other answers work, but I wonder if this might be an XY

Re: Including fermata in \cueDuring

On 03/02/2023 04:37, Vaughan McAlley wrote: > Hi, > > I can’t seem to get fermatas included in cues. I have tried adding > text-script-event to Score.quotedCueEventTypes, but this doesn’t seem to > work. Do I have the wrong event type? It's a script-event. text-script-event is for note^"text"

Re: \stopStaff \startStaff spacing & line continuity

On 01/02/2023 02:56, Ahanu Banerjee wrote: > I am trying to modify the color of the ledger lines for a single note. My > understanding is that I need to use \stopStaff and \startStaff for this. > However, doing so causes the staff lines to be discontinuous. This rounds the > ends of the staff

Re: Error in Extending Lilypond example

On 01/02/2023 18:05, Saul Tobin wrote: > Oh wow really? It's the best/only documentation for several things that > aren't really covered in the official Extending docs. Maybe it should become > official? Or at least easier to find.I didn't know it existed until you > posted to the list about

Re: Error in Extending Lilypond example

On 01/02/2023 11:12, Jean Abou Samra wrote: > Saul, > > >> Le 1 févr. 2023 à 04:16, Saul Tobin a écrit : >> >> The fourth example engraver here: >> https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example >&g

Re: \stopStaff shows/doesn't show ledger lines?

On 01/02/2023 17:49, Valentin Petzel wrote: > Hello Richard, > > This is not so much a bug in \stopStaff, but an inconsistency in the > LedgerLineSpanner engraver. It is good you’ve found a workaround that works > for you! If you see a bug, please file a GitLab issue. Thanks, Jean

Re: Error in Extending Lilypond example

> Le 1 févr. 2023 à 11:23, Thomas Morley a écrit : > > Am Mi., 1. Feb. 2023 um 04:16 Uhr schrieb Saul Tobin > : >> >> The fourth example engraver here: >> https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example >> >> Running this code in 2.24

Re: Error in Extending Lilypond example

Saul, > Le 1 févr. 2023 à 04:16, Saul Tobin a écrit : > > The fourth example engraver here: > https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example > > Running this code in 2.24 crashes on initializing the engraver with In > procedure

Re: Multiple instances of same articulation/bowing on one note

On 01/02/2023 03:51, Ahanu Banerjee wrote: > It's obviously not a bug. Jean, thanks for pointing out where the relevant > instruction is. > > What would be the easiest way to modify this behavior for a single score?  It's a bit of a weird thing to do, but you could consider \version "2.24.0"

Re: Multiple instances of same articulation/bowing on one note

On 01/02/2023 03:59, kie...@kierenmacmillan.info wrote: > Hi all, > >> I would personally consider that a bug! >> script-engraver.cc: >> >> void >> Script_engraver::listen_articulation (Stream_event *ev) >> { >>   /* Discard double articulations for part-combining.  */ >>   for (vsize i = 0; i <

Re: Multiple instances of same articulation/bowing on one note

On 01/02/2023 03:34, kie...@kierenmacmillan.info wrote: > Hi Ahanu, > >> g_\upbow ^\upbow g g % fails >   > I would personally consider that a bug! script-engraver.cc: void Script_engraver::listen_articulation (Stream_event *ev) { /* Discard double articulations for part-combining. */ for

Re: Setting default arguments for music function?

On 01/02/2023 01:23, Ahanu Banerjee wrote: > Is it possible to have one of the arguments rely on a property of another > argument?  > > In my example, I want the default value for "parenColor" to be the same as > the color of the "parenItem": > > \version "2.24" > \language "english"  >

Re: Setting default arguments for music function?

On 01/02/2023 01:04, Ahanu Banerjee wrote: > Is it possible to specify default values for a function to use when arguments > are missing? In the example below, I want the default font size to be -4 and > the default color to be blue without having to specify it each time, but I > also want the

Re: Tie not working as expected

On 31/01/2023 23:06, Steve Carlock wrote: > Jean, > > Thank you for approving my email - I did subscribe using the website and > confirmed the email (and have logged into my account page successfully) prior > to sending my email to the list. Maybe I was impatient and needed to wait a > day for

Re: Understanding marks in 2.24

On 31/01/2023 22:33, Jean Abou Samra wrote: > Uh, why did I just write this already? The latter wouldn't > be a problem. assign_event_once uses "equal?" The former, > with procedures, is indeed a problem. > > Sorry for the noise. Looking a bit more into d

Re: Understanding marks in 2.24

On 31/01/2023 22:32, Jean Abou Samra wrote: > On 31/01/2023 22:07, Saul Tobin wrote: >> I have a few questions: >> 1. How to achieve horizontal alignment and avoid vertical overlap of >> RehearsalMarks and MetronomeMarks at the beginning of a system, or when >> mus

Re: Understanding marks in 2.24

On 31/01/2023 22:07, Saul Tobin wrote: > I have a few questions: > 1. How to achieve horizontal alignment and avoid vertical overlap of > RehearsalMarks and MetronomeMarks at the beginning of a system, or when > musical objects push them away from the staff as in measure 3? I have to say > I

Re: Tie not working as expected

Hello, Welcome to this list. I had to approve your message manually because you are not subscribed to the list yet. Please fix this by subscribing on https://lists.gnu.org/mailman/listinfo/lilypond-user On 31/01/2023 22:04, Steve Carlock wrote: > New Lilypond user here.  The following code is

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