VCI Stability poll.

[Jack Bastard]

The problem doesn't affect OSX, it's a windows only thing.

[hurundi]

Some buttons on the VCI change colour when you press them anyway, thats controlled by the controller itself. Some (most) change colour when receiving midi messages from DJ software. Its these that seem to cause the problem.

P.S. Not sure what you mean by edit mode, but all LED feedback is edittable via the midi mapping options in traktor.

with an edit-mode i mean the possibility to change the settings on the controller itself. i just don't recognize why this souldn't be possible with the vci 100.

i loved the BCManager which i used to configure my bcr2000. looks like this:
http://home.hetnet.nl/~f2hmjvandenbe...20encoders.jpg
http://home.hetnet.nl/~f2hmjvandenbe...%20encoder.jpg

sadly i din't find such a software for the vci 100 yet..

finally the fact that my deck c button changes its colour when activated still tells me that it must somehow be possible to define these things on the controller itself. i guess in this case its more a mistake than purose. perhaps it has somethingt to do with the firmware. if so, it would be cool to integrate the following in further firmware updates:
- all buttons lighting up if no midi command received
- all buttoons change colour after pushing them

this way i would have visual feedback of what i'm doing even if midi-out is disabled. surely it won't match if you activate things directly in the software, but i could live with this. its quite easy to quickly check if the leds match the settings in traktor and if not making the changes in traktor.

Its a well known issue, but its difficult where to point the finger. It only affects windows users, but does affect more than just traktor, so my money is on something to do with the vestax firmware/controller chip (not the bit that DJTT modify).

@DJTT
did you ever adress this problem to vestax? i guess you would have a louder voice than a single user.

[J-Reign]

I would think most the DJTT staff uses a mac, so they're probably quietly saying in their heads: "You shoulda bought a mac." haha

[DvlsAdvct]

Actually, I think most of the DJTT people use windows. And, judging by the threads posted here, that rarely comes from anyone who is here regularly.

[hurundi]

hooray! i have some good news concerning the freeze problem. in this thread http://www.djtechtools.com/forum/showthread.php?t=8525 DJPhaidon gave me the advice that using bomes could fix the promlem. i didn't really expect it to work but i gave it a try and guess what, i never had a freeze in traktor again!

this is what i did:
- install bomes http://www.bome.com/midi/translator/
- install LoopBe1 (free virstual midi port software) http://nerds.de/data/setuploopbe1.exe
- select your vci as midi-in in traktor and LoopBe1 as midi-out
- select LoopBe1 as midi-in in bomes und your vci as midi-out
- choose MIDI Thru under options in bomes
- enjoy the led-feedback on a stable system

it's quite simple and all it does is routing the midi-out signals thur loopBe and bomes. i'm not sure if bomes or loopbe prevents the freeze, but my money is on loopbe which seems to be stronger than it looks.

i tested this setup in a 10min stress-test hitting every button i could as fast as possible with extensive use of filters and fader-fx and also for about an hour under normal mixing conditions. i never had a problem. the only way i was able to "crash" the system was while pusing the juggle-on-button realy fast for ~20 times (which makes absoultely no sense ). this results in loopbe automaticly muting itself because it detects problems with the midi-data. so loopbe acts like a gatekeeper for the vci, if it detects problems in the midi-out singnals it just mutes itself and neighter traktor nor the vci is affected in a way like having a freeze or audio dropouts. and i have to repeat, this muting thing never happend while doing normal mixing on the vci.

another realy positive sideeffect of this setup is the response time of the leds on the vci. while using midi-out directly from traktor to the vci, the response time of leds got slower the longer i was mixing (after half an hour of mixing it took the led ~5s to change color after pushing the button). with bomes and loopbe you get immediate led feedback like it should be. so at the end apart from preventing the freeze it works even better than normal.

i'm quite happy now, it's a cool thing getting back the led-feedback

my setup:
- IBM Thinkpad T60 running winXP SP2
- VCI-100SE FW 1.3
- Traptor Pro v1.1

[djmoonie]

Thats really interesting. I've tried midi-ox and loopbe, and neither helped, so it sounds like bomes might be filtering something.. will check this out and report back!

[Karlos Santos]

I would think most the DJTT staff uses a mac, so they're probably quietly saying in their heads: "You shoulda bought a mac." haha

Trust me, this problem pisses everybody off.

[hurundi]

Thats really interesting. I've tried midi-ox and loopbe, and neither helped, so it sounds like bomes might be filtering something.. will check this out and report back!

any news? did it work for you too?

[djtimmmy]

Well so far I have been testing on Windows-7 Pro 23 & 64 bit on the road doing 2 different 4-5 hour sets and so far I have not had one lockup using the midi out..

This looks to may have been resolved in the newer OS...

but I still want to buy a mackbook pro, just cannot afford one yet...

[Abyrne7]

Im going to give it a shot. I'll let you know if it works.

hooray! i have some good news concerning the freeze problem. in this thread http://www.djtechtools.com/forum/showthread.php?t=8525 DJPhaidon gave me the advice that using bomes could fix the promlem. i didn't really expect it to work but i gave it a try and guess what, i never had a freeze in traktor again!

this is what i did:
- install bomes http://www.bome.com/midi/translator/
- install LoopBe1 (free virstual midi port software) http://nerds.de/data/setuploopbe1.exe
- select your vci as midi-in in traktor and LoopBe1 as midi-out
- select LoopBe1 as midi-in in bomes und your vci as midi-out
- choose MIDI Thru under options in bomes
- enjoy the led-feedback on a stable system

it's quite simple and all it does is routing the midi-out signals thur loopBe and bomes. i'm not sure if bomes or loopbe prevents the freeze, but my money is on loopbe which seems to be stronger than it looks.

i tested this setup in a 10min stress-test hitting every button i could as fast as possible with extensive use of filters and fader-fx and also for about an hour under normal mixing conditions. i never had a problem. the only way i was able to "crash" the system was while pusing the juggle-on-button realy fast for ~20 times (which makes absoultely no sense ). this results in loopbe automaticly muting itself because it detects problems with the midi-data. so loopbe acts like a gatekeeper for the vci, if it detects problems in the midi-out singnals it just mutes itself and neighter traktor nor the vci is affected in a way like having a freeze or audio dropouts. and i have to repeat, this muting thing never happend while doing normal mixing on the vci.

another realy positive sideeffect of this setup is the response time of the leds on the vci. while using midi-out directly from traktor to the vci, the response time of leds got slower the longer i was mixing (after half an hour of mixing it took the led ~5s to change color after pushing the button). with bomes and loopbe you get immediate led feedback like it should be. so at the end apart from preventing the freeze it works even better than normal.

i'm quite happy now, it's a cool thing getting back the led-feedback

my setup:
- IBM Thinkpad T60 running winXP SP2
- VCI-100SE FW 1.3
- Traptor Pro v1.1