[Solved] Could not open MIDI output: There is not enough memory available for this task.

[Ploppz]

Bitwig version: 4.1.2
Connected my NI Komplete Kontrol M32.
I have Komplete Kontrol application installed and running.
I installed DrivenByMoss for bitwig as well.
But Bitwig gives this message consistently:



It doesn't help to unplug and replug the keyboard.
I have 32 GB RAM in my system, of which 15 GB is used.

[Karbon L. Forms]

Nothing to do with memory. It's an archaic windows error which usually actually means "MIDI port already in use".

Normally, only one application at a time can open a port.

You probably have ports open in Komplete Kontrol? You don't need that.

KK speaks directly to the hardware (normal mode), DbM uses the midi input/output ports (MIDI mode) Forget about KK (or maybe use the plugin) if your using DrivenByMoss.

[backtomusic]

If you have this problem without open ports, there may a corrupt config file or something like that.
Basically, that error locks the midi port when the system boots and your f***ed.

Reinstall cant solve the problem, because NI:s install and deinstall does not overwrite or remove the file that is corrupt.

In another thread I wrote this, which solved my problem:

Well, I have found the solution. All evidence in my case pointed to that NI has stored
a corrupt file somewhere that it reads upon reboot, and that this file is not removed during uninstall.
So I searched the usual folders for Native Instruments folder, and renamed the containing folders to X-<something>-

Basically I did the following, and I had nothing that needed saving, but I guess it's good to keep the backup by renaming the folders instead of deleting them if presets one has setup is stored somewhere there.


1.I Inactivated the device "KOMPLETE KONTROL M32 MIDI"

2. I stopped every NI-service I could find and the app started in the background called "NTKDaemon" and whatever NI-related wasn't stopped by the services. This is because the folders contained in the native instruments folders was locked and could not be renamed otherwise.

3. In AppData/Local/Native Instruments folder I renamed all folders with a prefix "X-" i had to get them back. In c:\ProgramData\Native Instruments I renamed the folders "Controller Editor" and "Komplete Kontrol"

4. Reboot

5. Activated the device "KOMPLETE KONTROL M32 MIDI"

6. Rebooted once more.

7. Everything is working and KOMPLETE KONTROL M32 MIDI is not blocked anymore, I can reboot how many times I want and the problem is gone.. no more locked M32 MIDI.

[Ploppz]

Nothing to do with memory. It's an archaic windows error which usually actually means "MIDI port already in use".

Normally, only one application at a time can open a port.

You probably have ports open in Komplete Kontrol? You don't need that.

KK speaks directly to the hardware (normal mode), DbM uses the midi input/output ports (MIDI mode) Forget about KK (or maybe use the plugin) if your using DrivenByMoss.

Thanks for the clarification.

The reason I installed KK is because it said so in the DrivenByMoss user manual:



At this moment I am quite confused because I have this problem even when I don't start the KK application after boot, but what is still running is this:



Is the "Host Integration" problematic? Are there settings in KK that I must have inadvertently made that still are in effect even without the app running?

[backtomusic]

Too me it sounds like you have my problem if ir persists upon boot and the only thing you started is bitwig. Then tou nerd to manually delete folders that contains settings, for it was those listen above

[Ploppz]

Too me it sounds like you have my problem if ir persists upon boot and the only thing you started is bitwig. Then tou nerd to manually delete folders that contains settings, for it was those listen above

Many thanks, your instructions fixed it!!

[EnGee]

Too me it sounds like you have my problem if ir persists upon boot and the only thing you started is bitwig. Then tou nerd to manually delete folders that contains settings, for it was those listen above

Many thanks, your instructions fixed it!!

+1
Thanks backtomusic!

[16Hz]

Quick solution for M32:

• Delete file "%PROGRAMDATA%\Native Instruments\Komplete Kontrol\Komplete Kontrol AM Settings.dat"
• Reboot.

File may be named somewhat differently based on keyboard used, but it's the Komplete Kontrol settings file in given location anyway.

Thats it, midi ports are working properly again.

[subtlearts]

Just a quick reply in case anyone else is searching for answers and finds this thread, as I did...

The 'easy' solution proposed by 16hz just above does work, but in my case it did not 'stick' - that is, I kept having to do it over and over, and sometimes it would work and sometimes not, like I would sometimes have to do it a couple of times in a row including rebooting, which got annoying pretty quickly and I couldn't find a way around it.

The slightly more fiddly approach detailed by 'backtomusic' further back, on the other hand, seems to have solved the problem in a more persistent manner, so that - so far - I have not had to repeat the steps, and the controller just works with Bitwig, without any issues. So the extra futzing about seems worthwhile.

[zerocrossing]

So, I started getting this today and I can't figure it out. Stupid Windows update. If I run MidiView, and try to select a device like my Nina (USB MIDI) it tells me another application is using it. There is no application running other than MidiView. Anyone have any idea what could be going on? Is there any way of knowing what's gotten control of a device?

[BobDog]

You can use Process Explorer to work out what might be locking it, there are some details here: https://gearspace.com/board/music-compu ... ation.html