|
Tags: Mobile edit Mobile web edit Advanced mobile edit |
| (60 intermediate revisions by 13 users not shown) |
| Line 1: |
Line 1: |
| * [[User talk:FloraC/Archive 2020]]
| | {{Archives}} |
|
| |
|
| == Fractions vs. names in interval lemmas == | | == Higher primes == |
| | A while back I made an edit on [[181edo]], saying it has less than 30% error on most prime harmonics up to 137. You removed this info, giving the edit summary "don't bombard the readers with random prime numbers. 30% unsigned error isn't even special." There is a similar section on the page for [[43edo]], which goes as follows: |
|
| |
|
| What about moving the limit to 9 digits, or 4 digits in the denominator? Kite already suggested this for comma tables, I run an (in my opinion) acceptable test on [[41edo#Commas]]. I'd also like to be more consistent in this aspect, i.e. pages that can easily be linked by just copying their title. So the limits about comma tables should maybe also been applied to (comma) page titles itself. What do you think? --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 17:30, 9 January 2021 (UTC)
| | <blockquote>Although not [[consistent]], 43edo performs quite well in very high prime limits. It has unambiguous mappings for all prime harmonics up to ''113'' (after which the demands on its pitch resolution finally become too great), with the sole exceptions of 23, 71, 89, and 103, making a great [[#Ringer 43|Ringer scale]].</blockquote> |
|
| |
|
| : The change for page titles is minimal, as I don't remember of a single 9-digit comma. I'm not fond of comma tables also subjecting to that rule though. Comma tables can afford to show more digits, and hiding them removes the aspect of the sensation of complexity by the sheer length. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 16:25, 10 January 2021 (UTC)
| | Here, prime 41 with 37.5% relative error is considered "unambiguous". Four missing primes in the 113-limit isn't really too special with this rather relaxed bound. You may want to do something about this section, though maybe more can be kept as 43edo is smaller than 181.--[[User:Overthink|Overthink]] ([[User talk:Overthink|talk]]) 22:52, 12 January 2026 (UTC) |
|
| |
|
| :: The 9-digit rule is nothing other than an extended 8-digit rule. With octave-reduced fractions, cases are possible with 5-digit nominators with a <code>1</code> as leading digit. In my opinion, the comma tables on the EDO pages are overloaded anyway. There all the information we have about commas is repeated, I assume that most of this information is obtained by copying from other pages, so there could be a number of errors to correct multiple times. And this tendency will rather increase if we don't push back this kind of duplicates. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 17:15, 10 January 2021 (UTC) | | : Originally, this part read: |
|
| |
|
| ::: I agree the comma tables in edo pages are overloaded. What should be there and what should not, then? [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 07:25, 11 January 2021 (UTC) | | : <blockquote>Although not consistent, it performs quite decently in very high limits. It has unambiguous mappings for all prime harmonics up to 64 [61], with the sole exceptions of 23 and, perhaps, 41. </blockquote> |
|
| |
|
| :::: I'd say limit and one name or fraction (depending on target lemma) with link, maybe a column for comments. The comments column can be used to contain the information if there is no comma page to link to, but I think we should soon create these pages and link to them as well from the global comma tables. I now think I probably should have started this discussion in the Xenharmonic Wiki namespace. I now try to move it to there: [[Xenharmonic Wiki: Things to do #Comma tables in EDO_pages]]. Sorry for the trouble. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 08:57, 11 January 2021 (UTC) | | : Then some editor was being crazy about it cuz ''four'' exceptions are no ''sole'' exceptions. But I don't think I'm gonna remove that entirely. Rather, I'm moving it to a higher-limit JI subsection of the approximation to JI section to hopefully declutter the theory section. |
|
| |
|
| == dev ==
| | : —[[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 10:36, 13 January 2026 (UTC) |
|
| |
|
| You are now member of dev.xen.wiki. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 06:42, 12 January 2021 (UTC)
| | == 2187/1250 == |
| | I’m planning to draft a page for 2187/1250 in my userspace since it’s a 5-limit ratio closely approximating 7/4, but I think I should name it something. Something like 5-limit harmonic-esque seventh or something referencing the ragismic temperament since it’s 4375/4374 below 7/4. Do you have any name suggestions? <span style="display: inline-block;transform: rotate(15deg);background:#E1EBF2;font-family:Verdana;text-shadow: 3px 3px 4px #0008;">[[User:Hotcrystal0|hotcrysta]][[User talk: Hotcrystal0|l0]]</span> 19:12, 14 January 2026 (UTC) |
|
| |
|
| == Telicity ==
| | : Tetraptolemaic diminished seventh. —[[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 20:09, 14 January 2026 (UTC) |
|
| |
|
| Hey, Flora, I finally have a name for the collection of properties which I once dubbed as being a sort of "consistency". Now that I have terminology to talk about this concept, which I call "telicity", I'm hoping we can discuss this some, as I'm hoping this topic is worthy of an article here. Perhaps I ought to lay down what I know about telicity here so you can evaluate the concept for yourself.
| | == Generator counts == |
| | I'm planning to start another chord page draft at [[User:Overthink/Chords of pajara]] (not yet created as of the time this is written). The issue is that it's not as simple to give a chord by generator counts, as there's a half-octave period in pajara. The page [[Unidec/Chords]] uses a val, but it is quite messy. I propose the following solution: The half-octave is taken as the period, and the generator is a perfect fifth. Intervals reachable by stacking fifths are just written with a number; for example, 1–3/2–12/7 would be "0–1–3". An interval that requires stacking fifths from the half-octave would be written with "T" (for tritone) before the number of fifths stacked; for example, 1–6/5–3/2 would be written as "0–T3–1". Maybe it would be better to give an "R" (for root) before intervals reachable by stacking fifths, so that 1–6/5–3/2 would be "R0–T3–R1", which is more readable. I'm also not too sure if the fifth should be the generator or the semitone instead.--[[User:Overthink|Overthink]] ([[User talk:Overthink|talk]]) 01:28, 20 January 2026 (UTC) |
|
| |
|
| Telicity- as I'm defining it here- is a property of [[EDO]]s, which involves the given EDO being able to stack a number of instances of a given prime's [[patent interval]] to connect with an interval belonging to a chain created by lower prime's [[patent interval]] without accumulating 50% relative error or more at any point in the process on the part of either prime's chain.
| | : I have to say I'm influenced by hkm's usage of an apostrophe to denote an offset by a period, so in that scheme, 1–6/5–3/2 can be written as "0–'3–1". I feel it looks fairly clean, not too intrusive, at least for temps with a semi-octave period. I think the generator should be taken as the fifth, not the semitone, cuz it's easier to think of the temp as two chains of fifths offset by a semi-octave. —[[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 09:29, 20 January 2026 (UTC) |
|
| |
|
| Given this definition, the only type of telicity available to the 3-prime is 3-to-2 telicity, as the 3-prime can only connect with the 2-prime in this fashion, and since the 2-prime simply results in manifestations of the [[unison]] at different registers- meaning that the unison is the only available target- that means that the 3-prime requires a complete [[circle of fifths]] without accumulating 50% relative error or more. However, higher primes have more options for achieving a form of telicity as there are multiple lower primes to chose from to potentially connect with, For instance, the 5-prime has both 5-to-3 and 5-to-2 telicity available to it.
| | :: Hm... Maybe placing the apostrophe ''after'' the number is more readable. This way 1–6/5–3/2 will become "0–3'–1", and the number coming first is more readable, plus it will be read as "3 prime" which fits better with math notation.--[[User:Overthink|Overthink]] ([[User talk:Overthink|talk]]) 21:39, 20 January 2026 (UTC) |
|
| |
|
| Combinations of primes are more complicated, and some of the nuances are yet to be considered in this realm, but it's safe to say that there are more types of telicity available in such cases- namely "full telicity" and "partial telicity". Full telicity for combinations involving multiple primes occurs when the EDO in question is able to stack a number of instances of a given combination's patent interval to connect with an interval belonging to a chain created by the patent interval for a prime that is lower than the lowest prime in the initial combination. In contrast, partial telicity for combinations involving multiple primes occurs when the EDO in question is able to stack a number of instances of a given combination's patent interval to connect with an interval belonging to a chain created by the patent interval for a prime that is lower than the highest prime in the initial combination.
| | ::: Good point. —[[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 11:49, 21 January 2026 (UTC) |
|
| |
|
| Given that different EDOs can temper out different commas to achieve the same type of telicity- for example, [[12edo]] tempers out the [[Pythagorean comma]] to achieve 3-to-2 telicity, while [[53edo]] tempers out [[Mercator's comma]] to achieve 3-to-2 telicity- it can thus be argued that sequences of different EDOs demonstrating one or more types of telicity can be compiled. For instance, the first seven EDOs to demonstrate 3-to-2 telicity specifically are {{EDOs| 2, 5, 12, 24, 53, 106, 159 }}- yes, I checked this without a computer algorithm available to me, and this is the result I got.
| | == {{monzo| -37 0 0 0 0 10}} == |
| | Does there exist a page for the {{monzo| -37 0 0 0 0 10 }} comma, or the difference between 10 13/8s and 7 octaves? <span style="display: inline-block;transform: rotate(15deg);background:#E1EBF2;font-family:Verdana;text-shadow: 3px 3px 4px #0008;">[[User:Hotcrystal0|hotcrysta]][[User talk: Hotcrystal0|l0]]</span> 16:24, 20 January 2026 (UTC) |
|
| |
|
| I hope this idea makes more sense than my initial attempts to talk about it on the [[Talk:159edo|159edo talk page]]. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 07:03, 19 January 2021 (UTC)
| | : As you can see in ''Small comma'' page, the comma was named the ''valerisma'', and no articles exist for it. —[[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 16:28, 20 January 2026 (UTC) |
|
| |
|
| : For single-ring edos, every interval is on the chain of 3s. Take 31edo for example, isn't its first step of harmonic 5, 10\31, already on the circle of fifths, for the tempering of 81/80? [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 07:34, 19 January 2021 (UTC)
| | == Odd prime sum limit notability == |
| | I noticed that you removed the mentions of odd prime sum limit records I made from a couple of edo pages. Is it too arbitrary of a metric for prime approximation to be mentioned on these pages? If so, how is it different in this regard from Pepper ambiguity (still mentioned on the 270edo page)? |
|
| |
|
| :: Let's see, for 31edo, 81/80 is larger than half of a step in size, so 31edo actually fails to demonstrate 5-to-3 telicity as the relative error induced by the comma is liable to be greater than 50%. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 07:38, 19 January 2021 (UTC) | | : I do take issue with Pepper ambiguity specifically when the intervals involve inconsistency, but as the information have been there for a long time I don't feel like removing them. —[[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 11:46, 29 January 2026 (UTC) |
| | : <small>P.S. pls remember to sign your comment with <code><nowiki>~~~~</nowiki></code>. </small> |
|
| |
|
| :: For the sure-fire examples of telicity, the comma being tempered out has to be less than half an EDO step in size. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 07:42, 19 January 2021 (UTC)
| | == EDO impressions == |
| | In your EDO impressions for 36edo you mentioned adding “third tones”, even though the correct term here would be “sixth tones”. Can you fix that? <span style="display: inline-block;transform: rotate(15deg);background:#E1EBF2;font-family:Verdana;text-shadow: 3px 3px 4px #0008;">[[User:Hotcrystal0|hotcrysta]][[User talk: Hotcrystal0|l0]]</span> 18:16, 29 January 2026 (UTC) |
|
| |
|
| ::: Such commas are ubiquitous. What about 8 steps of 10\31 to 3/2, for the tempering of würschmidt comma? [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 08:04, 19 January 2021 (UTC) | | : Fixed. —[[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 20:23, 29 January 2026 (UTC) |
|
| |
|
| :::: Ah, this makes more sense for 5-to-3 telicity. Sorry about that, looks like 31edo does demonstrate 5-to-3 telicity after all, my mistake. It may be true that commas that are less than half a step in size are ubiquitous, but I've also noticed in my explorations that sometimes commas of this sort fail to be tempered out. Truth be told, the reason I'm tying to limit my idea of telic commas to commas that are less than half an EDO-step in size is because any instance of telicity involving the 2-prime cannot afford to temper out commas greater than half an EDO-step in size due to the unison being such a foundational interval to both EDOs and JI, and, the resultant inability to temper out commas greater than half a step in size without exceeding the 50% relative error threshold. Thus, I'm trying to impose a uniform standard for this across the board just to make it easier. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 08:17, 19 January 2021 (UTC)
| | == Tetracot == |
|
| |
|
| To state the definition of telicity more mathematically, where "N" is the number of steps in a given EDO, "r" is the ratio of an interval in one of the two prime chains, and "M" is the monzo of "r", the equation {N, round(log2(3)*N), round(log2(5)*N), round(log2(7)*N), round(log2(11)*N), ...}.{M} = round(log2(r)*N) must hold true along both prime chains up to and including the point of connection. Does this make more sense?
| | On the page [[Tetracot extensions]], you suggested splitting it into four pages: [[Monkey]], [[Bunya]], [[Modus]], and [[Wollemia]]. Tetracot splits the [[2187/2048|apotome]] into four comma steps. It maps 5/4 to the vM3, 11/8 to the sA4, and 13/8 to the n6. The main tetracot edos are [[27edo]] (27e val for prime 11), [[34edo]], and [[41edo]]. These extensions differ is the mapping of prime 7: |
|
| |
|
| == Discord ==
| | Monkey (34 & 41): 7/4 is vm7 |
|
| |
|
| Hello Flora, I see that you're on Discord. Since I myself am also on Discord, and since this [https://discord.com/channels/786387772885565442/786387772885565445 Microtonal Server] was established by another user here last year, I feel that you would be quite welcome. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 17:24, 21 January 2021 (UTC)
| | Bunya (34d & 41): 7/4 is sA6 |
|
| |
|
| : It's not an invite link. You should get the invite link so that I can join. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 06:47, 22 January 2021 (UTC)
| | Modus (27e & 34d): 7/4 is m7 |
|
| |
|
| :: Right. I'll get to that in a bit. | | Wollemia (27e & 34): 7/4 is ^A6 |
|
| |
|
| :: Excuse me, but I'm not sure how to invite users who are not on my friends list... --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 16:00, 22 January 2021 (UTC)
| | I've noticed that in 27edo the pythagorean thirds are quite clearly supermajor/subminor, and the 5-limit thirds are quite far from each other, with [[5/4]] being the same 400{{c}} major third as in 12edo, and [[6/5]] being slightly flat at 311.{{Overline|1}}{{c}}. 34edo makes 5/4 and 6/5 both about equally sharp, and the pythagorean thirds are mapped as in 17edo. 41edo maps the pythagorean thirds close to just, but the 5-limit thirds are slightly closer to neutral as a result. In any case, intervals of 11 and 13 are mapped to neutral intervals. The way I tend to think of tetracot is as a tertian structure (like [[keemic]]). |
|
| |
|
| == Inharmonic vs subgroup TE ==
| | Monkey and modus map 7/4 to a 7th (they are supported by the 7edo patent val). The tertian structures of 27edo and 41edo are quite clearly different, while 34edo is somewhat similar to both (though IMO closer to 27edo as 34d is better than patent 34). Here 34d&27 is modus, while 34&41 is monkey. They are quite clearly different, as modus sets the pythagorean thirds to septimal ones while pental thirds are halfway between the septimal thirds and neutral ones. Monkey, on the other hand, distinguishes the pythagorean thirds from pental and septimal ones, and sets them equidistant from pental and septimal thirds. |
|
| |
|
| Would you happen to know the difference between "inharmonic TE" and "subgroup TE" tunings on x31eq for subgroup temperaments? For 2.9.5.21 13&18 temperament, the POTE generator is 464.1396c using inharmonic TE but 464.3865c using subgroup TE. Is subgroup TE specifically intended for approximating JI subgroups? [[User:IlL|Inthar]] ([[User talk:IlL|talk]]) 11:39, 4 February 2021 (UTC)
| | Bunya and wollemia, on the other hand, map 7/4 to a 6th (corresponding to the 7d val). Bunya (34d&41) maps 7/4 to a sA6, so that 28/27 is equated with 33/32 as an sA1, as in [[parapyth]]. This sets the pythagorean major third to [[14/11]], and 9/7 to an sd4 instead. Bunya also tempers out [[225/224]], so that 7/4 is equated with the [[225/128]] augmented 6th, which in tetracot is a vvA6 = sA6. Wollemia (27e & 34), on the other hand, is quite strange. It tunes the fifth so that the pythagorean intervals are close to septimal intervals, but doesn't actually map them to septimal intervals. Instead, 28/27 is mapped to a ^1, so 9/7 is a v4, and 7/6 is a ^A2. Optimal tunings of wollemia are close to optimal tunings of modus, but doesn't temper out [[64/63]], instead equating septimal supermajor/subminor intervals to tridecimal ultramajor/inframinor intervals via tempering of [[91/90]]. In wollemia [[14/11]] is also mapped to the same interval as [[5/4]], and [[11/8]] the same interval as [[7/5]]. I'm not too sure of the significance of this yet, besides that both the 27e and 34 vals contain these equivalences. |
|
| |
|
| : I'm only able to reproduce the results of "inharmonic TE". It finds the least square in the TE weighted space by treating any basis just like prime ones. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 12:01, 4 February 2021 (UTC)
| | In any case, I suggest you add a 7et detemperament section to the [[Tetracot]] article. |
|
| |
|
| == [[Template:Val|Val]] vs [[Template:Vals|Vals]] ==
| | --[[User:Overthink|Overthink]] ([[User talk:Overthink|talk]]) 23:45, 13 February 2026 (UTC) |
|
| |
|
| Hi Flora, <br>
| | : Sure. —[[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 13:39, 14 February 2026 (UTC) |
| Sorry that I wasn't aware of this problem, when I suggested to branch out ''Vals'' from [[Template:EDOs]]. The distance pattern of <code>vals</code> and <code>val</code> is one of the worst possible, in the same class of coding horror with <code>valf</code> vs <code>vals</code> (slightly better) and <code>sonth</code> and <code>sonth</code> (even worse). While <code>val</code> is for formatting one val (long form), <code>vals</code> is for adding links to EDO pages. As a programmer, I'd like to get rid of <code>val</code> being a sub string of the other, but maybe this is too much to change and also means more typing in the future ... <br>
| |
| Do you have any ideas how to solve it? <br>
| |
| Best regards --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 09:53, 7 February 2021 (UTC)
| |
|
| |
|
| : Just an idea: what about <code><nowiki>{{List of vals|...}}</nowiki></code>? --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 09:55, 7 February 2021 (UTC)
| | == About schismina == |
| | What's the deal with the schisminic temp? It is 2.3.5.7.13, there's no 11. Also, I would deem the differences I outlined are notable, because they show how many ''simple'' ratios of 35 have tiny differences with tridecimal equivalents and viceversa. Specially 8505/8192, whose pressence in Sagittal pretty much assumes that the schismina is either tempered out or fudged. It's that important of a schisma, we have to sell it as such! --[[User:Eufalesio|Eufalesio]] ([[User talk:Eufalesio|talk]]) 17:05, 22 February 2026 (UTC) |
|
| |
|
| :: Maybe we add ''Not to be confused with Template:Vals'' to ''Template:Val'' and vice versa. Does it solves the problem? If not, we can go for <code><nowiki>{{val list| ... }}</nowiki></code>. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 10:23, 7 February 2021 (UTC) | | : > What's the deal with the schisminic temp? It is 2.3.5.7.13, there's no 11. |
|
| |
|
| ::: I think <code><nowiki>{{val list}}</nowiki></code> is great. This way we can wait to point out the possible confusion until we actually observe the first confusion. Of course, in this solution the search for "val" will return both.--[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 18:04, 7 February 2021 (UTC) | | : That's why ''schismina'' isn't a great name for the comma; there's no room to distinguish the minimal-prime-subgroup temp and the full-prime-limit temp according to our rules. I've proposed something else in ''Talk: 4096/4095''. |
|
| |
|
| == 159edo Notation System ==
| | : > I would deem the differences I outlined are notable. |
|
| |
|
| Hey, Flora, I've been talking with a few other people about my proposed system for notating 159edo on my user talk page and elsewhere, and I'm getting the sense that my system is clear and straightforward. My question now is whether or not it's feasible to try and finalize the system. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 06:19, 20 February 2021 (UTC)
| | : I think there's a problem in how you present your ideas. If all you wanna discuss is the merge of intervals of 13 with intervals of 35, add that instead. A pair of ratios may serve as an example, but the entire point is in the context. The ratios alone which comprise three- or even four-digit ones aren't notable cuz no one uses them in music. |
|
| |
|
| : To say "finalize" is like you don't take long-term maintenance of your system, but I reckon it more sensible to iterate it whenever you feel the need in the course of use. | | : —[[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 17:33, 22 February 2026 (UTC) |
|
| |
|
| : If you plan on the MuseScore plugin, you'll want to consider that MuseScore doesn't allow freely combined accidentals. To access each step you need independent symbols. MuseScore's current sagittal coverage isn't enough for 159edo, either. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 07:00, 20 February 2021 (UTC)
| | == Thanks == |
| | | Hello Flora, how are you today? I see you corrected some mistakes I unwittingly made when editing MOS pages, for example, when I called 2L 17s a MOS of Pycnic temperament and you took it out, noting that 2L 17s is actually tritonic temperament. So, I just wanted to say thank you, and I will double-check my edits in the future. [[User:MisterShafXen|MisterShafXen]] ([[User talk:MisterShafXen|talk]]) 17:28, 6 May 2026 (UTC) |
| :: In this case, I say "finalize" in regards to the selection of symbols themselves and their design- the remaining symbols are made from single symbols that have been strung together. Also, I'm wondering if support for custom accidentals can be incorporated into MuseScore 4. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 07:18, 20 February 2021 (UTC)
| |
| | |
| ::: I'd say the selection of symbols and their design could be iterated through use as well. As for software, if Dorico can do it, I believe MuseScore too. Let's wait and see. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 07:30, 20 February 2021 (UTC)
| |
| | |
| :::: Well, the better the selection is to begin with, the fewer changes will have to be made later- aside from those caused by things like font changes in general. So, I'm looking to get the designs for this iteration finalized- however, Xenwolf seems to be quite busy at the moment. --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 07:42, 20 February 2021 (UTC)
| |
| | |
| ::::: Only through real application can you evaluate your selection. I don't know if the double dart is clear enough when stacked notes are present, for example. You'll have to check that in a real score. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 08:10, 20 February 2021 (UTC)
| |
| | |
| == Will you check up my implementation of the traditional Chinese tonal system? == | |
| | |
| Hi FloraC,
| |
| | |
| I assume you are more into Chinese culture than I am. :-)
| |
| | |
| Would you take a look at my Microtonal Playground platform and, among other things, provide some feedback on the implementation of the Chinese scales?
| |
| | |
| With my system, you can play music directly in your browser. The entire introductory part can be found on my page: [[User:SAKryukov#Microtonal_Fabric|Microtonal Fabric]].
| |
| | |
| The particular application I'm asking you to look at is called [[User:SAKryukov#New.21_Microtonal_Playground|Microtonal Playground]].
| |
| | |
| Live play with different systems is [[https://SAKryukov.github.io/microtonal-fabric/code/playground/custom here]].
| |
| | |
| I reproduced intervals, modes, the names of notes, and modes based on the Wikipedia article referenced in the Tonal System Metadata (will see it when you start the application). | |
| | |
| I'll be very grateful if you take a look. Does it make sense? Can you see any mistakes in sound and names?
| |
| | |
| If you have any questions, I'll gladly answer. What I do is all open-source and a non-commercial project project, open for many kinds of collaboration for mutual benefits. For example, I could make the [[User:FloraC/Flora's_12-note_well_temperament|tonal system you suggested]] playable.
| |
| | |
| Thank you. — [[User:SAKryukov|SA]], ''Sunday 2021 February 21, 05:16 UTC''
| |
| | |
| : I'm afraid I'm not as familiar with traditional Chinese tonal system as you've hoped. But if you're talking about [[Wikipedia: Shí-èr-lǜ|Shí-èr-lǜ]] specifically, afaik it's very similar to Pythagorean tuning, except that every block of notes in an octave is stretched by a Pythagorean comma – at least that's how I interpret the sources. In your app the jiázhōng and zhònglǚ clearly doesn't sound right though. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 10:03, 21 February 2021 (UTC)
| |
| | |
| :: Thank you! This is not so much of musical knowledge, but rather a fresh look. For example, as I don't understand the words, I could have messed them up. It looks like you do understand the words, even though they are spelled in some Latin-based rendering. I do hear the problematic sounds; it looks like a recent regression bug, so I just did not re-test it after some latest changes. The data describing the system is [https://github.com/SAKryukov/microtonal-fabric/blob/master/code/playground/custom/chinese.user.data here]. — [[User:SAKryukov|SA]], ''Sunday 2021 February 21, 15:29 UTC''
| |
| | |
| ::: I checked the file and it turns out an asterisk is missing for jiázhōng and zhònglǚ. I tried fixing it (see your pull request). For musicians, the words are nothing but note names like ABCDEFG. Yet still, it's not really different from Pythagorean tuning if you don't apply the octave stretch. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 16:02, 21 February 2021 (UTC)
| |
| | |
| :::: You are right. I've fixed it and pushed the code. Thank you for your help!
| |
| :::: My impression of this system is: the goal was the equidistant tone arrangement, without any concerns of better harmony. Even obvious perfect 4th 4/3 is 3**11/2**17 there. To me, it looks like if the system was changed to 12-EDO even for traditional music, it would lose nothing. What do you think? — [[User:SAKryukov|SA]], ''Sunday 2021 February 21, 16:42 UTC''
| |
| | |
| ::::: I suppose it is, and it motivated prince Zhū Zǎiyù to compute the twelfth root of 2. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 17:52, 21 February 2021 (UTC)
| |
| | |
| :::::: Very interesting. I'm very curious: when it happened? Was the notion of irrational numbers also introduced or proven? — [[User:SAKryukov|SA]], ''Sunday 2021 February 21, 19:51 UTC''
| |
| | |
| ::::::: It's published in 1581. By the time irrational numbers had been recognized across the world. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 07:02, 22 February 2021 (UTC)
| |
| | |
| :::::::: Thank you! Any links? I'm asking because I was unaware of this; and it is very interesting and dramatically related to music. You know, the discovery on the irrational numbers is often attributed to Híppasos (c. 530 — c. 450 BC, by the way), but this is not known for certain, it could have been found by some other person of that time, but this is also not completely certain. And then, all that story about the death of Híppasos, who could have been killed by Pythagoreans... The entire idea of mystical Pythagorean... how to call it?... something closer to superstition than to science makes the idea of thinking of Pythagoreans and Pythagoras himself as of advanced mathematicians very questionable. No wonder some argue that the mathematical achievements of Pythagoras were faked, attributing them to, surprisingly, Híppasos. By the way, some scholars believe the irrationality proof was related to √2, which is the tritone in music, exactly half of the octave, «most disharmonic» and a very important interval. — [[User:SAKryukov|SA]], ''Tuesday 2021 February 23, 03:16 UTC''
| |
| | |
| ::::::::: See [[Wikipedia: 12 equal temperament #History]] for the history of 12edo (but the Baroque era section is probably incorrect as it confuses well temperaments for equal temperament). [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 04:06, 23 February 2021 (UTC)
| |
| | |
| :::::::::: Got it. Thank you! — [[User:SAKryukov|SA]], ''Tuesday 2021 February 23, 07:31 UTC''
| |
| | |
| == 42edo ==
| |
| | |
| Thanks, [https://en.xen.wiki/index.php?title=42edo&curid=771&diff=62335&oldid=62334 that] clarifies all :-) --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 13:53, 26 February 2021 (UTC)
| |
| | |
| == Tour of Regular Temperaments ==
| |
| Hey, I'm curious why you deleted Laconic and Comic. --[[User:TallKite|TallKite]] ([[User talk:TallKite|talk]]) 05:18, 17 March 2021 (UTC)
| |
| | |
| : There's no alternative extensions to them, so it seems unnecessary to keep the "families". I moved all the data (including the 5-limit version) to the related clan pages. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 06:11, 17 March 2021 (UTC)
| |
| | |
| == "temperaments not discussed in this page" sections ==
| |
| | |
| Hi Flora, I know that you added a lot of these sections ([https://en.xen.wiki/index.php?title=Breedsmic_temperaments&diff=next&oldid=51795]): Do I get it right that the temperaments mentioned in this sections do, technically spoken, also belong into the "category" of temperaments discussed on that page? My long-term goal is to link the individual temperaments (if they don't have their own wiki pages) via redirects. The redirects (and pages) can then be categorized (multiple times if needed). Thanks in advance for you help. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 08:18, 21 May 2021 (UTC)
| |
| | |
| : Right. Mike has written about it recently (see ''Subgroup Temperament Families, Relationships, and Genes''). [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 12:35, 21 May 2021 (UTC)
| |
| | |
| :: Ah, thanks a lot for the hint. Before reading it, a quick question: is there a quick explanation for the relation between [[Starling family]] and [[Starling temperaments]]? --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 12:40, 21 May 2021 (UTC)
| |
| | |
| ::: The former starts with the rank-3 temperament for 126/125 and includes ''extensions'' to higher limits. The latter, as the intro I wrote, is a misc collection of rank-2 temperaments tempering out 126/125. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 17:29, 21 May 2021 (UTC)
| |
| | |
| == On mitigating S(A)NS ==
| |
| | |
| <small>S(A)NS = "sticky (article) namespace syndrome"</small> <br>
| |
| As we know, there are a few users who show little or no activity outside of the main namespace. The spontaneous assumption that this must be due to them could be deceptive. I currently see the following factors as well: (1) lack of guidance from [[help]] pages; (2) habits (Wikispaces and other platforms do not provide discussion pages or messaging systems); (3) inconvenient user account configuration (perhaps defaults?); (4) inconspicuousness of invitations (for example in the Timeless skin, you can barely see that there are messages on the user page). I recently had an inspiring look into [[Wikipedia: Category:Article message templates]] and found that: <br>
| |
| One simple measure (to address factor #4) would be to add an obvious link in via <code>comment=</code> of [[template:todo]] (that therefore has to be visible, <code>inline=1</code>) on pages that lack clarity. The link should lead to a dedicated talk section further explaining the issue. <br>
| |
| What do you think? --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 07:39, 3 June 2021 (UTC)
| |
| | |
| == Minor update to prime interval table ==
| |
| | |
| I changed the <code>prec</code> parameter in a way that calculates the number of decimals for the given EDO value. I tried to keep the formula simple but it looks a bit unprofessional:
| |
| | |
| <syntaxhighlight lang="lua">
| |
| local function prec_by_edo(edo)
| |
| return math.floor(math.log(edo*1.9)/math.log(10))
| |
| end
| |
| </syntaxhighlight>
| |
| | |
| This way, we have increments at 6, 53, 527, 5264, 52632, etc. BTW: the error values get unreadable for higher EDOs (see [[103169edo]] and [[Talk:103169edo #Phone numbers]]). After changing [[Module:Primes in edo]] and [[Template:Primes in edo]], I removed redundant template arguments, mostly <code><nowiki>|prec=2</nowiki></code>.
| |
| | |
| I'm planning to add [[fifthspan]] information as well, but this will (probably) not be enabled by default. I also wish to make two rows out of the current last one to get rid of the parentheses. What do you think? --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 12:50, 11 July 2021 (UTC) | |
| | |
| # That was impressive! I just wonder where the 1.9 comes from. Are you targeting 53edo specifically?
| |
| # Sure, this table doesn't scale well into edos as high as 103169. Switching to scientific notation would somewhat improve the readability, but such edos aren't of much use anyway. I wouldn't say it's an emergent problem.
| |
| # I don't like separating two rows for the steps. "Reduced" stuff has always been in parentheses and it's fine. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 15:36, 11 July 2021 (UTC)
| |
| | |
| :: See [[User:Xenwolf/Fifthspan #EDO information with fifthspans]] for examples. This way we include the patent val in one row and the octave reduced steps in the other. I find the values in parentheses confusing, also because of the vagueness of the caption. If we add fifth spans, it's a lot of numbers that can easily be mixed up. So I decided to use thicker borders in some places. Please have a look as to see if the version without parentheses is really that bad... --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 20:59, 12 July 2021 (UTC)
| |
| | |
| ::: It's not ''really that bad''. It's acceptible. Yet an immediate suggestion is getting rid of that ''v'' and really saying "octave reduced" instead of mod ''n''.
| |
| | |
| ::: My preferred form is shown in my sandbox page now.
| |
| | |
| ::: But wait, maybe patent val and fifthspan could be placed in the infobox on the top-right? Since I just realized it ''is'' the patent val, which is simply a line of numbers, where each number need not be separated into cells like that. Placing it in the infobox saves a lot of space and flows better. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 04:46, 13 July 2021 (UTC)
| |
| | |
| == Redirects when moving pages to user namespace ==
| |
| | |
| I think it's better to leave redirects to the pages under construction (i.e., in user namespace) so it's easier for the editor to find their page and to understand what happened. Or do you see any harm to the article namespace possibly caused by these redirects? In that case, please tell me. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 15:38, 21 August 2021 (UTC)
| |
| | |
| : No problem. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 16:03, 21 August 2021 (UTC)
| |
| | |
| == Hemiterm vs Semiterm ==
| |
| | |
| Why did you rename 12&342 temperament "semiterm"? I named it "hemiterm" on 15 May 2021. Why is the name of 159&183 temperament "hemiterm"? The generator of term/terminal (12&159) ~35/33 = 98.3¢ (~3/2 = 701.7¢) and hemiterm (159&183) ~12/11 = 150.9¢ (~11/8 = 550.9¢, ~26/15 = 950.9¢), is it weird? [[User:Xenllium|Xenllium]] ([[User talk:Xenllium|talk]]) 14:13, 17 October 2021 (UTC)
| |
| | |
| : See [[Temperament names #Sensi]]: ''it was decided that "bi" or "semi" should be half for periods and "hemi" should be half for generators''. There are counterexamples but I hope new names follow it. Or you can swap them back, no problem. It's up to you. Sorry for disturbance. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 17:19, 17 October 2021 (UTC)
| |
| | |
| == Howto help ==
| |
| | |
| Thanks for having a look and [https://en.xen.wiki/index.php?title=Help%3AHow_to_Get_Your_Xenwiki_Account&type=revision&diff=81907&oldid=53580 updating ''Help:How to Get Your Xenwiki Account'']. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 22:50, 14 December 2021 (UTC)
| |
| | |
| : Well, I took a look since a user on the Discord reported they had issues signing up. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 11:11, 15 December 2021 (UTC)
| |
| | |
| == Normalized mapping vs minimum generator ==
| |
| | |
| Why is the generator wider than a half octave in some temperaments? Why did you edit mappings to normalize?
| |
| | |
| * [{{val|1 0 -4 -13}}, {{val|0 1 4 10}}] (generator: ~3 = 1896.5 cents) vs [{{val|1 2 4 7}}, {{val|0 -1 -4 -10}}] (generator: ~4/3 = 503.5 cents) in the [[Meantone family|meantone temperament]] (12&19)
| |
| * [{{val|1 0 -4 2}}, {{val|0 2 8 1}}] (generator: ~7/4 = 947.4 cents) vs [{{val|1 2 4 3}}, {{val|0 -2 -8 -1}}] (generator: ~7/6 = 252.6 cents) in the [[Meantone temperament #Godzilla|godzilla temperament]] (5&14c)
| |
| * [{{val|1 0 -13 -3}}, {{val|0 3 29 11}}] (generator: ~81/56 = 634.0 cents) vs [{{val|1 3 16 8}}, {{val|0 -3 -29 -11}}] (generator: ~112/81 = 566.0 cents) in the [[Tricot family|tricot temperament]] (53&70)
| |
| * [{{val|1 7 3 15}}, {{val|0 -8 -1 -18}}] (generator: ~8/5 = 812.6 cents) vs [{{val|1 -1 2 -3}}, {{val|0 8 1 18}}] (generator: ~5/4 = 387.4 cents) in the [[Würschmidt family|würschmidt temperament]] (31&96)
| |
| * [{{val|1 12 56 -2}}, {{val|0 -13 -67 6}}] (generator: ~256/147 = 961.4 cents) vs [{{val|1 -1 -11 4}}, {{val|0 13 67 -6}}] (generator: ~147/128 = 238.6 cents) in the [[Wizmic microtemperaments #Tokko|tokko temperament]] (5&166)
| |
| * [{{val|1 16 32 -15}}, {{val|0 -17 -35 21}}] (generator: ~9/5 = 1017.5 cents) vs [{{val|1 -1 -3 6}}, {{val|0 17 35 -21}}] (generator: ~10/9 = 182.5 cents) in the [[Minortonic family #Mitonic|mitonic temperament]] (46&125)
| |
| * [{{val|1 25 -31 -8}}, {{val|0 -26 37 12}}] (generator: ~28/15 = 1080.7 cents) vs [{{val|1 -1 6 4}}, {{val|0 26 -37 -12}}] (generator: ~15/14 = 119.3 cents) in the [[Breedsmic temperaments #Septidiasemi|septidiasemi temperament]] (10&161)
| |
| * [{{val|1 17 9 10}}, {{val|0 -30 -13 -14}}] (generator: ~10/7 = 616.6 cents) vs [{{val|1 -13 -4 -4}}, {{val|0 30 13 14}}] (generator: ~7/5 = 583.4 cents) in the [[Breedsmic temperaments #Cotritone|cotritone temperament]] (37&72)
| |
| * [{{val|2 0 11 31}}, {{val|0 1 -2 -8}}] (generator: ~3 = 1903.7 cents) vs [{{val|2 3 5 7}}, {{val|0 1 -2 -8}}] (generator: ~16/15 = 103.7 cents) in the [[Diaschismic family #Diaschismic|diaschismic temperament]] (46&58)
| |
| * [{{val|2 1 9 -2}}, {{val|0 2 -4 7}}] (generator: ~35/24 = 652.8 cents) vs [{{val|2 3 5 5}}, {{val|0 2 -4 7}}] (generator: ~36/35 = 52.8 cents) in the [[Diaschismic family #Shrutar|shrutar temperament]] (22&46)
| |
| * [{{val|3 0 7 18}}, {{val|0 1 0 -2}}] (generator: ~3 = 1909.3 cents) vs [{{val|3 5 7 8}}, {{val|0 -1 0 2}}] (generator: ~16/15 = 90.7 cents) in [[Augmented family #Augene|augene temperament]] (12&15)
| |
| * [{{val|9 1 1 12}}, {{val|0 2 3 2}}] (generator: ~5/3 = 884.3 cents) vs [{{val|9 15 22 26}}, {{val|0 -2 -3 -2}}] (generator: ~36/35 = 49.0 cents) in the [[Ragismic microtemperaments #Ennealimmal|ennealimmic temperament]] (27&45)
| |
| | |
| There are an infinite of mappings of each temperaments including normalized form (left) and minimum generator form (right). In the normalized form, ''a<sub>2</sub>'' in the mapping [{{val|a<sub>1</sub> a<sub>2</sub> a<sub>3</sub> …}}, {{val|0 b<sub>2</sub> b<sub>3</sub> …}}] takes 0 ≤ ''a<sub>2</sub>'' < abs(''b<sub>2</sub>'') if ''b<sub>2</sub>'' ≠ 0. The minimum generator form ("Reduced Mapping" in the [http://x31eq.com/temper Temperament finding scripts] by [[Graham Breed]], taking 0 ≤ ''g'' ≤ ''p''/2 where ''p'' is the period and ''g'' is the generator) can be yielded by Euclidean algorithm. Which form are you favor? --[[User:Xenllium|Xenllium]] ([[User talk:Xenllium|talk]]) 13:48, 29 January 2022 (UTC)
| |
| | |
| : I'm aware of all the normal forms. I participated in the rework on the ''Normal lists'' page, after all (see also the corresponding talk page). The positive generator form is what I prefer, and with ''mapping generators'' showing the corresponding ratios. Reasons? First, Gene has always chosen that form. Second, it makes sense in higher ranks, whereas the minimum generator form doesn't. That said, I'm less sure about the ''POTE generator'' line. This line is more practical and sometimes really used to tune things. I hope octave-reduced form for this line isn't a bad choice. We're used to meantone being generated by fifths, not fourths. We may also add minimum generator form in parentheses when appropriate. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 14:08, 29 January 2022 (UTC)
| |
| | |
| == Reasonable commas extension ==
| |
| | |
| Hi there,
| |
| | |
| I recently stumbled upon your "reasonable commas" page, and I wanted to know a few things:
| |
| - What are/were your motivations for this page?
| |
| - What is the difference between the two definitions on that page?
| |
| - What is the algorithm you used? (as to extend to higher limits)
| |
| | |
| Thank you --[[User:Royalmilktea|Royalmilktea]] ([[User talk:Royalmilktea|talk]]) 07:27, 28 September 2022 (UTC)
| |
| | |
| :> What are/were your motivations for this page?
| |
| : It seems like a good criterion for whether a comma is an efficient one.
| |
| | |
| :> What is the difference between the two definitions on that page?
| |
| : My redefinition is more strict. For example, 135/128 would be a reasonable comma in the original definition cuz none of 129, 130, 131, 132, 133, 134 is 5-limit. In my redefinition 135/128 isn't one since 135/128 = (25/24)(81/80), factored into two simpler commas.
| |
| | |
| :> What is the algorithm you used? (as to extend to higher limits)
| |
| : Dead Shaman somehow generated the lists of commas according to his original definition. I simply checked each comma manually. So unfortunately I don't have an algorithm to share.
| |
| | |
| : [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 05:50, 29 September 2022 (UTC)
| |
| | |
| == Optimal GPV sequence template/module ==
| |
| | |
| Is there a way to actually implement your temperament evaluator python files to find a temperament's optimal GPV sequence into a template on this site for better ease of use? Or for all of your temperament evaluator files? --[[User:Royalmilktea|Royalmilktea]] ([[User talk:Royalmilktea|talk]]) 04:28, 12 October 2022 (UTC)
| |
| | |
| : I have no idea how to implement it in lua. That said, I might make a separate python script for this particular functionality. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 09:37, 12 October 2022 (UTC)
| |
| | |
| == Equivalence continua: fractional n's ==
| |
| | |
| How exactly do you get a rational number from using a fractional exponent? This is mostly for the diaschismic-porcupine continuum page I'm making.
| |
| | |
| --[[User:Royalmilktea|Royalmilktea]] ([[User talk:Royalmilktea|talk]]) 02:52, 30 April 2023 (UTC)
| |
| | |
| : You can get the fractional monzos by adding or subtracting fractional multiples of the ''n'' = infinity monzo from the ''n'' = 0 3-limit base monzo, and then eliminate fractions by lcm-ing it. Btw I have some important comments and plz make sure you read the talk page of that particular page you mentioned. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 09:47, 30 April 2023 (UTC)
| |
| | |
| == Constrained tuning vs. POTE tuning ==
| |
| | |
| I wondered that optimal tunings of some temperaments are indicated by [[Constrained tuning|constrained TE]] (CTE) instead of [[POTE tuning|octave-destretched TE]] (POTE). Why did you update to replace generators POTE to CTE?
| |
| | |
| Temperament generators indicated by CTE tuning:
| |
| | |
| * [[Meantone family]]
| |
| * [[Porcupine family]]
| |
| * [[Augmented family]]
| |
| * [[Hemifamity temperaments]]
| |
| | |
| and so on ... --[[User:Xenllium|Xenllium]] ([[User talk:Xenllium|talk]]) 08:36, 3 May 2023 (UTC)
| |
| | |
| : The community (at least the part from Discord) have generally agreed that CTE is a more logical tuning. It's planned that most of the RTT pages will be eventually updated to CTE. [[User:FloraC|FloraC]] ([[User talk:FloraC|talk]]) 10:24, 3 May 2023 (UTC)
| |
|
This page has associated archive pages:
|
Higher primes
A while back I made an edit on 181edo, saying it has less than 30% error on most prime harmonics up to 137. You removed this info, giving the edit summary "don't bombard the readers with random prime numbers. 30% unsigned error isn't even special." There is a similar section on the page for 43edo, which goes as follows:
Although not consistent, 43edo performs quite well in very high prime limits. It has unambiguous mappings for all prime harmonics up to 113 (after which the demands on its pitch resolution finally become too great), with the sole exceptions of 23, 71, 89, and 103, making a great Ringer scale.
Here, prime 41 with 37.5% relative error is considered "unambiguous". Four missing primes in the 113-limit isn't really too special with this rather relaxed bound. You may want to do something about this section, though maybe more can be kept as 43edo is smaller than 181.--Overthink (talk) 22:52, 12 January 2026 (UTC)
- Originally, this part read:
Although not consistent, it performs quite decently in very high limits. It has unambiguous mappings for all prime harmonics up to 64 [61], with the sole exceptions of 23 and, perhaps, 41.
- Then some editor was being crazy about it cuz four exceptions are no sole exceptions. But I don't think I'm gonna remove that entirely. Rather, I'm moving it to a higher-limit JI subsection of the approximation to JI section to hopefully declutter the theory section.
- —FloraC (talk) 10:36, 13 January 2026 (UTC)
2187/1250
I’m planning to draft a page for 2187/1250 in my userspace since it’s a 5-limit ratio closely approximating 7/4, but I think I should name it something. Something like 5-limit harmonic-esque seventh or something referencing the ragismic temperament since it’s 4375/4374 below 7/4. Do you have any name suggestions? hotcrystal0 19:12, 14 January 2026 (UTC)
- Tetraptolemaic diminished seventh. —FloraC (talk) 20:09, 14 January 2026 (UTC)
Generator counts
I'm planning to start another chord page draft at User:Overthink/Chords of pajara (not yet created as of the time this is written). The issue is that it's not as simple to give a chord by generator counts, as there's a half-octave period in pajara. The page Unidec/Chords uses a val, but it is quite messy. I propose the following solution: The half-octave is taken as the period, and the generator is a perfect fifth. Intervals reachable by stacking fifths are just written with a number; for example, 1–3/2–12/7 would be "0–1–3". An interval that requires stacking fifths from the half-octave would be written with "T" (for tritone) before the number of fifths stacked; for example, 1–6/5–3/2 would be written as "0–T3–1". Maybe it would be better to give an "R" (for root) before intervals reachable by stacking fifths, so that 1–6/5–3/2 would be "R0–T3–R1", which is more readable. I'm also not too sure if the fifth should be the generator or the semitone instead.--Overthink (talk) 01:28, 20 January 2026 (UTC)
- I have to say I'm influenced by hkm's usage of an apostrophe to denote an offset by a period, so in that scheme, 1–6/5–3/2 can be written as "0–'3–1". I feel it looks fairly clean, not too intrusive, at least for temps with a semi-octave period. I think the generator should be taken as the fifth, not the semitone, cuz it's easier to think of the temp as two chains of fifths offset by a semi-octave. —FloraC (talk) 09:29, 20 January 2026 (UTC)
- Hm... Maybe placing the apostrophe after the number is more readable. This way 1–6/5–3/2 will become "0–3'–1", and the number coming first is more readable, plus it will be read as "3 prime" which fits better with math notation.--Overthink (talk) 21:39, 20 January 2026 (UTC)
- Good point. —FloraC (talk) 11:49, 21 January 2026 (UTC)
[-37 0 0 0 0 10⟩
Does there exist a page for the [-37 0 0 0 0 10⟩ comma, or the difference between 10 13/8s and 7 octaves? hotcrystal0 16:24, 20 January 2026 (UTC)
- As you can see in Small comma page, the comma was named the valerisma, and no articles exist for it. —FloraC (talk) 16:28, 20 January 2026 (UTC)
Odd prime sum limit notability
I noticed that you removed the mentions of odd prime sum limit records I made from a couple of edo pages. Is it too arbitrary of a metric for prime approximation to be mentioned on these pages? If so, how is it different in this regard from Pepper ambiguity (still mentioned on the 270edo page)?
- I do take issue with Pepper ambiguity specifically when the intervals involve inconsistency, but as the information have been there for a long time I don't feel like removing them. —FloraC (talk) 11:46, 29 January 2026 (UTC)
- P.S. pls remember to sign your comment with
~~~~.
EDO impressions
In your EDO impressions for 36edo you mentioned adding “third tones”, even though the correct term here would be “sixth tones”. Can you fix that? hotcrystal0 18:16, 29 January 2026 (UTC)
- Fixed. —FloraC (talk) 20:23, 29 January 2026 (UTC)
Tetracot
On the page Tetracot extensions, you suggested splitting it into four pages: Monkey, Bunya, Modus, and Wollemia. Tetracot splits the apotome into four comma steps. It maps 5/4 to the vM3, 11/8 to the sA4, and 13/8 to the n6. The main tetracot edos are 27edo (27e val for prime 11), 34edo, and 41edo. These extensions differ is the mapping of prime 7:
Monkey (34 & 41): 7/4 is vm7
Bunya (34d & 41): 7/4 is sA6
Modus (27e & 34d): 7/4 is m7
Wollemia (27e & 34): 7/4 is ^A6
I've noticed that in 27edo the pythagorean thirds are quite clearly supermajor/subminor, and the 5-limit thirds are quite far from each other, with 5/4 being the same 400 ¢ major third as in 12edo, and 6/5 being slightly flat at 311.1 ¢. 34edo makes 5/4 and 6/5 both about equally sharp, and the pythagorean thirds are mapped as in 17edo. 41edo maps the pythagorean thirds close to just, but the 5-limit thirds are slightly closer to neutral as a result. In any case, intervals of 11 and 13 are mapped to neutral intervals. The way I tend to think of tetracot is as a tertian structure (like keemic).
Monkey and modus map 7/4 to a 7th (they are supported by the 7edo patent val). The tertian structures of 27edo and 41edo are quite clearly different, while 34edo is somewhat similar to both (though IMO closer to 27edo as 34d is better than patent 34). Here 34d&27 is modus, while 34&41 is monkey. They are quite clearly different, as modus sets the pythagorean thirds to septimal ones while pental thirds are halfway between the septimal thirds and neutral ones. Monkey, on the other hand, distinguishes the pythagorean thirds from pental and septimal ones, and sets them equidistant from pental and septimal thirds.
Bunya and wollemia, on the other hand, map 7/4 to a 6th (corresponding to the 7d val). Bunya (34d&41) maps 7/4 to a sA6, so that 28/27 is equated with 33/32 as an sA1, as in parapyth. This sets the pythagorean major third to 14/11, and 9/7 to an sd4 instead. Bunya also tempers out 225/224, so that 7/4 is equated with the 225/128 augmented 6th, which in tetracot is a vvA6 = sA6. Wollemia (27e & 34), on the other hand, is quite strange. It tunes the fifth so that the pythagorean intervals are close to septimal intervals, but doesn't actually map them to septimal intervals. Instead, 28/27 is mapped to a ^1, so 9/7 is a v4, and 7/6 is a ^A2. Optimal tunings of wollemia are close to optimal tunings of modus, but doesn't temper out 64/63, instead equating septimal supermajor/subminor intervals to tridecimal ultramajor/inframinor intervals via tempering of 91/90. In wollemia 14/11 is also mapped to the same interval as 5/4, and 11/8 the same interval as 7/5. I'm not too sure of the significance of this yet, besides that both the 27e and 34 vals contain these equivalences.
In any case, I suggest you add a 7et detemperament section to the Tetracot article.
--Overthink (talk) 23:45, 13 February 2026 (UTC)
- Sure. —FloraC (talk) 13:39, 14 February 2026 (UTC)
About schismina
What's the deal with the schisminic temp? It is 2.3.5.7.13, there's no 11. Also, I would deem the differences I outlined are notable, because they show how many simple ratios of 35 have tiny differences with tridecimal equivalents and viceversa. Specially 8505/8192, whose pressence in Sagittal pretty much assumes that the schismina is either tempered out or fudged. It's that important of a schisma, we have to sell it as such! --Eufalesio (talk) 17:05, 22 February 2026 (UTC)
- > What's the deal with the schisminic temp? It is 2.3.5.7.13, there's no 11.
- That's why schismina isn't a great name for the comma; there's no room to distinguish the minimal-prime-subgroup temp and the full-prime-limit temp according to our rules. I've proposed something else in Talk: 4096/4095.
- > I would deem the differences I outlined are notable.
- I think there's a problem in how you present your ideas. If all you wanna discuss is the merge of intervals of 13 with intervals of 35, add that instead. A pair of ratios may serve as an example, but the entire point is in the context. The ratios alone which comprise three- or even four-digit ones aren't notable cuz no one uses them in music.
- —FloraC (talk) 17:33, 22 February 2026 (UTC)
Thanks
Hello Flora, how are you today? I see you corrected some mistakes I unwittingly made when editing MOS pages, for example, when I called 2L 17s a MOS of Pycnic temperament and you took it out, noting that 2L 17s is actually tritonic temperament. So, I just wanted to say thank you, and I will double-check my edits in the future. MisterShafXen (talk) 17:28, 6 May 2026 (UTC)