# Korg nanoKONTROL2 - CUSTOM MIDI Remote Script

**URL:** <https://forums.steinberg.net/t/korg-nanokontrol2-custom-midi-remote-script/912745>\
**Category:** Cubase\
**Tags:** midi-remote, shared-midi-remote\
**Created:** [May 8, 2024, 2:46pm UTC](https://forums.steinberg.net/t/korg-nanokontrol2-custom-midi-remote-script/912745 "2024-05-08T14:46:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![VISFOTIKA](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/visfotika/32/259105_2.png) [@VISFOTIKA](https://forums.steinberg.net/u/VISFOTIKA)\
**Post date:** [May 8, 2024, 2:46pm UTC](https://forums.steinberg.net/t/korg-nanokontrol2-custom-midi-remote-script/912745/1 "2024-05-08T14:46:44Z")

</div>

![nanoKONTROL2](https://europe1.discourse-cdn.com/steinberg/original/4X/7/a/e/7aeae6f5b8141255cc5d19c417e0529b39dc8e09.jpeg)

Here is a custom MIDI Remote script made from the factory script that came with Cubase 13.  
I have modified/added the following:

- **Functionality** - Factory script gets rewritten on every startup and reset to the default CC values. I have removed (commented out) the code which resets the CC values. Currently, the CC values of 8 sliders are set to CC1, CC11, CC2, CC3, CC4, CC5, CC6, CC7. (explained in detail [here](https://forums.steinberg.net/t/korg-nanokontrol2-reset-to-default-cc-when-opening-cubase13/879077/12))
- **Customization** - Rearranged the default alignment of the transport buttons and added titles for Marker buttons and Track selection buttons. Modified the model name display and Company name along with a small LED lamp as in the actual controller.

The zip file contains a .js file. Just extract the zip file inside the directory  
`C:\Users\#####\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local`  
in the order **‘Local’ \> ‘Korg’ \> ‘nanoKONTROL2’ \> Korg\_nanoKONTROL2.js**  
This adds the company ‘ **Korg** ’ and the model ‘ **nanoKONTROL2** ’ in the MIDI Remote Assistant dropdown menu while adding a new controller.

[Korg.zip](https://forums.steinberg.net/uploads/short-url/x2RrQtiM8ZHD5H9efJfVmBXsM9C.zip) (3.6 KB)  
[Korg\_nanoKONTROL2.midiremote](https://forums.steinberg.net/uploads/short-url/dTnAtpN7tHm9n9WoTBUwbA1P4JJ.midiremote) (6.1 KB)

---

<div class="post-metadata">

**Author:** ![chart](https://avatars.discourse-cdn.com/v4/letter/c/aca169/32.png) [@chart](https://forums.steinberg.net/u/chart)\
**Post date:** [January 14, 2025, 5:29pm UTC](https://forums.steinberg.net/t/korg-nanokontrol2-custom-midi-remote-script/912745/2 "2025-01-14T17:29:03Z")

</div>

Hello, sounds like a great idea however the dropdown menu does not show the nanokontrol unit although the file is in the mentioned userdir. I must however say I am using a nanocontrol.

---

<div class="post-metadata">

**Author:** ![antoinevankampen](https://dub1.discourse-cdn.com/steinberg/user_avatar/forums.steinberg.net/antoinevankampen/32/836_2.png) [@antoinevankampen](https://forums.steinberg.net/u/antoinevankampen)\
**Post date:** [January 2, 2026, 9:01am UTC](https://forums.steinberg.net/t/korg-nanokontrol2-custom-midi-remote-script/912745/3 "2026-01-02T09:01:14Z")

</div>

Hi Visfotika, what exactly is the .midiremote file? Can find any information about this. And where does cubase store this files? Thanks, Antoine

PS. The re-definition of the CC values does not seem to work in my case. However, commenting out the sysex works perfectly.
