Re: Contemporary music required feature #1: chromatic transposition

2009-09-25 Thread Hans Aberg
On 25 Sep 2009, at 07:11, Joseph Wakeling wrote: Joe, can you come up with a short description and a minimal example, so Valentin can add it to the tracker? Will do. Sorry for not replying earlier to your kind offer of help -- I'm going through a bit of a busy patch -- but will get to work

Re: Contemporary music required feature #1: chromatic transposition

2009-09-24 Thread Joseph Wakeling
Carl Sorensen wrote: > Joe, can you come up with a short description and a minimal example, so > Valentin can add it to the tracker? Will do. Sorry for not replying earlier to your kind offer of help -- I'm going through a bit of a busy patch -- but will get to work on this ASAP. :-) Best wishe

Re: Contemporary music required feature #1: chromatic transposition

2009-09-24 Thread Carl Sorensen
On 9/24/09 1:29 PM, "Valentin Villenave" wrote: > On Tue, Sep 22, 2009 at 3:00 PM, Carl Sorensen wrote: >> If you get the chromatic transposition working properly, I'll commit to >> helping you get it embedded in LilyPond. > > Carl, please consider yourself my personal beacon of light in suc

Re: Contemporary music required feature #1: chromatic transposition

2009-09-24 Thread Valentin Villenave
On Tue, Sep 22, 2009 at 3:00 PM, Carl Sorensen wrote: > If you get the chromatic transposition working properly, I'll commit to > helping you get it embedded in LilyPond. Carl, please consider yourself my personal beacon of light in such discussions :-) Could you give me a hint as to whether thi

Re: Contemporary music required feature #1: chromatic transposition

2009-09-22 Thread Hans Aberg
On 22 Sep 2009, at 15:00, Carl Sorensen wrote: If you get the chromatic transposition working properly, I'll commit to helping you get it embedded in LilyPond. My impression is that this works properly, only that LilyPond does not have the capacity to treat # and b as operators that can be

Re: Contemporary music required feature #1: chromatic transposition

2009-09-22 Thread Carl Sorensen
On 9/21/09 5:09 PM, "Joseph Wakeling" wrote: > As I mentioned a little while back, I'm working on a specialist notation > section on contemporary music for the Notation Reference. And, as I > also mentioned, I'm going to be trying to implement and/or motivate some > feature development to sup

Re: Contemporary music required feature #1: chromatic transposition

2009-09-22 Thread Hans Aberg
On 22 Sep 2009, at 13:44, Joseph Wakeling wrote: So I think you need to add a choice of glyph. LilyPond is too primitive to treat # and b and other accidentals as operators acting on all intervals. Well, the point is that a glyph for 5/4 sharp is nonsensical. A contemporary music player wou

Re: Contemporary music required feature #1: chromatic transposition

2009-09-22 Thread Joseph Wakeling
Hans Aberg wrote: > I think LilyPond, once it has found the correct scale degree, computes > the interval offset. As there is none for this particular offset, it > typesets nothing. It should report at least a warning, though. The value > stored inside should though be correct. Yes, I think this i

Re: Contemporary music required feature #1: chromatic transposition

2009-09-22 Thread Hans Aberg
On 22 Sep 2009, at 11:49, Joseph Wakeling wrote: The correct accidental is a # plus a !/4. It then does not change the scale degree. This will also be correct in if the sharp and microtonal accents are relative a tuning system other than E12. No, it's a DOUBLE-sharp plus a 1/4, ... Yes, s

Re: Contemporary music required feature #1: chromatic transposition

2009-09-22 Thread Joseph Wakeling
Hans Aberg wrote: > The correct accidental is a # plus a !/4. It then does not change the > scale degree. This will also be correct in if the sharp and microtonal > accents are relative a tuning system other than E12. No, it's a DOUBLE-sharp plus a 1/4, which quite obviously does not exist. > In

Re: Contemporary music required feature #1: chromatic transposition

2009-09-22 Thread Hans Aberg
On 22 Sep 2009, at 11:16, Joseph Wakeling wrote: Hans Aberg wrote: What you see is that (i) without naturalizeMusic, transposition fails: transposition alone leaves the final pitch being 'g+5/4' which has no accidental I think is just a bug. Somehow the sharp drops out. It's not

Re: Contemporary music required feature #1: chromatic transposition

2009-09-22 Thread Joseph Wakeling
Hans Aberg wrote: >> What you see is that >> >> (i) without naturalizeMusic, transposition fails: transposition alone >> leaves the final pitch being 'g+5/4' which has no accidental > > I think is just a bug. Somehow the sharp drops out. It's not so much a bug as a notational impossibilit

Re: Contemporary music required feature #1: chromatic transposition

2009-09-22 Thread Hans Aberg
On 22 Sep 2009, at 01:09, Joseph Wakeling wrote: Currently Lilypond's transposition is tonal only, with the 'smart transpose' snippet providing a Scheme function to minimise accidental use. Unfortunately this function is incompatible with quarter-tone notation. Discussing with Graham Breed, I

Re: Contemporary music required feature #1: chromatic transposition

2009-09-21 Thread Joseph Wakeling
Joseph Wakeling wrote: > Currently Lilypond's transposition is tonal only, with the 'smart > transpose' snippet providing a Scheme function to minimise accidental > use. Unfortunately this function is incompatible with quarter-tone > notation. The attached snippet shows the problem. A quarter-to

Contemporary music required feature #1: chromatic transposition

2009-09-21 Thread Joseph Wakeling
Hello all, As I mentioned a little while back, I'm working on a specialist notation section on contemporary music for the Notation Reference. And, as I also mentioned, I'm going to be trying to implement and/or motivate some feature development to support this. The first feature I'm looking to g