[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fixed vs relative
From: |
Urs Liska |
Subject: |
Re: fixed vs relative |
Date: |
Thu, 09 May 2019 22:27:05 +0200 |
User-agent: |
K-9 Mail for Android |
Am 9. Mai 2019 21:52:49 MESZ schrieb David Kastrup <address@hidden>:
>David Wright <address@hidden> writes:
>
>> one note has a dramatic effect on the following music, but is easily
>> corrected with one tick. When this trick has been applied, many notes
>> may have to be individually tickled after the mistake is discovered.
>
>I was of the opinion that Frescobaldi can transpose regions. That
>should be usable for octave-shifting, shouldn't it?
Yes, but it can quickly become cumbersome. The function works upon a selection
in the document. I'd say that chances are that once you're in need of
correction after the fact you may not have a continuous section with the same
error. What about mis-octavized chord notes for example? They might well be
wrongnkn different ways.
.Urs
- fixed vs relative, Gianmaria Lari, 2019/05/09
- Re: fixed vs relative, David Kastrup, 2019/05/09
- Re: fixed vs relative, Urs Liska, 2019/05/09
- Re: fixed vs relative, Gianmaria Lari, 2019/05/09
- Re: fixed vs relative, David Wright, 2019/05/09
- Re: fixed vs relative, Gianmaria Lari, 2019/05/09
- Re: fixed vs relative, Urs Liska, 2019/05/09
- Re: fixed vs relative, David Wright, 2019/05/09
- python3-ly WAS Re: fixed vs relative, Andrew Bernard, 2019/05/09
- Re: fixed vs relative, Urs Liska, 2019/05/10
Re: fixed vs relative, Vaughan McAlley, 2019/05/11