button "FX TYPE" and "ROUTE FX" odd sound

Home :: DJ TechTools' VCI-100 FAQ :: button "FX TYPE" and "ROUTE FX" odd soundReply
button "FX TYPE" and "ROUTE FX" odd sound
Posted on: 03.03.2010 by Marianne Steel
Hello DJ Techtools,
I just recieved my brand new VCI-100 SE and got a problem with it.

- Mapping 3.3 TSI
- Firmware 1.3
- Traktor Pro 1.2.4

My Laptop has got a Intel Core2 Duo P8700 and 4GB RAM. The OS is Windows 7 Pro 64bit (up2date) and my soundcard is an external NI Audio 2 DJ (latest driver).
Playing a track in Traktor and pressing the "FX TYPE" button on my VCI-100SE plays an odd sound. Pressing "ROUTE FX" does the same. This sound is very disturbing and with this bug I am not able to use the Midi controller.

I tried to fix it by using a 9V DC adaper with my VCI-100SE but still got the same problem.

Is this a known problem?
Is my controller broken?
Is this Traktor bug?

Any ideas?

Regards,
engel
Shaquana Wesselhoff
23.04.2010
Originally Posted by yosemite
I tried several things suggested here on the community over the weekend to solve this problem but to no avail.

The LoopBe1/Bome way is no option for me because I expect a flawless hardware/software-setup at this price point.

I wonder if there could be a solution to this or if I should prepare myself to get rid of the VCI100-SE as it is totally unusable at the moment?!
Hold tight mate I believe the guys are already working on it, use the workaround for the time being, i believe you may well regret it if u get rid of it
Marianne Steel
11.03.2010
Originally Posted by EanGolden
A few important points.

1) This is not a problem with the VCi-100SE. I finally built a feature that is exposing problems with Traktors midi engine on some computers (PCs).

2) there is a fix. Download the ZIp file in this thread:

http://www.djranking s.com/community /showthread.php?t=11938

and use the "FX glitch Fix" file. This disables the LED command that causes the problems. Everything else works perfectly and you wont have the issue.

Here is the technical answer to what is causing your issue.

Those 2 buttons (route FX and FX TYPE) send out a massive amount of midi-data to the controller. On Windows machines, this can cause a problem and interrupt the audio stream momentarily. This does not appear to be a problem with mac machines.

This problem is due to the way traktor handles midi data. Bomes routes the data differently and is able to handle the data faster fixing the problem on all computers. We may re-release our Mini-Translator which runs the bomes engine for free so everyone can benefit from the faster midi-engine. That will take a few months to test, so in the mean time- just use the file that removes the problematic features.

I am sorry for your frustration with this issue. Its not a problem with our controller but just me stretching the limits of technology a little too far

Hi Ean,
I was sure this is a problem with windows or traktor and not the VCI-100SE. I just wanted to figure out what causes this problem. I believe I will switch to Mac OS X

Thank your for your answer.

Regards,
engel
Marianne Steel
10.03.2010
Originally Posted by yosemite
actually it's more like 30-40
Daniel McCoy
10.03.2010
Originally Posted by engel75
what kind of hardware are you using? 50
Marianne Steel
09.03.2010
I disabled now nearly every HW device that is not needed (bios and windows) and the best latency I can get is about 120
Marianne Steel
09.03.2010
Originally Posted by yosemite
@engel75:

thanks for detailing your test methods.

I just checked with DPC latency checker but even with my "non-optimized" OS (Win7 Ultimate, 64-bit) I get an average of 30-40
Daniel McCoy
09.03.2010
@engel75:

thanks for detailing your test methods.

I just checked with DPC latency checker but even with my "non-optimized" OS (Win7 Ultimate, 64-bit) I get an average of 30-40
Marianne Steel
09.03.2010
Originally Posted by midifidler
Ok have you tried

a)

Using the V2 Tsi

b)

Downgrading the version of traktor you have installed to an older build

This is obviosuly nothing to do with the VCI hardware itself, but something to do with either the latest build of Traktor or the v3 DJTT Tsi
I tried the following things:

1. downloaded and started DPC latency checker (http://www.thesycon.de/deu/latency_check.shtml) - this was showing my system has got about 150 - 200
Daniel McCoy
09.03.2010
Originally Posted by midifidler
Ok have you tried

a)

Using the V2 Tsi

b)

Downgrading the version of traktor you have installed to an older build

This is obviosuly nothing to do with the VCI hardware itself, but something to do with either the latest build of Traktor or the v3 DJTT Tsi
Hi,

Thanks for the help.

No, I did not use any of the pre-V3 .tsis as I already have applied the V3-overlay to the VCI-100 SE.

I also didn't use any older Traktor-builds because the requirement for the V3 3.4 tsi required 1.2.4 (or higher). The 3.4 FX Fix-tsi produces slightly less distortion but still is unusable.
Warner Rotberg
12.05.2010
I was in exactly the same situation a couple months back when I purchased the VCI-SE, Audio 4 and Traktor Pro. I felt really hard done by, with the amount of money I had spent. I took my time searching the net and community s for fixes... What worked for me was:

- Full format of my (laptop) hard drives (I have 2 seperate ones in there).
- Creating a dual boot of Vista, one of each hard drive (one for everyday use, one purely for Traktor)
- I then followed this guide thoroughly http://www.native-instruments.com/kn...dio+processing

The only section I haven't followed is

"Disable HyperThreading (Pentium IV computer with 3GHz or higher ONLY)"

and everything has come up trumps! No glitching on the "FX TYPE" and "ROUTE FX" at all.

FYI, I'm running:

Dell Vostro
Dual core 2.2ghz
3gb RAM
Vista
Latest Traktor and latest DJTT vsi.
Shaquana Wesselhoff
02.05.2010
Pity you are leaving it behind, I actually managed to solve some of the more annoying issues (Shift giving pops and clicks) by raising the latency on my soundcard (Terratec DMX 6Fire USB) to max (8ms) hope you come back at some point mate, though I can completely understand your frustration, I ahd similar feelings about Traktor 3, around the time Traktor Pro first came out, it can really be peeving...

Anyway best of luck mate, hope you find something that works for you.
Vernon Positano
02.05.2010
Unfortunately, compatibility issues are not uncommon. However, they are usually fairly easily resolved, but sometimes need a bit of digging and technical knowledge to do so. That can put it out of reach of average consumers and rightly cause the confusion you are expressing.

I hope you do come back to traktor, and that your issues can get resolved.

There have however been posted fixes for your particular issues that you could use. I know you are unhappy using 'fixes' and rightly expect things to work out of the box, but its not just midi controllers that suffer this, especially in the pc arena.
Daniel McCoy
01.05.2010
@djmoonie:

the unfortunate reality is that I get nothing out of a not so cheap piece of software and hardware.

I gave it another shot with yet another fresh install (from XP Pro 32-bit to Win7 64-bit) with TPro 1.2.6 and the latest .tsi-file (3.5.1).

problems remain the same and the "FIX"-.tsi "softens" the problem but doesn't fix them. totally unusable.

no, it's not my hardware, a faulty install, a crappy soundcard and whatnot and yes, I know that a Mac is sooo much better.

I had enough and solved the problem: trashed the VCI in the bin and cut the TPro CD in a million pieces. I don't have plans wasting my time any longer.

VCI 100 SE + Overlay 2 + Overlay 3 + T Pro + many hours installing and whanot = big $$$ = not working = no fun

I am deeply, deeply disappointed. I guess you've noticed that by now.

Just to clarify one thing: I am not blaming Ean or DJTT as their support is top notch. Just a slight criticism: imho pushing something to the limit doesn't make sense if it doesn't work.
Vernon Positano
25.04.2010
The reality is that to get the most out of digital DJing at present, you need to get your techy hands dirty to some extent. Start poking under the hood at traktor and you'll never look back!
Shaquana Wesselhoff
23.04.2010
Originally Posted by yosemite
I tried several things suggested here on the community over the weekend to solve this problem but to no avail.

The LoopBe1/Bome way is no option for me because I expect a flawless hardware/software-setup at this price point.

I wonder if there could be a solution to this or if I should prepare myself to get rid of the VCI100-SE as it is totally unusable at the moment?!
Hold tight mate I believe the guys are already working on it, use the workaround for the time being, i believe you may well regret it if u get rid of it
Daniel McCoy
14.03.2010
@eangolden:

hi ean,

first of all thanks a lot for the outstanding support. you have to dig real deep to find another site with such a tremendous amount of dedicated support.

the "glitch fix"-.tsi doesn't do the job for me however. it's better (less distortion and less odd sounds) but nowhere near usable.

I have to admit I somewhat regret upgrading to traktor pro as I hate electronics that doesn't work as expected.
Marianne Steel
11.03.2010
Originally Posted by EanGolden
A few important points.

1) This is not a problem with the VCi-100SE. I finally built a feature that is exposing problems with Traktors midi engine on some computers (PCs).

2) there is a fix. Download the ZIp file in this thread:

http://www.djranking s.com/community /showthread.php?t=11938

and use the "FX glitch Fix" file. This disables the LED command that causes the problems. Everything else works perfectly and you wont have the issue.

Here is the technical answer to what is causing your issue.

Those 2 buttons (route FX and FX TYPE) send out a massive amount of midi-data to the controller. On Windows machines, this can cause a problem and interrupt the audio stream momentarily. This does not appear to be a problem with mac machines.

This problem is due to the way traktor handles midi data. Bomes routes the data differently and is able to handle the data faster fixing the problem on all computers. We may re-release our Mini-Translator which runs the bomes engine for free so everyone can benefit from the faster midi-engine. That will take a few months to test, so in the mean time- just use the file that removes the problematic features.

I am sorry for your frustration with this issue. Its not a problem with our controller but just me stretching the limits of technology a little too far

Hi Ean,
I was sure this is a problem with windows or traktor and not the VCI-100SE. I just wanted to figure out what causes this problem. I believe I will switch to Mac OS X

Thank your for your answer.

Regards,
engel

11.03.2010
A few important points.

1) This is not a problem with the VCi-100SE. I finally built a feature that is exposing problems with Traktors midi engine on some computers (PCs).

2) there is a fix. Download the ZIp file in this thread:

http://www.djranking s.com/community /showthread.php?t=11938

and use the "FX glitch Fix" file. This disables the LED command that causes the problems. Everything else works perfectly and you wont have the issue.

Here is the technical answer to what is causing your issue.

Those 2 buttons (route FX and FX TYPE) send out a massive amount of midi-data to the controller. On Windows machines, this can cause a problem and interrupt the audio stream momentarily. This does not appear to be a problem with mac machines.

This problem is due to the way traktor handles midi data. Bomes routes the data differently and is able to handle the data faster fixing the problem on all computers. We may re-release our Mini-Translator which runs the bomes engine for free so everyone can benefit from the faster midi-engine. That will take a few months to test, so in the mean time- just use the file that removes the problematic features.

I am sorry for your frustration with this issue. Its not a problem with our controller but just me stretching the limits of technology a little too far
Marianne Steel
10.03.2010
Originally Posted by yosemite
actually it's more like 30-40
Daniel McCoy
10.03.2010
Originally Posted by engel75
what kind of hardware are you using? 50
Eloy Snopkowski
09.03.2010
same thing happen to me the only temp fix that work like engel75 said is setting out-port to none or putting 60ms + latency -_- not so cool

win vista 32bit
core2 duo 3ghz
4gb of ram
x-fi xtreme gamer soundcard
traktor 1.2.4
firmware 1.2
tsi 3.4
Marianne Steel
09.03.2010
I disabled now nearly every HW device that is not needed (bios and windows) and the best latency I can get is about 120
Marianne Steel
09.03.2010
Originally Posted by yosemite
@engel75:

thanks for detailing your test methods.

I just checked with DPC latency checker but even with my "non-optimized" OS (Win7 Ultimate, 64-bit) I get an average of 30-40
Daniel McCoy
09.03.2010
@engel75:

thanks for detailing your test methods.

I just checked with DPC latency checker but even with my "non-optimized" OS (Win7 Ultimate, 64-bit) I get an average of 30-40
Marianne Steel
09.03.2010
Originally Posted by midifidler
Ok have you tried

a)

Using the V2 Tsi

b)

Downgrading the version of traktor you have installed to an older build

This is obviosuly nothing to do with the VCI hardware itself, but something to do with either the latest build of Traktor or the v3 DJTT Tsi
I tried the following things:

1. downloaded and started DPC latency checker (http://www.thesycon.de/deu/latency_check.shtml) - this was showing my system has got about 150 - 200
Daniel McCoy
09.03.2010
Originally Posted by midifidler
Ok have you tried

a)

Using the V2 Tsi

b)

Downgrading the version of traktor you have installed to an older build

This is obviosuly nothing to do with the VCI hardware itself, but something to do with either the latest build of Traktor or the v3 DJTT Tsi
Hi,

Thanks for the help.

No, I did not use any of the pre-V3 .tsis as I already have applied the V3-overlay to the VCI-100 SE.

I also didn't use any older Traktor-builds because the requirement for the V3 3.4 tsi required 1.2.4 (or higher). The 3.4 FX Fix-tsi produces slightly less distortion but still is unusable.
Adolf Hit
08.03.2010
Ok have you tried

a)

Using the V2 Tsi

b)

Downgrading the version of traktor you have installed to an older build

This is obviosuly nothing to do with the VCI hardware itself, but something to do with either the latest build of Traktor or the v3 DJTT Tsi
Daniel McCoy
08.03.2010
I tried several things suggested here on the community over the weekend to solve this problem but to no avail.

The LoopBe1/Bome way is no option for me because I expect a flawless hardware/software-setup at this price point.

I wonder if there could be a solution to this or if I should prepare myself to get rid of the VCI100-SE as it is totally unusable at the moment?!
Daniel McCoy
05.03.2010
Exactly the same problem here (including the odd sounds when pressing the JUGGLE 1-4 or JUGGLE 5-8 button).

The latest .tsi (3.4) didn't help.

Hardware: Intel D5400XS Skulltrail /w 2 x Xeon E5405, lots of RAM, M-Audio Firewire 410, Windows 7 Ultimate 64-bit, latest drivers

Controller: VCI-100SE (out of the initial first batch)

Obviously computing power is not an issue, latency is low and all other audio apps work flawless.

Just upgraded from Traktor 3 (never had any audio issues) to Traktor Pro (1.24) and I am greatly, deeply disappointed because of the audio glitches. I even made a fresh clean install with all the latest drivers and no other app except Traktro Pro. Same result.

Frankly speaking I don't believe the Loopbe1/Bome-way is a solution to the problem. It might be a workaround but given the fact that I've spent a substantial amount of money I feel this is not acceptable.

I have a hard time to believe that Traktor Pro is not able to handle the MIDI messages. Also I've monitored how much CPU time/resources are used by Traktor Pro but with my hardware setup there's barely any stress for the multiple cores.
Marianne Steel
05.03.2010
Originally Posted by midifidler
Do you still have this problem when using the built in sound card on you laptop?

Yes I tried that -> same problem.
Adolf Hit
04.03.2010
I agree is is not a solution, but it would be interesting to isolate the source of the noise...

Is this problem present on the v2 Tsi?
Rosaura Bergholz
04.03.2010
Originally Posted by midifidler
Do you still have this problem when using the built in sound card on you laptop?
I haven't tried this but will give it a shot toevening .

It's not a real solution overall as I'm certainly not switching from an Audio 8 DJ using ASIO to a Realtek HD chip using WDM drivers.

Ean mentioned during the Saturday video broadcast when introducing the new mapping that audio latency would need to be bumped up to handle the outgoing MIDI messages that drive the Route FX button. Unfortunately I had to push it all the way to 64ms before the glitch went away.

The fact that I can keep latency at 3.5ms with the Loopbe1 in place definitely makes me believe Traktor has a shortcut issue with outbound MIDI; maybe Native Instruments should license loopbe tech for the next service update!

-kb
Adolf Hit
04.03.2010
Do you still have this problem when using the built in sound card on you laptop?
Rosaura Bergholz
04.03.2010
Search the community s for "Loopbe1" to find info on using it in conjunction with Bome's MIDI translator to correct this issue.

I was having the same problem myself on a similar setup and the above worked to correct it (as did droppping my audio latency to 64ms, but that's clearly not a solution).

-kb
Marianne Steel
03.03.2010
setting controller out-port to none solves the problem but that is no real solution
Marianne Steel
03.03.2010
I tried to connect the VCI-100SE to a USB 2.0 HUB (AC powered) but I still get those odd sounds. A silent odd sound is also hearable if I press the JUGGLE1-4 or JUGGLE5-8 button.

<< Back to DJ TechTools' VCI-100 FAQReply

Copyright 2012-2023
DJRANKINGS.ORG n.g.o.
Chuo-ku, Osaka, Japan

Created by Ajaxel CMS

Terms & Privacy