No they dont work properly with TPro yet, they work… but not properly
Pitch faders do work - you get 14 bit accuracy with these
Yes Tpro supports 14bit midi. However… The 14 bit jog wheel messages don’t work, while it appears you can assign the jog with a 14 bit message(the midi learn accepts the 14-bit message) in working practice it just doesn’t work correctly.
When NI finally fix this DJTT will put out a VCI-300 mapping… however until then we cant get satisfactory performance from the jog wheels (unless we downscale them to 7 bit messages) to make it worth while.
Bento, I’m working with a VCI-300 for test purposes, and have some interesting results. I don’t want to jump the gun on this, so can you clarify what you mean when you say “the jogs work, but not properly?”
I’ve got a test tsi that has the scratch set to receive BOTH messages as a single relative fader/knob command with a sensitivity of about 30%, and the thing is scratching great. It doesn’t track like Itch, but I can’t tell the difference between this setting with the VCI-300 and my VCI-100. I’m not downgrading the message in Bomes either, so what gives?
I see a million posts about people trying to get this to work and having weird start/stop and drift issues and such, and I’m having trouble believing this is such a simple fix (granted, it still doesn’t sound like 14 bit).
Since the vci-300 xfader curve adjust also does not translate to Traktor, I’ve routed midi through Bomes into Ableton, setting up translators to do the instant cut thing, and it’s spot on.
I am obviously missing an important element of the fuss over the VCI-300. Yes, it is a nice clean layout and the improved resolution of the pitch fader and jogs is a clear benefit (maybe that IS all the fuss?). But from an economical point of view, the soundcard is not well reputed and you do not have enough controls on the deck for FX (well not without serious layering) and I understand that it still needs to be run through a translator.
With all that stacked against it, why does it still get so much attention? I’m not hating at all, I am genuinely curious to why?
I would love to have a serious go with Itch, as it has some features that interest me, but the dedicated controllers available all have too large of a “cons” column versus the “pros”.
Yeah Phil your not wrong. The 300 is missing a lot of what makes the 100 great.
I suppose i just wanna use hi-res jogs with Traktor.
Ive heard the same about the sound card. Also its pretty large in comparison to the 100.
And some of the buttons dont seem to be freely mappable ?
But … like others i just cant get enough info in one place to make me really hunger for it.
Had my hands on a A&H DX a few weeks back. That thing excited me a lot more.
all the buttons are freely mappable, but some of the knobs are controling the internal soundcard and cannot be mapped.
doing LED stuff is not fun because all of the led’s use different midi notes than the buttons they are mapped too, which doesnt make it very fun to midi map
Not to hi-jack the thread (well maybe I did already…), but I would love to hear your thoughts on the DX Karlos. Apart from the jogs, this looks killer (I’ve already got the arcade button mod plotted from thictool’s videos!).
But as far as sorting an “ultimate controller”, nobody is there yet!
You said it man. I think the big fuss IS the hi-res jogwheels. I wish that controller existed. The DX looks great – but man those jogwheels aren’t even touch sensitive. A DX with VCI-300 jogs working with traktor would be a dream machine. Funny i was just talking to a friend about this same topic this morning. I love the VCI, but jumping on some TT 1200’s has such an awesome feel and response, I wish there was a way to replicate that with a controller using Traktor.
I just thought it was laid out quite intuitively. Compared to the VCI where im having to cross my hands to perform certain functions, the DX is laid out much better. Theres so much more you can do with a mapping as well.
I didnt get chance to change the jogs but i think you can map them so you can scratch a bit. Lets face it the VCI 100 jogs are pretty poor for accurate scratching anyway.
The DX is still far from that “ideal controller” thats never gonna happen but its definitely a step in the right direction.
A DX style controller with better jogs would just kill the comp.
Then again a VCI arcade is a killer controller if you wanna do crazy-ass cue jumping. Nothing comes close in that respect.
I’d tend to agree with most of the above posts re: vci-300. I wanted to test one for midi capabilty, and to experiment with the jogs.
There are more physical buttons on the vci-300, and quite a few more mappable knobs on the vci-100: Like Bento said, you lose two knobs on the 300 that cant be mapped. The vci-100 also has it’s 3 banks (stock=effect parameter select) that effectively give you 8 more knobs and 8 more buttons to work with. I feel like with the 300, you’re really just paying extra for the soundcard and build quality, which is phenomenal.
But back to the main topic: Anyone who has a 300, please map the jogs to Traktor EXACTLY as I described above, and try it out. I really want to get some opinions on the feel. Like I said, it seems like a pretty solid stopgap for those using the 300, and I don’t know why on every tsi out there, the jogs are semi functional or broken…
Zac can you post up the tsi you have.
I can give this a go tomorrow if i can get to the club and get the VCI 300 (shouldnt be a problem).
I also agree (no offense to anyone) but every tsi i have tried has been shit. Riddled with Modifiers (i think the most i counted was 7 conditions for some buttons).
If you an post up the tsi to save me some time id love to have lookie and see how it performs.
It’s not a complete tsi, it’s just a couple commands. Karlos, you can load it, drag a track to deck A or B and work the xfader (keep in mind, no sharp cuts without a translator) - should give you enough to assess the feel. Seems that scratch sensitivity settings of between 23 and 30% work best.
I’m trying to figure that out now, scratching and scratching. It’s interesting, it seems to be lying somewhere between the two in terms of tracking, but I also have Traktor set at 5.5ms latency right now, while I’ve experimented with Itch at 2ms. I’ll try bringing Traktor down a bit and see what happens.
EDIT: Yeah, it definitely doesn’t respond like Itch regardless of latency, but at low latencies I can’t tell a difference between this setting with the VCI-300 and the VCI-100. It’s weird - If dual messages in one command are programmed it works as a relative fader/knob at 23-30%, but if only one message is sent, CC28 doesn’t really work right (it’s the faster message of the two), and CC60 will work only at 0-3%.
So just to recap: Dual message in one command relative fader/knob ~25% sensitivity, or just CC60 at ~1%. No translator, sounds pretty much like the VCI-100.
Can’t you export the .tsi file to your desktop and then upload it as an attachement?
Either way, Im curious to see how this works out. I enjoy occasionaly scratching in songs, but carrying 1200’s sucks, and the jogs on the VCI really aren’t meant for this. Like someone said in another thread - a DX type controller thats solid, with tons of buttons, knobs, etc. and with touch sensitive jogs like the VCI-300 would be a perfect controller. For now, i’ll settle for a VCI-300 + a Kontrol X1. I just need some good jogs!!