Have a feature request or suggestion? Post your idea here!

Publication

2 abonnés S’abonner
0
Avatar

Output Level drops when increasing FX2 Dry/Wet knob

My problem is that when I use the FX2 bank of controls, the output levels drop as I increase the dry/wet knob towards wet. When I drop out of the FX either by deactivating the individual effect or by turning the dry knob back down, there is a noticeable increase in output level. The dropout seems to be more abrupt and noticeable than the introduction of the fx. My workaround for the time being is to gradually increase the gain on the deck to which I am applying the FX2, and then backing off on the gain it when I stop or reduce the FX.

This only happens on the FX2 side If it is happening at all on the FX1 side, it is not noticeable to me.

lectric77

Cette publication n’accepte pas de commentaire.

Date Votes

4 commentaires

0
Avatar

T1? or S1?

If it is for the T1, is it with the Pioneer Edition of Traktor, or Pro 2?

And lastly if it is a T1, which effect does this occur with?  For Traktor in chained mode, certain effects use a filter element within the parameters that you can't modify, that will increase with the application of the effect.  This can cause a loss in output level.  In advanced mode you can control this yourself as a parameter of certain effects.

For example; with a delay, in advanced mode you can modify 3 different parameters, Filter, Feedback, and Rate (or time).  Increasing the filter will decrease the output level as you increase the application of the effect.  I can only imagine that this is true also when in chained mode.  Someone please correct me if I am wrong.

 

 

 

geminimech 0 votes
Actions pour les commentaires Permalien
0
Avatar

Sorry, forgot to mention: T1 using TP2. On FX2, I was using Flanger, Beatmasher, and Gator. On FX1, was Delay, Reverb, Filter, but was not activating Filter at all.

I haven't used Advanced Mode enough to know the difference

lectric77 0 votes
Actions pour les commentaires Permalien
0
Avatar

Sounds like a possible issue for Native Instruments as it would likely be the software causing this issue.

Pulse 0 votes
Actions pour les commentaires Permalien