Korg Forums

I would assume you both are using Windows? If so, there are two potential causes for this that I know of. 1. You’re using the standard Windows driver that gets installed when you initially connect the controller to a USB port. This driver is NOT multi-client meaning that it can only be used in one a ...

Sorry for no updates last week. Bunch of new files added today though.

http://beatwise.proboards80.com

I’m not happy with that either, but can’t really complain for the money. Would be nice if Korg released the implementation so we could look into fixing it ourselves.

Anyhow, more scenes and utilities were added today.

http://beatwise.proboards80.com

The nanoSERIES are great controllers for the money. They’d be even better if they came with a wider selection of scene sets. Since they don’t, I think it would be a good idea for us users to pool our scenes together and make an easy to access online resource for nanoSERIES scenes. I’ve got one start ...

Sharing scenes is a real good idea. I have a bunch available and you’re more than welcome to contribute.

http://beatwise.proboards80.com

Can’t really say for sure without seeing the MIDI implementation for the nanos, which Korg Support said they won’t be releasing. I can tell you that the SysEx for the native mode in/out request is nearly identical for the pK/mK/Kontrol 49…the only difference is the model# for each. The nanoPAD and KO ...

I have an app (nativeKONTROL Reason) that adds Reason remote capabilities to the pK, but it’s relatively basic. It emulates the Frontier Design Tranzport. Unfortunately, the pK doesn’t have enough knobs or displays to emulate something like the microKontrol. But, along with remote abilities, my app a ...

It might have something to do with the amperage of the adapter you’re using. I’m not sure what Korg recommends, but the 9v/0.2 amp adapter I have works perfectly.

Ableton Live mainly.

Really nice work.

If it’s anything like the padKontrol (which I think it is), when connected by USB, the MIDI ports become a MIDI interface. If you go into Live’s MIDI prefs, you should see a listing for mK MIDI out under Outputs. Turn Track on for that port and you should be good to go.

To save writing space…controls = knobs and X/Y. It’s kind of strange. On Scenes 1-9, the controls will send on the highest MIDI ch you have assigned to the pads to be affected by the controls. So if all your pads are set up to be affected and send on ch 1, but one pad is assigned to ch 2…the contr ...

I don’t really have anything else I could suggest. Maybe someone with more knowledge on Reason can help you out…I’ve really only used it a couple time.

I’m not really sure what the problem could be. But you’re saying only Combinator works for you? What happens if you select Subtractor or NN19?

So you got 4 outs…the pK, the QY, the MC and the keys. And you got 3 ins…the QY, the MC and the SP. If the keys have sounds you’re using, that would make 4 ins. I don’t know of any 4 x 4 patch bays. There is a nice 3 x 8 Thru box made by MidiMan which might do the trick. But you’d probably be better ...