User:Eufalesio/PLIN: Difference between revisions

Eufalesio (talk | contribs)
No edit summary
Eufalesio (talk | contribs)
No edit summary
 
Line 19: Line 19:


== PLIN ==
== PLIN ==
Short for '''Pythagoreanoid Loose Interval Notation''', it's a type of [[2.3-equivalent class and Pythagorean-commatic interval naming system|2.3-equivalent class]]. It attempts to provide precision tiers to name intervals, based on a chain of '''pure''' fifths. The reason of why to use a chain of fifths, apart from tradition and my biases, is that it provides the simplest framefork for building scales, and because it is the most widely used worldwide. Why to use pure fifths and not an edo's best approximation of a fifth is to have a retrocompatible sistem. Among the lower primes, it makes the best small MOS scales (2,3,5,(7),12,(17),(29),41,53), second in place to 11 (2,5,(7),(9),11,13,24,37). An argument could be made to make a system based on 11 to build scales, but that's beyond the scope of this article. After all, this is about a ''pythagoreanoid'' notation, not a ''hendecoid'' notation.
Short for '''Pythagoreanoid Loose Interval Notation''', it's a type of [[2.3-equivalent class and Pythagorean-commatic interval naming system|2.3-equivalent class]]. It attempts to provide precision tiers to name intervals, based on a chain of '''pure''' fifths. The reason of why to use a chain of fifths, apart from tradition and my biases, is that it provides the simplest framefork for building scales, and because it is the most widely used worldwide.  
 
Why use pure fifths and have unequal sized buckets? For retrocompatibility. If I equalize the buckets, the fifth changes, and the buckets also change. Most intervals will be the same, but for higher precisions, the buckets will change. It isn't desirable for an interval to be a minor sixth in one precision and then a major sixth in another.  
 
Among the lower primes, it makes the best small MOS scales (2,3,5,(7),12,(17),(29),41,53), second in place to 11 (2,5,(7),(9),11,13,24,37). An argument could be made to make a system based on 11 to build scales, but that's beyond the scope of this article. After all, this is about a ''pythagoreanoid'' notation, not a ''hendecoid'' notation.


The notation, much like Sagittal, comes in precision packs, which are the 12-form PLIN, 53-form PLIN, 159-form PLIN, 665-PLIN and 7315-form PLIN. The reason why to have these numbers of intervals is that they are part of the sequence of 3-2 telic edos that have high limit consistencies, and the biggest they can be. Each finer PLIN adds one more class of independent prefixes, from the others, having one (nominals) with 12-PLIN, and up to 5 with 7315-PLIN, which for some intervals will become hard to distinguish.
The notation, much like Sagittal, comes in precision packs, which are the 12-form PLIN, 53-form PLIN, 159-form PLIN, 665-PLIN and 7315-form PLIN. The reason why to have these numbers of intervals is that they are part of the sequence of 3-2 telic edos that have high limit consistencies, and the biggest they can be. Each finer PLIN adds one more class of independent prefixes, from the others, having one (nominals) with 12-PLIN, and up to 5 with 7315-PLIN, which for some intervals will become hard to distinguish.
Line 30: Line 34:
PLINs generate regions whose center correspond to a pure pythagorean interval generated by the chain-of-fiths,  For example, there are infinite minor sixths, no matter how much you narrow the buckets, but there is ''only'' one true minor sixth, and that is 128/81.
PLINs generate regions whose center correspond to a pure pythagorean interval generated by the chain-of-fiths,  For example, there are infinite minor sixths, no matter how much you narrow the buckets, but there is ''only'' one true minor sixth, and that is 128/81.


Any single region has infinite intervals represented in it, and thus it is important to distinguish the breadth of the buckets any JI interval can fall into. So, while there are an infinite amount of minor thirds, and of superminor thirds, and of qu superminorthirds, and of twomins qu superminor thirds, all of them will 6/5; with 12-PLIN being quite rough, 53-PLIN being very accurate, and 665-PLIN and 7315-PLIN further refining the accuracy to extreme levels to the point where all of those will sound indistinguishable from 6/5, since the difference will be only of 0.16 c per region in 7315-PLIN.
Any single region has infinite intervals represented in it, and thus it is important to distinguish the breadth of the buckets any JI interval can fall into. So, while there are an infinite amount of minor thirds, and of superminor thirds, and of qu superminorthirds, and of twomins qu superminor thirds, all of them will converge towards 6/5; with 12-PLIN being quite rough, 53-PLIN being very accurate, and 665-PLIN and 7315-PLIN further refining the accuracy to extreme levels to the point where all of those will sound indistinguishable from 6/5, since the difference will be only of 0.16 c per region in 7315-PLIN.


12-PLIN, 53-PLIN and 665-PLIN are MOSses, more concretely, 5L 7s 6|5 1.260, 41L 12s 26|26 H=1.1822, and 306L 359s H=1.0427, but 159-PLIN and 7315 are not, as they modify the two last MOSses respectively with fractions of the telic commas. As such, to make things easier, '''EPLIN'''s may be used to have exactly equal regions, which will make things easier to work with. by default, PLINs are not equal, so it needs to be specified when an equalized PLIN is being used, because it can change the region an interval falls into. For example, 31/16 is a rough octave, but in 12-EPLIN, a '''eq'''rough major seventh. 7/4 is a fixsubminor seventh, but in 159-EPLIN, an '''equwee'''subminor seventh.  
12-PLIN, 53-PLIN and 665-PLIN are MOSses, more concretely, 5L 7s 6|5 1.260, 41L 12s 26|26 H=1.1822, and 306L 359s H=1.0427, but 159-PLIN and 7315 are not, as they modify the two last MOSses respectively with fractions of the telic commas. '''EPLIN'''s may be used to have exactly equalized buckets, which could make things easier to work with. by default, PLINs are not equal, so it needs to be specified when an equalized PLIN is being used, because it can change the region an interval falls into. For example, 31/16 is a rough octave, but in 12-EPLIN, an eqrough ''major seventh''. 7/4 is a fixsubminor seventh, but in 159-EPLIN, an eq''wee''subminor seventh.  


One glaring design feature about PLINs is the lack of ''neutral'' categories, and of ''augmented'', ''diminished'' and ''perfect''. The reason to avoid those is that for one, true neutral intervals do not exist in integer pythagorean, but even if they did, using this term is unnecessary. 11/9 is commonly called a neutral interval, but it is closer to a minor third. So it is roughly a minor third. More precisely a hyperminor third, at the extreme of minor thirds. Same thing applies to the interordinals like chthonics, naiadics, cocytics and ouranics. You can do fine with using hyper/hypo to refer to them at the edges of the nominals. All of this ''sonically speaking''.
One glaring design feature about PLINs is the lack of ''neutral'' categories, and of ''augmented'', ''diminished'' and ''perfect''. The reason to avoid those is that for one, true neutral intervals do not exist in integer pythagorean, but even if they did, using this term is unnecessary. 11/9 is commonly called a neutral interval, but it is closer to a minor third. So it is roughly a minor third. More precisely a hyperminor third, at the extreme of minor thirds. Same thing applies to the interordinals like chthonics, naiadics, cocytics and ouranics. You can do fine with using hyper/hypo to refer to them at the edges of the nominals. All of this ''sonically speaking''.


For two, is 11/9 a minor third or a major third? Or 13/10 a major third or a fourth? That depends on how you treat it. Augmented/diminished, and '''chromas''' have the same logic in that they are '''''functional''''' in this system. Using ''perfect'' is also redundant and ambiguous, so use different coinages to refer specifically to the centers of regions of the different PLINs. An interval is not a chroma, but rather, '''''works''''' as a chroma. When you are dealing with intervals inside a scale and a piece, it may be useful to refer to 25/16 as an augmented fifth, but '''sonically''' speaking, it is a rough minor sixth. Or a hypominor sixth. Or a mi hypominor sixth. Or a fourplus mi hypominor sixth... you get the point.  
For two, is 11/9 a minor third or a major third? Or 13/10 a major third or a fourth? That depends on how you treat it. ''Augmented/diminished'', and ''chromas'' have the same logic in that they are '''functional''' in this system. Using ''perfect'' is also redundant and ambiguous, so use different coinages to refer specifically to the centers of regions of the different PLINs. An interval is not a chroma, but rather, '''works''' as a chroma. When you are dealing with intervals inside a scale and a piece, it may be useful to refer to 25/16 as an augmented fifth, but '''sonically''' speaking, it is a rough minor sixth. Or a hypominor sixth. Or a mi hypominor sixth. Or a fourplus mi hypominor sixth... you get the point.  


Also, no words for other primes. So no ptolemaic/pental/classical, septimal, undecimal... etc. Everything stays in the 3-limit. Minimum complexity, reducing the amount of classes and descriptors to worry about to the absolute minimum.
Everything stays in the 3-limit. Minimum complexity, reducing the amount of descriptors to worry about to the absolute minimum.  


Regarding the choice of words to refer to the descriptors; you might not agree about the use of hypo/hyper, or wee/wide, or qi/qu, or mi/mu, or n-plus/n-minus; but that's only a semantics problem. I chose those names because they kind of make sense to me, but the rigor is in the system, because you have these commas in the k-strong 3-2 telic sequence:
Regarding the choice of words to refer to the descriptors; you might not agree about the use of hypo/hyper, or wee/wide, or qi/qu, or mi/mu, or n-plus/n-minus; but that's only a semantics problem. I chose those names because they kind of make sense to me, but the rigor is in the system, because you have these commas in the k-strong 3-2 telic sequence:
Line 49: Line 53:
* Sasktel comma elevenths ([0~5]plus/[0~5]-minus) Available '''only''' in 7315-PLIN [spot
* Sasktel comma elevenths ([0~5]plus/[0~5]-minus) Available '''only''' in 7315-PLIN [spot


The choice of giving no center descriptor to 53-PLIN is that I believe that for the average xennie, 53 regions is precise enough to accurately name most intervals, and simple enough that the regions cannot be confused.
The choice of giving no center descriptor to 53-PLIN is that I believe that for the average xennie, 53 regions is precise enough to accurately name most intervals, and simple enough so that the regions cannot be confused.


Of course, the names would have many synonyms, so hypo/hyper = infra/ultra, minor second = limma, major second = tone, unison = prime, major third = ditone. Extending my rules; apotome = superminor second; superlimma.  
Of course, the names would have many synonyms, so hypo/hyper = infra/ultra, minor second = limma, major second = tone, unison = prime, major third = ditone. Extending my rules; apotome = superminor second; superlimma. Alternatively you could use the [[User:Eufalesio/Punctional Just System#Punny names|Punny names]], to save yourself some syllables.  


==== Syntax of a PLIN ====
==== Syntax of a PLIN ====
Line 635: Line 639:
None of the PLINs from this point on will be MOS, as it is much more retrocompatible and feasible to alter by fractions of a pythagorean comma than to make a multiperiod MOS scale. It's just not worth the mental gymnastics.
None of the PLINs from this point on will be MOS, as it is much more retrocompatible and feasible to alter by fractions of a pythagorean comma than to make a multiperiod MOS scale. It's just not worth the mental gymnastics.
{| class="wikitable"
{| class="wikitable"
|+ 159-PLIN; 41L 12s 26 |159-PLIN up to the first major second; MOS 41L 12s 26|26; tolerance = '''3.91c'''
|+ 159-PLIN; 41L 12s 26 |159-PLIN up to the first fixmajor second; MOS 41L 12s 26|26; tolerance = '''3.91c'''
!Spoken name
!Spoken name
!Simplified
!Simplified
Line 1,474: Line 1,478:
* kirn- for Atomic (Kirnberger's atom)
* kirn- for Atomic (Kirnberger's atom)
* pir- for Pirate
* pir- for Pirate
The only ones of this EPLINs that can use the mercator comma are 2460-EPLIN and 6079-EPLIN, as the sizes aren't too dissimilar and/or inconsistent. Yes, 42%, 69% error, but in all other EPLINs it is wildly out of shape, in some even negative!
Examples:
{| class="wikitable"
|+
!
!94-EPLIN
!130-EPLIN
!311-EPLIN
|-
|5/4
|garsubmajor third
|spensubmajor third
|vlussubmajor third
|-
|7/4
|garsubminor seventh
|hinssubminor seventh
|vusubminor seventh
|-
|11/8
|garhyperfourth
|slushyperfourth
|vuhyperfourth
|-
|13/8
|garhyperminor sixth
|slushyperminor sixth
|vlushyperminor sixth
|}
WIP