71 postsPage 4 of 4
1, 2, 3, 4
There's a lot of vids about control link like this one:

https://www.youtube.com/watch?v=woFOqHjoZ28

I noticed that there's different modes and you have to restart it, also there is editor software.

I think there's a CC mode that you probably have to use then try the process to use control link.

Forum Moderator.
Please add your specs to your SIGNATURE.
Search the STUDIO ONE 5 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


Studio OnePro5.1 64bit Melodyne Studio
Studio Computer - Nectar Impact LX25+
Win10 i7 7700k 16gb ram 1TB SSD AsusH270M-PLUS interface:StudioKonnekt 48
Kitchen Computer
Win10 Ryzen 5 3600 - Radeon RX 590 - 16GB DDR4 3000MHz - 512GB SSD interface: Motu M2
User avatar
by Trucky on Wed Aug 05, 2020 3:55 pm
normanyoung2 wroteJust bought one these and it works correctly out of the box, with PAN and everything doing as expected, BUT I want to use the sliders to control CC values, and I've failed completely to manage this.

I would have assumed you should be able to edit this from within Studio One 5, but when looking at the edit page, none of the sliders are there, so it isn't possible to edit them.

I tried setting up a new CONTROL surface but that didn't work either.
Setting up as a Mackie Control didn't help.

Has anyone succeeded in using one of these to control sampled instruments?

I wrote the nanoKONTROL 2 device drivers specifically for transport controls, markers, loop toggle, faders, pans, etc. so that all those features would work with Studio One. This driver is now included with the Studio One distribution.

To have it work "custom" per your request will require the following steps:
1. If installed, uninstall the nanoKONTROL 2 device from your External Devices because this device driver will conflict with what you're trying to do.
2. Factory default the nanoKONTROL 2 by holding [Prev Track], [Next Track] & [Cycle] buttons down while plugging it in to your USB port.
3. Now you should be able to setup all the knobs, faders, buttons etc. using "Control Link" and "MIDI Learn" in Studio One as demonstrated in the following video:

phpBB [video]

Please add your specs to your SIGNATURE.
Download the STUDIO ONE 5 PDF MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


Windows 10 Pro 64-bit (20H2), Studio One 5.1.1 Pro | Notion 6.8 | Universal Control v3.4.0.61835
Dell Inspiron 17 5770 (Intel Core i7-8550U 1.8 GHz, 4GB AMD Radeon 530 Graphics, 16GB RAM, Samsung 860 EVO 2TB SSD
StudioLive Series III 32 v2.4.17466
User avatar
by kozmyk on Tue Oct 06, 2020 7:11 pm
Excellent Trucky.
I think I'm gradually catching on.
I've been fighting for nigh on three days trying to get nanoKontrol2 to work in any shape.
I finally found a Registry Tweak on YouTube that got the MIDI Ports visible.
https://www.youtube.com/watch?v=18SLcnbqwaI
Bad bad Korg for not keeping their driver software up to date, it really isn't Win10 friendly at all.

Anywhooo I eventually got the nK2 working as a vanilla transport and mix controller
BUT
In CC Mode everything was cock-eyed again.
Korg's own Korg Kontrol Editor could not see the MIDI in/out Ports of the nK2.
If there's a Registry fix for that problem, I haven't found it.
BUT
Presonus to the rescue here, Control Link will let me remap the nk2's CC output.

I note your comment Trucky about Removing the unused instance of nK2 in the External Hardware setup.
Question – Does it HAVE TO be removed ?. Is there not a way to just disable it ?
I'm thinking of a possible scenario where I might actually WANT the vanilla Mix & Transport Control for a particular job.
If I then Remove the CC setup would I have lost my Macro settings ?
That's a possible 51 control settings.
OR
Would those settings be reapplied upon instantiating another CC mK2 setup ?

Firepod(FP10 firmware), Studio One v5.0.1 (Sphere), Melodyne 5 Studio, Ableton Lite, Bitwig, Mixers (Soundcraft,Behringer,Studiomaster) Remotes Android, Sensel Morph, Instruments Basses, Guitars, Keyboards, Banjo, Didj, Cowbell, Mics-Dozens

Win10 Home, Intel i7 3770K 4.2GHz, 32GB RAM, Gigabyte SKT-1155 Z77X-UD5H, Gigabyte GeForce GTX670 2GB
User avatar
by kozmyk on Wed Oct 07, 2020 12:01 pm
KORG nanoKONTROL2 NOT Kontrolling

Korg DID try to be helpful, up to a point.
The bottom line of their advice was
“Windows won't allow more than 10 USB MIDI drivers on the go at once”
And
“Uninstall all the Korg drivers and the Korg Kontrol CC Editor, keep deleting drivers until you have less than ten. Unplug all other USB MIDI devices – Reinstall”

Except, I had already tried that.
They DID come up with “Check for hidden drivers in Device Manager”.
That Could work I guess.
BUT
They say that it's all due to a limitation imposed by Windows 10.
If that's true how come none of the other drivers, well over 10 of them have never caused a problem ?? Huh ?
Now I get that it USED to be a limitation on Win7 and possibly Win8 (I never had Win8) but blaming this problem on Win10 is just laziness on Korg's part in my opinion.
Can't be bothered to properly update their software.
They're still selling this product, they should keep it properly supported.

For now I've just junked Korg Kontrol Editor and remap for CC changes in Studio One and Ableton Live via their respective MIDI learn functions …
I've wasted days chasing this damned driver about the place.
A bodge fix is going to have to do for now.

When in DAW mode the nK2 runs sweet, now the “Alias” fix is in place in the Registry.
The “Alias” fix doesn't do it for the CC Editor software unfortunately ...
Last edited by kozmyk on Sat Oct 10, 2020 3:00 pm, edited 1 time in total.

Firepod(FP10 firmware), Studio One v5.0.1 (Sphere), Melodyne 5 Studio, Ableton Lite, Bitwig, Mixers (Soundcraft,Behringer,Studiomaster) Remotes Android, Sensel Morph, Instruments Basses, Guitars, Keyboards, Banjo, Didj, Cowbell, Mics-Dozens

Win10 Home, Intel i7 3770K 4.2GHz, 32GB RAM, Gigabyte SKT-1155 Z77X-UD5H, Gigabyte GeForce GTX670 2GB
User avatar
by Trucky on Wed Oct 07, 2020 3:32 pm
I agree that Korg is not very helpful with these kinds of requests.

You should check out USBDeview for Windows.
It's a great tool for troubleshooting USB devices.

https://www.nirsoft.net/utils/usb_devices_view.html

Please add your specs to your SIGNATURE.
Download the STUDIO ONE 5 PDF MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


Windows 10 Pro 64-bit (20H2), Studio One 5.1.1 Pro | Notion 6.8 | Universal Control v3.4.0.61835
Dell Inspiron 17 5770 (Intel Core i7-8550U 1.8 GHz, 4GB AMD Radeon 530 Graphics, 16GB RAM, Samsung 860 EVO 2TB SSD
StudioLive Series III 32 v2.4.17466
User avatar
by kozmyk on Sat Oct 10, 2020 3:22 pm
Trucky wroteI agree that Korg is not very helpful with these kinds of requests.
You should check out USBDeview for Windows.
It's a great tool for troubleshooting USB devices.
https://www.nirsoft.net/utils/usb_devices_view.html

Thanks Trucky, I almost half-understand what I'm looking at there ... ;)

Korg DO have a point. If I remove everything else, disconnect all the hardware - remove all the drivers, THEN reinstall their less than up to date software I Might just have a chance to get it running as it ought to.
I'm not in a hurry to do that right now in case it disrupts the rest of my system regarding the reconnection and refinding of the drivers they recommend removing.
If Korg kept their software up to date then it wouldn't be hamstrung by the old 10 driver limit.
None of my other gear suffers from it, yet Korg continues to blame Windows ...

I'm getting CC utility from the nK2 unit, just without the benefit of the Korg Software.
For now I can make it do what I want by MIDI mapping.
That's fine until I encounter a CC number conflict ...

In the meantime I've just discovered some tasty Glitch Machine plugins and I'm adding to the Chaos in the Universe with those for now .... :punk:

Firepod(FP10 firmware), Studio One v5.0.1 (Sphere), Melodyne 5 Studio, Ableton Lite, Bitwig, Mixers (Soundcraft,Behringer,Studiomaster) Remotes Android, Sensel Morph, Instruments Basses, Guitars, Keyboards, Banjo, Didj, Cowbell, Mics-Dozens

Win10 Home, Intel i7 3770K 4.2GHz, 32GB RAM, Gigabyte SKT-1155 Z77X-UD5H, Gigabyte GeForce GTX670 2GB
User avatar
by danielbuckley4 on Tue Oct 20, 2020 3:09 pm
Hello,

I just downloaded Studio One version 5 and was very excited to set up my new Korg nanoKONTROL 2. After adding selecting Korg nanoKONTROL 2 from the external device list and holding down the "SET" marker button and rewind button while plugging in in the usb device to activate Mackie mode my device was working great! I was able to adjust volume all the solo record and transport buttons just fine and bank between channels, however, when I went in to edit the parameters of a plug-in I was unable to assign any of the plug-in buttons to anything except the twisty knobs on top. I mention all this because I was able to go into the XML file within Studio One and make some edits so now the 8 faders are assignable to plug-in parameters. I’ve uploaded the XML file in case anybody wanted to try it out. I’d recommend backing up your original XML file just in case as I’m a novice coder 😀

Here's the steps to get the XML file working with your copy of Studio One

1. Download the xml file attached to this post and extract (it's a .zip file)
2. Navigate to PreSonus\Studio One 5\devices\Korg\nanoKONTROL 2
3. Save the current copy of nanoKONTROL 2.surface.xml somewhere else on your computer (just in case)
4. Delete the nanoKONTROL 2.surface.xml file
5. Copy > Paste in the file you downloaded from the attached file

Restart Studio One and you should be good to go! Let me know if it works for you.

Attachments
nanoKONTROL 2.surface.zip
Updated XML for nanoKONTROL 2 to allow assigning plugin parameters to faders
(2.71 KiB) Downloaded 17 times
User avatar
by Bbd on Tue Oct 20, 2020 3:24 pm
That was great for you to post this. I don't use that equipment but this might help someone who does.
:+1

Bbd

Please add your specs to your SIGNATURE.
Search the STUDIO ONE 5 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


OS: Win 10 x64 Home, Studio One Pro 5.x, Notion 6, Series III 24, Studio 192, Haswell CPU: i7 4790k @ 4.4GHz, RAM: 16GB, Faderport 8/16, Central Station +, PreSonus Sceptre S6, Eris 3.5, Temblor 10, ATOM, ATOM SQ
User avatar
by kozmyk on Tue Oct 20, 2020 4:53 pm
danielbuckley4 wroteHello,
I just downloaded Studio One version 5 and was very excited to set up my new Korg nanoKONTROL 2. After adding selecting Korg nanoKONTROL 2 from the external device list and holding down the "SET" marker button and rewind button while plugging in in the usb device to activate Mackie mode my device was working great! I was able to adjust volume all the solo record and transport buttons just fine and bank between channels, however, when I went in to edit the parameters of a plug-in I was unable to assign any of the plug-in buttons to anything except the twisty knobs on top. I mention all this because I was able to go into the XML file within Studio One and make some edits so now the 8 faders are assignable to plug-in parameters. I’ve uploaded the XML file in case anybody wanted to try it out. I’d recommend backing up your original XML file just in case as I’m a novice coder 😀

Here's the steps to get the XML file working with your copy of Studio One
1. Download the xml file attached to this post and extract (it's a .zip file)
2. Navigate to PreSonus\Studio One 5\devices\Korg\nanoKONTROL 2
3. Save the current copy of nanoKONTROL 2.surface.xml somewhere else on your computer (just in case)
4. Delete the nanoKONTROL 2.surface.xml file
5. Copy > Paste in the file you downloaded from the attached file

Restart Studio One and you should be good to go! Let me know if it works for you.

Excellent work danielbuckley4
I've downloaded it and will have a go with it at the earliest opportunity.
Thank you for sharing.

Firepod(FP10 firmware), Studio One v5.0.1 (Sphere), Melodyne 5 Studio, Ableton Lite, Bitwig, Mixers (Soundcraft,Behringer,Studiomaster) Remotes Android, Sensel Morph, Instruments Basses, Guitars, Keyboards, Banjo, Didj, Cowbell, Mics-Dozens

Win10 Home, Intel i7 3770K 4.2GHz, 32GB RAM, Gigabyte SKT-1155 Z77X-UD5H, Gigabyte GeForce GTX670 2GB
User avatar
by GreatExpectations on Sun Nov 08, 2020 1:49 pm
Hey different question: I think about picking one up, how is the feel of the faders and potis on the device?

thanks!
User avatar
by kozmyk on Sun Nov 08, 2020 6:34 pm
GreatExpectations wroteHey different question: I think about picking one up, how is the feel of the faders and potis on the device?
thanks!

Nothing special but perfectly adequate.
Sliders are short throw but smooth, both in feel and response.
Pots are smooth.
Simple. no detents or click positions.

Firepod(FP10 firmware), Studio One v5.0.1 (Sphere), Melodyne 5 Studio, Ableton Lite, Bitwig, Mixers (Soundcraft,Behringer,Studiomaster) Remotes Android, Sensel Morph, Instruments Basses, Guitars, Keyboards, Banjo, Didj, Cowbell, Mics-Dozens

Win10 Home, Intel i7 3770K 4.2GHz, 32GB RAM, Gigabyte SKT-1155 Z77X-UD5H, Gigabyte GeForce GTX670 2GB

71 postsPage 4 of 4
1, 2, 3, 4

Who is online

Users browsing this forum: roblof, wibem and 35 guests