# "Overflow" message

**URL:** <https://community.blokas.io/t/overflow-message/4543>\
**Category:** Support\
**Created:** [June 13, 2023, 2:15pm UTC](https://community.blokas.io/t/overflow-message/4543 "2023-06-13T14:15:42Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ahgi](https://community.blokas.io/user_avatar/community.blokas.io/ahgi/32/3831_2.png) [@ahgi](https://community.blokas.io/u/ahgi)\
**Post date:** [June 13, 2023, 2:15pm UTC](https://community.blokas.io/t/overflow-message/4543/1 "2023-06-13T14:15:42Z")

</div>

Hi  
I am using the midi hub for awhile,  
‏it is very nice.  
‏solved alot of problems  
‏the product is very necessary in live performance.

Some time it’s crash - all the midi note play whit a delay  
I didn’t know why…  
It is happened when I sending a  
midi Aftertoch & midi controller & pitch bend  
at the same time  
so  
I contacted to the midi hub editor and  
I get the this message “Overflow”

Is there anything that can do to solve it?

---

<div class="post-metadata">

**Author:** ![Giedrius](https://community.blokas.io/letter_avatar_proxy/v4/letter/g/6a8cbe/32.png) [@Giedrius](https://community.blokas.io/u/Giedrius)\
**Post date:** [June 14, 2023, 6:40am UTC](https://community.blokas.io/t/overflow-message/4543/2 "2023-06-14T06:40:28Z")

</div>

Hi, you should make sure you’re not getting MIDI data loopbacked into Midihub itself, otherwise it can produce tremendous amount of messages and slow the whole system down.

Another possibility is inadvertently duplicating messages within a preset, without having the right filters in place.

The “Overflow” message in the MIDI monitor pane indicates, that the MIDI monitoring can’t keep up with providing the editor with all the MIDI data flowing, the physical MIDI transfer between MIDI and USB ports has the highest priority, so in some instances, even if you see “Overflow” in the MIDI monitor pane, it might not necessarily mean that some MIDI messages are getting lost.

By the way, the messages you mentioned are all rather chatty - they produce lots of MIDI messages even within a short period, you may be hitting the inherent MIDI bandwidth limitation of 3125 bytes per second. Most MIDI messages are made up of 3 bytes, so transferring, say, a single CC message takes 0.96ms, if there’s a mix of lots of messages at the same time, they all get queued, and sent, the delay can quickly add up to \>= 5ms which becomes easily noticeable to the performer.

You could post up your preset for us and the community to take a look if there’s anything to fix, let us know which inputs receive which kinds of MIDI data, and whether there’s something we should know about the further MIDI connections between your MIDI instruments, like if there’s some daisy chain on Midihub output that ends up connected to Midihub’s input again.

---

<div class="post-metadata">

**Author:** ![resonotter](https://community.blokas.io/user_avatar/community.blokas.io/resonotter/32/6354_2.png) [@resonotter](https://community.blokas.io/u/resonotter)\
**Post date:** [June 14, 2023, 8:32am UTC](https://community.blokas.io/t/overflow-message/4543/3 "2023-06-14T08:32:51Z")

</div>

> [@Giedrius](#):
>
> The “Overflow” message in the MIDI monitor pane indicates, that the MIDI monitoring can’t keep up with providing the editor with all the MIDI data flowing, the physical MIDI transfer between MIDI and USB ports has the highest priority, so in some instances, even if you see “Overflow” in the MIDI monitor pane, it might not necessarily mean that some MIDI messages are getting lost.

> By the way, the messages you mentioned are all rather chatty - they produce lots of MIDI messages even within a short period, you may be hitting the inherent MIDI bandwidth limitation of 3125 bytes per second. Most MIDI messages are made up of 3 bytes, so transferring, say, a single CC message takes 0.96ms, if there’s a mix of lots of messages at the same time, they all get queued, and sent, the delay can quickly add up to \>= 5ms which becomes easily noticeable to the performer.

Hey, @Giedrius, these are two **really** useful bits of knowledge!  
If they’re not _already_ somewhere (that I’ve overlooked), it would be good to them pinned.

* * *

PS. On “chatty” messages, would a `Discarder` pipe be _theoretically_ viable?  
It would throw away m/n of selected message type (PB, CP, etc), a bit like `Tempo Div` but with maybe time-related thresholds.

Strikes me it might be popular for performance patchers…

---

<div class="post-metadata">

**Author:** ![ahgi](https://community.blokas.io/user_avatar/community.blokas.io/ahgi/32/3831_2.png) [@ahgi](https://community.blokas.io/u/ahgi)\
**Post date:** [June 14, 2023, 11:15am UTC](https://community.blokas.io/t/overflow-message/4543/4 "2023-06-14T11:15:43Z")

</div>

![midi hub 1](https://community.blokas.io/uploads/default/original/2X/b/b1d0dc86ff7679b218ea5c0e093fb57e0fbb8da1.gif)

---

<div class="post-metadata">

**Author:** ![ahgi](https://community.blokas.io/user_avatar/community.blokas.io/ahgi/32/3831_2.png) [@ahgi](https://community.blokas.io/u/ahgi)\
**Post date:** [June 14, 2023, 11:23am UTC](https://community.blokas.io/t/overflow-message/4543/5 "2023-06-14T11:23:42Z")

</div>

Ok  
My instruments are

1. I am using the korg pa1000 as a main keyboard
2. Roland MC 101 for a drums bass percussion and a guitar  
3.korg wavestate as a secondary keyboard
3. Ak5 midi quarter tune remote for a scale  
(Arabic style) by [https://kelfar.net/](https://kelfar.net/)

It is work like that :

I send all midi data from korg pa to the midi hub input A  
In the midi hub i filter the midi SYS Exclusive message  
(the ROLAND MC response badly to midi exclusive message and should be blocked)  
And send it to Roland MC 101 OUT A  
I am Using 4 midi channels

In out B to Korg wavestate  
I send midi clock & midi control  
(for using the pitch joystick & expression pedal form korg pa to Korg wavestate)

In input B  
There’s ak5 midi scale as a midi through to out B to Korg wavestate  
The ak5 sand a midi Aftertoch message for change the scale

When I using quarter tune and playing and change the expression there is a daily in the midi hub

It’s too complicated… I know 😅

---

<div class="post-metadata">

**Author:** ![ahgi](https://community.blokas.io/user_avatar/community.blokas.io/ahgi/32/3831_2.png) [@ahgi](https://community.blokas.io/u/ahgi)\
**Post date:** [June 14, 2023, 11:25am UTC](https://community.blokas.io/t/overflow-message/4543/6 "2023-06-14T11:25:30Z")

</div>

![my set](https://community.blokas.io/uploads/default/original/2X/4/4f9807e99a4e882a757dfc22b8b16b202dfae11c.jpeg)

---

<div class="post-metadata">

**Author:** ![Giedrius](https://community.blokas.io/letter_avatar_proxy/v4/letter/g/6a8cbe/32.png) [@Giedrius](https://community.blokas.io/u/Giedrius)\
**Post date:** [June 16, 2023, 5:54am UTC](https://community.blokas.io/t/overflow-message/4543/7 "2023-06-16T05:54:16Z")

</div>

Where are the AK5 cables connected to?

---

<div class="post-metadata">

**Author:** ![Giedrius](https://community.blokas.io/letter_avatar_proxy/v4/letter/g/6a8cbe/32.png) [@Giedrius](https://community.blokas.io/u/Giedrius)\
**Post date:** [June 16, 2023, 6:05am UTC](https://community.blokas.io/t/overflow-message/4543/8 "2023-06-16T06:05:10Z")

</div>

> [@resonotter](#):
>
> Hey, @Giedrius, these are two **really** useful bits of knowledge!  
> If they’re not _already_ somewhere (that I’ve overlooked), it would be good to them pinned.

The first bit is hinted very succinctly at “Overflow” description in the docs: [MIDI Monitor - Midihub Documentation](https://blokas.io/midihub/docs/midi-monitor/), as in it’s talking about only the monitor data. 🙂

For the other thing, it might be a good idea to have some article on how MIDI works here in the community, but there’s ought to be lots of articles already written on this subject on the internet, so I’m not sure if we should have our own variation.

> [@resonotter](#):
>
> PS. On “chatty” messages, would a `Discarder` pipe be _theoretically_ viable?  
> It would throw away m/n of selected message type (PB, CP, etc), a bit like `Tempo Div` but with maybe time-related thresholds.
> 
> Strikes me it might be popular for performance patchers…

It could help for some devices that have difficulty to cope with the amount of data they receive, but it would not solve a MIDI controller sending too much data to the Midihub’s inputs taking a long time to arrive.

I’ve seen some MIDI controllers with knobs sending CCs in step size of 1 for whatever quick twist of the knob you make, which is not really ideal. 🙂

---

<div class="post-metadata">

**Author:** ![ahgi](https://community.blokas.io/user_avatar/community.blokas.io/ahgi/32/3831_2.png) [@ahgi](https://community.blokas.io/u/ahgi)\
**Post date:** [June 16, 2023, 6:25am UTC](https://community.blokas.io/t/overflow-message/4543/9 "2023-06-16T06:25:44Z")

</div>

to input 2

in 1 korg pa  
in 2 ak5  
out 1 roland mc 101  
out 2 Korg Wavestate

---

<div class="post-metadata">

**Author:** ![Giedrius](https://community.blokas.io/letter_avatar_proxy/v4/letter/g/6a8cbe/32.png) [@Giedrius](https://community.blokas.io/u/Giedrius)\
**Post date:** [June 16, 2023, 6:28am UTC](https://community.blokas.io/t/overflow-message/4543/10 "2023-06-16T06:28:59Z")

</div>

Where does it get its own MIDI input from? Or just the buttons on the unit?

---

<div class="post-metadata">

**Author:** ![ahgi](https://community.blokas.io/user_avatar/community.blokas.io/ahgi/32/3831_2.png) [@ahgi](https://community.blokas.io/u/ahgi)\
**Post date:** [June 16, 2023, 6:30am UTC](https://community.blokas.io/t/overflow-message/4543/11 "2023-06-16T06:30:45Z")

</div>

> [@Giedrius](#):
>
> just the buttons on the unit

just the buttons on the unit

---

<div class="post-metadata">

**Author:** ![ahgi](https://community.blokas.io/user_avatar/community.blokas.io/ahgi/32/3831_2.png) [@ahgi](https://community.blokas.io/u/ahgi)\
**Post date:** [June 16, 2023, 6:34am UTC](https://community.blokas.io/t/overflow-message/4543/12 "2023-06-16T06:34:54Z")

</div>

it is a remote control micro tune for change the scale - each button change the key tune

---

<div class="post-metadata">

**Author:** ![resonotter](https://community.blokas.io/user_avatar/community.blokas.io/resonotter/32/6354_2.png) [@resonotter](https://community.blokas.io/u/resonotter)\
**Post date:** [June 16, 2023, 6:43am UTC](https://community.blokas.io/t/overflow-message/4543/13 "2023-06-16T06:43:44Z")

</div>

Hi @ahgi

I see in your photo, you have 3 cables going into Kelfar:

- 1 is power/USB
- 1 is MIDI out
- What is the 3rd one for?

---

<div class="post-metadata">

**Author:** ![ahgi](https://community.blokas.io/user_avatar/community.blokas.io/ahgi/32/3831_2.png) [@ahgi](https://community.blokas.io/u/ahgi)\
**Post date:** [June 16, 2023, 6:49am UTC](https://community.blokas.io/t/overflow-message/4543/14 "2023-06-16T06:49:58Z")

</div>

to midi in of the korg pa1000  
there is no loop from korg pa1000

---

<div class="post-metadata">

**Author:** ![Giedrius](https://community.blokas.io/letter_avatar_proxy/v4/letter/g/6a8cbe/32.png) [@Giedrius](https://community.blokas.io/u/Giedrius)\
**Post date:** [June 16, 2023, 7:12am UTC](https://community.blokas.io/t/overflow-message/4543/15 "2023-06-16T07:12:05Z")

</div>

So 1 MIDI output from AK5 goes directly to Midihub Input B, and 2nd MIDI output from AK5 goes to PA1000.

If PA1000 is merging & forwarding the incoming MIDI data to its own output, which is connected to Midihub Input A, this could cause problems.

---

<div class="post-metadata">

**Author:** ![ahgi](https://community.blokas.io/user_avatar/community.blokas.io/ahgi/32/3831_2.png) [@ahgi](https://community.blokas.io/u/ahgi)\
**Post date:** [June 16, 2023, 9:00am UTC](https://community.blokas.io/t/overflow-message/4543/16 "2023-06-16T09:00:41Z")

</div>

the korg pa1000 doesn’t merge any data  
I disconnected MIDI IN in from korg pa1000 and it is the same reaction

---

<div class="post-metadata">

**Author:** ![Giedrius](https://community.blokas.io/letter_avatar_proxy/v4/letter/g/6a8cbe/32.png) [@Giedrius](https://community.blokas.io/u/Giedrius)\
**Post date:** [June 16, 2023, 9:14am UTC](https://community.blokas.io/t/overflow-message/4543/17 "2023-06-16T09:14:04Z")

</div>

Does this issue occur only for a little while after you trigger the aftertouch and pitch bend messages, or it keeps being delayed afterwards, no matter what?

---

<div class="post-metadata">

**Author:** ![ahgi](https://community.blokas.io/user_avatar/community.blokas.io/ahgi/32/3831_2.png) [@ahgi](https://community.blokas.io/u/ahgi)\
**Post date:** [June 16, 2023, 9:55am UTC](https://community.blokas.io/t/overflow-message/4543/18 "2023-06-16T09:55:34Z")

</div>

it is happened when i use the expression pedal and pitch band joystick while the AK 5 send after touch midi cc message

---

<div class="post-metadata">

**Author:** ![resonotter](https://community.blokas.io/user_avatar/community.blokas.io/resonotter/32/6354_2.png) [@resonotter](https://community.blokas.io/u/resonotter)\
**Post date:** [June 16, 2023, 1:26pm UTC](https://community.blokas.io/t/overflow-message/4543/19 "2023-06-16T13:26:18Z")

</div>

@ahgi

I know you want to use MIDI DIN to connect to your Wavestate but…

… I wonder if it’s worth trying to connect Midihub → {USB} → PC/Mac → {USB} → Wavestate

(…using MidiPatchbay(Mac) or MIDI-OX (PC))

…_just to investigate?_

* * *

This would _also_ let you _ **record** _ a few seconds of …

> the expression pedal and pitch band joystick while the AK 5 is sending after touch midi cc message

…into a DAW to be able to see just what the PA1000 and the AK5 are sending out to Wavestate.

Won’t _solve_ your problem (yet) but might help to see _what_ your problem is:  
you can upload the .mid file here

---

<div class="post-metadata">

**Author:** ![ahgi](https://community.blokas.io/user_avatar/community.blokas.io/ahgi/32/3831_2.png) [@ahgi](https://community.blokas.io/u/ahgi)\
**Post date:** [June 16, 2023, 1:58pm UTC](https://community.blokas.io/t/overflow-message/4543/20 "2023-06-16T13:58:14Z")

</div>

I will try with usb cable and let you know 🙂

[Next page](https://community.blokas.io/t/overflow-message/4543.md?page=2)
