ALL VCI-100’s with Traktor Pro (Dj TT official SE mapping)
This Thread is closed and the file has been updated. Please post new bugs here:
ALL VCI-100’s with Traktor Pro (Dj TT official SE mapping)
This Thread is closed and the file has been updated. Please post new bugs here:
Transport Bug
Hi Ean,
First off thanks for all your hard work in getting this working.
I have found a bug with the transport that occurs when 2 decks are playing. If you try scratching with one of the VCI-100 platters (Even just cueing up), it makes the other playing deck’s audio stutter badly - Even though the cross fader isn’t in the middle. It’s like the scratching midi data jitters the audio output.
I’ve made a movie to show you what I mean here:
Thanks for the video- that made it easy. I am afraid thats not a TSI bug but actually your sound card breaking up. You need to:
raise your buffer
load more ram
clean up the hard drive
get your system running at optimum performance
try a different sound card
We are able to scratch just fine here ![]()
I’ve noticed this too. it seems that TPro requires more processing power.
firmware version: 1.2
It simply doesn’t work:
When I press the button, the next one in line lights up (deck a, then deck b, then deck c) but nothing works.
Therefore I have to select the FX-banks with my mouse manually.
Hey Mate,
I’ve raised the buffer to 20ms and it seems to be OK now (as in it doesn’t cause that glitch when you cue one of the platters, BUT the scratching itself still sounds very digital (clipping, modulation, a sort of gating). This happens at all latency and bit rate settings. It was 44100 11ms before. However, when I use vinyl control records (I usually have it at about 5ms - Well I did in T3. Haven’t tested in Pro yet).
As the poster above (Sheph) mentioned, TPro seems much more resource hungry than T3.
As for my Mac…
OSX 10.4.11
I’m rammed to 2GB (Max for my Black Macbook)
HD is cleaned & system optimized (ala Onyx & Disk Warrior)
Sound Card is Native Instruments very own Audio 8 DJ with latest drivers.
Do you think 20ms is high? What latency setting are you guys scratching with?
20ms will be too high, as built-in soundcards normally have around 40ms which makes it impossible to work with it as a controllerist, well, you can get used to it, but it just feels unreal.
Anything below 10ms should be good to work with.
the banks dont select the effects (that was not possible because of bad midi programming from vestax)
you need to push the on buttons to select an effect under the knobs. first push loads the effect, 2nd push turns it on.
all will be explained in the video on wed
Deck copy
hi Ean,
Just to say cheers again for getting this .tsi out so quick.
I’ve noticed in 1.3 that deck copy a-c and b-c doesn’t seem to work when a loop is engaged on the deck you want to copy from.
I haven’t got serial yet so this might be a demo issue and not for full version.
After a quick play around I was wondering do you think it might be useful to use the tiny deck c and fader fx buttons to toggle the fx banks on or off for each deck rather than having to use the mouse to press the 1&2. I’m gonna have a look at it when get home. So maybe 1 button per deck, press once activates bank 1, twice bank 2, three bank 1&2.
Is this possible or do these buttons send the same midi data as the tiny pots?
Cheers,
Stuart
Hello Hedge,
Problem being anything below 20ms = undesirable sound artefacts, modulation and break up.
You should try to unload as many non-needed processes as possible. Have you tried a sample rate of 48 kHz? strangely on some cards it works better than 44,1kHz combined with ASIO-drivers.
Ean is still right, it looks either like a driver issue or one with your configuration (but I’m on Windows) so I can’t give good advices.
Have you checked the NI forums for other users with similiar problems?
can t copy a to c or b to c ?!?!?!? firm 1.3
Hey Ean,
Thanks again for the hard work in providing the TSI. I have noticed this bug/wierd behaviour/firmware issue:
For me in 1.3 mode, Pushing the snap button works kinda weird. Let me explain.
Starting with SNAP on traktor engaged and the SNAP button lit up blue. Pushing SNAP again, the button will go white, but no change on traktor. Pushing SNAP button again will then disengage SNAP on traktor with the button remaining white. Then pushing it again will have no effect on either the button or traktor. Pushing the fourth time will then engage traktor SNAP and turn the button blue.
Is this the way its designed or a bug in 1.3 firmware for that particular button? As I also notice that this unexpected behaviour is repeated in similar ways when I try and assign that button to other toggle functions e.g if i try and assign it to key lock etc.
What to do from here?
Deck Copy fixed
Hi all deck copy A-C and B-C added to Ean’s DJTT Official SE TSI
Works in both 1.2 and 1.3
Not really for this post but I’ve added the 2nd TSI which allows effects unit toggling on the mixer.
Works as follows:
HOLD DECK A OR DECK B ON TOP LEFT LOOP SECTION OF VCI/SE
PRESS SMALL DECK C BUTTON IN TOP RIGHT PERFORMANCE MODE SECTION TO TOGGLE FX UNIT 1.
PRESS SMALL FADER BUTTON TO TOGGLE FX UNIT 2.
I didn’t configure the LED as looking at your screen is, well easier but if anyone wants that added give me a shout.
Cheers,
Stuart
sorry guys, I forgot to add deck copy A/C B/C in that file. It was a long weekend. Yes- there is something weird with SNAP in 1.3. The problem is that we switched snap to a toggle button in 1.3 so its not really compatible with the 1.2 mapping. it basically means you have to hit it twice to engage or disengage.
Just a suggestion. With the looping section, do you believe it would be good when a loop is released or stopped that the loop length returns to the standard 4 count loop. Sometimes after shortening a loop to a micro loop, releasing it then go to drop another loop and its at like 1/32 count because I forgot to lengthen it again, it screws the mix. I’ve just got to used to the T3 looping techniques.
+1
good idea.
Care to Add in Deck C toggle FX 1 & 2 on/off like you did for Deck A & B?
(me being lazy)
Ean,
Have SE edition with 1.3 running and Jog Grips.
Problem:
In the how to video, you mention if you momentarily hold/press the ‘filter’ button say on Deck A, that you can use the Jog Wheels to control main fx wet/dry mix to ‘scratch’ the fx blend. Sounds super cool in your video.
However, when I do it… touching the outside of the jog wheel, affects only the pitch/tempo bend up/down. If I touch in the inside (the metal part) of the jog wheel, THE MUSIC STOPS, but the fx mix wet dry DOES move up/down. This is while juggle/scratch mode is engaged (button lit up). If i turn OFF the juggle/scratch (not lit) here’s what happens. Outside manipulation on the Jog Grips, you get the same pitch bend up/down effect. Touching the metal platter, NOTHING happens.
It feels like this may be an overlapping control issue.
Could you perhaps map the Momentary or FX MODE of the JOG Wheels to the Inside of the platter to that FX Wet/Dry Mix?
Exact same behavior occurs also,when you flip the small fader fx knop full clockwise too.
Is this possibly an issue because I use the Jog Grips?
thanks for hopefully looking into this and providing an explanation.
At first a bigh thanks to eanfor the wonderful template. But now to my problem. It seems to be the same as with blancodisco except that I just have the bug with jog A. If I go into FX mode and turn jog B dry/wet moves and the song on the deck keeps playing. If I do the same on deck A with Jog A the songs stops (like in scratch mode). So seems just to be a small mapping bug.
Now to my humble question. Would it be possible to switch the VCI completly from A/B control to C/D control by pressing the deck C button?
Thanks in advance and for making my so happy on monday! ![]()