User talk:Yourmusic Productions: Difference between revisions

Line 66:

- Yeah, it seems that this is particularly a problem with superpythagorean systems, where if you follow the math strictly, it frequently looks like you're going the wrong way on staff notation. Guitar tab is so much less of a headache in that respect. Regarding ups and downs in general, I do think it might be helpful to distinguish between movements in systems where every interval is reachable by chains of 5ths, so you could just use sharps and flats if you want, and the ups & downs just give you different ways to notate the same interval, and edos that are contorted in the 3-limit, so a different type of notation becomes essential to move between chains. --[[User:Yourmusic Productions|Yourmusic Productions]] ([[User talk:Yourmusic Productions|talk]]) 08:57, 16 December 2020 (UTC)

: Good points. Very true about C# being above Db in those edos. About distinguishing between contorted vs. non-contorted use: in practice, any score that uses ups and downs must define them at the top of the page, e.g. "^1 = 1\15" or "^1 = 1\15 = 80¢" for 15-edo. That sort of clues you in to that. One could also write something more explicit there, e.g. "fifth = 9\15 = 720¢" or even "fifth = 3\5 = 720¢". --[[User:TallKite|TallKite]] ([[User talk:TallKite|talk]]) 22:56, 16 December 2020 (UTC)

Revision as of 13:44, 16 December 2020 view source Xenwolf (talk \| contribs) autopatrolled, Bureaucrats, confirmaccount-notify, Interface administrators, Sysops 8,705 edits →Commas, commas, commas!: minor update ← Older edit		Revision as of 22:56, 16 December 2020 view source TallKite (talk \| contribs) autopatrolled, Sysops 3,992 edits →Ups and downs notation tables on the EDO pages Newer edit →
Line 66:		Line 66:

	- Yeah, it seems that this is particularly a problem with superpythagorean systems, where if you follow the math strictly, it frequently looks like you're going the wrong way on staff notation. Guitar tab is so much less of a headache in that respect. Regarding ups and downs in general, I do think it might be helpful to distinguish between movements in systems where every interval is reachable by chains of 5ths, so you could just use sharps and flats if you want, and the ups & downs just give you different ways to notate the same interval, and edos that are contorted in the 3-limit, so a different type of notation becomes essential to move between chains. --[[User:Yourmusic Productions\|Yourmusic Productions]] ([[User talk:Yourmusic Productions\|talk]]) 08:57, 16 December 2020 (UTC)		- Yeah, it seems that this is particularly a problem with superpythagorean systems, where if you follow the math strictly, it frequently looks like you're going the wrong way on staff notation. Guitar tab is so much less of a headache in that respect. Regarding ups and downs in general, I do think it might be helpful to distinguish between movements in systems where every interval is reachable by chains of 5ths, so you could just use sharps and flats if you want, and the ups & downs just give you different ways to notate the same interval, and edos that are contorted in the 3-limit, so a different type of notation becomes essential to move between chains. --[[User:Yourmusic Productions\|Yourmusic Productions]] ([[User talk:Yourmusic Productions\|talk]]) 08:57, 16 December 2020 (UTC)

			: Good points. Very true about C# being above Db in those edos. About distinguishing between contorted vs. non-contorted use: in practice, any score that uses ups and downs must define them at the top of the page, e.g. "^1 = 1\15" or "^1 = 1\15 = 80¢" for 15-edo. That sort of clues you in to that. One could also write something more explicit there, e.g. "fifth = 9\15 = 720¢" or even "fifth = 3\5 = 720¢". --[[User:TallKite\|TallKite]] ([[User talk:TallKite\|talk]]) 22:56, 16 December 2020 (UTC)