Add support for Korg minilogue xd

[rl2939]

Would it be possible to support the Minilogue XD? The reason I ask is because the official editor does not work on Linux.

The Minilogue XD has six things that can be imported/exported off of the device:

• Programs (presets)
• User Oscillators
• Three types of User Effects:
  • Modulation Effects
  • Delay Effects
  • Reverb Effects
• Microtuning (custom scales)

[dagargo]

I own a KORG NTS-1 and based on the official information from here it looks like they are compatible, meaning that they might work with the same SysEx messages and code.

I've already done some tests and tried a few things and listing the oscillators and FX is almost ready. Uploading and downloading will be more difficult but let's start from the beginning.

Regarding the scales, from what I've read, the code might be compatible with the code already existent for the Novation Summit as both seem to use the MIDI standard for scales and scala files, which are stored as text files.

Finally, programs probably use their own SysEx messages and their own program dump request. That's something that might be easy to do as most of the required code is already available but we'll need to find that request message. Renaming usually requires to download, rename in the stored SysEx and upload back, so let's leave this for later on as it's quite complex.

I'd require you to run some tests with your Minilogue XD whenever a type is ready but, at the moment, I'd need you to send these 5 SysEx messages to be sure that both devices behave the same way.

$ amidi -p hw:4,0,0 -S "f0 7e 7f 06 01 f7" -d -t 1
F0 7E 00 06 02 42 57 01 00 00 01 00 14 00 F7
15 bytes read

$ amidi -p hw:4,0,0 -S "f0 42 50 00 55 f7" -d -t 1
F0 42 50 01 00 55 57 01 00 00 01 00 14 00 F7
15 bytes read

$ amidi -p hw:4,0,0 -S "f0 42 30 00 01 57 17 f7" -d -t 1
F0 42 30 00 01 57 47 03 01 01 00 F7
12 bytes read

$ amidi -p hw:4,0,0 -S "f0 42 30 00 01 57 18 01 f7" -d -t 1
F0 42 30 00 01 57 48 01 00 01 74 1F 00 00 00 18 00 00 00 10 00 00 00 F7
24 bytes read

$ amidi -p hw:4,0,0 -S "f0 42 30 00 01 57 19 01 00 f7" -d -t 1
F0 42 30 00 01 57 49 01 00 00 00 01 03 00 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 73 6F 6C 00 61 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 F7
53 bytes read

Notice that the hw:4,0,0 device needs to be this value.

$ amidi -lio | grep NTS
IO  hw:4,0,0  NTS-1 digital kit _ KBD/KNOB

[dagargo]

I've been working on this for some time and uploading is starting to work. It's still a work in progress and no code is still available but it will be during February with any luck.

Not sure if downloading makes any sense in this case. Downloading the item works but returns a SysEx message that needs some work to be sent again.

[rl2939]

Hello,
Thanks for the update.

It's still a work in progress

There is no need to rush, as my Minilogue XD is in another place right now. I'll be able to access to it again within a month or two and I'll run the amidi commands at that time.

[dagargo]

Support for KORG NTS-1 added to branch feat-add-korg-logue.

The SysEx messages are just built around the manifest.json and the payload.bin so it is very likely that the code is gonna be compatible with the Minilogue XD.

This is the struct of the ntkdigunit.

$ unzip -l modfx_sola.ntkdigunit 
Archive:  modfx_sola.ntkdigunit
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  2026-01-14 09:21   modfx_sola/
      245  2024-08-20 21:15   modfx_sola/manifest.json
     1272  2026-01-14 09:06   modfx_sola/payload.bin
---------                     -------
     1517                     3 files
$ unzip -c modfx_sola.ntkdigunit modfx_sola/manifest.json
Archive:  modfx_sola.ntkdigunit
  inflating: modfx_sola/manifest.json  
{
    "header" :
    {
        "platform" : "nutekt-digital",
        "module" : "modfx",
        "api" : "1.1-0",
        "dev_id" : 0,
        "prg_id" : 0,
        "version" : "1.0-0",
        "name" : "sola",
        "num_param" : 0
    }
}

In order to reverse engineer the official tool logue-cli, I've used black box TDD based on some ntkdigunit files that I created myself for the NTS-1, so that running more tests on other devices is required. For anyone that might be interested in this, it would be nice if you could give it a try.

I'll probably borrow a Minilogue XD during the following weeks but I can't promise anything.

[henning]

hey !

found this by your link in the logue-cli issue 37!

i have a minilogue xd module and can happily offer to try things out!

are the messages from 2 months ago still valid or do you need something else that i can run and send you the results?

(btw great! i haven't looked at elektroid since a while and it's fantastic that you support so many devices, of which i own a few!! especially Microfreaks normal management tool is so horrible, looking forward to replace it with something sane!!!)

[dagargo]

are the messages from 2 months ago still valid or do you need something else that i can run and send you the results?

Honestly, I don't know which messages are you talking about. I'm very forgetful so...
Anyway, since the code was pushed during the weekend I think you could give a try to the feat-add-korg-logue branch and report back.

Theoretically, SysEx messages are exactly the same, or so I remember from the official KORG MIDI implementation charts. If something doesn't, then we'll start checking things with the CLI to get some logs.

[henning]

i was meaning to refer to the comments in this issue like from Jan 12 „ I'd require you to run some tests with your Minilogue XD…“ - it sounds like an advice for possible tester volunteers ;)

but fine - I’m gonna look at the branch these days!

[dagargo]

Sorry, I didn't understand you.

Yes. Back then, I meant that I was gonna need some help in the future. Now that the code is ready, it's time to put it to test against the Minilogue XD. 🚀

[henning]

before testing the minilogue xd i tried with my nts-1 as i understood this is what you have yourself and should already work.

but i dont know what to do with this view after chosing the NTS-1 in the selection menu on the right:

the NTS-1 has no programs and even all units together dont sum up to 127... these "files" can also not be moved or opened by clicking or something.

I also checked the cli:

$ ~/.local/bin/elektroid-cli ld
0: id: SYSTEM_ID; name: ultraframe
1: id: hw:0,0,0; name: hw:0,0,0: Steinberg UR22C MIDI 1
2: id: hw:0,0,1; name: hw:0,0,1: Steinberg UR22C MIDI 2
3: id: hw:3,0,0; name: hw:3,0,0: NTS-1 digital kit _ KBD/KNOB
4: id: volca-sample; name: KORG Volca Sample

$ ~/.local/bin/elektroid-cli info 3 
Type: MIDI
Device name: MIDI device
Device version: 1.0.20.0
Device description: 
Connector name: default
Filesystems: program

I checked this same behaviour on two machines, also where logue-cli works for me.

[dagargo]

If you're seeing that it is because the compiled code is not the branch or I didn't pushed the code correctly. Check again if you're in the aforementioned branch.

You can know this because Elektroid is using the "default" connector and showing the only filesystem available in it, which is "Programs". Also, at the right bottom corner, the device is identified with the generic name "MIDI device" which is also shown by the CLI.

[henning]

argh sorry you're right...

NTS works fine, also upload/download - even on a machine where logue-cli didn't work!

minor things: it crashes when i accidentally drag an empty slot into my local folder.
and the downloaded .syx files could be named like the patch :)

[henning]

But the behavior for Minlogue-XD is like the above screenshot from NTS: it only shows 127 programs that dont react on anything.

$ ./src/elektroid-cli ld
0: id: SYSTEM_ID; name: x1e-debian
1: id: hw:2,0,0; name: hw:2,0,0: Launch Control XL Launch Contro
2: id: hw:2,0,1; name: hw:2,0,1: Launch Control XL HUI
3: id: hw:3,0,0; name: hw:3,0,0: NTS-1 digital kit _ KBD/KNOB
4: id: hw:4,0,0; name: hw:4,0,0: Elektron Model:Samples MIDI 1
5: id: hw:5,0,0; name: hw:5,0,0: minilogue xd _ MIDI IN
6: id: hw:5,0,1; name: hw:5,0,1: minilogue xd _ KBD/KNOB
7: id: hw:6,0,0; name: hw:6,0,0: Arturia MicroFreak
8: id: volca-sample; name: KORG Volca Sample

$ ./src/elektroid-cli info 6
Type: MIDI
Device name: MIDI device
Device version: 2.0.10.0
Device description: 
Connector name: default
Filesystems: program

let me know what else you'd like to see!

by the way Microfreak tested, works great, thanks!!! :=)

[dagargo]

NTS works fine, also upload/download - even on a machine where logue-cli didn't work!

Great! We're on the right track!

minor things: it crashes when i accidentally drag an empty slot into my local folder.

Thanks for reporting this. Definitely, it needs more testing and I'll add some integration tests too.

and the downloaded .syx files could be named like the patch :)

At the moment, the downloading process stores what the devices return and tweaks it into something that can be sent back. The ideal goal would be to convert this to the same unit formats the compiler generates but this requieres some work and I'm not sure if it's worth the effort. Extracting the name only is possible too and easier.

Post here the output of the elektroid-cli info 6 -vv command because it might be the handshaking process causing the device to not being recognised.