kore 2 upgrade

[revolver87]

Just downloaded the upgrade to kore 2 hardware edition. The hardware now can control all plugins along with kores.. Just wondering does anyone know if it controls the daw or in my case logics own plugins.. Tried looking everywhere online but cant get an answer.. cheers

[sphelan]

I don't see any of Logic's instruments listed in my Kore2. Don't know, maybe we have to set something, but at the moment I don't think it's possible to control them with Kore2

[I_Am_Bic_Pentameter]

Thanks to the free KORE 2.1 update, the KORE controller is now a powerful universal hardware controller for use with any MIDI-compatible hardware or software.

The new Controller Editor application provides pre-mapped templates to use KORE as a MIDI controller for many NI and third-party products, as well as the option to fully customise your own MIDI assignments for any hardware/software set-up.

The KORE controller now features:

* Easily assign any button, pad and knob to a MIDI function:
From software to hardware synths, samplers, sequencers and effects

* Switch control from KORE 2 to other gear instantly with a dedicated hardware button

* Pre-produced templates for many Native Instruments and third-party instruments included

* Easily create your own custom KORE Controller settings using the included MIDI mapping software

* DAWs with Mackie Control Universal (MCU) support can be controlled easily with the KORE Controller. Information from the sequencer/DAW is shown on the hardware displays.

Video

That's all I could find

Edit:
how does midi get from kore 2 into logics clicks and port ?

when mackie control is not enabled using kore midi i/o midi gets fed into logic.


It doesn't get from Kore 2 to logic. Thats the whole point of the commentary above. The kore 2 software is not involved. The kore hardware connects to the hardware control service which outputs midi through a virtual midi port into logic. As you may recall, logic merges all available midi inputs unless you create a custom environment or change the configuration in the clicks and ports environment layer.

Previously when NI said [KORE] it meant this unified hardware and software system designed at all levels to be integrated together. Things took a slightly different direction when the software only version was released, and further when the global controller midi feature was added in the 2.0.4 update allowing most kore functions to be handled by a generic midi device of your choosing.

Now with 2.1, the hardware and software are completely separated yet there is still a tendency to say [KORE] and expect people to understand, which they don't. There is Kore HARDWARE which can now send midi to external devices and to other concurrent running apps like live or logic via a virtual midi cable; and the Kore SOFTWARE which is a great plugin host. The reason for this change is that NI is trying to unify all hardware support under a new system using the controller editor to make templates and the hardware control service to connect to the hardware. This new system started with Maschine and is now working with Kore. Following this pattern we might expect the other NI controllers like the Guitar Rig Controllers to eventually receive this kind of support. This is cool because you can use 1 editor and service to manage all your NI controllers even potentially using them all at the same time.

The kore software is not required for the kore hardware to generate midi events to external devices or other running apps. My gripe at this point is 2 fold - that this new way of 'dealing' midi hasn't brought midi generation to the kore software, and that the new editor and service package is only available through a kore updater. If they have separate functionality, I would prefer to have a separate installer for hardware support. Currently, hardware support is only possible if you have Maschine and Kore installed on the computer.

[revolver87]

great post.. cheers