Ok guys i have no clue what the hell is wrong with my VCI!!! It freezes on me all the damn time. I have talkied to ol BentoSan and he says adjust it. I did…ever which way I can. I dont think its a sensitivity thing. it made noise when it moves. I followed the link to take care of that and it no longer makes any sound but it still freezes.
If i touch the plater it freezes. when I touch any of the controls it freezes, I’ll adjust the sensitvity and that works sometimes for a bit and then its back to doing the same thing. I have been on that thing for the past 8 hours trying everything.
I thought that it might be my computer so I hooked it up to my boys comp and it did the samething. Changed usb ports and still the same.
is it my sensor…WHAT THE HELL!!! I have no fkn clue here people.
Im runnin TPRO VCIse latest TSI from MIDIMAP page
PLEASE if you know somebody that this is going on with and has fixed it let me know how. I cant take it to a gig like this
No sir I hanvt tried that. Could that be a problem?? See I really wish I could understand this midi and codes the way you guys do because this is driving me crazy.
I i’ll give it a go and get back to ya.
Also, I hope no one gets the wrong idea about this but, It seemed like everthing was working great untill I switched to the SE version. Not sure if I did anythig wrong or if I just plain have a faulty piece of dookie on my hands.
Repost:
I have switche off the midi out for the vestax. I adjusted the sensor a bit. It seems to be working for now. I need a good hour or two to make sure though. It seems that when it does work. After a good hor or so playing it starts to mess up. I will repost later for more info.
update: after opening traktor i’m finding none of the lights work. it still controls the fader and the eq but the sync and the quntize no longer works. or it seems like it dont work.
When i cue the head phones it shows on TP that its doing it, but on the vci it dosent do anything the lights are completly inop.
it no longer freezes but now a new problem. we r on the right track tho.
No lights on VCi is due to the fact that you turned out the midi-out in TP,i think.
Basically its sending signals into the software but doesnt get signals, like light on/off. You should still be able to use all functions, just no LED´s/lights.
I thought so.. because whe I turn it off it…well it just acts funny. The quntize??? or what ever…it dont work. The sync…waters off homie!
when I press the buttons on the VCI it shows on the TP that it’s doing something but, it really dont. It stops freezing tho. When I turn it back on, it goes back to freezing…I mean…I can mess around a bit, but if I got a loop set and i’m using some sort of effect,the next thing I touch…BAM…dun
The fimware I’m using is the one i got off the MIDIMAP. The TSI also.
See I want to know how Midifidler knew to turn off the midi out. That means someone somewhere has had the same issue.
I hope it’s an easy fix tho…ew…damn…I think I just jinxed myself.:eek:
There is little point going to that thread, its merely a poll I setup to determine the scale of the issue. If you want the troubleshooting thread, just do a google search for ‘VCI-100 freeze’
However, to save you some hassle.. the bottom line is that if you turn off midi out and it cures the problem, the chances are that nothing else will help.
I have tried everything to cure the problem, from running on different pc’s, using different cables, and using a power adapter. Nothing worked EXCEPT turning off Midi out.
I am convinced its a firmware issue with the VCI-100.
Mine came with the 1.2 firmware, which most units have now as shipped from vestax. This has the same problem as the DJTT firmware 1.3, so its either something in another part of the firmware code, or the usb / midi controller chip.
Either way, re-flashing back is highly unlikely to fix it, I think the issue is lower down.
EAN!!! dude can you calm the waters over here please?
So has Ean or anybody on here that has takin these things apart givin any imput? I mean theres cats on here that have built one of these things from the ground up. What have they to say on this issue?
No one on these boards, and I repeat NO ONE, has sufficient in depth knowledge of the VCI-100 firmware and chipsets to answer your question. Taking a VCI-100 apart and understanding the components is not what we are talking about here.
This is a low level firm/software issue thats a combination of the windows midi stack and how the VCI sends data.
The 1.3 firmware code was created by vestax after a feature request was made by the DJTT team here. They did not program the firmware themselves.
This thread is ending up a repeat of another on the same subject.
Just trust me when I say lots of users have had this issue and tried everything reasonable to fix it.
See my shit worked great untill I did the whole “upgrade” shit! Now I got a piece of crap on my hands. And your telling me no one, not one person on here can do anything about it. With all the talk I see about firmware this and “made my own midi controler” that, not ONE person can give input on this stupid ass bug!!!
WHAT THE FK…YEAH I’M PISSED OFF!!!
Ean!! Moderators!!! Damn, sombody!!! This is your site…YOUR selling these products what do you have to say.
Tomii can you please verify that your problem still occurs when you use the Tsi you were using before you upgraded to 1.3.
The problem you are experiencing seems to be fairly common for users of the VCI on windows XP, however it does not occur on OSX. This problem also occurs for users both 1.2 and 1.3 firmware so rest assured in the fact that upgrading the firmware has not introduced this problem for you.
I understand your frustration with this, but I have to stress the fact this bug is not in any way a fault or responsibility of DJTT.
That being said it seems to be a problem for many users , and does seem to be due to a conflict in the code for either the XP usb midi device driver or the USB code in the VCI (1.1 & 1.2 & 1.3). - I think Vestax needs to seriously address this problem.
Its somewhere around version 3.2 or above that it seems to have started. I think people have said that is when they introduced new plug and play code into traktor, but its been in there ever since.
