Re: Is Anyone Working on a Better Tablature Algorithm?
David Kastrup wrote > christopher-heckman < > ccheckman@ > > writes: > >> David Kastrup wrote >>> >>> Personally I think there should be a _translator_ doing the string/fret >>> assignment and recording it into the music expression. >>> >>> Why? >>> >>> This translator can keep context and, for example, default to using the >>> identical assignment for repeated chords, continued _notes_ and similar. >> >> I strongly disagree with you on this. > > The following rather sounds like you strongly disagree with something > else. No idea what. You're saying the fingering should be the same every time you play a certain chord. Or at least that's what your email is saying. THAT is what I am disagreeing to. --- Christopher Heckman -- View this message in context: http://lilypond.1069038.n5.nabble.com/Is-Anyone-Working-on-a-Better-Tablature-Algorithm-tp196422p196472.html Sent from the Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Stepping down and moving on
David, thank you for all your work and good luck with the new job! Can you share the name of the company and what you will be working on? All the best, Janek 2016-11-09 9:09 GMT-08:00 David Kastrup : > > Hi folks and team, > > while I haven't really occupied an official function in LilyPond > development, it's hard to deny that I have effectively functioned as > acting chief architect and vetter (with a rather mottled performance). > > Partly in connection with a drop of my productivity particularly this > year, the amount of financial support for my work from members of the > LilyPond community went down from overall survivable to disastrous. Of > course this is bitter for those of you that did contribute in > significant amounts to my subsistence but I have to be moving on. > > I have accepted a full-time development (and team management) position > with another company. Due to their project and team expansion plans, > I will be starting already in December. > > This employment is in another city. I'll be travelling back and forth > weekly for the foreseeable future. While I might be working on some > LilyPond side projects interesting to me occasionally, I will not be > able to do any serious amound of coordination or other activity > involving me with LilyPond's community. > > As my communication style has proven to be a somewhat mixed blessing for > the purpose of attracting long-term developers, I expect that this may > help in the long run for finding a different balance of areas LilyPond > is getting worked on. > > During his tenure as LilyPond leader, Graham has demonstrated that even > without a central technical lead there is a lot of potential to focus > the resources of people willing to work on and expand LilyPond and we > have been continuing to reap the results of his talent for organizing > people into useful teams even though I have not really figured out how > to fill gaps in the various teams and tools managing LilyPond's > infrastructure to offset the "natural" amounts of fluctuation. > > I'll try seeing through the release of 2.20 in the little time remaining > to me both before and after starting my job. My main worry is the > current comparative amount of instability with regard to font handling, > and my main bad taste is that 2.20.1 will not be able to support > Guile 2: there is no way that anything deserving the label of "stable" > and including Guile 2 will come about in the rest of my tenure. > > There are also several half-completed features that are a nuisance. > I do not expect to be able to to a significant amount of work on them in > the foreseeable future. > > Once consequence, of course, is that my requirement for funding is over. > I am greatly thankful to the people who have enabled me to keep working > on LilyPond as long as I did, but what remains in my bank account, in > spite of being quite less than what I started with when working on > LilyPond, is sufficient to tide me over the time to my first paycheck. > > So I would ask you to cancel any regular bank payments you might still > have in place as of December: I don't see that I will have a reasonable > chance at returning a tangible value for them. > > Thanks for making me stay in the pond as long as I did! > > -- > David Kastrup > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Is Anyone Working on a Better Tablature Algorithm?
christopher-heckman writes: > David Kastrup wrote >> christopher-heckman < > >> ccheckman@ > >> > writes: >> >>> In the past few years, a couple of algorithms have been released which >>> do a better job for tablature. Since Lilypond uses one of the most >>> naïve ones (not much different from the one that TuxGuitar uses), it >>> might be time for an update. >>> >>> Is anyone working on this? I haven't been able to find any information >>> on current projects. >> >> Personally I think there should be a _translator_ doing the string/fret >> assignment and recording it into the music expression. >> >> Why? >> >> This translator can keep context and, for example, default to using the >> identical assignment for repeated chords, continued _notes_ and similar. > > I strongly disagree with you on this. The following rather sounds like you strongly disagree with something else. No idea what. > If you are playing the guitar, especially if you are playing passages > with lots of notes, you may not always want to go to the same > fingering for the chord. There are cases where you would have to shift > your hand position by 5 or 10 frets, play one chord, and move > back. This is not idea. > > >> It can also be employed at TabStaff level (rather than at TabVoice >> level) in order to create a workable assignment for polyphonic >> guitar/lute play. > > The algorithm I have in mind does work for polyphony, so it can be > used at the staff level. (And that would be how I would design it: for > the entire piece.) I thought you strongly disagreed with keeping context, like "the entire piece"? > It would accept a musical expression and then add the string (and > fingering) information to the notes. Some disagreement that is... >> So with a bit of retooling, one end up with a more versatile set of >> modular tools than what we have now. > > Which begs the question that I started off with: Is anyone working on > this? Not that I know of. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Is Anyone Working on a Better Tablature Algorithm?
David Kastrup wrote > christopher-heckman < > ccheckman@ > > writes: > >> In the past few years, a couple of algorithms have been released which >> do a better job for tablature. Since Lilypond uses one of the most >> naïve ones (not much different from the one that TuxGuitar uses), it >> might be time for an update. >> >> Is anyone working on this? I haven't been able to find any information >> on current projects. > > Personally I think there should be a _translator_ doing the string/fret > assignment and recording it into the music expression. > > Why? > > This translator can keep context and, for example, default to using the > identical assignment for repeated chords, continued _notes_ and similar. I strongly disagree with you on this. If you are playing the guitar, especially if you are playing passages with lots of notes, you may not always want to go to the same fingering for the chord. There are cases where you would have to shift your hand position by 5 or 10 frets, play one chord, and move back. This is not idea. > It can also be employed at TabStaff level (rather than at TabVoice > level) in order to create a workable assignment for polyphonic > guitar/lute play. The algorithm I have in mind does work for polyphony, so it can be used at the staff level. (And that would be how I would design it: for the entire piece.) It would accept a musical expression and then add the string (and fingering) information to the notes. > The output of the translator would obviously be also usable for > fretboard diagrams and similar. You're thinking of chords here, and I'm thinking of melodies/riffs. In that case, fretboard diagrams really don't help. > A "reverse" translator (quite simpler) could optionally translate > string/fret to note pitch. > > The advantage of that would be that people could enter information in > tablature (namely as string/fret pairs) and manage to create tablature > as well as notes from it. Currently you are restricted to entering > stuff as notes. Someone could work on that. It would be much easier than figuring out the finger positions. > Some combination could even be used for letting people enter music in > tablature. > > So with a bit of retooling, one end up with a more versatile set of > modular tools than what we have now. Which begs the question that I started off with: Is anyone working on this? We shouldn't have half a dozen people working on the same improvement independently; you will get half a dozen different pieces of code, all inconsistent. (And if one of them works for Microsoft, you may get eight or nine.) --- Christopher Heckman -- View this message in context: http://lilypond.1069038.n5.nabble.com/Is-Anyone-Working-on-a-Better-Tablature-Algorithm-tp196422p196466.html Sent from the Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Stepping down and moving on
Dear David, I have nothing to add to what others have written here. But I want to repeat it from my side: Thank you so much for your work on LilyPond! Thank you for new functionality, for cleaner code, for easier input syntax, for leading discussions with insightful contributions and LilyPond facts and for the help for so many on this list! I was kind of shocked when I read the mail subject from your address. But I am convinced that it is a good decision for your finances and your future - I feared it would happen earlier. I wish you a good start in your new position. Hopefully, we will see you from time to time on these lists. Cordially, Joram ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Is Anyone Working on a Better Tablature Algorithm?
christopher-heckman writes: > In the past few years, a couple of algorithms have been released which > do a better job for tablature. Since Lilypond uses one of the most > naïve ones (not much different from the one that TuxGuitar uses), it > might be time for an update. > > Is anyone working on this? I haven't been able to find any information > on current projects. Personally I think there should be a _translator_ doing the string/fret assignment and recording it into the music expression. Why? This translator can keep context and, for example, default to using the identical assignment for repeated chords, continued _notes_ and similar. It can also be employed at TabStaff level (rather than at TabVoice level) in order to create a workable assignment for polyphonic guitar/lute play. The output of the translator would obviously be also usable for fretboard diagrams and similar. A "reverse" translator (quite simpler) could optionally translate string/fret to note pitch. The advantage of that would be that people could enter information in tablature (namely as string/fret pairs) and manage to create tablature as well as notes from it. Currently you are restricted to entering stuff as notes. Some combination could even be used for letting people enter music in tablature. So with a bit of retooling, one end up with a more versatile set of modular tools than what we have now. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Is Anyone Working on a Better Tablature Algorithm?
In the past few years, a couple of algorithms have been released which do a better job for tablature. Since Lilypond uses one of the most naïve ones (not much different from the one that TuxGuitar uses), it might be time for an update. Is anyone working on this? I haven't been able to find any information on current projects. --- Christopher Heckman -- View this message in context: http://lilypond.1069038.n5.nabble.com/Is-Anyone-Working-on-a-Better-Tablature-Algorithm-tp196422.html Sent from the Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Stepping down and moving on
+1 many times over. Thank you for your excellent, creative, and vital work in helping LilyPond become the world’s best and most stable digital music engraver. Best of luck! ~Mike On 10 November 2016 at 13.23.24, Kieren MacMillan (kieren_macmil...@sympatico.ca) wrote: Dear David, Congratulations on the new position! I hope it brings you great personal satisfaction and financial security. Your programming and code-shepherding efforts in the ‘Pond have been nearly miraculous, and the codebase is immeasurably better for you having been on the team. Thank you so much for everything you did to make Lilypond better for everyone, users and developers alike. Sincerely, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-user mailing list lilypond-u...@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Stepping down and moving on
Dear David, Congratulations on the new position! I hope it brings you great personal satisfaction and financial security. Your programming and code-shepherding efforts in the ‘Pond have been nearly miraculous, and the codebase is immeasurably better for you having been on the team. Thank you so much for everything you did to make Lilypond better for everyone, users and developers alike. Sincerely, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.info ‣ email: i...@kierenmacmillan.info ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Stepping down and moving on
2016-11-10 11:46 GMT+01:00 Andrew Bernard : > David, > > I wish you all the very best for your future endeavours. I thank you most > sincerely for your immensely significant and important contribution to > making lilypond the exceptional tool for engraving that it is. Having tried > myself to study the source code and remaining baffled despite decades of > software development experience, I am in awe at your ability to comprehend > and extend this complex code base, for the benefit of us all. It will be > difficult if not impossible for anybody to fill your shoes. I extend my > immense gratitude to you for your tireless pursuit of software excellence. > > All the best from Down Under! > > Andrew Bernard ... and all the same from me, Pal ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Stepping down and moving on
David, I wish you all the very best for your future endeavours. I thank you most sincerely for your immensely significant and important contribution to making lilypond the exceptional tool for engraving that it is. Having tried myself to study the source code and remaining baffled despite decades of software development experience, I am in awe at your ability to comprehend and extend this complex code base, for the benefit of us all. It will be difficult if not impossible for anybody to fill your shoes. I extend my immense gratitude to you for your tireless pursuit of software excellence. All the best from Down Under! Andrew Bernard On 10 November 2016 at 04:09, David Kastrup wrote: > > Hi folks and team, > > while I haven't really occupied an official function in LilyPond > development, it's hard to deny that I have effectively functioned as > acting chief architect and vetter (with a rather mottled performance). > > Partly in connection with a drop of my productivity particularly this > year, the amount of financial support for my work from members of the > LilyPond community went down from overall survivable to disastrous. Of > course this is bitter for those of you that did contribute in > significant amounts to my subsistence but I have to be moving on. > > I have accepted a full-time development (and team management) position > with another company. Due to their project and team expansion plans, > I will be starting already in December. > > This employment is in another city. I'll be travelling back and forth > weekly for the foreseeable future. While I might be working on some > LilyPond side projects interesting to me occasionally, I will not be > able to do any serious amound of coordination or other activity > involving me with LilyPond's community. > > As my communication style has proven to be a somewhat mixed blessing for > the purpose of attracting long-term developers, I expect that this may > help in the long run for finding a different balance of areas LilyPond > is getting worked on. > > During his tenure as LilyPond leader, Graham has demonstrated that even > without a central technical lead there is a lot of potential to focus > the resources of people willing to work on and expand LilyPond and we > have been continuing to reap the results of his talent for organizing > people into useful teams even though I have not really figured out how > to fill gaps in the various teams and tools managing LilyPond's > infrastructure to offset the "natural" amounts of fluctuation. > > I'll try seeing through the release of 2.20 in the little time remaining > to me both before and after starting my job. My main worry is the > current comparative amount of instability with regard to font handling, > and my main bad taste is that 2.20.1 will not be able to support > Guile 2: there is no way that anything deserving the label of "stable" > and including Guile 2 will come about in the rest of my tenure. > > There are also several half-completed features that are a nuisance. > I do not expect to be able to to a significant amount of work on them in > the foreseeable future. > > Once consequence, of course, is that my requirement for funding is over. > I am greatly thankful to the people who have enabled me to keep working > on LilyPond as long as I did, but what remains in my bank account, in > spite of being quite less than what I started with when working on > LilyPond, is sufficient to tide me over the time to my first paycheck. > > So I would ask you to cancel any regular bank payments you might still > have in place as of December: I don't see that I will have a reasonable > chance at returning a tangible value for them. > > Thanks for making me stay in the pond as long as I did! > > -- > David Kastrup > > ___ > lilypond-user mailing list > lilypond-u...@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Stepping down and moving on
Hi David, Thank you for your hard work et nice helps. My very best wishes for the future. Cheers, Pierre 2016-11-10 8:58 GMT+01:00 Federico Bruni : > Il giorno mer 9 nov 2016 alle 18:09, David Kastrup ha > scritto: > >> Thanks for making me stay in the pond as long as I did! >> > > Thanks to you David for the great work you made for LilyPond! > We'll miss you. > > Best > Federico > > > > ___ > lilypond-user mailing list > lilypond-u...@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
