Korg Forums

Has anyone figured out how to assign "chords" to the bottom row of pads (9-16)?
I have successfully assigned chords on pads 1-8 but CANNOT figure out if its even possible to get more than one note assigned to pads 9-16.
I don't see any information on-line on this topic regarding the BOTTOM row of pads on the NANOPAD 2.
Any help would be appreciated!!!
Thank you

The manuals of both versions of the Nanopad are very basic and neither describes the multiple note function for the trigger pads. The manual that comes with KorgKontrol Editor likewise.

In the latest (OS.2.) Parameter guide pg. 1129 it says:

Limitations of USB pad support.
The nanoPAD and nanoPAD2 both support multiple note assignments per pad. Only the first such event will be mapped to the KRONOS pads; the remainder act as normal MIDI in events.

I thought this was a bit ambiguous as it's not clear if this refers only to pads 1-8 (which are automatically assigned) or whether trigger pads 9-16 are also interpreted by the Kronos in the same way, when sending multiple note signals. (e.g. First event is a note and the other events (remaining notes) are interpreted as some other sort of 'normal' MIDI in data)

I've never tried assigned multiple notes to the Nanopad when in use with the Kronos, so can't speak from experience.

You can assign up to 4 notes per pad iirc with the nanopad editor software. The top 8 pads are constant regardless of scene, so you have 32 4-note chord pads in groups of 8 per scene, that need to be programmed in advance. The practicality of this setup? Depends on the user.

Sparker wrote:The manuals of both versions of the Nanopad are very basic and neither describes the multiple note function for the trigger pads. The manual that comes with KorgKontrol Editor likewise.

In the latest (OS.2.) Parameter guide pg. 1129 it says:

Limitations of USB pad support.
The nanoPAD and nanoPAD2 both support multiple note assignments per pad. Only the first such event will be mapped to the KRONOS pads; the remainder act as normal MIDI in events.

I thought this was a bit ambiguous as it's not clear if this refers only to pads 1-8 (which are automatically assigned) or whether trigger pads 9-16 are also interpreted by the Kronos in the same way, when sending multiple note signals. (e.g. First event is a note and the other events (remaining notes) are interpreted as some other sort of 'normal' MIDI in data)

Since only pads 1-8 are mapped to the pads, the note applies only to them. This seems pretty clear in context with the rest of the section, which goes into great detail as to how the mapping works; if you like, read it again and let me know if it still seems ambiguous to you.

shock410 wrote:Has anyone figured out how to assign "chords" to the bottom row of pads (9-16).

The pads 9-16 can be assign and edit using the Karma kronos software.

You could also set up those 8 Nano keys to different RPPR, particularly if you had an 88 (and had keys your not likely to need).

shock410: I checked the Nanopad multi-note assignment for trigger pads 9-12 (nanopad1) and it works fine.
I assigned a chord to pad 12 using the Korg Kontrol Editor software, transmitted the Scene Data to the Nanopad and when connected to the Kronos I get a chord sounding when I press pad 12.

Dan: My apologies. The guide is comprehensive about the auto-assign mapping to the first 8 trigger pads and dual assignments of the same message from different pads. What I was attemping to say was that I couldn't find any details in the guides (both Kronos & Nanopad Manuals) about the multi-note function assignment to pads 9-16.

There have been several threads on here and Karma-Lab about exactly how the Nanopads work with the Kronos, so I think it's fair to say that there's some level of user confusion about Nanopad operations.

Admittedly, a bit of hands on experimentation and common sense tells me what is and what is not possible to do. However, often it's easier to refer to the guide to see what the available parameters are and how they work; and I couldn't find anything detailing operations re: trigger pads 9-16.

My understanding is that:
a) The Nanopads automatically assign the Kronos Pads to the first 8 Trigger Pads on the Nanopad. (As explained in the guide)
b) That Trigger Pads 9-16 (9-12 on Vers.1) can be assigned to multi-note output that will play those notes as a chord in the Kronos - as long as there is no note replication of the trigger pad notes and the assigned (first) note for the auto-assigned pads 1-8.

And this means that with Nanopad2 it is possible to assign an extra eight 4 note chords (or four 8 note chords with Nanopad1) to the non-auto-assigned trigger pads; with the above proviso regarding the duplication of the notes that are recognised by the Kronos's pads.

Sparker wrote:Dan: My apologies. The guide is comprehensive about the auto-assign mapping to the first 8 trigger pads and dual assignments of the same message from different pads. What I was attemping to say was that I couldn't find any details in the guides (both Kronos & Nanopad Manuals) about the multi-note function assignment to pads 9-16.

There have been several threads on here and Karma-Lab about exactly how the Nanopads work with the Kronos, so I think it's fair to say that there's some level of user confusion about Nanopad operations.

Admittedly, a bit of hands on experimentation and common sense tells me what is and what is not possible to do. However, often it's easier to refer to the guide to see what the available parameters are and how they work; and I couldn't find anything detailing operations re: trigger pads 9-16.

My understanding is that:
a) The Nanopads automatically assign the Kronos Pads to the first 8 Trigger Pads on the Nanopad. (As explained in the guide)
b) That Trigger Pads 9-16 (9-12 on Vers.1) can be assigned to multi-note output that will play those notes as a chord in the Kronos - as long as there is no note replication of the trigger pad notes and the assigned (first) note for the auto-assigned pads 1-8.

Put simply, only pads 1-8 are treated in a special way (i.e., they are mapped to the internal KRONOS pads. Everything else is simply treated as MIDI input.

how can you assign rppr's to nanopads 9-12?