nanoKontrol2 with Logic Pro 10.4.5

Question

nanoKontrol2 with Logic Pro 10.4.5

I downloaded the Logic 10.4.5 update, and suddenly my Korg nanoKontrol 2 stopped working. Previous to this, it worked without the driver and all of the controls worked entirely as expected. I was using the default setup, with the faders controlling the track volume, knobs controlling pan, etc.

I tried deleting it from the controller setup and re-adding it, but only the transport controls work. None of the faders, knobs or solo/mute/record buttons work.

I even tried installing the Korg drivers to see if that would work. No luck.

I’d love to hear from anyone with a similar experience or any suggestions.

Posted on Jun 13, 2019 3:14 PM

Reply

Answer 1

Best reply

Leon Elegant

Level 2

245 points

Jul 10, 2019 12:31 AM in response to Dylan Winslow

Hi Dylan Winslow

They have fixed this problem in Logic Pro X new update 10.4.6

You can Update your Logic Pro X to 10.4.6 and see if this will solve your problem.

Before updating Logic, make sure to back up the currently installed version of the Logic application and your Logic projects.

I hope this was helpful and solved your problem.

-Leon Elegant

Reply

Answer 2

Pancenter

Level 6

14,662 points

Jun 13, 2019 5:04 PM in response to Dylan Winslow

Dylan, see below, you will only need to delete the Control Surfaces com.apple.logic.pro.cs file.

The reboot the computer with the nanoKontol unplugged, let the computer settle then plug the nanocontrol back in and see if you have any luck.

-----------------------------------------------------------------------------------------

In the Finder, choose Go > Go to Folder from the menu.

Type ~/Library/Preferences in the "Go to the folder" field. Note: exactly like this. ~/Library/Preferences

Press the Go button.

Remove the com.apple.logic10.plist file from the Preferences folder. Note that if you have programmed any custom key commands, this will reset them to the defaults. You may wish to export your custom key command as a preset before performing this step. See the Logic Pro User Manual for details on how to do this. If you are having trouble with a control surface in Logic Pro. then delete the com.apple.logic.pro.cs file from the preferences folder.

Reply

Answer 3

Jun 13, 2019 7:31 PM in response to Pancenter

I tried doing this, and I still wasn’t able to add the nanoKontrol2. Then I tried quitting and then restoring com.apple.logic.pro.cs from before the update. When I started Logic, the nanoKontrol2 was there, but the assignments were off, and Logic crashed when I moved a fader.

Reply

Answer 4

Jun 13, 2019 7:52 PM in response to Dylan Winslow

And for what it’s worth, here’s the relevant part of the crash log. I think I might have to just submit a report to Apple and hope it gets fixed in a future update.

Process: Logic Pro X [730]

Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X

Identifier: com.apple.logic10

Version: 10.4.5 (5076)

Build Info: MALogic-5076000000000000~2

App Item ID: 634148309

App External ID: 831355815

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Logic Pro X [730]

User ID: 501

Date/Time: 2019-06-13 20:29:15.240 -0600

OS Version: Mac OS X 10.14.5 (18F132)

Report Version: 12

Anonymous UUID: D08A1154-46CD-935A-C146-40143BD0778F

Time Awake Since Boot: 830 seconds

System Integrity Protection: enabled

Crashed Thread: 5 SeqTimer

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000007c

Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [730]

VM Regions Near 0x7c:

-->

__TEXT 000000010a6cd000-000000010c399000 [ 28.8M] r-x/rwx SM=COW /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X

Application Specific Information:

MALondonIII | e84d8ecce95d250e32c0f73d4c79d2b685e8718a80997af9a2b0f6c679216e01 | f0f16a31943d0462f17b5a9cb01433111f8f39e7 | 2019-06-11_16:38:41

Thread 5 Crashed:: SeqTimer

0 com.apple.music.apps.midi.device.plugin.nanoKONTROL2 0x0000000115705695 messageProc(long, long, ...) + 133

1 com.apple.logic10 0x000000010b081c79 0x10a6cd000 + 10177657

2 com.apple.logic10 0x000000010b0839d5 0x10a6cd000 + 10185173

3 com.apple.logic10 0x000000010b08587f 0x10a6cd000 + 10193023

4 com.apple.logic10 0x000000010ad90b33 0x10a6cd000 + 7093043

5 com.apple.logic10 0x000000010ad8fe89 0x10a6cd000 + 7089801

6 com.apple.CoreServices.CarbonCore 0x00007fff40e004e2 TimerThread + 127

7 libsystem_pthread.dylib 0x00007fff6bc002eb _pthread_body + 126

8 libsystem_pthread.dylib 0x00007fff6bc03249 _pthread_start + 66

9 libsystem_pthread.dylib 0x00007fff6bbff40d thread_start + 13

Reply

Answer 5

kerochan

Level 4

1,065 points

Jun 14, 2019 12:22 AM in response to Pancenter

OMG

Do we all have to do this with our midicontrollers when we update Logic?

sorry again for the hi jack, I didn't know that all this was needed when just updating Logic? I am sure many wont bother if this is the case, myself included.

Reply

Answer 6

Pancenter

Level 6

14,662 points

Jun 14, 2019 12:57 AM in response to kerochan

K,

This is NO different than any other time, it looks like a Logic problem that affects one make controller so far.

Don't over react, it's always like this with complex software. It looks like a great upgrade but there will Always be a few things not right, that's life. Learn to live with it. Does it affect you NOW, at this very moment? NO it doesn't.

Reply

Answer 7

kerochan

Level 4

1,065 points

Jun 14, 2019 1:25 AM in response to Pancenter

Thanks for the reassurance Pancenter,

I just thought that Dylan's Korg Nano was plug n' play. nothing to do, no drivers, same as my Korg Micro Key keyboard I have, its the main reason I bought it!

When I updated from Logic 10.3.1 to 10.3.2 I had nothing to change.

Reply

Answer 8

Jul 2, 2019 9:00 PM in response to Dylan Winslow

FWIW I can confirm this bug. My two Korg nanoKontrol controllers worked perfectly before upgrading to Logic 10.4.5. Now they get recognized in setup but the mapping is all over the place. I've chucked the control surface pref file as well. No luck.

This is definitely a bug on Apple's side, as my Nektar LX49 controller ALSO stopped working with Logic 10.4.5, and that thing had the most rock solid, no fuss integration of any controller I've used.

Here's hoping I still have a backup to revert to.

Reply

Answer 9

kerochan

Level 4

1,065 points

Jul 3, 2019 12:58 AM in response to PBordeaux

Sorry to hear this PBordeaux

This is one reason I am still on Logic 10.3.2 and El Capitan, and don't bother with a controller either, less stuff, less to go wrong.

However, hoping everything gets sorted with Logic 10.4.5

Reply

Answer 10

Jul 9, 2019 1:50 PM in response to Dylan Winslow

So I downloaded 10.4.6 today, and while it doesn’t crash when I use a fader (yay), none of the controls actually do anything except for the 1st knob, which controls the pan on the selected track. I’ve tried trashing the com.apple.logic.pro.cs a couple of times, deleting it from the Control Surface setup, etc.

Anyone have any better experiences with this version?

Reply

Answer 11

Jul 10, 2019 3:18 AM in response to Leon Elegant

I’ve tried the 10.4.6 update (see my post above). What I’ve found is that, after deleting the com.apple.logic.pro.cs file, it works. But if I quit Logic and restart it, it’s broken again. I was on the phone with support for a couple of hours yesterday, and it’s in the hands of engineers now.

Reply

Answer 12

Jul 13, 2019 6:48 PM in response to stratquebec

Um... spoke a little bit too quickly. It works but if I quit logic and open it again it no longer works. The nano appears normally int the control surface setup but I have to delete it and chose New>Automatic installation. It detects the nano and it works again. In the en I have the same problem as Dylan Winslow's (ref: post above).

Reply

Answer 13

Jul 18, 2019 4:59 AM in response to Dylan Winslow

A workaround that works for me is in 10.4.6

Logic Pro x>Control Surfaces>Setup...

Click on the nanoKONTROL2 icon and press delete on your keyboard delete it.

Choose New>Automatic installation.

The nanoKONTROL2 is automaticaly detected.

I need to do this everytime I launch Logic.

Also make sure that Auto is unticked in

Logic Pro x>Control Surfaces>Preferences>MIDI Controllers

Reply

Answer 14

Jul 18, 2019 7:25 AM in response to stratquebec

It's true that way it works, but it's not the right one. Let's wait and see if the engineers will fix it in the next updates. Also add that the same thing happens to the automap.

Greetings.

Thank you.

Reply

Answer 15

Jul 30, 2019 2:51 PM in response to Leon Elegant

I was pretty excited when I saw this on change log.

The only way to make it work was deleting the CS file, but I have to delete it every time I open Logic. if I close it an re open it without deleting that file it gets stuck again.

I'm getting stick to version 10.4.4 meanwhile there's a real fix.

Reply

nanoKontrol2 with Logic Pro 10.4.5

Similar questions