malaell daronycah creating

0 views

Skip to first unread message

Marsilius Boa

unread,

Aug 3, 2024, 1:45:31 AM8/3/24

to cernlentingchi

My goal is to simply setup CC1 to control modulation (i.e the mod wheel) for my Kontakt orchestral instruments in Logic. Unfortunately, the first problem is that my Korg Nanokontrol Editor doesn't let me change the values of the CC numbers and the lower/higher values of each slider. It seems to be completely none responsive and changes the values randomly when I try to manipulate it. Does anyone know if there still are compatibility issues with the Korg Nanokontrol Editor and macOS Big Sur as I'm also using the M1 chips ?

Ignoring the fact that I can't handle the editor, I still somehow managed to get a CC1 slider and wrote the scene to save the changes. But now when I move this CC1 slider in Kontakt, it doesn't affect the mod wheel (doesn't affect anything to be precise). Do you have any idea how to solve this eternal issue of mine ?

Thanks for the video, it's exactly the weird flicker issue I have but as you saw in the screenshot I sent in my first post I did manage to do what is done in the video, I actually have a slider set to CC1, it's showing in the editor interface but it just doesn't work inside logic.

I'll try using Snoize MIDI Monitor though ! Also the auto checkbox wasn't checked but I voluntarily unchecked it since I didn't want to use the auto assigned presets. Checking this box didn't change anything to my modulation issue.

Also here are some screenshots of the my MIDI Studio, Control Surface Setup in Logic and midi controller preferences. The nanokontrol2 is there no problem. I must also mention that I bought my Komplete Kontrol after the nanokontrol2 and I don't use them together so there is no interference here.

I tried assigning my sliders to automation parameters like track volume, expression, and other smart controls with the learn mode feature from LPX and when I move them logic detects it perfectly, it worked alright but not with modulation (CC1).

I tried it and nothing is changing when I use the "bypass all control surface" - the nanokontrol2 sliders are no longer registered by logic and there's no longer sound coming out my Kontakt instruments.

I saw the AMS glitch thing, I believe it's not normal but it doesn't have an impact on my issue though. I think most of these problems come from the lack of compatibility of the nanokontrol2 and MacOS Big Sur.

Maybe if you have some time, you could give a quick look at the forum discussion I talked about in my latest post to see if this gives you any new ideas... What I'm really trying to achieve is to set this mod wheel in the Kontakt player and this comes directly from the Kontakt and logic interfaces as they talk about in other forums.

Everything maps great except that I cannot get the buttons to stay lit on the Nano. I've downloaded the KORG Kontrol editor from Korg and set the buttons to toggle, I've tried the different settings in Mainstage but the toggle setting in mainstage is greyed out and un-selectable.

I read your post on how to get the red lights to work on a Korg NanoKontrol 2 and I wanted to ask you if you would be willing to give me a step by step breakdown on how you got the red lights to work on the Korg Kontroller.

I'm using it w/ MainStage 3 on my Macbook Pro and can't figure out how to get the light tasty on. I would love to be able to do so to help when using with my keyboard on a dark stage. Any help would be greatly appreciated.

I wasn't aware the nanoKontrol was capable of bidirectional communication. My church uses one with the MainStage concert I developed for weekly use and if the nanoKontrol is capable of bidirectional comms, I'll set it up for that. Can anyone confirm the nanoKontrol's capabilities in this area?

After finally getting a chance to spend some time with my church's MacBook Pro and the nanoKontrol yesterday, I can confirm that it supports bidirectional communication with MainStage. It was a bit tricky to work out but you'll need to use the KORG Kontrol Editor to set the global LED status of the nanoKontrol to "external" instead of "internal"...this is what will enable MS to keep the nanoKontrol LEDs lit when the corresponding control in MainStage is lit or executed. For my purposes, I found the best control type in MainStage to be "Press/Release" and I left the nanoKontrol button status as "momentary". Everything works perfectly and I have bidirectional comms between MS and the nanoKontrol, with LEDs and controls in both responding as they should.

HI Gary, thanks for the reply. I went to work on this but cannot find the "external" or "internal" LED status setting with the Kork Kontrol Editor. I am using the Nano Kontrol version 1 not the more recent Korg Nano Kontorl 2. Does yours happen to look like this one? ,85/nanokontrolnanoKONTROL_oblique-3fdbd d94726ead98da44a8b679e2fcd9.jpg

I'm using a nanoKontrol 2 and have no idea if this particular functionality is different between the 2 models. The option for internal vs external LEDs was tricky to find and because I don't have the nanoKontrol with me (it stays at my church), I can't actually connect it to help you. Perhaps see if anyone on the Korg forums can clarify if the Internal/External LED setting is available on the v1 nanoKontrol?

Hello,
I wrote a nanoKontrol tox. I just updated it on my github.
For the moment there is no real manual but it works.
There is also a file to assign the proper controlers to the nanoKontrol.

hey! Ive set up my midi in the korg editor previously, a long time ago, but now when I open that file it says the midi is not supported! I press cycle + set before plugging it in - also updated it to the latest editor - any ideas?