MidiMasher Controllerism Software
Startup (Mac OS X)
- run midimasher
- run traktor
Startup (Windows)
- run loopMIDI (can be set to autostart)
- run midimasher
- run traktor
if using a version of traktor older than 2.1.2 midimasher needs to be run before traktor, else traktor will lock midi ports and midimasher will be unable to use them spewing out errors/warnings on startup
once running you can exit and restart midimasher as often as needed, while creating new configs
Setup
these instructions describe how to setup midimasher for use with traktor though it can be used with any midi software
Exit Traktor if running
-
Setup Virtual Midi Ports
-
Mac OS X and Linux
- ports are automatically created when they have a prefix of V: in the config file like "V:Traktor to MM"
- ports on mac osx can alternatively be created manually using the IAC driver to make them persistent, else they will be removed when you close midimasher
- also midi ports on linux can also be manually created to make them persistent (alsa)
-
Windows only
- download loopMIDI
- add the following ports which will allow communication between midimasher and traktor and also two additional virtual midifighter devices

- skip the MidiFighter ones if you don't need virtual midifighter emulation
- NOTE: The port names are case sensitive and there is no 'space' character after "MidiFighter". ie: "MidiFighter1 Input" and not "MidiFighter 1 Input"
Run Traktor
-
Midi Fighter Setup
- only needed if you want midi fighter emulation from midimasher
- download midi fighter mappings here
- in traktor click File > Controller Manager...

- make sure you use the big import button at the bottom of the controller manager window

- import settings, restart traktor and repeat. this ensures that effects are setup correctly.
- see djtt for more info
MidiMasher/Traktor Setup
- in traktor click File > Controller Manager...

- under Device Setup near the top click on Add... and then Import

- select the traktor.tsi file you find in the midimasher/settings directory
- for In-Port select MM to Traktor

- for Out-Port select Traktor to MM

- if using virtual midifighters select their ports, i.e: MidiFighter1 Input as Out-Port for the first midi fighter mapping (instant grat or deckalized etc) you want to use
- close traktor
Run Midimasher
- run midimasher (.bat on windows, .command on mac or .sh on linux) which will display the config select prompt:
midimasher: build 20111016
#1: default.lua
#2: launchpad.lua
#3: lpd8.lua
#4: lpd8_midifighter_4banks.lua
#5: mpd18_midifighter_4banks.lua
select a config >
- select the config (or create your own first!) and if you see no errors then all is good:
select a config > 2
midi: scan devices...
midi.in.0: LoopBe Internal MIDI
midi.in.1: MM to Traktor
midi.in.2: Traktor to MM
midi.in.3: MidiFighter1 Input
midi.in.4: MidiFighter1 Output
midi.in.5: MidiFighter2 Input
midi.in.6: MidiFighter2 Output
midi.in.7: 6- Launchpad
midi.out.0: Microsoft GS Wavetable Synth
midi.out.1: LoopBe Internal MIDI
midi.out.2: MM to Traktor
midi.out.3: Traktor to MM
midi.out.5: MidiFighter1 Input
midi.out.5: MidiFighter1 Output
midi.out.8: 6- Launchpad
lua: register functions...
lua: run embedded lua...
loading: lib/startup.lua
loading: config/launchpad.lua
traktor: open midi.in.2: Traktor to MM
traktor: open midi.out.2: MM to Traktor
loading: devices/traktor.lua
midifighter1: open midi.in.3: MidiFighter1 Input
midifighter1: open midi.out.5: MidiFighter1 Output
lp: open midi.in.7: Launchpad
lp: open midi.out.8: Launchpad
loading: devices/launchpad.lua
running... <ctrl>-<c> to quit.
Run Traktor
(again)