synthet1c

Sorry I’m comparing it to having no restrictions, you can do a lot in trakor just not as much as VDJ, when talking about restrictions I also mean new software features will be added, but control of those functions will probably be locked to hardware.

The other main concern is jog wheels which would be as easy as adding another attribute to tell the program the tics per revolution, they have not done this and I don’t expect it to change as it would make competitors hardware which is generally better quality more appealing.

now you need to use midi trace (link above) to find out the midi locations for the controls. when you move a control it will display the raw midi data. for a button it will be two lines like this

9[COLOR=#ff0000]1[/COLOR] 1A 7F 00
8[COLOR=#ff0000]1[/COLOR] 1A 00 00

All you are concerned with is the red number which is the midi channel and the blue numbers which is the midi number

this is the first of the controls defined
<button note="0x35” name=”CRATES” channel=”0” />

if you got the top result you would change it to
<button note="0x1A” name=”CRATES” channel=”1” />

absolute sliders and knobs will generally send out 128 CC messages so that many lines of raw midi data will show in miditrace, but it is the same parts you are concerned with. the green number is incremental and not important for this.

…etc
B[COLOR=#ff0000]4[/COLOR] 3B [COLOR=#339966]17 00[/COLOR]
B[COLOR=#ff0000]4[/COLOR] 3B [COLOR=#339966]18 00[/COLOR]
B[COLOR=#ff0000]4[/COLOR] 3B [COLOR=#339966]19 00[/COLOR]
B[COLOR=#ff0000]4[/COLOR] 3B [COLOR=#339966]1A 00[/COLOR]
B[COLOR=#ff0000]4[/COLOR] 3B [COLOR=#339966]1B 00[/COLOR]
B[COLOR=#ff0000]4[/COLOR] 3B [COLOR=#339966]1C 00[/COLOR]
etc…

[COLOR=#000000]this is the first slider in the definition [/COLOR]
[COLOR=#000000] <slider cc="0x[COLOR=#0000ff]33” name=”HEADPHONE_MIX” channel=”0” />[/COLOR][/COLOR]

If you got the above result you would change it to
[COLOR=#000000] <slider cc="0x[COLOR=#0000ff]3B” name=”HEADPHONE_MIX” channel=”4” />[/COLOR][/COLOR]

Be advised this will only work if the device line and everything in it is correct & there can be no mistakes with XML, every attribute must be opened and closed with “quotation marks” or it wont work. if all the midi messages are the same then that is where the problem lies. You should start with only a few controls then make sure they work before proceeding with the rest of the definition.

If you use notepad++ it can pick up errors and highlight them for you.
http://notepad-plus-plus.org/

https://www.google.com.au/search?q=how+to+find+hardware+id%27s+in+xp&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-GB:official&client=firefox-a

I gave you an in depth answer in one of your other threads, but it looks like Terry must have deleted it by accident…

In short you map jogs with the following for “simple midi”.

param_smaller 50% ? deck left touchwheel –0.05% : deck left touchwheel +0.05%
param_smaller 50% ? deck right touchwheel –0.05% : deck right touchwheel +0.05%

you can change the percentage value to change the sensitivity.

You are better off creating a >>definition file<< though as you will get full resolution of the pitch faders & jogs and get the use of the LED’s. Mapping is also quicker and easier when properly defined as you don’t need to map everything separately.

the filter and any other control can be allocated to a deck with
deck 1 filter
deck 2 volume
deck 3 eq_high
deck 4 eq_low
deck left eq_mid
deck right gain
etc…

The syntax is all in the >>VDJScript wiki<< have a read of it.

You should try to avoid creating multiple threads in future so you don’t lose valuable information tailored to your situation.

your best bet is to download the Terminal mix 4 mapping from the VDJ Forum and make some small changes to make it work with the TM2. You will need VDJ Pro to download mappers.

[the picture is a link]

Reloop Terminal Mix 4 1.0

Author: jpboggis

Aside from that you have two choices…

1. you can create your own definition file so VDJ recognises the device and you can use all of the controls with full resolution and make the LED’s work. http://www.virtualdj.com/wiki/Controller_Definition.html

2. You can use the “simple midi wrapper” to map your controller with basic functionality excluding any non standard midi messages and LED’s. Using this method you will need to allocate a deck focus for every script and map both sides of the controller eg

deck left play_pause
deck 1 cue_stop
deck 2 eq_high
deck right eq_low
deck 3 eq_mid
deck 4 volume

For encoders in “simple midi” you must use the following formula
param_smaller 50% ? action if counter clockwise modifier : action if clockwise modifier

**the modifier can be an integer or percentage value**

So for your example of a touch sensitive jogwheel it’s

param_smaller 50% ? touchwheel –0.05% : touchwheel +0.05%

**change the modifier value to change the sensitivity, and don’t forget to allocate a deck it should operate on in the mapping**

http://www.virtualdj.com/wiki/VDJscript.html

don’t know… you will need to contact support I guess… but try the latency first

I start with a clean slate every time, then map everything exactly the way I want.

Also in regard to your comment about mapping crashing your software, It is impossible so get in there and have a play around.

I started by mapping 32 hot cues to my MPD24 that I could use to jump around cues in blues tracks to tap out hip hop intro’s after seeing equilibrum on youtube doing it a couple of years ago. then figured out how to shift to delete, after that I figured out how to set all the cues throughout the track with one button press and return to the position I pressed it, it all happened instantly using a macro command…. after that I figured out how to change the distance the cues would be set dependant on the size of the loop select, so I could set cues in a track on the fly while it was playing… I took it one step further and wanted to be able to move the cues to put them on the beatgrid, so did that…. then wanted to be able to change between having the cues 1/4, 1/2 or 1 beat apart so with a little maths achieved that so if I have set them the incorrect size I can change it on the fly while the track is playing… On and on I kept going as it is very rewarding to be able to do these sorts of things as they pop into your head.

Now I’m somewhat addicted having mapped and remapped all of my controllers many times over as I discovered new things and though up different ways of utilising mapping. It’s pretty much to the point where I can fluently and coherently write in VDJScript without needing any reference to any verb lists or descriptions and it’s still fun to stretch the imagination and come up with new things. This is the real benefit of digital djing to me and if you don’t use these tools to their potential you may as well stick with CDJ’s and a mixer because that is all factory maps ever try to emulate.