How to map an Omni control
How to map an Omni control Posted on: 22.11.2010 by Rena Conde Hi all,I've got an Omni control and the latest traktor pro, and I'm looking at making my own map for my control, but don't have a clue on where to start!! I've downloaded a couple of TSI files (DJ Stormeagles and some 4 deck control files) and would like to combine some of the features of each to make "my own" mapping. I looking for any help, tips or comments on how i go about creating my own mapping as i litterally dont have a clue where to start! Hopefully this will also help others in a similar position! Thanks for your time in advance. Olie | |
| Rena Conde 22.11.2010 | Hi all, I've got an Omni control and the latest traktor pro, and I'm looking at making my own map for my control, but don't have a clue on where to start!! I've downloaded a couple of TSI files (DJ Stormeagles and some 4 deck control files) and would like to combine some of the features of each to make "my own" mapping. I looking for any help, tips or comments on how i go about creating my own mapping as i litterally dont have a clue where to start! Hopefully this will also help others in a similar position! Thanks for your time in advance. Olie |
| Annalisa Shogren 25.11.2010 | The LEDs are a bitch to map, I'll tell you that now. Haha. |
| Leida Blasko 22.11.2010 | Go into preferences... then into controller manager when you get there, this is basically lists all the controllers you currently have set up for traktor (through USB/MIDI). Select whatever device you want to map to in the drop down menu. Basically from here, you can ignore the right 2 drop down menus that say in-port and output and you can also ignor the device target drop down menu (for simple mappings, i never mess with those). So from here you basically have 2 kinds of mappings: input and output input mappings are what you will mostly be doing (buttons, knobs, faders, etc) output mappings are for LEDs and other visual output devices (levels, mode identifying, ect) so I'm just going to help you with In mappings because that is what you will mostly be doing, and they are the easiest to get familiar with. I'm assuming you have an omni control if you looked at my mapping, if you have another device that you want to play around with. Click: Add In>>Cue/Loops>>Select/Set+Store Hotcue - click: Learn (now the next button you press will be assigned to this control) - press a button on your keyboard or whatever button you want to map this to on your controller - traktor will detect if it is a button or fader/knob usually and display under "type of controller" interaction mode changes which kind of interaction mode this button will use, just select "hold" - on the right side where it says "assignment" select Deck A You have just learned how to map an input as a hotcue While you have a track playing in deck A, press whatever button you mapped to and you will store a hotcue there. you can then press that button as fast or whenever you want, and the track will play from that point. So for a more complex mapping, you can use modifiers to configure for different Decks or whatever else (I used modifier 7=0 for Deck A mod 7=1 for Deck C, 8=0 Deck B, 8=1 Deck D) This was so you could use the same controller for 4 decks. The pitchbend buttons feedback which deck you are in. Hopefully this makes sense and you got a mapping, I basically learned how to map just by messing around with it. BTW: You should buy a Korg nanoKontrol. This is absolutely worth the 50 bucks or whatever. 9 knobs, 9 faders, 18+6 buttons. I just started mapping everything to mine. Let me know if you need some more help. |
<< Back to Post and find Controller MappingsReply