A major bug in Traktor - What is your workaround?

A major bug in Traktor - What is your workaround?

Hi, I’m new to DJTT Forum, so I’m not sure if ‘General Discussion’ is right board to start this Thread.
(If it is not, please let me know.)

I have been using Traktor for about 3 or 4 years and I really like strong midi mapping capability of it as many of you here do.

However, this one bug really frustrates me out and I cannot use its FX at all.

But I see so many of DJs are still using its FX so well.
How do you avoid this problem?

I have received reply from NI for my bug report, they said this bug indeed exist and they are working for it but yet to find solution.

Any comments are welcomed. Thank you!

I use effects but I never noticed that. I usually change the effects before I assign a track to the effects bank.

I wouldnt call this a bug. You are literally pulling one FX unit out of a live signal path, and putting in another one. How do you think Traktor should behave?

Traktor has 4 FX units, each of them can have 3 individual FX. This gives you more than enough separate FX to be able to do transitions smoothly without having to change FX on a live channel.

I have exactly the same and it has been the case for years, it’s one of the most irritating things for me. I can live with all the rest (still being frustrated by bugs or things that weren’t corrected properly or the lack of follow-up), but that issue with fx has an live impact.
I tend to stay clear of changing an activated fx to another activated one on the spot to limit the issue.
If I have to change an fx I do it in rhythm so the small drop out is limited, less felt.

However even putting aside the idea of changing fx on a track on the spot. It happens everytime on specific fx, either when the fx itself is changed or when the unit is activated for a deck. For example the reverb t3 always has that impact, there’s a small drop out or “pop”.
It’s fucking annoying as hell.

and to answer the question:
“But I see so many of DJs are still using its FX so well.
How do you avoid this problem?”
It seems not everybody has it. Don’t ask me why, it may come form the hardware or electrical connections issues, I just don’t know. I stopped sending a ticket about that years ago when the only answer I got was we’re not able to reproduce the issue…

To work around you could map the FX On and FX Unit On to the same button.

Imagine that. A mapping issue being solved by Stewe…

I did not see that coming…

Yes, the best way I could find is the way you do. Choose FX and assign in to the deck before bringing in the track to the master output. However, if I forget to do, I just give up using FX to the channel :confused: Thanks anyway :slight_smile:

Are you using a controller? With direct controller control this just isnt an issue because you can simultaneously turn on an effect and raise the dry/wet to eliminate pops.

to be honest I use two FX, one delay and one reverb and I literally never have this problem. But I do often build up fx using the dry/wet even if very quickly.

Yeah, it is very irritating for me as well :disappointed: As you mentioned the real problem is dropout or pop coming out when activated for a deck (or, assigned for a deck). It makes really no sense that the signal is interrupted just by assigning the FX to the deck when FX is actually turned off.

And the fact that you’ve got reply for NI that they couldn’t reproduce the issue makes me ‘wow’, because this bug is so easy to reproduce. (In my field, a software bug called to be ‘hard to reproduce’ usually takes at least 1 week to be reproduced) Anyway, let’s hope NI could find the solution. Thank you for your comments :slight_smile:

Thank you for your comments ImNoDJ, I’ve written a reply for your first comment, but it is not displayed yet (maybe because I clicked Post before answering the question to prevent a bot or something from writing the reply)

First of all, whether is problem occurs or not highly depends on what FX you are using. Delay and Reverb are ones that do not cause this problem. On the other hand, Filter & Filter 92 are very likely to make this problem.

Go back to the first question, Yes, I’m using iPad Lemur (with template that I make) to control. Of course I have done my mapping as you tell. The problem arises when I give a very small amount of filter. If I just give a large amount of FX the noise may not be recognized, but usually we don’t do so. Imagine as you touch your filter knob and the sound drops out. It is so easy to be recognized.

Originally, i was planning to create XY pad to control FX in Traktor, but I just gave up it because the first subtle movement in the XY pad created the noise for whatever FX chain that has a filter inside (or internally)

Thank you for your reply. But, I’m sorry to say it won’t solve the problem. Noise when switching through FX is removed, but when you turn your FX on, the noise is still there.

Of course if you want to change the sound as soon as FX is turned on, noise won’t be heard.
However, if you want to give a very short amount of FX, you just hear the noise every time.

Imagine you grab filter knob in the DJM900, and once you turn 1deg, you hear the sound dropping out. That’s what this bug is.. Hmm

Thanks Patch for your comments. Sorry, but mapping is not a true solution for the problem.

If this bug is only about the noise being heard only when switching through FX, mapping should solve this. However, this bug also tells you that anytime you assign FX to a deck, there can be sound dropout or noise. That means if you want to use FX for a very small amount, you must hear the noise as well.

Sorry.. I would say this is definitely a bug. Actually, NI also said this is a bug of their product and they are working on this. Traktor is basically a digital mixer before being a DJ software. You don’t see this kind of behavior in any other digital mixer.

If putting in or pulling out an insert FX in the analog domain, this kind of noise is almost unavoidable.
In digital domain, however, things can be different.

Let’s see how input to the audio buffer can be calculated. This is a simple implementation in a pseudo-code.


if (fx_is_not_assigned || fx_is_off) :
input_to_audio_buffer = upfader_output;
else :
input_to_audio_buffer = InsertFx(upfader_output);

I think this is pretty straight forward implementation and it should work well.
If FX is not assigned or FX is turned off, it just pass through the upfader’s output.
If FX is turned on & assigned to the deck, then we can put that into the InsertFx function and use its output as input to the audio buffer.

If there is any delay in calculation (because of interrupt to handle user input or something), it won’t make any problem because what we do affects ‘before’ the buffer. (That is why we have audio buffer; although there is no input to the buffer for a while, it should keep enough data to output and make output signal without problem)

I don’t think NI has implemented Traktor this way, but I don’t know why. Traktor may have multiple signal paths fed into the audio buffer. However, there should be a lock to prevent any undesirable signal is fed. In this case, also, temporarily locking the buffer input won’t make any dropout in sound for the same reason.

In my video, you can see that although FX is off, assigning fx affects the sound, which is output of the buffer. That says, Traktor’s logic to calculate input to the audio buffer is implemented in a wrong way, or the audio buffer is controlled in undesirable way by Traktor.

Well I have had this issue before 2.5 and that mapping worked for me - not sure if you understand. Also, what happens if you lower the Dry/Wet to 0% and close the signal?

What about using Traktors “snapshot” feature to reset all settings when changing fx/fx slots?

Is that the same as the assignment “FX Store Preset”? Because if it is, the only thing it does for me is to make sure that a specific effect is always immediately ON when switching to it (mainly for macro [hold] effects) and it doesn’t solve the artifact problem (for me at least).

The one thing i always do before even starting to mix live in order to avoid most artifacts is to

  • activate all four FX Units on all four decks.
  • activate all four filter knobs.
  • activate Keylock for all four decks.
    and (although it doesn’t do much artifact-wise it’s always good not to forget :slight_smile: )
  • activate the Audio Recorder.

Edit: I almost forgot.

  • Load up the Remix Set that i am going to use and trigger every sample at least once.

Hi,
As of latest 2.11.2 (11), this is still there. On the beginning and breakdowns this is even more disturbing.
changing options / effects / “restore parameters when switching FX” had no influence on this.
Only workaround I know is to change dry=0% before changing any effect!


Annexed a TSI that demos this bug. Pressing the buttons will swap the effect, showing the pronlem.
(please remap any 3x buttons of your controller).

  • button 1: swaps “filter” and “reverb”. wet=100% — GLITCH
  • button 2: swaps “filter” and “reverb”. dry=0% — OK!
  • button 3: reset demo

FX Gligth - Filter and Reverb.tsi (608 KB)

(another thread on the same problem: Small glitch when loading effects )

Thank you djestrela to direct to me here and noticed there are others with the same issue.

From my older post my observations:

I have noticed that when I load certain effects (filters, reverb) in Traktor Pro 2 you can hear a very small glitch/muted audio when you load the effect to an fx unit. I have no idea what produces this.

For example I have mapped to a button commands that it loads the reverb/filter to fx unit 1, sets d/w to 0 and fx unit 1 on in deck X (where music is playing).

If I modify the command to not turn the fx units on while loading only the effect parameters, it does not produce any glitch. But when I turn the fx unit on manually with another button that controls fx unit on/off, it produces the glitch when turning on, even the fx has been loaded earlier.

It might have something to do with the midi messages transmitting between the controller (Maschine) and Traktor. I tried to modify it so that Unit ON (button - hold) is bind to same knob that that FX unit d/w. With this workaround (although not 100% sure) it is not producing the glitch.

I have not been able to create a workaround for this. Also I have noticed that when I have a track playing just switching from group effect mode to single mode creates the glitch too if I have certain effects loaded in the slots.

That bug is present back from the old Traktor 1 version. If you delete midi out messages (LED feedback) for FX’s then it doesn’t glitch.

Hi all,

got a reply from NI support - hopefully this helps:

This is a known issue, which occurs when enabling Traktors FX units, Keylock & Filter for the first time - here is the corresponding Bug entry, for your reference:
• TP-9872 - enabling keylock, FX, and Filter causes LOAD spike and dropout
So this is a general software problem and has nothing to do with the performance or specs of your Macbook.
So at this point of time, we recommend to make sure to enable the FX-1 & FX-2 & Filter on/off buttons before you start your set and make sure that Keylock is already turned on or off depending if you use Keylock.
Our developers are lookoing for a solution and this will hopefully be fixed in a future Traktor release, since it currently affects all users and is obviously set as a “Major bug” and our developers are still looking for a reliable solution to prevent this problem in the future.