i always connect traktor to a virtual midi device for both IN and OUT - then my midimasher software connects to the other ends of those ports and also my launchpads etc, routing the data.
so i have it connected like this, naming my virtual midi ports as "Traktor to MM" and "MM to Traktor"
Traktor -> "Traktor to MM" -> MidiMasher -> all midi controllers
all midi controllers -> MidiMasher -> "MM to Traktor" -> Traktor
if its not possible to directly connect a loopBE port etc to a midi controller u could always stick midimasher in the middle using a config based on
this one which will just route data between traktor and the launchpad:
Code:
open_midi_device("traktor", "generic", "from traktor port", "to traktor port")
open_midi_device("launchpad", "launchpad", "Launchpad", "Launchpad")
set_device_route("traktor", "launchpad")
set_device_route_status("traktor", true)
set_device_route("launchpad", "traktor")
set_device_route_status("launchpad", true)
not sure how loopbe names its ports - think loopmidi allows u to name them how u want - which is what i last used before going mac...
obviously tho if youre going to the hassle of using virtual midi ports and running something like midimasher u could also do some mapping inside it
this was my first multi page launchpad mapping in midimasher with full 2 deck control, some virtual midifighters plus a mixer page etc - a bit out of date now tho with all the recent traktor functions etc...
Bookmarks