Elephant's Mapping

Sign in to download
Upload an edit of this mapping

Description and Instructions

RUDI-J’s “ELEPHANT” TSI

A cross-linked TSI for the VCI-400SE, MASCHINE (MK1) and Behringer’s BCR 2000

This mapping is making use of virtual Midi ports and MIDIOX as middleware allowing the involved TRAKTOR devices to communicate to each other.

The underlying mapping design concept is introduced as “Midi Linked Modifiers” (MLM)
(see video and documentation)

Version 2.0,    January 2014

Main Features:

·        Enhanced EQ control with kill functionality and EQ blend support

·        Isolated FX, fine adjustable by enhanced EQ

·        Sample deck control on VCI and MASCHINE; Loop sampler (VCI)

·        Manual FX knob/button control on VCI, MASCHINE and BCR 2000.

·        4 banks with velocity sensitive FX pads; 2 banks for key adjustments (MASCHINE)

·        Unique Jog-FX functionality featuring FX parameter velocity control presets, adjustable thresholds for Jog-FX button control, dry/wet auto-decay presets,
4 multi-unit activation modes

·        GRATIFY section harboring 27 banks with a multitude of effect presets and Superknob functionality (4 modes); ability to duplicate GRATIFY FX selection
to Jog-FX units

·        GRID (Beatslicer FX) with 32 presets

·        Recall of FX to deck assignments for FX1&2 when switching decks on the VCI.

·        SLICER featuring static and dynamic mode á la TRAKTOR DJ

·        HOTCUES, beat juggling scratch on VCI and MASCHINE (2 banks); Loop controls (VCI)

·        4+1  selectable screen layouts; extensive LED feedback

Compatibility:

·        TRAKTOR pro 2.6

·        VCI-400SE with USB firmware 1.0 and any audio firmware

·        MASCHINE MK1, most probably also MK2 (not tested)

·        Windows: XP, 7, most probably also 8 (not tested)

·        Uses LoopBe30, MIDIOX and BC Manager

Content of ZIP:

·        Compound TSI including all 40 TRAKTOR device definitions, as well as individual TSIs for each device

·        Configuration files for MIDIOX, BC Manager and NI Controller Editor

·         Instruction manual (130 pages) covering Installation and usage of mapping as well implementation notes explaining mapping design principles

Problem downloading or other issues? Let us know on the forum.
-
Comments for v2.0.0
dj_estrela over 4 years ago
Indeed, the documentation pdf of this mapping is amazing! very well done. The concept of MLMs is crucial to enable sequential processing, global variables and have any command as a modifier!
Rudi-J over 4 years ago

Thanks :)

Nico about 8 years ago
Amazing!!!!!!!
Earobic about 9 years ago
The biggest and best presentated Mapping i have ever seen ! The "Mona Lisa" of Midimappings !
Francisco Barroso over 9 years ago
Hi Rudi-j, thank you for this awesome mapping. I have been using your former one (with some little modifications) till now, and it is very fine, but this one is superior to any other VCI 400 mapping I tested. The extensive information you give is a nice plus too. I have been using the VCI 400 and a midi fighter twister (with a multiple effects and super knobs configuration too) together, and I am experiencing some interference between both controllers. When any of the encoder switches of the twister are pressed to activate the effects, the play button on traktor is activated and the playing track is stopped. Actioning the rotary encoders produce some minor interferences too. I tried to route and filter the signal from the twister out of the rest of signals trough midi-ox, without success (the commands from the twister enter other midi channels or do not find their way to traktor. May be that this consult should be made on another forum (midi-ox or loopbe) but I could not find any solution. Have you any idea about how to prevent the signals coming from other controllers to interfere elephant’s? Thank you again Rudi-j for your great job. Francisco.
Rudi-J over 9 years ago

Hi Francisco, Nice to hear you use and appreciate the elephant mapping. To solve your problem i recommend to try and do the following. 1. double check that all routings in Midi OX are exactly the same as pointed out in the documentation. I assume you use a maschine controller and a bcr 2000. If not the problem may be that your mapping in Midi OX refers to wrong/nonexisting devices. 2. make as well sure in traktor, with the loaded tsi all device mappings refer to the correct in and out ports. ( for shure non of the ports of my mapping should refer to any of the twister ports) 3. i would not route the twister mapping through midiOX. Just add the necessary device file to the list of elephant device files and make sure the in out port setting of the twister device file(s) is only referring to the twister midi ports. 4. if the error persists, try to mute one device file after the other (by setting the in/out port to "none" in order track down the problematic one that causes the side efect. 5. let me hear your results. PS i am currently on a holiday in Hungary so my response may take longer than expected. Sorry for that.

Francisco Barroso over 9 years ago

Hi Rudi-j, I appreciate your fast replay and help. I am using neither maschine nor the bcr, so I will star by adapting the midi ox mapping and I will give you my feedback as soon as possible. Have nice holidays, Francisco.

Simon about 10 years ago
Hi Rudi-J, absolutely ingenious and impressive mapping! To bad I'm using totally different gear, but at least I can shamelessly steal some of your clever ideas :-) For starters, I'll map some of your gratify effect banks to an AKAI LPD8. Could you please give comment some more on the "recall" feature for the FX-units? As far as I understand it works as follows: If you switch to a certain deck, the effect last selected for this deck as well as all its knob/button states are automatically restored. Correct? If so, how exactly do you save and recall these parameters? I saw that you're somehow using a virtual midi (port 5) for this. Keep up the good work, Simon
Rudi-J about 10 years ago

Hi Simon, thanks for acknowledgements. Yes feel free to incorporate some of the concepts you like into a different environment of controllers (that's why I actually explained so much about the mapping concepts in the documentation). Your assumption about the FX assignment recall functionality is correct. The point about recalling the FX assignments is that there are individual device assignment tables available for each FX deck combination (FX1 A or C; FX2 B or D). These simply sense the deck switch and recall any change in modifiers, so they "know" at all times which decks were were assigned in either position of the switch. Likewise the deck individual GRATIFY devices track a deck switch (as well as switching between GRATIFY and GRID) so that they can recall all settings that were used last time when GRATIFY is re-activated for that deck. The last "Super-knob modes" are maintained and restored in the two devices tables Gratify AC/BD super-knobs. The Elephant mapping actually has it's name from that behavior: It's the Elaphant, not because it so big, but because it remembers a lot (like an Elephant)

© 2023 DJTechTools