Controls Initializing on Traktor Startup

Controls Initializing on Traktor Startup

So, I have the following problem: My midi controller usually has its faders set to 0, I generally do this for travel reasons. Traktor, being the piece of whatever we love it for, has its software-faders set to 127/maximum value on startup. This means, when I look at my physical faders after Traktor has finished starting and think that the track is at volume 0, it’s actually volume 127, which is super annoying when your Traktor layout usually does not have the mixer section showing.

After moving the faders once the issue is resolved.

I remember reading the following line in a mapping update some time ago:

[QUOTE]

  • The Faders of the Mixer initialize automatically when Traktor is started up.[/QUOTE]

From this mapping: https://maps.djtechtools.com/mappings/1336

Is there a way to “force” Traktor to get every Midi value on every controller in startup, so the software matches the hardware?

Do any of you guys have an Idea on how to do that? Thank you so much in advance!

Not true with MIDI mapping - that is known behavior of HID (native mapping of NI controllers only).

It could be done with some MIDI routing trickery but since you would be using “ALL PORT” setting your traktor settings might break. I’d not recommend doing this.

This is the biggest non-problem I’ve ever heard. :confused:

It could be for people who are coming from the native map experience. I already tried to create a MIDI mapping that does it automatically (just like HID) but Traktor didn’t like that as I could break TraktorSettings.tsi file. (resulting in crashes and latency issues)

Sure, I’m totally overreacting on this. It’s just a problem i thought would be easily fixed with like some setting I don’t know.

I am mapping two Novation Controllers, a old Launchpad and the Launch Control XL. Am I missing something?

Is there like a guide on using your ALL PORTS method? Sound quite interesting..

Thanks to both of you