Scooby’s Map for Traktor Scratch Pro & Korg nanoPAD
Repost from the NI Forums:
Well everybody, I’m hooked on Traktor, back in love with DJing, and blew an easy $60 on the Korg nanoPAD after I ended up watching TONS of Zabelia YouTube vids over the last 2 days.
I haven’t documented the whole thing but here’s my midi mapping for the Korg. This was designed for 2 decks and to be used with turntable control. Top Row is always Deck A and bottom is always B. All I’ll tell you is scene 1 is browsing and loading, and playing tracks. Scene 2 is looping. Scene 4 is Effects. I also designed it so that FX1 has 3 effects and FX2 only has 1. The Effect On/Offs are the modifiers for the XY and their respective amounts. It has taken me about 6 hours to take this this far. I use a lot of modifiers to map things to the XY Pad.
You WILL need to load my software into the Korg using the KORG KONTROL Editor. You’ll see both files in the ZIP.
No support will be given. YMMV. This is Freeware. Enjoy
Thanks a lot, that’s an awesome mapping. Do you ever run into the problem that the XY just doesn’t control the effects?
EDIT: Just kidding, I guess I’d just transferred the korg programming incorrectly, I reworked it and it works fine now. Thanks again for the sick setup!
hey thanks, i liked your nanopad setup.
i have a small problem, once i added your .TSI it seems to remove all the settings for my faderfox - so i can either have one or the other going…
It’s probably just that all of the controlls that the nanopad setup maps are the same as the controls from the faderfox, but a different mapping (so the stuff the faderfox once did now doesn’t happen, and instead some of the faderfox controls overlap the nanopad). You have two options: reprogram the faderfox outputs (if you have a program to do so similar to KORG KONTROL editor) and add new mappings in TSP (settings>midi at the bottom) (This option’s sort of a pain in the ass, but guaranteed to work if you do it right. Mostly it just takes a lot of time) OR if you don’t have a program to edit the outputs, you’ll have to totally remap the nanopad to use different control signals, which is an even bigger pain in the ass.
Unfortunately, there’s no way that I know of to just click go and have the two tsp settings merged so they don’t stomp on each other’s toes.
Scooby, did you just not map any of the middle two scenes (2/3) to anything? I’m looking through the control setup in the midi tab of TSP settings, and I can’t find anything that’s tied to keys other than in scenes 1 and 4. I’d have assumed the middle two scenes at least contained cue triggering or something. If this is not true, and I’m correct, I’ll fill that out myself and re post it here, but if I’m just wrong, I’d rather not do the extra work needlessly
I have T-Pro, no Scratch and no other controller apart from a nanoPAD. Anyone has a map that will let me use it on its own? I have played around but while the pads work, the XY doesn’t at all.
For all those having problems with the X/Y pad: the problem is that you aren’t loading global data to the korg. For some reason, you can load individual scenes OR you can do a global upload, and while the individual scenes get you the pads, XY info is only loaded when you do the global upload. It’s in a menu somewhere, and I don’t have my nanoPad with me so I can’t find it exactly right now, but basically look through the menus for something along the lines of “upload global data.” If you find it, post it here. If not and you’re still lost, post back and I’ll see if I can find it when I get home.
Unrelated, I’m actually working on building on top of this for the Pad, with the addition of two iPhone OS based additional controllers probably to control play functions while FX and cues are left to the nanoPad. We’ll see what I come up with, but it should be fun. Fair warning, it’ll probably be mac-only since I’ll probably use OSC and I’ll build my own OSC to MIDI translator patch in quartz composer.
From Korg KONTROL Editor, you can read/write data to/from the pad in two ways. You can read/write SCENE data, which ONLY pertains to the PADS in the current scene, and you can also read/write GLOBAL data, which is what you have to do in order to write XY pad data.
To reiterate, what you need to do in order to get scooby’s config onto the pad is to load the config into KONTROL Editor, then click the “Global” button in the top right corner. Click “write” and that should load the ENTIRE config to the pad, including the XY data.
Dean, they’re not terribly difficult to make. It’s mostly just a lot of keeping track of what you’ve assigned to what. Essentially, everything on the pad (or Kontrol) is assigned to a “note” which exists in a specific channel. Midi has 16 of these channels, but rarely do you need that many since each channel has 128 possible notes. In addition, each note is sent with a “velocity” which is intended to be a measure of how hard you hit it. The 'Pad, for example, has pressure-sensitive pads, so if you tap one lightly, the volume of the instrument you trigger is lower. Finally, there are also CC messages (cc meaning control channel) which are like notes but instead are sent as a value that updates something in the program, say, a slider.
The point of all that is it’s basically a matching game. Everything that changes a knob or slider in your program should be set up as a CC message from the Kontrol. More to the point, they should already be set up like that by default, so what I’d recommend is this: open KONTROL editor and change the global channel for your kontrol. This makes sure you don’t overlap any existing configuration. Then, (if you’re on mac) you can use the program midigram (http://mac.softpedia.com/get/Audio/Midigram.shtml) to see in real time what message each of the knobs/sliders in each scene sends. Then, just add those to the Midi config in preferences of your program, set up for what you want them to do.
It’ll probably take some getting used to, but as you play around, you’ll get a better sense of how to wire everything up to do what you want.
