Xenoindex
Joined 19 January 2021
→Table usability: new section |
thank |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 26: | Line 26: | ||
::::: Oh, and as for your question as to whether this chain of primes is JI primes or each respective EDO's patent val primes, given that we're working with EDOs, it follows that the 2-prime is just, though for everything else... well... let's say [[49/32]] is "r", since this interval is made by stacking two instance of [[7/4]] then octave-reducing. There's a difference between say, the direct mapping of your example interval (represented by the right side of the equation), which is the step of the EDO that most closely approximates the just interval in question, and the patent-val-based traditional mapping of that same interval (represented by the left side of the equation), which depends on the mapping generated by stacking multiple instances of the EDO's best approximation of the patent prime interval and octave reducing. The equation tests to see if the results of both of these mappings are identical (indicated by the equation being "true") or not. From there, the only way I can think of to answer that is to say that you need to study the definition of "telicity" itself. Does this make sense? --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 14:41, 25 January 2021 (UTC) | ::::: Oh, and as for your question as to whether this chain of primes is JI primes or each respective EDO's patent val primes, given that we're working with EDOs, it follows that the 2-prime is just, though for everything else... well... let's say [[49/32]] is "r", since this interval is made by stacking two instance of [[7/4]] then octave-reducing. There's a difference between say, the direct mapping of your example interval (represented by the right side of the equation), which is the step of the EDO that most closely approximates the just interval in question, and the patent-val-based traditional mapping of that same interval (represented by the left side of the equation), which depends on the mapping generated by stacking multiple instances of the EDO's best approximation of the patent prime interval and octave reducing. The equation tests to see if the results of both of these mappings are identical (indicated by the equation being "true") or not. From there, the only way I can think of to answer that is to say that you need to study the definition of "telicity" itself. Does this make sense? --[[User:Aura|Aura]] ([[User talk:Aura|talk]]) 14:41, 25 January 2021 (UTC) | ||
Hi! You have some neat things here, wow! --[[User:Arseniiv|Arseniiv]] ([[User talk:Arseniiv|talk]]) 17:21, 11 October 2021 (UTC) | |||
: Thank you! come join us on the discord server if you wanna chat about it (linked in the side bar under connect). --[[User:Xenoindex|Xenoindex]] ([[User talk:Xenoindex|talk]]) 18:16, 11 October 2021 (UTC) | |||
== Table usability == | == Table usability == | ||
I doubt that [[NEJI Tables/Average Error]] or [[NEJI Tables/Greatest Error]] will be of high value to readers. Did you ever try to view the information (about 41EDO) on a mobile device? I think it would be better to provide some examples for illustration and some script (or pseudo code) that would enable readers to get the specific information they want. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 22:19, 27 June 2021 (UTC) | I doubt that [[NEJI Tables/Average Error]] or [[NEJI Tables/Greatest Error]] will be of high value to readers. Did you ever try to view the information (about 41EDO) on a mobile device? I think it would be better to provide some examples for illustration and some script (or pseudo code) that would enable readers to get the specific information they want. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 22:19, 27 June 2021 (UTC) | ||
: Several XA Discord users have expressed to me the immediate usefulness of these tables. They're meant to be accessed on a PC where a user can select which EDO they want a NEJI of from the table of contents then copy and paste different scales to try. But I understand if you deem it necessary to remove them. --[[User:Xenoindex|Xenoindex]] ([[User talk:Xenoindex|talk]]) 00:19, 28 June 2021 (UTC) | |||
:: There is no need to remove tables ''if'' they are helpful. But maybe it would be good to ask (on XA Discord) which specific parts are useful. We already have a lot of tables that try to be complete in an area where completeness is impossible. I see a problem in long static pages, when most users wait for them to load, only to find afterwards that the content is (for the most part) irrelevant to them. Isn't this exactly the occasion for a dynamic web application where users can specify exactly what kind of data they want? --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 08:11, 28 June 2021 (UTC) | |||
:: BTW: which code/script are you using? Wouldn't it make sense to add it as well? --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 08:13, 28 June 2021 (UTC) | |||
::: I've shortened the tables by about half, I hope this is adequate. And my code is written in SuperCollider, I suppose I could upload the source but I can't imagine the intersection of SuperCollider users and NEJI users is very large. --[[User:Xenoindex|Xenoindex]] ([[User talk:Xenoindex|talk]]) 08:53, 28 June 2021 (UTC) | |||
:::: In that case I think it would help to show the core algorithm to get the NEJIs that correspond to EDOs. This could also be in [[wikipedia: SuperCollider| SuperCollider]]: <div><!-- don't break line here --><syntaxhighlight lang="sc"> | |||
// Print "Hello world!" | |||
"Hello world!".postln; | |||
</syntaxhighlight><!-- don't break line here --></div> we have syntax highlighting for it (<code>lang="sc"</code>). Maybe someone will be able to translate it into [[Python]], [[JavaScript]], [[Lua]] or whatever. --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 13:33, 28 June 2021 (UTC) | |||