Whoever that dude is, hes right - though im pretty sure there is a user fix that i should be able to do to fix this. Wont be long, ill have the 1.2firmware and ill be able to make a proper fix 
Hmm, i’ll probably get on this as i get home since i’ve been looking a way to get the scratching better.
It shouldnt be too hard, capture the scratch off in bomes midi and make it send out another note that hits the play button. Easy fix
And when the track is playing and you hit the jog (accidentally) it hits play → stops the track. 
I think it requires a bit more than that but shouldn’t be too hard.
You make it sound like i am trying to make the jog work like a giant play button.
If you hit the jog accidentally it still sends a Scratch on before it hits the play button, which is only sent on the release of the jog.
Yeah, but I remember correctly scratching doesn’t release the play button = it stays on → scratch off sends note → traktor receives another play button message which is now actually stop if the deck is playing.
Atleast that’s the default, I can’t remember if there’s separate commands in traktor for stop and play. If there is, then it’s easy of course.
My theory is if that doesnt work then make it press the play button twice(both with the same midi time stamp would be preferable), either way i’m sure the answer lies in the play button and release of the jog.
I agree that with play button you can get the start immediate and remove slow start up with traktor. Maybe feedback from traktor is required to make it work in every situtation. But I’ll check the options in few hours.
Well you CAN scratch on the VCI as is. It’s the intensity of what you’re doing that will have to be curved. I can scratch all day and pretty much get the sound and feel that I want. Now when it comes to “cutting” (equivalent to hitting the pause/cue 3 button in rhythm) or flashing (repeating a word or phrase on each turntable in rhythm…again something else that can be done with buttons) that’s where the Traktor falls off.
Once you pull the jog wheel back AND forth with any siginificant, rhythmic speed it tough to do because of Traktor’s software. Now just to do a jugga-jugga-jugga or even some more concentrated patterns, I (we) can do those now with the software and the VCI as is. In Traktor’s defense, it takes some practice too. Even though CDJ’s immitate turntables out of the box (now), it took time to get there. People have been mixing on CD since the 80’s. However, the scratching didn’t get in good on CDJ’s until the late 90’s (anyone can correct me if I’m wrong). So, we are @ the front of this new technology. It will get better.
But if you can’t scratch now, keep practicing. Aside from what I described above, I’m happy with what the VCI and Traktor CAN do right now. Once I invest in a web cam, I’ll post some video of me goofing off.
In Traktors defence midi just doest offer enough messages per second to be able to keep up with intense scratching, midi was never made for scratching with its just a byproduct of its open and simple nature. You can kind of think of this like the first turntables, they wernt that crash hot for scratching and stuff either. In time though, especially with high definition midi so close, emulated vinyl will feel very much like vinyl.
So save your pennies people if you really want to scratch. Wait it out for HD midi or products that are coming out from manufactures that say they will upgrade to HD midi when it comes out.
Well, it’s close (midi response time) becasue you can do a respectable amount of scratchery with the VCI/Traktor as is.
I have to ask though (and this is not a quiz, I REALLY don’t know). The response time on programs like Final Scratch and Serato seem to be FLAWLESS by nearly all accounts and personal observation. Are those not midi too or is the whole control record setup different?
As well, I’ve seen a few VCI-300/Serato Itch posts including the one I put at the beginning of this thread and that midi has what looks to be a big improvement on response time. No, not quite perfect but on a scale of 1 to 10, it looks to be a 9+.
Thoughts?
Nope thats not midi, thats something else all together. The vinyl contains a audio signal time code thats used to control the deck, at no stage is this signal turned into midi. This process adds a fair amount of latency that is possible to avoid with the technology we have today.
Thank you for the detail. Now that leaves The VCI-300 & Serato Itch. Does that mean Serato has a lead on how to make the software more scratch & (manual) juggle friendly?
The million dollar question will be answered in Eans review of the VCI-300. I haven’t had any hands on experience so its hard to answer that.
i’m just wondering if itch is going to be as user customizable as traktor. i mean the whole reason i went with a midi controller over the time-code setup is the control / creative reworking i could do.
that said, i doubt it’s going to have a noticeable lack of a latency over traktor.
sill, i’m real interested to see what ean does with the vci-300 when he gets his hands on it…
I don’t know if it’s exactly a latency issue but more of a midi command issue. Look @ the video @ the beginning of this post. Not to mention (as also detailed in a post on the previous page), it’s not the VCI, it’s the Traktor software. They (Native Instruments) are about 92% there but there are a few things some believe can be adjusted to make Traktor respond like Serato Itch or more turntable-like. Reworking on midi/VCI is surperior in our software and hardware. If that’s your goal, you made the right move in my opinion.