FCB Manager 2.2.3 MAC OS Monterey "Not enough MIDI Sysex Input buffers"

10 posts / 0 new
Last post
ttango
ttango's picture
FCB Manager 2.2.3 MAC OS Monterey "Not enough MIDI Sysex Input buffers"

MAC OS Monterey. MIO USB device MAC M`1 FCB Manager 2.2.3 FCB 1010 FW 2.5

I get error Not enough MIDI Sysex input buffers when trying to write to the FCB 1010

I am holding the down button and turning on the pressing up button until config lights up.

I select send to FCB 1010

Press 7 sysex receive and wait. 

error. "Not enough MIDI sysex input buffers". I see this error had previously been fixed in, I think 2.0?

A little history

I have never been able to write to the FCB ever using any types of tools and or methods.  I purchased the UNO chip and have never been able to write to the FCB 1010 either.  I have replaced the UNO chip with the original Behringer 2.5 chip and tried your product a number of times.

I suspect that maybe the error might be the last [try catch] when all else fails thus, this error. Any way looking to hear back for some other ideas. 

Tim 

Mark van den Berg
Mark van den Berg's picture

error. "Not enough MIDI sysex input buffers". I see this error had previously been fixed in, I think 2.0?

Indeed, as the version history in the FCB1010 Manager manual states, the 2.0.0 macOS edition fixed a bug that could cause the terminating F7 byte of an incoming SysEx message to be cut off, which could then lead to the "Not enough MIDI SysEx input buffers" error message.
However, this error message itself can still occur, namely when the application is no longer able to process the incoming SysEx messages fast enough to prevent an overflow of the application's 256 SysEx input buffers of 256 bytes each.

I get error Not enough MIDI Sysex input buffers when trying to write to the FCB 1010

This indicates that SysEx messages are being sent to FCB1010 Manager during its Send operation, which shouldn't happen.

As a first step, you can monitor which SysEx messages FCB1010 Manager is receiving in the "MIDI input messages" window (accessible from the main window's menu via View -> MIDI -> Input messages): press the Record button, then perform your usual Send routine.

FCB1010 Manager's Send operation only sends a single SysEx message (consisting of 2352 bytes) to the FCB1010, so your input buffer overflow error is probably caused by an infinite loop.
Do you perform step 1 mentioned in the "Send data to the FCB1010" dialog box: "Disconnect any cable from the FCB1010's MIDI IN socket"?
If you do, the infinite loop can't involve your FCB1010, so it must be created elsewhere in your MIDI setup.
An interesting experiment might be to perform the Send operation with your FCB1010 being switched off: if the "Not enough ... input buffers" error still occurs, then you know there's something wrong with your MIDI setup.

Hope this helps,
   Mark.

ttango
ttango's picture

OK, a little back story.  I watched the video where it had me CONFIG 8 to fix the issue with MIDI thru, plus being a MAC I left the input cable in.  The only way I get any response is leaving both cables in.

I have included the midi output for you, but I'm not getting the error now.

Files are rcv, send and recv 2

I received the data and cut out bank 0 preset 1 so there is no data and then sending that back.   8 bytes,  no error. [$F0 $00 $20 $32 $01 $0C $0F $F7] I press down after sending data and it counts down 9-0.  then I recv the data back, and as you can see preset 0:1 is back to the original values.

If I remove the out when sending , or the in when receiving I get nothing.

I will keep testing

I guess I will send the files to you through mail

Mark van den Berg
Mark van den Berg's picture

In my first reply I wrote:

Do you perform step 1 mentioned in the "Send data to the FCB1010" dialog box: "Disconnect any cable from the FCB1010's MIDI IN socket"?
If you do, the infinite loop can't involve your FCB1010, so it must be created elsewhere in your MIDI setup.

This is nonsense. blush
Step 1 is necessary to ensure that step 2 (switching the FCB1010 on in Global Configuration mode) succeeds.
However, step 3 involves (re)connecting the cable at the FCB1010's MIDI IN socket, so step 1 doesn't prevent any infinite loop after step 6 (sending the SysEx message to the FCB1010).

Whether the FCB1010 passes on any message being received at its MIDI IN socket to its MIDI OUT socket is determined by the setting of the MERGE function.
As section 2.2.3 ("CONFIG page") of the official FCB1010 User's Manual explains, the MERGE function

[a]llows to merge MIDI IN data with FCB1010-generated data. The combined data stream is subsequently output at the MIDI OUT.

So to prevent messages being received by the FCB1010's MIDI IN socket from being looped back to the computer via the FCB1010's MIDI OUT socket, you can do one of two things:

  • Disable the FCB1010's MERGE function "permanently" via pedal 8 on the CONFIG page of Global Configuration.
  • Temporarily disconnect the cable between the FCB1010's MIDI OUT socket and the computer, either at the MIDI socket side or at the computer side.

I watched the video where it had me CONFIG 8 to fix the issue with MIDI thru, plus being a MAC I left the input cable in.  The only way I get any response is leaving both cables in.

At least during FCB1010 Manager's Send operation you don't want any response from the FCB1010's MIDI OUT. So you should use one of the two methods mentioned above. In particular, if MERGE is on, simply disconnect the cable before you perform the Send operation.

ttango
ttango's picture

Oh, BTW, the soft FCB or virtual FCB only displays the one switch and a sort of drawn line for the two expression pedals and nothing else. I will send a print screen to you through email

 

Mark van den Berg
Mark van den Berg's picture

the soft FCB or virtual FCB only displays the one switch and a sort of drawn line for the two expression pedals and nothing else

This is a totally different issue, so it would have been better if you had created a separate topic for this.
But thanks for reporting this! I'll look into it.

Mark van den Berg
Mark van den Berg's picture

the soft FCB or virtual FCB only displays the one switch and a sort of drawn line for the two expression pedals and nothing else

This issue turned out to be caused by yet another bug in the underlying Lazarus library communicating with the 64-bit Cocoa interface (which FCB1010 Manager has been using since version 2.2.0).

FCB1010 Manager 2.2.4 Alpha 1 tries to work around this bug:
https://mountainutilities.eu/dl/fcbman-2.2.4a1.dmg

This version makes the Soft FCB1010 window look OK again on my system, but I don't have Monterey.
So if you can confirm that it works on Monterey too, I'll publish the corresponding Release version.

ttango
ttango's picture

sending data

Power + down, UP UP,  DOWN to "MIDI Function" banks says 01.(why not just UP once?)

Both input and output in and It and it sort of works , I get data in the messages screen. then the error

If I remove the output and retry the exact same way I get nothing

 

It will only send data to the FCB if both Inputs and Outputs are connected and then I get the error

I deleted all of BANK 0 and it sent 2226 bytes to the FCB with no error.  However, MIDIView showed that 2352 bytes were sent. See attached PDF "sending MIDI correct"

the second time I ran it I deleted all of Bank 0 and it was 2187 bytes from MIO, 2352 from MidiView.

 

this is where I am now

tim

 

ttango
ttango's picture

OBTW, yes  I am removing the midi in and then attaching it as the dialog box says. I thought I had said that earlier.

 

Tim

ttango
ttango's picture

this thing is toast, as it won't even do the river dance

 

thanks

 

trash time