m32 and Bitwig/DAW Settings

narot23
narot23 Member Posts: 17 Member

Please see attached. When configuring the MIDI OUTPUT sections of the m32, following the guide, the M32 MIDI OUTPUT should be selected in the bottom of the list. Strangely, doing this causes the first error image above. To fix this issue, selecting None does not work. Only by choosing an Arbritrary MIDI Output Port, does the Komplete Kontrol m32 actually function in DAW mode.

Is there any correction for this? I'd rather not use my MIDI OUTPUT port from anotehr device for the Komplete Kontrol m32, I'd rather it stay within it's lane and either have no DAW output to the device, or the correct DAW output to the device.

Why is this jank workaround functioning? What is the correct way of setting this up? The guide's instructions lead to the error message. If I buy an S49 will it have the same issue? Thank you.

Tagged:

Answers

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 8,916 mod

    @narot23 Have you installed the NI Accessibility Helper? One user solved this MIDI output error by uninstalling it. How to Uninstall Native Instruments Software from a Windows Computer

    If that doesn't help, do you have other control surfaces used in Bitwig? What version of Bitwig are you using?

  • narot23
    narot23 Member Posts: 17 Member

    @Jeremy_NI I am using the latest version of Bitwig, 5.0.7 ...

    The other MIDI control surfaces would be, hardware synths using USB MIDI. No issues crop up in Studio One 6, only Bitwig.

    I don't believe I have the Accessibility Helper installed? How do I go about removing it? Thanks.


  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 8,916 mod

    It's easy to check if installed or not. If it's in the available section, it's not, if it's in the installed section, it is,

    If it is installed, then you need to uninstall like this: How to Uninstall Native Instruments Software from a Windows Computer

    Not sure it's the source of the issue anyway, from this thread in KVR, it seems that this error message from Bitwig means something else: "It's an archaic windows error which usually actually means "MIDI port already in use". Check the thread and see if it helps solving the issue: https://www.kvraudio.com/forum/viewtopic.php?t=577541

  • narot23
    narot23 Member Posts: 17 Member

    It's curious, although there appears to be a program running on my system for the NIHardwareAccessibilityHelper.exe

    , it neither displays nor shows as an Installed Application or an Available Application. How do I go about removing the Hardware Accessibility Helper service/application if it's not installed through NI Access? It looks like the executable is installed in C:\Program Files\Common Files\Native Instruments\Hardware by something, runs on system start as an executable, etc.

    I'm going to go ahead and disable it on System Startup, rename it so something else so that another service doesn't fire it up, and give things a shot. Are those kinds of Accessibility Features even an option now? Nevertheless, that should in description solve the issue.



  • narot23
    narot23 Member Posts: 17 Member

    @Jeremy_NI Well, that did not succeed. It appears the NIAcessibilityHelper.exe file needs to be running for the Komplete Kontrol M32 DAW instance of the controller to display in Bitwig. Now, both in S1 and in Bitwig, it appears that Event Viewer also does not note which device stops the M32 from pairing with the BOME middleware, whatever it may be, to establish and maintain the DAW Port. That was coming and going.

    Clean reinstall, using a utility to shore up any registry misgivings and left behinds, also fruitless. It costs me an arbitrary MIDI OUT port to utilize this controller correctly. Following NI's documentation results in a non-functional controller. Is this at least a documented issue within NI? Or is it something where the documentation/workarounds are only on non-NI websites?

    Make no mistake, I would absolutely be buying an S49 mk3 were this thing working properly as instructed. I've got Komplete Ultimate, the integration with Bitwig is the best I've seen with a DAW thus far, but I'm thinking I am going to be losing more MIDI OUT ports if I invest further in NI Hardware due to the lack of this devices ability to define itself within Windows. What is the published date of the drivers running on the new S49 MK3? The MS WHQL drivers for the new device? Just curious. Thank you.



  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 8,916 mod

    @narot23 Oh, I'm really sorry. I've contacted you by email and will forward your case to our specialists.

  • samhainmitch
    samhainmitch Member Posts: 1 Newcomer

    @Jeremy_NI would you kindly do the same for me as I have the exact same problem as OP. the M32 has given me all sorts of grief.

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 8,916 mod

    @samhainmitch There might be another application "stealing the MIDI ins & outs of the M32, please check this article: I Cannot activate the MIDI Input in the Audio and MIDI Settings (Windows)

Back To Top