[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>
From: |
Wols Lists |
Subject: |
Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>> |
Date: |
Sat, 5 Jan 2019 10:40:32 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 |
On 04/01/19 18:41, Aaron Hill wrote:
>
>> Yeesh, that is terrible.This is why it's important to follow good
>> notation
>> practice: I was so confused by this bad typesetting that I thought the
>> bar
>> was 6/4 time, and now my day is ruined.
>
> Unless someone is doing academic work where it is critical for the
> typesetting to precisely match that of a reference work, all new
> typesetting ideally should follow the current wisdom of notation. There
> is little reason to continue to propagate archaic and non-standard
> practices, especially if they are more likely to cause confusion.
This is exactly what I *H*A*T*E* about people who proclaim "This is
correct".
Take my case - which would you choose between "follow the current
wisdom" and "music that is readable (and hence playable)". Note that
this *IS* an either/or choice! How often have I moaned on this list
because I need to over-ride lily's defaults because the result is
otherwise pretty much unplayable ...
I make no comment about the current piece being discussed - it sounds
like it's incomprehensible to orchestral musicians, but why should
everybody be forced to speak "orchestra"? We don't all speak English, or
write in the Latin script!
Cheers,
Wol
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, (continued)
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Gianmaria Lari, 2019/01/04
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Thomas Morley, 2019/01/04
- Re: Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Mats Bengtsson, 2019/01/04
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Heikki Tauriainen, 2019/01/04
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Gianmaria Lari, 2019/01/04
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Gianmaria Lari, 2019/01/04
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Thomas Morley, 2019/01/04
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Gianmaria Lari, 2019/01/04
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, N. Andrew Walsh, 2019/01/04
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Aaron Hill, 2019/01/04
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>,
Wols Lists <=
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Aaron Hill, 2019/01/05
- RE: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Mark Stephen Mrotek, 2019/01/05
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Wols Lists, 2019/01/05
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Kieren MacMillan, 2019/01/05
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Aaron Hill, 2019/01/05
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Wols Lists, 2019/01/05
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Aaron Hill, 2019/01/05
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Wols Lists, 2019/01/05
- Re: <<aes,2. \\ {s4 ees2} \\ {s2 bes4}>>, Karlin High, 2019/01/05