Error: Cannot add MIDI input buffer

5 posts / 0 new
Last post
drepalla
drepalla's picture
Error: Cannot add MIDI input buffer

Hi all

I am new to the BC Control software, and recently bought a BCF2000

After installing the BC Manager latest version and run, I get this error message prompt:

Error: Cannot add MIDI input buffer, the MIDI header was not prepared. Use the prepare function to prepare the header, and then try again.

I tried the portable version too, same error.

Problem is that when I acknowledge the error box, BC Manager shuts down so it is impossible for me to "use the prepare function".

My system is Core i7 with 64 bit Windows 10 operating system, and my midi interface is MOTU MTP AV.

The BCF2000 is in midi configuration mode 4. - midi only

Any ideas?

Thanks

in advance,

 

 

drepalla

 

 

drepalla
drepalla's picture

Hi again

I now tried installing the USB driver for the BCF2000, the driver works fine, but still the same error in BC manager. :(

 

 

Mark van den Berg
Mark van den Berg's picture

I tried the portable version too, same error.

That's natural: the 32-bit and 64-bit executables of the installer are identical to the executables of the 32-bit and 64-bit portable editions.

Problem is that when I acknowledge the error box, BC Manager shuts down so it is impossible for me to "use the prepare function".

This error message is provided by the operating system. BC Manager doesn't have some "prepare function"  that the user can execute.

my midi interface is MOTU MTP AV.

The BCF2000 is in midi configuration mode 4. - midi only

I now tried installing the USB driver for the BCF2000, the driver works fine, but still the same error in BC manager.

I'm confused: The first quote above (from your original post) suggests that you were routing the BCF in S-4 mode to the MOTU MTP AV via MIDI cables. However, the second quote (from your second post) suggests that you're using the BCF in a U mode.
So which is it?

Note that communication between a BCF and a computer via the BCF's USB cable is only possible if the BCF is in a U operating mode: U-1 is best if you only need to access the BCF itself, U-3 is required if you also want to access the BCF's MIDI Input socket and 2 MIDI Output sockets.

For troubleshooting your situation it's best to start with U-1: it reduces the risk of inadvertent communication attempts with incorrect MIDI I/O devices. For instance, if the BCF is in U-3, the modern Windows (>=7) USB driver for the BCF creates a dysfunctional MIDI input device (called "BCF2000 Port 3" or so), which produces an "undefined external error" when any program attempts to open it. So it's best to disable this device in BC Manager's MIDI options dialog box to prevent problems.

I don't know what's causing your "Cannot add MIDI input buffer" error. It might be some unrelated "rogue" MIDI input device.
Can you identify the device causing this error? For instance, does the error also occur if the BCF is off?
It might also help to use the MIDI Tools application to test this: MIDI Tools is cleaner than BC Manager in that it doesn't do any BCF-specific things.

Hope this helps,
   Mark.

drepalla
drepalla's picture

Hi Mark

I appreciate you trying to help me with this problem, I was hoping that this was a known error and maybe I was doing something wrong.

The error comes regardless if I have the BCF2000 turned on or not, and I stick to the USB mode 1 now, for simplicity. (U1)

You are right that this is a windows error message, it lookes like it comes from the windows WinMM dynamic Link Library, String ID#64:

https://www.win7dll.info/winmm_dll.html

I use MIDI a lot and my PC has more that one Midi interface drivers installed, and software too, Loopmidi and RTP midi, but I never encounted this error or any problems before.

I just now tried installing Midi tool as well and I get excactly the same error. All other MIDI applications are running fine, Midi-OX, RTPMIDI, loopMIDI, BLoxPander, VanBasco's Karaoke player, Varranger2.. no MIDI relatet problems with any other programs.

Next I will try to install it on my laptop from Work, and see how that goes.

Thanks again for trying to help me with this.

drepalla

 

Mark van den Berg
Mark van den Berg's picture

Apologies for the late reply, but I've been very busy, and this is a tricky problem.

I've never encountered this problem before, and considering that thousands of people have used my MIDI applications, there must be something exceptional about your system.
My best guess at this point is that one of your MIDI input devices doesn't like my applications trying to set up 256 SysEx buffers of 256 bytes each.

So here's a test version of MIDI Tools that will tell you which MIDI input device is involved:
MIDI Tools 2.2.2 Alpha 1 32-bit
MIDI Tools 2.2.2 Alpha 1 64-bit
(These zip files only contain the executable files. You can simply unzip them to a folder to which you have write access, and run them.)
In this test version, the error message concerning the SysEx buffer includes the name of the MIDI input device to which the error relates.
Then disable this MIDI input device temporarily (e.g. via Windows' "Device Manager"), and run MIDI Tools again: then the error should no longer occur.