By extension I guess the situation could be similar under MacOSX.Īnd just to be sure, I just tried the NanoKontrol2 here under MacOSX 10.8.5 and 10.9.3 and it is fully supported by CopperLan.
Using the standard MIDI support offered by the OS seems to be the solution. It seems that we are not alone to reach this conclusion, there are plenty of complaints on the internet related to this. We bought a NanoKontrol2 to check what's going wrong with it and didn't find any reason under Windows but the Korg MIDI driver.
Yes indeed, the MacOSX minor update included in 1.3(3) includes just a fix to the VMIDI port engine that was freezing on VMIDI port number change, nothing related to "physical" MIDI port management (an therefore nothing related to the NanoKontrol) So, it appears the updated version of CopperLan Manager for Mac you posted has not patched this issue and is still something that needs addressed. I then rebooted my machine and opened CopperLan Manager and experienced the exact same behavior described in my previous post(Mac Node disappears when KorgNanoKontrol2 is plugged in as well as all Ethernet Interfaces disappear and then both the Mac Node and the Ethernet Interfaces re-appear when you disconnect the KorgNanoKontrol2). That being said, I have since uninstalled the MIDI Driver plugin for the NanoKontrol2 located at /Library/Audio/MIDI Drivers, as there is no "Official" MIDI driver uninstaller from Korg. Therefore, considering your above post regarding the Mac issue not being related to the Korg Driver issue others are experiencing when using Windows, I did not think that uninstalling the KorgNanoKontrol2 driver was required for the patch to work. CopperPhil wrote: (The bug fix related to MacOSX is a minor update, not related to the Korg driver issue.)Īnd as my post earlier this evening states, I am experiencing the issues described on a Mac running 10.9.3.
0 kommentar(er)
