Talk:Kite's ups and downs notation: Difference between revisions
No edit summary |
m TallKite moved page Talk:Ups and downs notation to Talk:Kite's ups and downs notation: Editor VectorGraphics has repeatedly edited pages I've written about my own research and inserted misinformation. On discord he is openly hostile to me. This move is necessary to avoid a toxic work environment for me. |
||
| (10 intermediate revisions by 4 users not shown) | |||
| Line 21: | Line 21: | ||
::: I'm a little confused about the last thing you said. You would never need to write ^ND under the diamond-mos standard because ^/v alone already cancel #/b. In fact, I'm not including ^N in the diamond-mos template mscz I'm making, because ^ alone has the same meaning. In general, I don't think either choice is creates more or less clutter. The "independent" rule can write D# ^D# with less clutter, and the "dependent" rule can write D# ^D with less clutter. I go with the dependent rule because it's more in line with how standard 12edo accidentals already work. [[User:SupahstarSaga|SupahstarSaga]] ([[User talk:SupahstarSaga|talk]]) 15:23, 31 July 2021 (UTC) | ::: I'm a little confused about the last thing you said. You would never need to write ^ND under the diamond-mos standard because ^/v alone already cancel #/b. In fact, I'm not including ^N in the diamond-mos template mscz I'm making, because ^ alone has the same meaning. In general, I don't think either choice is creates more or less clutter. The "independent" rule can write D# ^D# with less clutter, and the "dependent" rule can write D# ^D with less clutter. I go with the dependent rule because it's more in line with how standard 12edo accidentals already work. [[User:SupahstarSaga|SupahstarSaga]] ([[User talk:SupahstarSaga|talk]]) 15:23, 31 July 2021 (UTC) | ||
::: Reading the page Flirora linked, I now think there's a little misunderstanding here. Your "dependent" rule requires that ups and downs always be attached to a #/b/N accidental. I agree that that causes clutter. The diamond-mos rule is different; ups and downs can appear alone, but they cancel #/b/N. You can think of diamond-mos ^/v as including implicit naturals. I don't think my rule is more or less cluttered than your "independent" rule. [[User:SupahstarSaga|SupahstarSaga]] ([[User talk:SupahstarSaga|talk]]) 15:27, 31 July 2021 (UTC) | ::: Reading the page Flirora linked, I now think there's a little misunderstanding here. Your "dependent" rule requires that ups and downs always be attached to a #/b/N accidental. I agree that that causes clutter. The diamond-mos rule is different; ups and downs can appear alone, but they cancel #/b/N. You can think of diamond-mos ^/v as including implicit naturals. I don't think my rule is more or less cluttered than your "independent" rule. [[User:SupahstarSaga|SupahstarSaga]] ([[User talk:SupahstarSaga|talk]]) 15:27, 31 July 2021 (UTC) | ||
== Cancel == | |||
> If an up-C is followed by a down-C, the down-arrow cancels the up-arrow. | |||
''To cancel'' means to remove the previous effect, but I think what's meant here is to completely replace the previous effect with the new effect, so that the notated down-C sounds a down-C, not a natural C. If I'm right about that, I think ''replace'' is right word to use here. ''To override'' means the same thing as ''to replace'' in this specific context so I'm not sure of the comparison between ''override'' and ''"cancel"'' in the next paragraph. I think the two approaches are addition and replacement/override. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 14:47, 27 April 2024 (UTC) | |||
:Done. Sorry it took so long, I only just now noticed this. Feel free to ping me on discord next time. --[[User:TallKite|TallKite]] ([[User talk:TallKite|talk]]) 10:10, 23 March 2025 (UTC) | |||