FREAKIN out!!

[djmoonie]

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.

[tomii]

Have you set it back to the original firmware..?? back to factory standards ......I guess. Cant think of anything else it could be.

Sucks tho.......like a fkn dk tease

[djmoonie]

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.

[tomii]

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?

[djmoonie]

Tomii,

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.

[tomii]

Well talk about a waste of 800 bucks!

This fkin blows!!!!!!!

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.

[midifidler]

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.

[tomii]

When I upgraded to 1.3 i was using T3. I didnt have the problems that I am having now. I am using vista.

Also you are correct vastex need to look at this more. but we have people on here that have tried contacting them and we get nothing.

[djmoonie]

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.

I agree about the customer service.. its rubbish

[tomii]

same here