Traktor Pro 4 doesn't remember my selected audio device (also have another issue)

BJ1981

I have Traktor Kontrol S2 MK3 which I am using with Pro 4 and the ASIO driver (most convenient for me).

Each time I open the software, the audio button turns red, and the settings tells me to select an audio device. It always reverts to Traktor Kontrol S2 MK3 (WASAPI (Shared Mode)) but it needs to be on Traktor Kontrol S2 MK3 WDM Audio (WASAPI (Shared Mode)).

I always select that one, but when I go back in for my next session, it's reverted back to the non-WDM one.

The other problem is that each time I open it, I get the pop-up that it can't open, another instance is probably running, so I have to end task in the task manager every time!

Anyone have any solutions for these?

TIA

lord-carlos

I had similar problem with other devices. For me it got solved by connecting the device 10 - 20 seconds before I open traktor.

MonyG

Same issue on Traktor 3... I've been looking for a solution as well with no luck

MrCee

How many interesting sound drivers have you installed since last doing a clean install of your OS? Ever use OBS or other software that could cause a conflict? Uninstalling it doesn't always work,
Chances are there are conflicting files left over, although I'm only able to speculate based on issues I have had previously.

Where did you get your Windows 11 ASIO driver from? Do they match up with the exact drivers listed on Native Instruments? And have you tried something previously only to eventually find the correct drivers? It's usually conflicting files. I'd normally re-install the OS in this case (if using Windows).

BJ1981

https://community.native-instruments.com/discussion/comment/166650#Comment_166650

I did a clean reinstall of windows within the last month. Got the ASIO driver from the NI website, so it is the correct and latest version.

I do have OBS installed, yes, is that possibly the cause? And if so, is there any way to circumvent it? I mean, it's not a major issue, just annoying that opening Traktor Pro involves the two extra steps of ending the task in Task Manager then selecting the correct audio device in settings

MrCee

Again I can only speculate, but normally it will be OBS drivers and anything involved with OBS, should it be gaming? Are they loaded at start up? Do a quick search on the net to see if you can minimize background processes starting up in the first place.

e.g.. "windows 11 disable startup programs"

lord-carlos

The heck is a OBS driver? I doubt OBS has anything to do with it.

The problem with Traktor forgetting / choosing the wrong audio device is a story as old as times.

MrCee

I have experienced many times where a driver that can extend or re-route audio channels has remained within the OS to cause issues not only with latency, but continuing to load first. Rogue Amoeba was one for example on MacOS which needed to be carefully uninstalled by deleting everything at the core to ensure Traktor drivers were clean again. The un-install process for these apps did not actually remove drivers that were being loaded at start-up. Similar to what is starting up with Windows, it's worth looking into in my humble opinion.

MrCee

So disable everything you can in windows during start-up, make the OS as minimal as possible by removing what you can from start-up (not just the start-up folder but anything you deem as extra bloat). Run the CMD services.msc to see what's really going on during start-up. Strip it back till you find the conflicting app.

MrCee

@lord-carlos Could this be as simple as a registry fix?

MrCee

I'd be interested to see what is listed in the registry in these locations:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
and
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

andy_andy

I have the same issue when I try to connect my Z1 controller. With Traktor Pro 3 I didn't have such a problem. And I have the same setup, nothing different, nothing else installed except the traktor upgrade, WITHOUT any audio driver, beacause I had them already installed from TP3. And something elese: If I remember correct my first two or three times when I connected the controller it worked fine, it connected… and then this problem appeared.

MrCee

Just a question: Did anyone here using a Thinkpad install the full suite of Lenovo drivers at any stage?

I wouldn't want them on my OS. The first thing I would do with any laptop that is shipped with OEM Windows and usually additional bloatware is reinstall a clean version of Windows and carefully choose your drivers after that, and not necessarily from the Lenovo website unless required by a chipset.

I don't have these problems on new install of Windows 10 or 11 on laptops by ensuring the correct drivers are installed initially by going through Device Manager direct with manufacturer each component, and never doing an OEM all in one download. Keeping it minimal.

@andy_andy Are you saying you haven't installed the drivers for Z1 shown here » https://www.native-instruments.com/en/support/downloads/drivers-other-files

andy_andy

https://community.native-instruments.com/discussion/comment/169534#Comment_169534

Not now. I installed them from Traktor pro 3, because then you didn't have the option to select which driver you want to be installed and it installed all of them by default. With TP3 I never had the problem of recognizing the driver right away after connecting the controller.