none 2/1 microtunings - scala file import problem
Posted on 03 Jul 2021, 02:59 PMhave just been loading in some none 2/1 based tunings and i get a problem of notes resetting to further down the keyboard. an example tuning enclosed from the scala library, reproduced below. as you can see it has 21 notes, with the repeating of the tuning appearing at 4/1. from what i can tell from a brief look, it seems to reset to 2/1 after each set of 21 notes.
Heinz Bohlen, mode of 4\47 (1998), www.huygens-fokker.org/bpsite/pythagorean.html
there are a lot of tunings out there that dont use 2/1 as the repeat. see also some the tunings of wendy carlos alpha tuning excerpted from the scala scale library below, this also has the same problem.
Wendy Carlos' Alpha scale with perfect fifth divided in nine
another useful tuning as a check case is the fixed 1/1 tuning. this also loads incorrectly, but in a different way to the others. if you go into advanced mode it is easy to see that instead of computing the same value for all the notes [which should be the master tuning value], it diverges from 0Hz to a frequency value of 42949672.42Hz. this is the scala file to check :
fixed note tuning of 1/1 across whole keyboard
there is possibly also going to be problems with tunings using repeats at values less than 2/1 if this problem is occurring with the above fixed 1/1 tuning.
Posted on 03 Jul 2021, 03:09 PMThis might explain the problems I'm finding with transposing layers.
Posted on 04 Jul 2021, 07:56 PMOnly 2/1 scales are supported as indicated here https://kodamo.org/tutorials.php?id=7
May be improved in the future although it is rarely used
Posted on 05 Jul 2021, 11:53 AMOh no!😢😱
Some of the most interesting tunings in the universe are not 2/1, I think this now explains the problems I was having with the patch layer transpose now.
Basically FULL microtuning is not implemented, damn!
Please Kodamo can you implement this otherwise its really half baked and the Essence will not be viewed as an amazing microtuning hardware unit which it is SO close to being.
Posted on 05 Jul 2021, 01:12 PMWe'll check how feasible this is.
That's only a limitation for Scala file import, you can still do full microtunings by sending a non-realtime MTS message (full dump - 128 notes) to the EssenceFM then saving the tuning.
Posted on 06 Jul 2021, 04:04 AMok great 👍 thanks for info, will give it a try. it would certainly be handy to have the .scl import work that way as well if possible. i did a batch convert of the scala library to all the output formats including MTS, available here if anyone is wanting to save time
if i'm creating new tunings algorithmically, eg using something like python or mathematica, the scala format is the easiest way to generate & export.
Posted on 08 Jan 2022, 12:15 AMhi
is there any chance the Scala import can be fixed to be inline with full MTS please? i have a lot of files that are .scl only and it would be a massive hassle to convert them all. and as mentioned when generating new tunings [and also when sharing tunings], i suspect most people will make an .scl in the first instance anyway. having this sorted out would massively improve my microtuning workflow on this synth.
Posted on 28 Jan 2022, 06:31 PM+1 for this. Would love to have this flexibility. 🙂
Posted on 29 Jan 2022, 12:36 AM+1 to the fullest
Posted on 05 Feb 2022, 03:12 AMBig +1 for full .scl support
Posted on 12 Mar 2022, 09:53 AM+1 for .scl import being fixed so it mirrors the non-realtime MTS message dump.