Mapping TSI - Split Files!

[DJStone]

Hi guys,

I've been thinking about this and everyone makes a custom layout for a specific device.

I was wondering if all the nice GURU's here would like to share info to us beginners.
VanGogo has some brilliant mappings.

Question to you Well Educated Midi Masters.

When you to a knob or super fader or whatever nice tsi, Would you be so kind as to export only that part of that tsi in order for other people to use.

In other words - The individual can then select one effect tsi - custom it for his device and use it.

Am I asking the impossible here.

Is there a thread like this??

Let me know what you think.
Thanks

[sarasin]

They will tell you not to be lazy....as I have been told.

LOL

If you have the same device, you can strip the mapping totally, only leaving the bit you want.

Then save this file....Part 1.

Then open your master file (the one you use to play etc), and import the part 1 file.
This will add that bit to your current master file.

Save that as the new master....BOOM!

[padi_04]

There is no splitting tool, the mapper would have to delete every other command on the tsi and then export it.

Studying someone else's map is usually enough to copy and port to your TSI a specific function.

[bartboy]

Essentially your asking mappers to tare out the good parts and post them piece meal. While this is a nice idea in theory there is no practical use for a single command in a TSI.

Your better off going thru the whole thing and figuring out how they did it. You'll learn a lot more about how mapping and modifiers work.

On my APC40 Mapping (yet to be released) I have split the mapping into 3 different mappings/sections to make it easier for me to make changes. If that's what your asking then yes it's possible but it's difficult to keep all the modifiers correct across mappings.

[DJStone]

I understand that.
I'm not saying that a person should strip his tsi.
Surely before you add the tsi you sit and make up a smaller file.

I'm not complaining about doing it myself.
I'm busy with the traktor bible and some vids on mapping.
There are many new members to contrllerism every day.
This could help many achieve more than what they possibly could on their own.

I am busy with the midi fighter at the moment.
I start withe a clean layout - do one effect until I'm happy and save that under a tsi.
When done I will compile a master tsi.

open up the S4 software. things have changed. You can't just jump in and map through it if you don't know midi that well. you'll screw up something.

Anyway, just thought it might offer even the better guys a chance to tweak some of the stuff other people already did.

[sarasin]

Thats why you save a master copy of the file. Your MONEY FILE!

Then you open one and mess with it....only way to learn!

You always have your backup!

[DJStone]

Ok you win, I'm happy.

I do most my work on PC and use mac for DJ so my stuff is save.

[bartboy]

I get where your coming from now. Ok best way is to start from the ground up. Don't try to alter a mapping unless you know the modifiers inside and out, everything else can be fixed if broken. What I like to do is get a blank layout from TraktorBible.com and put down what you want each button to do. Don't worry about how to map it yet just figure out what you want the whole controller to do. If you need multiple Layer/Modes or Chained FX/Group FX all these things just get it down on paper what every button, knob, and fader should do. Then start at the basic transport controls get those working then move on to something more difficult. You'd be amazed how easy it is if you can stay organized. If you want a button to do something you read/saw somewhere but can't figure out how to do it then come here and between all of us we should have some kind of answer. Hope this helps.

[DJStone]

Thanks Bartboy,

Appreciate your answer.

I take it button at a time. Figure it out and then save that mapping.
Makes it easier for me to keep track.

Mostly I find that everyone talks the same language basically but there are the versions of traktor software that makes it more challenging.

Thanks again

[padi_04]

The renaming of some parameters does happen from time to time but they usually follow a logic path, so they are not that hard to track (ie: advanced/chained vs single/group).

I tend to split my mappings into several pages to keep things a bit more organized in the tiny mapping window (normally left/right, mixer section and global parameters). It's easier to scroll through 4 groups of 100 parameters than a list of 400 commands. Also, when you are testing a new idea back up your previous map and do it in a separate page to avoid accidentally modifying something that worked perfectly well (since there is no undo) or have some conflicts with it, you can just disable/delete that particular function. Modifiers are independent from page to page so you should take this into account too.