Re: feature requests: scalable \shape values; (stem) for \shapeII

Hi Andrew, I'll put up a MR to add the improved \shape to lilypond proper, as soon as I find the time to do so. At least it will be an improvement. Though, I did not look into shapeII, maybe it could be improved similarly? Cheers, Harm Am Mo., 12. Okt. 2020 um 09:55 Uhr schrieb Andrew Bernard

Re: feature requests: scalable \shape values; (stem) for \shapeII

Stay tuned, and will add the improvement to the OLL repository, once I have it all set up. Andrew On Mon, 12 Oct 2020 at 17:44, Martín Rincón Botero wrote: > > > I have to run more tests, but your \shape-h function is simply excellent. > Thank you! I wish this could be the default behavior of a

Re: feature requests: scalable \shape values; (stem) for \shapeII

Dear Harm, I have to run more tests, but your \shape-h function is simply excellent. Thank you! I wish this could be the default behavior of a new \reshape function. Perhaps the open issue shouldn’t be fixed for \shape: that way the folks who carefully used small values for small staves to fix

Re: feature requests: scalable \shape values; (stem) for \shapeII

Dear Thomas, sorry for not having provided examples myself of what doesn’t scale. I haven’t had the time for that yet. However, your explanation seems to be right. I definitely have to use smaller values for smaller font sizes. I was planning to collect a few examples from the viola concerto I’

Re: feature requests: scalable \shape values; (stem) for \shapeII

Am Mi., 7. Okt. 2020 um 10:35 Uhr schrieb Martín Rincón Botero : > > Now that we’ve been talking about \shape and \shapeII, I would like to ask if > it’s possible that values put for \shape(II) could scale according to staff > size. Whenever I have a smaller staff, whatever values work for a 20 p

Re: feature requests: scalable \shape values; (stem) for \shapeII

Le 07/10/2020 à 19:50, Jean Abou Samra a écrit : Le 07/10/2020 à 18:58, Martín Rincón Botero a écrit : Hello Jean, thanks for further exploring the first request. In my experience with Lilypond 2.20 \shape doesn’t scale with set-global-staff-size either. I’m already kinda “used” to writing

Re: feature requests: scalable \shape values; (stem) for \shapeII

Le 07/10/2020 à 18:58, Martín Rincón Botero a écrit : Hello Jean, thanks for further exploring the first request. In my experience with Lilypond 2.20 \shape doesn’t scale with set-global-staff-size either. I’m already kinda “used” to writing smaller values —my primitive math only cooperated

Re: feature requests: scalable \shape values; (stem) for \shapeII

Hello Jean, thanks for further exploring the first request. In my experience with Lilypond 2.20 \shape doesn’t scale with set-global-staff-size either. I’m already kinda “used” to writing smaller values —my primitive math only cooperated with me today to figure that I can use fractions to easil

feature requests: scalable \shape values; (stem) for \shapeII

Now that we’ve been talking about \shape and \shapeII, I would like to ask if it’s possible that values put for \shape(II) could scale according to staff size. Whenever I have a smaller staff, whatever values work for a 20 points staff are too much for smaller staves (either with a smaller font

feature requests: scalable \shape values; (stem) for \shapeII

Now that we’ve been talking about \shape and \shapeII, I would like to ask if it’s possible that values put for \shape(II) could scale according to staff size. Whenever I have a smaller staff, whatever values work for a 20 points staff are too much for smaller staves (either with a smaller font

Re: Feature Requests

Simon Albrecht writes: > On 23.10.2015 20:31, Bernardo Barros wrote: >> Something I requested many years ago was the support for quarter-tone >> tablatures notation, which seems to work but is actually buggy at the >> moment, it generates wrong tablatures in strings with quarter-tones >> alterati

Re: Feature Requests

On 24.10.2015 00:26, Simon Albrecht wrote: On 23.10.2015 20:31, Bernardo Barros wrote: Something I requested many years ago was the support for quarter-tone tablatures notation, which seems to work but is actually buggy at the moment, it generates wrong tablatures in strings with quarter-tones a

Feature Requests (was: Re: My finances for working on LilyPond)

done on LilyPond (as you can guess from the figures he sent), many other core developers having (largely or wholly) ceased to work on LilyPond. Third, feature requests aren’t quite as crucial in the motivation of a developer to take up a certain task. As has been said, even bounties lately tend to

Re: TabStaff feature requests

On Thu, Nov 25, 2010 at 1:34 PM, Jan Warchoł < lemniskata.bernoulli...@gmail.com> wrote: > 2010/11/25 Steve Yegge > >> I bit the bullet and went through all 100-odd guitar music publications >> I've >> collected over the years, from publishers around the world on every >> continent, >> across mul

Re: TabStaff feature requests

Am Freitag, 26. November 2010, um 11:08:36 schrieb Phil Holmes: > +1. I use a lot of choral scores, and I don't believe I've ever seen the > correct clef for tenors, which is a treble clef and octave down. Looking at my large collection of vocal scores, it appears that while most older scores

Re: TabStaff feature requests

t bother. -- Phil Holmes - Original Message - From: Jan Warchoł To: Steve Yegge Cc: lilypond-user Sent: Thursday, November 25, 2010 9:34 PM Subject: Re: TabStaff feature requests 2010/11/25 Steve Yegge I bit the bullet and went through all 100-odd guitar music publication

Re: TabStaff feature requests

On 26/11/10 08:34, Jan Warchoł wrote: 2010/11/25 Steve Yegge > I bit the bullet and went through all 100-odd guitar music publications I've collected over the years, from publishers around the world on every continent, across multiple genres (alt

Re: TabStaff feature requests

2010/11/25 Steve Yegge > > I bit the bullet and went through all 100-odd guitar music publications > I've > collected over the years, from publishers around the world on every > continent, > across multiple genres (although admittedly mostly classical and South > American). The set includes many

Re: TabStaff feature requests

On Wed, Nov 24, 2010 at 11:26 AM, Marc Hohl wrote: > >> Thanks; I'll try it. How do I turn off the little "8" symbol by the clef? >> > Why do you want to remove it? This is the standard way of guitar notation. > I bit the bullet and went through all 100-odd guitar music publications I've collec

Re: TabStaff feature requests

Am 24.11.2010 15:59, schrieb Steve Yegge: Hi Marc, On Tue, Nov 23, 2010 at 11:28 PM, Marc Hohl > wrote: Just for clarification: as the guitar is notated one octave above its sounding pitch, I use the following template: \score { \new StaffGroup <<

Re: TabStaff feature requests

Am 24.11.2010 17:16, schrieb Steve Yegge: Sigh... please disregard this. It works fine. I just had the wrong expectations. I assumed incorrectly that for purposes of relative pitch calculation, the harmonics would be ignored, allowing you to focus on the base string pitches. It has to be prop

Re: TabStaff feature requests

On 11/24/10 8:22 AM, "Steve Yegge" wrote: > On Wed, Nov 24, 2010 at 7:00 AM, Carl Sorensen wrote: >> On 11/24/10 7:51 AM, "Steve Yegge" wrote: >> After reading Marc's responses I think I see where I may have sewn some confusion.  I have conventional string numbers in the non-tab

Re: TabStaff feature requests

Sigh... please disregard this. It works fine. I just had the wrong expectations. I assumed incorrectly that for purposes of relative pitch calculation, the harmonics would be ignored, allowing you to focus on the base string pitches. It requires a bit more arithmetic this way, but it's logical

Re: TabStaff feature requests

Hi Marc, I've tried out your patch and it works like a charm! Unfortunately it seems to be happiest in absolute pitch mode. When I switch to relative mode it yields unexpected results. I've modified your harmonic-test.ly to demonstrate the issue. \include "./harmonic.ly" test = { e,4 \harmonic

Re: TabStaff feature requests

On Wed, Nov 24, 2010 at 7:00 AM, Carl Sorensen wrote: > On 11/24/10 7:51 AM, "Steve Yegge" wrote: > > > After reading Marc's responses I think I see where I may have > > sewn some confusion. I have conventional string numbers in the > > non-tab staff, since my audience is partly classical guita

Re: TabStaff feature requests

On 11/24/10 7:51 AM, "Steve Yegge" wrote: > After reading Marc's responses I think I see where I may have > sewn some confusion.  I have conventional string numbers in the > non-tab staff, since my audience is partly classical guitarists who > cannot (or do not) read tab.  So the information I'm

Re: TabStaff feature requests

Hi Marc, On Tue, Nov 23, 2010 at 11:28 PM, Marc Hohl wrote: > >> Just for clarification: as the guitar is notated one octave above its > sounding pitch, > I use the following template: > > \score { > \new StaffGroup << >\new Staff { > \new Voice { \global \clef "treble_8" >

Re: TabStaff feature requests

ople who want tabs, LilyPond makes it easy to add them. >> > >> > I've been busily adding tabs for a few months and have some feature >> > requests to put into the queue if possible. >> > >> > 1) Setting fixed strings to use for ascending/desc

Re: TabStaff feature requests

#x27;m not a big tab user myself, but for people who want tabs, LilyPond makes it easy to add them. I've been busily adding tabs for a few months and have some feature requests to put into the queue if possible. 1) Setting fixed strings to use for ascending/descending chords. Currently it'

Re: TabStaff feature requests

Am 24.11.2010 06:25, schrieb Steve Yegge: [...] \include "english.ly " music = \relative c { 1 } \score { << \new Staff { \music } \new TabStaff { \transpose c c, { \music } } >> } Just for clarification: as the guitar is notated one octave above i

Re: TabStaff feature requests

On Tue, Nov 23, 2010 at 12:39 AM, Marc Hohl wrote: > Am 23.11.2010 08:37, schrieb Steve Yegge: > >> Hi all, >> > Hi Steve, > >> >> 1) Setting fixed strings to use for ascending/descending chords. >> Currently it's nontrivial to specify tab positions for something like: >> >> >> >> >> [...

Re: TabStaff feature requests

, >> >> The TabStaff is amazingly cool. I'm not a big tab user myself, >> but for people who want tabs, LilyPond makes it easy to add them. >> >> I've been busily adding tabs for a few months and have some feature >> requests to

Re: TabStaff feature requests

dd them. > > > > I've been busily adding tabs for a few months and have some feature > > requests to put into the queue if possible. > > > > 1) Setting fixed strings to use for ascending/descending chords. > > Currently it's nontrivial to specify tab p

Re: TabStaff feature requests

On 11/23/10 12:37 AM, "Steve Yegge" wrote: > Hi all, > > The TabStaff is amazingly cool.  I'm not a big tab user myself, > but for people who want tabs, LilyPond makes it easy to add them. > > I've been busily adding tabs for a few months and have some fe

Re: TabStaff feature requests

May I append my feature request here? I would support this fix if anyone would be interested in fixing it! There is a bug in tablature when you choose a quarter tone scordatura, the pitches are not always represented correctly. ___ lilypond-user mailing

Re: TabStaff feature requests

Hi Steve, Am 23.11.2010 um 08:37 schrieb Steve Yegge: Hi all, The TabStaff is amazingly cool. I'm not a big tab user myself, but for people who want tabs, LilyPond makes it easy to add them. I've been busily adding tabs for a few months and have some feature requests to put into th

Re: TabStaff feature requests

Am 23.11.2010 08:37, schrieb Steve Yegge: Hi all, Hi Steve, The TabStaff is amazingly cool. I'm not a big tab user myself, but for people who want tabs, LilyPond makes it easy to add them. I've been busily adding tabs for a few months and have some feature requests to put into th

TabStaff feature requests

Hi all, The TabStaff is amazingly cool. I'm not a big tab user myself, but for people who want tabs, LilyPond makes it easy to add them. I've been busily adding tabs for a few months and have some feature requests to put into the queue if possible. 1) Setting fixed strings to use for

guitar tab feature requests

Hello, I have just read in the mailing archive about the plans (mainly encouraged by David Stocker) about expanding the features of lilypond concerning guitar tabs. I don't know how to code bendings and such in Scheme, but if someone is needed for testing, I will gladly join. I play and write m

Re: Feature requests

Horton are going to make some contributions to the docs about Vocal Music in a near future, that's why I'm researching more about lily's lyrics management. - Original Message - From: Jacob Cooper To: Cameron Horsburgh ; Eduardo Vieira ; Geoff Horton Sent: Saturday, April 1

Re: Feature requests

Jacob Cooper wrote: One hangup for me is lilypond's handling of lyrics. I don't care as much how they're entered as how they're output. Right now, it looks like syllables are aligned so that the left edge of the longest syllable (in polyphonic choral music) is aligned with the center of the note

Re: Feature requests

Jacob Cooper wrote: > I don't care as much how > they're entered as how they're output. Right now, it looks like syllables are > aligned so that the left edge of the longest syllable (in polyphonic choral > music) is aligned with the center of the note it's matched with, and in every > other part,

Re: Feature requests

Geoff Horton wrote: > I have seen some really odd things with this, as you note. The > (undocumented, as far as I know) \alignAboveContext property fixes it, > but I have a little trouble getting that to work consistently. > > Geoff > > > ___ > lilypo

Re: Feature requests

> One hangup for me is lilypond's handling of lyrics. I don't care as much how > they're entered as how they're output. Right now, it looks like syllables are > aligned so that the left edge of the longest syllable (in polyphonic choral > music) is aligned with the center of the note it's matched w

Feature requests

Hi there, First - thank you for a tremendous program! I've used it minimally so far, but I eagerly follow updates, and look forward to being able to use it more. One hangup for me is lilypond's handling of lyrics. I don't care as much how they're entered as how they're output. Right now, it looks