Nanokontrol2 on Traktor2 (4decks+metronomes+browsing+loop recorder)|v0.5
Home :: Post and find Controller Mappings :: Nanokontrol2 on Traktor2 (4decks+metronomes+browsing+loop recorder)|v0.5Reply
Nanokontrol2 on Traktor2 (4decks+metronomes+browsing+loop recorder)|v0.5 Posted on: 01.11.2011 by Simona Schar Here's my first mapping done all by myself (I often slightly modify some existing mappings, but never did the whole thing by myself... 'till now^^Here is a summary of what you'll control with this cheap controller mapping :
Here's how the mapping works : ************************************************** ************************************************ Midi*IN: 1 Modifier: Cycle Led Off/Cycle Led On 2 Browser layout+previous track/FX Unit 1 Deck C+A 3 Browser layout+next track/FX Unit 1 Deck B+D 4 Browser layout+page up/FX Unit 2 Deck C+A 5 Browser layout+next down/FX Unit 1 Deck B+D 6 Loop recorder*: define loop size /Fx Unit 1 Fx1 On/Off 7 Loop recorder dry/Fx Unit 1 Fx2 On/Off 8 Loop recorder wet/Fx Unit 1 Fx3 On/Off 9 Loop recorder*: delete loop/Fx Unit 2 Fx1 On/Off 10 Loop recorder*: play/pause loop/Fx Unit 2 Fx1 On/Off 11 Loop recorder*: record loop/Fx Unit 2 Fx1 On/Off 12 Filter 13 Loop size/ Fx Unit 1 control : DeckC : Dry/wet | DeckA : Fx1amount | DeckB : Fx2 | DeckD : Fx3 14 Load track+Return in mixer layout + play + loop set 15 Play/pause(pause reset all Eqs to normal state) 16 Loop On/off 17 Volume 18 Autorize 21 for High EQ/ High Kill 19 Autorize 21 for Mid EQ/ Mid Kill 20 Autorize 21 for Low EQ/ Low Kill 21 Multi Eqs fader/ Fx unit2 control*DeckC : Dry/wet | DeckA:Fx1amount | DeckB:Fx2 | DeckD:Fx3 MIDI OUT*: 1 Cycle On/Off*: Led ON/ Led Off 4 Quantize Mode On*: Led ON 5 Snap Mode On*: Led ON 10 Loop recorded playing*: ON 11 Recording*loop: Led ON 14+15+16*: Playing track*: Vumeter 14+15+16*: Playing loop (inverted vumeter) 18*: Kill high Eq*: Led Off 19*: Kill Mid Eq*: Led Off 20*: Kill Low Eq*: Led Off ************************************************** ************************************************** ***** Changelog VERSION*(0,5) : First version, put the main functions together working, define ergonomy VERSION*(0,6) : - Major Improvement : Two mods
- Improved browsing functions. VERSION 0,7 : - Minor Version : - Vuemeter Led Issue partially solved, - EQs state reset when pausing the track - Creating a better mapping documentation ************************************************** ************************************************ Future improvements :
My own Impressions : About the One Faders three band EQs : This part of the mapping is both the thing I like the most (I thought I can | |
| Chasidy Heckenbach 12.11.2011 |
Originally Posted by Just Friday
that debug file is showing that some other app has grabbed the lpd8 ports, or had grabbed and not released them properly, so midimasher wasn't about to connect. i usually see that if i run traktor before running midimasher, or something else like midiox etc. also just very occasionally i've seen that error when even tho i've quit traktor the midi ports haven't been released properly. it does output "failed to open out port LPD8" in that trace - but it's a bit hidden by all the default RtMidi lib errors. i should try and clean that up. it does detect the lpd8 and correctly work out what port indexes to open. very off topic but at least this is your own thread |
| Chasidy Heckenbach 12.11.2011 |
Originally Posted by Just Friday
|
| Chasidy Heckenbach 11.11.2011 |
Originally Posted by Just Friday
is there any chance u could give it another shot? in debug mode run that config but without traktor and see if u get any debug at all when u press button on the lpd8? and if not do u get any output when u run dump.exe, select the lpd8 and press some buttons? it's almost the weekend and i have plenty of time to fix any issues in midimasher and also going to finally release a full multipage launchpad config. probably going to mod the "itch slicer" to use the method chris described on the blog post "String Theory for DJs". it'll still flash each pad on the beat like the twitch one but use his method of dropping a hot cue at the start of the 8 beats and always jumping to that cue before then sending beatjumps back to where i need to be. should make it much more reliable. that "twitch slicer" also works on the lpd8 btw - any grid controller in fact - even any controller that has grid pads in it's devices file, tho it's much more fun with led feedback on the pads |
| Chasidy Heckenbach 11.11.2011 |
Originally Posted by Just Friday
sounds like it wasn't able to connect to the lpd8 properly anyway. |
| Chasidy Heckenbach 09.11.2011 |
Originally Posted by Just Friday
just need to know whether midimasher is sending the midi fighter midi to traktor or not - then we'll know whether it's my issue or a traktor setup one. |
| Marybeth Sardone 29.12.2011 | awesome! thank's so much dude! keep up the good work!! |
| Simona Schar 29.12.2011 | No problem. It's totally normal. By default, Leds are set up as in internal mode(you press the button, the led lights up). To have the VUmeter and all the external output, you need to install korg driver and nanoseries manager, then plug your nanokontrol2 in, and switch LEDs mode from internal to external in the device manager. That's all. Hope it helps Regards, Pierre. |
| Marybeth Sardone 29.12.2011 | hey all i just got a nanoKontrol2 in the mail today, and i tried this mapping but my outputs arent working so i can not tell when, IE. the modifier is on or off. any help with this would be appreciated! right now the buttons only light up when pressed and shut off after release. |
| Chasidy Heckenbach 12.11.2011 |
Originally Posted by Just Friday
that debug file is showing that some other app has grabbed the lpd8 ports, or had grabbed and not released them properly, so midimasher wasn't about to connect. i usually see that if i run traktor before running midimasher, or something else like midiox etc. also just very occasionally i've seen that error when even tho i've quit traktor the midi ports haven't been released properly. it does output "failed to open out port LPD8" in that trace - but it's a bit hidden by all the default RtMidi lib errors. i should try and clean that up. it does detect the lpd8 and correctly work out what port indexes to open. very off topic but at least this is your own thread |
| Simona Schar 12.11.2011 | Here's my second debug file. It takes some times to do it (my day by day installation is ubntu based...). This looks even worse than the previous backtrace with traktor... Nevertheless, hope it helps... BTW, the nanokontrol2 thread was totaly highjacked by our midimasher talk... No offense, I did the half of the answers |
| Chasidy Heckenbach 12.11.2011 |
Originally Posted by Just Friday
|
| Simona Schar 12.11.2011 | Ok... I'll do it for shure! |
| Chasidy Heckenbach 11.11.2011 |
Originally Posted by Just Friday
is there any chance u could give it another shot? in debug mode run that config but without traktor and see if u get any debug at all when u press button on the lpd8? and if not do u get any output when u run dump.exe, select the lpd8 and press some buttons? it's almost the weekend and i have plenty of time to fix any issues in midimasher and also going to finally release a full multipage launchpad config. probably going to mod the "itch slicer" to use the method chris described on the blog post "String Theory for DJs". it'll still flash each pad on the beat like the twitch one but use his method of dropping a hot cue at the start of the 8 beats and always jumping to that cue before then sending beatjumps back to where i need to be. should make it much more reliable. that "twitch slicer" also works on the lpd8 btw - any grid controller in fact - even any controller that has grid pads in it's devices file, tho it's much more fun with led feedback on the pads |
| Simona Schar 11.11.2011 | Does it mean I found a bug ? :$ |
| Chasidy Heckenbach 11.11.2011 |
Originally Posted by Just Friday
sounds like it wasn't able to connect to the lpd8 properly anyway. |
| Simona Schar 10.11.2011 | In the beginning of the debug file, I pressed a few buttons before launching traktor... However, I found a solution. Not the best, but it works more or less and let me wait my foreseas coming midifighter! |
| Chasidy Heckenbach 09.11.2011 | there's no data in that debug log at all from your lpd8 - very odd. can u press some buttons when traktor isn't playing - and see whats in the log? tho there should have been lpd8 and midi fighter stuff in there as well as the beatphase and levels from traktor ofc. you don't get any warnings from midimasher when u start it now? ah - did u use the akai lpd8 editor and configure your lpd8 with the file settings/lpd8_editor_config.txt ? could be your lpd8 is setup differently to mine *but* there still should have been some messages in the debug log from your lpd8 - even if midimasher didn't understand what the messages were. i'll plug in my lpd8 tomorrow with traktor and dble check things and paste the output i would expect to see. any input from any connected midi device should be in that log in theory. at least we know that traktor is connected now ofc as the beatphase is in there. |
| Simona Schar 09.11.2011 | Here's the debug file. My traktor config is : Midimasher MM to Traktor/Traktor to MM (focus) MF Bank[A] : MidiFighter1 Input/Midifighter1 Output (Deck A) MFBank[B] : MidiFighter1 Input/Midifighter1 Output (Deck B) MFBank[C] : MidiFighter1 Input/Midifighter1 Output (Deck C) MFBank[D] : MidiFighter1 Input/Midifighter1 Output (Deck D) What did I do wrong? |
| Chasidy Heckenbach 09.11.2011 |
Originally Posted by Just Friday
just need to know whether midimasher is sending the midi fighter midi to traktor or not - then we'll know whether it's my issue or a traktor setup one. |
| Simona Schar 09.11.2011 | Thanks a lot!!! It works in the midimasher, but after, i donno why, but there's still nothing... I launch Midimasher, everything seems ok, but after, nothing happens... I use the instant grat 1.0.3 tsi... I loaded it twice, etc... I don't understand... |
| Chasidy Heckenbach 09.11.2011 |
Originally Posted by Just Friday
traktor: open midi.in.2: Traktor to MM
warning: no midi out device [MM to Traktor] loading: devices/traktor.lua loading: lib/traktor.lua lpd8: open midi.in.0: LPD8 lpd8: open midi.out.1: LPD8 loading: devices/lpd8.lua warning: no midi in device [MidiFighter1 Input] warning: no midi out device [MidiFighter1 Output] running... <ctrl>-<c> to quit. Obviously, something went wrong... but what??? similar issue for your virtual midifighter ports as you added a space with "MidiFighter 1 Input" where the code was looking for "MidiFighter1 Input" i'll also fix that in the next release. it already matches on a device called "1-Launchpad" if you call the device "Launchpad" in the config (due to windows multiple device renaming) so i'll strip the spaces and convert to lower case before the final check. renaming your loopMIDI ports should make it work tho. hopefully soon this will be a mute point anyway (for virtual devices anyway) as i've been in contact with the authour of loopMIDI and hopefully he'll be giving me access to an interface that will allow midimasher to create/delete virtual ports on the fly. |
| Simona Schar 08.11.2011 | I didn't succed in making the midimasher work... I followed the tutorial : loopmidi config, then traktor launch + double instant grat mapping load then traktor launch for the third time, then load the traktor.tsi mapping, then config (and here's where it's not clear for me... I did as can : the midimasher mappin MM to Traktor/Traktor to MM, the Midi fighter banks : MidiFighter 1 I/O)... Of course I have tried with the midimasher last version, and here's what I obtain : Code:
midimasher: build 20111026 #1: default.lua #2: launchpad.lua #3: lpd8.lua #4: lpd8_midifighter_4banks.lua #5: mpd18_midifighter_4banks.lua select a config > 4 midi: scan devices... midi.in.0: LPD8 midi.in.1: MM to trakor midi.in.2: Traktor to MM midi.in.3: MidiFighter 1 Input midi.in.4: MidiFighter 1 Output midi.in.5: MidiFighter 2 Input midi.in.6: MidiFighter 2 Output midi.out.0: Microsoft GS Wavetable Synth midi.out.1: LPD8 midi.out.2: MM to trakor midi.out.3: Traktor to MM midi.out.4: MidiFighter 1 Input midi.out.5: MidiFighter 1 Output midi.out.6: MidiFighter 2 Input midi.out.7: MidiFighter 2 Output lua: register functions... lua: run embedded lua... loading: lib/startup.lua loading: config/lpd8_midifighter_4banks.lua traktor: open midi.in.2: Traktor to MM warning: no midi out device [MM to Traktor] loading: devices/traktor.lua loading: lib/traktor.lua lpd8: open midi.in.0: LPD8 lpd8: open midi.out.1: LPD8 loading: devices/lpd8.lua warning: no midi in device [MidiFighter1 Input] warning: no midi out device [MidiFighter1 Output] running... <ctrl>-<c> to quit. |
| Chasidy Heckenbach 07.11.2011 |
Originally Posted by Just Friday
it has a massive tsi and associated config that tells it what messages to send out to do different things in traktor. like to create a toggle button to control the playing of deck 'a' you'd use something like this in your config file: Code:
toggle("lpd8", "1,0", 1, ON, OFF, "traktor", "play_a")
|
| Simona Schar 07.11.2011 |
Originally Posted by zestoi
Originally Posted by zestoi
I just wanted to see how I can map some instant grat functionnality, in order to add it to my all-in-one ldp8 mapping... |
| Chasidy Heckenbach 06.11.2011 |
Originally Posted by Just Friday
Furthermore, I plan to use the midifighter "instant gratification" adaptation for 2 ldp8 and map the more i can on 1 ldp8... I'll do my best to map the more I can... do you believe it's possible (for exemple, mapping the combos on one button, and of course, I know I can't use the banking mode (( ) ?
there's also this config http://midimasher.djism.com/lua/config/lpd8.lua that i created for the lpd8 that has a twitch style "slicer" when u are in CC mode. not 100% sure i haven't broken something that it needs to recently while doing more launchpad stuff. |
| Simona Schar 06.11.2011 |
Originally Posted by zestoi
Originally Posted by zestoi
Of course, it won't work with everything, but I hope I could find enough modifiers to map everything. Do you believe it's the good way to deal with this controler? Furthermore, I plan to use the midifighter "instant gratification" adaptation for 2 ldp8 and map the more i can on 1 ldp8... I'll do my best to map the more I can... do you believe it's possible (for exemple, mapping the combos on one button, and of course, I know I can't use the banking mode (( ) ? |
| Chasidy Heckenbach 06.11.2011 |
Originally Posted by Just Friday
the biggest pain with the lpd8 is a pad's led will *always* turn off once you release the pad, even if traktor had sent the pad a message to turn it on. to work round that u need to send the lpd8 another midi message to turn it back on when u release. the other issue that i can believe of is while in PAD mode the lpd8 ignores any CC's and vice versa. so when u switch to CC mode the lpd8 will light up the pads exactly the same as the last time u were in CC mode - minus any midi messages that u may have sent to it since. nothing u can really do about that issue. |
| Simona Schar 06.11.2011 | New version (the last before the mapping is completly over, I guess...)...It's stable, and has few issues... The next (and last, with four FX units) version will be released in few weeks. I start working seriously on the LDP8... |
<< Back to Post and find Controller MappingsReply