Talk:Functional Just System: Difference between revisions
→How to name a pythagorean interval: re + re |
|||
| Line 8: | Line 8: | ||
::: Well, Aura, to my knowledge this is a limitation of the FJS itself. If I remember correctly, FloraC has done research in this... --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 12:53, 29 November 2020 (UTC) | ::: Well, Aura, to my knowledge this is a limitation of the FJS itself. If I remember correctly, FloraC has done research in this... --[[User:Xenwolf|Xenwolf]] ([[User talk:Xenwolf|talk]]) 12:53, 29 November 2020 (UTC) | ||
::: I recently read that page too! I think FloraC even suggested another tolerance radius to rename some intervals. Aura maybe that one will work better for your vision of 2.3.11 intervals too? As of SHEFKHED, that one looks interesting and maybe I would take myself up to trying to implement it, but as at first glance it’s indeed very sophisticated, and as it also names only edostep intervals, that may prove being hard to do. If I’ll end up with some algorithm sounding simpler than at [[SHEFKHED interval names]], I’ll let you know! --[[User:Arseniiv|Arseniiv]] ([[User talk:Arseniiv|talk]]) 15:04, 29 November 2020 (UTC) | |||
:: I fixed my algorithm, now it correctly names [[2048/2187]] as d1, [[2187/1024]] as A8, 1073741824/1162261467 as dd2, [[531441/262144]] as A7, 2/3 as P−5 etc.. My troubles were with correctly calculating octave shift: at first I just took <math>\lfloor \log_2 \mathrm{interval} \rfloor</math>, but that’s wrong because Cb is still the same octave as C, but one octave lower with this definition, and B# would be determined as one octave higher. Now it all works, though I need to make one part look nicer. --[[User:Arseniiv|Arseniiv]] ([[User talk:Arseniiv|talk]]) 15:04, 29 November 2020 (UTC) | |||