Combining multiple TSI-files
Short question: Is there a way to combine several TSI-files, so that you can actually save different mappings to different files? I made the mistake of thinking Traktor would simply import the files rather than clearing the midi-mappings and ONLY loading the files and now I can use any ONE of my three controllers :-/
A guy at the NI forums posted an instruction for this. I haven’t looked at his pdf, but maybe it helps.
http://www.native-instruments.com/forum/showthread.php?t=78940
Please give feedback if it worked for you.
The makers of the Traktor Bible promise a TSI combining tool shortly.
Hopefully as a web-application, since I’m on OS X 
First test didn’t go too well, perhaps something with the format of the file.
Will report back if I figure it out.
EDIT: User error, typed in a " too much. Seems to work right now, I’d still rather have something of a load-file where I can simply enter the tsi’s I want to use. Time for some complaining at NI 
I emailed Ean on this. I made a simple how-to with the steps needed to merge TSI files. Its a pretty simple task. I can send it over if anyone needs it.
Thats wicked news ! thanks for the heads up 
McRossi.. maybe just post the steps in this thread… or attach a file with the details.
thanks.
Here is the PDF from NI’s forums.
Sorry for the delay. I was a little overloaded at work.
Here are the simple steps to do this.
How to Merge Traktor Pro TSI Midi Mappings
by Mark Rossi
I would like to use my VCI-100 SE with the RemoteSL 25 and Traktor Pro. I have endured the process of mapping the settings I want for the SL25 and am going to use the DJTT settings for the VCI SE. The problem is, if I import the DJTT SE settings, they overwrite my SL25 settings. The problem here is that there is no merge function built in to Traktor.
I have come up with a solution to address the lack of this feature that involves a TextEdit for MACs and Notepad for PCs and a few simple steps.
First build your midi mappings for one device (in my case it will be for the Remote SL25). Make sure there are no other mappings pre-existing before you configure them. You should add a label to the comments section of each mapping that identifies the piece of hardware you are configuring it for. For example I typed in SL25 for all of my SL25 mappings, when you sort on the comments section, it groups them all together and will help to distinguish between controllers when your mappings are finally merged.
After you are satisfied with the mapping, test it to make sure all functions work. Now Export the midi mappings (make sure that midi mapping is the only object with a check in the box.)
Repeat these steps for additional hardware if needed. Each piece of hardware should have its own TSI file. This will make it easier to make changes down the road.
You need to make backup copies of your TSI files. (If you put in hours of editing, it would suck to lose all your work by overwriting the wrong file).
Open both TSI files that you would like to merge using TextEdit for the MAC or Notepad for the PC. In my case it is the file containing the midi mappings for the SL25 and the DJTT SE TSI. Also determine which file will contain the final TSI that you will be importing back into Traktor. In my case it will be the DJTT TSI because it contains additional configurations for the FX and interface. This will be the file we copy into.
Start with the TSI file we will be copying from (this will most likely be the TSI you created earlier, in my case, the SL25.) The TSI files are grouped into sections. The section we must locate starts with…
What you will need to copy will be in between the quote marks “”. Copy all the data between these quote marks (do not copy the quote marks themselves).
Now bring up the destination file (in my case the DJTT TSI.) Find that same section listed in step 6, go to the end of the mappings just before the last quote mark. Put a space after the last entry there (before the quote mark) and past the text you copied in step 7.
Save the file with a new name so you can identify what pieces of hardware are configured within it.
Import into Traktor Pro. Make sure all of your midi mappings have imported. If you sort on the comments section, you will see all of your custom mappings grouped together to make sure nothing is missing.
Good Luck!
Thanks for the walkthough McRossi.
Makes total sense. a basic copy n paste job, but just need to have a watchful eye.
Terrific.
Great info
Thanks a million for posting this. I was wondering what kind of set up you have come up with for the SL. I too am using a VCI and SL (well, will be thanks to you!) and I have the sliders set to control the effects, yet haven’t made up my mind about the functionality of the knobs. Also, the x/y pad is not very sensitive - I have to press down really hard, so I haven’t assigned it to anything specific yet.
I have, though, found the interface between the SL and Traktor very easy to navigate.
Hopeful that we can collaborate in the future!!
Has NI changed anything in the update? Did anyone retry importing different mappings? I’m at work right now, otherwise I’d check it out myself.
As far
as I can tell, the update did not change this. I just (last night and 5 min ago) combined the .tsi’s in the manner described by McRossi and it worked brilliantly well. For those not technologically inclined (like myself) I would like to point out that you just need to name the file .tsi (that is, delete the .txt that OSX automatically assigns it) and then open it using the “all files” option in the Traktor Pro Import window. If you have Traktor Pro Compatible files only enabled, then it will not let you select it.
It is actually fairly easy if you just follow the instructions line by line.
HELP!
i cant get it to merge:
do these instructions also apply for Traktor 2?
the only Controllermapping tsi files of mine look like this:
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
I just want them to merge!!!
Epic necro. Sadly there’s no way of combining tsi files at the moment.
Shouldn’t there be cookies for those who used the search button?
True dat. Or pizza.
This procedure no longer works since NI decided to get rid of human-readable settings files.