Traktor (Scratch) Pro - MIDI construction & Issues

Hope I'm posting in the correct thread. Just wondering if Anyone has used the Novation Nocturn with Traktor PRO. I was reading in a previous thread where people seemed to have trouble with Traktor 3 and Novation. Particularly keen to know if the Speed Dial works the way its supposed to work.

Cheers.

 

Faderfox DX2 Traktor Pro Preset now available

Go here:
http://faderfox.de/html/download_page.html

 

Hi Phil and others

I'm having a few issues customising the MIDI settings for my VCM-100 and I hope this is the right thread for asking about them...

1. Fine Pitch Range using a midi-fader:

"Fine Pitch Range: Determines the range of an additional pitch controller available only via MIDI."​

I can't find this anywhere! It doesn't seem to exist as a midi function you can add, nor is there a way of adjusting the range in the Transport Preferences like the manual says there should be. So how can I get the pitch-faders on my VCM-100 to have a resolution smaller than 8%?

2. Pitch bend using midi-buttons:

"Click the left arrow to slightly slow down the track and the right arrow to speed it up. Holding down either Pitch Bend button will continue to speed up or slow down the track until the button is released."​

In T3 I liked to use buttons on my VCM-100 to pitch bend (like touching the record when using vinyl), but I can't for the life of me work out what the right midi-function is for this. Anyone?

Thanks

 

Yeah... Well done Mathias for the DX2 preset .

 

Sorry, one more:

3. Fine Tempo Adjust

"To adjust the tempo in steps, use the “+” and “-“ Buttons under the Pitch Fader.
The sensitivity of the “+” and “-“ Buttons can be adjusted by right-/ ctrl-clicking on the “+” or “-“ Button and selecting one of the sensitivity options."​

I can't find the right midi-function for this to assign to buttons on my controller.

 

[MIDI Modifiers] 100 – Basic Theory

This series of messages will take you from the very beginnings with modifiers all the way through to advanced switching and control. Each of the message titles will be prefixed with lesson(?) number, This one being [MIDI Modifiers] 100 – Basic Theory

As you’ve no doubt discovered one of the changes to MIDI control is the removal of the MIDI pages. On the surface this looks to be a HUGE impediment to being able to do some really fancy control trickery, until you realize the presence of the new MIDI Modifier feature(s). When you first look at it, you are no doubt going to be scratching your head going “What the hell is this and how can I use it?” Think of modifiers as MIDI pages on steroids. They offer much greater flexibility, instead of just 4 pages you have the capability now to do essentially 128 pages. You can just map the controls you need to a modifier or all the controls if you want to emulate the T3 control model.

To start with modifiers looks like a confusing mess, and while its true the learning curve is steep, its fairly short, at least to gain a basic understanding. As already noted MIDI modifiers replaces MIDI Pages. There is no analog for Keyboard Modifiers sorry to say, (not yet anyway) but keyboard keys can be used to trigger MIDI Modifiers.

So what are modifiers? The easiest way to think of them is as a bank of 8 rotary switches. Each rotary switch can be used to select a single value from 0 to 7. The switches have the additional function of reverting automagically to default value of 0 once the button or knob is done sending a message and the modifier is not locked at the new value. There is a way to latch the modifier value, that will be shown in a future lesson.

If you look in preferences | MIDI Mapping there are several new pieces that go to making up the whole MIDI Modifier landscape.

1/ the first piece is to look at is when you click the Add Button, there is a new function group called “modifier”. It contains a sublist with Modifiers #1 – 8 in it. Each of these modifiers is MIDI trigger-able. You can use any control that generates a midi message to trigger the modifier. A common use is a button type control. When triggered the modifier has its value set to what ever is defined in the button options. Possible range of values is 0 –7. Zero is special in that its the default value, if no other value has over-ridden the default value, then zero is set for the modifier. This lists of modifiers lists all the available modifier switches in Traktor Pro. Its not user definable or changeable, it doesn’t need to be. The list of modifiers is fixed at 8. The list of values usable for each modifier is 8 (ranging from 0-7). You may think that is not enough for what you want to do but consider that each modifier has 8 possible values AND you can apply 2 modifiers to each MIDI control then you have tremendous flexibility. During testing I created working presets with over 800 Midi controls and throughout that I used just 4 modifiers and 4 values to do everything I needed. You could get much more complicated than that but trying to remember and understand your logic ladder later on will become impossible. The critical point to take away from this this section; when constructing your preset remember K.I.S.S. Keep It Simple Stupid! Just about every single propellerhead in the world who sees this functionality and grasps its use will first construct presets that are totally magnificent, but so complicated and intricate that they will ultimately fail. We’ll cover the modifier control types and what you can do with them later. For now we’ll simply be using the hold type with a button.

2/ The second piece of the puzzle is the Modifiers section that has been added to the preferences MIDI Mapping page for every MIDI control. There are two pairs of items Modifier/Value, Modifier/Value. Well come back to how they work in second.

3/ The third and final piece is in the Assignments Table list, MOD1 and MOD2. These are the Modifier and Value pairs (noted in piece 2/) defined for a control. Each MIDI control you setup can have from 0 to 2 modifiers defined. Any control that has zero (0) modifiers defined will always work no matter what modifier is pressed. So, say for example you have your controller layout setup so that no matter what modifier is set you always want your deck volume controls to be accessible then you could a) add additional mappings for each state you have or b)not to add any modifier at all and its always accessible.

So to sum up so far:
Modifier Switches are listed as Modifier #1 through Modifier #8 and are also noted as M1, M2 ... M8.
All modifiers have a default value assigned. That value is always zero unless the modifier is triggered.
Mod1 and Mod2 are essentially list filter criteria. Say you have a MIDI controller that when you press a button that produces MIDI message CC1(ch1). You define a Modifier set to value = 1 (and set it to button and hold mode). When you press that button, Traktor first updates the modifier table it keeps in memory, setting the new value for M1 to 1 then it evaluates all the MIDI controls to see which controls are also assigned to message CC1. When it filters down to those controls, it next looks to see if Mod1 or Mod2 have an entry defined for that control. If nothing is set, the control works always, regardless of the modifier and value being set. If Mod1 and or MOD2 has been set then Traktor gets the tag/value pair for the control and looks up the modifier number (M1) in the lookup table to see what values are currently set. If the value in the lookup table and the value from the control (1) match, then whatever action the MIDI control says to do, actually gets done. If the values don’t match the control operation is ignored.

So now that we’re done with the theory lets do something semi-useful. First off save your current Traktor Midi preset by exporting the MIDI section in preferences.
To make it easier to see you may want to delete all your current MIDI controls after you have exported, you can import again after experimenting.

First control entry we’ll create is Modifier#1. Set it as follows: Interaction mode = Hold, Type of controller = Button, Value = 1. Do not set M Numbers or values for either modifier If you did then this modifier will get filtered based on those entries and this demo will not work. Use learn to set a MIDI controller button to this control entry.

Next Control Add a control entry Mixer | Key on, set it as follows: Interaction mode = Toggle, Type of controller = Button, Assignment = focus. Set the first modifier to M1 and value to 1. Use learn to set a second MIDI controller button to this control entry.

Next Control entry Add Mixer | Monitor Cue, set it as follows: Interaction mode = Toggle, Type of controller = Button, Assignment = focus. Set no modifier at all right now.
Use learn to also set the second controller button to this control entry.

Turn Learn off and press button 2, monitor cue will turn on and off. Key on state will remain as it was.
Press and hold Button 1 then press button 2. Both Monitor Cue and Key on will change state. This occurs because the Modifier Button is triggering the modifier so the filter gets applied, that means key on gets evaluated and therefore changes. Also, since no modifier at all is applied to Monitor Cue it always works. Take care later on when making your presets, failing to set Mod 1 or 2 to zero when necessary can result in unexpected behaviors.
Next step lets go back and edit the entry for Monitor cue. Change the modifier entry for MOD1 to be M1=0.
Now press button 2 and you’ll see the same behavior as step 1 above.
Press and hold Button 1 then press button 2. Monitor Cue will not change, But Key on will change state. This occurs because the Modifier button is now triggering the modifier so the filter gets applied. That means 'key on' gets evaluated and changed state since Modifier#1 = 1 now since Monitor Cue was set to on act if M1 = 0 , it doesn't get acted upon.

So that’s the most basic of setups. It should be enough to get you started experimenting. We’ll begin covering more advanced options in next lessons in the coming days. We’ll look at Toggling, Latching, Using multiple Mod values, Jog wheel scaling, control reuse, preset design guidelines and rules among other items.

 

holy crap,

thanks Phil!

 

It works better than older version! I've post the right assignment in the appropriate Thread...

 

M-Audio Xponent

Has anyone got The Xponent working with Traktor Pro please?

 

but this one not working so good
anyone have .tki file for xone 3D ?

 

What is not working so well?

 

My EVO5 doesn't work at all in Traktor Scratch Pro (the midi part), it still works in Traktor Scratch though. In the new Traktor pro the EVO5 is recognised by the software but the software doesn't respond when i push an button on the EVO5 (and the midi symbol also doesn't light up).


I stand corrected, after unplugging all cables and replugging them it seems like the EVO5 is working now. The only thing is that sometimes the software doesnt pick up an button press. I'll try to debug that tomorrow

 

Not happy with Scratch pro. The vestax vci tsi supplied does not work. I have remapped loads tonight, took me ages to get the "one hit loop" to work but got there in the end, FX don't seem to be mapped at all. I still have issue with the scratch function. I just cannot get it to work. Tried all different combinations. The sound quality is poor when scratching, get lots of clicks, tried different latency settings but to no avail. Back to T3.4 till it gets sorted, will post tech support Monday with al my issues. Does anyone have a good VCI 100 map?

Synnerz

 

Hi,

Does anyone know how to make my Vestax VCI-100 jogwheels behave like they did with Traktor 3.x?

What I mean is when in "Vinyl Mode" (on the VCI-100) putting a finger on the metal plate should actually stop the tune playing (as if you're stopping a record) and then allow you to do spinbacks etc...

At the moment winding the jogwheel back in this way just slows the tune down like it's tempo bending it.

I've played around with the MIDI learn and the CD-DJ and both Scratch functions but no joy yet.

This is using the default VCI-100 .tsi file which comes with Traktor Pro.

In fact I can't get it to scratch at all either... where am I going wrong?

Cheers...

 

Well, I've found some answers to my own questions so I thought I might as well post them here...

I found this solution by reading the 1.0.1 Manual Addendum - it looks like it's something that changed between the initial release and the update. There is now a "new Midi Controller Type":

"6.1 New MIDI Controller Type:
By assigning a knob or fader to “Relative Fader/Knob”, you can adjust its range of action and its sensitivity. Furthermore changes on the hardware are interpreted relatively to the position of the fader in the software. For example this can be useful if using it for the Pitch Fader to fine adjust a tempo after having pressed the Sync Button. The range depends on the setting for Rotary Sensitivity. A higher setting results a larger range."​

So by using this for the Tempo|Tempo midi-function you can now have very good control over the sensitivity of your pitch-faders. No idea what the Rotary Acceleration slider does, though!

OK, so Tempo|Tempo Bend does work, but it isn't quite the same as it used to be in T3. In T3, if you held one of these buttons down, the deck would slow down progressively, eventually coming to a stop, and then when you released the button it would quickly wind back up to the right speed. Now, in TPro, when you hold it down it slows just a little and then stays at this new slightly slower speed until you release it. I think I may actually prefer the new functionality as it makes its use less noticeable.

Tempo|Tempo is the one again, this time set to Button Inc and Button Dec - you then have some control over the resolution.

So it seems TPro has streamlined the choices for midi commands so that you use the same command for various different controllers by providing more options to configure those controls.

 

I have no idea how the jogs on the vci-100 works, but if they work kinda like my xp10's, u need to do like this, scratching in Traktor needs to midi messages, first u need to use the command "scratch on" set it up and tap your jog, but dont move it, onee u have that u can map "scratch" to when u move the platter, thats about it

 

In midi mapping: control 'Tempo' , in button options u can change the resolution too.
A bit hard to find especially if a right click works on the other buttons, U'd think it would be the same with the tempo slider.

 

Brilliant, thanks that worked just great!

Now I just need to figure out how to to quickly scroll through tracks using the "Seek Position" function... At the moment, when I let go of the platter the position marker seems to reset back to where it was before I started seeking. What I really want is to quickly move through a track to the point I want on the fly. Does that make sense?

 

midi settings korg zero 4 y traktor scratch pro

Hi Phil, attempt a question, to see if you can help me. do you not come to any file TKS KORG zero 4 in the pro TRAKTOR SCRATCH?. Because I can not find it anywhere in midi settings.
Thank you very much, a greeting

 

No midi map for M-Audio Xponent. Almost all controlers has fully midi map (.tsi file) except Xponent.

Why these treatment with one of the best sellers?



Native Support:

Allen & Heath 1D&2D
Allen & Heath 3D&4D
Behringer BCD3000
Behringer DDM4000
Denon DN-HC4500
Denon DN-S1200
DJTech iMix
DJTech iMix reload
Ecler NUO4
EKS XP Series
Hercules DJConsole MK2
Numark OmniControl
Numark TotalControl
Pioneer CDJ-400
Pioneer MEP7000
Reloop Digital Jockey (Interface)
Vestax VCI-100
Vestax VCM-100