So, how is scratching with TPro and VCI-100 TT tsi?
I was wondering if DJ TT Tsi works with Traktor Pro and scratching? I mean I have tried many ways to get it to work properly with my VCI-300 and with tsi’s, but when I click on a scratch button (Scratch On) and try to scratch with the jogwheel (CDJ-MODE) & it stutters and stops a bit before the scratch begins. So, how is it functioning with the DJTT tsi? I assume ok..So if ok, what is the trick? It is the last thing I need to finish up properly my new TSI for the VCI-300. I would like it to just be able to hit the Scratch On button and the jog wheels would be scratchable, but not stop playback.
hey, i was actually discussing this with another forum member. we’ve had the same issue, but with the bcd 3000. when scratch is activated, the music stops, and then the jogwheels need to be moved to start scratching. also, every time after a scratch is performed, the scratch mode is deactivated, making it impossible to perform continuous scratches.
edit: for me this function used to work perfectly on traktor 3/LE and also with virtual dj.
Scratching works great in TPro with a VCI-100 and the DJTT tsi, or many of the other great tsi’s posted here. Sounds to me almost like your scratch on commands are mapped to your scratch button, rather than the jog wheels (this goes for the VCI-300 too). Set things so the jogs scratch by default, and you hit the scratch button to escape to a different function.
ok been playing around with the mappings again, still can’t get the scratch to work. your suggestion requires a touch sensitive platter (like the vci-100/300) that enables scratch on to be held while scratching. on a non-touch sensitive jogwheel like my bcd 3000, the scratch on cannot really be toggled, held or directly set to on (it does acknowledge the command but does not perform the desired effect).
in the old traktor when scratch was turned on (via button), the track would continue to play, as if nothing had been pressed, then moving the jogwheel would manipulate the track, as with any form of scratching. my point is that somewhere between the last version of traktor 3 and the current traktor, the behaviour of the scratch on command has become different.
so i guess the question is, if it has changed, what was the reason, and is there a solution out there for non sensitive jog wheels, and also those who don’t want to use the touch-platters for this command?
Ah, I understand now. I am at work right now so I can’t confirm the difference in behavior between T3 and TPro, but is it possible to set the scratch on command to the jog rotation note number? Would that allow the scratch to be triggered by any movement on the jog? I’m not very familiar with the BCD, so these are just shots in the dark.
I use a custom 4 deck tsi. I have a simplified 2 deck version available for download in the mappings section. There’s nothing special about the scratching in my file or ean’s, for example. The functionality is affected by three things: A “scratch on” command (hold), a “scratch” command (direct, rotary, 3h…whatever it is), and the sensitivity and acceleration settings you use in that command. Which tsi are you using with a VCI-100 where the scratching doesn’t work?
The factory mapping for the VCI-100 from vestax is a disaster for TPro. The T3 mapping was a little better. Either way, I have trouble seeing anyone wanting to use those files. Making your own is the way to go, either that or download one you like from another user.
when the jogwheel is assigned to scratch on with interaction mode to
hold: spinning the jogwheel forward locks the track into a ‘forward spin’ (sounds like spinning the wheel forward with cd-dj jog), and countering this will lock it into a ‘backward spin’.
toggle: as you can imagine, spinning the jogwheel in either direction will constantly toggle the scratch (on off on off…), however letting go of the wheel when the scratch turns off (this is by chance of course ) will resume the track from a scratch (had me entertained for a few minutes).
direct: same effect as hold.
the sensitivity and acceleration do not noticeably change these actions.
i’ve tried searching the n.i. forums, and so far, nothing (partly due to the fact that so many posts include the word ‘scratch’). it seems like this would have occured to many, many users who have tried to customise their mappings, but how did this slip under the table?
any other ideas? i’m not exactly desperate for an answer (don’t use scratch), but this one is slowly getting to me.
i completely agree with you. the factory mapping for this controller was barely working (the scratch on button hadn’t even been assigned) as well, so i built my own mapping from the ground up. custom mappings is definately the way forward!
thanks for your inputs so far, i hope this issue gets resolved for everyone soon.
So just to clarify, you have both the BCD 3000 and a VCI-100? I’m a little confused. The beringer unit doesn’t send a note off message, so the scratch gets locked an forward/backward spin. I am guessing maybe you have to hold down a scratch on command on a button, then scratch? The VCI-100 scratches great, (as far as 7 bit midi can do), the only thing holding it back is a firmware upgrade to 14 bit and an implementation in TPro.
I know what you mean though, about it driving you crazy… there’s been things that I don’t really use that I get obsessed with solving, lol! You just want a rig with no buggyness all around.
I just bought a VCI-100 and trying to scratch or even scrub audio and it does not do anything. I noticed the plates on my VCI-100 have plastic stickers on them, so maybe there is a scratch message that is not coming from the platter? I also notice that the jog wheels send 2 midi messages with the 100: forward (B3) and reverse (A#2). How does one get both directions to cdj mode then? Sorry, my first days with the 100 .
Gotcha - the plastic needs to come off. The jogs respond to an electrical current, and your hand needs to touch the metal for them to work. Also, the two notes you get from the edges can be mapped to cd-dj-jog commands, tempo bend, or a combo of the two (one note for forward, one for back). Check out some of the community’s tsi files to see the specifics of how it’s done. Also, just for reference: if key lock is on, the edges of the jogs will send two new note numbers, (this is hard-wired) so if you need to nudge with key lock on, set up duplicate commands and midi learn those note numbers too. It’ll take a little time to set your file up just how you like it, but rest assured the VCI-100 and TPro can handle what you want to do.
) will resume the track from a scratch (had me entertained for a few minutes).