Cross Platform Visual Mapper - TSI Format
Hey All,
I am writing a visual midi mapper for traktor. I am in the early stages, but the problem is, there is one line of binary crap in the tsi file. Can any of you please shed some light on this part of the TSI file.
The app is going to be written in Adobe AIR and I am going to target the xponent, hercules rmx and the vsi-100.
Any help would me MUCH appreciated,
Joe
Wow, cool project. Adobe Air makes it available for PC and Mac!
Would love to see a bcr2000 added to that list.
If you know Flex or more importantly Actionscript, you should be able to develop in AIR. Its basically just a FLash app. The cool thing with AIR is that you have access to the hard drive so you can (drum roll please) WRITE FILES… TSI files if I can figure out that one effing line.
Regards,
J
Let’s hope Karlos or Hedgehog can shed some light on this one. 
Hey man. If your going to write a visual mapper, could perhaps write a text on as well?
The whole click set click thing is fucking annoying.
Being able to write it or have a drop down list setting would be awesome.
Something as simple as xml or even a spreadsheet arrangement with columns from traktor but able to type and copy them. This would make the most complex mappings so much more workable.
Thanks for the tip.
My goal is to have drag and drop as well as pull downs. It would be awesome to see which buttons haven’t been mapped and what commands are unmapped.
This is starting to look more and more awesome every post!
I would def love to see this thing in action!
True that man!
at this point i do not expect theencoding to be anything sophisticated. try having a look with a hex editor for example. that being said, the message NI is sending clear: they do not want people to write these kinds of applications. i think its great that you are still taking a stab at this as this again reminds them that we do not agree with their choice.
however this will probably lead towards a cat and mouse game, so i think the more sustainable thing to do is to launch a big enough protest against this close mindedness NI is displaying here.
just a simple idea..
do you know something about the “one line of binary crap” ?
is the binary code
in every tsi file the same… or different ?
as long as thats every time the same .. it sould not be a prob … ?!
ps.
whats withe the tsi merger ..
you got to files.. both have this binary sequence … the megrer need to handle that sequence too so my idea is now
take two tsi files .. lookt at the binarycode … if there same .. good to know ^^
merge the files an look again in the merged file for the binarycode ..did it chage ? wehn yes how
i think the guy who wrote the merger knows about the binary code.
I had never looked inside the TSI format files until today. I thought the question was interesting, and since I’m a programmer I thought I’d look at it.
What I am seeing is a little bit of trivial xml code at the start and end. The majority of the file is just a bunch of random characters with the sequence “/////” popping up over and over again (probably a separator?).
My guess is that you’re just looking at some form of serialization. The big random string seems to be the only important part of the file. The fact that they need all the other XML crap suggests to me that they’re using some sort of library to serialize it for them.
If I’m right then the good news is deserializing it is easy once you know what function they used. The bad news is that you probably won’t have these functions available to you in Adobe Air. This might be a factor behind why the tsi viewer/merger uses .net.
However, I’d really just have to get my hands on the tsi viewer source code to really know for sure. Other than that your best best is probably to just reverse engineer it bit by bit. Add only one mapping into the TSI and see what comes out. Change it slightly and see the difference.
Rainer G. Haselier wrote a TSI viewer didn’t he?
Or is that a different one? Anyway my understanding was there’s no viewer/merger for any TSI post Traktor 1.2.
Also I think TWD is on the right track.
Why NI continue to block this sort of development and seem to actively fight it is utterly beyond me unless you want to play devils advocate and say they are making it harder so people will only buy pre-mapped/HID hardware.
The least they could do is make the window for the mapper resizable.
Geez,
Joe