Re: Sponsored feature request--partially-tied chords, Thank You Han-Wen
On Thu, Aug 24, 2006 at 05:39:57PM +0200, Han-Wen Nienhuys wrote: Steve D wrote: After thinking about it for awhile, I agree with Werner and like his idea better also, if it can be done. [...] c~ e g bes~ would mean that only the c and b-flat would be tied c e g bes~ would mean that the whole chord would be tied c~ e g bes~~ would mean--well, LilyPond would issue an error message? The whole-chord tie would take precedence? ;-) After some thought, I agree with Werner (as usual), and I've changed the implementation to do this. Thank you so much Han-Wen for implementing this sponsored feature (chords in which some but not all notes are tied) and especially for being able to use Werner's clear and easy idea for notating a partially-tied chord. If you work on the issue where in dotted chords that contain an interval of a second, the dots can be too close to a following chord, discussed in the following thread-- http://lists.gnu.org/archive/html/lilypond-user/2006-08/msg00342.html please send the invoice to me and I'll pay for it promptly via PayPal. I'm also interested in sponsoring (preferably with one or more other interested people) work on cross-staff chords as has been discussed on this thread-- http://lists.gnu.org/archive/html/lilypond-user/2006-08/msg00379.html I believe that at this point Trevor Baca and I are both willing to co-sponsor it. (Right, Trevor?) Does anyone else wish to help sponsor cross-staff chords, which is an important feature but also a considerable project in terms of Han-Wen's time and attention. Once again, thank you very much Han-Wen, Steve Steve Doonan New Mexico US -- I am an old man and have known a great many troubles, but most of them never happened. -Mark Twain ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords, Thank You Han-Wen
On 8/28/06, Steve D [EMAIL PROTECTED] wrote: On Thu, Aug 24, 2006 at 05:39:57PM +0200, Han-Wen Nienhuys wrote: Steve D wrote: After thinking about it for awhile, I agree with Werner and like his idea better also, if it can be done. [...] c~ e g bes~ would mean that only the c and b-flat would be tied c e g bes~ would mean that the whole chord would be tied c~ e g bes~~ would mean--well, LilyPond would issue an error message? The whole-chord tie would take precedence? ;-) After some thought, I agree with Werner (as usual), and I've changed the implementation to do this. Thank you so much Han-Wen for implementing this sponsored feature (chords in which some but not all notes are tied) and especially for being able to use Werner's clear and easy idea for notating a partially-tied chord. If you work on the issue where in dotted chords that contain an interval of a second, the dots can be too close to a following chord, discussed in the following thread-- http://lists.gnu.org/archive/html/lilypond-user/2006-08/msg00342.html please send the invoice to me and I'll pay for it promptly via PayPal. I'm also interested in sponsoring (preferably with one or more other interested people) work on cross-staff chords as has been discussed on this thread-- http://lists.gnu.org/archive/html/lilypond-user/2006-08/msg00379.html I believe that at this point Trevor Baca and I are both willing to co-sponsor it. (Right, Trevor?) Yup. I'll split evenly with whoever else wants to help sponsor, like Steve. Does anyone else wish to help sponsor cross-staff chords, which is an important feature but also a considerable project in terms of Han-Wen's time and attention. Once again, thank you very much Han-Wen, Steve Steve Doonan New Mexico US -- I am an old man and have known a great many troubles, but most of them never happened. -Mark Twain ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- Trevor Bača [EMAIL PROTECTED] ... like the dew, or like lightning ... ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
On Thursday 24 August 2006 17:39, Han-Wen Nienhuys wrote: Steve D wrote: On Tue, Aug 22, 2006 at 10:55:05AM +0200, Han-Wen Nienhuys wrote: it's easiest to add a property so you can do c e \tweak #'forbid-tie = ##t g bes cost: 65 EUR. Werner LEMBERG then asked: Just wondering what the much simpler syntax c~ e~ g b~ costs... Han-Wen Nienhuys responded: I can put it in for 35 eur extra, I hope. (the tie engraver is quite tricky, and handling c~ e~ offers more potential for bugs) After thinking about it for awhile, I agree with Werner and like his idea better also, if it can be done. Aside from being clear and simple (to the end user), it can save a lot of typing, especially because when lots of partially-tied chords appear in a piece of music as the result of a rhythmic or other motive. SO-- c~ e g bes~ would mean that only the c and b-flat would be tied c e g bes~ would mean that the whole chord would be tied c~ e g bes~~ would mean--well, LilyPond would issue an error message? The whole-chord tie would take precedence? ;-) After some thought, I agree with Werner (as usual), and I've changed the implementation to do this. Erik, can you look over my use of stream events vs. events in tie-engraver.cc? I have the feeling that the dichotomy between both is a bit ugly, but is there currently another way? With my last patch (which I sent a few weeks ago but without response -- was it lost?), 'articulations is converted to a stream event list when music is converted to event. Also, music_cause is eliminated. Should I resend the patch? -- Erik ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
Erik Sandberg wrote: With my last patch (which I sent a few weeks ago but without response -- was it lost?), 'articulations is converted to a stream event list when music is converted to event. Also, music_cause is eliminated. Should I resend the patch? yes, I think I lost it in the din. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
SO-- c~ e g bes~ would mean that only the c and b-flat would be tied c e g bes~ would mean that the whole chord would be tied c~ e g bes~~ would mean--well, LilyPond would issue an error message? The whole-chord tie would take precedence? ;-) Werner, would you be willing to split the sponsorship of this feature with me 50%/50%? Yes, but it will take some time -- first, I'm just returning from a longer trip to Austria, and second, I don't have a Paypal account yet. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
Werner, would you be willing to split the sponsorship of this feature with me 50%/50%? Yes, but it will take some time -- first, I'm just returning from a longer trip to Austria, and second, I don't have a Paypal account yet. Obviously, this is now obsolete -- pfffew :-) Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
On Friday 25 August 2006 11:45, Han-Wen Nienhuys wrote: Erik Sandberg wrote: With my last patch (which I sent a few weeks ago but without response -- was it lost?), 'articulations is converted to a stream event list when music is converted to event. Also, music_cause is eliminated. Should I resend the patch? yes, I think I lost it in the din. It's attached. This is a copy of the last patch, it's not a patch against the newest lily. === The attached patch makes a couple of further cleanups: - eliminate Grob_info::ultimate_music_cause, Grob_info::music_cause - possible bugfix in figured-bass-engraver: never decrement stop_moment - kill all remaining music refs in engravers; remove music.hh include from engraver.hh - use ASSIGN_EVENT_ONCE in engravers where appropriate - junk try_music in Translator, Translator_group, Context, Context_handle - small cleanup in part-combine-iterator; use an enum to distinguish between the outlet contexts. The only remaining part of the translator cleanup is, AFAIK, to remove obsolete translators. -- Erik es-060802-final-cleanups.diff.bz2 Description: BZip2 compressed data ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
Steve D wrote: On Tue, Aug 22, 2006 at 10:55:05AM +0200, Han-Wen Nienhuys wrote: it's easiest to add a property so you can do c e \tweak #'forbid-tie = ##t g bes cost: 65 EUR. Werner LEMBERG then asked: Just wondering what the much simpler syntax c~ e~ g b~ costs... Han-Wen Nienhuys responded: I can put it in for 35 eur extra, I hope. (the tie engraver is quite tricky, and handling c~ e~ offers more potential for bugs) After thinking about it for awhile, I agree with Werner and like his idea better also, if it can be done. Aside from being clear and simple (to the end user), it can save a lot of typing, especially because when lots of partially-tied chords appear in a piece of music as the result of a rhythmic or other motive. SO-- c~ e g bes~ would mean that only the c and b-flat would be tied c e g bes~ would mean that the whole chord would be tied c~ e g bes~~ would mean--well, LilyPond would issue an error message? The whole-chord tie would take precedence? ;-) After some thought, I agree with Werner (as usual), and I've changed the implementation to do this. Erik, can you look over my use of stream events vs. events in tie-engraver.cc? I have the feeling that the dichotomy between both is a bit ugly, but is there currently another way? -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
On Tue, Aug 22, 2006 at 10:55:05AM +0200, Han-Wen Nienhuys wrote: it's easiest to add a property so you can do c e \tweak #'forbid-tie = ##t g bes cost: 65 EUR. Werner LEMBERG then asked: Just wondering what the much simpler syntax c~ e~ g b~ costs... Han-Wen Nienhuys responded: I can put it in for 35 eur extra, I hope. (the tie engraver is quite tricky, and handling c~ e~ offers more potential for bugs) After thinking about it for awhile, I agree with Werner and like his idea better also, if it can be done. Aside from being clear and simple (to the end user), it can save a lot of typing, especially because when lots of partially-tied chords appear in a piece of music as the result of a rhythmic or other motive. SO-- c~ e g bes~ would mean that only the c and b-flat would be tied c e g bes~ would mean that the whole chord would be tied c~ e g bes~~ would mean--well, LilyPond would issue an error message? The whole-chord tie would take precedence? ;-) Werner, would you be willing to split the sponsorship of this feature with me 50%/50%? I'll commit to its sponsorship, if Han-Wen approves, right now. Steve Steve Doonan New Mexico, US http://www.xscd.com/pub/ -- Good judgement comes from experience. Unfortunately, the experience usually comes from bad judgement. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
Werner LEMBERG wrote: it's easiest to add a property so you can do c e \tweak #'forbid-tie = ##t g bes cost: 65 EUR. Just wondering what the much simpler syntax c~ e~ g b~ costs... I can put it in for 35 eur extra, I hope. (the tie engraver is quite tricky, and handling c~ e~ offers more potential for bugs) -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
On Tue, Aug 22, 2006 at 10:55:05AM +0200, Han-Wen Nienhuys wrote: Werner LEMBERG wrote: it's easiest to add a property so you can do c e \tweak #'forbid-tie = ##t g bes cost: 65 EUR. Just wondering what the much simpler syntax c~ e~ g b~ costs... I can put it in for 35 eur extra, I hope. (the tie engraver is quite tricky, and handling c~ e~ offers more potential for bugs) I like Werner's simpler suggestion also, but I am willing to sponsor whatever you think will work best and integrate best into LilyPond. Thank you Han-Wen, Steve S. Doonan New Mexico US ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
Steve D wrote: Trevor Baca recently asked how one might write in LilyPond tied chords in which only *some* (one or more, but not all) notes are tied to the following identical chord. I am also interested in this, because it sometimes happens in piano music, and I would be interested in sponsoring a feature in LilyPond which one could use to prevent one or more notes within a chord from being tied. At any rate, if Han-Wen thinks this is worthy of some thought and effort, I would be happy to sponsor such a user-specified selective exclusion of notes or partially tied chord feature. it's easiest to add a property so you can do c e \tweak #'forbid-tie = ##t g bes cost: 65 EUR. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
On Mon, Aug 21, 2006 at 12:57:51PM +0200, Han-Wen Nienhuys wrote: Steve D wrote: Trevor Baca recently asked how one might write in LilyPond tied chords in which only *some* (one or more, but not all) notes are tied to the following identical chord. I am also interested in this, because it sometimes happens in piano music, and I would be interested in sponsoring a feature in LilyPond which one could use to prevent one or more notes within a chord from being tied. At any rate, if Han-Wen thinks this is worthy of some thought and effort, I would be happy to sponsor such a user-specified selective exclusion of notes or partially tied chord feature. it's easiest to add a property so you can do c e \tweak #'forbid-tie = ##t g bes cost: 65 EUR. Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com That sounds good to me, Han-Wen. The \tweak would affect only the note immediately after it, right? (like \once \override ?) If a piece has lots of partially tied chords, a person could define a macro at the top of his or her piece to diminish the amount of typing: \notie = \tweak #'forbid-tie = ##t c \notie e \notie g bes4~ c e g bes I will be happy to sponsor this. I can pay now via PayPal or later after the invoice. Thank you, Steve -- The difference between a violin and a viola is that a viola burns longer. -Victor Borge ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
It might be nice to be able to write something like: c e\noTie g\noTie bes4~ c e g bes Hmm, much to type. What about the opposite: c~ e g bes~4 c e g bes This looks most natural to me. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Sponsored feature request--partially-tied chords
On Sun, Aug 20, 2006 at 12:39:56PM +0200, Werner LEMBERG wrote: It might be nice to be able to write something like: c e\noTie g\noTie bes4~ c e g bes Hmm, much to type. What about the opposite: c~ e g bes~4 c e g bes This looks most natural to me. Werner Whatever seems better to Han-Wen and the developers. The reason I used the exclusion rather than inclusion approach (which notes of an otherwise tied chord should *not* be tied, instead of which notes of an otherwise untied chord *should* be tied) in my example, was because I thought someone might write the ambiguous-- c~ e g bes~4~ --but your example looks fine to me too. I merely suggested the functionality, and trust that Han-Wen and the developers with their knowledge of the logic and design principles of LilyPond would best know how to include such functionality. Steve ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Sponsored feature request--partially-tied chords
Trevor Baca recently asked how one might write in LilyPond tied chords in which only *some* (one or more, but not all) notes are tied to the following identical chord. I am also interested in this, because it sometimes happens in piano music, and I would be interested in sponsoring a feature in LilyPond which one could use to prevent one or more notes within a chord from being tied. For example, consider a C 7 chord tied to another C 7: c e g bes4~ c e g bes In piano music (and perhaps other polyphonic instruments) a chord can be played in such a way that some notes are sustained (tied) and some are sounded or repeated. Someone might notate a piece in which the c and b-flat of the above chord are held, while the e and g are struck in the second and subsequent identical chords. It might be nice to be able to write something like: c e\noTie g\noTie bes4~ c e g bes At any rate, if Han-Wen thinks this is worthy of some thought and effort, I would be happy to sponsor such a user-specified selective exclusion of notes or partially tied chord feature. Steve Doonan New Mexico US -- Nearly all men can stand adversity, but if you want to test a man's character, give him power. -Abraham Lincoln ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
