Re: Future of OpenLilyLib

I may as well shutdown openlilylib.space then. There are only 15 users, and it costs money for me to run the server, and there is zero traffic on Discourse. Andrew On 22/11/2022 9:22 am, Jean Abou Samra wrote: Le 21/11/2022 à 23:19, Andrew Bernard a écrit : Hello All, Why don't we keep

Re: Future of OpenLilyLib

On Mon, Nov 21, 2022, 6:11 PM Andrew Bernard wrote: > it costs money for me to run the server > What storage and RAM is needed? I might be able to host it for you. -- Karlin High Missouri, USA >

Re: Note head as a custom image chosen according to note duration

On 2022-11-21 3:36 pm, Jean Abou Samra wrote: Le 22/11/2022 à 00:31, Aaron Hill a écrit : But NoteHead has a duration-log property ready to go: The OP says "according to the duration". I didn't know if using duration-log would be OK for this case, because duration-log does not make a

Re: Custom Music font doesn't scale with staff

On Mon, Nov 21, 2022 at 2:33 PM Leo Correia de Verdier < leo.correia.de.verd...@gmail.com> wrote: > In the expression > > #:factor (/ staff-height pt 20) > > staff-height retrieves the staff height and divides it by 20. It works for > any staff height. > > > 21 nov. 2022 kl. 22:23 skrev Yentl

Re: Future of OpenLilyLib

Am 21.11.22 um 23:28 schrieb Jean Abou Samra: One would add a new keyword in the parser akin to \include (\import? \load?). How about \require? ... module code ... \endModule % or whatever name ... example ... where \endModule would act as a "trap" interrupting the parsing, but only if

Re: Prefer luatex for documentation

Le 21/11/2022 à 23:14, Jean Abou Samra a écrit : I tried doing a speed test myself, but hit https://gitlab.com/lilypond/lilypond/-/merge_requests/1714#note_1180441076 After correcting my stupid mistake, I got pdfTeX: real    21m43,063s user    117m52,570s sys    17m24,881s LuaTeX: real 

Re: Flexible lyric alignment

On Mon, Nov 21, 2022 at 6:36 PM Jean Abou Samra wrote: > Hi, > > > Le 20/11/2022 à 21:50, Kieren MacMillan a écrit : > >> Kieren, you've got to try this out! It will blow your mind! > > I just took Jean’s example, and compared the output with and without the > \include step… Truly astonishing. >

Re: Flexible lyric alignment

Hi, Le 20/11/2022 à 21:50, Kieren MacMillan a écrit : Kieren, you've got to try this out! It will blow your mind! I just took Jean’s example, and compared the output with and without the \include step… Truly astonishing. (I haven’t tried it with my Real World Scores™, but can’t wait to do

Note head as a custom image chosen according to note duration

Hi. The code below is a copy, I do not quite understand what it does. Can I modify it so that an image is chosen according to the following note's duration? Like custom4.eps, custom8.eps? customHead = { \once \override NoteHead #'stencil = #ly:text-interface::print \once \override NoteHead

Future of OpenLilyLib

With the imminent release of LilyPond 2.24, I thought it would be good to (once again) raise the topic of OpenLilyLib. There has been some recent movement on this (thanks to Jean and Andrew) to get the code mostly working with recent LilyPond versions and Guile 2. I have also just pushed a bunch

Re: Future of OpenLilyLib

Maybe what I'm going to say will sadden some, but personally, I never quite understood what the advantage of developing openLilyLib as a library external to LilyPond, as opposed to contributing features to LilyPond itself, was supposed to be. I was going to add my lyrics code to LSR, actually.

Re: Future of OpenLilyLib

On 11/21/2022 11:09 AM, Mark Knoop wrote: It would be good to get a feel from users how much this resource isused I have heard lots of good things about OpenLilyLib. But I remain somewhat unclear as to what it offers and how it would be used in my usages for SATB/TTBB shape-note hymns and

Re: Note head as a custom image chosen according to note duration

Le 21/11/2022 à 13:43, Jean Faure a écrit : Hi. The code below is a copy, I do not quite understand what it does. Can I modify it so that an image is chosen according to the following note's duration? Like custom4.eps, custom8.eps? customHead = {  \once \override NoteHead  #'stencil =

Re: Future of OpenLilyLib

Thanks Jean for your thoughts, which are not so far from my own. A few comments: > Maybe what I'm going to say will sadden some, but personally, > I never quite understood what the advantage of developing > openLilyLib as a library external to LilyPond, as opposed to > contributing features to

Re: Future of OpenLilyLib

Le 21/11/2022 à 20:02, Mark Knoop a écrit : Thanks Jean for your thoughts, which are not so far from my own. A few comments: Maybe what I'm going to say will sadden some, but personally, I never quite understood what the advantage of developing openLilyLib as a library external to LilyPond, as

Re: Future of OpenLilyLib

Le 21/11/2022 à 23:19, Andrew Bernard a écrit : Hello All, Why don't we keep the discussion about OLL on the OLL Discourse forum I created and run? That's the whole point of it, and to avoid cluttering the Lilypond User list. I think Mark's goal was to reach LilyPond users who are only

A lyrics problem

Hello folks, I have a word across a measure and a coda placed farther ahead in the score, as shown below. Is there a way to hide the hyphens between "Kumba" and the measure starting the coda? This can be tested on the snippet at the end of this message. Thanks if you can help! JM … … …

Re: Future of OpenLilyLib

Le 21/11/2022 à 23:02, Kieren MacMillan a écrit : Then they should definitely be added: those were things Urs and I discussed (a fair bit off-list) as principle obstacles to the integration of “external” code (mostly equivalent to OLL at the time) into the ’Pond ecosystem. The first step to

Re: Future of OpenLilyLib

Hi Jean, > The first step to adding non-trivial things that need discussion > is opening an issue. Do you feel like doing that? https://gitlab.com/lilypond/lilypond/-/issues/6475 Look at me, being all “Do first” ’n’ stuff… ;) We taking the discussion over there? K

Re: Future of OpenLilyLib

Hi Jean, > I would change the tense: > > [Independently of OLL,] non core developers *are* able to implement > new features with Scheme code that *can* potentially be included in > base LilyPond if proven reasonable. > > Don't you agree? I do agree that users are able to implement feature with

Re: A lyrics problem

With: % (12) Oh | Lo -- rd Kum -- \once \override LyricText.X-offset = #-0.5 "ba -" -- | I get this, which is not bad : > Le 21 nov. 2022 à 23:27, Jacques Menu a écrit : > > Hello folks, > > I have a word across a measure and a coda placed farther ahead in the score,

Re: Note head as a custom image chosen according to note duration

Hello Jean, the line \once \override NoteHead.stencil = #ly:text-interface::print tells Lilypond to derive the symbol it uses for the note head as if the note head was some sort of text object (changed the old syntax NoteHead #'stencil to the new prefered syntax NoteHead.stencil). Then

Re: Note head as a custom image chosen according to note duration

On 2022-11-21 3:13 pm, Valentin Petzel wrote: The duration of the NoteHead is not in fact a property of the grob, but of the music event that leads to creation of the grob, accessible from the grob by the "cause"-property. Thus Jean uses (ly:event-property (event-cause grob) 'duration) to

Re: A lyrics problem

Hi Jacques, there is also the option of doing something like this: { c2 2 << R1*3 { s8 \grace { \once\omit NoteHead c1 } s4. s2 s1 s2 s4. \grace { \once\omit NoteHead c1 } } >> c1 } \addlyrics { \set includeGraceNotes = ##t Kum -- ba -- "" "" -- ya } I suppse a proper implementation would have

Re: Note head as a custom image chosen according to note duration

Le 22/11/2022 à 00:31, Aaron Hill a écrit : But NoteHead has a duration-log property ready to go: The OP says "according to the duration". I didn't know if using duration-log would be OK for this case, because duration-log does not make a difference between quarters, heighth notes and

Re: Custom Music font doesn't scale with staff

Le 21/11/2022 à 21:11, Yentl Tijssens a écrit : Hello, I use the custom font Beethoven. Even though I have all the correct sizes installed, the font doesn’t use the right one when changing the default size: Doesn’t anyone have a solution to this? \version "2.22.2" #(set-global-staff-size 12)

Re: Future of OpenLilyLib

Hi all, > Maybe what I'm going to say will sadden some, but personally, > I never quite understood what the advantage of developing > openLilyLib as a library external to LilyPond, as opposed to > contributing features to LilyPond itself, was supposed to be. cf. our past discussions (some on

Re: Custom Music font doesn't scale with staff

On Mon, Nov 21, 2022 at 2:11 PM Yentl Tijssens wrote: > Oh, it’s the creator themselves, what an honour! > Your solution worked. I was only wondering how I should calculate the > required #:factor depending on the staff size. > > PS: I have to tell you, it’s largely thanks to your font that I

Re: Custom Music font doesn't scale with staff

In case you missed it: I was just wondering how I should calculate the required #:factor depending on the staff size? Happy Holidays as well, Yentl Tijssens > On 21 Nov 2022, at 22:19, Abraham Lee wrote: > > On Mon, Nov 21, 2022 at 2:11 PM Yentl Tijssens >

Re: Future of OpenLilyLib

Le 21/11/2022 à 21:55, Kieren MacMillan a écrit : cf. our past discussions (some on -devel, some private) about my attempts to add code, where it should go, etc. =) Yes, I remember that :-) 2. Obviously I use oll-core, since that is foundational to the EE. Note: oll-core is a

Re: Future of OpenLilyLib

Hello Jean, Hello All, I think the main problem with OLL is that it tries to provide some sort of equivalent of the STL for Lilypond. Thus is packs a lot of functionality in one big chunk that is hard to organize and hard to maintain, feeling like a big, alien thing. In my opinion it is not

Re: Future of OpenLilyLib

Le 21/11/2022 à 22:38, Valentin Petzel a écrit : In my opinion it is not bad to allow for modular extension of Lilypond, especially for things that do not fit the core of the program. You need to keep in mind that this would be a strong possibility of enhancing Lilypond without cluttering it’s

Re: Future of OpenLilyLib

Hello Karlin, I’m sure no one who engages on the list will feel burdened by your questions, in the worst case they might just not engage with it and ignore it, that is as long as you talk nicely and do not demand for things (as the people here are doing this because they want to in their spare

Re: Custom Music font doesn't scale with staff

Hello, Look here: https://lilypond.org/doc/v2.22/Documentation/notation/fonts[1] You will find a #:factor parameter: #:factor (/ staff-height pt 20) This factor is used for scaling the actual glyphs, and if you omit it your font will not be scaled and be issued at a standard staff size of 20

Re: Custom Music font doesn't scale with staff

Hi, Yentl! On Mon, Nov 21, 2022 at 1:40 PM Yentl Tijssens wrote: > Hello, > I use the custom font Beethoven. Even though I have all the correct sizes > installed, the font doesn’t use the right one when changing the default > size: > Doesn’t anyone have a solution to this? > > \version "2.22.2"

Re: Custom Music font doesn't scale with staff

Le 21/11/2022 à 21:57, Abraham Lee a écrit : If you do that, it resets the font tree back to Emmentaler. So, the order is correct, the set-global-fonts command is just incomplete (see my other response). Oops, sorry, I was going too fast. Best, Jean OpenPGP_signature Description:

Re: Custom Music font doesn't scale with staff

On Mon, Nov 21, 2022 at 1:53 PM Jean Abou Samra wrote: > Le 21/11/2022 à 21:11, Yentl Tijssens a écrit : > > Hello, > > I use the custom font Beethoven. Even though I have all the correct > sizes installed, the font doesn’t use the right one when changing the > default size: > > Doesn’t anyone

Re: Custom Music font doesn't scale with staff

Oh, it’s the creator themselves, what an honour! Your solution worked. I was only wondering how I should calculate the required #:factor depending on the staff size. PS: I have to tell you, it’s largely thanks to your font that I get so many compliments from the jury of my conservatory on the

Re: Custom Music font doesn't scale with staff

In the expression #:factor (/ staff-height pt 20) staff-height retrieves the staff height and divides it by 20. It works for any staff height. > 21 nov. 2022 kl. 22:23 skrev Yentl Tijssens : > > In case you missed it: I was just wondering how I should calculate the > required #:factor

Re: Future of OpenLilyLib

Hi all, > I don't think we're very far from that. Include files already work > as kinds of modules. I only see two potential differences between modules > and include files: > > - a module should only be loaded once, even if imported twice in > different locations, > > - a module could

Re: Prefer luatex for documentation

Le 21/11/2022 à 22:10, Jonas Hahnfeld via Discussions on LilyPond development a écrit : And whether we can just *require* LuaTeX and stop looking for pdfTeX and XeTeX altogether? I did a few measurements for the case of building the LilyPond documentation and, in terms of speed with the "CI

Re: Future of OpenLilyLib

Hello All, Why don't we keep the discussion about OLL on the OLL Discourse forum I created and run? That's the whole point of it, and to avoid cluttering the Lilypond User list. It's free to sign and and join. Otherwise I am running the website for nothing. https://openlilylib.space All