Z1 MK2 Driver error. Audio interface selection is buggy

treetop sf · November 2

Windows 11
i7
32g ram
Traktor 4.1

Im getting a driver error in device manager.
I tried installing the drivers from NI for the Z1 mk2. (Ni driver 5.7) This did not remedy the error.

In settings, sometimes it tells me to connect audio device even though z1 mk2 asio is selected. If I restart traktor it works ok. wdm exclusive only lets me select 2 outputs instead of 4.

What's going on?

Sunborn · November 16

I have found a solution to the above problem i had. It is rather complicated but it works!
Now Traktor opens with the correct driver and there is no need to re-assigned it every time it starts. 🙂

It seems that there are 2 ASIO's and the one is 32bit, thus it is not working on 64bit systems.

Step 1:

Open Registry Editor and go to this key:

HKEY_CLASSES_ROOT\WOW6432Node\CLSID{B877F272-6DFE-4809-AF95-B114DCA2582E}\InprocServer32

Change the default value,
from:
C:\Program Files\Native Instruments\Traktor Z1 MK2 Driver\x64\NativeInstrumentsTRUsbAudioasio.dll
to:
C:\Program Files\Native Instruments\Traktor Z1 MK2 Driver\x64\NativeInstrumentsTRUsbAudioasio_x64.dll

Step 2:

Open Traktor Settings.tsi with a good text editor (i use Notepad++)

Find and remove the above value (exactly as i write it). It is at the top so it's easy to find it:

AudioDeviceSettingStart;1.01;Traktor Z1 MK2;1;0;44100;512;0;6;12;14;0;1;2;3;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;-1;AudioDeviceSettingEnd;

Save the file.
By the way, i used the above tip to remove every other old and non-existing driver.

Open Traktor. It asks you to switch to Traktor Z1 MK2 (ASIO).

Click NO and tick "do not show this again".

Now, go to Preferences and select the good driver, Traktor Z1 MK2 ASIO Driver (ASIO).

Enjoy!

Note: I opened and close Traktor 10 times and every time was ready to roll, instantly.
No need to re-assign anymore. 😊

treetop sf · November 2

Update…

I uninstalled the Ni driver and now there are no driver errors in windows device manager. The z1 mk2 asio option is now gone from audio devices. I can select wasapi exclusive and set it to 48k. but when i restart traktor, it defaults to wasapi shared and is stuck at 44k.

So every time i open traktor i have to reselect my desired device and set its Hz?

Stevan · November 2

Right-click uninstall all Z1 related devices.
Disconnect Z1 and then reboot.
Reinstall the Z1 driver.
Connect Z1 and test.

Hopefully that helps. Otherwise try a different computer if you have access to.

treetop sf · November 2

Thank you for your reply Stevan,

I had already tried, and got the same driver error on an older win 10 laptop before starting the post...

So now; I have uninstalled all z1 mk2 devices in device manager. Disconnected and rebooted. Reinstalled the Ni drivers. Restarted. Connected the z1 mk2. Started traktor…

This resulted with the original problem of having a driver error, and the glitchy audio device setting.

I guess this is better at the moment because i don't have to reselect the device every time i start traktor. And as long as i don't touch the output routing it wont glitch out. But, such a bummer seeing that driver error…

I will have to test an extended set with the mk2 to see if it runs ok before I'm on a stage. Technical difficulties with an audience suck, lol.

treetop sf · November 4

How can i fix this?
Wait for a new driver release?

Is anyone else having this problem?

MichaelK_NI · November 6

@treetop sf The Subdevice driver is a Windows driver but not the one that you can install using the driver from our website:

https://www.native-instruments.com/fileadmin/drivers/audiohardware/NativeInstrumentsTRUsbAudio_v5.70.0.zip

This is a dedicated ASIO driver which we just tested here again and works on our side.

BJQ1972 · November 6

https://community.native-instruments.com/discussion/comment/188264#Comment_188264

But that subdevice driver doesn't show an error unless the NI ASIO driver is installed? If the ASIO driver is not installed the WASAPI drivers on the Audio setup preferences are different to other NI devices that work with WASAPI exclusive - Buffer size can only be reduced to 320?

treetop sf · November 6

https://community.native-instruments.com/discussion/comment/188272#Comment_188272

"But that subdevice driver doesn't show an error unless the NI ASIO driver is installed?"
- This is true

"If the ASIO driver is not installed the WASAPI drivers on the Audio setup preferences…"
- The wasapi exclusive device in settings has to be reset each time you start traktor.

Stevan · November 6

https://community.native-instruments.com/discussion/comment/188383#Comment_188383

Try to disable the exclusive mode for the Z1 Mk2 device in audio settings. Perhaps the OS has exclusive control of the device and you need to override that in Traktor each time you start the app. Just a thought.

treetop sf · November 6

https://community.native-instruments.com/discussion/comment/188264#Comment_188264

"This is a dedicated ASIO driver which we just tested here again and works on our side."
- Another possible bug, and how to recreate it…

In settings with the asio driver selected and working, click "output routing" tab. now click "external" under mixing mode, and then click back to "internal". now it says, "please connect and select an audio device". If you select the asio driver again, nothing happens. To get it to go back to normal, you have to select a different audio device, and then select the asio one again.

treetop sf · November 6

https://community.native-instruments.com/discussion/comment/188398#Comment_188398

If using wasapi in shared mode, then we are stuck with a non desirable buffer size that cannot be changed.

In my opinion its better to use the Ni's asio driver even though it shows an error in devices and device manager. So far everything seems to work.

BJQ1972 · November 6

The error is nothing to be concerned about. ASIO works fine and, with earlier devices, used to be the default recommended setting. I can't recall ever choosing to use WASAPI if ASIO is available

We bought a bit of kit almost day one - it works, but there's one or two glitches - that's par for the course nowadays.

I'm still going to have a sit down in the next week or so, and see if they can be installed in an order that doesn't cause errors but for now I'm fine with it.

Sunborn · November 9

https://community.native-instruments.com/discussion/comment/188399#Comment_188399

@MichaelK_NI this is definitely a bug and i have it too.

While the device is working when you select the correct driver, this is extremely annoying to see it in my Device Manager and never see it before on an ASIO device. I work with ASIO exclusively for over 20 years and WASAPI is not an option for me, i never used it.

Then, as the OP mentioned above, when you open Traktor it shows 2 ASIO and the "default" is not working (i assume it is the faulty one), and you have to choose the second one!

Here is the "faulty" one, when you open Traktor

Here is the good one (the one that you have to choose every time you open Traktor!)

Please report this to the devs as a bug, or provide more specific details on how we should fix it. Also please explain what it means the "Subdevice" on the 3rd (and non-working) driver and also, what is the purpose of 3 different drivers (one is signed by Microsoft!) for a simple device.

Thank you 🙏

BJQ1972 · November 9

There's definitely something strange going on. I thought I had it set up correctly the other day, but I plugged it into the USB, after launching Traktor, and no WASAPI driver options were available (I had previously installed and uninstalled the ASIO driver, and configured the WASAPI driver).

I closed Traktor down, restarted it and the switch to Z1Mk2 Dialog appeared. I clicked on yes and it selected an ASIO driver that is no longer installed. I manually switched to the WASAPI Exclusive mode, and it switched over to the configuration I had previously set, and it's working OK.

BJQ1972 · November 9

https://community.native-instruments.com/discussion/comment/189626#Comment_189626

If you don't install the ASIO driver there's 2 generic Microsoft drivers - I assume these are the WASAPI drivers, one for shared and one for exclusive. When the NI ASIO driver is installed it conflicts with one of the generic MS drivers - but the ASIO driver still works correctly as far as I can tell. If you try to switch to WASAPI Exclusive when the ASIO driver is installed it will no longer work.

Sunborn · November 16