[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: shortened Hairpin hack; how to get "width" of current ChordEvent?

From: Anthony Youngman
Subject: RE: shortened Hairpin hack; how to get "width" of current ChordEvent?
Date: Tue, 6 Jun 2006 12:49:48 +0100

Your second method is the method I'm planning to switch to with
(de)crescendi, but it's no use with glissandi which I also need! The
problem is s doesn't have a note value attached to tie the glissando end
to (unless we can add it, like you can do with rests...).

Your idea of putting a notelength after the > or whatever is also a very
neat idea, but again doesn't solve the glissando problem ...

If you can come up with a good idea of how to attach any generic "link
two notes together" notation such that we can hang it off just one note,
I think it'll go down well (just remember, some of them need a nominal
pitch to hang onto, even if there's no note there).


-----Original Message-----
From: Kieren MacMillan [mailto:address@hidden 
Sent: 06 June 2006 11:52
To: Anthony Youngman
Cc: address@hidden
Subject: Re: shortened Hairpin hack; how to get "width" of current

Hi, Anthony:

>       {g1}
>       {s2\> s4\! s}

Yeah, that's the messiness I'm trying to avoid!  =)

My second method was

     g1*7/8\> s1*1/8\!

which is messy in different ways (though less messy overall,  
perhaps?). I prefer the former method for the fact that it doesn't  
mess with the "virtual durations" in any way, but I like the latter  
because it doesn't spawn an extra Voice just to deal with a visual/ 
formatting construct.

I guess I just think it should be easier/cleaner, somehow, to stop an  
event (e.g., a spanner) partway through another event. Don't get me  
wrong -- it's not that I think it's easy to come up with a syntax  
that covers all (or even nearly all) possibilities, never mind the  
code to parse it. Just brainstorming it as I type here, I suppose a  
syntax like


for a whole note g with a half-note length decrescendo might be very  
nice. Then

     g1\> g\!

would act as it always has, and

     g1\>{4 2}

would give a hairpin starting one quarter note after the main note  
and having a duration of a half-note.

I have no idea how complicated all that would be (for the programming  
side of it), but I always go by the principle that it's usually  
better to sacrifice complexity on the code (programmer's) side in  
order to simplify things from the input (user's) perspective.

Maybe the new MusicStream approach will offer some assistance here?

Anyway, just thinking out loud, really...  =)


* ************************************************************************ *

This transmission is intended for the named recipient only. It may contain 
private and confidential information. If this has come to you in error you must 
not act on anything disclosed in it, nor must you copy it, modify it, 
disseminate it in any way, or show it to anyone. Please e-mail the sender to 
inform us of the transmission error or telephone ECA International immediately 
and delete the e-mail from your information system.

Telephone numbers for ECA International offices are: Sydney +61 (0)2 8272 5300, 
Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 

* ************************************************************************ *

reply via email to

[Prev in Thread] Current Thread [Next in Thread]