Bespoke Mapping Design Tools, what are people using?
All,
Just returned from being away for 10 months travelling. About a year ago, I was using Traktor Pro 1.2.x with an M-Audio X-session Pro controller. A very simple device, but a good start nonetheless.
I have an aerospace engineering background, so fairly handy with technical problem solving. Looking at the annoyingly small Traktor mapping window (which I hear many people complain of), and understanding the potential for these mapping files to get pretty complicated, I made a little design tool in Microsoft XL. The general idea for the use was as follows:
1. Initial design of the mapping in XL file
2. Implement in traktor, which is easier once you a well organised list of commands
3. Test and de-bug, and interate the design
4. Record/track any changes you make to the mapping in XL
If you open the attached file, then see this explanation:
Split into 3 tabs:
"setting cue points" - dedicated to designing a mapping for setting cue points
"Mixing" - dedicated to designing a mapping for mixing
"sheet 1" - a copy of the Traktor Pro manual available mapping commands
Look at one tab in more detail
“setting cue points”
Top section, aimed at laying out the mapping commands you want to use, any modifiers, etc. Most cells were linked to drop down table of all the available commands.
The next section beneath the table was a schematic of the layout of the controller, and an associated schematic that links to the design table above. So when you make changes to the mapping, it is reflected automatically in your schematic. i.e. the button label changes as you change the design, essentially an “overlay” that updates as you change the design.
The last section was just the lookup values for the drop down table. These are a bit outdated now, as they were built on Traktor Pro 1.2.something...
OK, so getting to the point.
I now recently have VCI-100 SE Arcrade (DJ Techtools version). I am a bit behind the times on this one, but I think it is a cool piece of kit. This is a more complicated controller than my X-session Pro. I have loaded up some of the mapping files for this controller by flashflooder & klaemo (some great work btw). However, I don’t want to have to rely on others for my mapping files, I want to edit and create my own, as the software evolves, and I am sure others are going to be using the VCI-100 for time. Plus the additional complexity of this controller means that keeping a mind-map of what the hell is going on with your mapping file, is even more important. Especially if you are picking up something someone else has designed.
Finally getting to the point of me posting this thread (apologies for the essay....)
Does anyone have a slicker way of designing mapping files, i.e. any useful ideas or bespoke tools?
Are there any working TSI viewers out there for Traktor Pro 2, which could be useful in reverse engineering existing mapping files?
Would people be interested if I developed this further and adapt it to VCI-100 and TP2?
Anyone interested in sharing some ideas on this, and helping to come up with something better?
I am not a computer programmer, but I personally think it would be worth putting some of my own personal time in getting my understanding of mappings up, and being able to develop something others could use, but anything that could jump start the process, and save me reinventing the wheel would be great.
Bookmarks