[Top][All Lists]

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

Re: Bug in ties over barlines

From: Alexander Kobel
Subject: Re: Bug in ties over barlines
Date: Mon, 31 Jan 2011 22:16:10 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7

On 2011-01-31 21:06, James Lowe wrote:
> -----Original Message-----
> From: Alexander Kobel <address@hidden>
>> By the way: if you have  { r2.. cis8( | c2!) r2 }  all over the place,
>> and then there suddenly comes a  { r2 cis2~ | cis2 r2 }, you'd expect an
>> additional sharp there too, don't you?
> Hmm...why not use (in your example) { r2.. cis8( | c2?) r2 } which to me
> makes more sense. [...]
> No one (as I can see) has spoken about the ? Vs ! And I think that's the
> difference for me. It depends on what is already sharp/flat in the key
> signature as a musician. ! Means it isn't and ? Means it is but 'be aware'
> right?

Ah, good point. I didn't actually think about the ? vs. ! difference;
probably it's just a matter of personal taste of the engraver.  In this
situation, I guess both can be reasoned: the cautionary since the key
signature says it should be c by default anyway, and the mandatory
accidental (without parentheses) because tie and slur could not be
distinguished otherwise, so it's indeed at least semi-mandatory.
But IMHO the important point here is the fact that the notation can be
ambigous without the accidental, and is definitely clear with it.  No
matter if ? or !.


reply via email to

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