Bespoke Mapping Design Tools, what are people using?
Home :: Post and find Controller Mappings :: Bespoke Mapping Design Tools, what are people using?Reply
Bespoke Mapping Design Tools, what are people using? Posted on: 28.03.2012 by Wally Aduna 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 | |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Wally Aduna 28.03.2012 | 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 |
Tawna Ulmen 28.03.2012 | Yep theres only one Newport. I believe everyone in the country has had a evening in TJ's at some point in their lives. Shame its gone now |
Wally Aduna 28.03.2012 | Sweet, Thanks bro. Newport? I'm Just across the bridge in Bristol. TJ's I remember rocking out there a few times. Lol |
Tawna Ulmen 28.03.2012 | Check this thread out http://community .djranking s.com/showthread.php?t=32001 zestoi created an app called midimapper. he da man, you should take a look. |
<< Back to Post and find Controller MappingsReply