KRONOS and Korg padKontrol - FUN!

[Yuma]

But not really - so here we go.

...

The only other solution is an update in firmware from Korg for the padKontrol or someone hacking the padKontrol.

Again, this is the best solution for now. I'm tired!

Hey Ernie,

Thanks for trying, man. I really appreciate it.
From your post I understand that you ran into the same issues as I did.

Since step 3 already works for me (recording MIDI-data generated by the virtual pads of the Kronos into CuBase) and
step 4 most likely will work as well (recording MIDI-data generated by the pads of the PadKontrol directly into CuBase),
I guess that means there's no real solution for what I wanted (triggering the virtual pads on the Kronos by the PadKontrol and recording the generated MIDI-data into CuBase).

Too bad for now, but thanks for your time again!

Cheers,

Yuma

[jamsire]

But not really - so here we go.

...

The only other solution is an update in firmware from Korg for the padKontrol or someone hacking the padKontrol.

Again, this is the best solution for now. I'm tired!

I guess that means there's no real solution for what I wanted (triggering the virtual pads on the Kronos by the PadKontrol and recording the generated MIDI-data into CuBase).

Too bad for now, but thanks for your time again!

Cheers,

Yuma

Yuma - I'm a little confused here. You can do what you want - I said so here:

3. Recording the PADS from the KRONOS into CUBASE: padKontrol into Kronos, USB from Kronos into the computer. Set the midi in on the midi track to KRONOS KEYBOARD - IT WILL RECORD the chord notes. The midi channel is irrelevant - just set it to "ANY." Set the output for the midi data to KRONOS SOUND - AFTER YOU RECORD!! You'll hear some weird phasing if you have both midi in and midi out on at the same time (or maybe you won't - I did).

It works - you just don't get the drums on the last 8 pads. I'm still confused.

[Yuma]

Hi Ernie,

That only works for me when I set up the PadKONTROL as I wrote earlier in this thread:

After some trial&error I found out that, to trigger the Kronos on screen pads, I have to send MIDI notes from the PadKontrol to the Kronos.
Those MIDI notes are not interpreted by the Kronos as MIDI notes, but as triggers for the on screen pads.

To trigger on screen pad 1, I have to send note C˚4 to the Kronos.
To trigger on screen pad 2, I have to send note A4 to the Kronos.
To trigger on screen pad 3, I have to send note F4 to the Kronos.
To trigger on screen pad 4, I have to send note D˚4 to the Kronos.
To trigger on screen pad 5, I have to send note C4 to the Kronos.
To trigger on screen pad 6, I have to send note B3 to the Kronos.
To trigger on screen pad 7, I have to send note A3 to the Kronos.
To trigger on screen pad 8, I have to send note G3 to the Kronos.

I have no clue why this is, but maybe this has to do with the integration of Korg products.
This way I can succesfully record the MIDI notes of the on screen pads to my DAW.

So if I set up the PadKONTROL to have pad 1 send C˚4 to the Kronos, the Kronos will trigger virtual pad 1.
If I program virtual pad 1 to play a C-chord, that results in my CuBase recording that chord.
See picture below.



I have no clue why it does work, when I do it this way.
But this goes only for triggering the virtual pads.

I can't trigger the keyboard keys by the PadKONTROL pads in such a way,
that I can record the MIDI in CuBase. I can only record the generated audio in that case.

So to summarise:

1) Having the PadKONTROL trigger the virtual pads on the Kronos and recording the resulting generated MIDI-data in CuBase works.
2) Having the PadKONTROL trigger the keys on the Kronos and recording the resulting generated MIDI-data in CuBase doesn't work.

It's step 1 that's working (eventhough I don't understand why).
It's step 2 that I'm after to get working.

[jamsire]

Hi Ernie,

That only works for me when I set up the PadKONTROL as I wrote earlier in this thread:

After some trial&error I found out that, to trigger the Kronos on screen pads, I have to send MIDI notes from the PadKontrol to the Kronos.
Those MIDI notes are not interpreted by the Kronos as MIDI notes, but as triggers for the on screen pads.

To trigger on screen pad 1, I have to send note C˚4 to the Kronos.
To trigger on screen pad 2, I have to send note A4 to the Kronos.
To trigger on screen pad 3, I have to send note F4 to the Kronos.
To trigger on screen pad 4, I have to send note D˚4 to the Kronos.
To trigger on screen pad 5, I have to send note C4 to the Kronos.
To trigger on screen pad 6, I have to send note B3 to the Kronos.
To trigger on screen pad 7, I have to send note A3 to the Kronos.
To trigger on screen pad 8, I have to send note G3 to the Kronos.

I have no clue why this is, but maybe this has to do with the integration of Korg products.
This way I can succesfully record the MIDI notes of the on screen pads to my DAW.

So if I set up the PadKONTROL to have pad 1 send C˚4 to the Kronos, the Kronos will trigger virtual pad 1.
If I program virtual pad 1 to play a C-chord, that results in my CuBase recording that chord.
See picture below.



I have no clue why it does work, when I do it this way.
But this goes only for triggering the virtual pads.

I can't trigger the keyboard keys by the PadKONTROL pads in such a way,
that I can record the MIDI in CuBase. I can only record the generated audio in that case.

So to summarise:

1) Having the PadKONTROL trigger the virtual pads on the Kronos and recording the resulting generated MIDI-data in CuBase works.
2) Having the PadKONTROL trigger the keys on the Kronos and recording the resulting generated MIDI-data in CuBase doesn't work.

It's step 1 that's working (eventhough I don't understand why).
It's step 2 that I'm after to get working.

Ok Yuma - you missed that part in my video when I said - "Change the MIDI CHANNEL of the pad on the padKontrol from midi channel 10 to midi channel 1." You will get the single notes only.

Try it - that works for sure.

[jamsire]

Ok - the mystery has been solved. I don't smell good as I have been at this for a while.

Yuma said he could do the pads and play the chords - but he could not get the pads on the padKontrol to play "SINGLE" notes into Cubase.

SOLUTION:

The notes you assign on the padKontrol are IRRELEVANT!!! If you want to play single notes using the padKontrol - you must do either one of the following:

1. Go the program patch and turn it to MONO in the Program/ Basic tab under the Vector/ Basic tab. Then what you will hear is the LAST NOTE of the chord on the virtual pads. A bass patch is the perfect way to see this work.

2. Make a new patch of WHATEVER - and program ONE NOTE per pad. Same thing.

The notes you program with the padKontrol are irrelevant - trust me. You have to do it in the pads tab.

D-O-N-E!!!

I want to thank you all for challenging me. I've been suffering with a horrible foot injury and this was a great distraction.

Yuma - you are diagram master!

[Yuma]

Hi Ernie,

I have my virtual pads on the Kronos set to MIDI channel 10, because I normally use them for drums.
When I have the MIDI channel on the PadKONTROL set to 10 as well, then I can trigger the virtual pads on the Kronos AND record the
resulting MIDI data (= whatever I programmed on the virtual pads) in CuBase.

Let's say I assign a Strings patch to MIDI channel 1.
In that case you are correct when you say that changing the MIDI channel on the PadKONTROL from 10 to 1 will result in a single note.
The reason for this is, that the note programmed in the PadKONTROL goes to MIDI channel 1, which triggers the Strings patch.
You can change the note programmed in the PadKONTROL to a different one and hear the Strings patch play that different note.

I can reproduce that, and I can hear the String sound of the note coming from the Kronos.
But... the MIDI data related to that note is not send through to my CuBase.

I noticed in your video in the opening post, that yours isn't sending MIDI data from that single note either to your DAW.
I saw that in the bottom part of the editor as there was no MIDI activity when you played that single note pad.
There was only MIDI activity when you played the chord pads (the ones that trigger the virtual pads on the Kronos).
So it seems you can't record that note either in your DAW.

And yes, I can program a single note per virtual pad on the Kronos, but that I consider a work-around.
Nevertheless, that's what I've been doing since I have the PadKONTROL.

It would have been nice if I could have triggered AND recorded MIDI notes for the full range of
my keyboard (61 keys) by creating 4 scenes (4x16=64 pads) on the PadKONTROL.
I guess there's no solution at the moment, only the work-around.

Thanks again for your efforts.

Yuma

[jamsire]

Hi Ernie,

I have my virtual pads on the Kronos set to MIDI channel 10, because I normally use them for drums.

That's the first mistake - you do NOT have to set the pads to ANYTHING - you change the Global channel to go out to Cubase - especially if your drums are in Cubase, or you're coming back into Kronos via a Combi. I realized that you have to do this anyway when you are sequencing in the Kronos


When I have the MIDI channel on the PadKONTROL set to 10 as well, then I can trigger the virtual pads on the Kronos AND record the
resulting MIDI data (= whatever I programmed on the virtual pads) in CuBase.

True - in fact - you never have to change the midi channels in the padKontrol - I realized that as well.

Let's say I assign a Strings patch to MIDI channel 1.
In that case you are correct when you say that changing the MIDI channel on the PadKONTROL from 10 to 1 will result in a single note.
The reason for this is, that the note programmed in the PadKONTROL goes to MIDI channel 1, which triggers the Strings patch.
You can change the note programmed in the PadKONTROL to a different one and hear the Strings patch play that different note.

I can reproduce that, and I can hear the String sound of the note coming from the Kronos.
But... the MIDI data related to that note is not send through to my
CuBase.

I noticed in your video in the opening post, that yours isn't sending MIDI data from that single note either to your DAW.
I saw that in the bottom part of the editor as there was no MIDI activity when you played that single note pad.


I realized that when I re-watched my video - and now - I say don't do that.

There was only MIDI activity when you played the chord pads (the ones that trigger the virtual pads on the Kronos).
So it seems you can't record that note either in your DAW.

Again, I realized that - BUT - this only happens when you plug the padKontrol directly into the Kronos. If you plug it directly into the computer, it will work as you desire.

And yes, I can program a single note per virtual pad on the Kronos, but that I consider a work-around.
Nevertheless, that's what I've been doing since I have the PadKONTROL.

It would have been nice if I could have triggered AND recorded MIDI notes for the full range of
my keyboard (61 keys) by creating 4 scenes (4x16=64 pads) on the PadKONTROL.
I guess there's no solution at the moment, only the work-around.

[b]If you plug it directly into the computer, it will work as you desire.
[/b]
Thanks again for your efforts.

I'm not done!!! Thank you for the challenge.

Yuma

[Yuma]

Again, I realized that - BUT - this only happens when you plug the padKontrol directly into the Kronos. If you plug it directly into the computer, it will work as you desire.

The starting point of my posts in this thread was though that I wanted to plug the PadKONTROL into the Kronos, not into my DAW.

As I understand now, it will all work when I plug in the PadKONTROL into my DAW and trigger the Kronos from there.
I guess I'll have to go that way then.

[jamsire]

Again, I realized that - BUT - this only happens when you plug the padKontrol directly into the Kronos. If you plug it directly into the computer, it will work as you desire.

The starting point of my posts in this thread was though that I wanted to plug the PadKONTROL into the Kronos, not into my DAW.

As I understand now, it will all work when I plug in the PadKONTROL into my DAW and trigger the Kronos from there.
I guess I'll have to go that way then.

Yup, but I realized the reason why after carefully reading BOTH manuals on the USB devices matter.

The Kronos just reads what the usb device is sending out and updates itself accordingly. BUT for full integration - the Kronos itself is limited because you can't load the USB device driver into the Kronos to really program it. The Kronos instantly sees the padKontrol, nanopad, nanopad2 and directs the pads to the virtual pads. I think an AWESOME "Wish List" item would be to have to the Kronos OS updated to sense these Korg USB devices and have an option to have them control the pads or not.

I am also still trying to see if this is a USB issue. I have a power adapter for the padKontrol and I will try and use that with the traditional midi out of the padKontrol into the Kronos traditional midi input. I'll keep you posted.

But the only question I have left for you Yuma is that if you are trying to record midi into your DAW - Cubase, why is plugging the USB into the computer "a workaround" if it works perfectly? I can understand if you were plugging into the Kronos in a live situation on stage, in a performance, etc., but for at home, in the studio sequencing - it works perfectly. Especially your great idea about have 4 scenes to access all of your keys on the 61K - which I can see being useful for orchestral combi's with percussion (and I may actually try this today with the padKontrol editor).

But remember - you never have to change the midi channels on the padKontrol, you have to change the Global channel in the Kronos to trigger the sound you want in the combi's.

Let's keep trying to make this happen! The main reason I'm still on the case is because you could easily be one of my students or clients that is trying to figure this out - and I should have an answer.

Ernie

[Yuma]

Basically my reasons for hooking up the PadKONTROL to the Kronos, instead of my PC, is because my PC is already stuffed with USB devices.

I'll see if I can read the PadKONTROL manual soon about connecting through my DAW and how to control the Kronos from within CuBase.

[jamsire]

Basically my reasons for hooking up the PadKONTROL to the Kronos, instead of my PC, is because my PC is already stuffed with USB devices.

I'll see if I can read the PadKONTROL manual soon about connecting through my DAW and how to control the Kronos from within CuBase.

Ok. I'm still on the case. With the padKontrol, you have to make sure you install the latest Korg USB driver. That's all you really need and Cubase with see it. Use Port A.

Ernie

[Lou]

A very simple workaround ..
If you recorded a track or tracks with chord changes, (midi) Simply make a quick one track stereo audio recording all tracks.
Now select a drum kit (on Kronos) and mute all MIDI tracks in Cubase, playback the audio while laying down your drum track, (pads, midi notes and all)

Now mute the audio track and playback all MIDI tracks with the drum track on channel 10.
In Kronos make sure the drum kit you chose is on channel 10 (Kronos Drum Track) done.

[jamsire]

A very simple workaround ..
If you recorded a track or tracks with chord changes, (midi) Simply make a quick one track stereo audio recording all tracks.
Now select a drum kit (on Kronos) and mute all MIDI tracks in Cubase, playback the audio while laying down your drum track, (pads, midi notes and all)

Now mute the audio track and playback all MIDI tracks with the drum track on channel 10.
In Kronos make sure the drum kit you chose is on channel 10 (Kronos Drum Track) done.

Sorry Lou - I completely figured it out and it's even more simple than what you wrote above. I have to do a video - because it's amazing.

[jamsire]

DONE!!!!

http://www.youtube.com/watch?feature=pl ... jnyI_mM27k

I remain!

[Lou]

Jamsire,

In the video when you played back the track (which was recorded with karma midi) what you should do is turn the karma switch off or local control off on kronos, that is why you were getting all the double notes.

Also thank you for doing the work, this should help Yuma out.
Unfortunately I'm using a nanopad, USB.
You have a lot more options with Padkontrol..