You sir are correct and I will adopt that as my start ritual.
You should stress that it needs to be the shift and reset to 0 feature and not just move the physical pitch fader to the center or you’ll have a flood of people complaining that they’re songs start out pitched up or down.
What exactly is this issue? I’ve heard it mentioned in this forum a few times now. I sort of have an idea of what you’re describing in this thread, but not exactly…
Start Traktor, load a track, start the track, then move the pitch slider. How far is the initial movement? A few of us are seeing 8% as the initial pitch range adjustment. If you hold shift and move your pitch slider to center on the controller it zeros it out and doesn’t appear to happen again until you start traktor up again. Even when everything was already at zero from the start.
From Phill’s walk through which you’ve obvioulsy not had to time to read either
SHIFT + JUGGLE 1-4 will toggle Snap on/off
SHIFT + JUGGLE 5-8 will toggle Quantize on/off
my appologies, i have not had the time to read that, let alone try the new mapping
Anyways, in terms of the pitch jump issue, i ran some short tests
Steps:
-Turned on traktor, then VCI, moved the pitch bend, recalibrate after it jumped, problem solved. turned VCI on and off (while traktor was still on), problem did not happen again.
-Turned on VCI before traktor, turned traktor on, moved pitch fader and re calibrated once it jumped, problem solved. turned VCI on and off (while traktor was still on), problem did not happen again.
From this, it seems that the problem is with traktor. So after fixing the problem after I start it, it does not happen again until after I start traktor again. It does not matter (it seems) how many times I turn the VCI on and off while traktor itself is on.
Another note: the pitch always jumps all the way down no matter if u move it slightly up or down on the controller.
I did this test on all 5 pitch settings (8%, 10%, 35%, 50%, and 100%). On all instances they all moved all the way to the lower extrema if i moved the pitch bender down or up.
This test DOES NOT show if there are any problems after a while of use
NOTE: this is with the 3_5_1 mapping AND I FORGOT TO TEST DECKS C AND D! silly me
A new updated zip file has been attached to the initial post in this thread. If you downloaded it before this post, please re-download it since the mapping and walkthrough have both been updated.
Thanks to everyone who provided quick initial feedback on this mapping! All of the issues that were brought up seem to be solved now; however, if anyone finds anything else please let me know.
Ahh, apparently the .tsi has 0% set to the top of the pitch slider (where -8 normally is). So when you start Traktor with the pitch slider at the center position (or 0%), that’s normally +8% and moving the pitch slider will adjust the pitch accordingly. If you start Traktor with the pitch slider at the top position, you’ll see that the pitch slider in Traktor doesn’t jump or anything and will have a range of 0-16%.
I figured this was the way the .tsi worked so I’ve never thought of it as a bug. Ean even mentions this in the mapping tutorial videos.
Excellent to see another update with all the work you guys have been putting into the MF. Ean’s mentioned how hectic things have been, so a big thank you from me for this.
Looking forward to loading this up and playing with it this weekend
I’m sorry this makes no sense to me – am I being dense here? The problem is not where it’s initially set but the behavior when you move it. Even a slight touch on the pitch slider makes the actual pitch jump dramatically. Obviously this is completely unacceptable when the track is playing. I sometimes use an x-session pro with pitch sliders mapped and the mapping I use there does not have the same behavior - a small movement of the pitch slider leads to a small movement of the tempo, just as a real pitch slider would do. If this behavior is intentional for some reason that is fine, but does anyone know of an easy way to map the pitch sliders in the normal way so that they work as actual pitch sliders rather than creating such a huge noticeable jump in tempo when they are touched?
The issue, as far as I know, is being worked on. Some of us are supplying the DJTT team with information on when it is happening and under what circumstances so that they may better find a solution.
I already stated on a previous post on how to initially fix the problem before you start mixing.
And if you did not bother reading that or do not want to do it there is a way to make it easier (assuming you have it set to no more than like 10%, maybe 35%…MAYBE)
Here is what I do. When a track is playing move the pitch bend ad IMMEDIATELY click shift and recalibrate to middle position (with key lock on of course). You can easily do this in literally less than half a second, should go unnnoticed.
I think the behavior is due to where the mapping has 0% set to. Because it’s set to 0-16% rather than -8/+8, when you move the pitch slider from the middle position, you’re actually moving it to the +8 position since +8% would be right in the middle.
Now, whether or not you like this is another topic, I was just trying to explain what exactly was going on.
Personally, it’s extremely rare that I play anything at a negative pitch value, so it doesn’t bother me to work around this. But it would be more intuitive to have it set to -8/+8 so that the pitch fader could be set to the middle position and work like a turntable would.
Ahhh that does make sense to me now… so, yes, I was being dense. Sorry I didn’t mean to cause offense. Yes I was expecting it to be set up like a turntable; I’ll play around in the mapping myself and see if I can set it up a way that is more intuitive for me.