it will internally in KontrolModule still be using the same name as the duplicated module…
this may cause an issue as KontrolRack and KontrolModule will be using different names, Im not sure what if any issues that will cause, as its a use-case ive not tested, and would not consider a bug.
that said, I will look at the where the module name is currently being used, im pretty sure I can remove it from module.json … ideally id remove it from module.pd too (so the module name is purely defined by the subdirectory) , but that is a bit more problematic… and whilst it suits orac, its not ideal for Kontrol.
you need to carefully delete everything from the preset name to the end of that section
BUT back it up before making any changes, its easy to get this wrong, then none of the presets will load.
basically its something like
{
"presets" : {
"preset1" : {
/// blah blah blah
},
"preset2" : {
/// blah blah blah
},
"preset3" : {
/// blah blah blah
}
}
you need to change too.
{
"presets" : {
"preset1" : {
/// blah blah blah
},
"preset3" : {
/// blah blah blah
}
}
the key thing is to find the correct }, if you get the wrong one you will break it, and the file will refuse to load.
but its not too difficult if your careful since the file is correctly indented.
special note: there is a comma between each preset but none on the last one, so if you remove the last preset, then you need to make sure there is no comma on the last line for the preceding preset.
for more information, you can google ‘json file format’ and find an explanation on how json files are formatted.
(sorry, I dont have enough time to give a more detailed walkthrough of this, hopefully this will point you in the right direction)
If 
