my Vci froze over 50 times last night.
Other problem… generaly, when it freeze, I turn the unit off and on again to restore functionality…but,
I tried not to turn the unit of but disconect the USB cable and when i did this, everything froze (computer and vci)…
Don’t you think i could be an usb problem of my VCI?
Play around. Update everything, cut down system processes, add paging files to increase ram, get better equipment or cables, or maybe it is just the way you are using it. Maybe there is a problem with your usb port, maybe a problem with how your computer threads and responds to commands. Maybe your computer isn’t giving out priority properly to background processes such as midi. I’m pc so I don’t know. Search the forums, google stuff, look up usb problems on macs and fixes for them. I fixed a lot of my freezes by simply changing vistas shell and threading commands, setting a new partition on my hard drive and stripping the OS down to bare essentials. The more crap you have running, the higher your problem is. Even stupid things such as the ability to connect to and monitor internet connections eats up memory. Turn it all off. Anything you do not need.
No one knows because everyone has unique setups. I mean, you for instance are using an incredibly outdated tsi file, so who knows.
This is something that completely slipped my mind. I know that you (kissbanger) prefer the 2.4 mapping, can you at least try the new 3.5.2 mapping and see if you get the same freezes?
Yeah I mean, I don’t know, but I assume the 2.4 was not built for newer versions of traktor. Maybe just copying the programming fresh into your new traktor build will fix the problem. Or maybe you could just download the older version. Technology is wonderful, but not streamlined and rarely without problems.
Did the freezing problem start after you installed the 1.3 firmware? Or is it something that started before or long after the update?
Maybe try re-flashing the firmware. I have not heard of it becoming corrupt but it is possible…
Also, please try the new TSI (3.5.2) just to see if there is not a problem with Traktor running the old TSI. I doubt that this is the problem, but lets just confirm.
I spoke to DJTT about this problem (I speak to them about articles for the main page and brought up this issue), and beyond what is suggested above, they are not to sure what it could be.
ok it got the same problems few weeks ago …
it was happens 2 times …
1 time - after i turn on/off vci and it continue to work for few minutes…and freeze again …turn on/off again and work for few minutes and freeze. i delete vestax in midi-audio utilities application , and i restart 2.4 midimaping, restart traktor and computer , and it was working around 25 minutes .after i turn off/on my vci , and finish my set with out any problem. my set up was TRAKTOR 1.2.6 and 2.4 old layout.
Before i was using TPRO 1.2.6 - 2.4 without any problems , im working every night 2 hours , 12 - 2 prime time in China…
2 time - problem start from the set up beginning , vci was freeze i restart everything computer, traktor , midimapping its starts to work but after it was freeze and i continue my mix from cds, so guys better to have some cds in your dj bag. cd with mix , or few cd with tracks , you can finish you set or just start cd mix and try to find art manager or djs to make dj transition …its really magic i came back home and everything was working perfect … i was playing few hours…so finally i decide to make downgrade from 1.2.6 to 1.2.4 .last 2 weeks guys no any problems!
i have 2 ideas :
first,1.2.6 bug.before i was using 1.2.4 with old 2.4 midi-mapping without any crashes.and all my problems starts after i was start using 1.2.6 TPRO.
second, dj booth with many equipment like 2 light-mixers , 4 radio microphones , 24 channel mixer can produce a lot off electromagnetic waves and high temperature .My coworkers using serato and 2 guys was crashed in the same day …?
try to restart traktor , try different midi-mapping , delete and add vestax in audio-midi utilities applications, change usb cables, plug different usb ports…
Hi Artak,
so i was using last night traktor 1.2.4 and 2.4 mapping and YES !!! no bug during the night… my vci never froze !!!
Only a problem with traktor… an audio drop…
Could you tell me your audio latency in your preference for your traktor?
hello i dont know if this is the same problem. but today some buttons of my vci 100 se freeze. i can push the button but there is no response. for example the left sync button works fine but the right button i push traktor received the info and sync but the green light dont show up. the button stays orange. or the juggle buttons i push and nothing happens. the fx button at the top left works fine but the green light for activated doesn`t show up. i hope you can understand me when i turn the vci 100se off and on the problem is gone. it freezes only a few buttons. that happened today the second time since i use the vci 100 (1 year).
and do you have that extrem problem with the new 3.5.1 tsi file?i dont want to load the new file in traktor and have more problems than before? i have an older tsi file load in traktor but i dont know which one?
where can i see waht tsi file i loaded?
i hope someone can answer all that questions! thank you very much
@Pilmat:
Focusing specifically on Fader FX VCI freezes, what’s the word as far as what DJTTs has been able to make of this? Just to add to the body of info, here’s my setup:
MacBook 2.4 GHz
VCI-100, custom map, incl fader fx type commands
running with APC40
TPro 1.2.6
Ableton Live 8.1.3
Bomes MT
Jack OSX
Latency 5.5ms
The VCI freezes nearly every time (and only when) using fader fx mode.
It still sends commands, everything works in Traktor. Just the LEDs are frozen/unresponsive.
Traktor audio is NOT affected
Ableton is not affected
APC40 is not affected
And it’s driving me crazy. I’ve noticed this since about TPro 1.2.4, I don’t remember VCI freezes before that…
In the controller manager in the drop down box for device mine says VCI-100SE 3.5.2. I think DJTT have kept it pretty standard as far as what they name them so yours should say something along those lines.
This is true; unfortunately, almost none of the past tsi’s have their version number named in the comment section of the mapping. We will make sure to continue to name everything in the future but it may be difficult to distinguish older tsi’s from one another without pin pointing some differences in functionality.