Some months ago I moved to Traktor and I bought a second hand VCI-100 self-arcade with FW 1.4. When I bought it I connected it and checked that the buttons were working then I spent some time getting used to Traktor. Last December I started to work with the VCI and I noticed that some the light of some buttons was stuck. No matter what I do the light of these buttons is always on. I read in the forum that sometimes the USB connection is not powerful enough causing the leds/lights to go a bit funny so I bought a variable switch adaptor for 3-12V and up to 1000mA. The problem is still there, I contacted the seller and he told me that the VCI was working fine with him, there is no reason to distrust him.
Anyway, I was wondering if any of you could help me with that. I just don’t know what the hell is going on…is it getting older? is it the firmware?
I have recorded a video showing the issues, if you realise when I connect the VCI a few buttons flash for 1 millisecond, i.e. 1-4 juggles, dedicated delay for deck A, Fader FX led 1, loop 8 deck A, sample B, etc, those are the buttons that stay on/lighted afterwards, please have a look at the video and any help will be much appreciated.
Thanks but I have tried that many times and still does not work. The mapping es for both win and mac, there is no distinction. I have also tried v3.6.4 for F1.4 and still does not work. Thanks for your help but I think it is not to do with the mapping.
Yes, I know but I am still learning that and I think it will take me some time. I’d like in a future to have my own mapping but as I said I don’t see that happening any soon…
By the way, I have created a generic midi mappin and assigned a simple play/pause action to it, no leds or anything advanced and the problem is still there.
Could anybody tell me what the F1.4W does? What exactly is the firmware?
OK, so you should add output command for your Play button and see what happens. I’m not introduced to this controller or it’s custom firmware but could be that it has some code for LED back light state when Traktor doesn’t take over of the output. Just a thought…
how do the leds act when the vci is connected to your computer BUT traktor is NOT running?
what version of traktor do you use? are your tested mapping made for that version of traktor?
i believe it is a mapping problem. when loading mappings into traktor it happens sometimes that some values are loaded incorrect. did you follow the importing steps?
have you tried to delete every mapping from your controller manager and checked the leds behaviour? try to map some leds on your own and check if they work.
sure the vci has FW 1.4? to confirm, try getting into “disco mode”.
When the VCI is connected to the computer and not to traktor some buttons work and some other don’t but the stuck ones are still on.
I use traktor 2.6.7 and the mapping is from djtechtools “VCI-100SE v4.1 (T2).tsi”, I don’t know if the mapping is made for this traktor version but I would guess it is.
When loading the mapping file I use the “add” button and select “IMPORT TSI” and “import other” in the controller manager. I have noticed that sometimes it loads the file correctly and some others the VCI does funny things.
I don’t know how to map leds, sorry.
I have tried to get into disco mode but the demo video does not have any sound and I only get to flash the bottom buttons by holding the most left two bottom buttons when connecting the VCI. I don’t know what to do next since I can’t listen to the guy. I guess he tries to match the lights on both decks but if this is it I can’t do it because my most left bottom button is stuck and I don’t know how to do it to be honest.
I was told it was FW1.4 but I can’t confirm, if the flashing of the bottom buttons from the beginning of the video is enough then I have the FW1.4.
THe thing is that everytime I connect the VCI the “stuck button” light for a very short period of time, why is that if the VCI hasnot even been recognised by the computer yet?
I just don’t know what to do, thank you all for your advice anyway.
The mapping that you use is from 2011. It was not made for TP 2.6.x. I believe this could cause unexpected behaviours.
The VCI 100 support by DJTT is discontinued. You have to look for a newer mapping (https://maps.djtechtools.com/) or create one on your own.
To import mappings it is important to follow these steps from the manual:
After downloading the latest TSI from the DJTT MAPPING page, open Traktor, click on Preferences (the little gear in the right side of the title bar) and use the big IMPORT but- ton on the bottom of the preferences window (see figure below). Do NOT import the TSI using the small ADD button under Device Setup in Controller Manager as not all the functions and settings necessary for the TSI will be added this way. What Settings to Load MIDI: Everyone EFFECTS: Everyone (please load this file twice if you are using it for the first time to load the FX properly) LAYOUT: Only if you want the layout to change when switching decks from A/B to C/D. To customize your own, modify the layouts in position 1 and 3. ALL OTHER SETTINGS: Import these if you want the Pitch fader to be set to 8%, and for deck copy to work perfectly. Warning this will over-write your Traktor settings! So if you like your settings, then do an export to save them before testing these. Then you can always revert later. Otherwise DON’T import this part of the TSI file.
Next is a very important step!
In Device Setup under Controller Manager, select the VCI-100 from the Device list. You will see that the In Port and Out Port settings are probably defaulted to All Ports, this will cause the TSI to operate incorrectly with the VCI-100. Both Port settings MUST be set to Vestax PC-CONTROLLER.
Note: Do not be concerned with the order of devices in the Device list. The Generic Keyboard will be the “top” item only because it was the first to be created during compil- ation of the TSI. All controllers on this list will be able to command Traktor without con- flict, provided the ports setting are allocated correctly. For example, when adding a Midi Fighter, the ports on it must also be set to the Midi Fighter so as to not conflict with sim-
ilar midi inputs from the VCI-100. However, if the ports are set correctly, each will control the same function independently (e.g., a cue point) without conflict.
It is recommended to close and re-start Traktor TWICE after first importing the TSI. This is due to the complex mappings of the TSI and some minor bugs within Traktor regard- ing the handling of synonymous commands.
Upon starting Traktor with the VCI-100 and your sound card connected to the computer, you should always “initialize” the controls. Usually it will suffice to simply move the line faders, cross fader and pitch/tempo sliders (see note below) so that Traktor knows where they are positioned. The EQ and FX controls are not normally affected, but might be slightly off and are always worth validating. Also, pressing the Slice and Echo but- tons will initialize FX bank 3 and 4 so that their first activation in a song is perfectly seamless.
i can imagine that the fx preset leds (1,2,3,4- on the top left side) stuck due to mapping problems.
but the control fx leds (1,2,3- on the top right side) are hardware set… so another mapping may not solve the problem.
can you make one more short video of your controller. just plug the vci into your computer but DON´T start traktor. dim the lights and press each button. i can compare it to my vci100 fw1.4 and tell the difference.
to assure the fx preset leds are not stuck due to a mapping error, delete all mappings in your controller manager. (BACKUP each file) and import this little tsi.
sorry for starting a new thread everytime.. I´m to fast pressing reply.
the mapping will make the fx preset leds (1,2,3,4) go on, when deck A is playing. and the leds should turn off when pausing/stopping deck A. the only working button in this mapping is the play button for deck A!
I watched your videos and compared the LED behavior of your and mine VCI. I´m pretty sure that your VCI has a hardware error. (And it has nothing to do with mappings you loaded.)
The most important:
Does your VCI send the right midi messages? Or is it firing nonstop the midi notes of the stuck buttons? (Use “midi monitor” or similiar freeware to prove)
If your VCI sends all notes correctly, you can use it without problems.
I think the error is in the LED wiring. The brighter lights of the stuck LEDs indicate that too.
Might be a wrong connected cable or a loose one…
It is easy to open the VCI and here are a lot of videos & tutorials how to open and mod the vci with arcade buttons and/or LEDs. Maybe you can follow the steps the find the error. It´s not to hard opening it and checking the LED wiring. But if you are not used to soldering jobs and electric stuff, I recommend to ask a friend with experience, BEFORE reconnecting anything.
I hope these links will help you repairing your VCI.
