Xenharmonic Wiki talk:Things to do: Difference between revisions
| Line 289: | Line 289: | ||
: Slightly off topic, but I would rather patent vals be octave reduced, so that ⟨41 65 95 115 142...] becomes ⟨41 24 13 33 19...]. Less mathematician-friendly, but more musician-friendly. --[[User:TallKite|TallKite]] ([[User talk:TallKite|talk]]) 03:11, 12 January 2021 (UTC) | : Slightly off topic, but I would rather patent vals be octave reduced, so that ⟨41 65 95 115 142...] becomes ⟨41 24 13 33 19...]. Less mathematician-friendly, but more musician-friendly. --[[User:TallKite|TallKite]] ([[User talk:TallKite|talk]]) 03:11, 12 January 2021 (UTC) | ||
:: Hmm, IMO, reducing patent vals wouldn't help. It seems your problem is the general idea of monzos being "musician-unfriendly", in which case maybe you'd prefer "musician-friendly monzos" where primes are octave-reduced and octave-complemented to be in the 0c to 600c range, and where all ratios written in the form of these "musician-friendly monzos" are octave-agnostic, with a "number of octaves" specified only if needed but otherwise deduced to be the right amount for the context. --[[User:Godtone|Godtone]] ([[User talk:Godtone|talk]]) 22:39, 18 January 2021 (UTC) | |||
:: Duplication of information is a severe problem we discussed. The tendency to copy&past from table to table raises the danger of spreading errors and making much more work... That's the problem I have with all that information. I had much hope in your comments, @Kite, but to be honest, I still don't see in how far this information will be helpful for you. Just saying I like it is not enough in my opinion. Can you please explain your personal use of comma information? --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 06:31, 12 January 2021 (UTC) | :: Duplication of information is a severe problem we discussed. The tendency to copy&past from table to table raises the danger of spreading errors and making much more work... That's the problem I have with all that information. I had much hope in your comments, @Kite, but to be honest, I still don't see in how far this information will be helpful for you. Just saying I like it is not enough in my opinion. Can you please explain your personal use of comma information? --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 06:31, 12 January 2021 (UTC) | ||
| Line 303: | Line 305: | ||
:::: Okay, seems we have to find another way to do reduce duplication or ensure correctness. In my opinion, we then should leave it for now as it is. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 07:32, 15 January 2021 (UTC) | :::: Okay, seems we have to find another way to do reduce duplication or ensure correctness. In my opinion, we then should leave it for now as it is. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 07:32, 15 January 2021 (UTC) | ||
:::: In terms of the risk of errors due to duplication of information in tables, this shouldn't be a problem if the tables are computer-generated or at least computer-checked. I kind of presumed they were at least in part (either generated or checked, or both)... I have some (quite unpolished) Python 3 code that could be relatively easily used to verify commas' ratios, monzos and cent sizes, but I have yet to figure out a good general-purpose way to ''find'' the commas that a rank one temperament tempers, mainly because I can't think of a good general-purpose way of thinking of what commas are meaningful/interesting, as there are many very complex commas that might be considered of interest, such as [[Tolermic_family|the tolerma]], which is interesting mainly because of the variety of commas it can combine with and the unique resulting tempered arithmetics/rank one temperaments. The only thing is the tables would have to list information in a predictable way so that code could be made that accepts text input and spits out any inconsistencies, but I presume they are mostly already in that format? Removing the "comments" column could help with this. As for "hovering", maybe we could just show the patent val and the cents and the hover can give the ratio if needed? I've seen the ratio appear as a hover in other parts of the xen wiki already, and it'd remove one of the columns, the only problem is some commas may be more easily identifiable by their ratios than their vals, and hovering doesn't (necessarily?) work on phones (and probably some other devices). Removing the "prime limit" column in favour of having rows that separate the prime limits is something I can get behind, especially if it means we can instead list commas by JI subgroup interpretations of a rank one temperament rather than just by the rather restricted (but not unuseful) "prime limits" construct. This would also be very beneficial to rank one temperaments with multiple valid JI subgroup interpretations, such as [[9edo]]. The only thing is the rows that separate different comma subgroups should be bolded or made easy to spot in some way. (Oh and BTW, my name is based on my nickname for my favourite JI interval, [[23/20]], which is just about 2 cents sharp of 1 step of 5 EDO. I was gonna mention it on my user page at some point later but I wanna get a bulk of my thoughts/theories about microtonal music written first before I talk about it.) --[[User:Godtone|Godtone]] ([[User talk:Godtone|talk]]) 22:39, 18 January 2021 (UTC) | |||
:: The octave reduced version of (patent) vals can easily be added in EDO pages, but in this case the first value would be zero. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 06:31, 12 January 2021 (UTC) | :: The octave reduced version of (patent) vals can easily be added in EDO pages, but in this case the first value would be zero. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 06:31, 12 January 2021 (UTC) | ||