i just published my new mapping (Elephant’s map) , which is a crosslinked VCI-400SE, MASCHINE, and BCR-2000 solution using Virtual Midi Ports (created by LoopBe30) and MIDIOX as middleware.
One special thing about it that I use Midi feedback techniques i call Midi Linked Modifiers (MLM) to implement:
Global Traktor Modifiers (used here for inter-communication between involved Traktor devices)
Ability to read any Traktor Midi Out event into a Modifier (used for advanced processing)
Ability to put a given set of mapping statements into a conrolled sequence of processing
(an alternative to the “String Theory for DJs” published on the DJTT blog).
Even if you don’t own one of theses controllers the video/documentation might contain interesting information for you as the MLM concept and implementation is explained.
Pretty exciting stuff! I’ve been thinking about this type of thing for a while.
It’s MADNESS that Traktor’s modifiers can’t work across mappings/controllers. I’ve been thinking for a while about combining my Zomo MC-1000 and my Dicers into a single controller in Midi-Ox, so that when a modifier is active on the MC-1000, I get a different set of commands from the Dicers. I want to have full 4 deck control from the Zomo + the Dicers, and there is already full 4 deck control from the Zomo - so I need a way to have the Zomo modifier affect the Dicers. I’d also like to incorporate my Launchpad into teh mapping - but there are some controller conflicts with the Zomo that I need to iron out first!
I look forward to watching your vid - and I will be back with questions!
It’s really awesome what you can do with “thinking” midi routing and Traktor mapping. I find a way to hack in to the Loop Recorder and use it’s beat position output to start up the step sequencer like LED pattern which is always on time with Traktor’s internal MIDI clock speed. (no midi offset issue with this one)
Try this cascade when selected track loads to Deck A:
Midi OUT 001 _ Load Modifier OUT
Midi IN 001 _ Sync On = Yes
Midi IN 001 _ Loop Size = 4
Midi IN 001 _ High Adjust Reset
Midi IN 001 _ High Kill Off
Midi IN 001 _ Mid Adjust Reset
Midi IN 001 _ Mid Kill Off
Midi IN 001 _ Low Adjust Reset
Midi IN 001 _ Low Kill Off
Midi IN 001 _ Filter Adjust Reset
Midi IN 001 _ Filter Off
Midi IN 001 _ Balance Adjust Reset
Midi IN 001 _ Monitor Cue On
Midi IN 001 _ FX Unit 1 Off
Midi IN 001 _ FX Unit 2 Off
Midi IN 001 _ FX Unit 3 Off
Midi IN 001 _ FX Unit 4 Off
Midi IN 001 _ Key Adjust Reset
Midi IN 001 _ Flux Mode Off
It is nessesary to route the Midi-Out Port virtual to the Midi-In Port.
Traktor can accept the input for all those commands at once. No need for advanced mapping trickery right there
But this kind of hotkeys are very useful. I have a few keys mapped to reset and preset the Stems Deck controls. All the stuff that NI currently doesn’t address in the Controller Manager but can be achieved ether by creating macro controls or by looping MIDI signals back in to Traktor.
Midi Linked Modifiers. That might be the exact thing I was looking for. I tried to search for something like this, but I had no idea which keywords to use. Now I do.
Just checking; I’m remapping my entire setup, but I have been working on some stability / audio isseus in the mean time. Therefore I have not been very enthousiastic about using middleware alongside traktor. I’d like to hear people’s opinions on this, because you guys seem to trust on bome heavily.
i hope to understand you correct ?
you made bad experiences with middleware for stability / audio issues. that makes you distrustful about using middleware.
now you want to remap you entire MIDI setup ? (bome will not solve your audio problems).
i love miditranslator for the endless possibilities to work with MIDI by using variables, timers, delays…
i think there is nothing with MIDI you cant do with the app. but it is not quite easy to understand how to use the best features
like rules and variables. if your MIDI setup is very large or complicated, miditranslator can save a lot of time for you, or makes really crazy technics possible. miditranslator is not really expensive but i need a lot time to work with it like i do now.
for simple MIDI tasks you can use free software (MIDI Patchbay, TransMIDIfier, MIDI Pipe)
for example: routing a MIDI-output command back to MIDI-input command to use it as Modifier.
I can give you a detailed answer after a few questions:
What is your Reason to remap your Setup ?
Which Controllers do you want to use ?
Which features of Traktor do you want to use ?
Should one mapping react of some others ?
Do you use NHL mappings as well ?
Do you want use some special midi behaviour features Traktor-Editor cant realize for you ? (tab, double tab & hold, midi clock)
thanks for the response.
I think I’ve got a handle on the problems: Audio issues were resolved by removing me Reloop contour and it’s ASIO driver. Traktor crashes seem to be resolved after upgrading to 2.10.1 (been testdriving for several hours, no problesm so far)
I ran into a problem of too little Midi channels (I don’t want controllers to use the same channels) and too little modifier states when I tried to map Hot cues to the Traktor Kontrol F1’s Midi Mode. I’ve resolved that by resorting to the user mode. I had to give up white lights, but I freed up another Midi channel, and the User Mode (some kind of NHL i guess) is fairly straight forward.
I’m still interested in the concept of Midi Linked Modifiers, but for now I’m taking a break from mapping / bugfixing, so I’ll just keep watching this thread.