Ingresar:     


Forum: VirtualDJ Technical Support

Tópico: New controller permanently overwrote VDJ settings
I ran into an interesting issue the other day.

I usually use a Pioneer DDJ FLX4 for my gigs and it works very well with VDJ. I recently acquired a new controller Akai AMX, and connected it to Virtual DJ on my MB Pro to give it a try at home for a short time.

The next day I had a gig for which I used my regular controller Pioneer DDJ FLX4, and to my surprise, after starting the set I realized that the crossfader was behaving odd. It took me some time to realize what happened, it turns out that the crossfader curve was now showing 0 instead of my regular setting "smooth".

In retrospect, I understand now what likely happened. The Akai AMX has a knob on the side that allows crossfader curve adjustment. Mine happened to be set at 0 when I plugged it in, and naturally VDJ changed the setting to match that of the controller. And because crossfader curve is a global setting and not a controller specific mapping, the setting carried over to when I plugged in my FLX4. That was unexpected for me as my regular FLX4 doesn't have knobs that adjust any "settings", only performance related controls (i.e. EQ, loop, jog wheels, cue etc).

I'm wondering now how to switch between the two controllers or even connecting a new controller without worrying about overwriting some arbitrary setting that the controller might have. Is there a method in VDJ to do this properly?

If not, I wonder if this behavior could be improved, either by VDJ overwriting permanent settings only temporarily and reverting upon controller disconnect, or if it's going to override a permanent setting then displaying a warning about which settings are about to be modified so that there are no surprises.
 

Mensajes Sun 09 Feb 25 @ 2:56 am
use the oninit mapping for the flx to set the xf curve setting to the desired setting.
 

Thank you for the response, I think the oninit workaround would address the issue when I switch between these two controllers.

But what about when connecting a new controller I'm not yet familiar with? Any way to preserve settings then?
 

DJ JEMME wrote :
Thank you for the response, I think the oninit workaround would address the issue when I switch between these two controllers.

But what about when connecting a new controller I'm not yet familiar with? Any way to preserve settings then?

Sure. you can for instance back up the settings.xml file