Z1 MK2 Driver error??? Audio interface selection is buggy

treetop sf
treetop sf Member Posts: 10 Newcomer
in Traktor Software & Hardware

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?

Screenshot 2024-11-01 211038.png

Tagged:

Answers

  • treetop sf
    treetop sf Member Posts: 10 Newcomer

    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
    Stevan Traktor Mapping Mod Posts: 1,988 mod
    1. Right-click uninstall all Z1 related devices.
    2. Disconnect Z1 and then reboot.
    3. Reinstall the Z1 driver.
    4. Connect Z1 and test.

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

  • treetop sf
    treetop sf Member Posts: 10 Newcomer

    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
    treetop sf Member Posts: 10 Newcomer

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

    Is anyone else having this problem?

  • MichaelK_NI
    MichaelK_NI Product Team Posts: 95 mod

    @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
    BJQ1972 Member Posts: 14 Member
    edited 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
    treetop sf Member Posts: 10 Newcomer
    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
    Stevan Traktor Mapping Mod Posts: 1,988 mod
    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
    treetop sf Member Posts: 10 Newcomer
    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.

    Screenshot 2024-11-06 091141.jpg

  • treetop sf
    treetop sf Member Posts: 10 Newcomer
    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
    BJQ1972 Member Posts: 14 Member

    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.

Back To Top

Categories