Notifications
Clear all

Korg nanoKontrol 2 text file ???


Zorzi
(@zorzi)
Eminent Member
Joined: 11 months ago
Posts: 21
Topic starter  

Hi, I have just seen John's last video about Unify 1.2 and I did not understand what's about this text file somewhere.

I have a Korg NanoKontrol and I am badly interested with this new possibility : how to use it in Unify please ?


Quote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2850
 

@zorzi

Sorry to have kept you waiting. I have just completed documenting this feature in the Unify manual at https://pluginguru.net/unify/manual/doku.php?id=midi-controller-files.

To get you started more quickly, I have prepared a special .guru file which you can download from https://www.dropbox.com/s/4pf0gz7npmnouhu/NanoKontrol2.guru?dl=0. Drag/drop this file onto the Unify GUI, and it will create a MIDI Controller Files folder in the right location, with a controller file for the KORG nanoKONTROL2 inside it.

Please note that computer systems vary greatly, and the sample controller file may not work as-is on your system, so read the manual section carefully and make changes as required.


Nico Fyve liked
ReplyQuote
mschiff
(@mschiff)
Member
Joined: 1 year ago
Posts: 317
 

@getdunne

Thank you for this. I do have both a nanoKONTROL2, and a nanoKONTROL. 

I installed the .guru file after reading the docs, reset my nanoKONTROL2 to factory defaults, and then opened the stand alone Unify app.

The sliders work properly, controlling the levels of the individual patches, and the knobs control the aux send #1 for each lane.

 

I also tried the nanoKONTROL (1), setting it to default, and removing the 2 from the name, but it did not work properly. I presume it has different defaults than the 2. When I moved the slider #1, it moved the volume for lane 3, and 3, 4 and 5 moved the aux #1 for 1,2 and 3.

I tried midi learn, and that worked well to assign the faders to the knob controls, but it seems to have removed the defaults from the knobs. Are they stored separately from the patches? I didn't save anything, but after I did that the knobs seemed different.

What I would like is for the sliders on the korgKONTROL (1) to be able to control the knobs in Unify, like John does with his device. 

Did I mess something up with midi learn? If so, how can I get back to the default?

Even after doing all this, the nanoKONTROL2 still works properly.

-- Martin


ReplyQuote
Zorzi
(@zorzi)
Eminent Member
Joined: 11 months ago
Posts: 21
Topic starter  

Thank you Shane ! I understand how it works. With your example, I can even write a file with the commands I need (if I knew how to name macro knobs). In fact I don't need to command the mix levels and so on as your text file which is very clear (and convenient, thanks !). I should want to control the first row of 8 Unify Macro knobs with the sliders (the pan buttons are impossible to control !) and to be able to record these as an automation. And this NanoKontrol2 don't want to let me work from a blank sheet : there is a default command ensemble for the main DAWs and another which is not blank. Annoying. Thank you again. I love Unify and the guru videos and sounds. I have so much fun.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2850
 

@mschiff

I also tried the nanoKONTROL (1), setting it to default, and removing the 2 from the name, but it did not work properly. I presume it has different defaults than the 2. When I moved the slider #1, it moved the volume for lane 3, and 3, 4 and 5 moved the aux #1 for 1,2 and 3.

Did you create a second .txt file for the nanoKontrol 1? If not, I suggest you do so. Look at the controller names as reported in the Audio/MIDI Settings view, and choose an appropriate name-prefix which will match only that controller name. Then you can set it up however you like.

You can use MIDI Monitor to figure out exactly which CC numbers any controller is sending.

What I would like is for the sliders on the korgKONTROL (1) to be able to control the knobs in Unify...

I tried midi learn, and that worked well to assign the faders to the knob controls, but it seems to have removed the defaults from the knobs. Are they stored separately from the patches? I didn't save anything, but after I did that the knobs seemed different.

If you're going to use MIDI control files, you don't need to worry about MIDI-learn or knob CC-assignments at all. If you set up a MIDI control file for your nanoKONTROL (1), you can assign the knobs directly to the macro knobs using the macro/1macro/2, etc. parameter paths, as described in the page I added to the Unify manual yesterday.

Yes, the MIDI-learned CC assignments for Unify's macro knobs are stored separately from patches. Each time you start Unify, it remembers knob CC assignments that you used most recently. You can also save the assignments yourself, in a "CC Assignments preset", as described in this section of the Unify manual.

Did I mess something up with midi learn? If so, how can I get back to the default?

CC Assignments presets live in the <Unify content folder>/Presets/Midi Controller Presets folder, but if you have never yet saved any CC-assignment presets, you won't have such a folder.

Download this .guru file: https://www.dropbox.com/s/g5584xk4kx9sd6v/MIDI%20CC%20Assignment%20Presets.guru?dl=0 and drag/drop into Unify to add a Midi Controller Presets folder containing three example CC-assignment presets. Load the one called AIRWAVE 4 Controllers.xml to restore the Unify defaults (CC#1, CC#2, CC#4, CC#67 on first four knobs, nothing else).

Because Unify remembers the last-used knob CC assignments, after you load the AIRWAVE 4 Controllers.xml file once, you won't need to use it again unless you change some of the assignments (using MIDI-learn or any other method).


ReplyQuote
mschiff
(@mschiff)
Member
Joined: 1 year ago
Posts: 317
 

@getdunne

Yes. I copied the file that you created and installed with the .guru file, gave it a different name. Put the file for the NK2 in an "unused" folder beneath the folder that was created by the .guru file, removed all the sections but the top one (after the comments) and modified the top one to:

cc 1 midi/cc/1
cc 2 midi/cc/2
etc.
This worked somewhat, but the sliders were not in the proper order.

The midi cc numbers in the last column matched the numbers shown on the knobs.

After looking at the app for the NK (1) I found that the default numbers for the sliders were different than the NK2, and that's why they did not match.

So in Unify, the knobs are referred to as macro/1, macro/2, etc?

So the above should be:
cc 1 macro/1
cc 2 macro/2
etc.?

All I want is for the NK (1) to use the sliders to move the first 8 knobs, no matter what their assignments. Is that possible? I see John doing it on his videos with the Maschine Jam. Does he have settings for each patch, or is he doing what I am trying to accomplish with the NK (1)?

Are the knob assignments contained in each patch if they are used?

-- Martin


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2850
 

@mschiff

Yes, you should be using macro/1 and macro/2 for the parameter paths. However, the CC numbers on each line MUST match what your controller is sending. Use MIDI Monitor to check what the controller is sending, making sure to disable any MIDI controller files first (to ensure whatever CC messages are coming from your controller actually get through to MIDI Monitor).

This is not what John is doing with his Maschine Jam; it's more advanced than that. John just set up his Maschine Jam to send CC#1, CC#2, CC#4, and CC#67 for the first four sliders, and then assigned the first four Unify knobs to respond to those CCs. If that's all you need, you don't need to use MIDI controller files at all.

However, for the nanoKONTROL2, the new MIDI controller file-based approach is probably better. All you need is a .txt file like this:

nanoKONTROL2

cc 0  /macro/1

cc 1  /macro/2

cc 2  /macro/3

cc 3  /macro/4

cc 4  /macro/5

cc 5  /macro/6

cc 6  /macro/7

cc 7  /macro/8

This assumes your NK2 knobs are sending on CC#0, CC#1, ... , CC#7. If not, you must change the "cc" numbers in the file to match whatever CC numbers it actually sends.


ReplyQuote
Kendall W Cochran III
(@pbeprod)
Member
Joined: 2 years ago
Posts: 240
 

@getdunne

Hey just got my nanokontrol2. I'm going to start from the beginning. So when I open the settings and then open Audio/Midi Settings, should nanoKontrol2 be showing in Active Midi inputs area? It's not for me, I also had a NanoKontrol it showed up once and then disappeared. This is on my PC. It's showing and working on my Mac.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2850
 

@pbeprod

Yes, the nanoKontrol should be listed and checked in active MIDI inputs. If not, Unify won't be getting input from it.

Perhaps you need to install a driver, or reboot the PC? I have no idea.


ReplyQuote
Kendall W Cochran III
(@pbeprod)
Member
Joined: 2 years ago
Posts: 240
 

@getdunne

Evidently the driver being installed was an issue, once I deleted the driver, and didn't let the Korg configuration tool install it, it started showing up. Very odd.


mj_prod liked
ReplyQuote
Share: